Skip to main content

10.3.4 Traps

10.3.4 Traps
If you enable the SNMP agent function, a notification called Trap is issued to the SNMP manager. XSCF traps cover the following events:
  1. Heartbeat notification (XCP 2050 or later)
  2. XSCF failover occurrence
  3. Configuration changes due to the addition, removal, replacement, etc. of PSBs and components
  4. Failure occurrence of a part in the system, or replacement of the failed part in the system followed by recovery in such cases
  5. Change of a physical partition to the start, panic, power-off, or other state
  6. Incorporation or release of a BB (PSB) in a physical partition
  7. Hypervisor abort
  8. Configuration changes such as the addition and deletion of parts in the PCI expansion unit
  9. Change of the LED status of a part in the PCI expansion unit
  10. Abnormal temperature of the PCI expansion unit
  11. Mode switch change
  12. When a panic or other change in status of the logical domain occurs
  13. Start of the XSCF SNMP agent function (standard trap)
  14. Unauthorized access to the XSCF SNMP agent (standard trap)
  15. Issuing of a cold start trap (standard trap) generated when a change in management object configuration occurred at the SNMP agent start time
Among the parts monitored by the XSCF in the system, the target part of a trap can be identified from the failure location and part number. A trap is generated when an XSCF event notification is issued, even if the part cannot be identified.

The following example shows the SNMP-Trap for the failure occurrence of a part in the system.
Aug 12 06:07:16 paplsv2 snmptrapd[11958]: 2012-08-12 06:07:16 A4U4S141 [] (via UDP: []:38221) TRAP, SNMP v1, community abccommunity    XSCF-SP-MIB::scfMIBTraps Enterprise Specific Trap (XSCF-SP-MIB::scfComponentStatusEvent) Uptime: 6:27:33.28 = INTEGER: deconfigured(4)      XSCF-SP-MIB::scfTrapStatusEventType.0 = INTEGER: alarm(1)
This example contains the following information:
  1. IP address of the XSCF that issued the trap (e.g.,
  2. Community string under SNMPv1 (e.g., adcommunity)
  3. Trap type (e.g., EnterpriseSpecific, model-specific trap)
  4. Trap issuing time (e.g., Uptime: 6:27:33:28)
  5. Additional trap information
    The information may include a possibly faulty part, event type, or error level. 
For the firmware version XCP 2050 or later, if you enable the XSCF SNMP agent function, the XSCF heartbeat notification (existence information) traps are sent to the system.
The heartbeat notifications are sent at the occurrence of the following events.
  1. When the XSCF SNMP agent function is started or resumed.
  2. Every 12 hours since the start of the XSCF SNMP agent function
  3. When the rastest -c hb command is executed
The following example shows an SNMP trap concerning the XSCF heartbeat notification.
You can confirm the XSCF heartbeat notification when the trap code is "FF010001" and MessageId of the trap is "M10-Heartbeat."
(solaris. [1 1 0] 1)
(solaris. [1 1 0] 4)
(solaris. [2 10 0] PZ31426015)
(solaris. [2 11 0] SPARC M10-1)
(solaris. [2 10 0] x-integ-ts)
(solaris. [2 8 0] FF010001)
(solaris. [2 28 0] Oct 23 03:06:04.367 JST 2014)
(solaris. [2 0 0] )
(solaris. [2 0 0] )

(solaris. [2 0 0] )
(solaris. [2 0 0] )
(solaris. [2 0 0] )
(solaris. [2 0 0] )
(solaris. [2 0 0] )
(solaris. [2 0 0] )
(solaris. [2 13 0] Fujitsu M10-1)
(solaris. [1 1 0] 1)
(solaris. [2 13 0] M10-Heartbeat) 
For details of the OID information about the XSCF heartbeat notification, see "Chapter 5 XSCF Trap Type List" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF MIB and Trap Lists.
XSCF Trap Information
XSCF traps consist of traps that report failures and traps that report changes in the system status. To send the appropriate traps to the systems used, make the necessary trap reception settings with the SNMP manager.
For information on the lists of XSCF SNMP MIB traps, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF MIB and Trap Lists.