IMM in shared mode with Broadcom NetXtreme II ML2 10GBase-T drops Remote Control during POST - IBM Systems

Resolving The Problem

Source

RETAIN tip: H213427

Symptom

When the Integrated Management Module (IMM) Network Configuration is set to Shared Mode (NC-SI) with the Broadcom NetXtreme II ML2 10GBase-T Adapter, the IMM Remote Control Session will disconnect during Power On Self Test (POST).

Upon disconnection, a status box will appear explaining that the IMM Remote Control session has disconnected.

The Remote Control session disconnection occurs each time NC-SI is enabled with the Broadcom NetXtreme II ML2 10Gbase-T adapter and the system enters POST.

Affected configurations

The system may be any of the following IBM servers:

• System x3750 M4, type 8718, any model, any AC1
• System x3750 M4, type 8752, any model
• System x3850 X6, type 3837 (4-socket, 3-year warranty), any model
• System x3850 X6, type 3839 (4-socket, 4-year warranty), any model
• System x3950 X6, type 3837 (8-socket, 3-year warranty), any model
• System x3950 X6, type 3839 (8-socket, 4-year warranty), any model

The system is configured with one or more of the following IBM Options:

• Broadcom NetXtreme II ML2 Dual-Port 10GbaseT for IBM System X, Option part number 00D2026, any 94Y5233

This tip is not software specific.

The T7.10 firmware for the Broadcom NetXtreme II adapters is affected.

Solution

There will not be a fix to this issue, as the IMM Remote Control disconnection during Shared Mode with the Broadcom NetXtreme II ML2 10GBase-T Adapter is a permanent limitation.

Workaround

When the IMM Remote Control session disconnects during POST, Operating System Boot, or system restart, the user can restart the Remote Control session once connection to the IMM is restored.

Additional Information

QLogic has determined that the loss of the IMM Remote Control connection in Shared Mode (NC-SI) is expected behavior.

There is a temporary connection (ping) loss when the link trains from 1 Gb to 10 Gb and vice-versa. The connection is restored, but not in enough time for the IMM Remote Control session to stay connected.

The workaround allows for the user to reconnect to the Remote Control session once IMM connectivity is restored.