Its strange to see the big difference in the system uptime and the kernel uptime. The ACE had caused a production impact for around 8 minutes and the standby ace didn't took over during that time frame although the FT/query vlan is configured perfectly fine.
Since there was no log generated on the 6500 switch for the module reset, i suspect that the module would have got hung and recovered by itself.
I also dont find any thing strange in the ft history * outputs.
I suspect that this might be a bug since the image is very old (Version A2(1.0))
`show system uptime`
System start time: Tue Jun 12 10:41:12 2012
System uptime: 0 days, 20 hours, 5 minutes, 6 seconds
As you said, probably the device might have started hunging at that moment then that´s why the failover was never fired, it would have been good to force a manual reset of the module.
There are some bugs which show: "last reboot reason: unknown" and they are called: "silent bugs" however the ACE might have had a process which was stuck at that moment. Do you have a high logging level?
Also you can check with: # dir core: to see if the device generated any core dump, here you have the link about it:
Anyway, if the device did not generate any core dump, it will be good if you proceed with a proactive upgrade to the version:a2.3.3 or higher and monitor the behavior, in case you experience the same behavior, please try to collect #show tech-support if it is possible, if not hopefully the ACE will failover to its peer but it does not happen, force the reboot and trigger the failover and avoid further outage, but please be aware that as much information we got it will be better to determine the root cause.
Here you have the link where you can get the software from:
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...