Dell PowerVault NX3610 User Manual - Page 96

Associating LUN Names To Virtual Disks, NAS IDU Failed To Discover Any Controllers

Get Dell PowerVault NX3610 PDF manuals and user guides View all Dell PowerVault NX3610 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 96 highlights

1. Verify that more than one LUN is mapped to the host group. The minimum number of LUNs required is 2. 2. If the number of LUNs is less than 2, add LUNs to meet the required minimum LUN count of 2. 3. Try to format the system. Associating LUN Names To Virtual Disks Description Workaround Determining which LUNs in the NAS Manager are virtual disks in the Modular Disk Storage Manager. Open the NAS Manager web interface and go to Cluster Management → Maintenance → Add Luns. This page displays all LUNs that the NAS cluster solution has access to (assigned to the NAS cluster solution host group). Each LUN can be identified using its world-wide name. In the NAS Manager web interface, the LUN's world-wide name is preceded by a prefix. Open MDSM and go to the Logical tab and click Virtual Disk. The virtual disk world-wide identifier is displayed in the Properties pane. This workaround enables you determine which virtual disks are assigned to the NAS file system. NAS IDU Failed To Discover Any Controllers Description Cause Workaround NAS IDU failed to discover any controllers. IPV6 may not be enabled on your workstation. Enable IPV6 support on your management workstation. Attach Operation Fails Description Workaround The operation to attach the controller to NAS cluster fails. • Connect a keyboard and monitor to the controller that failed the attach operation, and view the error message to determine why the attach operation failed. • Verify the following: - While the controller was detached, the IP assigned to it on the client network was not allocated to another host. While the controller is detached, it loses its identity, including IP addresses. When it is attached, its identity is applied back to the controller, including the IP addresses. - Verify the default gateway is in the Primary subnet by using the NAS Manager. In Cluster Management → 96

  • 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
1. Verify that more than one LUN is mapped to the host
group. The minimum number of LUNs required is 2.
2. If the number of LUNs is less than 2, add LUNs to
meet the required minimum LUN count of 2.
3. Try to format the system.
Associating LUN Names To Virtual Disks
Description
Determining which LUNs in the NAS Manager are virtual
disks in the Modular Disk Storage Manager.
Workaround
Open the NAS Manager web interface and go to
Cluster
Management
→
Maintenance
→
Add Luns.
This page
displays all LUNs that the NAS cluster solution has access
to (assigned to the NAS cluster solution host group). Each
LUN can be identified using its world-wide name. In the
NAS Manager web interface, the LUN's world-wide name
is preceded by a prefix.
Open MDSM and go to the
Logical
tab and click
Virtual
Disk
. The virtual disk world-wide identifier is displayed in
the
Properties
pane. This workaround enables you
determine which virtual disks are assigned to the NAS file
system.
NAS IDU Failed To Discover Any Controllers
Description
NAS IDU failed to discover any controllers.
Cause
IPV6 may not be enabled on your workstation.
Workaround
Enable IPV6 support on your management workstation.
Attach Operation Fails
Description
The operation to attach the controller to NAS cluster fails.
Workaround
•
Connect a keyboard and monitor to the controller
that failed the attach operation, and view the error
message to determine why the attach operation
failed.
•
Verify the following:
–
While the controller was detached, the IP
assigned to it on the client network was
not allocated to another host. While the
controller is detached, it loses its identity,
including IP addresses. When it is
attached, its identity is applied back to the
controller, including the IP addresses.
–
Verify the default gateway is in the
Primary
subnet by using the NAS
Manager. In
Cluster Management
→
96