Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1007176.1
Update Date:2011-03-31
Keywords:

Solution Type  Technical Instruction Sure

Solution  1007176.1 :   SL3000/SL8500 - General Information on Replacing HBC/HBCR Card  


Related Items
  • Sun StorageTek SL3000 Modular Library System
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Tape>Libraries - SL-Series
  •  

PreviouslyPublishedAs
209885


Applies to:

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

Goal

General Information on Replacing HBC and HBCR Card:

-The HBC card from spares should only have the boot-strap code loaded into memory which will make the card fully functional but no auto-updates will occur. Due to the potential of having unwanted versions of code on the new HBC card we need to control the auto update process.

- This necessitates having the target SL8500 code preloaded on the SL Console remote client to upgrade the target code after installing the HBC card.

- The Library Controller maintained volume id and location data base is loaded on the HBC(R) card and after installing a new HBC card it will be necessary to complete a full physical audit via SLC.

- The library configuration is housed on the HBK card but best practice is to verify the library configuration on the new HBC card.

- The new HBC card will have a different MAC address and some customer network's routing tables can take a period of time before the new MAC address is populated throughout the network.

Solution

Steps to Follow:

HBC Replacement Caution:

There might be spare HBC cards in stock that have pre-installed boot strap-code below 3.97.  These cards do not have the "U-Boot" module installed and are not compatible with code versions at or above 3.97.

Spare HBC cards should have "Boot Strap" code installed; thus no versions should be listed in the Code Activate SLC screen.  If the code is below 3.97 you MUST FIRST LOAD AND ACTIVATE FRS_3.98b code.  Currently there is no method to determine the current code level installed on the spare HBC card.  If you suspect the card has been in stock longer than 3 years <2008> use 3.98b as bridge code before upgrading to current code levels.

Note: Code version 3.98b is the ONLY code level you can use as a bridge code that will install the U-Boot module and successfully allow an upgrade to current code levels.

Please contact Tape Hardware support if you are unsure on how to proceed.

1. Note current code version in SL Console under "Tools -> System Detail -> Properties -> Library Controller.
2. Disable all robotics with the front ERS switch (this prevents wasting time downgrading/upgrading code to the H-Bots, HBZ(s), and PTPs or risking a problem activating a downlevel code)
3. Power off ECM cardcage with rocker switches
4. Remove and replace the HBC or HBCR card.
5. Power on ECM cardcage.
6. If you suspect the code is lower than 3.97, load and activate 3.98b code. Reboot library to this version.
7. Load desired current code and activate/boot; follow the code upgrade instructions in the targeted code level. This will not take a long time because robotics are powered off.
8. Once the desired code is booted on the HBC(R), release the ERS switch and wait for all mechanisms to update code and become ready.
9. Run a full library physical audit via SLC.

Failure to follow the above precautions can cause an extended outage and another HBC card replacement.



Storagetek, SL8500 Modular Library System, Replacing HBC Card, CRCM
Previously Published As 90810



Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback