Skip to main content
NetApp Knowledge Base

nis.server.not.available due to a network connection issue

  1. Last updated
  2. Save as PDF
Views:
288
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NIS 

Issue

  • The NIS server disconnected with the following event from the EMS log
Mon Jun 29 01:17:11 +0200 [node1: ypbind: nis.server.not.available:error]: None of the NIS servers configured for SVM 'svm1' can be contacted.
  • The NIS domain bound status shows Could not connect to server
Cluster::*> vserver services name-service nis-domain show-bound-debug  -vserver svm1
                                  Bound             Bound
Vserver       Domain              NIS Server        Status
------------- ------------------- ----------------- -------------------
svm1          ntap.local          10.10.10.20       Could not connect to server
 
  • ypbind log show "RPC client creation failure event" after deleting and recreating the NIS configuration
 Mon Jun 29 2023 10:42:09 +02:00 [kern_ypbind:debug:6427] ypbind.cc 2850 write_bindings: Successfully wrote binding to /mroot/etc/cluster_config/vserver/.vserver_1/config/name_services//var/yp/binding/NTAP.local.2.
Mon Jun 29 2023 10:42:17 +02:00 [kern_ypbind:warning:6427] yp_ping.cc 331 __yp_ping_proto: RPC client creation failed for Vserver 1 and NIS server 10.10.10.20. Error = 14
Mon Jun 29 2023 10:42:25 +02:00 [kern_ypbind:warning:6427] yp_ping.cc 331 __yp_ping_proto: RPC client creation failed for Vserver 1 and NIS server 10.10.10.20. Error = 14
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.