Verify Communication with the Name Service Master

Skip this procedure if the client specified the name service, NIS or NIS+, during network install.

1. As root, at label ADMIN_LOW, check to see that you can ping the name service master.

   # ping name-service-master

2. Check to see that you can rup the name service master.

   # rup name-service-master

   If the rup(1) command succeeds, you may proceed. If it fails, debug your network setup until the rup command succeeds.

   ---

   Note -

   If you have added a client that was not initially on the master, you must add it to the master and assign it a template. On the master, the ping and rup commands must work to contact the new client.

   ---

Summary

These client files must be compatible with the name service master files:

• /etc/security/tsol/label_encodings

• /etc/security/tsol/tnrhtp

The client's local tnrhdb(4) file must have the IP address and host type of the NIS+ master (or the IP address and host type of the subnet), the client's static routers, and the client.

In addition, the client's address and name, the NIS+ master's name and address, and the static routers' names and addresses must be in the local hosts database.