02-04-2019 06:17 AM
We have a scenario with 3 switches Nexus 7K, topology attached run OTV between them, topology Multi-Homing. Everything is working.
We need to UPGRADE IOS in the Nexus 7006 that is located in the site-vlan from 7.2 to 8.3 version IOS. After UPGRADE in one switch Nexus, we have a problem with AED vlans extended. All adjacencies UP.
I would like to know if the Nexus needs to be with the same IOS when used in multi-homing or there are any Bugs?
02-06-2019 06:33 AM
Hi Felipe,
Could you share the output to the following commands:
show system reset-reason show logging log | i i otv show logging nvram | i i otv show otv isis adjacency show otv vlan show otv site show span vlan 1 show run vlan 1 show run interface vlan 1 show run otv show interface vlan 1
show ip interface vlan 1
Please type them exactly as shown above. I have a behavior in mind but need to confirm with your configuration.
Thanks!
02-06-2019 06:38 AM
02-06-2019 11:47 AM
02-06-2019 12:56 PM
02-07-2019 02:45 AM
02-07-2019 05:57 AM
02-07-2019 07:42 AM
Felipe,
Thank you. I did not see VLAN 1 as part of your "otv extend-vlan" command under the Overlay so this is not CSCvb28788 which is what I had in mind.
Since you've rolled back, there wont be much in the logs that is meaningful. I did check for OTV defects in 8.3(x) but without further data points, it would be tough to diagnose one.
My recommendation would be to open a TAC case proactively prior to your next upgrade attempt and call in if you run into any issues again so Cisco TAC can troubleshoot live. The following show techs should be collected from the OTV VDC at a minimum as soon as you see the problem (grab them while its broken, makes it easier for TAC to attempt root cause that way):
show tech otv > bootflash:$(SWITCHNAME)-otv.txt show tech details > bootflash:$(SWITCHNAME)-techdet.txt show tech lim > bootflash:$(SWITCHNAME)-ilm.txt show tech oim > bootflash:$(SWITCHNAME)-oim.txt
Hope that helps!
02-08-2019 08:15 AM
Thanks of the support.
02-18-2022 04:35 AM
With this new image try two things
1. Ensure that there is no SVI that is active on the OTV VDC.
2. Try re-applying the OTV overlay config.
This worked for me.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide