Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

How to permanently remove SecureStack switch and configuration from an existing stack

« Go Back

Information

 
TitleHow to permanently remove SecureStack switch and configuration from an existing stack
Objective
  • How to permanently remove SecureStack switch and configuration from an existing stack
  • This procedure is intended if you are permanently removing a switch to relocate it elsewhere on your network
Environment
  • SecureStack
  • All firmware versions
Procedure
1. Create a configuration backup and copy the backup off the switch via TFTP:
show config outfile configs/filename.cfg
copy configs/filename.cfg tftp://<TFTP_IP_ADDRESS>/filename.cfg

2. If there are more than two units in the stack, a closed loop stacking connection (stack cable from top unit to bottom unit for redundancy) may be necessary to ensure switches above and below the switch being removed can still communicate with each other

3. Disconnect power cable from the unit to be removed from the stack, then disconnect the stack cables (Note: If the manager unit is being removed, a disruption to the other stack members will occur until new manager is chosen)

4. To clear the configuration from the stack for the disconnected switch, issue the command:
clear switch member <MEMBER_NUMBER>

5. Reconnect the running units back together in the same matter with the stack cables (up to down, or down to up ports)

6.  To renumber the existing units in the stack, save the config first and push it back down to the switch after the remaining units have been renumbered (process described below). For example, if you remove unit #3 in a 5-high stack, you will be left with a stack with units numbers 1,2,4,5. To renumber the units, issue:
set switch 4 renumber 3
set switch 5 renumber 4

 
NOTE:  Renumbering a switch DOES NOT carry over the configuration to the new switch.

Either manually re-configure the switch ports or modify the current configuration in a text-pad editor and push it back to the stack with the below procedure
1.  Make a new copy of the configuration and copy it off the stack:
show config outfile configs/newfilename.cfg
copy configs/newfilename.cfg tftp://<TFTP_IP_ADDRESS>/newfilename.cfg

2.  Open the configuration with a text-editor and change the switch member numbers
From:
set switch member 1 7
set switch member 2 7
set switch member 4 7
set switch member 5 7
To:
set switch member 1 7
set switch member 2 7
set switch member 3 7
set switch member 4 7
(Note: Only change the 1st number which is the switch member, the 2nd number is the switch index type and should stay the same for each line)

3.  Review the remaining configuration for any port specific configuration that will need to be modified (before > after): 
Before: set port vlan ge.4.1 10
After:  set port vlan ge.3.1 10

Before: set vlan egress 20 ge.4.1 tagged
After:  set vlan egress 20 ge.3.1 tagged
 
This could include a number of different items, most common being Port configuration, Policy, Authentication, etc. 
A thorough review of the original config will help ensure nothing is missed

4.  Save the text file and copy it back to the switch, and reload it as the new switch configuration:
copy tftp://<TFTP_IP_ADDRESS>/newfilename.cfg configs/newfilename2.cfg
configure configs/newfilename2.cfg
The configure command will prompt for a reboot and will load the new configuration on the switch stack
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255