This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized management capabilities, creates a unified management domain, and serves as the central nervous system of the Cisco Unified Computing System. UCS configuration is comprised of operational and administrative settings. The data is organized hierarchically in a tree structure, starts from the top (root) and contains children and parent nodes. Each node in the tree is a managed object and each object in the UCS has a unique Distinguished Name (DN) that describes the object and its place in the tree. Every managed object is also identified through a CucsManagedObjectId of type integer. Managed objects are abstractions of real world resources, they represent the physical and logical components of the UCS, for example, switch, chassis, blades, and so on. Properties on the Managed Objects (MO) are characterized as configurations and operations. Configuration Policies are the majority of the policies in the system and are used to describe configurations of different components of the UCS. Policies determine how the system behaves under specific circumstances. Certain MOs are not created by users, but are automatically created by the UCS, power supply objects and fan objects are examples of automatically created MOs.
IPHost Network Monitor offer an easy way of SNMP monitoring your Cisco Servers, Routers, Switches, Bridges, Firewalls, Repeaters.
OID list for CISCO-UNIFIED-COMPUTING-MIB
- A table of UCS faults. This table may contain both active and cleared faults. The following UCS Managed Objects may have faults: * MOs representing physical equipment, such as chassis, blades, fans, IO modules, interface cards... * Service Profiles and th ...
- This object uniquely identifies a specific instance of a UCS fault. For example, if two separate chassis have a Fan Failure, then each chassis will have a fault instance with a unique index.
- A human-readable message providing details about the fault.
- This object uniquely identifies the managed object on which this fault is occurring. For example, suppose a chassis has 2 power supply units PSU1 and PSU2. PSU1 is operational and PSU2 is in a failed state, hence the MO representing PSU2 has a fault. Supp ...
- The distinguished name (DN) of the managed object that has a fault. The DN value provides a friendly unique identifier for the object and can be used to query Managed Objects through the XML API.
- The date and time when the fault was created.
- The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.
- A code uniquely identifying the fault class. A managed object can have multiple faults, but it cannot have multiple faults with the same code.
- This object is used to categorize faults.
- A code identifying the probable cause of the fault.
- A code identifying the perceived severity of the fault.
- The number of times this fault has occurred since the fault became active. This counter can only increase when the fault is active. It does not increase when the fault is cleared. When a fault is cleared, the value of this counter remains at the value it ...
- A collection of objects providing UCS fault information.
Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring network devices right now.