Removal of a SummitStack member
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-17-2016 01:27 AM
How do you clean up stacking config and port info after a stack member has been removed?
After removing a stack member by logging into the master node - and running "unconfigure stacking" {node address or slot number} then "reboot" {node address or slot number}.
The stack member you chose to remove will reboot and return to factory defaults. However the master node still "thinks" there is a stack member and shows all ports as being present - present and disabled.
The status of the master (in this case originally a 2 stack) when a show "stacking" is run - you see that it has "stacking enabled - master"
After removing a stack member by logging into the master node - and running "unconfigure stacking" {node address or slot number} then "reboot" {node address or slot number}.
The stack member you chose to remove will reboot and return to factory defaults. However the master node still "thinks" there is a stack member and shows all ports as being present - present and disabled.
The status of the master (in this case originally a 2 stack) when a show "stacking" is run - you see that it has "stacking enabled - master"
14 REPLIES 14
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-22-2016 03:05 AM
Hi Peter, I updated the title to reflect this 🙂
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-22-2016 01:35 AM
Port reports from Ridgeline and Netsight still include these ports in results.
None of these ports show up as unused ports in Netsight....but it does display them in port details in capacity manager.
None of these ports show up as unused ports in Netsight....but it does display them in port details in capacity manager.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-22-2016 12:22 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-21-2016 10:57 PM
Slot-1 SWITCHXX.4 # sh stackingStack Topology is a Daisy-Chain
Active Topology is a Daisy-Chain
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:82:40:07 1 Active Master CA-
Active Topology is a Daisy-Chain
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:82:40:07 1 Active Master CA-
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-17-2016 02:43 AM
Hi Peter,
Please confirm below step is performed ?
Disable stacking
If yes share show stacking from master node.
Thanks,
Suresh.B
Please confirm below step is performed ?
Disable stacking
If yes share show stacking from master node.
Thanks,
Suresh.B
