SNMP::...ystack(3pm)
π NAME π
SNMP::Info::Layer2::Baystack β the SNMP Interface to Avaya Ethernet Switch (Baystack) and VSP 7000 series switches, bestie π
β¨ AUTHOR β¨
Eric Miller π«Ά
πΈ SYNOPSIS πΈ
okay so literally the easiest way in, let SNMP::Info pick the right subclass for you and vibe:
# Let SNMP::Info determine the correct subclass for you.
my $baystack = new SNMP::Info(
AutoSpecify => 1,
Debug => 1,
DestHost => 'myswitch',
Community => 'public',
Version => 2
)
or die "Can't connect to DestHost.\n";
my $class = $baystack->class();
print "SNMP::Info determined this device to fall under subclass : $class\n";
π¦ DESCRIPTION π¦
It gives you abstraction to all the config info you can pull off an Avaya Ethernet Switch (formerly Nortel/Bay Baystack) and VSP 7000 series through SNMP. it's giving β¨pluggableβ¨, no cap.
π Inherited Classes
SNMP::Info::SONMPSNMP::Info::NortelStackSNMP::Info::RapidCitySNMP::Info::Layer3
π Required MIBs
BAY-STACK-PETH-EXT-MIB
π§ Inherited MIBs
fr fr, go check these yourself:
- See "Required MIBs" in
SNMP::Info::SONMPfor its MIB requirements. - See "Required MIBs" in
SNMP::Info::NortelStackfor its MIB requirements. - See "Required MIBs" in
SNMP::Info::RapidCityfor its MIB requirements. - See "Required MIBs" in
SNMP::Info::Layer3for its MIB requirements.
π GLOBALS π
These are methods that return scalar value from SNMP β lil single-value glow-ups, one at a time bestie. π
$baystack->vendor()β Returns'avaya'. iconic, honestly.$baystack->model()β Cross references$baystack->id()to theSYNOPTICS-MIBand returns the results. 303s and 304s have the same ID, so we have a hack to return depending on which it is. π ReturnsBPSfor Business Policy Switch. For others extracts and returns the switch numeric designation.$baystack->os()β Returns'baystack'or'boss'depending on software version. pick your fighter.$baystack->os_bin()β Returns the firmware version extracted from"sysDescr".$baystack->stp_ver()β Returns the particular STP version running on this device. Values:"nortelStpg","pvst","rstp","mstp","ieee8021d". (from"s5AgSysSpanningTreeOperMode")
π₯ Overrides
$baystack->index_factor()β Required bySNMP::Info::SONMP. It's the number representing the number of ports reserved per slot within the device MIB. Index factor on the Baystack switches are determined by the formula:Index Factor = 64 if (model = 470 or (os eq 'boss' and operating in pure mode)) or else Index factor = 32. Returns either32or64based upon the formula. π math girlies rise.
π Global Methods imported from SNMP::Info::SONMP
See "GLOBALS" in SNMP::Info::SONMP for details.
π Globals imported from SNMP::Info::NortelStack
See "GLOBALS" in SNMP::Info::NortelStack for details.
π Global Methods imported from SNMP::Info::RapidCity
See "GLOBALS" in SNMP::Info::RapidCity for details.
π Globals imported from SNMP::Info::Layer3
See "GLOBALS" in SNMP::Info::Layer3 for details.
π TABLE METHODS π
These are methods that return tables of information in the form of a reference to a hash. (yes, a whole hash. we love a data structure. π)
π Overrides
$baystack->interfaces()β Returns reference to the map between IID and physical Port. Slot and port numbers on the Baystack switches are determined by the formula:
port = (Interface index % Index factor)
slot = (int(Interface index / Index factor)) + Slot offset
The physical port name is returned as slot.port. π―
$baystack->i_mac()β Returns the"ifPhysAddress"table entries. Removes all entries matching'00:00:00:00:00:00'β Certain revisions of Baystack firmware report all zeros for each port mac. not the all-zeros jumpscare π$baystack->i_name()β Crosses"ifName"with"ifAlias"and returns the human set port name if exists.$baystack->peth_port_ifindex()β Maps the"pethPsePortTable"to"ifIndex"by way of the ENTITY-MIB.$baystack->peth_port_power()β Power supplied by PoE ports, in milliwatts. (from"bspePethPsePortExtMeasuredPower") β‘
ποΈ ENTITY-MIB Information
For older devices which do not support ENTITY-MIB, these methods emulate Physical Table methods using S5-CHASSIS-MIB. See "TABLE METHODS" in SNMP::Info::NortelStack for details on ns_e_* methods. the way these fake it till they make it π«Ά
$baystack->e_index()β If the device doesn't support"entPhysicalDescr", this will tryns_e_index(). Note that this is based on"entPhysicalDescr"due to implementation details ofSNMP::Info::Entity::e_index().$baystack->e_class()β If the device doesn't support"entPhysicalClass", this will tryns_e_class().$baystack->e_descr()β If the device doesn't support"entPhysicalDescr", this will tryns_e_descr().$baystack->e_name()β If the device doesn't support"entPhysicalName", this will tryns_e_name().$baystack->e_fwver()β If the device doesn't support"entPhysicalFirmwareRev", this will tryns_e_fwver().$baystack->e_hwver()β If the device doesn't support"entPhysicalHardwareRev", this will tryns_e_hwver().$baystack->e_parent()β If the device doesn't support"entPhysicalContainedIn", this will tryns_e_parent().$baystack->e_pos()β If the device doesn't support"entPhysicalParentRelPos", this will tryns_e_pos().$baystack->e_serial()β If the device doesn't support"entPhysicalSerialNum", this will tryns_e_serial().$baystack->e_swver()β If the device doesn't support"entPhysicalSoftwareRev", this will tryns_e_swver().$baystack->e_type()β If the device doesn't support"entPhysicalVendorType", this will tryns_e_type().$baystack->e_vendor()β If the device doesn't support"entPhysicalMfgName", this will tryns_e_vendor().
π Layer 2 Forwarding Database
These methods try to obtain the layer 2 forwarding database entries via the normal bridge methods as well as SPBM entries via rapid city methods. multi-source slay.
$baystack->fw_mac()β Returns reference to hash of forwarding table MAC Addresses.$baystack->fw_port()β Returns reference to hash of forwarding table entries port interface identifier (iid).$baystack->qb_fw_vlan()β Returns reference to hash of forwarding table entries VLAN ID.$baystack->fw_status()β Returns reference to hash of forwarding table entries status.
π Table Methods imported from SNMP::Info::SONMP
See "TABLE METHODS" in SNMP::Info::SONMP for details.
π Table Methods imported from SNMP::Info::NortelStack
See "TABLE METHODS" in SNMP::Info::NortelStack for details.
π Table Methods imported from SNMP::Info::RapidCity
See "TABLE METHODS" in SNMP::Info::RapidCity for details.
π Table Methods imported from SNMP::Info::Layer3
See "TABLE METHODS" in SNMP::Info::Layer3 for details.
and that's the whole page bestie, go forth and poll responsibly πβ¨
this one's running perl v5.40.1, dated 2026-02-28, and it lives under the SNMP::...ystack(3pm) name π mwah, bye π
π¦ where this page comes from
- ubuntu stonking: libsnmp-info-perl 3.975000-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms