Reconfigure IPs on VPC Peer-KeepAlive Link (mgmt0) for Nexus 5Ks
I would like to ask if there is a best practice of reconfiguring VPCs on a Nexus 5K Switch
Our team has taken infrastructure that is using Nexus 5Ks - 2K FEXs and we need to basically re-address the network including the management IPs of all switches.
I understand that as per best practice, the VPC Peer-Keepalive link should use the management address and that we need to change.
Currently no etherchannels are using VPC.
I tried changing the IP of mgmt0 of the secondary earlier and when I did that, I lost connectivity to the primary switch on the console. When I console to the primary switch so I can do the change, the prompt shows that it is the secondary switch which somehow suggests that the primary emulates the console of the secondary for some reasons.
Is there any other way to go around this? I'm thinking of removing the VPC domain configs, putting it back in once I set the IPs that we want. I'm not sure if there is any other way to do it.
I had been looking on Cisco documentations but could not find any suggestions.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...