Dell PowerVault NX3610 User Manual - Page 95

LUNs must be discovered and formatted., If the issue is due to uneven number of LUNs

Page 95 highlights

Workaround • Uneven number of LUNs are mapped to the host group. • LUN size is below the minimum required size. • Less than minimum number of required LUNs. If wrong SAN IPs are used while running the NAS IDU: 1. Verify that the MD discovery IP used while running the NAS IDU is on the same subnet as one of the two SAN IPs configured on your controllers. 2. To verify MD discovery IP, log in to your NAS Manger IP using CLI and run the following command:system maintenance luns configuration iscsi-view This command shows the MD discovery IP. If the IP is not in the same subnet as the IPs configured for your SAN, change the MD discovery IP to one of the subnets defined on your controller's SAN A and B. If wrong IQNs are used while defining hosts in MDSM, verify that the IQNs displayed in MDSM match the controller IQNs. To verify the controller IQNs: To change the discovery IP in the CLI, run the following command: system maintenance luns configuration iscsi-set -iSCSIDiscoveryIPs none none After the command is complete, refresh the host port identifiers. You can now run the configuration wizard from the NAS Manager again. 1. Compare if the IQNs displayed in MDSM are the same as the ones under the Mappings tab in the hosts section in the NAS Manager. 2. If there is a mismatch, correct the IQNs used for the hosts in MDSM and try formatting the system. The LUNs must be discovered and formatted. If the issue is due to uneven number of LUNs: 1. If an error is encountered, verify that even number of LUNs are mapped to the host group. An odd number of LUNs is not supported. LUNs have to grow in pairs starting from 2 to 16. 2. If uneven LUNs are used, correct the count by adding or removing a LUN. 3. Try to format the system. If the LUN size is below minimum requirements: 1. Verify that the LUNs are larger than the minimum required size of 125 GB. 2. If the LUNs are less than 125 GB, change LUN size to meet or exceed the minimum required size. 3. Try to format the system. If the LUN count is below the minimum requirements: 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117

Uneven number of LUNs are mapped to the host
group.
LUN size is below the minimum required size.
Less than minimum number of required LUNs.
Workaround
If wrong SAN IPs are used while running the NAS IDU:
1. Verify that the MD discovery IP used while running
the NAS IDU is on the same subnet as one of the two
SAN IPs configured on your controllers.
2. To verify MD discovery IP, log in to your NAS
Manger IP using CLI and run the following
command:
system maintenance luns
configuration iscsi-view
This command shows the MD discovery IP.
If the IP is not in the same subnet as the IPs configured for
your SAN, change the MD discovery IP to one of the
subnets defined on your controller's SAN A and B.
If wrong IQNs are used while defining hosts in MDSM,
verify that the IQNs displayed in MDSM match the
controller IQNs. To verify the controller IQNs:
To change the discovery IP in the CLI, run the following
command:
system maintenance luns configuration
iscsi-set -iSCSIDiscoveryIPs <IP
Address> none none
After the command is complete, refresh the host port
identifiers. You can now run the configuration wizard from
the NAS Manager again.
1. Compare if the IQNs displayed in MDSM are the
same as the ones under the
Mappings
tab in the
hosts section in the NAS Manager.
2. If there is a mismatch, correct the IQNs used for the
hosts in MDSM and try formatting the system. The
LUNs must be discovered and formatted.
If the issue is due to uneven number of LUNs:
1. If an error is encountered, verify that even number of
LUNs are mapped to the host group. An odd number
of LUNs is not supported. LUNs have to grow in pairs
starting from 2 to 16.
2. If uneven LUNs are used, correct the count by
adding or removing a LUN.
3. Try to format the system.
If the LUN size is below minimum requirements:
1. Verify that the LUNs are larger than the minimum
required size of 125 GB.
2. If the LUNs are less than 125 GB, change LUN size to
meet or exceed the minimum required size.
3. Try to format the system.
If the LUN count is below the minimum requirements:
95