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-1007164.1
Update Date:2009-04-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  1007164.1 :   Sun StorageTek[TM] 5000 Series NAS arrays: Validating reasons for a lack of awareness of the NAS server to the underlying luns  


Related Items
  • Sun Storage 5210 NAS Appliance
  •  
  • Sun Storage 5220 NAS Appliance
  •  
  • Sun Storage 5310 NAS Appliance
  •  
  • Sun Storage 5320 NAS Gateway/Cluster System
  •  
  • Sun Storage 5320 NAS Appliance
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
  •  

PreviouslyPublishedAs
209869


Description
The NAS server may at times 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.


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 Technical Instruction: <Document: 1007165.1> 

1. Refer to the Technical Instruction: <Document: 1008205.1> Verifying 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 and 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 Sun Support engineer to handle this.

5. If these are ISCSI luns, then see document # <Document: 1008016.1> Renaming NAS volume containing iSCSI luns causes data contained on the iSCSI luns to become inaccessible.
Also have a look at Technical Instruction: <Document: 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 Technical Instruction: <Document: 1012815.1> FC Controller (HBA) "isp" Numbering and LUN Path on Sun StorageTek[TM] 5320 NAS Heads.
See also Technical Instruction: <Document: 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 Technical Instruction: <Document: 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 Technical Instruction: <Document: 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 Technical Instruction: <Document: 1005474.1> and contact Sun Support.



Product
Sun StorageTek 5320 NAS Gateway/Cluster System
Sun StorageTek 5320 NAS Appliance
Sun StorageTek 5310 NAS Gateway/Cluster System
Sun StorageTek 5310 NAS Appliance
Sun StorageTek 5220 NAS Appliance
Sun StorageTek 5210 NAS Appliance

Internal Comments
To access the documents internally,

This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-nas-domain@sun.com

The Knowledge Work Queue for this article is KNO-STO-NAS.

Please refer to http://sunsolve.central.sun.com


luns.missing, NAS, 5210, 5310, 5320, 5220, 5310C, 5320C, normalized, volume, enclosure, tray, audited
Previously Published As
90566

Change History
Date: 2007-10-04
User Name: 71396
Action: Approved
Comment: Performed final review of article.
Updated trademarking.
Publishing.
Version: 5
Date: 2007-10-01
User Name: 71396
Action: Accept
Comment:
Version: 0

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