SuperCluster and Exadata smconfigtest:ERROR: /etc/opensm/opensm.conf file has log_max_size out of range: 8, should not be greater than 4 during IB switch pacthing or enablesm

Asset ID:	1-72-2013833.1
Update Date:	2015-05-25
Keywords:

Solution Type Problem Resolution Sure

Solution 2013833.1 : SuperCluster and Exadata smconfigtest:ERROR: /etc/opensm/opensm.conf file has log_max_size out of range: 8, should not be greater than 4 during IB switch pacthing or enablesm

Applies to:

Solaris SPARC Operating System - Version 11.1 to 11.1 [Release 11.0]
SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster T5-8 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster M6-32 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Exadata Storage Server Software - Version 11.2.3.3.1 to 12.1.2.1.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

During patching or enablesm manual command you get an smconfigtest:ERROR stating

smconfigtest:ERROR: /etc/opensm/opensm.conf file has log_max_size out of range: 8, should not be greater than 4
SubnetManager configuration is invalid.

Changes

Patching the IB switches with either patchmgr or patchmgr-ibsw or running enablesm for other reasons

Cause

The switch was either delivered or modified in some way to change the setting from 4 to 8

Solution

Run "vi /etc/opensm/opensm.conf" to restore "log_max_size 4".

smconfigtest , patchmgr or enablesm now reports:

smconfigtest:ERROR: /etc/opensm/opensm.conf has been modified. Please configure the SM using the /SYS/Fabric_Mgmt CLI.
SubnetManager configuration is invalid.

Running "vi /etc/opensm/opensm.conf" is the ONLY way to restore "log_max_size 4". So, to trick smconfigtest to think such changes are done via the /SYS/Fabric_Mgmt restricted shell, we can do a simple setting (i.e. change then restore). So in the code below we change from the original smpriority and back.

- Run spsh to enter into the IB switch iLOM prompt.

-> ls /SYS/Fabric_Mgmt
> setsmpriority list
> setsmpriority 2
> setsmpriority 5
> exit
-> exit

I your original smconfigtest:ERROR is just about smpriority you can change it following the shell steps to change it form the original value to the proper one.

References

<NOTE:1567979.1> - Oracle SuperCluster Supported Software Versions - All Hardware Types
<NOTE:1632521.1> - SuperCluster- Solaris 11 Support Repository Updates (SRU) and Jumbo Interim Diagnostic Relief (JIDR) Support Matrix.

Attachments

This solution has no attachment