Deploying FCoE (FIP Snooping) on Dell Force 10 MXL
52
Key Items:
·
vPC domain number can be any chosen number as long as it does not conflict with other
switches in the infrastructure, but it also match on both vPC peer switches.
·
The 2 Cisco Nexus 5000 series switches should be considered as a single switch but planning and
strategies must be applied for redundant behavior. With this in mind the same VLAN’s and
configurations should exist on both switches so that if the peer-link or one or the other Nexus
switch goes down the interruption will be very low.
·
When adding the separate FCoE links it will be a good practive to insure that the FCoE VLAN’s are
not passed across the peer-link. In some instances the PortChannel for the peer-link will be
configured for all VLAN’s. It will be necessary in this situation to reconfigure to not include the
FCoE VLAN’s as mentioned.
·
Role priority
–
this is an optional step but recommended as it will establish primary and
secondary switch roles in a known configured manner. The switch with the lower priority will be
configured as the primary switch. If the peer link fails the peer keep-alive link will establish peer
switch status. If the primary switch is alive the secondary switch will suspend its vPC member
ports to prevent potential looping while the primary switch keeps all member ports active (Cisco
Systems, Inc., 2009).
