I wasn't quite sure where to start that topic, but decided to drop it here as I found this specific related to Nexus 7000.
Right, so the scenario is as follow:
| \ / |
| / \ |
| / \ |
These links are all physical, doubled, port-channel links, terminated on M2XL module.
Native vlan I've been using in Core is 3967, and it does traverse tagged (vlan dot1Q tag native in global config).
For some reason, I am unable to get two cdp neighborship between N7K-1-1 and N7K1-2 (which are both on same physical chassis but in different vDCs). Everything else works just fine (L2/L3). I have L3 OSPF adjacency working just fine there.
N7K1-1 can see N7K2-1 & 2 with absolutely the same configuration. The configuration I've got is as follow:
Now, the interesting part, absolutely the same configuration, applied on links to N7K1-1/1-2 - works just fine. CDP traverses and everything is good..I found, empirically, that if I add vlan 1 to the trunk - CDP pops-up...
What do I miss...?
Here are some more additional snippets, which might help:
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...