Configuring a Stack

Before configuring a new stack, do the following:

Ensure that every switch, or node, in the stack is running on the same partition (primary or secondary).
Ensure that every switch in the stack is running the same version of ExtremeXOS.
Ensure that every master-capable switch in the stack is running the same version and patch level of ExtremeXOS.
Note
New switches are master-capable by default. To turn off master capability for a switch, use the following command: configure stacking node-address address master-capability off

Follow these steps to configure a new stack. Some of the steps include references where you can find additional information.

Physically connect the switches (stack nodes) using their stacking ports or alternate stacking ports.

Instructions for physically setting up the stack are provided in ExtremeSwitching and Summit Switches: Hardware Installation Guide for Switches Using ExtremeXOS 21.1 or Later.

Note
To complete the cabling, you must first install any option cards you plan to use.
Power on the switches.
For each switch on which the stacking ports are not already enabled, issue the command enable stacking-support.
Then reboot the switch.
Note
On new switches, stacking-support is disabled by default.
Configure all switches in the stack that will use the SummitStack-V, SummitStack-V80, SummitStack-V160, SummitStack-V320, or MPLS (Multiprotocol Label Switching) features.

Note
If the stack will use MPLS, only the following switch types can act as master and backup: Summit X460-G2, X670-G2, and X770; Extreme Switching X690 or X870.
1. Configure switches that will use alternate stacking ports as described in Using Ethernet Ports for Stacking (SummitStack-V Feature).
2. Reboot the switches whose configurations you changed.
Log in, using the console port, to the switch that will be the master.

Issue the command show stacking stack-ports to verify that the stacking ports are set up properly.

If any ports display a state other than Operational, look for the following potential problems. For example, a Link Down state might indicate a connection problem. Check the physical connections for those ports. Also verify that both ports are using the same stacking technology, for example SummitStack-V80.

The following example shows connection problems for the two ports on the switch in slot 2:

* switch1 > > show stacking stack-ports
Stack Topology is a Ring
Slot Port Select Node MAC Address  Port State  Flags Speed
---- ---- ------ ----------------- ----------- ----- -----
*1   1    Native 00:04:96:52:57:ab Operational C-      20G
*1   2    Native 00:04:96:52:57:ab Operational C-      20G
 2   1    Native 00:04:96:7e:00:6e Link Down   C-      20G
 2   2    Native 00:04:96:7e:00:6e No-Neighbor C-      20G
 3   1    Native 00:04:96:51:ea:18 Operational C-      20G
 3   2    Native 00:04:96:51:ea:18 Operational CB      20G
 4   1    Native 00:04:96:36:52:61 Operational CB      20G
 4   2    Native 00:04:96:36:52:61 Operational C-      20G
 5   1    Native 00:04:96:52:57:b8 Operational C-      20G
 5   2    Native 00:04:96:52:57:b8 Operational C-      20G
* - Indicates this node
Flags:  (C) Control path is active, (B) Port is Blocked

If you are using switches that were used previously in other stacks, issue the command show stacking configuration.

All switches must have stacking-support enabled, but stacking disabled, before you run Easy Setup.

Example:

* switch1 > show stacking configuration
Stack MAC in use: <unknown>
Node               Slot         Alternate          Alternate
MAC Address        Cfg Cur Prio Mgmt IP / Mask     Gateway         Flags     Lic
------------------ --- --- ---- ------------------ --------------- --------- ---
*00:04:96:52:57:ab 1   1   5    <none>             <none>          CcEe--iNn --
 00:04:96:7e:00:6e 2   2   1    <none>             <none>          --Ee--iNn --
 00:04:96:51:ea:18 3   3   2    <none>             <none>          --Ee--iNn --
 00:04:96:36:52:61 4   4   3    <none>             <none>          --Ee--iNn --
 00:04:96:52:57:b8 5   5   4    <none>             <none>          CcEe--iNn --
* - Indicates this node
Flags:  (C) master-Capable in use, (c) master-capable is configured,
        (E) Stacking is currently Enabled, (e) Stacking is configured Enabled,
        (M) Stack MAC in use, (m) Stack MACs configured and in use are the same,
        (i) Stack MACs configured and in use are not the same or unknown,
        (N) Enhanced protocol is in use, (n) Enhanced protocol is configured,
        (-) Not in use or not configured
License level restrictions: (C) Core, (A) Advanced edge, or (E) Edge in use,
        (c) Core, (a) Advanced edge, or (e) Edge configured,
        (-) Not in use or not configured

If a switch is enabled for stacking (shown by a capital letter E in the Flags column), issue the command disable stacking node-address mac_address. Then reboot the switch.

If necessary, configure a license level restriction.
See Managing Licenses on a Stack.
From the node that will be the master, issue the command enable stacking.
Enter y if you receive the following prompt:
You have not yet configured all required stacking parameters. Would you like to perform an easy setup for stacking operation? (y/N)

Entering y invokes Easy Setup. All of the switches reboot automatically and form a stack with a master node and a backup node. The rest of the switches in the new stack become standby nodes.

Easy Setup configures all other required stacking parameters for every switch in the stack.

Note
To bypass Easy Setup (not recommended), respond n and follow the steps in Manually Configuring a Stack.
Verify the configuration.
Follow the instructions in Verifying the Configuration.
Save the ExtremeXOS configuration to every active node in the stack.
On the master node, issue the command save configuration config_name, where config_name is a descriptive name for this configuration.

The stacking-specific configuration parameters are saved in a file called config_name.cfg to the NVRAM of each node.