Dell PowerVault NX3610 User Manual - Page 89

Specific Subnet Clients Cannot Access The NAS Cluster Solution, Troubleshooting DNS Configurations

Page 89 highlights

Specific Subnet Clients Cannot Access The NAS Cluster Solution Description Cause Workaround Users (new or old), accessing from specific network(s), cannot access the NAS cluster solution. This issue is due to a conflict between the users' subnet addresses and the NAS system internal network's address. The NAS system routes the response packets to the wrong network. 1. Check the internal network addresses of the NAS system and verify if there is a conflict with the problematic client network addresses. 2. If a conflict exists, manually change the conflicting NAS internal network address using either the NAS Manager or CLI. Troubleshooting DNS Configurations Description Cause Workaround Unable to connect to the NAS cluster solution using the system name and/or unable to resolve host names. Probable causes may be: • Unable to ping system using Fully Qualified Domain Name (FQDN). • Unable to connect to the NAS Manager using system name. 1. Verify that the client IP information is set correctly. 2. Verify that the NAS cluster solution controller is configured to the correct DNS server. 3. Contact DNS server administrator to verify the DNS record creation. Determining The IQN Of The NAS Cluster Solution Controllers Using CLI Description Workaround Determining the IQN of the NAS cluster solution controllers using CLI. Using an ssh client and the NAS Management VIP, log in to the NAS cluster solution CLI as an admin. From the command line type the following command: system maintenance luns iscsiconfiguration view 89

  • 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

Specific Subnet Clients Cannot Access The NAS Cluster Solution
Description
Users (new or old), accessing from specific network(s),
cannot access the NAS cluster solution.
Cause
This issue is due to a conflict between the users' subnet
addresses and the NAS system internal network's
address. The NAS system routes the response packets to
the wrong network.
Workaround
1. Check the internal network addresses of the NAS
system and verify if there is a conflict with the
problematic client network addresses.
2. If a conflict exists, manually change the conflicting
NAS internal network address using either the NAS
Manager or CLI.
Troubleshooting DNS Configurations
Description
Unable to connect to the NAS cluster solution using the
system name and/or unable to resolve host names.
Cause
Probable causes may be:
Unable to ping system using Fully Qualified
Domain Name (FQDN).
Unable to connect to the NAS Manager using
system name.
Workaround
1. Verify that the client IP information is set correctly.
2. Verify that the NAS cluster solution controller is
configured to the correct DNS server.
3. Contact DNS server administrator to verify the DNS
record creation.
Determining The IQN Of The NAS Cluster Solution Controllers Using CLI
Description
Determining the IQN of the NAS cluster solution
controllers using CLI.
Workaround
Using an ssh client and the NAS Management VIP, log in
to the NAS cluster solution CLI as an admin.
From the command line type the following command:
system maintenance luns iscsi-
configuration view
89