| PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System) |
|
Contents
Index
|
| Appendix D Notice of supplemental information | > D.2 Trouble shooting | > D.2.1 Communication as expected cannot be performed (Common to IPv4 and IPv6) |
The following message is displayed and activation of a system or an interface hangs up.
|
ypbind[xxxx]: [ID xxxxxx daemon.error] NIS server not responding for domain "domain_name"; still trying |
When a system that a Redundant Line Control function works is set as an NIS client, occasionally not possible to connect NIS server temporarily due to the process to deactivate an interface executed by a Redundant Line Control function. In such a case, if set a netmask to an interface by an ifconfig command, occasionally the process to activate a system or an interface hangs up because an ifconfig command waits for the connection with NIS server to get a subnet mask.
Be sure to set as follows when using a Redundant Line Control function in the NIS environment.
To specify "files" first in /etc/nsswitch.conf to refer "netmasks".
|
netmasks: files |
or
|
netmasks: files [NOTFOUND=return] nis |
As to accessing NIS server, design a network not to use an interface that is the target of control in a Redundant Line Control function (activation/deactivation) as possible.
|
Contents
Index
|