![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1333009.1 : SL8500/SL3000 - Netmask Not Being Set With 3.00/7.01 Firmware
In this Document
Oracle Confidential (PARTNER). Do not distribute to customers
Applies to:Sun StorageTek SL3000 Modular Library System - Version: Not ApplicableSun StorageTek SL8500 Modular Library System - Version: Not Applicable and later [Release: N/A and later] Information in this document applies to any platform. SymptomsSignificant problem has been found on the 2.6 kernel based library codes for the SL8500 and SL3000 codes. If planning on upgrading to SL8500 7.01 or SL3000 3.0 you must first set the subnet mask.Note the following warning on the subnet mask IP configuration if it is not set before you upgrade code. If there is no subnet mask set prior to the upgrade from 2.4 kernel based code (2.8x or 6.0x or below) to 2.6 kernel based code (3.00 or 7.01) the system will be left in an unusable state. There will be no access to the library via Ethernet or Serial port. To verify the netmask settings use CLI: "network print". Example: SL8500> network print Host Name: gulibtst02b Gateway: 10.79.252.1 Domain Name: Primary Dns: Secondary Dns: 2B IP Address: 10.79.255.195 2B Subnet Mask: 255.255.252.0 2B MAC Address: 00:10:4f:0a:ce:00 COMPLETED Note: The SLC display shows the current netmask and not necessarily the configured netmask and should not be used for verification. ChangesFirmware upgrade.CauseCause:Error converting from IPv4 to IPv6 network compatible files. SolutionNone currently available; will be addressed in a future code level. A valid subnet mask must be verified prior to the upgrade to avoid the issue. If a library is upgraded without a netmask, the following can be done to bring the library back to a usable state. 1. Replace the HBC or HBCR card.2. Load and activate 2.81/6.05 (or below). 3. Configure the netmask. 4. Upgrade to SL3000 3.60 or greater or SL8500 7.60 or greater. Note: The above procedures assume that the replacement HBC/HBCR card will have 2.4 kernel code. As of 8/1/2011 all spare controller cards will have 2.4 kernel code. Going forward that may not always be the case. Attachments This solution has no attachment |
||||||||||||
|