VSF Stack Errors and Recommendations
In the expanded view of the Stack card, VSF stack-related errors and recommendations are displayed. If any member attempting to join the VSF stack encounters an error or if any configured port is not connected to member, a dummy card for that particular member is displayed with the error details.
The following table lists the possible errors and recommendations that are displayed in the card.
|
Error |
Recommendation |
|---|---|
|
Interface is physically down |
Check cabling and configuration. |
|
Loop detected on the interface |
VSF interfaces are connected back to back. Cabling needs to be fixed. |
|
Peer with incompatible product type |
Remove and replace the peer with any one of the compatible product types. |
|
Peer with incompatible software version |
VSF protocol version mismatch detected. Upgrade the device to firmware image (FL.10.07.0001) or above, before attempting to add the device to this stack. |
|
Peer attempting to auto-join on non-provisioned interface |
New switch is not able to autojoin as it is connected on non-provisioned VSF interface. |
|
Peer with non-default vsf attempting to autojoin |
Auto-join failed, Connect this device via interfaces those are the auto-join capable interfaces on this device. |
|
Peer auto-join failed, as it connected in incorrect direction |
New switch being added via autojoin should always be connected to a member which is in the direction of conductors VSF link having the highest denomination interface. |
|
Peer auto-join failed as there is no free member number available |
Remove a member using (no vsf member x) CLI and then physically disconnect and reconnect the new switch for adding it into the stack. |
|
Peer timed out |
Follow best practices for cabling. |
|
Peer is not autojoin eligible |
Configure vsf force-auto-join on the switch. Reset the switch configuration and reboot. |
|
Peer with inconsistent mac address |
Multiple VSF neighbors detected on same VSF link. Ensure the VSF interfaces of one link terminate on the same peer device. |
|
Peer with inconsistent VSF link configuration |
New switch is not able to autojoin as it is connected on non-provisioned VSF interface. |
|
Peer with multiple VSF interfaces attempting to autojoin |
- |
|
Peer autojoin validations failed. |
- |
For best cabling practices, see AOS-CX Virtual Switching Framework (VSF) Guide
Examples
The following are some examples of VSF related-errors and recommendations:
Interface is physically down
This error is displayed if any interface is shut down.
Figure 1: Interface is physically down
Loop detected on the interface
This error is displayed if there is a loop detected on the VSF configured port. To resolve this error, follow best practices for cabling.
Figure 2: Loop detected on the interface
Peer with incompatible software version
This error is displayed when the switch trying to join the stack is running the firmware prior to AOS-CX 10.07 version. To resolve this error, you need to upgrade the switch to a compatible firmware.
Figure 3: Peer with incompatible software version
Multiple port errors on a single VSF link
The following image shows the multiple port errors on a single VSF link.
Figure 4: Multiple port errors on a single VSF link
Peer with inconsistent VSF link configuration
This error is displayed when all interfaces within a single VSF link is terminating onto the same peer switch through a single VSF link. To resolve this error, follow best practices for cabling.
Figure 5: Peer with inconsistent VSF link configuration
Peer with inconsistent system MAC address
This error is displayed when same VSF link is connected to two different switches. To resolve this error, follow best practices for cabling.
Figure 6: Peer with inconsistent system MAC address
