![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1020835.1 : SL8500/SL3000 - Pinging Component Addresses Inside the Library
PreviouslyPublishedAs 265708 Oracle Confidential (PARTNER). Do not distribute to customers Reason: Confidential for Partners and Oracle Support personnel
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 18-July-2011. GoalHow to ping addresses inside the library and what the addresses are.SolutionSteps to Follow Components inside the library can be pinged using the following instructions: Use the hostname of the device instead of the address. Examples are, hbb11, hbb12, hbb31, etc. Use the "libstate" CLI command to find out what the actual hostname is for the desired device. The numbers after the alpha characters can increment to 9 (hbb19) if bots have been added/changed since the last reboot. Use the output of the libstate command to determine the correct full hostname for the device. Some examples: HBZ modules - hbza, hbzb HBT card - hbta, hbtb (when it is there) PTPs - hbp1, hbp2 H-Bots - hbb11, hbb21 (initial hostnames of the left and right top rail bots after a reboot) H-Bots - hbb12, hbb21 - after replacement of the top left H-Bot without rebooting the SL8500 How to ping address inside the library, Pinging library components, libstate CLI command, Hostname of device, Host name Attachments This solution has no attachment |
||||||||||||
|