cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
462
Views
0
Helpful
7
Replies

Converting HSRP to Stackwise virtual on 9400

sakshi-singh22
Level 1
Level 1

I have a 2 9400 catalyst switches running HSRP and want to convert it to stackwise virtual. 

When I am trying to do so, the switch 2 interfaces configurations are getting removed after coming up in stackwise. 

steps followed: 

-Removed HSRP config 

- now, both the switched are standalone, added the stackwise virtual config. Reloaded the switches. 

- After reloading, the switch 1 comes up fine but the switch 2 interfaces configurations are removed. 

Is it an accepted behavior or is there any other way to do it. Any suggestions are appreciated. 

Little Correction to above: 

We are not getting any switch interfaces configurations on both the switches. So, when the switches come up in stackwise, entire switch 1 and 2 interface configuration wipes out. Meaning nothing shows when I tried to check on any interface configs.

7 Replies 7

Hello @sakshi-singh22 ,

I'm not sure I understand correctly your issue, but after configuring StackWise, the configuration of the second switch is merged into that of the first switch. The interfaces on the second switch are renumbered with 2/x/y and you see one single configuration from the switch that is active. If you try accessing the console on the second switch, it will tell you thet it's disabled.

Can you share some configs of the issue you are experiencing in order to better understand it?

Regards, LG
*** Please Rate All Helpful Responses ***

Little Correction to previous post: 

We are not getting any switch interfaces configurations on both the switches. So, when the switches come up in stackwise, entire switch 1 and 2 interface configuration wipes out. Meaning nothing shows when I tried to check on any interface configs.

 

Can you share the output of the following commands:

show stackwise-virtual link

show stackwise-virtual neighbors

show stackwise-virtual bandwidth

Please refer to the following guide on configuring Stackwise virtual: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/17-9/configuration_guide/ha/b_179_ha_9400_cg/configuring_cisco_stackwise_virtual.html

Regards, LG
*** Please Rate All Helpful Responses ***

sowlee1919
Level 1
Level 1

we have a HSRP setup we are planning to change to stack wise virtual. While doing this we still want to maintain  connections so we will keep let's say in 2 switches we will keep switch 2 to connect to access switches to maintain connection. We want to isolate switch 1 to build stack wise virtual. In the process of configuring this switch to stack wise virtual we shut down all interfaces configuration but after the reload it did not keep this old interface config it completely wiped it. What are the ways to keep these old configurations before building the stack wise.

  1. So what we want to do here is "keep the old configuration on the switch 1 ( we are going to isolate this switch and keep switch 2 active to maintain production) and ensure its retained after building stack wise virtual and reload" 

Leo Laohoo
Hall of Fame
Hall of Fame

@sakshi-singh22 wrote:

- now, both the switched are standalone, added the stackwise virtual config. Reloaded the switches. 


1.  Delete the config off Switch 2. 

2.  Completely power down Switch 2 until VSS configuration on Switch 1 is complete. 

3.  Hook up the inter-connection links (for heartbeat).

4.  Power up Switch 2 and apply the VSS config.  Reboot

POST:  

1.  Monitor the control-plane memory utilization of the VSS daily.  If the control-plane memory utilization goes >55%, get ready to intervene.  

2.  Reboot the VSS once every 8 to 12 months.

sakshi-singh22
Level 1
Level 1

I want to confirm if this is the expected behavior: When we add pre-configured switches (meaning all the configurations are already set up before adding the Stackwise configurations) to a Stackwise Virtual setup, the interface configurations are lost.
Is there any white paper stating this? 

Raise a TAC Case or talk to the Cisco Account Manager if they know of someone who has done this before/recently.