This section looks at performance monitoring for switches. Many of the issues are the same as for routers. As with routers, performance monitoring in switch hardware relates mainly to slot positioning. MIBs and CLI commands are again the main ways of collecting information on switch chasses and cards. As with routers, the polling period for switch performance MIBs should be right after a change management window period. MIB Variables for Chassis InformationFrom CISCO-STACK-MIB, MIB variables to watch for chassis information include the following:
The purpose of these MIB objects is to give you an understanding of the type of LAN switches you have in the network. Polling these MIB objects after a change management window is ideal to get an up-to-date and accurate inventory of your network. You can also use this data to quickly assess any issues that may arise with particular common hardware platforms based on Cisco Field Notices that may come out regarding major hardware defects. From ENTITY-MIB (RFC 2037) from the entPhysicalTable, other MIB objects relating to these five are as follows:
Chassis Information via show versionThe show version command can be used to obtain chassis information for performance management of a switch. For the scope of this portion of performance management, the important data reported in this output are the hardware version of the chassis, the chassis model, and the chassis serial number because all other data relates to the supervisor cards or line cards. The total number of slots in the chassis is not visible here, but the total number of configured slots is available indirectly. The show version command is useful for displaying all the hardware information for the entire switch in a single CLI output. Example 10-7 focuses on the chassis-specific data. Example 10-7 Obtaining switch chassis information with show version. Switch> show version WS-C5500 Software, Version McpSW: 4.5(1) NmpSW: 4.5(1) Copyright 1995-1999 by Cisco Systems NMP S/W compiled on Mar 29 1999, 16:09:01 MCP S/W compiled on Mar 29 1999, 16:06:50 System Bootstrap Version: 3.1.2 Hardware Version: 1.2 A Model: WS-C5500 B Serial #: 069002256 C Mod Port Model Serial # Versions --- ---- ---------- --------- ---------------------------------------- 1 D 2 WS-X5530 011437543 Hw : 2.0 Fw : 3.1.2 Fw1: 4.2(1) Sw : 4.5(1) 2 D 2 WS-X5101 003397731 Hw : 1.1 Fw : 1.1 Fw1: 1.3 Sw : 3.1(1) 6 D 12 WS-X5213 003974709 Hw : 1.0 Fw : 1.4 Sw : 4.5(1) DRAM FLASH NVRAM Module Total Used Free Total Used Free Total Used Free ------ ------- ------- ------- ------- ------- ------- ----- ----- ----- 1 32640K 14322K 18318K 8192K 4118K 4074K 512K 109K 403K Uptime is 11 days, 8 hours, 8 minutes Following is the annotated information from Example 10-7:
MIB Variables for Card InformationFrom CISCO-STACK MIB moduleTable, MIB variables to watch for chassis information include the following:
These MIBs report the hardware characteristics of the supervisor and line cards installed in the switch, such as hardware, firmware, and software versions. Typically, the line cards exhibit the same firmware and software version as the supervisor card because the supervisor card controls most line cards. There are some line cards, however, that have their own versions of software running on them, such as the FDDI modules and ATM LANE modules. These two line cards require separate software images stored in flash memory. As with the MIBs for chassis information, polling these MIB objects after a change management window is a good way to obtain up-to-date and accurate inventory of your network. You can also use this data to quickly assess any hardware defects that you learn about through Cisco Field Notices. In addition to these MIB objects, the following are comparable MIBs from the ENTITY MIB from the entPhysicalTable:
CLI Commands for Line Card InformationIn addition to MIB objects that gather hardware information on the switches, there are also a couple of show commands that can get the same bit of information from the MIBs previously discussed. Line Card Information from show versionFor the scope of this portion of performance management, the important data reported in this output are the hardware version, model, and serial number of the supervisor and line cards. The DRAM, flash, and NVRAM memory installed are reported here under module 1 or 2 where the supervisor card resides. The show version command is useful for displaying all the hardware information for the entire switch in a single CLI output. Example 10-8 focuses on the supervisor and line card specific data here. Example 10-8 Obtaining switch card information with show version. Switch> show version WS-C5500 Software, Version McpSW: 4.5(1) NmpSW: 4.5(1) Copyright 1995-1999 by Cisco Systems NMP S/W compiled on Mar 29 1999, 16:09:01 MCP S/W compiled on Mar 29 1999, 16:06:50 System Bootstrap Version: 3.1.2 Hardware Version: 1.2 Model: WS-C5500 Serial #: 069002256 Mod Port Model Serial # Versions --- ---- ---------- --------- ---------------------------------------- 1 A 2 B WS-X5530 C 011437543 D Hw : 2.0 E Fw : 3.1.2 F Fw1: 4.2(1) Sw : 4.5(1) G 2 D 2 B WS-X5101 C 003397731 D Hw : 1.1 E Fw : 1.1 F Fw1: 1.3 Sw : 3.1(1) G 6 A 12 B WS-X5213 C 003974709 D Hw : 1.0 E Fw : 1.4 F Sw : 4.5(1) G DRAM FLASH NVRAM Module Total Used Free Total Used Free Total Used Free ------ ------- ------- ------- ------- ------- ------- ----- ----- ----- 1 A 32640K H 14322K 18318K 8192K I 4118K 4074K 512K J 109K 403K Uptime is 11 days, 8 hours, 8 minutes Following is the annotated information from Example 10-8:
NOTE Please note that the software for these feature cards is stored in flash on the supervisor card, not on the individual cards directly. TIP It is good practice to clear the log after upgrading the software on the switch to accurately track the issues seen with the new software release; for example, possible exception errors or other failures that exists on the switch. Line Card Information from show moduleThe show module command will show you just about the same bits of information as the show version command, except for the module description and module status, as displayed in Example 10-9. This command allows you to see what kind of card is installed in the switch chassis and what the status is of the line cards or supervisor cards. You can also get the module, number of ports, card model, serial number, hardware version, firmware version, and software version from this output. You can also see from this output any sub-model types typically installed on the supervisor card, such as the netflow feature card (NFFC) or the uplink modules. This data is especially prevalent on the newer Supervisor cards (Supervisor III or WS-X5530). Example 10-9 Obtaining line card information from show module.Switch>show module Mod Module-Name Ports Module-Type Model Serial-Num Status --- ------------------- ----- --------------------- --------- --------- ------- 1A 2B 100BaseFX MMF SuperviC WS-X5530D 011437543E okF 2A 2B MM MIC FDDIC WS-X5101D 003397731E okF 6A 12B 10/100BaseTX EthernetC WS-X5213D 003974709E okF Mod MAC-Address(es) Hw Fw Sw --- --------------------------------------- ------ --------- ----------------- 1 00-e0-4f-73-8e-00 to 00-e0-4f-73-91-ff 2.0G 3.1.2H 4.5(1)I 2 00-60-3e-cd-55-6c 1.1G 1.1H 3.1(1)I 6 00-60-83-5d-8a-ec to 00-60-83-5d-8a-f7 1.0G 1.4H 4.5(1)I Mod Sub-Type Sub-Model Sub-Serial Sub-Hw --- -------- --------- ----------- ----- 1A NFFCC WS-F5521D 0011437958E 1.1G 1A uplinkC WS-U5533D 0008588482E 1.0G Mod SMT User-Data T-Notify CF-St ECM-St Bypass --- ------------------- --------- ----------------- ------------- 2 WorkGroup Stack 30 c-Wrap-B in absent
SNMP Traps and Syslog Messages for Chassis and Line Card InformationA number of syslog messages are useful for switch chassis performance management, and apply directly to the MIB objects and CLI commands previously discussed. They are collected in Table 10-3.
Chassis and Card Information via the Entity MIBFrom ENTITY-MIB (RFC 2037) with the CISCO-ENTITY-VENDORTYPE-OID-MIB and CISCO-ENTITY-ASSET-MIB, here are some MIBs that are useful for chassis and card information:
The purpose of these MIBs is to replace the existing CISCO-STACK MIB and make it more of a standard based on the RFC 2037 definition. The Entity MIBs are still evolving. |