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). To find this information for any node, issue the command show switch and look for the Image Booted field in the output.
Ensure that every switch in the stack is running the same version and patch level of ExtremeXOS. To find this information for any node, issue the command show switch and look for the Primary Ver or Secondary Ver field in the output.
If necessary, enable switch license levels or configure license level restrictions for the nodes in the stack.
- To understand how licensing works in stacked switches, see Managing Licenses on a Stack.
- To enable a license on a node, see Software Upgrade and Boot Options.
- To restrict the license level for one or more nodes in a stack, see Restricting a Switch License Level.
We recommend that you save the configuration for each switch that will participate in the stack, so that you can reinstate the configuration after the switch is no longer needed in the stack.

Note

New switches are primary-capable by default.

Because stacks can consist of switches of different series and different models, ExtremeXOS does not restrict configuration settings based on the capabilities of any particular node in the stack. Therefore, you are responsible for ensuring that your configuration settings are appropriate for all switches in the stack.

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 the hardware installation guide for your switch.

Note
If your stack includes X460-G2 switches, you must first install the versatile interface modules (VIMs) that you plan to use.
Power on the switches.
On each switch, issue the command enable stacking-support.
This command configures the switch so that it is capable of being added to a stack. It is not the same as enable stacking, which you will use later to build the stack.
Note
You do not need to enable stacking support on the ExtremeSwitching X450-G2 and X465 series switches, since these switches have dedicated stacking ports that are always enabled.
Ensure that all of the cabled stacking ports are enabled for stacking:
1. On each node, issue the command show ports x,y, where x and y are the port numbers.
  In the output, port state = E means a port is enabled.
2. For any ports that are not enabled, issue the command enable ports x,y, where x and y are the port numbers.
3. If you enabled ports on any switches, reboot those switches.
  Save the configuration files.
Configure all switches in the stack that will use the SummitStack-V, SummitStack-V160, SummitStack-V320, SummitStack-V400, or MPLS features.

Note
If the stack will use MPLS, only the following switch types can act as primary and backup: Extreme Switching X460-G2; X465, or X695.
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 primary.

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

All of the ports should show a state of Operational.

In the following example, two of the ports are not in an Operational state, which means they are not connected properly.

* switch1 # show stacking stack-ports
Stack Topology is a Ring
Slot Port Select Node MAC Address  Port State  Flags Speed
---- ---- ------ ----------------- ----------- ----- -----
*-   1    27     00:04:96:9c:e4:39 Operational C-      10G
*-   2    28     00:04:96:9c:e4:39 Operational CB      10G
 -   1    27     00:04:96:9b:c1:34 Operational CB      10G
 -   2    28     00:04:96:9b:c1:34 Operational C-      10G
 -   1    15     00:04:96:9e:5c:76 Link Down   C-      10G
 -   2    16     00:04:96:9e:5c:76 No-Neighbor C-      10G
 -   1    15     00:04:96:9c:53:b6 Operational C-      10G
 -   2    16     00:04:96:9c:53:b6 Operational C-      10G
* - Indicates this node
Flags:  (C) Control path is active, (B) Port is Blocked

When a port displays a state other than Operational, use the following tips to troubleshoot:

If the state displays as Link Down, check the port's physical connections.
Verify that the port is using the same stacking technology, for example SummitStack-V160, as the rest of the ports in the stack.

Verify that all nodes in the stack have stacking disabled.

Note that, even though you enabled stacking-support in step 3, it is necessary that stacking be disabled before the stack is actually built.

Issue the command show stacking configuration.

For example:

* switch1 # show stacking configuration
Stack MAC in use: <none>
Node               Slot         Alternate          Alternate
MAC Address        Cfg Cur Prio Mgmt IP / Mask     Gateway         Flags     Lic
------------------ --- --- ---- ------------------ --------------- --------- ---
*00:04:96:9c:e4:39 1   -   Auto <none>             <none>          -c-----Nn --
 00:04:96:9b:c1:34 1   -   Auto <none>             <none>          -c-----Nn --
 00:04:96:9e:5c:76 1   -   Auto <none>             <none>          -c-----Nn --
 00:04:96:9c:53:b6 1   -   Auto <none>             <none>          -c-----Nn --
* - 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 node is enabled for stacking (shown by a capital letter E in the Flags column), issue the command disable stacking node-address mac_address for that node.
Then reboot the switch.

From the node that will be the primary, issue the command enable stacking.

The following prompt displays:

X440G2-24t-10G4.4 # enable stacking
You have not yet configured all required stacking parameters.
Would you like to perform an easy setup for stacking operation? (y/N)

Enter y to proceed with Easy Setup (strongly recommended), or enter n to configure the stack manually.
- When you enter y for Easy Setup, you are prompted to confirm your choice:
```
Executing "configure stacking easy-setup" command...
For every node in the 4-node stack, this command will:
- enable stacking
- configure a stack MAC address
- choose and configure a slot number (this node will be assigned to slot 1)
- configure redundancy to minimal (slot 1 will be the master node)
- configure the stacking protocol to enhanced
Upon completion, the stack will automatically be rebooted into the new configuration.
Warning: If stacking is already configured, this command will alter that configuration.
Do you wish to proceed? (y/N)	
```
  Enter y again to confirm. All of the switches reboot automatically and form a stack in which one switch is the primary, one is the backup, and the rest are standby nodes. Easy Setup configures all other required stacking parameters for every switch in the stack.
- If you forgo Easy Setup by entering n in response to the prompt (not recommended), you will need to configure the stack manually. Instead of continuing with step 11, follow the steps in Manually Configuring a Stack.
Verify the configuration, following the instructions in Verifying the Configuration.
Save the ExtremeXOS configuration to every active node in the stack.
On the primary 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.

The stack is ready to use.