Replacing a Node with the Same Switch Type
When you replace a node with the same switch
type, for example when you replace an X460-G2-48t-10GE4 switch with another X460-G2-48t-10GE4
switch, you can continue to use the same stack configuration.
If you are
replacing a node with a different switch type, you must change the stack configuration
before the new node can operate. Follow the procedure in Replacing a Node with a Different Switch Type.
Note
If the stack uses
MPLS (Multiprotocol Label Switching), only the following switch
types can act as master and backup: Summit X460-G2, X670-G2, and X770; Extreme Switching
X690 or X870.
To replace a node with an identical switch type,
follow these steps:
-
Use the show switch, show licenses, and show stacking configuration commands to display
configuration information for the node that is being replaced.
Note the following atributes of the node you are
replacing:
- ExtremeXOS software version
- Partition on which the switch is booted
- Effective license level for the stack
- Slot number
- Master-capable feature configuration
- Node priority
- Alternate gateway IP address
-
Remove the stacking cables from the node that is being
replaced.
-
Replace the node with another switch of the same
type.
-
Before connecting the new (replacement) switch to the
stack, prepare the switch as follows:
-
Review the attributes needed for the node you are
installing, as listed in step 1.
-
With the power off, install any required option cards
as described in ExtremeSwitching and Summit Switches: Hardware Installation Guide for
Switches Using ExtremeXOS 21.1 or Later.
-
Power on the new node.
-
Use the show
switch command to verify that the new node's software is compatible with the
stack:
- The new node, must run the same ExtremeXOS version as the stack. Install the
correct version if necessary.
- The ExtremeXOS software must be booted on the same image (primary or secondary)
as the stack. If the new node is booted on a different image, change the image
before you continue.
-
Use the enable
stacking command to enable stacking. Then decline the Easy Setup
option.
-
Configure the slot number for the new node using the
slot number noted in step 1. For more information, see Configuring Slot Numbers.
-
Configure the node's master-capability to correspond
to the role it should have in the stack (see Configuring Master-Capability).
-
If the new node will operate as a master-capable node,
use the show licenses command to verify
that the enabled license level is at the same level as the master-capable nodes in the
stack.
If necessary, configure the license-level
restriction of the new node to be same as the other master-capable nodes in the stack
(see
Managing Licenses on a Stack).
-
Configure the node role priority to correspond to the
priority it should have in the stack (see Configuring the Master, Backup, and Standby Roles).
-
Configure an alternate IP address and gateway (see
Configuring an Alternate IP Address and Gateway).
-
If the new node will use the SummitStack-V feature,
configure the alternate stacking ports as described in Using Ethernet Ports for Stacking (SummitStack-V Feature).
-
Connect the stacking cables and reboot the node. The new
node will join the stack topology.
-
At the stack master node, enter synchronize stacking.
Note
If the master node was replaced, log into another
stack node before entering this command.
-
Reboot the new node by entering the command: reboot slot [slot-number | node-address
node-address].
Note
If the master node was replaced, reboot the stack
by entering the reboot command at the master node.
-
Run the show
stacking configuration command and verify that the configuration is what you
want.
Note
To verify that the new node became operational,
enter the
show slot {slot {detail} | detail }
command. If the slot shows a Mismatch state, the node was replaced with a different type
of switch (see
Replacing a Node with a Different Switch Type).
Print
this page
Email this topic
Feedback
View PDF
Download EPUB