About This Documentation (PDF and HTML)
Related Third-Party Web Site References
Introduction to Sun Server Management Agents
Sun Server Management Agents Features
Sun Server Hardware Management Agent
Sun Server Hardware SNMP Plugins
Sun Server Storage Management Agent
Sun SSM Component Manager Overview
Upgrading from Previous Versions
(Linux and Solaris) Using Component Manager
(Linux and Solaris) Using Component Manager in Interactive Mode
(Linux and Solaris) Using Component Manager in Unattended Mode
(Windows) Using Component Manager
(Windows) Using the Component Manager Graphic Interface
(Windows) Using Component Manager Command-line Interface
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:
(Solaris and Linux) Hardware Management Agent Runtime Options
Configuring your Host Operating System's SNMP
(Solaris and Linux ) Configuring Net-SNMP/SMA
Sun Server Hardware SNMP Plugins
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
Working With Management Agents
Retrieving and Setting Information Through SNMP
Troubleshooting Management Agents
General Management Agents Troubleshooting
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
which 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 Windows application log correspond exactly to the SNMP traps. On Linux and Solaris operating systems, the messages are logged with facilitydaemonand level notice.
Note - If records corresponding to SNMP traps are not being stored on Linux and Solaris operating systems, make sure that the daemon facility and notice level are enabled.