CHAPTER
Send documentation comments to mdsfeedback-doc@cisco.com
57-1
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
57
Network Monitoring
The primary purpose of Fabric Manager is to manage the network. In particular, SAN discovery and
network monitoring are two of its key network management capabilities.
This chapter contains the following sections:
• SAN Discovery and Topology Mapping, page 57-1
• Health and Event Monitoring, page 57-4
SAN Discovery and Topology Mapping
Fabric Manager provides extensive SAN discovery, topology mapping, and information viewing
capabilities. Fabric Manager collects information on the fabric topology through SNMP queries to the
switches connected to it. Fabric Manager recreates a fabric topology, presents it in a customizable map,
and provides inventory and configuration information in multiple viewing options.
Device Discovery
Once Fabric Manager is invoked, a SAN discovery process begins. Using information polled from a seed
Cisco MDS 9000 Family switch, including Name Server registrations, Fibre Channel Generic Services
(FC-GS), Fabric Shortest Path First (FSPF), and SCSI-3, Fabric Manager automatically discovers all
devices and interconnects on one or more fabrics. All available switches, host bus adapters (HBAs), and
storage devices are discovered. The Cisco MDS 9000 Family switches use Fabric-Device Management
Interface (FMDI) to retrieve HBA model, serial number and firmware version, and host operating-system
type and version discovery without host agents. Fabric Manager gathers this information through SNMP
queries to each switch. The device information discovered includes device names, software revision
levels, vendor, ISLs, PortChannels, and VSANs.
For a VSAN change involving a third-party switch, Fabric Manager will need a second discovery to show
the correct topology due to the discovery dependency when there is any change in a mixed VSAN. The
first discovery finds the third-party switch and the subsequent discovery will show the information on
which VSAN it is going to join and can discover the end devices connected to it. You can wait for the
subsequent discovery or trigger a manual discovery