Dell PowerVault NX3500 Administrator's Guide - Page 184

Workaround, Mappings, Configuration Utility

Page 184 highlights

Workaround If wrong SAN IPs are used while running the PowerVault NAS Configuration Utility: 1 Verify that the MD discovery IP used while running the PowerVault NAS Configuration Utility 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: Kjd This command shows the MD discovery IP. 3 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: 1 Compare if the iqns displayed in MDSM is 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 one 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. 184 Troubleshooting

  • 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
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198

184
Troubleshooting
Workaround
If wrong SAN IPs are used while running the PowerVault NAS
Configuration Utility:
1
Verify that the MD discovery IP used while running the
PowerVault NAS Configuration Utility 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:
Kjd
This command shows the MD discovery IP.
3
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:
1
Compare if the iqns displayed in MDSM is 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 one 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.