Document ID: 13391
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
CNR 3.5.x and Earlier
CNR 5.0.x and Above
Stopping and Starting the Network Registrar Service
CNR 6.0.x and Earlier
CNR 6.1
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document provides the process for changing the log size and the number of logs for the DNS, DHCP, and TFTP servers in Cisco Network Registrar. The procedure is different depending on the CNR version used:
-
For CNR 3.5.x and earlier the mcdadmin utility is used.
-
For CNR 5.0.x and above, the CLI server [DNS|DHCP|TFTP] serverLogs command is used.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document applies to all CNR versions.
Note: In CNR 6.1 the process of changing the number and size of the log files for the DNS, DHCP and TFTP servers only applies to the Local Cluster, not the Regional Server.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
CNR 3.5.x and Earlier
Follow these steps to change the log size and the number of logs for the DNS, DHCP, and TFTP servers in Cisco Network Registrar:
-
Stop the Network Registrar service.
-
Create a file named biglogs.txt containing 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 follows:
-
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
Note: The x file extension is 01, 02, and so on, and increments up to the total number of files you specify.
-
-
Run the mcdadmin utility to include the file:
> mcdadmin -N admin -P password -o -i biglogs.txt
-
Restart the Network Registrar service.
CNR 5.0.x and Above
Follow these steps to change the log size and the number of logs for the DNS, DHCP, and TFTP servers in Cisco Network Registrar:
-
Start the nrcmd program and check your current values as follows:
nrcmd> server DNS serverLogs show 100 Ok nlogs=3 logsize=100000
Note: The serverLogs action is new to the server command in Network Registrar 5.0 and is not available in prior releases. You can set from 1 to 100 log files and a range of file sizes from 10 KB to 500 MB.
-
Perform the same show command for the DHCP and TFTP servers. Then, adjust the settings as follows:
nrcmd> server DNS serverLogs nlogs=5 logsize=10M nrcmd> server DHCP serverLogs nlogs=5 logsize=10M nrcmd> server TFTP serverLogs nlogs=5 logsize=10M 100 Ok
-
For changes to take effect, save (or exit).
-
Restart the Network Registrar service.
Stopping and Starting the Network Registrar Service
CNR 6.0.x and Earlier
Follow these steps to stop or start the Network Registrar Service:
-
Solaris, Linux—/etc/init.d/aicservagt [stop|start]
-
Windows—From a DOS command line
-
Type net [stop|start]
-
Select "AIC Server Agent 2.0"
-
CNR 6.1
Follow these steps to stop or start the Network Registrar Service:
-
Solaris, Linux—/etc/init.d/nwreglocal [stop|start]
-
Windows—From a DOS command line, type net [stop|start] nwreglocal
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for Network Management |
| Network Infrastructure: Network Management |
| Virtual Private Networks: Network and Policy Management |
Related Information
- CLI Reference Guide "server" Command
- Troubleshooting DHCP Problems in Cable Networks using Cisco Network Registrar Debugs
- Technical Support - Cisco Systems
| Updated: Oct 26, 2005 | Document ID: 13391 |
