SNMP::Info::Layer3::C6500 - SNMP Interface to Cisco Catalyst 6500 Layer 2/3 Switches running IOS and/or CatOS
Max Baker
# Let SNMP::Info determine the correct subclass for you. my $c6500 = 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 = $c6500->class(); print "SNMP::Info determined this device to fall under subclass : $class\n";
Abstraction subclass for Cisco Catalyst 6500 Layer 2/3 Switches.
These devices run IOS but have some of the same characteristics as the Catalyst WS-C family (5xxx). For example, forwarding tables are held in VLANs, and extended interface information is gleaned from CISCO-SWITCH-MIB.
For speed or debugging purposes you can call the subclass directly, but not after determining a more specific class using the method above.
my $c6500 = new SNMP::Info::Layer3::C6500(...);
See "Required MIBs" in SNMP::Info::CiscoVTP for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoStack for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CDP for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoStats for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoImage for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoPortSecurity for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoConfig for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoPower for its own MIB requirements.
See "Required MIBs" in SNMP::Info::Layer3 for its own MIB requirements.
See "Required MIBs" in SNMP::Info::CiscoStpExtensions for its own MIB requirements.
These are methods that return scalar value from SNMP
Returns 'cisco'
Returns 1. Use vlan indexing.
See documentation in "GLOBALS" in SNMP::Info::CiscoVTP for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoStack for details.
See documentation in "GLOBALS" in SNMP::Info::CDP for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoStats for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoImage for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoPortSecurity for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoConfig for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoPower for details.
See documentation in "GLOBALS" in SNMP::Info::Layer3 for details.
See documentation in "GLOBALS" in SNMP::Info::CiscoStpExtensions for details.
These are methods that return tables of information in the form of a reference to a hash.
Returns reference to hash of iid to current link duplex setting.
Newer software versions return duplex based upon the result of $c6500->el_duplex(). Otherwise it uses the result of the call to CiscoStack::i_duplex().
See SNMP::Info::Etherlike for el_duplex() method and SNMP::Info::CiscoStack for its i_duplex() method.
Returns reference to hash of iid to administrative duplex setting.
Newer software versions return duplex based upon the result of $c6500->p_duplex(). Otherwise it uses the result of the call to CiscoStack::i_duplex().
See SNMP::Info::CiscoStack for its i_duplex() and p_duplex() methods.
Sets port duplex, must be supplied with duplex and port ifIndex.
ifIndex
Speed choices are 'auto', 'half', 'full'.
Crosses $c6500->p_port() with $c6500->p_duplex() to utilize port ifIndex.
Example: my %if_map = reverse %{$c6500->interfaces()}; $c6500->set_i_duplex_admin('auto', $if_map{'FastEthernet0/1'}) or die "Couldn't change port duplex. ",$c6500->error(1);
Based upon the firmware version Cisco devices may support Link Layer Discover Protocol (LLDP) in addition to the Cisco-proprietary CDP. These methods will query both and return the combination of all information. As a result, there may be identical topology information returned from the two protocols causing duplicate entries. It is the calling program's responsibility to identify any duplicate entries and remove duplicates if necessary.
Returns true if the device is running either CDP or LLDP.
Returns reference to hash. Key: iid Value: local device port (interfaces)
Returns reference to hash. Key: iid Value: remote IPv4 address
If multiple entries exist with the same local port, c_if(), with the same IPv4 address, c_ip(), it may be a duplicate entry.
If multiple entries exist with the same local port, c_if(), with different IPv4 addresses, c_ip(), there is either a non-CDP/LLDP device in between two or more devices or multiple devices which are not directly connected.
Use the data from the Layer2 Topology Table below to dig deeper.
Returns reference to hash. Key: iid Value: remote port (interfaces)
Returns reference to hash. Key: iid Value: string value used to identify the chassis component associated with the remote system.
Returns reference to hash. Key: iid Value: Remote Device Type
See documentation in "TABLE METHODS" in SNMP::Info::CiscoVTP for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoStack for details.
See documentation in "TABLE METHODS" in SNMP::Info::CDP for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoStats for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoImage for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoPortSecurity for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoConfig for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoPower for details.
See documentation in "TABLE METHODS" in SNMP::Info::Layer3 for details.
See documentation in "TABLE METHODS" in SNMP::Info::CiscoStpExtensions for details.
To install SNMP::Info, copy and paste the appropriate command in to your terminal.
cpanm
cpanm SNMP::Info
CPAN shell
perl -MCPAN -e shell install SNMP::Info
For more information on module installation, please visit the detailed CPAN module installation guide.