Exalogic Spine Switch Error When Running Exachk in an Exadata/Exalogic Multirack Environment

Asset ID:	1-71-1994298.1
Update Date:	2015-08-12
Keywords:

Solution Type Technical Instruction Sure

Solution 1994298.1 : Exalogic Spine Switch Error When Running Exachk in an Exadata/Exalogic Multirack Environment

Applies to:

Exalogic Elastic Cloud X3-2 Hardware - Version X3 and later
Oracle Exadata Storage Server Software - Version 11.1.0.3.1 and later
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.2 to 2.0.6.0.2
Information in this document applies to any platform.

Goal

Can we disregard the following errors when running Exachk on an Exadata Machine that is part of a multi-rack configuration with Exalogic?

skipping Infiniband switch HOSTNAME configuration (checkid:- 9AD56124DDFE9FCCE040E50A1EC038A6) on el01sp01 because s_sysconfig_network_el01sp01.out not found
skipping Infiniband Switch NTP configuration (checkid:- 9AD59DE0898D0513E040E50A1EC03EEA) on el01sp01 because s_ntp_el01sp01.out not found
skipping Infiniband switch routing_engine configuration (checkid:- 9AD8F72CFE0AC95BE040E50A1EC050D0) on el01sp01 because s_opensm_el01sp01.out not found
skipping Infiniband switch log_flags configuration (checkid:- 9ADA623709086DC5E040E50A1EC0168D) on el01sp01 because s_opensm_el01sp01.out not found
skipping Infiniband switch controlled_handover configuration (checkid:- 9ADAAD73FF532FE4E040E50A1EC0284E) on el01sp01 because s_opensm_el01sp01.out not found

Solution

Per the error, Exachk is skipping the validation because there is no .out file for the given NM2-36P switch which is actually the Exalogic spine switch that is being used to connect Exalogic to Exadata. This is expected as the Exalogic NM2-36P spine switch wouldn't be checked for Exadata. The messages can be ignored.

References

<NOTE:1478378.1> - Exalogic Exachk Health-Check Tool Known Issues

Attachments

This solution has no attachment