Cisco Nexus 5000 Series Switch CLI Software Configuration Guide, NX-OS 4.0(1a)N1 (OL-16597-01, January 2009)

Send feedback to [e-mail]
41-4
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 41 Managing FLOGI, Name Server, FDMI, and RSCN Databases
FDMI
------------------------
The following example shows how to display the name server database statistics for all VSANs:
switch# show fcns statistics
FDMI
Cisco Nexus 5000 Series switches provide support for the Fabric-Device Management Interface (FDMI)
functionality, as described in the FC-GS-4 standard. FDMI enables management of devices such as Fibre
Channel host bus adapters (HBAs) through in-band communications. This addition complements the
existing Fibre Channel name server and management server functions.
Using the FDMI functionality, the switch software can extract the following management information
about attached HBAs and host operating systems without installing proprietary host agents:
• Manufacturer, model, and serial number
• Node name and node symbolic name
• Hardware, driver, and firmware versions
• Host operating system (OS) name and version number
All FDMI entries are stored in persistent storage and are retrieved when the FDMI process is started.
Displaying FDMI
The following example shows how to display all HBA details for a specified VSAN:
switch# show fdmi database detail vsan 1
RSCN
The Registered State Change Notification (RSCN) is a Fibre Channel service that informs hosts about
changes in the fabric. Hosts can receive this information by registering with the fabric controller
(through SCR). These notifications provide a timely indication of one or more of the following events:
• Disks joining or leaving the fabric
• A name server registration change
• A new zone enforcement
• IP address change
• Any other similar event that affects the operation of the host
This section includes the following topics:
• About RSCN Information, page 41-5
• Displaying RSCN Information, page 41-5
• About the multi-pid Option, page 41-5
• Configuring the multi-pid Option, page 41-6