BTW - if your affected blades have "Board Controllers", ensure these have been upgrade to 2.0(1t) also. If you miss these this will generate a disk fault. Double check that all blade components (adaptors, BIOS, CIMC, board controllers) have be upgraded to 2.0(1t) firmware.
Thanks for taking the time to respond. I was in a bit of hurry last week and I didn't put as much detail as I usually would do. I am not on that site at the current time but I do have the TS bundles with me, so if you could possibly point me to the right file or location I can get the exact error message out.
The blades are B200 M2, half width. All blades were affected and they have the ~75Gb SAS disks in them running on the LSI controller.
I had created a Host Firmware package for the service profile and it was only when I applied this (using version 2.0(1t)) that I first saw the errors appear. When they were running the 2.0(1q) release this was not an issue and there was a copy of Windows installed on one of the blades.
I then created HFW packages going back to 2.0(1q) and 1.4(3s), after applying these the error was resolved (I wanted to try both for completeness). The issue does appear to be with the board/bios firmware as I didn't need to completely revert all of the UCS environment to clear the errors.
Like I said I can get the error exactly from the TS bundle if I get a little guidance as to where to find it, however, until then from memory the error was something along the lines of "Blade X disk x/y inoperable", this was showing as a major fault in UCSM and also produced an amber light on the physical disks. Changing RAID layout or swapping disks across blades made no improvement, also decomissioning and scrub of the disks made no improvement.
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...