SL3000/SL8500 - Unable to Install 2nd Handbot on the Rail, The 2nd Handbot Will Not Initialize

Asset ID:	1-72-1929483.1
Update Date:	2017-05-22
Keywords:

Solution Type Problem Resolution Sure

Solution 1929483.1 : SL3000/SL8500 - Unable to Install 2nd Handbot on the Rail, The 2nd Handbot Will Not Initialize

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Bots from other rails were swapped onto rail 2 and the rail came up without any issues due to the fact that the bots had already had code loaded and did not require initialization.

Symptoms

Newly installed bot would not initialize on the rail. The one bot was running on the rail with no issues.

After encountering multiple rail associated failures bot replacement was unsuccessful due to the 2nd bot failing to initialize on the rail.

Changes

The customer had added an additional 2 lpars to the environment prior to encountering this Bot issue.

Cause

When the command network ip route show was issued via the CLI interface the results were as follows

SL8500> network ip route show
10.0.2.65 dev 2A
10.0.2.81 dev 2B
10.0.2.80/28 dev 2B
10.0.2.64/28 dev 2A
10.0.0.0/8 via 10.0.2.65 dev 2A
default via 10.0.2.65 dev 2A

The host ip of 10.0.2.65 directly conflicts with the internal IP address's used by the SL8500 and SL3000 libraries.

Solution

Per the requirements outlined in SL8500 - Host IP Address Conflict (Doc ID 1014452.1)

The following block of IP addresses should not be configured for the Host IP Interface on the SL8500 HBC card. Consider the following range of IP addresses be reserved for the SL8500 and not for customer use:

10.0.0.0----10.0.225.255

Note: The first usable customer IP address in this range is 10.1.0.0.

This exposure exists all code levels.

The customer will be required to re-configure the host IP's so they will not conflict with the internal IP's used by the SL8500/SL3000 libraries.

References

<NOTE:1014452.1> - SL8500 - Host IP Address Conflict

Attachments

This solution has no attachment