Was hoping you could help. We have a UCS system running firmware 1.3(1) and are using QLogic CNAs for our HBA & LAN connectivity.
I was wondering if there was a way in the BIOS (or wherever) Policy to enable the HBAs by default as each time we assign a Service Profile they are disabled by default. We have to go into the Adapter BIOS (CRTL-Q) to enable them.
I have looked everywhere but cannot find out where to enable this or where the configuration might be. Would be grateful of any insight, even if only to find out that its not possible or is a feature request in the pipeline?!
If your Service Profile is using local disk for boot and you have defined additional storage using SAN there should be no reason to go into BIOS to enable the FC adapter. That is primarily a precursor to using SAN boot. For SAN boot, you'd see the following: Adapter -Enable, Boot -Enable, Boot Lun Identified. For SAN boot, all of this would be configured by a SAN boot policy.
If you need to access SAN luns with a local disk Service Profile there is no need to enable the adapter. The configuration is handled by the storage policy of the Service Profile. Once the Operating System is installed and HBA drivers installed (if necessary) you will have access to SAN luns.
Going into BIOS is not necessary in this case. Also, as you have discovered making manual changes to BIOS or HBA Option ROM settings will not survive a Service Profile associate/disassociate process. Likewise, moving that Service Profile to another blade (same idea) would not bring along the manual BIOS changes made on the original blade. The purpose of the Service Profile is to completely control the BIOS and Option Rom configurations so it can move to another piece of hardware without additional manual configuration changes.
Although, if you are using local boot, you'd have to move the disks to the new blade
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...