Welcome to Knowledge Base!

Applies to

• SAN
• FlexPod

Description

A LUN Network Address Authority (NAA) number is a globally unique identifier for a LUN. The NAA number can be used to determine a LUN's serial number and vice versa.

Procedure

Data ONTAP operating in 7-Mode or clustered Data ONTAP 8.3 or later include a LUN command to obtain the LUN serial number in the hexadecimal format:

lun serial -x /vol/test/lun

Serial (hex)#: 0x486e542d4f5a2f47694d684b

Take the example of a LUN with the following NAA number:

naa.60a98000486e542d4f5a2f47694d684b

Remove the NAA string and the first 8 characters. In this example, naa.60a98000 (this is one of the NetApp vendor identifiers).

The remaining value (486e542d4f5a2f47694d684b) is the hexadecimal string which, when converted from HEX to ASCII, will be the LUN serial number. There are many Web-based tools to convert HEX to ASCII and vice versa if you are using a version of Data ONTAP that does not have the lun serial -x command available.

486e542d4f5a2f47694d684b in HEX converts to an ASCII value of HnT-OZ/GiMhK

You can either use the output of the command lun show –v , or review the 'LUN CONFIGURATION' section of a storage system’s autosupport output to determine which is the LUN, based on the LUN serial number in the ASCII format.

The following is an example of the output of the lun show –v command:

Filer1> lun show -v /vol/test/lun
/vol/test/lun  5g (5368709120)(r/w, online, mapped)
Serial#: HnT-OZ/GiMhK
Share: none
Space Reservation: disabled
Multiprotocol Type: vmware
Maps: test=0

Note the LUN serial number above (HnT-0Z/GiMhK). The LUN with naa.60a98000486e542d4f5a2f47694d684b is /vol/test/lun.

Note: For more information on identifying disks in a VMware ESX environment, see VMware article 1014953.

NetApp NAA prefixes are as follows:

Applies to

• SnapDrive for windows
• Snap Manager for Oracle (SMO)

Issue

From the NetApp storage system console, the lun show –v command reports the LUN to be misaligned:

netappstorage> lun show -v

/vol/orabackup_precg1asdl01/orabackup/orabackup_precg1asdl01_new.lun

/vol/orabackup_precg1asdl01/orabackup/orabackup_precg1asdl01_new

.lun 400.0g (429523992576) (r/w, online, mapped)

Serial#: HndnCZmKv33k

Share: none

Space Reservation: disabled

Multiprotocol Type: linux

Maps: precg1asdl01=0

Occupied Size: 6.5g (6926499840)

Creation Time: Mon Sep 10 14:25:43 MDT 2012

Alignment: misaligned

Cluster Shared Volume Information: 0x0

LUN created with the correct OS type setting (Linux) uses the fdisk -u –l /dev/sdxx command from the UNIX host to get this information.

Example output :

Disk /dev/sdbh: 429.5 GB, 429523992576 bytes

255 heads, 63 sectors/track, 52219 cylinders, total 838914048 sectors

Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System

/dev/sdbh1 8 838898234 419449113+ 83 Linux

Cause

Solution

Applies to

• ONTAP 9.1 and earlier

Issue

When running the metrocluster check command while in the switchover state, some checks return warnings:

ClusterA::> metrocluster  check show
Last Checked On: 4/21/2016 07:34:32

Component           Result
------------------- ---------
nodes               warning
lifs                ok
config-replication  warning
aggregates          ok
clusters            ok
5 entries were displayed.

ClusterA::> metrocluster check node show
Last Checked On: 4/21/2016 07:34:32

Node                  Check                                Result
--------------------- ------------------------------------ ---------
ClusterA-01
node-reachable                       ok
metrocluster-ready                   ok
local-ha-partner                     ok
ha-mirroring-on                      ok
ha-mirroring-op-state                ok
symmetric-ha-relationship            ok
remote-dr-partner                    ok
dr-mirroring-on                      warning
dr-mirroring-op-state                warning
symmetric-dr-relationship            ok
remote-dr-auxiliary-partner          ok
symmetric-dr-auxiliary-relationship  ok
storage-failover-enabled             ok
has-intercluster-lif                 ok
node-object-limit                    ok
automatic-uso                        not-applicable

ClusterA::> metrocluster check config-replication  show -instance
Enabled: true
Running: true
Recovery Steps: -

Remote Heartbeat: ok
Last Heartbeat Sent: 4/21/2016 08:20:32
Last Heartbeat Received: 4/21/2016 08:19:57
Recovery Steps: -

Storage Status: ok
Storage In Use: Cluster-wide Volume: MDV_CRS_1fa20d6af0df11e5942100a0985bb98a_A
Storage Remarks: -
Recovery Steps: -

Vserver Streams: warning
Recovery Steps: Run the "metrocluster vserver show" command for more details.

Cluster Streams: warning
Recovery Steps: Contact technical support for assistance.

Applies to

• ONTAP 9
• MetroCluster

Issue

• Aggregate creation fails with error
  Error: command failed: An aggregate already uses <duplicate aggr name> as name

Applies to

• MetroCluster
• ONTAP 9

Description

This Article describes how to create unique aggregate names if accidently duplicate aggregate names got created.

Procedure