Logging in as ilom-admin on a 36P or GW Infiniband Switch hangs as well as the spsh command hangs when logged in as root

Asset ID:	1-72-2359268.1
Update Date:	2018-02-09
Keywords:

Solution Type Problem Resolution Sure

Solution 2359268.1 : Logging in as ilom-admin on a 36P or GW Infiniband Switch hangs as well as the spsh command hangs when logged in as root

Applies to:

Sun Datacenter InfiniBand Switch 36 - Version All Versions to All Versions [Release All Releases]
Sun Network QDR InfiniBand Gateway Switch - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

When logging into an Infiniband switch as ilom-admin the prompt hangs and never get's to ILOM
When loged in as root and attempting to start ILOM using the spsh command, it hangs and doesn't enter ILOM

The following command (Note: if the switche was recently booted, you may have to execute this command a couple of times to see the error):

# service ilom status

Returns the following:

[root@localhost ~]# service ilom status
ILOM stack is partly started with 14 processes.
ILOM daemons that failed to start are : IPMIMain MsgHndlr PEF LAN
However, ILOM stack subsystem is locked..... OK!

Changes

Disabling IPv6 on the Infiniband switch:

-> set /SP/network/ipv6/ state=disabled

Cause

Bug 27506307 : IPMI stack/ILOM spsh fails to starts when IPv6 is disabled

Solution

WORKAROUND:

Workaround is to make IPv6 stack enabled:

1- verify that /etc/sysconfig/network-scripts/ifcfg-eth0 has IPV6INIT set to
yes as below:

IPV6INIT=yes
This is set to no when IPV6 stack is down.

2- verify that /tmp has correct permissions:

# ls -l /
drwxrwxrwt X root root X X X tmp

If that is not the case, please fix that by doing the following commands and
verify the permissions again:

chmod 777 /tmp
chmod g-s /tmp
chmod o+t /tmp

3- Verify /conf/ipv6.conf has ipv6-disabled set to 0:

ipv6-disabled 0
(This is set to 1 when IPV6 is disabled using ILOM targets.)

4- reboot the switch after changes.

The fix for this issue will be included in the 2.2.9 release of the firmware.

Attachments

This solution has no attachment