NAME

SNMP::Info::Layer2::Catalyst - SNMP Interface to Cisco Catalyst devices running Catalyst OS.

AUTHOR

Max Baker

SYNOPSIS

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

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

DESCRIPTION

SNMP::Info subclass to provide information for Cisco Catalyst series switches running CatOS.

This class includes the Catalyst 2920, 4000, 5000, 6000 (hybrid mode) families.

This subclass is not for all devices that have the name Catalyst. Note that some Catalyst switches run IOS, like the 2900 and 3550 families. Cisco Catalyst 1900 switches use their own MIB and have a separate subclass. Use the method above to have SNMP::Info determine the appropriate subclass before using this class directly.

See SNMP::Info::device_type() for specifics.

Note: Some older Catalyst switches will only talk SNMP version 1. Some newer ones will not return all their data if connected via Version 1.

For speed or debugging purposes you can call the subclass directly, but not after determining a more specific class using the method above.

 my $cat = new SNMP::Info::Layer2::Catalyst(...);

Required MIBs

Inherited Classes' MIBs: See Required MIBs in the SNMP::Info::CiscoStack manpage for its own MIB requirements.; See Required MIBs in the SNMP::Info::CiscoVTP manpage for its own MIB requirements.; See Required MIBs in the SNMP::Info::CDP manpage for its own MIB requirements.; See Required MIBs in the SNMP::Info::CiscoStats manpage for its own MIB requirements.; See Required MIBs in the SNMP::Info::CiscoPortSecurity manpage for its own MIB requirements.; See Required MIBs in the SNMP::Info::Layer2 manpage for its own MIB requirements.

These MIBs are found in the standard v2 MIBs from Cisco.

GLOBALS

These are methods that return scalar value from SNMP

$cat->os(): Returns 'catalyst'
$cat->os_ver(): Tries to use the value from SNMP::Info::CiscoStats->os_ver() and if it fails it grabs $cat->m_swver()->{1} and uses that.
$cat->vendor(): Returns 'cisco'
$cat->cisco_comm_indexing(): Returns 1. Use vlan indexing.

TABLE METHODS

These are methods that return tables of information in the form of a reference to a hash.

Overrides

$cat->interfaces(): Returns the map between SNMP Interface Identifier (iid) and physical port name.
$cat->i_name(): Returns reference to hash of iid to human set name.; portName
$cat->i_physical(): Returns a map to IID for ports that are physical ports, not vlans, etc.
$cat->bp_index(): Returns reference to hash of bridge port table entries map back to interface identifier (iid); Crosses (portCrossIndex) to (portIfIndex) since some devices seem to have problems with BRIDGE-MIB