Reset Search
 

 

Article

How to troubleshoot a failed node or a node without a role in a stack

« Go Back

Information

 
TitleHow to troubleshoot a failed node or a node without a role in a stack
Objective
Some steps to take to troubleshoot a failed node or a node without a role in a stack. This will display itself in the following outputs:

Slot-1 Stack.1 # show stacking
Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address     Slot     Stack State     Role     Flags
------------------   ----     -----------     -------  ---
*00:04:96:28:22:1b   1        Active          Master   CA-
 00:04:96:26:64:a9   2        Active          <none>   CA-
* - Indicates this node
Flags:  (C) Candidate for this active topology, (A) Active Node
        (O) node may be in Other active topology

Slot-1 Stack.4 # show slot
Slots     Type          Configured     State          Ports
-----------------------------------------------------------
Slot-1    X250e-48p     X250e-48p      Operational    50
Slot-2    X250e-48t     X250e-48t      Failed         50
Slot-3                                 Empty          0
Slot-4                                 Empty          0
Slot-5                                 Empty          0
Slot-6                                 Empty          0
Slot-7                                 Empty          0
Slot-8                                 Empty          0

 
Environment
  • Summit
  • EXOS
Procedure
Reason why a node may come up in the failed state or without a role:
  • License mismatch
    • All master-capable nodes in a stack have to have the same license-level (Master capability can be checked using the show stacking configuration command)
  • Version mismatch
    • All nodes in the stack should match both the primary and secondary partition and be running on the same partition.
  • Configuration mismatch
    • Stacking mode mismatch on slots.
    • Stack MAC address mismatch on slots.
    • The selected partition mismatch on slots.

How to confirm:
  • show log​
    • The logs may describe why a node is in the failed state.
  • show slot <failed slot#>
    • This output will provide the current state and typically provide the reason for being in the failed state.

How to resolve:
  • License mismatch
    • Using the telnet slot <slot#> command log into each switch and find out what license is installed on each node. The license will then have to match the rest of the master-capable nodes. If the node is failed because of a license mismatch and there is not an available license to install then you can explore the options presented in this article: Failed Slot - License Mismatch
  • Version mismatch
  • Configuration mismatch
    • If a reason is not present on why the node does not have a role or why it is in the failed state simply try to use the synchronize stacking slot <slot#> command and then reboot the failed slot.
The command "synchronize stacking" synchronizes the following NVRAM-based parameters:
  • Stacking mode.
  • Stack MAC address.
  • Failsafe account and password.
  • Failsafe account access point permissions
  • The selected partition.
Additional notes
If the above resolutions prove unsuccessful please contact GTAC for further troubleshooting.

Please reference the following discussion in the link below:

https://community.extremenetworks.com/extreme/topics/how-to-do-stacking-role-from-none-to-backup

 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255