Cisco ucs snmp mib download

Different software releases support different MIBs. You should download the latest MIBs from Cisco. During the life cycle of a fault, it can change from one state or severity to another. Each fault includes information about the operational state of the affected object at the time the fault was raised.

If the fault is transitional and the failure is resolved, then the object transitions to a functional state. The table contains one entry for every fault instance. Each entry has variables to indicate the nature of a problem, such as its severity and type.

The same object is used to model all Cisco UCS fault types, including equipment problems, and configuration or environmental issues. The cucsFaultTable table includes all active faults those that have been raised and need user attention , and all faults that have been cleared but not yet deleted because of the retention interval.

The severity of the fault. Fault severity transitions throughout the lifecyle of the fault, so several different fault severities can be reported during the lifecyle of a fault. These include:. The trap variables indicate the nature of the problem, including the fault type. A fault is cleared when the underlying issue has been resolved. This notification is generated by a Cisco UCS instance whenever a fault is cleared. Inventory information includes data such as , serial numbers, DIMMs, and other intelligence related to system equipment.

The table lists the statistics most commonly monitored in Cisco UCS Standalone C-Series servers, but it does not contain an exhaustive list of all statistics that can be monitored. To gather statistics beyond those listed below, refer to Purpose of the MIBs , review the content of the various packages, and download the additional MIB files necessary to meet your specific needs. This notification is generated by a Cisco UCS instance whenever a fault is raised.

Affected Object DN The distinguished name of the mutable object that has the fault. Last Modification The time when any of the attributes were modified. Code A code that provides information specific to the nature of the fault.

Type The fault type. These include:. In Release 1. The trap variables indicate the nature of the problem, including the fault type. A fault is cleared when the underlying issue has been resolved. You should load the MIBs in the order listed to eliminate most of the load-order issues. Inventory information includes data such as blades , serial numbers, DIMMs, and other intelligence related to system equipment.

The table lists the statistics most commonly monitored in Cisco UCS Manager , but it does not contain an exhaustive list of all statistics that can be monitored. To gather statistics beyond those listed below, refer to Purpose of the Cisco UCS MIBs , review the content of the various packages, and download the additional MIB files necessary to meet your specific needs. This model includes polices, service profiles, configuration and monitoring data, and statistics.

The IF-MIB supports basic management status and control of interfaces and sublayers within a network switch. This MIB provides details about each module, power supply, and fan tray within a switch chassis. It provides enough information to correctly map the containment of these entities within the switch.

Each MIB extension shares the common index value, entPhysicalIndex, which allows the management application developer to link information across multiple MIBs. Extends the entity physical table for modules with processors. Skip to content Skip to search Skip to footer. Book Contents Book Contents.

Find Matches in This Book. PDF - Complete Book 2. Updated: October 9, Table 1. The following table describes the attributes exposed by the cucsFaultTable. Table 2. Affected Object DN The distinguished name of the mutable object that has the fault.

Last Modification The time when any of the attributes were modified. Code A code that provides information specific to the nature of the fault. Type The fault type. Cause The probable cause of the fault.

Severity The severity of the fault. These include: Original severity reported when the fault was first detected Current severity reported for the fault Previous severity reported for the fault Highest severity reported for the fault Occurrence The number of times that a fault has occurred since it was created. Description A human readable string that contains all information related to the fault. Important You should load the MIBs in the order listed to eliminate most of the load-order issues.

Table 3. Note The table lists the statistics most commonly monitored in Cisco UCS Manager , but it does not contain an exhaustive list of all statistics that can be monitored. Table 4. Table 5. Table 6. Was this Document Helpful? Yes No Feedback.