SNMP::Info::Layer1::Bayhub(3pm) | User Contributed Perl Documentation | SNMP::Info::Layer1::Bayhub(3pm) |
SNMP::Info::Layer1::Bayhub - SNMP Interface to Bay/Nortel/Avaya Hubs
Eric Miller
#Let SNMP::Info determine the correct subclass for you. my $bayhub = new SNMP::Info( AutoSpecify => 1, Debug => 1, DestHost => 'myswitch', Community => 'public', Version => 2 ) or die "Can't connect to DestHost.\n"; my $class = $bayhub->class(); print "SNMP::Info determined this device to fall under subclass : $class\n";
Provides abstraction to the configuration information obtainable from a Bay hub device through SNMP. Also provides device MAC to port mapping through the proprietary MIB.
See "Required MIBs" in SNMP::Info::Layer2 for its MIB requirements.
See "Required MIBs" in SNMP::Info::NortelStack for its MIB requirements.
See "Required MIBs" in SNMP::Info::SONMP for its MIB requirements.
These are methods that return scalar value from SNMP
Removes either Baystack Hub, 5000, or 5005 depending on the model.
See "GLOBALS" in SNMP::Info::Layer2 for details.
See "GLOBALS" in SNMP::Info::NortelStack for details.
See "GLOBALS" in SNMP::Info::SONMP for details.
These are methods that return tables of information in the form of a reference to a hash.
Since hubs do not support "ifIndex", the interface index is created using the formula (board * 256 + port).
State choices are 'up' or 'down'
Example:
my %if_map = reverse
%{$bayhub->interfaces()};
$bayhub->set_i_up_admin('down',
$if_map{'1.1'})
or die "Couldn't change port state.
",$bayhub->error(1);
These devices do not support ENTITY-MIB. These methods emulate Physical Table methods using S5-CHASSIS-MIB. See "TABLE METHODS" in SNMP::Info::NortelStack for details.
See "TABLE METHODS" in SNMP::Info::Layer2 for details.
See "TABLE METHODS" in SNMP::Info::NortelStack for details.
See "TABLE METHODS" in SNMP::Info::SONMP for details.
2023-09-30 | perl v5.36.0 |