i did spot the Virtual mac address: 0:1:64:f9:1a: available on both switch!!
plus LRP Errors:
Ver mismatch 0 Active State Collision 0 Standby state collision 0
TX errors 0 xsum err 0 HB miss (0)
kinda curious, would it anything on the network design?
my topology is using 2 of 6500 with CSM, configuring in single subnet mode.
Server's NIC doing in Switch Fault Tolerance + Adapter Load Balancing mode, where physically connected to both switch GigabitEthernet port.
On the configuration, there's 2 vlan client (SF and DMZ) bridging to the CSM vlan server. On both switch, i did trunking allow vlan SF and DMZ among them.
(So, i did try to trunk and allow the vlan server i create in CSM across the both switch, but this will causing bridge loop, even i try to encounter using rapid-pvst and assign one of the switch become root primary, still having bridge loop...)
For uplink, these 2 switch trunking allowed vlan carry to the core switch, and core switch connect to firewall.
The NAT for SF (server farm) is done inside firewall, and also the gateway for vlan SF and DMZ point to Firewall. (hmm, something like threshold for internal goto external)
hmm, just wondering, i thought the CSM should running in Active-Active mode. What's the impact having this Active-Active mode?
(if there's nothing can turn-around on this Active-Active, is there any active-standby mode i can refer with?)
Really really appreciate your feedback all this times..
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...