Skip Navigation Links | |
Exit Print View | |
Oracle Hardware Management Pack 2.2.x HTML Documentation Collection |
Management Agents User's Guide
Oracle Server Management Agents User's Guide Overview
Oracle Server Management Agents
Oracle Server Hardware Management Agent
Oracle Server Hardware SNMP Plugins
itpconfig and the ILOM Trap Proxy
Configuring Hardware Management Agent and Hardware SNMP Plugins
Hardware Management Agent Configuration File
Configuring the Hardware Management Agent Logging Level
How to Configure the Hardware Management Agent Logging Level
Configuring your Host Operating System's SNMP
(Solaris and Linux ) Configuring Net-SNMP/SMA
(Windows) How to Configure SNMP
Oracle Server Hardware SNMP Plugins Overview
Overview of Sun HW Monitoring MIB
Sun Server Product and Chassis
Sun Server Hardware Monitoring MIB
Sun Server Hardware Management Agent
Sun Server Hardware Monitor Sensor Group
Physical and Logical Storage Objects
Working With Management Agents
Retrieving and Setting Information Through SNMP
How to Retrieve the Product Information from a Sun x86 Server
How to Retrieve The Product Information on a Sun x86 Server Module
How to Retrieve the Server Module's Product Chassis Information
How to Retrieve Service Processor Information
How to Retrieve Inventory Information
How to Retrieve the Sensor Group Information
How to Set the Indicator Locator
Host-to-ILOM Interconnect Configuration Commands
How to Enable Host-to-ILOM Interconnect
How to Disable Host-to-ILOM Interconnect
How to List the Host-to-ILOM Interconnect Settings
itpconfig Trap Forwarding Commands
How to Disable Trap Forwarding
Configuring Trap Forwarding on Windows Servers
How to configure trap forwarding on Windows servers
Troubleshooting Management Agents
General Management Agents Troubleshooting
Oracle Solaris Operating System Troubleshooting
How to Remove a Packaging Lock File
Hardware Management Agent Service Fails to Start
How to Solve Issues With IPMI Device Drivers
Hardware Management Agent Service Status Dead
Caution ‐ This procedure returns test SNMP traps, however the values received might not match the values you expect to see when a real SNMP trap is generated. This does not impact non-test SNMP trap functionality. |
ipmitool -U user -P password -H hostname -v sdr list
Choose a sensor from the returned list that you want to inject a simulated fault to. In this example the IPMI event: 'P0/VTT' unc assert is used.
# ipmitool -U user -P password -H hostname event 'P0/VTT' unc assert
This injects the IPMI event: 'P0/VTT' unc assert.
You should receive an SNMP trap similar to the following:
sysUpTime.0 = Timeticks: (4300) 0:00:43.00
snmpModules.1.1.4.1.1 = OID: sunHwTrapVoltageNonCritThresholdExceeded
sunHwTrapSystemIdentifier.0 = STRING: sg-prg-x6220-01-sp0
sunHwTrapChassisId.0 = STRING: 1005LCB-0728YM01R7::0739AL71EA
sunHwTrapProductName.0 = STRING: SUN BLADE 6000 MODULAR SYSTEM::SUN BLADE X6220 SERVER MODULE
sunHwTrapComponentName.0 = STRING: /SYS/MB/P0/VTT
sunHwTrapThresholdType.0 = INTEGER: upper(1)
sunHwTrapThresholdValue.0 = STRING:
sunHwTrapSensorValue.0 = STRING:
sunHwTrapAdditionalInfo.0 = STRING: Upper Non-critical going high
sunHwTrapAssocObjectId.0 = OID: zeroDotZero
sunHwTrapSeverity.0 = INTEGER: nonCritical(4)
You can verify the SNMP trap by checking the syslog record, which should contain something similar to the following:
sg-prg-x6250-01 hwagentd[3470]: P0/VTT (Sensor ID: 0x1b) (Record ID: 0x821): Upper Non-critical going high.
The messages stored in syslog or the Windows application log correspond exactly to the SNMP traps. On Linux and Oracle Solaris operating systems, the messages are logged with facility daemon and level notice.