|
|
Through Network Registrar's graphical user interface (GUI) ntwkreg, or command line interface (CLI) nrcmd, you control your servers' operations. The nrcmd commands that control the server include the following.
The commands handle administration and affect the way you can view Network Registrar activity.
The admin command allows you to configure administrators for the cluster. You can choose any string for the administrator's name. Network Registrar uses the password to authenticate the names. If you create an administrator without a password, Network Registrar cannot authenticate the name and thus will deny that user access to the cluster.
Use the admin create command to create an administrator and associated password. For example, to create the administrator bob with the password of xyz, type:
nrcmd> admin bob create password=xyz
If you want to enter a password and not have Network Registrar display the password on your screen, create an administrator and do not supply a password. Then use the enterPassword command to enter a password and prevent Network Registrar from echoing it on the screen. Network Registrar prompts you to verify the password before it accepts it.
Use the admin enterPassword command to associate a password with an administrator. For example, to cause nrcmd to prompt you for a password for administrator bob, type:
nrcmd> admin bob enterPassword
Use the admin set command to change an existing password. For example, to change bob's password to abc, type:
nrcmd> admin bob set password=abc
Exiting Network Registrar's user interface does not affect your network servers' or your hosts' ability to request leases or access the Internet.
To exit Network Registrar's CLI, use the exit command. Network Registrar writes all your unsaved changes to the database. If Network Registrar is unable to save your changes, it displays the same error code as if you had used the save command.
Use the exit command to quit Network Registrar's command line interface when you are in interactive mode.
nrcmd> exit
The server command allows you to affect the behavior of the server. After you have used the server command or any other time you have changed the server's configuration, you need to reload the server.
Administration includes:
Use the server start command to start the specified server. For example, to start Network Registrar's DNS server, type:
nrcmd> server DNS start
Use the server stop command to stop the specified server. For example, to stop Network Registrar's DHCP server, type:
nrcmd> server DHCP stop
Use the server reload command to reload the specified server. For example, to reload Network Registrar's DHCP server, type:
nrcmd> server DHCP reload
Network Registrar stops the server you have selected, updates the database with the new configuration information, and restarts the server.
Use the server getHealth command to display the specified server's health. For example, to display Network Registrar's DHCP server's health, type:
nrcmd> server DHCP getHealth
Use the server getStats command to display the specified server's statistics. For example, to display Network Registrar's DHCP server's statistics, type:
nrcmd> server DHCP getStats
Use the report command to display the IP address usage for specified servers. For example, to display Network Registrar's DHCP server's address usage, type:
nrcmd> report
Use the server getRelatedServers command to display the connection status between the main and backup server. For example, to display Network Registrar's DHCP servers , type:
nrcmd> server getRelatedServers
You can use the server setDebug and server unsetDebug commands to set or unset the debugging level and the location of the debug messages. You can specify either MLOG or WINDOW as locations. The default is MLOG.
Use the server setdebug command to specify the debugging level. For example, to set the DNS debugging level to 5, type:
nrcmd> server DNS setDebug D=5
The Network Registrar Web GUI lets you login to your Network Registrar servers and run four different types of reports. These reports are:
Posted: Thu Nov 18 12:23:56 PST 1999
Copyright 1989-1999©Cisco Systems Inc.