This all started when we upgraded the APIC to 3.1 then did a remove/re-register attempt on some spine and leaf switches before upgrading them to 13.1. This lead to the switches coming back online as unsupported. We managed to upgrade them using the oob management, but they still come back as unsupported. I've attempted to do some setup-clean-config.sh to get the switches back to default state. Within the APIC fabric membership section I can see the wiped switches as blank registered switches waiting to be added to the fabric. On the switch itself however, a few minutes after reload the switch seems to revert to it's previous configuration (hostname changes from none to XXX-Leaf101, etc). It seems to be downloading this from the APIC, as I've reloaded the switch once after disconnecting it's connection to the spine and it came up blank and stayed blank, only to suddenly rename itself once the spine connection was restored. Any ideas?
No comments:
Post a Comment