跳转到主内容

nis.server.not.available、由于网络连接问题描述

Views:
10
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas<a>2009538763</a>
Last Updated:

适用场景

  • ONTAP 9
  • NIS 

问题描述

  • NIS服务器与EMS日志中的以下事件断开连接
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.
  • 此时将显示受NIS域制约的状态 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 在 RPC client creation failure event"设置和重新创建NIS配置后显示
 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.