Exadata Database Machine X2-2 Full Rack
 

PLA-Support>Database Technology>Engineered Systems>Oracle Exadata>DB: Exadata_EST
 
.Old GCS Categories>ST>Server>Engineered Systems>Exadata>Administration and Configuration
 

Applies to:

Symptoms

While watching the exachk executable run, you may see errors displayed to the screen:

Collecting - Verify Electronic Storage Module (ESM) Lifetime is within Specification
/tmp/exachk_cells.sh: line 25: [: N/A: integer expression expected
/tmp/exachk_cells.sh: line 25: [: N/A: integer expression expected
/tmp/exachk_cells.sh: line 25: [: N/A: integer expression expected
/tmp/exachk_cells.sh: line 25: [: N/A: integer expression expected

However, in the HTML summary page, the ESM is reported as PASS:

PASS    Storage Server Check    Electronic Storage Module (ESM) Lifetime is within specification for all flash cards on all storage servers    All Storage Servers

Cause

Exadata has a new version of Aura card: 1.1.  This version no longer presents a value for upper thresholds.  As such, the exachk script is in the process of being modified to handle this change.

Aura 1.0 card example:
        upper_nonrecov_threshold = 17500.000 Hours
        upper_critical_threshold = 17200.000 Hours
        upper_noncritical_threshold = 16800.000 Hours

Aura 1.1 card example:
       upper_nonrecov_threshold = N/A
       upper_critical_threshold = N/A
       upper_noncritical_threshold = N/A

Solution

This can be ignored.  There is no error.  You can confirm if your cards are programmed with N/A by using the following script:

for RISER in RISER1/PCIE1 RISER1/PCIE4 RISER2/PCIE2 RISER2/PCIE5; do ipmitool sunoem cli force "show /SYS/MB/$RISER/F20CARD/UPTIME";done;

This should be fixed in the exachk 2.1.3 release.

This solution has no attachment