UCS Manager monitors all of the elements (servers, CPU's, DIMM's, IO Modules, Chassis's, Fabric Interconnects, etc) for both the health and configuration of the hardware. It federates all of the state, inventory, faults, and configuration into UCS Manager. UCS manager's scope of control and monitoring includes all the aforementioned hardware, but does not include the Host OS or hypervisor / apps running on it. When sending out SNMP traps, UCS Manager just converts the fault conditions it stores in the XML Database (the faults you see in the UCS Manager GUI) into a SNMP trap and sends the fault condition on behalf of the failed component (server, CPU's, DIMM's, IO Modules, Chassis's, etc). UCS Manager utilizes either of the SNMP daemons running on the fabric interconnects to send the details. That is why the IP you get in your NMS system is either of the fabric interconnect IP's, and not the HOST IP, as UCSM doesn't have details about the host running on the system. I would recommend you look at the UCS Manager MIB Reference Guide for more details:
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...