The NIS domain bound status shows "Invalid Domain" on some nodes and "success" on other nodes
Applies to
- ONTAP 9
- NIS
- NFS
Issue
The NIS domain bound status shows "Invalid Domain" on one node and "success" on other node
- EMS logs:
cdot_vsim5::> event log show -event nis*
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
9/24/2021 13:07:42 node1 ERROR nis.server.not.available: None of the NIS servers configured for SVM 'svm1' can be contacted.
9/24/2021 13:07:21 node1 ERROR nis.server.inactive: 10.216.41.39 NIS server configured for SVM 'svm1' cannot be contacted.
9/24/2021 13:07:21 node1 ERROR nis.server.inactive: 10.216.41.26 NIS server configured for SVM 'svm1' cannot be contacted.
9/24/2021 13:07:21 node2 INFORMATIONAL nis.server.active: SVM 'svm1' has successfully bound to the 10.216.41.26 NIS server.- Nis-domain bound status shows invalid domain
cdot_vsim5::> nis-domain show-bound-debug -vserver svm1
Bound Bound
Vserver Domain NIS Server Status
------------- ------------------- ----------------- -------------------
svm1 naslab.local 10.216.41.26 Invalid domain
svm1 naslab.local 10.216.41.39 Invalid domain
2 entries were displayed.NOTE: It might show status as success. To confirm if NIS is working for all nodes use the "Getxxbyyy " command to validate. Refer to addition info section