CISCO-UNIFIED-COMPUTING-MIB

Registered at: 1.3.6.1.4.1.9.9.719
Last updated: 2010-05-20 00:00
Organization: Cisco
Revisions: 2010-05-20 00:00
Namespace: cisco
Source file: CISCO-UNIFIED-COMPUTING-MIB
Digest: sha256:b6b9b661435173094bc4b3dfc922c270e2859d53e825f204051f6c8eba161501

Description

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.

Contact

Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: ucs-snmp@cisco.com

Imports

From	Symbols
CISCO-SMI	`ciscoMgmt`
SNMP-FRAMEWORK-MIB	`SnmpAdminString`
SNMPv2-CONF	`MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP`
SNMPv2-SMI	`Counter32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso`
SNMPv2-TC	`DateAndTime, DisplayString, RowPointer, TEXTUAL-CONVENTION`

Imported by

86 module(s) in this corpus import this one; the first 50 are listed.

Load order

Every file a consumer needs in order to load this module, dependencies first.

CISCO-SMI
CISCO-UNIFIED-COMPUTING-MIB
SNMP-FRAMEWORK-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Under this module's arcs

Where the registration tree carries on below this module.

Arc	Name	Module
1.3.6.1.4.1.9.9.719.0	ciscoUnifiedComputingMIBNotifs	`CISCO-UNIFIED-COMPUTING-NOTIFS-MIB`
1.3.6.1.4.1.9.9.719.1	ciscoUnifiedComputingMIBObjects
1.3.6.1.4.1.9.9.719.2	ciscoUnifiedComputingMIBConform	`CISCO-UNIFIED-COMPUTING-CONFORM-MIB`
1.3.6.1.4.1.9.9.719.3	cucsMappingsObjects	`CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB`
1.3.6.1.4.1.9.9.719.4	cucsTextualConventionsObjects	`CISCO-UNIFIED-COMPUTING-TC-MIB`

Textual conventions

Name	OID	Syntax	Access	Status
CucsFaultCode TEXTUAL-CONVENTION A code identifying a class of fault.				current
CucsFaultProbableCause TEXTUAL-CONVENTION A code used to identify the probable cause of a fault				current
CucsFaultSeverity TEXTUAL-CONVENTION A code used to identify the severity of a fault				current
CucsFaultType TEXTUAL-CONVENTION A code used to categorize UCS faults				current
CucsManagedObjectDn TEXTUAL-CONVENTION An immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'.				current
CucsManagedObjectId TEXTUAL-CONVENTION A unique identifier for this managed object. Objects in UCS Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in UCS Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CucsManagedObjectId, which is an integer uniquely identifying an object. The CucsManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CucsManagedObjectId set to '13203'.				current

Objects

Name	OID	Syntax	Access	Status
ciscoUnifiedComputingMIBNotifs OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.0
ciscoUnifiedComputingMIBObjects OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.1
cucsFaultObjects OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.1.1
cucsFaultTable OBJECT-TYPE 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.	1.3.6.1.4.1.9.9.719.1.1.1		not-accessible	current
cucsFaultEntry OBJECT-TYPE 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.	1.3.6.1.4.1.9.9.719.1.1.1.1		not-accessible	current
cucsFaultIndex OBJECT-TYPE 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.	1.3.6.1.4.1.9.9.719.1.1.1.1.1	CucsManagedObjectId	not-accessible	current
cucsFaultAffectedObjectId OBJECT-TYPE 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'.	1.3.6.1.4.1.9.9.719.1.1.1.1.4	RowPointer	read-only	current
cucsFaultAffectedObjectDn OBJECT-TYPE 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.	1.3.6.1.4.1.9.9.719.1.1.1.1.5	CucsManagedObjectDn	read-only	current
cucsFaultProbableCause OBJECT-TYPE A code identifying the probable cause of the fault.	1.3.6.1.4.1.9.9.719.1.1.1.1.7	CucsFaultProbableCause	read-only	current
cucsFaultCode OBJECT-TYPE A code uniquely identifying the fault class. A managed object can have multiple faults, but it cannot have multiple faults with the same code.	1.3.6.1.4.1.9.9.719.1.1.1.1.9	CucsFaultCode	read-only	current
cucsFaultCreationTime OBJECT-TYPE The date and time when the fault was created.	1.3.6.1.4.1.9.9.719.1.1.1.1.10	DateAndTime	read-only	current
cucsFaultDescription OBJECT-TYPE A human-readable message providing details about the fault.	1.3.6.1.4.1.9.9.719.1.1.1.1.11	SnmpAdminString (SIZE(0..255))	read-only	current
cucsFaultLastModificationTime OBJECT-TYPE The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.	1.3.6.1.4.1.9.9.719.1.1.1.1.14	DateAndTime	read-only	current
cucsFaultOccur OBJECT-TYPE 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.	1.3.6.1.4.1.9.9.719.1.1.1.1.16	Counter32	read-only	current
cucsFaultSeverity OBJECT-TYPE A code identifying the perceived severity of the fault.	1.3.6.1.4.1.9.9.719.1.1.1.1.20	CucsFaultSeverity	read-only	current
cucsFaultType OBJECT-TYPE This object is used to categorize faults.	1.3.6.1.4.1.9.9.719.1.1.1.1.22	CucsFaultType	read-only	current
ciscoUnifiedComputingMIBConform OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.2
cucsFaultMIBConform OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.2.1
cucsFaultMIBCompliances OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.2.1.1
cucsFaultMIBGroups OBJECT-IDENTITY	1.3.6.1.4.1.9.9.719.2.1.2

Notifications

Name	OID	Status
cucsFaultActiveNotif NOTIFICATION-TYPE This notification is generated by a UCS node whenever a fault is active and the fault state changes.	1.3.6.1.4.1.9.9.719.0.1	current
cucsFaultClearNotif NOTIFICATION-TYPE This notification is generated by a UCS node whenever a fault is cleared.	1.3.6.1.4.1.9.9.719.0.2	current

Conformance

Name	OID	Status
cucsFaultMIBCompliance MODULE-COMPLIANCE The compliance statement for entities that support the Cisco UCS Fault Managed Objects.	1.3.6.1.4.1.9.9.719.2.1.1.1	current
cucsFaultsGroup OBJECT-GROUP A collection of objects providing UCS fault information.	1.3.6.1.4.1.9.9.719.2.1.2.1	current
cucsFaultsNotifGroup NOTIFICATION-GROUP The set of UCS notifications defined by this MIB.	1.3.6.1.4.1.9.9.719.2.1.2.2	current