I am facing a issue in using virtual connect (VC) with HSRP.
The setup is as below.
| (Link 1) | (Link2
VC1 ----------- VC2
| ----- Blade1 ------|
Router1 is running HSRP with Router2, Link1 is connected from Router1 to VC1 and Link2 is connected from Router2 to VC2. Both the VCs are in the same enclosure and are connected via a internal chasis backplane. Currently, the link on the VC1 is showing active and the link on VC2 is showing standby. This is causing a problem as Router2 is not able to receive hello packets from Router1 which results in the HSRP not working properly.
Does anyone have similar setup, and is there any workaround to let Link2 become active so that Router2 can receive the hello packet from Router1 which will allow the HSRP to work properly?
There is a link between router1 and router2, its is a HP enclosure. The default gateway is to the router HSRP VIP with no Physical switch in between, we are using Virtual connects to act as a switch between the blades and the router.
Please take a look at this document. There is no connectivity between VC-0 and VC-1, so I don't think the HSRP hello can go between theses two VCs unless you have another switch in between the routers and the VCs.
Virtual Connect is not a switch. It will NEVER pass packets from one uplink to the other.
Virtual Connect does not run spanning tree, and therefore it is not allowed to pass packets from one uplink to the other as this would require STP for loop prevention.
If you have dual L2 switches upstream, you have to interconnect them directly between each other. HSRP will run on this interconnect link.
You will have to trust HP NOT to pass any packets between the active and the standby uplink
TIP: run STP on the links towards the HP chassis and put BPDUguard on it. If there is ever a bridging loop within the HP chassis (ie. a server guy configures MS bridging between the two server NICs !), BPDUguard will block both uplinks and isolate the HP chassis. At least the rest of your datacenter will continue to run
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...