Specific Subnet Clients Cannot Access The Nas Cluster Solution; Troubleshooting Dns Configurations; Determining The Iqn Of The Nas Cluster Solution Controllers Using Cli - Dell PowerVault NX3600 Administrator's Manual

Specific Subnet Clients Cannot Access The NAS Cluster Solution

Description
Cause
Workaround

Troubleshooting DNS Configurations

Description
Cause
Workaround

Determining The IQN Of The NAS Cluster Solution Controllers Using CLI

Description
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.
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.
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