![]() ![]() ![]() The time that the fault was created, depicted in UTC format. The Object identifier (OID) of the mutable object that has the fault. The distinguished name of the mutable object that has the fault. Table 2 cucsFaultTable AttritubesĪ unique integer that identifies the fault. The following table describes the attributes exposed by the cucsFaultTable. In the Cisco UCS Standalone C-Series server WebUI, faults are available in from the Server tab under Faults and Logs. The cucsFaultTable table has the same information as the objects that can be queried through the XML API. 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 same object is used to model all Cisco UCS fault types, including equipment problems, and configuration or environmental issues. Each entry has variables to indicate the nature of a problem, such as its severity and type. The table contains one entry for every fault instance. This notification is generated by a Cisco UCS instance whenever a fault is cleared.Īll Cisco UCS Standalone C-Series server faults are available with SNMP using the cucsFaultTable table and the CISCO-UNIFIED-COMUTING-FAULT-MIB. This notification is generated by a Cisco UCS instance whenever a fault is raised. Table 1 CISCO-UNIFIED-COMPUTING-NOTIF-MIB Traps The following table lists the Cisco UCS traps included in the CISCO-UNIFIED-COMPUTING-NOTIF-MIB. If the fault is transitional and the failure is resolved, then the object transitions to a functional state.Ī fault remains in Cisco UCS Standalone C-Series servers until the fault is cleared and deleted according to the settings in the fault collection policy, or until the Cisco Integrated Managment Controller (CIMC) is restarted. During the life cycle of a fault, it can change from one state or severity to another.Įach fault includes information about the operational state of the affected object at the time the fault was raised. Each fault represents a failure in a Cisco UCS Standalone C-Series server or an alarm threshold that has been raised. In Cisco UCS, a fault is a mutable object that is managed by Cisco UCS. You should download the latest MIBs from whenever you upgrade the Cisco UCS software versions.įor Cisco UCS Standalone C-Series, Release 1.5 and later, see: ftp:///pub/mibs/supportlists/ucs/ucs-C-supportlist.html ![]() NoteĬisco and IETF MIBs are updated frequently. Different software releases support different MIBs. If the agent does not support a specific MIB variable, you must find out what version of system software you are running. For example, you might need to load the Cisco UCS private MIB or the supported RFC MIB into the NMS to execute the required data collection. If the NMS does not recognize a specific MIB variable, you might need to load the MIB into the NMS, usually with a MIB compiler. Typically, if an NMS cannot retrieve a particular MIB variable, either the NMS does not recognize that MIB variable, or the agent does not support the MIB variable. If your NMS cannot get requested information from a Standalone C-Series server or Cisco UCS, then the MIB that allows that specific data collection might be missing. See the IETF website http://for the latest updates to this MIB. Portions of MIB-II have been updated since RFC 1213. MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II. This chapter includes the following sections:Ĭisco UCS MIB files are a set of objects that are private extensions to the IETF standard MIB II. Use Cases for Cisco UCS Standalone C-Series Server MIBs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |