Skip to main content
NetApp Knowledgebase

Name services fail due to multiple default gateways with the same metric

Applies to

ONTAP 9

Issue

Check Active IQ if this impacts your systems

Possible symptoms include the following:

  • All CIFS clients per a particular Storage Virtual Machine (SVM) might be unable to access any shares.

Example:

Windows cannot access \<hostname>
Check the spelling of the name. Otherwise, there might be a problem with your network, To try to identify and resolve network problems, click Diagnose.

  • Unable to contact a domain controller while joining an SVM to the Active Directory Domain(AD).

  • NFS clients are unable to mount exports that include Hostnames instead of IP addresses.

  • Any protocol that relies on name services (LDAP, NIS, DNS) is susceptible.

Example:
Thu May 26 00:06:13 EDT [<NODENAME>: mgwd: dns.server.timed.out:warning]: DNS server <DNS_IP> did not respond to vserver = <VSERVER> within timeout interval.

EMS logs may include message which include the phrase: "No route to host"


Example:

[ 12] Failed to connect to <DNS_IP> for DNS: No route to host
[ 12] Failed to connect to <DNS_IP> for DNS: No route to host

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support