Guest

Cisco UCS Manager

UCSM Faults Report and SNMP Traps

Cisco - UCSM Faults Report and SNMP Traps

Document ID: 112003

Updated: Jul 23, 2010

   Print

Introduction

This document explains the Simple Network Management Protocol (SNMP) support when Cisco Unified Computing System Manager (UCSM) faults occur. Cisco Unified Computing System (UCS) reports equipment and logical faults through SNMP. When UCS detects abnormal condition or defect at the component, equipment, or sub-system level, it reports faults through SNMP traps.

Prerequisites

Requirements

Cisco recommends that you:

  • Have a working knowledge of Cisco UCS Server Blade software and hardware.

  • Be familiar with Cisco UCS components and topology.

  • Be familiar with the Cisco UCS Manager application.

Components Used

The information in this document is based on Cisco UCS 1.3 release.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Configure

Cisco UCS SNMP support sends SNMP traps when UCSM faults occur. This section includes information for the UCSM fault MIB sub tree, fault traps, fault trap attributes, and fault types.

UCSM Fault MIB and Fault Traps

  • Unified Computing MIB - MIB registered under iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.719

  • Trap only - SNMP Get not supported (for UCSM MIB).

  • UCSM Fault Traps - Includes cucsFaultActiveNotif (sent when fault is active or fault attributes change) and cucsFaultClearNotif (sent when fault is cleared).

  • Refer to Accessing and Downloading Cisco MIB Files section of MIB Quick Reference for Cisco UCS for more information.

UCSM Fault Trap Attributes

  • UCS SNMP trap attributes provide all the fault details to identify the nature and cause of the fault that UCSM detects.

  • In the Work pane of the UCSM GUI, click the Faults tab in the Details area in order to view these UCS fault trap attributes for fault details:

    • Description

    • Fault Instance ID

    • Affected Object DN

    • Affected Object OID

    • Creation Time

    • Last Modification

    • Severity

    • Code

    • Type

    • Cause

    • Occurence

UCS Fault Types

  • The UCS fault types provide you with the information as to which component, equipment, or server has detected a failure.

  • There are nine fault types:

    • fsm

    • equipment

    • server

    • configuration

    • environmental

    • management

    • connectivity

    • network

    • operational

Network Diagram

This is the typical topology used with Cisco UCS:

ucsm-faults-report-snmp-traps-01.gif

UCS Faults Reported through SNMP Traps

This section explains how UCS SNMP traps work and how the UCS faults are reported.

SNMP Configuration Steps

Perform these steps in order to configure the UCS SNMP services:

  1. Enable SNMP.

  2. Create trap receivers (configure trap hosts).

  3. Create an SNMPv3 user.

  4. The SNMP configuration is performed through the UCSM GUI and CLI. Refer to Cisco UCS Manager GUI Configuration Guide, Release 1.3(1) and Cisco UCS Manager CLI Configuration Guide, Release 1.3(1) for details.

  5. Refer to Cisco UCS Manager GUI Configuration Guide, Release 1.3(1) for SNMP configuration procedure by using the UCSM GUI. Step-by-step instructions are provided in the Configuring SNMP section.

    ucsm-faults-report-snmp-traps-02.gif

  6. Refer to Cisco UCS Manager CLI Configuration Guide, Release 1.3(1) for SNMP configuration steps using CLI. The command line details are provided in the Configuring SNMP section.

UCS Fault Trap Attribute

UCS SNMP trap attributes provide all the fault details to identify the nature and cause of the fault that UCSM detects.

  1. UCS faults are reported through SNMP traps.

    ucsm-faults-report-snmp-traps-03.gif

  2. In the Navigation pane, click the Equipment tab.

  3. On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.

  4. Choose the server for which you want to view the faults results.

  5. In the Work pane, click the Faults tab.

  6. In the Details area, you can view all the UCS Fault Trap Attributes for fault details.

    ucsm-faults-report-snmp-traps-04.gif

UCS Fault Types

Fault Types tell you exactly where the problem is located. It provides you with the information as to which component, equipment, or server has detected a failure.

  1. There are nine different Fault Types:

    • fsm—Finite State Machine (FSM) failed to complete successfully, or UCSM is retrying one of the FSM stages.

    • equipment—UCSM has detected that a physical component is inoperable.

    • server—UCSM is unable to complete a server task, such as unable to associate a Service Profile to a blade.

    • configuration—UCSM is unable to successfully configure a component.

    • environment—UCSM has detected a power problem, thermal problem, voltage problem, or loss of CMOS settings.

    • management—UCSM has detected a serious management issue. For example, it failed to start critical services, failed to elect the primary switch, vif is down (virtual interface 705 link state is down), or it has detected software version incompatibilities.

    • connectivity—UCSM has detected a connectivity problem, such as adapter is unreachable.

    • network—UCSM has detected a network issue, such as link down.

    • operational—UCSM has detected an operational problem, such as a log capacity issue or discovery failed. For example, a log datastore reached its maximum capacity, and is unable to transfer files; Server (Service Profile) discovery failed.

    Refer to Cisco UCS Faults Reference for a complete list of Faults in Cisco UCS.

  2. As shown in this diagram, it is a connectivity problem:

    ucsm-faults-report-snmp-traps-05.gif

    The Fault Type shows connectivity. The root cause is due to an unreachable adapter.

Verify

This section briefly describes how to check that the MIBS are actually working:

  • Issue the snmpwalk command to verify whether the UCS fault MIBs are present.

  • You can integrate UCSM with HP Openview - HP Openview can be configured to load UCS fault MIBs to verify MIBs present, SNMP traps, and device discovery.

There is currently no verification procedure available for this configuration.

Related Information

Updated: Jul 23, 2010
Document ID: 112003