Sun StorageTek[TM] 5000 Series NAS: Adding new LUNs to NAS cluster gateway system

Asset ID:	1-71-1018302.1
Update Date:	2017-06-12
Keywords:

Solution Type Technical Instruction Sure

Solution 1018302.1 : Sun StorageTek[TM] 5000 Series NAS: Adding new LUNs to NAS cluster gateway system

Applies to:

Sun Storage 5320 NAS Gateway - Version All Versions and later
Sun Storage 5310 NAS Gateway System - Version All Versions and later
All Platforms

Goal

On a Sun StorageTek[TM] 5000 Series NAS cluster gateway system, LUN ownership has to be established before any operation can be done to the new LUNs.

The NAS-OS for this family of NAS product writes a signature to the LUN to manage the LUN ownership.

Solution

On a Sun StorageTek[TM] 5000 Series NAS cluster gateway system the software to manage attached raid arrays is disabled as soon as the Gateway License is installed.

To create and map new LUNs for the Gateway Cluster provided by legacy storage you have to use storage array configuration tools designed for the specific array.

For example:

Sun StorageTek 6920/6540/6140/6130 uses CAM or Santricity.
Sun StorageTek 9900 series uses Storage Navigator or Hi-Command software.

Apply storage LUN masking and switch zoning to limit other hosts from accessing these new LUN(s).
Rule of thumb is, one target port and one initiator port per zone.
In the terminology of Sun StorageTek[TM] 5000 Series NAS, a LUN will be referenced as disk.
It is not immediately obvious that when adding new LUN in a gateway NAS that all resources are required to be on one head only.

Steps to make LUNs usable on your Sun StorageTek[TM] 5000 Series NAS:

Select one head of your cluster and telnet or ssh to this head to add the LUN(s) via CLI menu
Move all resources and services to this head with take over
Scan for new disks in menu D. Disk & Volumes
Press D to switch to menu and then 9 to scan for new disks, the new LUN(s) will show up in the list with volume name set to no partition table
Leave this menu item with 'ESC for Menu'
Assign ownership of the LUN to either head 1 or head 2 with U. Failover/Move LUN and modify lun owner, this will also reduce the number of displayed path.
CLI menu -> Failover/Move LUN -> modify lun owner
-> select the LUN -> select owner (Head1 or Head2) and save

If a LUN has no owner then user can not do anything to the system, and also failover and recovery might have problem if the LUN count is not the same on both heads.
Before user attempt to use the new LUNs, or do failover and recovery, make sure all LUNs have ownership assigned and both heads see all the new LUNs. Do not go any further until this is achieved.
Initialize the LUN to make it usable for volumes
CLI menu -> Disk -> select disk -> option 1 Initialize partition table
CLI is now showing disk size correctly.
Redistribute ownership of the resources with failback, both heads are active again.

Checking availability of LUN(s)

From both Heads, do another disk scan, User should see all new LUNs with proper LUN ownership.

Exit the NAS CLI menu and run "disk" and "luninfo" command to confirm new disks. User can now configure volumes on these disks as required.

Shell command luninfo will give the WWN of the LUN for that disk ISP number - if different ISP disks (on the NAS) show the same WWN, then they are really just different paths to the same backend LUN.

***Checked for relevance on 02-Nov-2016***

References

<NOTE:1006899.1> - Sun StorageTek[TM] 99x0 System: Identifying LUNs on NAS OS gateway
<NOTE:1008235.1> - NAS OS LUN stamp behaviour for new luns

Attachments

This solution has no attachment