Skip to main content
ONTAP FlexArray

LUN IDs for the same LDEV do not match

Contributors netapp-chikkusu
PDFs

A logical device (LDEV) must be mapped to the same LUN ID on all storage array ports over which it must be visible to ONTAP systems. The storage errors show output identifies the LDEVs whose LUN IDs do not match.

ONTAP does not allow you to assign array LUNs to an ONTAP system if the LUN IDs do not match.

Storage errors show message

HIT-1.4 (4849544143484920443630303035323430303132): This Array LUN is using multiple LUN IDs.  Only one LUN ID per serial number is supported.

Explanation

One of the following errors was made during storage array configuration:

  • The LDEV is presented to the same FC initiator port of the ONTAP system from multiple target ports and the LUN IDs are not consistent.

  • The LUN IDs of two LDEVs are swapped.

    In this case, an error is reported for each array LUN.

  • Different LUN IDs for the same LDEV are used when mapping the LDEV to storage array ports that are presenting the LDEV to the ONTAP system.

Note

This error is more likely to occur on storage arrays on which each port is configured separately, for example, on Hitachi storage arrays. On some storage arrays, for example IBM storage arrays, ports are not configured separately.

  • The Volume Set Addressing setting is inconsistent on the ports on which the LUN is mapped.

    On an EMC Symmetrix storage array, the problem would be that the Volume Set Addressing setting varies on the channel director ports.

Problem scenario

This scenario discusses the case of inconsistent LUN IDs as it applies to most storage arrays. See Volume Set Addressing is inconsistent section for a discussion of this same error message in the context of misconfigured Volume Set Addressing.

Volume Set Addressing is inconsistent

Assume that the storage array administrator creates a new LDEV Z. The LUN ID for LDEV Z is supposed to be LUN 3. However, the administrator presents LDEV Z as LUN 3 on storage array controller port 1A and as LUN 4 on storage array controller port 2A, as the following illustration shows:

This graphic is described in the surrounding text.

To fix this problem, the same LUN ID must be assigned to an LDEV on all ports to which the LDEV is mapped. In this example, the LDEV should be presented as LUN ID 3 on both ports.

Troubleshooting and problem resolution

To fix the problem, the storage array administrator must remap the LUN, using the correct LUN ID. You can use ONTAP commands to obtain the details that you need to provide information about the problem to the storage administrator.

  1. Review the storage errors show output to identify the array LUN whose LUN IDs do not match.

    When the LUN IDs for the same LDEV do not match, the output identifies the serial number of the LDEV with the problem. For example:

    mysystem1a::> storage errors show
Disk: HIT-1.4
UID: 48495441:43484920:44363030:30353234:30303132:00000000:...
----------

HITACHI_DF600F_1
----------
HIT-1.4 (4849544143484920443630303035323430303132): This Array LUN is using multiple LUN IDs.  Only one LUN ID per serial number is supported.
    Note

    THE UID in this example is 48495441:43484920:44363030:30353234:30303132:00000000:00000000:00000000:00000000:00000000. It is truncated in the example because of space.

  2. Obtain details about which LUN IDs are being used for the same LDEV by entering the following command: storage disk show arrayLUNname

    The storage disk show output for this example shows the following:

    mysystem1a::> storage disk show -disk HIT-1.4
                  Disk: HIT-1.4
        Container Type: unassigned
            Owner/Home: -  / -
               DR Home: -
                 Array: HITACHI_DF600F_1
                Vendor: HITACHI
                 Model: DF600F
         Serial Number: D600020C000C
                   UID: 48495441:43484920:44363030:30353234:30303132:00000000:...
                   BPS: 512
         Physical Size: -
              Position: present
Checksum Compatibility: block
             Aggregate: -
                  Plex: -
Paths:
                     LUN  Initiator Side  Target Side
Controller Initiator ID   Switch Port     Switch Port      Acc Use  Target Port     TPGN...
---------- --------- -------------------- ----------------- --- ---  --------------- ----
mysystem1a   0c       4  vgci9148s76:1-2  vgci9148s76:1-9  AO  INU  50060e80004291c1  1
mysystem1a   0a       3  vgbr300s89:1     vgbr300s89:9     S   RDY  50060e80004291c0  2
mysystem1b   0c       4  vgci9148s76:1-4  vgci9148s76:1-9  AO  INU  50060e80004291c1  1
mysystem1b   0a       3  vgbr300s89:3     vgbr300s89:10    S   RDY  50060e80004291c2  2

Errors:
HIT-1.4 (4849544143484920443630303035323430303132): This Array LUN is using multiple LUN IDs.  Only one LUN ID per serial number is supported.
Note

THE UID in this example is 48495441:43484920:44363030:30353234:30303132:00000000:00000000:00000000:00000000:00000000. It is truncated in the example because of space.

By looking at the LUN IDs in the Paths section of the storage disk show output, you can see that LUN IDs 3 and 4 are both being used for this LDEV.

  1. Determine which LUN ID is not correct for the LDEV.

    LUN ID 4 is the incorrect LUN ID in this example.

  2. In ONTAP, use the storage path quiesce command to quiesce the incorrect path for the array LUN.

    The following example shows the options to add to the storage path quiesce command for the path that is being quiesced—​LUN ID 4 on initiator 0c.

    storage path quiesce -node mysystem1a -initiator 0c -target-wwpn 50060e80004291c1 -lun-number 4

    The storage path quiesce command temporarily suspends I/O to a specific array LUN on a specific path. Some storage arrays require ceasing I/O for a period of time when an array LUN is to be removed or moved.

    After the path is quiesced, ONTAP can no longer see that LUN.

  3. Wait one minute for the storage array's activity timer to expire.

    Although not all storage arrays require ceasing I/O for a period of time, it is good practice to do so.

  4. On the storage array, remap the LUN to the target port by using the correct LUN ID, LUN ID 3 in this scenario.

    The next time the ONTAP discovery process runs, it discovers the new array LUN. Discovery runs every minute.

  5. After ONTAP discovery is complete, run storage array config show in ONTAP again to confirm that there is no longer an error.