I recently discovered my company has a single cisco 3550 switch which apparently does the VLAN routing. I need to move that switch without interrupting the flow of traffic. I have two possible solutions and wanted to check with the experts before deciding. I was simply going to power down the switch and move it. But I am afraid it might not come back up (and we have no spare). Also, if possible, I'd like to have as little (or none) downtime as possible.
Solution 1 is to purchase another 3550 and configure it identically to the current 3550 and swap the cable connecting it to the other switches.
Solution 2 is to take the spare 2960, upgrade the software to 12.22_55 and attempt to get vlan routing running on it.
Solution 1 gives us the benefit of having 2 switches where we currently only have 1.
Solution 2 removes the single 3550 switch (all other switches are 2960's).
My question is, can I have 2 switches performing vlan routing at the same time? That would make the transition easier.
My 2nd question is, how long would this switch take to boot back up, assuming it came back up?
It is very important you have a device backup. Vlan routing needs a router L3 or Sw L3 like your 3550. It would be interesting you purchase a router L3 (e.g. 1800, 1900, depending on your infra) and two switches 2960 depending on the number of workstation, printers, etc.
Question 1 - You need a router to do Vlan routing.
Question 2 - It depends how much config you have on it, but it is around 5 minutes.
1. Can I have 2 switches performing vlan routing at the same time? That would make the transition easier. -Technically, yes by using HSRP or VRRP AND if you distribute whoever is the active L3 HSRP/VRRP interface, e.g., if you have 20 L3 VLANs, 10 will be handled by SW1 and 10 will be handled by SW2
But configuring it in your network will still require downtime since current the gateway IP of your network is in your existing L3 switch device
To give you an analogy: Current SW: 192.168.10.1 -Gateway of current network
If you want to implement HSRP or VRRP, you need to change that Current SW: 192.168.10.2 New Switch: 192.168.10.3 Virtual IP: 184.108.40.206 -Gateway IP
Transistioning into HSRP/VRRP will cause downtime since you need to 'transfer' the IP as the Virtual IP
BUT the good thing about this is, the transition can be done per L3 VLAN, hence the L3 that you are current configuring will be the only one to go down, but still it will take time to configure
PS: Check if your switch license supports HSRP
2. My 2nd question is, how long would this switch take to boot back up, assuming it came back up? -Dude, you have the a spare switch in your hand w/c is the same model, use that to check the boot-up time. Though, probably 5 minutes. BUT allocate a longer downtime/maintenance window of course, at least 1 hour, just in case
Hi Milos, you are right, VRRP can use the physical interface IP, but if we do that, the current switch will still be the master since making the VIP=interface IP will make whoever the owner of the interface IP to always be the master, note we want to share the load of the L3 details e..g, ARP
Add to that the requirement that is must always be the master when its active, and preempt enabled, soo we are not quite flexible on how we want our switches to behave.
But yeah, if he wants minimal downtime, you can do that OP ^_^ It's all up to you OP, but again, check your license :P
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...