SNMP::...ssport(3pm)

📦

version 3.975000 · 8 versions

3.975000 · ubuntu stonking (latest)
3.974.0 · fedora 43
3.81 · ubuntu jammy
3.975.0 · fedora 44
3.95 · ubuntu noble
3.92 · debian bookworm
3.974000 · ubuntu resolute
3.972002 · debian trixie, ubuntu questing

💅 SNMP::Info::Layer3::Passport — bestie edition ✨

okay so this is SNMP::Info::Layer3::Passport, and it's the SNMP interface to modular Avaya Ethernet Routing Switch 8000 Series and VSP 9000 Series switches. yes that's a mouthful, we love her anyway 🫶

It lives in the User Contributed Perl Documentation, and ngl the vibe is very "your network closet has opinions." Let's get into it.

👑 NAME

SNMP::Info::Layer3::Passport — an SNMP Interface to modular Avaya Ethernet Routing Switch 8000 Series and VSP 9000 Series switches. periodt.

✍️ AUTHOR

Eric Miller — the icon who wrote this. 💖

✨ SYNOPSIS

so here's the move, bestie. let SNMP::Info pick the subclass for you, like a matchmaker but for MIBs:

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

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

and if you're feeling spicy and wanna skip the matchmaker, you can call the subclass directly:

my $passport = new SNMP::Info::Layer3::Passport(...);

lowkey powerful. 🔥

🌸 DESCRIPTION

She's an abstraction subclass for modular Avaya Ethernet Routing Switch 8000 Series (formerly known as Nortel/Bay Passport/Accelar, yes the name has had eras) and VSP 9000 Series switches. main character energy, honestly.

These devices share some characteristics with the stackable Avaya Ethernet Switches (Baystack). for example, extended interface information is gleaned from RAPID-CITY. the way that just works 💅

for speed or debugging purposes you can call the subclass directly — but NOT after determining a more specific class using the method above. like, do not do that. fr fr.

my $passport = new SNMP::Info::Layer3::Passport(...);

🧬 Inherited Classes

SNMP::Info::SONMP
SNMP::Info::RapidCity
SNMP::Info::Layer3

📚 Required MIBs

Inherited Classes' MIBs

See "Required MIBs" in SNMP::Info::SONMP for its own MIB requirements.
See "Required MIBs" in SNMP::Info::RapidCity for its own MIB requirements.
See "Required MIBs" in SNMP::Info::Layer3 for its own MIB requirements.

🌈 GLOBALS

these are methods that return scalar value from SNMP. lil one-value baddies. ⭐

$passport->model() — returns the model type. she checks $passport->id() against the RAPID-CITY-MIB and then parses out "rcA". detective behavior, obsessed.
$passport->vendor() — returns 'avaya'
$passport->os() — returns 'passport'
$passport->os_ver() — returns the software version extracted from "sysDescr"
$passport->serial() — returns ("rcChasSerialNumber")
$passport->root_ip() — returns the primary IP used to communicate with the device. returns the first found: CLIP (CircuitLess IP), Management Virtual IP ("rcSysVirtualIpAddr"), OSPF Router ID ("ospfRouterId"), SONMP Advertised IP Address. first come first served, no cap.

🔁 Overrides

$passport->index_factor() — required by SNMP::Info::SONMP. returns 64 for 8600, 16 for Accelar.
$passport->port_offset() — required by SNMP::Info::SONMP. returns 1.
$passport->slot_offset() — required by SNMP::Info::SONMP. returns 0.

🫶 Global Methods imported from SNMP::Info::SONMP

See documentation in "GLOBALS" in SNMP::Info::SONMP for details.

💜 Global Methods imported from SNMP::Info::RapidCity

See documentation in "GLOBALS" in SNMP::Info::RapidCity for details.

🎀 Globals imported from SNMP::Info::Layer3

See documentation in "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. hash girlies rise up 🍓

🔁 Overrides

$passport->i_index() — returns SNMP IID to Interface index. extends ("ifIndex") by adding the index of the CPU virtual management IP (if present), each CPU Ethernet port, and each VLAN, so that the virtual router ports are captured. making sure nobody gets left out 💖
$passport->interfaces() — returns a reference to the map between IID and physical Port.

Slot and port numbers on the Passport switches are determined by the formula: port = ("ifIndex % index_factor") + port_offset, slot = int("ifIndex / index_factor").

The physical port name is returned as slot.port. CPU Ethernet ports are prefixed with CPU and VLAN interfaces are returned as the VLAN ID prefixed with Vlan.

$passport->i_mac() — MAC address of the interface. note: this is just the MAC of the port, not anything connected to it. don't be fooled bestie 😭
$passport->i_description() — description of the interface. usually a little longer single word name that is both human and machine friendly. not always. 🙈
$passport->i_name() — crosses rc_alias() ("rcPortName") with ifAlias() and returns the human set port name if it exists.
$passport->ip_index() — maps the IP Table to the IID. extends ("ipAdEntIfIndex") by adding the index of the CPU virtual management IP (if present) and each CPU Ethernet port.
$passport->ip_netmask() — extends ("ipAdEntNetMask") by adding the mask of the CPU virtual management IP (if present) and each CPU Ethernet port.
$passport->bp_index() — returns a reference to a hash of bridge port table entries mapped back to interface identifier (iid).

returns ("ifIndex") for both key and value, since some devices seem to have problems with BRIDGE-MIB. not our fault, we're just being accommodating 💅

🌈 Forwarding Table

these methods utilize, in order: Q-BRIDGE-MIB, BRIDGE-MIB, and RAPID-CITY to obtain the forwarding table information.

$passport->fw_mac() — returns a reference to a hash of forwarding table MAC Addresses.

("dot1qTpFdbAddress"), ("dot1dTpFdbAddress"), ("rcBridgeTpFdbAddress")

$passport->fw_port() — returns a reference to a hash of forwarding table entries port interface identifier (iid).

("dot1qTpFdbPort"), ("dot1dTpFdbPort"), ("rcBridgeTpFdbPort")

$passport->fw_status() — returns a reference to a hash of forwarding table entries status.

("dot1qTpFdbStatus"), ("dot1dTpFdbStatus"), ("rcBridgeTpFdbStatus")

$passport->qb_fw_vlan() — returns a reference to a hash of forwarding table entries VLAN ID.

("dot1qFdbId"), ("rcBridgeTpFdbVlanId")

👻 Pseudo ENTITY-MIB information

so these devices do not support ENTITY-MIB. tragic, ik. so these methods emulate Physical Table methods using the RAPID-CITY MIB instead. fake it till you make it ✨

$passport->e_index() — returns a reference to a hash. Key and Value: Integer. the index is created by combining the slot, module, and position into a five or six digit integer. Slot can be either one or two digits while the module and position are each two digits padded with leading zero if required. math girlie behavior 🔥
$passport->e_class() — returns a reference to a hash. Key: IID, Value: General hardware type. this class only returns container, module, and power supply types.
$passport->e_descr() — returns a reference to a hash. Key: IID, Value: Human friendly name.
$passport->e_name() — returns a reference to a hash. Key: IID, Value: Human friendly name.
$passport->e_hwver() — returns a reference to a hash. Key: IID, Value: Hardware version.
$passport->e_vendor() — returns a reference to a hash. Key: IID, Value: avaya.
$passport->e_serial() — returns a reference to a hash. Key: IID, Value: Serial number.
$passport->e_pos() — returns a reference to a hash. Key: IID, Value: The relative position among all entities sharing the same parent.
$passport->e_type() — returns a reference to a hash. Key: IID, Value: Type of component/sub-component.
$passport->e_parent() — returns a reference to a hash. Key: IID, Value: The value of e_index() for the entity which 'contains' this entity. a value of zero indicates this entity is not contained in any other entity. orphan arc 😭

🧚 Table Methods imported from SNMP::Info::SONMP

See documentation in "TABLE METHODS" in SNMP::Info::SONMP for details.

🧚 Table Methods imported from SNMP::Info::RapidCity

See documentation in "TABLE METHODS" in SNMP::Info::RapidCity for details.

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

See documentation in "TABLE METHODS" in SNMP::Info::Layer3 for details.

okay that's the whole page, you ate that 💅

this was served fresh from perl v5.40.1 on 2026-02-28, courtesy of the User Contributed Perl Documentation. go forth and poll responsibly, bestie 🫶✨💖

📦 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 2026-11-03: a language model's rewrite of the original, under its terms