Fujitsu M10-1
 
Fujitsu M10-4S
 
Fujitsu M10-4
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
 

In this Document

Purpose

Details

Applies to:

Purpose

Provide additional information for message IDs: M10-Heartbeat

Fujitsu fault code:

FF010001

Details

Type

Hardware Fault

   Heartbeat

Severity

Minor

Description

It is possible to create a test heartbeat event and SNMP trap from the XSCF command line or XSCF BUI to check functionality of the M10 system heartbeat reporting mechanism. The trap generated is the standard fault trap but with a Fujitsu fault code value set to FF010001. On receipt of this trap, Oracle's Auto Service Request (ASR) infrastructure recognises this special fault code value as indicative of a heartbeat trap and processes it accordingly.

To generate a heartbeat event from the XSCF command line:

 XSCF> rastest -c hb

This will generate an error message that can be viewed with the showlogs error XSCF command, and, if SNMP is enabled on the XSCF, a heartbeat trap will be forwarded to any designated traphost(s).

Date: Jun 02 10:36:34 PDT 2014
    Code: 10000000-003e010000ff0000ff-ff0100010000000000000000
    Status: Information            Occurred: Jun 02 10:36:31.358 PDT 2014
    FRU: /BB#0/CMUL
    Msg: Pseudo error for heartbeat trap notice
XSCF>

The heartbeat trap will look something like this, for SNMP v2c:

2014-06-02 13:36:05 servername.customer.com [192.168.0.1]:
        DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25574) 0:04:15.74     
SNMPv2-MIB::snmpTrapOID.0 = OID:
SNMPv2-SMI::enterprises.211.1.15.4.1.2.0.1     
SNMPv2-SMI::enterprises.211.1.15.4.1.1.12.2.1.13.1.0.2.0.254.0 = INTEGER: 1     
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.2.0 = INTEGER: 4       
SNMPv2-SMI::enterprises.211.1.15.4.1.1.4.3.0 = STRING: "2081233004"     
SNMPv2-SMI::enterprises.211.1.15.4.1.1.4.2.0 = STRING: "SPARC M10-4S"   
SNMPv2-SMI::enterprises.211.1.15.4.1.1.4.1.0 = STRING: "servername"     
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.14.0 = STRING: "FF010001"      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.15.0 = STRING: "Jun 02 10:36:31.358 PDT 2014"  
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.16.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.17.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.18.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.19.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.20.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.21.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.22.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.23.0 = ""      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.24.0 = STRING: "Fujitsu M10-4S"        
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.25.0 = INTEGER: 1      
SNMPv2-SMI::enterprises.211.1.15.4.1.2.1.26.0 = STRING: "M10-Heartbeat"

Automated Response

Immediately following XSCF reboot if SNMP is enabled, or after SNMP is configured and enabled, a heartbeat trap is automatically generated and forwarded to the designated traphost(s). Heartbeat traps then continue to be automatically generated at approximately 12-hourly intervals, or, if rastest -c hb or the XSCF BUI heartbeat test is invoked, at 12-hourly intervals from the last time a heartbeat was generated at the command line or BUI.

Note that there are no log file entries created (showlogs error output, as shown above) for the automatic heartbeat events, only for the rastest -c hb or BUI heartbeat events.

Impact

No hardware is degraded or marked as faulty. rastest -c hb from the XSCF command line or the XSCF BUI heartbeat test are purely test mechanisms and have no impact on system operation.

Indicted Hardware

None.

Suggested Action for System Administrator

No action for this event is required.

System Administrators should reference the document SPARC M10 Systems System Operation and Administration Guide on docs.oracle.com for instructions on setting-up and testing SNMP configurations.

This solution has no attachment