No "second change" of IP address for Cisco IGESM may cause connectivity loss - IBM eServer BladeCenter

Resolving The Problem

RETAIN tip: H166117

There are situations when customers would like their Cisco Switch Module network on a network separate from the Management Module. In this case, users manually go in and change the Switch Module IP address. The problem is that users are not asked a second time if they really wants to change the IP Address.
 
Other switch modules issue one warning statement that the user may lose connectivity when the IP address of the switch module is changed. They then ask if the user really wants to change this IP address. The Cisco Switch Module only states that the user is going to lose connectivity when he changes the IP address. There is no "second chance" to change the user's mind. When this function is invoked, the user loses connection with the Management Module if the Cisco Switch Module's new IP address is on a different subnet than the Management Module.

The system may be any of the following IBM eServer servers:

• an IBM eServer BladeCenter, type 8677, any model
• an IBM eServer BladeCenter HS40, type 8839, any model
• an IBM eServer BladeCenter HS20, type 8678, any model
• an IBM eServer BladeCenter HS20, type 8832, any model
• an IBM eServer BladeCenter JS20, type 8842, any model

The system is configured with BRET59D (or later) diagnostics.

The system's diagnostics pass.

There is currently no fix for this problem.

There is no workaround for this problem.

This tip warns the user that communication between the Management Module and the Cisco Switch Module may be lost when the IP address of the Cisco Switch Module is changed.