SNMP::...ArubaCX(3pm)

πŸ’– SNMP::Info::Layer3::ArubaCX β€” the vibe ✨

okay bestie, so this is SNMP::Info::Layer3::ArubaCX, a Perl module that gives you an SNMP interface to L3 devices running ArubaOS-CX. It's part of the User Contributed Perl Documentation, and honestly? She's serving. πŸŽ€


🌸 AUTHORS 🌸

  • Jeroen van Ingen β€” the icon who wrote her πŸ’…

✨ SYNOPSIS ✨

no cap, the whole point is that SNMP::Info can pick the right subclass for you, so you don't even have to know who you're talking to:

# Let SNMP::Info determine the correct subclass for you.
my $cx = new SNMP::Info(
                         AutoSpecify => 1,
                         Debug       => 1,
                         DestHost    => 'myrouter',
                         Community   => 'public',
                         Version     => 2
                       )
   or die "Can't connect to DestHost.\n";

my $class      = $cx->class();
print "SNMP::Info determined this device to fall under subclass : $class\n";

that's it, that's the whole mood. she connects, she figures out what you are, she tells you. πŸ¦‹


🫢 DESCRIPTION 🫢

She's a subclass for devices running ArubaOS-CX. If that's your switch, this is your girl.

πŸ’œ Inherited Classes

she gets her whole personality from these three:

  • SNMP::Info::Layer3
  • SNMP::Info::IEEE802_Bridge
  • SNMP::Info::IEEE802dot3ad

🧚 Required MIBs

these MIBs are the bare minimum, fr fr, no MIBs no info:

  • ARUBAWIRED-FAN-MIB
  • ARUBAWIRED-VSF-MIB
  • ARUBAWIRED-POE-MIB
  • ARUBAWIRED-POWERSUPPLY-MIB

🌈 Inherited Classes' MIBs

and her inherited classes got their own needs too, so don't forget them:

  • See SNMP::Info::Layer3 for its own MIB requirements.
  • See SNMP::Info::IEEE802_Bridge for its own MIB requirements.
  • See SNMP::Info::IEEE802dot3ad for its own MIB requirements.

πŸ‘‘ GLOBALS πŸ‘‘

these are the methods that return scalar values straight from SNMP. little single facts about your device. obsessed.

  • $cx->stack_info() β€” if the device supports VSF stacking and is not in standalone mode, you get a string describing the switch family plus how many stack members there are. Example return value: '6300M (stack of 2)'. If VSF isn't supported at all, or if the device is VSF standalone, you get undef instead. sad but true. 😭
  • $cx->model() β€” returns stack_info() if it's defined. if not, she falls back to the model from "entPhysicalModelName.1". and if that's also not set, she goes to "sysObjectID" as a last resort, stripping 'arubaWiredSwitch' from the value. resourceful queen. πŸ’…
  • $cx->vendor() β€” returns the (lowercased!) value for "entPhysicalMfgName.1", or 'aruba' if there's nothing to work with.
  • $cx->os() β€” returns 'arubaos-cx'. that's it. that's the whole function. iconic.
  • $cx->os_ver() β€” returns the software version. either from "entPhysicalSoftwareRev.1", or extracted from "sysDescr".
  • $cx->fan() β€” returns a string with status information for all fans listed in "ARUBAWIRED-FAN-MIB". keep those fans cool, bestie. πŸ“

🌸 Globals imported from SNMP::Info::Layer3

See documentation in SNMP::Info::Layer3 for details.

🌸 Globals imported from SNMP::Info::IEEE802_Bridge

See documentation in SNMP::Info::IEEE802_Bridge for details.

🌸 Globals imported from SNMP::Info::IEEE802dot3ad

See documentation in SNMP::Info::IEEE802dot3ad for details.


πŸŽ€ TABLE ENTRIES πŸŽ€

these ones return tables of information β€” as a reference to a hash, naturally. so much data, so organized. 😌

  • $cx->peth_port_power() β€” power supplied by PoE ports, in milliwatts. ("arubaWiredPoePethPsePortAveragePower")

πŸ’… Overrides

  • "agg_ports" β€” returns a HASH reference mapping from slave to master port for each member of a port bundle on the device. keys are the ifIndex of the slave ports, values are the ifIndex of the corresponding master ports. slay.
  • "v_name", "qb_i_vlan", "i_vlan_type", "qb_v_egress", "qb_cv_egress", "qb_v_untagged", "qb_cv_untagged" β€” all of these are overridden to return the VLAN data structures that you'd expect for a device that implements "Q-BRIDGE-MIB", except with data coming from SNMP::Info::IEEE8021_Bridge at PBB 1. same vibe, different source. ✨

🌈 Table Methods imported from SNMP::Info::Layer3

See documentation in SNMP::Info::Layer3 for details.

🌈 Table Methods imported from SNMP::Info::IEEE802_Bridge

See documentation in SNMP::Info::IEEE802_Bridge for details.

🌈 Table Methods imported from SNMP::Info::IEEE802dot3ad

See documentation in SNMP::Info::IEEE802dot3ad for details.


okay that's the whole page, you're so welcome. πŸ’–

this was perl v5.40.1, dated 2026-02-28, from the SNMP::...ArubaCX(3pm) page β€” go read it, love her, run her. bye bestie! πŸ¦‹βœ¨πŸ’…

πŸ“¦ where this page comes from