Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
7-5
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 7 Using Cisco Fabric Services
CFS Distribution
Figure 7-2 is the same as Figure 7-1 except that node C and node D are connected using Fibre Channel.
All processes is the same in this example because node B has node C and node D the distribution list for
IP. Node C does not forward to node D because node D is already in the distribution list from node B.
Figure 7-2 Network Example 2 with Fibre Channel and IP Connections
Figure 7-3 is the same as Figure 7-2 except that node D and node E are connected using IP. Both node
C and node D forward the event to E because the node E is not in the distribution list from node B.
Figure 7-3 Network Example 3 with Fibre Channel and IP Connections
CFS Distribution over Fibre Channel
For FCS distribution over Fibre Channel, the CFS protocol layer resides on top of the FC2 layer. CFS
uses the FC2 transport services to send information to other switches. CFS uses a proprietary SW_ILS
(0x77434653) protocol for all CFS packets. CFS packets are sent to or from the switch domain controller
addresses.
CFS Distribution Scopes
Different applications on the Nexus 5000 Series switches need to distribute the configuration at various
levels. The following levels are available when using CFS distribution over Fibre Channel:
• VSAN level (logical scope)
Applications that operate within the scope of a VSAN have the configuration distribution restricted
to the VSAN. An example application is port security where the configuration database is applicable
only within a VSAN.
Note Logical scope is not supported for FCS distribution over IP.
Node A Node B Node C Node E
Node D
FC
IP
144861
Node A Node B Node C Node E
Node D
FC
IP
144862