CISCO-UNIFIED-COMPUTING-MIB: View SNMP OID List / Download MIB

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.

This notification is generated by a UCS node whenever a fault is active and the fault state changes.

This notification is generated by a UCS node whenever a fault is cleared.

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 their sub-components. * vNIC and vHBA templates. * Pools, such as server pools or WWN pools. * Port channels.

An entry in the UCS fault table. Entries appear in this table when faults are active. A system-wide fault policy specifies what to do when faults are cleared: * clearAction: what should happen to cleared faults (retain or delete) * retentionInterval: duration (seconds) to retain a cleared fault * flapInterval: duration (seconds) to detect possible flapping condition * clearInterval: for non-auto-cleared faults, duration (seconds) for a fault to be cleared Cleared faults may or may not remain in this table depending on the fault policy. Refer to the UCS documentation for more details about the fault policy.

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.

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. Suppose the MO Id of PSU2 is '1234' and its DN is 'sys/chassis-5/psu-1'. The cucsFaultTable table would have an entry for the PSU fault. The value of cucsFaultAffectedObjectId would be set to 'psuTable.psuEntry.1.1234' and the value of cucsFaultAffectedObjectDn would be set to 'sys/chassis-5/psu-1'.

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.

A code identifying the probable cause of the fault.

A code uniquely identifying the fault class. A managed object can have multiple faults, but it cannot have multiple faults with the same code.

The date and time when the fault was created.

A human-readable message providing details about the fault.

The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.

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 was before the fault was cleared.

A code identifying the perceived severity of the fault.

This object is used to categorize faults.

The compliance statement for entities that support the Cisco UCS Fault Managed Objects.

A collection of objects providing UCS fault information.

The set of UCS notifications defined by this MIB.