Hello ACI people!
I came across a strange issue today.
I have a jumphost living in the fabric. From that jumphost I tried to reach two different hosts in the same subnet, external to the fabric.
I can ping one of them from the jumphost with no issues...
Hello ACI Community!
I encountered an unusual issue recently.
Before making a change to the fabric, I took a snapshot as a precautionary measure. The change itself was quite simple: I removed several unused policies from the interfaces to reduce the ...
Hello ACI Folks,
I am working on a interesting case and I am here to ask for an opinion.
We had a cluster of three APICs, M2s running 5.2(5e).
One of the APICs got replaced for a new APIC L3, unfortunately an engineer did not notice
the SW versio...
I have an issue with ACI Fabric discovery.
Fabric was wiped clean and reconfigured.
After logging into the APIC GUI, I was able to register the first Leaf, but then the Spine has never showed up.
I can see the spine with lldp and when...
I have one switch that is managed by the DNA-C, the switch is reachable, Managed and Compliant.
However, its RUM license report is about to expire and I came across an issue that I can not fix.
The problem is that when I go into Tools...
Alright, issue is now solved!
I had a stale endpoint on the border lea...
My problem has been just resolved,
Just an update if anyone is interested.
As mentioned in the previous post, after the new APIC was connected to the Fabric with mismatching SW version, it was decommissioned and upgraded to the correct SW version of ...
I resolved the problem. Fabric is now fully discovered and registered.
The problem was that the Leaf port connecting to the Spine became a
downlink after I wiped it and rebooted. I was not aware of it at first.
So then I just converted...
I did exactly as you said,
I firstly wiped and reloaded the APIC, logged into the kvm in cimc and when I saw the setup script, that's when I reloaded the switches.
Once again I was able to register the Leaf, but spine is nowhere to be ...