MDS Call Home enhancement for ASIC Error on X-bar Interface
i am sad about the answer from Cisco (see below)
Unfortunately, it’s not possible yet, on any NX-OS version.
Reason being is that the X-Bar actually never goes into a failed state. The CS folks already are in the process of putting in an enhancement request specifically asking that ASIC errors on Fab modules set the state to failed and trigger an event. They have seen this several times on various code versions, and brought it up again last month in the quarterly service review with Cisco.
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...