SNMP::...Tasman(3pm)
π SNMP::Info::Layer3::Tasman π
okay bestie, so this is the SNMP::Info::Layer3::Tasman page β that's the SNMP Interface to Avaya Secure Routers β and it lives over in the User Contributed Perl Documentation section of the perl man pages. grab a boba, we're doing this πΈ
π NAME π
SNMP::Info::Layer3::Tasman β the SNMP interface to Avaya Secure Routers. that's it, that's the whole vibe check β¨
π«Ά AUTHOR π«Ά
Eric Miller wrote this one, and we thank him for his service π
β¨ SYNOPSIS β¨
so here's how you'd actually use it, bestie:
# Let SNMP::Info determine the correct subclass for you.
my $tasman = new SNMP::Info(
AutoSpecify => 1,
Debug => 1,
# These arguments are passed directly to SNMP::Session
DestHost => 'myswitch',
Community => 'public',
Version => 2
)
or die "Can't connect to DestHost.\n";
my $class = $tasman->class();
print "SNMP::Info determined this device to fall under subclass : $class\n";
basically you let it auto-detect the subclass for you, and if it can't connect to DestHost it just dies right there, no cap π those args get passed straight through to SNMP::Session so it's giving efficiency.
π DESCRIPTION π
it's a subclass for Avaya Secure Routers. iconic behavior.
𧬠Inherited Classes
SNMP::Info::Layer3SNMP::Info::MAU
π Required MIBs
NT-ENTERPRISE-DATA-MIBSYSTEM-MIBCHASSIS-MIBENVIRONMENT-MIB
π Inherited Classes' MIBs
- pop over to "Required MIBs" in SNMP::Info::Layer3 to see what it needs for its own MIB requirements.
- and also check "Required MIBs" in SNMP::Info::MAU for its own MIB requirements.
π GLOBALS π
these are the methods that hand you back scalar values straight from SNMP. little single-value besties π
$tasman->vendor()β returns'avaya'π$tasman->model()β tries to grab the model from"nnchassisModel", and if that's not available it cross-references$tasman->id()againstNT-ENTERPRISE-DATA-MIB. also it swaps'SR'in for'ntSecureRouter'in the name, because readability slay β¨$tasman->os()β returns'tasman'$tasman->os_ver()β grabs the OS version from"nnsysVersion"$tasman->ps1_type()β this is"nnenvPwrsupType.1"$tasman->ps1_status()β this is"nnenvPwrsupStatus.1"$tasman->ps2_type()β this is"nnenvPwrsupType.2"$tasman->ps2_status()β this is"nnenvPwrsupStatus.2"$tasman->nn_sys_ver()β this is"nnsysVersion.0"$tasman->nn_ch_model()β this is"nnchassisModel.0"$tasman->nn_ch_op_stat()β this is"nnchassisOperStatus.0"$tasman->nn_ch_serial()β this is"nnchassisSerialNumber.0"$tasman->serial()β tries both("nnchassisOperStatus")and("nnchassisSerialNumber"), because the oid got redefined between versions π gotta cover both bases fr fr
π Global Methods imported from SNMP::Info::Layer3
head to "GLOBALS" in SNMP::Info::Layer3 for the deets π
π Global Methods imported from SNMP::Info::MAU
and "GLOBALS" in SNMP::Info::MAU has its details too.
πΈ TABLE METHODS πΈ
these ones return tables of information, which show up as a reference to a hash. whole lil datasets, obsessed π
$tasman->i_duplex_admin()β returns a reference to a hash ofiidβ administrative duplex setting. first it checks for fixed gigabit ports, which are always full duplex, no negotiating periodt. next it checks the port administrative speed ("portAdminSpeed") β if that's set to autonegotiate, then the duplex autonegotiates too; otherwise it uses the reported port duplex ("portDuplex"). the way it layers those checks? it's giving logic π$tasman->i_speed_admin()β returns a reference to a hash ofiidβ administrative speed setting, via"portAdminSpeed".
π§ Pseudo ENTITY-MIB information
these methods emulate the ENTITY-MIB Physical Table methods using CHASSIS-MIB. cosplay but make it SNMP.
$tasman->e_index()β returns a reference to a hash. Key: IID, Value: Integer.$tasman->e_class()β returns a reference to a hash. Key: IID, Value: General hardware type.$tasman->e_descr()β returns a reference to a hash. Key: IID, Value: Human friendly name$tasman->e_vendor()β returns a reference to a hash. Key: IID, Value: avaya$tasman->e_serial()β returns a reference to a hash. Key: IID, Value: Serial number$tasman->e_pos()β returns a reference to a hash. Key: IID, Value: The relative position among all entities sharing the same parent.$tasman->e_type()β returns a reference to a hash. Key: IID, Value: Type of component/sub-component.$tasman->e_parent()β returns a reference to a hash. Key: IID, Value: The value ofe_index()for the entity which 'contains' this entity. A value of zero indicates this entity is not contained in any other entity.$entity->e_fru()β BOOLEAN. Is a Field Replaceable unit? π¦
π Table Methods imported from SNMP::Info::Layer3
see "TABLE METHODS" in SNMP::Info::Layer3 for all the details, bestie.
π Table Methods imported from SNMP::Info::MAU
and "TABLE METHODS" in SNMP::Info::MAU has its own β¨
ok so real talk β this whole thing is from perl v5.40.1, dated 2026-02-28, and it's the SNMP::...Tasman(3pm) page from the User Contributed Perl Documentation. that's the source and the date, and yes I remembered them because I would never do you like that π«Ά
love u, go configure something, mwah πβ¨π
π¦ 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