Exachk Reports Master (Rack) Serial Number Does Not Match for Exadata

Asset ID:	1-72-1634742.1
Update Date:	2014-06-26
Keywords:

Solution Type Problem Resolution Sure

Solution 1634742.1 : Exachk Reports Master (Rack) Serial Number Does Not Match for Exadata

Applies to:

Exadata Database Machine V2 - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X2-8 - Version All Versions to All Versions [Release All Releases]
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X3-8 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Customer owns V2 in half configuration
Initial configuration:
  4 db server
  7 cells
  2 infiniband switch

Actual configuration: The rack physically is not splitted.
  2 db server + 3 cells
  2 db server + 4 cells

First environment:
db node: hrsfo001, hrsfo002
cell node:
hrsao001lan, hrsao002lan, hrsao003lan

Second environment:
db node: hrsfo003, hrsfo004
cell node:
hrsao004lan, hrsao005lan, hrsao006lan, hrsao007lan

All servers have the same system_identifier.

On exechk execution only for second environment:
./exachk -clusternodes hrsfo003,hrsfo004

Exachk version used --2.2.3.2_20131213
Status on Cluster Wide:
FAIL => Master (Rack) Serial Number does not match across database servers and storage servers or not set on one or more server ---- Failure error.

hrsfo003 = Sun Oracle Database Machine 1007AK2043
hrsao004lan2 = Sun Oracle Database machine 1007AK2043
hrsao005lan2 = Sun Oracle Database machine 1007AK2043
hrsao006lan2 = Sun Oracle Database machine 1007AK2043
hrsao007lan2 = Sun Oracle Database machine 1007AK2043
hrsfo004 = Sun Oracle Database machine 1007AK2043

Using the command "ipmitool sunoem cli 'show /SP system_identifier'" all server reports the correct Exadata serial number: Sun Oracle Database machine 1007AK2043.

And exachk fails for FAIL => Master (Rack) Serial Number does not match across database servers and storage servers or not set on one or more server ---- Failure error.

Cause

In the system_identifier, the word "machine" should be "Machine" with a leading capital M. Therefore hrsfo003 is correct, the others are not.

Solution

The information required to change the MSN is provided in the "View" detail section of the generated HTML report:

On any server where the MSN (Master (Rack) Serial Number) is not set correctly, use the following command as the "root" userid to set it:
ipmitool sunoem cli 'set /SP system_identifier="text_identifier_string serial_number"'' -- ipmitool sunoem cli 'set /SP system_identifier="Sun Oracle Database Machine 1007AK2043"'

Now re-running the exachk will not fail on the Serial Number -- FAIL => Master (Rack) Serial Number does not match across database servers and storage servers or not set on one or more server.

References

<BUG:14319261> - EXACHK REPORTS MASTER RACK SERIAL NUMBER CHECK FAILED WHEN RAW DATA SHOWS OK
<NOTE:1351036.1> - How to Validate and Fix Proper ASM Failure Group Configuration on Oracle Exadata Database Machine
<NOTE:1070954.1> - Oracle Exadata Database Machine exachk or HealthCheck
<NOTE:1575239.1> - Exachk Reports "FAIL Storage Server Check One or more Exadata storage server does not meet system model number requirement"
<BUG:18188287> - EXACHK REPORTS MASTER (RACK) SERIAL NUMBER DOES NOT MATCH FOR EXADATA

Attachments

This solution has no attachment