I need to change the ID for a vlan and would like to minimize the outage for migrating the hosts. Our environment are Nexus cores using a VPCs to 5ks. The SVI for the vlan resides on the Nexus cores and only L2 on the Nexus 5ks. For example I have vlan100 with an SVI of 10.1.1.0/24 on the cores and it is trunked down to the Nexus 5ks using a vPC. I need to keep the same IP scheme but change the vlan ID to 300. I am trying to do this with very little down time.
I am thinking I could create the new vlan300 as an L2 only on the cores and trunk it down to the 5ks. On nexus core 1, connect a cable from a port that is in vlan100 to vlan300 with the ports being configured as access ports. Essentially I am creating a path for vlan300 to communicate with vlan100. Would this solution work? Of course this would be only temporary to migrate the hosts over the new vlan and then I would move the SVI address to the new vlan300.
I haven't used Nexus switches but I am struggling to see what you gain from your solution.
I know with vPCs Nexus handles STP differently but with other switches I have used joining two vlans together in the core of the network is not something I would really consider, or at least not for this.
The IPs are staying the same. So the main issue is when you shut the existing SVI and bring up the new one it could have a different virtual mac address which means all the servers mac to IP mapping for the default gateway would need clearing.
I just checked the N7K configuration guide and if you use the same HSRP group it should generate the same virtual mac. And if you don't you can actually configure your own virtual mac.
So that just leaves migrating the hosts and the Nexus switches support ranges of interfaces.
So I would just have the SVIs ready, then simply move all servers at once into the new vlan, shutdown the old SVI and bring up the new one.
There will obviously be an outage but there would anyway when you switch SVIs.
Like I say I haven't used Nexus so perhaps there is something I am overlooking but I cannot see what benefit you get and creating that link could potentially have a far bigger impact on your environment.
Listen: https://smarturl.it/CCRS8E37Follow us: twitter.com/ciscochampionSometimes, situations require temporary fixes. Sometimes, the network becomes an afterthought in overall office design and planning. In either situation, it may require netw...
In this special edition of the Insider Series, we hear from Cisco partners who have taken steps to be more eco-friendly and sustainable. We hear what inspires ASHRAE, Southwire, Igor, and NTT to create a workplace that is centered around people and how th...
We know that the Type-1 LSA describes the link type connected to the router, the neighbor router and the subnet number.In this topology, assume we dont have a Type-2 LSA, so each router will create its own Type-1 LSA, the Type-1 LSA will describe the neig...
Here are some commonly asked questions and answers to help with your adoption of Cisco DNA Center Wireless. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Q. I have a Cisco Appl...
Why IETF changed and inverted OSPF Type-7 LSA VS Type-5 LSA election In RFC 3101 compared to OLD RFC 1587?Many people learns that the Type-7 LSA and Type-5 election (ON Versus OE routes) depends on RFC 3101 for NSSA published in 2003 and RFC 1587 for NSSA...