The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The WatchDog is responsible for bootstrapping Prime Provisioning and starting the necessary set of server processes. In addition, the WatchDog monitors the health and performance of each server to ensure it is functioning properly. In the event of a software error that causes a server to fail, the WatchDog automatically restarts the errant server.
The WatchDog is a background daemon process that is automatically installed as part of the installation procedure for Prime Provisioning. After the installation procedure has completed, WatchDog is started automatically. You can execute the startwd command to run the WatchDog after the installation. The WatchDog can be configured to automatically start any time the machine is rebooted.
In addition to the commands that are specified in this chapter, in the product you can choose Administration > Control Center > Hosts and from there you can start, stop, restart, and view log files for the individual Prime Provisioning servers.
This chapter provides the description, syntax, and arguments (listed alphabetically) for the following WatchDog commands:
This section provides the description and syntax for the startdb command.
Go to PRIMEP_HOME and execute the following command:
The startdb command has no arguments and starts the database.
The location of startdb is: < Prime Provisioning Directory>/bin.
Note Do not run startdb in the background. Do not enter startdb &.
This section provides the description and syntax for the startns command.
The startns command starts the name server. The orbd process provides the name server functionality. orbd (from JDK) is required, but startwd starts it if it is not already running. The startns and stopns commands deal with orbd.
Go to PRIMEP_HOME and execute the following command:
The startns command has no arguments and starts the name server.
The location of startns is: < Prime Provisioning Directory>/bin.
This section provides the description and syntax for the startwd command.
The startwd command starts the WatchDog and all Prime Provisioning processes. The startwd command includes the functionality of startdb (see the “startdb Command” section) and startns (see the “startns Command” section). Executing this command is a necessary procedure and occurs automatically as part of the installation. Use this startwd command after issuing a stopwd command to restart the WatchDog.
If for some reason the Prime Provisioning host is stopped, either inadvertently or by issuing the stopwd command, it can be restarted by using the startwd command.
Go to PRIMEP_HOME and execute the following command:
The startwd command has no arguments and starts the WatchDog only for the machine where it is executed.
The location of startwd is: < Prime Provisioning Directory>/bin
Note Do not run startwd in the background. Do not enter startwd &.
This section provides the description and syntax for the stopall command.
The stopall command stops the database, name server, and WatchDog on the machine on which it is run. The stopall command includes the functionality of stopdb -y (see the “stopdb Command” section), stopns -y (see the “stopns Command” section), and stopwd -y (see the “stopwd Command” section). Normally this is only necessary before installing a new version of Prime Provisioning.
Go to PRIMEP_HOME and execute the following command:
The location of stopall is: < Prime Provisioning Directory>/bin.
This section provides the description and syntax for the stopdb command.
Go to PRIMEP_HOME and execute the following command:
-y
indicates not to prompt before shutdown. If -y is not specified, you are prompted with the following message: “Are you absolutely sure you want to stop the database?” You are then prompted to reply yes or no.
The location of stopdb is: < Prime Provisioning Directory>/bin.
This section provides the description and syntax for the stopns command.
The stopns command stops the name server. The startns and stopns commands deal with orbd.
Go to PRIMEP_HOME and execute the following command:
-y
indicates not to prompt before shutdown. If -y is not specified, you are prompted with the following message: “Are you absolutely sure you want to stop the nameserver?” You are then prompted to reply yes or no.
The location of stopns is: < Prime Provisioning Directory>/bin.
This section provides the description and syntax for the stopwd command.
The stopwd command stops the WatchDog and all Prime Provisioning processes other than the name server and the database.
Go to PRIMEP_HOME and execute the following command:
-y
indicates not to prompt before shutdown. If -y is not specified, you are prompted with the following message: “Are you absolutely sure you want to stop the watchdog and all of its servers? Other users may be using this system as well. No activity (for example: collections, performance monitoring, provisioning) occurs until the system is restarted.” You are then prompted to reply yes or no .
The location of stopwd is: < Prime Provisioning Directory>/bin .
Note Before running the wdclient command in Prime Provisioning, you need to source the environment variable with the following command: “source $PRIMEF_HOME/bin/vpnenv.sh”.
This section provides the description, syntax, and options (listed alphabetically) for the wdclient subcommands. These subcommands are diagnostic tools. This section also describes the column format of the output of each of the subcommands.
Note The location of wdclient is: <Prime Provisioning Directory>/bin.
The following are the wdclient subcommands:
– Information Produced: Name Column
– Information Produced: State Column
– Information Produced: Gen Column
– Information Produced: Exec Time Column
– Information Produced: Success Column
– Information Produced: Missed Column
Note If you enter wdclient -help, you receive a listing of all the wdclient subcommands.
This section provides the description and syntax for the wdclient disk subcommand.
The wdclient disk subcommand gives the disk space statistics for the directories where Prime Provisioning is installed.
This section provides the description and syntax for the wdclient group <group_name> subcommand.
The wdclient group <group_name> subcommand lists the servers in the specified server group. Server groups provide a convenient way to start or stop a group of servers with a single command.
<group_name> is the name of a server group chosen from the list displayed by the wdclient groups command.
This section provides the description and syntax for the wdclient groups subcommand.
The wdclient groups subcommand lists all the active server groups.
This section provides the description and syntax for the wdclient health subcommand.
The wdclient health subcommand indicates whether all the servers are stable.
This section provides the description and syntax for the wdclient restart subcommand.
The wdclient restart subcommand restarts one or more servers. Any dependent servers are also restarted.
Note It is not necessary to restart servers in a properly functioning system. The wdclient restart command should only be run under the direction of Cisco Support.
wdclient
restart
[ all | <server_name> |
group
<group_name> ]
where you can choose one of the following arguments:
all is all servers. This is the default if no argument is specified.
<server_name> is the name of a server chosen from the list displayed by the wdclient status command. See Table 6-1 , “ Servers and Their Functions ,” for server descriptions.
group
<group_name> where, <group_name> is the name of a server group chosen from the list displayed by the wdclient groups command.
This section provides the description and syntax for the wdclient start subcommand.
The wdclient start subcommand starts one or more servers. Other servers that depend on the specified server(s) might also start.
Note It is not necessary to stop and start servers in a properly functioning system. The wdclient start command should only be run under the direction of Cisco Support.
wdclient
start
[ all | <server_name> |
group
<group_name> ]
where you can choose one of the following arguments:
all is all servers. This is the default if no argument is specified.
<server_name> is the name of a server chosen from the list displayed by the wdclient status command. See Table 6-1 , “ Servers and Their Functions ,” for server descriptions.
group
<group_name> where, <group_name> is the name of a server group chosen from the list displayed by the wdclient groups command.
This section provides the description, syntax, and information produced for the wdclient status subcommand.
The wdclient status subcommand lists all the servers and their states. See Table 6-1, “ Servers and Their Functions ,” for server descriptions. See Table 6-2, “ Valid States ,” for the list of all the states.
wdclient
[ -poll
<seconds> ]
status
-poll
<seconds> is an optional parameter. <seconds> is the number of seconds. A number other than zero indicates that when new status data is available it is displayed every <seconds> seconds, where <seconds> is the specified number of seconds. The default -poll value is zero (0), which shows the status just once.
The Name column provides the name of each of the servers. Table 6-1 provides a list of the servers and a description of the function that each server provides.
|
|
---|---|
Executes various Prime Provisioning traffic engineering computations, such as tunnel repairing. |
Note The processes that no longer exist includes dispatcher, lockmanager, scheduler, and worker.
The State column provides the current state of the server. Table 6-2 provides a description of each of the states in normal progression order.
The Gen column provides the generation of the server. Each time the server is started, the generation is incremented by 1.
The Exec Time column provides the date and time the server was last started.
The Success column provides the number of successful heartbeats since the server was last started. Heartbeats are used to verify that servers are functioning correctly.
The Missed column provides the number of missed heartbeats since the server was last started.
A few missed heartbeats could simply indicate the system was busy. However, more than a couple of missed heartbeats per day could indicate a problem. See the logs to diagnose the reason.
Three missed heartbeats in a row is the default for restarting the server.
This section provides the description and syntax for the wdclient stop subcommand.
The wdclient stop subcommand stops one or more servers. Other servers that depend on the specified servers also stop.
Note It is not necessary to stop servers in a properly functioning system. The wdclient stop command should only be run under the direction of Cisco Support.
wdclient
stop [ all | <server_name> |
group
<group_name> ]
where you can choose one of the following arguments.
all is all servers. This is the default if no argument is specified.
<server_name> is the name of a server chosen from the list displayed by the wdclient status command. See Table 6-1 , “ Servers and Their Functions ,” for server descriptions.
group
<group_name> is the name of a server group chosen from the list displayed by the wdclient groups command.