Cisco Network Registrar

A. Complete these steps:

1. In the DNS tab for the scope, enter the proper DNS zone names and the IP address of the server that you wish to update, as shown here: Figure 1

   

2. If the DNS server is a CNR server, go to the DHCP tab for each DNS zone that receives updates and enter the IP address of the servers from which the zone accepts DNS updates (see Figure 2). If you run DNS/DHCP on the same system, use the loopback address in both locations. Figure 2

   

A. You can configure your network in a variety of ways—from simple (where a server has a backup server) to more complicated arrangements. These are three typical configurations:

A. Complete these steps:

1. Main Server:
   1. Issue the dhcp enable failover command to enable failover for this DHCP server.
   2. Issue the dhcp set failover-backup-server=backupserver.example.com command to specify the name of the backup server.
   3. Issue the server dhcp reload to reload the server.
2. Backup Server:
   1. Issue the dhcp enable failover command to enable failover for this DHCP server.
   2. Issue the dhcp set failover-main-server=mainserver.example.com command to specify the name of the main server.
   3. Issue the server dhcp reload command to reload the server.

A. Complete these steps:

1. Main Server-a:
   1. Issue the dhcp enable failover command to enable failover for this DHCP server.
   2. Issue the dhcp set failover-backup-server=server-c.example.com command to specify the name of the backup server.
2. Main Server-b:
   1. Issue the dhcp enable failover command to enable failover for this DHCP server.
   2. Issue the dhcp set failover-backup-server=server-c.example.com command to specify the name of the backup server.
3. Backup Server-c: You can specify only one default main server. If you have more than one main server, list the scopes of the other servers individually. This example enables failover for each scope on the two main servers, and designates the main server for each scope.
   1. Issue the scope scope1 set failover=scope-enabled command to enable failover for scope1.
   2. Issue the dhcp set failover-main-server=server-a.example.com command to specify the name of the main server.
   3. Repeat Steps 1 and 2 for scope2 and scope3.
   4. Isuse the scope scope4 set failover=scope-enabled command to enable failover for scope4.
   5. Issue the dhcp set failover-main-server=server-b.example.com command to specify the name of the main server.
   6. Repeat Steps 4 and 5 for scope5 and scope6.

A. Complete these steps:

1. Server-a:
   1. Issue the scope scope1 set failover=scope-enabled command to enable failover for this scope.
   2. Issue the scope scope1 set failover-backup-server=server-b.example.com command to specify the name of the backup server.
   3. Repeat Steps 1 and 2 for scope2 and scope3.
   4. Issue the scope scope4 set failover=scope-enabled command to enable failover for this scope.
   5. Issue the scope scope4 set failover-main-server=server-b.example.com command to specify the name of the main server.
   6. Repeat Steps 4 and 5 for scope5 and scope6.
2. Server-b:
   1. Issue the scope scope1 set failover=scope-enabled command to enable failover for this scope.
   2. Issue the scope scope1 set failover-main-server=server-b.example.com command to specify the name of the main server.
   3. Repeat Steps 1 and 2 for scope2 and scope3.
   4. Issue the scope scope4 set failover=scope-enabled command to enable failover for this scope.
   5. Issue the scope scope4 set failover-backup-server=server-b.example.com command to specify the name of the backup server.
   6. Repeat Steps 4 and 5 for scope5 and scope6.

A. In CNR 3.5.x and earlier, you must stop the CNR server agent and then restart it after you change the setting. After you exit nrcmd, you must stop and restart the services in order for the change to take effect. The log options are actually command line options to the server process itself, so you need a new incarnation of the process to have these changes take effect. A stop and restart or reload of a specific server is actually only a pause and resume of the server process (in order to reread internal configuration changes) and does not create a new incarnation of the server process.

To stop any related processes on Solaris, issue these commands:

> /etc/init.d/aicservagt stop
> ps -leaf | grep nwr
> kill -9 pid pid
 ... 
!--- All processes are noted in the ps output.

On Windows NT, issue the net stop "AIC Server Agent 2.0" command.

A. Complete these steps:

1. Create a file (biglogs.txt) with these lines:

   [ config/clusters/1/trampolines/1/servers/1 ]
   load_args = str:"-A nlogs=5 -A logsize=10000000"
   [ config/clusters/1/trampolines/1/servers/2 ]
   load_args = str:"-A nlogs=5 -A logsize=10000000"
   [ config/clusters/1/trampolines/1/servers/4 ]
   load_args = str:"-A nlogs=5 -A logsize=10000000"
   

   The servers are internally designated as shown here:
   • servers/1 —DNS server—name_dns_1_log.x files
   • servers/2 —DHCP server—name_dhcp_1_log.x files
   • servers/3 —UI—logs are not required
   • servers/4 —TFTP server—file_tftp_1_log.x files
   (The x file extension stands for 01, 02, and so on, incremented up to the total number of files you specify.)
2. Run the mcdadmin utility to include the file:

   > mcdadmin -N admin -P password -o -i biglogs.txt
   

3. Restart the Network Registrar service:
   • On Solaris, issue the /etc/init.d/aicservgt start command.
   • On Windows NT, issue the net start "AIC Server Agent 2.0" command.