Verify that the ExtremeXOS version running on both stackable switches is version 12.0 or later. Both the nodes must be running the same ExtremeXOS release.
Use the show licenses command to verify that the purchased license levels of the switches that you intend to be master-capable (as potential master or backup nodes) meet your requirements (see Managing Licenses on a Stack).
(Only for nodes on which you have not yet configured the SummitStack feature) If you want to preserve the ExtremeXOS configuration in use on node 1, use the upload configuration [hostname | ipaddress] filename {vr vr-name} command to retrieve the configuration. The file may be used to restore the ExtremeXOS configuration to the stack after the stacking configuration is complete.
Node 1 is the currently deployed node, and node 2 is the new node to be used to form a stack of two nodes.
You can power on node 2 before, during, or after the connection.
You can specify a number for each node manually, or you can use the automatic slot number assignment.
At this time, by default, the user ID is admin and there is no password.
The failsafe account parameter configuration is pushed to the nonvolatile memories of both nodes.
To restore the ExtremeXOS configuration, you must first edit the file created during configuration upload.
All port numbers in the file are simple numeric values. You must replace the port number with slot:port format with slot number set to one (1). Once the file is ready, you can:
Make sure the file has the extension .xsf (rename if necessary).
Use TFTP to get the file onto the master node.
Use the load script filename {arg1} {arg2} ... {arg9} command to run the commands in the file.
Use the save configuration {primary | secondary | existing-config | new-config} command.
If you intend to deploy new units that are not to be stacked, consider whether or not you want to eventually use them in a stack before you deploy them. If so, you should turn on stacking mode during initial deployment. If a new node is subsequently added, there is no need to switch the existing node to stacking mode, and since the existing stacking configuration uses the slot:port numbering format, there is no need to edit the configuration file. The only disadvantages of deployment in stacking mode are the inability to use QoS profile QP7 for your traffic, and the reservation of some of the packet buffer space for stacking control traffic.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB