Reasons for the incorrect number of LUNs in array LUN groups

Example of storage array config show output

The number of array LUNs in each LUN group appears in the storage array config show output, as the following example shows:

mysystem1::> storage array config show

               LUN     LUN
Node           Group   Count Array Name     Array Target Port  Initiator
------         ------ ----- -------------- -------------------- ---------- 
mysystem1        0      50   DGC_RAID5_1     201A00a0b80fee04     0a
                                             202A00a0b80fee04     0c

Explanation

The most likely reasons that an array LUN you expected to be in a LUN group is missing are as follows:

• The array LUN is not mapped to the ONTAP system.
• A mapping error is made that resulted in the array LUN being in the wrong LUN group.

  For example, the host group configuration might be incorrect.

• The storage array is still in the process of initializing and making the array LUNs available (transitional state).
• The ONTAP LUN scanner has not yet discovered the LUNs (transitional state).

Resolving the issue

1. If the array LUN has not been mapped to the ONTAP system, the storage array administrator has to map it.

   The process for mapping array LUNs to hosts varies among storage arrays.

2. If the array LUN has been mapped to the ONTAP system, check zoning and the host group configuration.
3. After the issue is fixed, run storage array config show again to confirm that the issue is fixed.