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.
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.
cucsFaultIndex
1.3.6.1.4.1.9.9.719.1.1.1.1.1
CucsManagedObjectIdA 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'. · Unsigned32 · hint d
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.
cucsFaultAffectedObjectId
1.3.6.1.4.1.9.9.719.1.1.1.1.4
RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row.
For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER
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'.
cucsFaultAffectedObjectDn
1.3.6.1.4.1.9.9.719.1.1.1.1.5
CucsManagedObjectDnAn 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'. · OCTET STRING
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 uniquely identifying the fault class. A managed object can have multiple faults, but it cannot have multiple faults with the same code.
cucsFaultCreationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was created.
cucsFaultDescription
1.3.6.1.4.1.9.9.719.1.1.1.1.11
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
A human-readable message providing details about the fault.
cucsFaultLastModificationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.14
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.
cucsFaultOccur
1.3.6.1.4.1.9.9.719.1.1.1.1.16
Counter32
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.
cucsFaultSeverity
1.3.6.1.4.1.9.9.719.1.1.1.1.20
CucsFaultSeverity0 = cleared1 = info3 = warning4 = minor5 = major6 = criticalA code used to identify the severity of a fault · Integer32
A code identifying the perceived severity of the fault.
This notification is generated by a UCS node whenever a fault is active and the fault state changes.
cucsFaultDescription
1.3.6.1.4.1.9.9.719.1.1.1.1.11
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
A human-readable message providing details about the fault.
cucsFaultAffectedObjectId
1.3.6.1.4.1.9.9.719.1.1.1.1.4
RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row.
For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER
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'.
cucsFaultAffectedObjectDn
1.3.6.1.4.1.9.9.719.1.1.1.1.5
CucsManagedObjectDnAn 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'. · OCTET STRING
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.
cucsFaultCreationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was created.
cucsFaultLastModificationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.14
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.
A code identifying the probable cause of the fault.
cucsFaultSeverity
1.3.6.1.4.1.9.9.719.1.1.1.1.20
CucsFaultSeverity0 = cleared1 = info3 = warning4 = minor5 = major6 = criticalA code used to identify the severity of a fault · Integer32
A code identifying the perceived severity of the fault.
cucsFaultOccur
1.3.6.1.4.1.9.9.719.1.1.1.1.16
Counter32
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.
cucsFaultClearNotif
1.3.6.1.4.1.9.9.719.0.2
This notification is generated by a UCS node whenever a fault is cleared.
cucsFaultDescription
1.3.6.1.4.1.9.9.719.1.1.1.1.11
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
A human-readable message providing details about the fault.
cucsFaultAffectedObjectId
1.3.6.1.4.1.9.9.719.1.1.1.1.4
RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row.
For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER
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'.
cucsFaultAffectedObjectDn
1.3.6.1.4.1.9.9.719.1.1.1.1.5
CucsManagedObjectDnAn 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'. · OCTET STRING
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.
cucsFaultCreationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was created.
cucsFaultLastModificationTime
1.3.6.1.4.1.9.9.719.1.1.1.1.14
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the fault was last modified. The modification time is changed whenever a fault attribute is changed.
A code identifying the probable cause of the fault.
cucsFaultSeverity
1.3.6.1.4.1.9.9.719.1.1.1.1.20
CucsFaultSeverity0 = cleared1 = info3 = warning4 = minor5 = major6 = criticalA code used to identify the severity of a fault · Integer32
A code identifying the perceived severity of the fault.
cucsFaultOccur
1.3.6.1.4.1.9.9.719.1.1.1.1.16
Counter32
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.