VSF split
A VSF split can occur due to a VSF link failure where all ports in the VSF link go down or any member is power-
cycled or crashes in the chain topology. This failure results in independent VSF fabric fragment each having its
own Commander role. It is recommended to configure a Multiple Active Detection (MAD) mechanism to avoid
duplicate IP addresses, routing issues and traffic forwarding problems when a VSF split occurs.
Figure 107: VSF split
Commander
+
Member 1
Member 2
Standby
Commander
+
Standby
Commander
Standby
Commander Member 1
Standby
Member 2
In the preceding figure, after the split, Member 1 will be elected as the new Standby in the previous Commander
fragment. Previous Standby will failover and become Commander. Member 2 will be elected as a new standby to
that fragment. Once the fragment become inactive, all front plane ports except VSF links will be brought down. A
limited set of CLI commands will be available on the inactive fragment.
VSF merge
VSF merge occurs on connecting two different VSF fragments having the same domain-ID through VSF links.
One of the VSF fragments reboots to merge with the other fragment and forms one VSF fabric. Devices merge
only if they have the same domain ID.
Figure 108: VSF Merge
Commander
+
Standby
Standby
Commander
Commander Standby
Member
Member
NOTE: Only two fragments can be merged at a time.
VSF commands
Configuration commands
Chapter 20 Virtual Switching Framework (VSF) 655
To Next Page
Loading...
Need help?
General