SNMP::...Adtran(3pm)
π SNMP::...Adtran(3pm) π
okay so bestie, this is a page from the User Contributed Perl Documentation collection, and it's about SNMP::Info::Layer2::Adtran β yes the name got squished down to SNMP::...Adtran(3pm) up in the header, she's shy like that, but we know her full name and we love her π
β¨ NAME β¨
SNMP::Info::Layer2::Adtran β the SNMP Interface to Adtran Devices, your little gateway to talking to Adtran boxes over SNMP π«Ά
πΈ SYNOPSIS πΈ
the whole vibe in code form, copy it exactly bestie:
# Let SNMP::Info determine the correct subclass for you.
my $adtran = new SNMP::Info(
AutoSpecify => 1,
Debug => 1,
DestHost => 'myrouter',
Community => 'public',
Version => 2
)
or die "Can't connect to DestHost.\n";
my $class = $adtran->class();
print "SNMP::Info determined this device to fall under subclass : $class\n";
like, you just let AutoSpecify => 1 do its thing and SNMP::Info figures out the subclass for you. no manual gatekeeping. periodt π
π¦ DESCRIPTION π¦
This is the subclass for adtran Devices running JUNOS. that's literally the whole description, short and iconic.
π Inherited Classes π
she didn't come from nowhere, she got it from her mamas:
SNMP::Info::Layer2SNMP::Info::Layer3
π Inherited Classes' MIBs π
the MIB requirements are on the family, not on her, so go read:
- See "Required MIBs" in
SNMP::Info::Layer2for its own MIB requirements. - See "Required MIBs" in
SNMP::Info::Layer3for its own MIB requirements.
β¨ GLOBALS β¨
these are methods that return a scalar value from SNMP β like one cute little answer per question, no table drama πΈ
$adtran->vendor()β Returns'adtran'. that's it. she knows who she is π$adtran->os()β Returns'aos'. slay.$adtran->layers()β Ensures that layer two is reported, at least. minimum effort, maximum presence π$adtran->os_ver()β Returns the software version extracted first from"adProdSwVersion"or"adAOSDeviceVersion". so if the first one's giving nothing, she goes to the second one, and that one's got her. king behavior π₯$adtran->model()β Returns the model extracted first from"adProdName"or"adAOSDeviceProductName". same energy, same fallback order, iconic.$adtran->serial()β Returns serial number. just the serial. no notes π§
π Globals imported from SNMP::Info::Layer3 π
See documentation in "GLOBALS" in SNMP::Info::Layer3 for the details β she borrowed those and you gotta go read the source page for the full lore iykyk.
π TABLE METHODS π
These are methods that return tables of information in the form of a reference to a hash. yes bestie, a hash ref of tables, we love a data structure moment π
$adtran->v_name()β VLAN names table. πΈ$adtran->i_name()β Interface names table. β¨$adtran->i_vlan()β Returns a mapping between"ifIndex"and the PVID or default VLAN. she's matching your ports to their vlan, matchmaker core π$adtran->i_vlan_membership()β Returns reference to hash of arrays: key ="ifIndex", value = array of VLAN IDs. These are the VLANs which are members of the egress list for the port. hash of arrays?? the way that she's structured ππ
π Table Methods imported from SNMP::Info::Layer2 π
See documentation in "TABLE METHODS" in SNMP::Info::Layer2 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 bestie, no skips, no gaps, every single method and fallback order present and accounted for π«Ά
and for the little sign-off moment: this fine piece of documentation lives with perl v5.40.1 and was dated 2026-02-28, filing her under SNMP::...Adtran(3pm) β go talk to your Adtran box now, no cap ππβ¨
π¦ 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