HP Cisco Nexus 5000 Cisco MDS 9000 Family CLI Configuration Guide - Release 4. - Page 1346

About FCS Chapter 55 Configuring Fabric Configuration Servers Send documentation comments to [email protected] In Figure 55-1 Management Application 1 (M1) is connected through an F port with port VSAN ID 1, and Management Application 2 (M2) is connected through an F port with port VSAN ID 2. M1 can query the FCS information of switches S1 and S3, and M2 can query switches S3 and S4. Switch S2 information is not known to both of them. FCS operations can be done only on those switches that are visible in the VSAN. Note that M2 can send FCS requests only for VSAN 2 even though S3 is also a part of VSAN 1. Figure 55-1 FCSs in a VSAN Environment Management Application 2 (port VSAN=2) F port VSAN 1 ISL1 Switch 3 (dFCS3) VSAN 2 ISL2 Management N port Application 1 F port (port VSAN=1) Switch 1 (dFCS1) Switch 4 (dFCS4) Switch 2 (dFCS2) ISL3 VSAN 3 85581 Significance of FCS This section lists the significance of FCSs. • FCSs support network management including the following: - N port management application can query and obtain information about fabric elements. - SNMP manager can use the FCS management information base (MIB) to start discovery and obtain information about the fabric topology. • FCSs support TE and TL ports in addition to the standard F and E ports. • FCS can maintain a group of modes with a logical name and management address when a platform registers with it. FCSs maintain a backup of all registrations in secondary storage and update it with every change. When a restart or switchover happens, FCSs retrieve the secondary storage information and rebuild its database. • SNMP manager can query FCSs for all IEs, ports, and platforms in the fabric. 55-2 Cisco MDS 9000 Family CLI Configuration Guide OL-18084-01, Cisco MDS NX-OS Release 4.x