JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Hardware Management Connector for IBM Tivoli Netcool/OMNIbus User's Guide
Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon

Document Information

Using This Documentation

Introduction

Installing Oracle HMC for Netcool/OMNIbus

Configuring Oracle Servers for IBM Netcool OMNIbus Monitoring

Choosing a Configuration Procedure

Configuring Oracle Servers for OS Level Monitoring

Configure the SNMP Management Agent File on SPARC Solaris

Configuring Oracle Servers for SP Level Monitoring

Configure SNMP Protocol Settings on Oracle ILOM SP

Configuring x86 Embedded LOM Version 2.91 Service Processors

Configure SNMP Protocol Settings on Embedded LOM SP Version 2.91

Configuring x86 Embedded LOM Version 4.x Service Processors

Configure SNMP Protocol Settings on Embedded LOM SP Version 4.x

Verifying Successful Configuration for IBM Netcool/OMNIbus

Verifying Configuration Manually

Test the Configuration Manually

Verifying Configuration Remotely Using ALOM

Verify Configuration for Remote ALOM-based SPARC Solaris System

Verifying Configuration Remotely Using IPMItool

Verify IBM Netcool/OMNIbus Is Configured to Receive Traps From Server SP

Verifying Configuration Remotely Using psradm

Verify Configuration Remotely and Generate Trap Using Solaris psradm Utility

Monitoring Oracle Servers in IBM Netcool/OMNIbus

Release Notes

Index

Verify IBM Netcool/OMNIbus Is Configured to Receive Traps From Server SP

  1. Collect the following information about the remote service processor that you want to test:
    Parameter
    Value
    SPname
    The name or IP address of the service processor
    SPadminname
    The administrator login name for the service processor
    SPadminpassword
    The administrator password for the service processor
  2. Open a command shell on the system that has IPMItool installed.
  3. Enter the following IPMItool command to generate a list of all available sensors on that remote server.
    ipmitool -U SPadminname -P SPadminpassword -H SPname -v sdr list

    For example, to get the list of available sensors on a Sun SPARC Enterprise T5120 server at IP address 192.168.1.1 and the ILOM SP login is root and password is changeme, use the following command:

    ipmitool -U root -P changeme -H 192.168.1.1 -v sdr list
  4. In the output from IPMItool, identify the Sensor ID name of a sensor that has at least one entry for Assertions Enabled or Deassertions Enabled.

    In the following example, IPMItool returns the following information about the sensor named /MB/T_AMB.

    Sensor ID             : /MB/T_AMB (0x9)
    Entity ID             : 7.0 (System Board)
    Sensor Type (Analog)  : Temperature
    Upper critical        : 55.000
    Assertions Enabled    : lnc- lcr- lnr- unc+ ucr+ unr+
    Deassertions Enabled  : lnc- lcr- lnr- unc+ ucr+ unr+

    This sensor monitors ambient temperature on the motherboard of servers.


    Note -  Exercise caution in choosing a sensor to use for a simulated event. Simulating extreme high or low temperature for some sensors may cause the server to shut down.
  5. Enter the following IPMI command to generate a simulated event:
    ipmitool -U SPadminname -P SPadminpassword -H SPname event sensorname option

    For example, to generate a simulated event for exceeding the upper critical (ucr) ambient temperature on a Sun SPARC Enterprise T5120 server at IP address 192.168.1.1 and the ILOM SP login is root and password is changeme, you would enter the following command:

    ipmitool -U root -P changeme -H 192.168.1.1 event /MB/T_AMB ucr assert

    In the command shell, IPMItool returns information similar to the following:

    Finding sensor /MB/T_AMB ... ok
    0 │ Pre-Init Time-stamp │ Temperature /MB/T_AMB │ \
    Upper Critical going high │ Reading 56 > Threshold \
    55 degrees C
  6. In the message or event console of your management package, verify that it has received an event from Oracle ILOM or from Embedded LOM relevant to the sensor that you specified in your IPMItool command.

    If you do not see these messages in the console, review this manual for required configuration steps or consult the Troubleshooting section of this manual.

  7. (Recommended) – Clear the simulated event with the following syntax:
    ipmitool -U SPadminname -P SPadminpassword -H SPname event sensorname option

    To clear (deassert) the simulated event in the previous example, enter the following command:

    ipmitool -U root -P changeme -H 192.168.1.1 event /MB/T_AMB ucr deassert

    If you do not see these messages in the console, review this manual for required configuration steps or consult the Release Notes section in this guide.