Monday, April 22, 2019

Extreme Switch - Summit Stacking

Extreme Networks provides an excellent visual Stacking tool makes it easier for you to understand EXOS stacking and hardware compatibility. With so many hardware configurations to choose from, it can be challenging to know which ones can work together.

With the EXOS Stacking Tool v2.0, users can:
  • Build a stack by selecting various EXOS models so the tool can verify compatibility
  • See which stacking technologies (VIM and stacking modules) are compatible and recommended
  • See the minimum and maximum EXOS versions supported by the entire stack
  • See the theoretical table size limits for the entire stack based on model selections
  • See the suggested stack master and backup
  • Access product information and knowledge articles linked from within the tool
The stacking tool is available here.

Here's how to get started:
  1. Drag switches from the Switch catalog on the left to the stack on the right (top to bottom)
  2. Select stacking technologies for Stack ports S1 and S2 by clicking on a switch in the stack
  3. Click on the arrow to the right of the stack to expand the Tables and Reporting section

Click on the "Hamburger button" for help at any time. There you'll find:
  1. Getting Started
  2. Things to Know
  3. About section (provide feedback direct to tool developers)

  • Prerequisite

Before connecting the stacking cables to add the switch to stack verify the following is the same:
  • License Level-----------"show licenses"(all master capable nodes should have the same license)
  • EXOS Version----------"show version images" (Ensure that every switch (or node) in the stack is running the same version of ExtremeXOS.)
  • Active Partition---------"show switch" (Primary or Secondary whatever is booted that should be same for all devices in stack)

Enabling stacking will remove the configuration. You will have to migrate the configuration manually.

To configure a new stack:

Step 1. Physically connect the nodes using the stacking ports.

1-1. Insert the VIM modules into the switches. (Power down the switch to install or remove card.)

1-2. Connect the stacking cables as below.
Various QSFP+ optics/cables can be used for stacking ports: 40G MPO cables with QSPF+ SR4 optics, QSFP+ direct-attach cables, etc. The picture shows in V320 stacking. Connect only S1 and S2 in the same way if it's in V160 stacking.
Summit X460-G2 to be added is required to have a VIM-2q option card (2 x 40GbE ports) installed in the back to support SummitStack-V160.

Step 2. Power on the nodes.

Step 3. For each switch on which the stacking ports are not already enabled, issue the command enable stacking-support.

exos_stack1 # show stacking-support

Stack    Available Ports
Port    Native  Alternate  Configured  Current
-----   -----------------  ----------  ----------
1       Yes     51         Native      N/A
2       Yes     52         Native      N/A
stacking-support:          Disabled    Disabled

Flags: * - Current stack port selection

exos_stack1# enable stacking-support

Stack port 1 configuration is Native
Stack port 2 configuration is Native

This setting will take effect at the next reboot of this switch.

Step 4. Make sure all switches have the same stacking protocol and stacking-support configured

configure stacking protocol [enhanced | standard]
configure stacking-support stack-port [stack-ports | all] selection [native {V80 | V160} | V320} | alternate]

e.g. For SummitStack-V160
exos_stack1 # configure stacking-support stack-ports all selection native V160

This setting will take effect at the next reboot of this switch.

Step 5. Login to any of the nodes through the console port, preferably the one you want to use as the master. If you plan to use Easy Setup, log into the intended master node.
If the stack is a new stack, the default parameters are in effect.

Step 6. Type "show stacking" to verify the stack.
The show stacking command displays all nodes in the stack. All nodes are in a disabled state and all nodes appear as master nodes.

exos_stack1 # show stacking
Stack Topology is a Ring
This node is not in an Active Topology
Node MAC Address    Slot  Stack State  Role     Flags
------------------  ----  -----------  -------  ---
*00:04:96:9b:b3:13  -     Disabled     Master   ---
 00:04:96:9e:a7:34  -     Disabled     Master   ---
 00:04:96:9d:05:56  -     Disabled     Master   ---
 00:04:96:9e:a7:78  -     Disabled     Master   ---
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology

Step 7. Type "enable stacking" from the master.

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

exos_stack1 # enable stacking
You have not yet configured all required stacking parameters.
Would you like to perform an easy setup for stacking operation? (y/N) Yes

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) Yes

Stacking configuration is complete.  Rebooting...

(Optional) Step 8. This command presents you the option of using the Easy Setup procedure. Type "configure stacking easy-setup"

(Optional) Step 9. Restart the stack and type "reboot stack-topology"
The configuration is set to default values while entering the stacking mode, so all previously entered configuration information (except for the NVRAM-based stacking parameters, selected image, and failsafe account information) is not available.

Step 10. Login to the intended master node and verify the stack type "show stacking", "show slot", and "show stacking configuration" commands.

Step 11. If the stack configuration is successful:
All nodes are visible in the stack.
All nodes move to the active state.
Some time after the nodes become active, each node is present in the configured slot.
After the roles are finalized, you can see one master node, one backup.

Step 12. Verify that the master node is the one you intended to be the master.

* Reference URL: Getting started with Summit Stacking

* Helpful articles on building a stack:

How to create a stack:
How to replace a node in a stack:
How to troubleshoot a node not receiving a role:
Why do I lose my current configuration when I build a stack:
How to setup up a stack with a X460-G2, X460-G1 and a X440-G1.

Note: there are community created scripts available to help with converting configurations to stacking.
Non-Stacking Configuration Converter

* Helpful articles on configuring a stack:
How to change master capability on a slot in a stack:
How to disable stacking in EXOS:
How to configure alternate stacking:
How to upgrade EXOS on summit stack:

* Helpful articles on troubleshooting stacking:
Failed Slot:
Failed Slot - Firmware Mismatch
Failed Slot - License Mismatch
Failed Slot - Unknown Master
Switch stuck pending AAA but REBOOT AS MASTER-CAPABLE is not working

Conduit receive error in logs:
Switch in Summit Stack Failed with Conduit Receive Error

* Helpful articles on configuring a stack for unique hardware:
Configuring a Summit X670V for native stacking with a VIM4-40G4X module:
Stacking port and up-link behavior while configuring a VIM4G4X in a X670V:
Stacking with X460-G2-10G4:

* Additional KBs:
How to configure sharing (LAG) with LACP in Summit stack or BlackDiamond switches

Thursday, March 28, 2019

Extreme (formerly, Avaya) VSP Switches - How to install a license file

First, you should get a license file (*.xml extension) from the Extreme Customer Support Portal.
Please follow the steps in the link.
The XML file contains the Base MAC address of VSP Chassis as below.

You may double check the Base MAC address by CLI command 'show sys-info.'

vsp-8404c_1:1#show sys-info

General Info :

 SysDescr : VSP-8404C ( 

 SysName : vsp-8404c_1
 SysUpTime    : 0 day(s), 23:38:35
SysContact   :
SysLocation  :

Chassis Info:

Chassis : 8404C ModelName : 8404C

BrandName          : Extreme Networks.
Serial#            : 18JP4930AAAA
H/W Revision       : 12
H/W Config         :
Part Number        : EC84000X2-E6
NumSlots           : 4
NumPorts           : 57
BaseMacAddr        : 64:6a:52:e8:1c:99
MacAddrCapacity    : 1024
MgmtMacAddr        : 64:6a:52:e8:1c:88

Step 1. Copy the license file (i.e. premier.xml) into VSP Chassis via FTP
You may copy the license file via FileZilla (open source FTP software). You can simply drag and drop the xml file into the /intflash directory to the right panel from your system.

or, you may copy from the USB as below.
(config)#copy /usb/premier.xml /intflash/premier.xml
   Make sure you have the xml file in the /intflash.

vsp-8404c_1:1#ls *.xml
Listing Directory /intflash:
-rw-r--r--  1 0       0           1017 Mar 29 03:19  license_premier_646A52E81C99.xml

Step 2. Load the license file
Enter the configuration mode by 'configure terminal' and load the license file by 'load-license' command.

vsp-8404c_1:1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.

* Note:
If more than one valid .xml license file exists in the /intflash/ directory, the switch uses the license with the highest capability. It does not require a reboot. However, please do not use a minus (-) symbol in the filename like license_premier-macsec_646A52E81C99.xml.

Step 2. Verify the license

vsp-8404c_1:1#sho license

License file name : /intflash/license_premier_646A52E81C99.xml

License Type           :    PREMIER (includes Base features)
MD5 of Key             :    00000000 00000000 00000000 00000000
MD5 of File            :    00000000 00000000 00000000 00000000
Generation Time        :    2019/03/28 18:20:45
Expiration Time        :
Base Mac Addr          :    64:6a:52:e8:1c:99
flags                  :    0x00000001 SINGLE
memo                   :

Features requiring a Premier license:
-  Layer 3 VSNs
-  MACsec
-  Distributed Virtual Routing(DvR)
-  >24 VRFs

  • 'save config' or 'write memory' CLI commands will show you the license file.
vsp-8404c_1:1#write memory
CP-1: Save config to file /intflash/config.cfg successful.
CP-1: Save license to file /intflash/license_premier_646A52E81C99.xml successful.

* Reference URL: 
How To Install a VSP License File

Wednesday, March 27, 2019

Extreme (formerly, Avaya) VSP Switches - Software Upgrades

1. (Optional) Backup your existing configuration
Copy the existing configuration file from the VSP to the TFTP or FTP server.

vsp-8404c_1:1#copy config.cfg

2. Download the firmware image that you want to load.
You should be able to download the latest image from the ExtremePortal.

In this example, I downloaded VOSS8K.

3. Upgrade VSP Software Image

Step 0. (Optional) Check the current version

vsp-8404c_1:1#show software


                    software releases in /intflash/release/
VOSS8K. (Primary Release)


Auto Commit     : enabled
Commit Timeout  : 10 minutes

Step 1. Copy the upgrade image to your VSP chassis using FTP (via SSH, TCP/22)
In this example, I have transferred the VOSS image via FileZilla (open source FTP software). You can simply drag and drop the tgz file into the /intflash directory to the right panel from your system. (/Users/username/TFTP/VOSS8K.

You may double check the file via CLI command 'ls' as below.

vsp-8404c_1:1#ls /intflash/VOSS*
Listing Directory /intflash:
-rw-r--r--  1 0       0      218989797 Mar 28 08:05  VOSS8K.

  • Internal flash
The switch has two internal flash memory devices: the boot flash memory and the system flash memory. The system flash memory size is 2 gigabytes (GB).

Boot flash memory is split into two banks that each contain a different copy of the boot image files. Only the Image Management feature can make changes to the boot flash.
The system flash memory stores configuration files, runtime images, the system log, and other files. You can access files on the internal flash through the /intflash/ folder.

Step 2. Unpack the software release
Add the VOSS image to the VSP 4000/8000.

vsp-8404c_1:1#software add VOSS8K.
Extracting distribution information from /intflash/VOSS8K.
Extracting software version VOSS8K. from /intflash/VOSS8K.
Extraction of VOSS8K. to /intflash/release/VOSS8K. successful
Setting permissions on /intflash/release/VOSS8K. successful

Step 3. Copy the software release to boot flash
Copy software version to boot flash

vsp-8404c_4:1#software activate VOSS8K.
Executing software activate for version VOSS8K.
Validating release VOSS8K.
[03/28/19 09:43:24] Sending upgrade message to slots: 1. Version=VOSS8K.

[03/28/19 09:43:25] Slot 1 : IMAGE SYNC: Running pre-install script for image version VOSS8K.
[03/28/19 09:43:25] Slot 1 : IMAGE SYNC: uBoot image is consistent
[03/28/19 09:43:25] Slot 1 : IMAGE SYNC: Kernel image is being updated...
[03/28/19 09:43:29] Slot 1 : IMAGE SYNC: Root_FS image is being updated...
[03/28/19 09:43:55] Slot 1 : IMAGE SYNC: APP_FS image is being updated...
[03/28/19 09:45:08] Slot 1 : IMAGE SYNC: Running post-install script for image version VOSS8K.
[03/28/19 09:45:08] Slot 1 : IMAGE SYNC: Backup image successfully upgraded to VOSS8K.

Primary Version:   VOSS8K.
Backup Version:    VOSS8K.

Changes will take effect on next reboot.

Step 4. Reboot the VSP 4000/8000 to load the new image
Are you sure you want to reset the switch (y/n) ? y

Rebooting takes about five minutes or so.

vsp-8404c_1:1#show software
Command Execution Time: Thu Mar 28 10:00:46 2019 UTC

                    software releases in /intflash/release/
VOSS8K. (Backup Release)
VOSS8K. (Primary Release)

Auto Commit     : enabled
Commit Timeout  : 10 minutes

Remaining time until software auto-commit is 9 minutes 33 seconds

Step 5. Commit the new software image updated after reboot

Make the running software release trusted.
Or it could be auto-committed after 10 minutes by default.

If you do not commit the software and auto-commit is not enabled, your switch restarts with the last known working version after the commit timer has expired. By default, auto-commit is enabled.

vsp-8404c_1:1#software commit
Executing software commit for version VOSS8K.
Software commit successful

Step 6. Check the software version/release

vsp-8404c_1:1#show software
Command Execution Time: Thu Mar 28 10:01:29 2019 UTC

                    software releases in /intflash/release/
VOSS8K. (Backup Release)
VOSS8K. (Primary Release)

Auto Commit     : enabled
Commit Timeout  : 10 minutes

vsp-8404c_1:1#show software detail
Command Execution Time: Thu Mar 28 10:51:10 2019 UTC

                    software releases in /intflash/release/
VOSS8K. (Backup Release)
    UBOOT                            18081615
    KERNEL                           4.9
    ROOTFS                           4.9
    APP_FS                           VOSS8K.
    No Modules Added

VOSS8K. (Primary Release)
    UBOOT                            18081615
    KERNEL                           4.9
    ROOTFS                           4.9
    APP_FS                           VOSS8K.


Auto Commit     : enabled
Commit Timeout  : 10 minutes