How to Inject a Simulated Fault

1. At the command prompt, type the following command:

   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.

2. At the command prompt, type the following command:

   # 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.

   ---