Thank you for asking this question in the support community. I will need some additional information to assist you. When you get a chance, will you please attach both of the configurations? (Please remove any information that might be sensitive to the organization)
1 of 1 people found this helpful
Thank you for replying with the requested information.
In the configuration files you sent, the configuration for “POE2” says it has 13.08.00 firmware. If this is the case, I recommend upgrading the firmware because there have been firmware enhancements since then.
Will you verify how the two switches are connected? Is port gigabit-eth 0/2 of the master connected to gigabit-eth 0/1 of the member? If the connecting ports are not set to stack mode, then the ports will not act like a trunk, nor will they pass stack information. Instead, it will act as an access port for whatever VLAN is set with the switchport trunk native vlan command (VLAN 1 by default), and it will not pass traffic from multiple VLANs.
Switch stacking, or clustering, on AOS products allows you to manage multiple switches from a single IP address (Single IP Management). The AOS implementation of stacking does not currently support configuration management or firmware management for stack members.
AOS Switch Stacking works by using LLDP (Link Layer Discovery Protocol) to allow the switches to communicate and register for stacking capabilities. LLDP is a Layer 2 protocol that acts as a way to pass information on a link between two devices that are directly connected.
To do this, the Stack Master will send out an LLDP packet querying the other switches it is connected to (as long as the ports that connect them have been configured to do stacking).
If a Stack Member has been configured for stacking on that port, it then will send a registration to the Stack Master. After receiving the registration, the Stack Master will acknowledge this, and add the Member as a candidate for stacking.
Once a Stack Member has been recognized as a candidate for stacking, the Stack Master then looks at its configuration to see if this candidate has an ID that would allow it to become a Stack Member. A Member in stacking is identified by the Master based on its MAC address.
After the Stack Master has verified the ID of the Member, the Stack Master then sends an Add packet to the Member. Once received, the Member then ACKs the packet and the Stacking relationship has been created.
A port in switchport mode stack goes through three stages:
Stage 1: (Stays in this stage until a stacking compatible device is determined to be on this link via LLDP)
- Behaves like an access port (only one untagged VLAN being passed) but uses the switchport trunk native vlan as the native VLAN (as opposed to the switchport access vlan).
Stage 2: (Visits this stage after finding a stacking compatible device on the link; establishes a separate VLAN connection between switches to pass additional stacking info outside of LLDP)
- Behaves like Stage 1 but adds a tagged stack VLAN (2386 by default) to talk between switches.
Stage 3: (Moves to this stage once stack master has taken control)
- Acts like a port configured as a trunk (whether it be a static trunk or one controlled by GVRP depends on GVRP setting on port) with added tagged stack VLAN (to maintain regular stacking info exchanges and for remote device configuration).
To further assist you in determining why the stack relationship is failing, will you obtain the output from the following show and debug commands from both switches:
show interface ethernet 0/x (where 'x' represents the stack port connecting switches)
show lldp neighbors
show stack candidates
debug lldp verbose
debug stack verbose
For future reference, please review the Switch Stacking in AoS document.
Thanks for your assistance.
>>In the configuration files you sent, the configuration for “POE2” says it has 13.08.00 firmware. If this is the case, I recommend upgrading the firmware >>because there have been firmware enhancements since then.
The firmware is actually 13.14.00. The configuration dump must not have been saved correctly. The logs attached support this.
>>Will you verify how the two switches are connected? Is port gigabit-eth 0/2 of the master connected to gigabit-eth 0/1 of the member?
The switches are correctly connected physically.
>>To further assist you in determining why the stack relationship is failing, will you obtain the output from the following show and debug commands from both >>switches:
The logs of the requested commands are attached.
Thank you for replying with the requested information. It appears that the stacking keepalives may not be received/transmitted between the stack master/member for some reason. I recommend you open a ticket with ADTRAN support to further troubleshoot stacking.
You can open a ticket in several ways:
- Open a webticket by clicking on this link: Create a Service Request
- Open a ticket by emailing firstname.lastname@example.org
- Open a ticket by phone by calling 1-888-423-8726
I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it and select another in its place with the applicable buttons. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.