Technical data

BCSM IN A NUTSHELL 2008

Page 15 of 44

MONITORING B-SERIES SWITCHES

• Use pathinfo, topologyshow or urouteshow to visualize the fabric

• Use porterrshow and portstatsshow to see if there are any port errors / discarded frames.

Note: These are just counters so you would need a set of logs, duplicate the problem and then

capture a second set of logs to determine if the errors are incrementing at the time the problem

was happening

• Use portperfshow / APM to see the I/O (must be captured during the time of the problem). If the

switch has APM Web Tools, Fabric Manager or CLI can be used to capture end-to-end

performance data

• Fabric Watch can be used to set thresholds to see ISL hot spots and send SNMP alerts. What also

makes this tool useful is it can be used to constantly monitor the fabric

• SAN Health can be also be used to look for hot spots and I/O over time; it also tells you if you have

a zoning configuration enabled

MONITORING M-SERIES SWITCHES

• SAN Routing: EOSdc -> RTM_Flow_01 file can be used to draw out the fabric

• Port Statistics log can be used to look at port errors / discarded frames. As with the B-Series

switches these are just counters so a before and after set of logs would be required to determine is

the error counters are increasing. LIN log can be looked at for link/port issues

• Performance reports (using EFCM Standard or EFCM Enterprise can be run to look at I/O rates on

ports.

• Thresholds can be set to determine ISL hot spots

• BB Credits: EOSdc -> PortModules files can be used to look at BB-Credit counters. Note: M-i10K

only: When Remote Fabric license is enabled, a 1 Gbit/sec, 2 Gbit/sec or 10 Gbit/sec port can be

configured from 1 to 1373 BB_Credits