I had a switch die the other day. I have redundant CSS11503's.
When the switch died, the CSS took out a couple of VIPS from the active state and moved them to suspended state. When the switch came back online, the CSS never returned the VIPs to an active state, they stayed suspended.
I am wondering what I need to look at to make sure everything comes back to active after a failure and recovery. My typical service configuration is below:
service apache2-e1 port 80 protocol tcp string uprweb002-e1 ip address 172.30.193.22 keepalive uri "/index.html" keepalive type http redundant-index 4 keepalive frequency 20 keepalive maxfailure 10 keepalive retryperiod 2 active
and my typical content rule is as follows:
content ssl-rule protocol tcp port 443 application ssl add service ssl_front_end vip address 172.30.194.193 active
Any thoughts from anyone about why it would have stayed suspended. The complicating thing was that when I did a show arp on my 3750 switch, it showed the IP for the VIP being on the port to the CSS that had the VIP in the suspended state....this meant that when everything SHOULD have been up, the traffic for the VIP was going up to link to the WRONG CSS. It should have been going to the OTHER CSS but because the ARP was showing one thing, it wasnt.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...