The end user should provide the management IP or the Cluster IP address in order to discover the Cisco UCS. However, this does not pose as a limitation as the user can discover the Cisco UCS equipment by using either the Management IP (Cluster IP) or any of the Fabric Interconnect IP address.

Note:

It is suggested to discover the Cisco UCS by using the Management IP or Cluster IP address.

The Cisco UCS can be discovered and managed by the end user. IP Availability Manager supports the discovery and monitoring of more than one Cisco UCS device.

Every Cisco UCS entity has the Cisco UCS 5100 series chassis which contains various physical components such as Power supply, Fan blade server and so on. These chassis are managed by the UCS Manager. When end user discovers the Cisco UCS entity, then IP is able to discover all the physical chassis that are present on the Cisco UCS entity.

IP Availability Manager discovers and monitors:

  • Cards (Fabric Extender) present on the BladeEnclosureManager (Cisco UCS Chassis). “Attribute of cards (Fabric Extender)” table in Chapter 1, Network Objects, in the VMware Smart Assurance IP Manager Reference Guide lists the attributes of card (Fabric Extender).

  • Fabric Ports on Cards (Fabric Extender) of the BladeEnclosureManager (Chassis). “Attributes and MIB Object IDs of Fabric port” table in Chapter 1, Network Objects, in the VMware Smart Assurance IP Manager Reference Guide lists the attributes and MIB Object IDs of Fabric port.

  • Cards on the Fabric Interconnect switch.

  • Ethernet Ports on Cards of the Fabric Interconnect switch.

  • Trunk Cable Connection between the Fabric Interconnect switch and the BladeEnclosureManager.

  • Host (Blade Server) on the BladeEnclosureManager.

    Note:

    ESX servers hosted by the blade servers are not discovered automatically.