SL8500/SL3000 - Maintenance Port-1A Attachment Procedures

Asset ID:	1-71-1019383.1
Update Date:	2011-04-04
Keywords:

Solution Type Technical Instruction Sure

Solution 1019383.1 : SL8500/SL3000 - Maintenance Port-1A Attachment Procedures

Applies to:

Sun StorageTek SL8500 Modular Library System - Version: Not Applicable and later [Release: N/A and later ]
Sun StorageTek SL3000 Modular Library System - Version: Not Applicable and later [Release: N/A and later]
All Platforms
Checked for relevance on 4-Apr-2011.

Goal

Library engineering has released Port 1A on the HBC & HBCR card for SDP direct attachment and for local maintenance support. This was previously released for the SL3000 and is now approved for use with the SL8500.

Words of caution:
Read the instructions carefully and use only the range of IP addresses specified; installation of a conflicting IP address on the remote PC could hang the library. Also do not install on a network with other devices; example do not install on a customer network, Drive LAN used for maintenance, or an additional Library complex.

Solution

Overview
The preferred SDP attachment is to port 1A for a private LAN connection to address some customer’s concerns with network security. If necessary this port can be temporarily disconnected from SDP for direct local maintenance support to allow access via the SLConsole or SSH on the below mentioned addresses. There is also a port typically configured on the SDP switch to attach to all available LANs; typically it is the last port on the switch. If SDP is not installed and 1A has not been activated, you can permanently activate the port via the following procedure:

Procedure to Enable HBC(R) Port_1A for Local Maintenance Support if not already activated to support SL3000/SL8500 SDP or SL8500 ILC multi-library communications:

-Login to the CLI port on the HBC(R) card with service id and password.
-Take library offline via the accessState cli command.
-Enable the ILC interface via config ILC enable command.
-Put library back online via accessState online command.
-Reboot library via reboot x,0,0,0,0 <x=library id>
-Configure local PC for non-conflicting ip address on same subnet; example 10.0.11.60 with subnet 255.255.255.0.
-Login via cross-over cable to port_1A at address:
SL3000
code levels < 2.81 10.0.11.1
code 2.81 or greater 10.0.11.1 or 10.0.11.201
SL8500
code levels < 6.0 10.0.11.x <x=library id>
code levels 6.0 or greater 10.0.11.20x <x=library id>
General Notes:
-SL3000 @ code 3.0 to set the sdpAlias it may be necessary to use the following sequence if the alias was previously set:
1) config complexId set 3 <obtain value of complexid from SDP support> <if set to 3 it will create complexid of 5; example 10.5.11.1>
2) accessState offline 1,0,0,0,0
3) config ilc disable
4) config ilc enable
5) accessState online 1,0,0,0,0
-The Library Controller can generate more than one IP address by the use of aliases. The config complexid set command generates an alias for use with SDP. Contact SDP support for the proper alias to be configured for SDP.
-SL3000 code 3.0 and SL8500 code 6.x Port_1A generates an alias address of 10.0.11.201 and is not configurable. The IP address is 10.0.11.202 for Library Id_2 etc for the SL8500.
-SL3000 code greater than 3.0 and SL8500 greater than 6.x the 4th octet will be a single digit for the SDP alias using the config complexid set command. An example; set=3 will generate 10.5.11.1
Redundant Electronics Notes:
- The active HBC card will be at alias 10.0.11.2XX address.
- The A side HBC card will be at the 10.0.11.XX address.
- The B side HBC card will be at the 10.0.11.1XX address.
-Be careful not to configure the remote PC with a conflicting address on the ILC; do not use the address ranges below:
Reserved for ILC communication:
10.0.11.1 - 10.0.11.32
10.0.11.101 - 10.0.11.132
10.0.11.201 - 10.0.11.232
Reserved for SDP:
10.0.11.62
-Listed below are available/open addresses:
10.0.11.33 - 10.0.11.100 (except 10.0.11.62)
10.0.11.133 - 10.11.200
10.0.11.233 - 10.11.254
-Thus an available address to use for the remote pc is 10.0.11.60.

Q&A since release of this procedure:
Q1). If you have a couple of SL8500s with PTPs, are we allowed to plug the PC into the hub used for the PTP connections?
A1). Yes the ILC switch; of course you would use a straight cable to attach to the switch.

Q2). If yes, I suspect that the first SL8500 will be IP address 10.0.11.201. What would the IP address for the second SL8500? Would it be 10.0.11.202?
A2). Yes; That is correct.

Q3). I thought Port 1A for SL8500 had already been approved for maintenance and SDP using
10.0.11.201. since the complex was released.
A3). No, the SL8500 1A maintenance connection was just approved within the last few of weeks.

Q4). If there are multiple SL8500 ACS connected to SDP, how do I connect to the desired subsystem?
A4). If an alias is assigned to port 1A for SDP attachment use the IP address of the alias. An alias is typically assigned when more than one ACS is connected to the same SDP site server. SDP support should be able to provide the alias IP address if needed. Example; two ACS's attached to the same SDP site server, the ACS1 libraries would be configured to use an IP alias of 10.3.11.201 for port 1A <10.0.11.201>

<CLI command example to enable Port 1A; case sensitive>

SL3000> accessState offline 1,0,0,0,0
requestId

   requestId 7201

   Device 1,0,0,0,0

   State offline

   Done

   Failure Count 0

   Success Count 1
COMPLETED

SL3000> config ilc enable

   requestId

   requestId 7401

   Ilc Astate enable

   Success           true

   Done

   Failure Count 0

   Success Count 1
COMPLETED

SL3000> accessState online 1,0,0,0,0
requestID

SL3000> reboot 1,0,0,0,0
requestId

   requestId 7201

   Device 1,0,0,0,0

   State online

   Done

   Failure Count 0

   Success Count 1
COMPLETED


SL8500 SL3000 SDP Maintenance Port 1A Attachment guidelines Private LAN connection SL Console

Change History
Authors intent is for this content to be available to internal and partners. Changed the Visibility from Contract to Internal. Changed visibility of statements from internal to external. Moved text from add'l Internal Comments statement in to body of doc. Minor typo corrections. Ready to publish ... after much ado! ;)

Attachments

This solution has no attachment