It maintains the current health and state of all components of all physical and logical elements in a UCS Domain, and maintains the transition information of all Finite State Machine (FSM) tasks occurring. It is the maintainer of the UCS XML database which houses the inventory database of all physical elements (blade / rack mount servers, chassis, IO modules, fabric interconnects, etc.), the logical configuration data for profiles, policies, pools, vNIC / vHBA templates, and the various networking related configuration details (VLANs, VSANs, port channels, network uplinks, server downlinks, etc). Alternatively, the UCS XML API is a monitoring that is “ read-write” in nature, which does allow an end user to both monitor UCS, as well as change the configuration if needed.ĭata Management Engine (DME) – The DME is the center of the UCS Manager universe, or the “queen bee” of the entire system. Both SNMP and Syslog are interfaces only used for monitoring as they are “ read-only” in nature, not allowing an end user to change the configuration. With UCS Manager there are three main ways of monitoring UCS servers, which are XML API, SNMP, and syslog. The core of UCS Manager is made up three core elements, which are the Data Management Engine (DME), Application Gateway (AG), and user accessible northbound interface (SNMP, Syslog, XMLAPI and UCS CLI). UCSM and Standalone C-Series Monitoring Overview: Additional Cisco Monitoring Resources: (Cited within this document) ‘Demystifying Monitoring for UCS Manager & C-Series’ Tech Talk available here:
0 kommentar(er)
