Cisco UCS Manager core is made up of three elements, which are the Data
Management Engine, Application Gateway, and user accessible northbound
interface. The northbound interface comprises of SNMP, Syslog, XML API, and
You can monitor the
Cisco UCS Manager servers through XML API, SNMP, and Syslog. Both SNMP and
Syslog are interfaces used only used for monitoring as they are read-only, so
no configuration changes are allowed from these interfaces. Alternatively, the
XML API is a monitoring interface that is read-write, which allows you to
Cisco UCS Manager, and change the configuration if needed.
Figure 1. Cisco UCS Manager Core and Monitoring Interfaces
The DME is the
center of the
Cisco UCS Manager system, which maintains:
Cisco UCS XML database which houses the inventory database of all physical
elements (blade and rack mount servers, chassis,
modules, and fabric interconnects).
configuration data for profiles, policies, pools, vNIC, and vHBA templates.
networking-related configuration details like VLANs, VSANs, port channels,
network uplinks, and server downlinks.
The DME monitors:
Only the current
information of inventory, health, and configuration data of the managed
endpoints are stored in the
Cisco UCS XML database resulting in near real time. By default the DME does not
store a historical log of faults that have occurred on a
Cisco UCS domain. As fault conditions are raised on the endpoints, the DME
creates faults in the
Cisco UCS XML database. As those faults are mitigated, the DME clears and
removes the faults from the
Cisco UCS XML database.
Gateways are software agents that communicate directly with the endpoints to
relay the health and state of the endpoints to the DME. AG-managed endpoints
include servers, chassis,
modules, fabric extenders, fabric interconnects, and
NX-OS. The AGs actively monitor the server through the IPMI and SEL logs using
the Cisco Integrated Management Controller (CIMC). They provide the DME with
the health, state, configuration, and potential fault conditions of a device.
The AGs manage configuration changes from the current state to the desired
state during FSM transitions when changes are made to the
Cisco UCS XML database.
module AG and chassis AG communicate with the Chassis
Management Controller (CMC) to get information about the health, state,
configuration, and fault conditions observed by the CMC. The fabric
interconnect NX-OS AG communicates directly with NX-OS to get information about
the health, state, configuration, statistics, and fault conditions observed by
NX-OS on the fabric interconnects. All AGs provide the inventory details to the
DME about the endpoints during the various discovery processes. The AGs perform
the state changes necessary to configure an endpoint during FSM-triggered
transitions, monitor the health and state of the endpoints, and notify the DME
of any faults.
interfaces include SNMP, Syslog, CLI, and XML API. The XML API present in the
Apache webserver layer sends login, logout, query, and configuration requests
using HTTP or HTTPS. SNMP and Syslog are both consumers of data from the DME.
SNMP informs and
traps are translated directly from the fault information stored in the
Cisco UCS XML database. SNMP GET requests are sent through the same object
translation engine in reverse, where the DME receives a request from the object
translation engine. The data is translated from the XML database to an SNMP
use the same object translation engine as SNMP, where the source of the data
(faults, events, audit logs) is translated from XML into a
Cisco UCS Manager-formatted Syslog message.