UCSM unable to monitor storage on blade after Firmware update
I'm getting the following fault on two of my B200-M3 blades after doing a firmware infrastructure autoinstall from 2.2(1d) to 2.2(3b). Firmware update was successful on everything, so I'm not sure why something happened to the blades.
The UCSM is claiming it can't talk to the SAS card, however the card is indeed working fine, blade boots up and works no problem. Any ideas? It seems it just can't monitor the disks for some reason, and I don't get why it's only on two of the blades...
code="F1004" created="2014-10-12T19:14:14" descr="Controller 1 on server 1/6 is inoperable. Reason: CIMC did not detect storage controller" dn="sys/chassis-1/blade-6/board/storage-SAS-1/fault-F1004" highestSeverity="critical" id="1335505" lastTransition="2014-10-12T19:14:14" lc="" occur="1" origSeverity="critical" prevSeverity="critical"
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...