Sun Storage 5320 NAS Appliance
 
Sun Storage 5210 NAS Appliance
 
Sun Storage 5220 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 

PLA-Support>Sun Systems>DISK>NAS>SN-DK: SE5xxx NAS
 
.Old GCS Categories>Sun Microsystems>Storage - Disk>Network Attached Storage
 

Applies to:

Goal

Description
The NAS server may sometimes boot up without all the expected LUNs
This document will help determine the reasons for the NAS server's lack of awareness of the underlying LUNs.

Fix

Steps to Follow

As the NAS server boots up, it will attempt to discover luns on the backend storage through the HBA's.  After it has completely booted, if the expected luns are not seen, then check the logs to see if there are any error messages pertaining to those luns.

If there are no such messages then continue further or else have a look at Document ID 1007165.1 - Verifying reasons for unavailability of known LUNs on the Sun StorageTek[TM] 5000 Series NAS arrays.

1. Refer to the Document ID 1008205.1 - How to verify LUN Status on NAS

2. Check for any missing enclosures in the RAID -> Manage RAID option.  This will help in determining whether the LUNs that are not seen are newly added LUNs or existing LUNs.

3. If the LUNS missing or not seen are newly added luns, then check the status LEDs of the new enclosure.  Verify it was added in the prescribed method.  Please refer to the documentation for the procedure.

4. If all enclosures are seen but the drives or drive in an enclosure are not available for use and if they appear OK physically with a green status LED, then this is probably due to the fact that the drive contains information of a LUN it previously belonged to.  This needs to be reinitialized using NRM or sometimes even replaced.  Contact Oracle Support engineer to handle this.

5. If these are ISCSI LUNs, then see Document ID 1008016.1 - Renaming NAS volume containing iSCSI luns causes data contained on the iSCSI luns to become inaccessible.  Also have a look at Document ID 1005308.1 to understand the basics of iscsi for Windows.

6. If you are unable to communicate using the 'Manage RAID' option or the process is taking too long then:

6.1 Verify that the HBA's exist and seen by the NAS.  For details see Document ID 1012815.1 - FC Controller (HBA) 'isp' Numbering and LUN Path on Sun StorageTek[TM] 5320 NAS Heads.
See also Document ID 1006686.1 - Sun StorEdge[TM] 5310: Associating ISP with physical port position

If the following messages are seen   "Command failed 10 time(s) on adapter isp1 ..."  and the expected LUN is not seen by the user, then it means that it was unable to discover the LUNs through that
particular HBA.  Replace the HBA and/or FC cable and scan the disks using the option D (Disks and Volumes) on the telnet menu -> 9 - scan for new disks.

6.2 Verify that the cable connections between the HBAs and the Raid controllers are fine.  Confirm physical connectivity of the cables.  Please refer to the documentation for further details to check if it is done as per recommendations.

6.3 Verify that the Raid controllers are online and active.  Please refer to Document ID 1004366.1 - Verifying that the Raid controllers are online and active in a Sun StorEdge[TM] 5310/5210 and Sun StorageTek[TM] 5320/5220 NAS.

7 There is a possibility that an incorrect NVSRAM is used on the Raid controller. Refer to Document ID 1004239.1 - Sun StorEdge[TM] 5310/5320 NAS: 'lsi_menu' overview for Disk Array Maintenance in NAS OS 4.20 or higher.

8. If you are unable to collect support data using lsi_menu of the backend storage, then collect whatever data is possible using Document ID 1005474.1 - Sun StorageTek[TM] 5000 Series NAS: How to Collect data for troubleshooting and contact Oracle Support.

References

This solution has no attachment