Downloads |
 Feedback
|
Table Of Contents
Starting the WSA Control System
Monitoring the WSA Control System
Stopping the WSA Control System
Starting and Stopping the WSA Discovery Server
Starting the WSA Discovery Server
Stopping the WSA Discovery Server
Loading a Network from a Live Network
Control System Configuration
Introduction
The WSA Control System consists of the servers: WatchDog, Scheduler, and Dispatcher that need to be running for end-to-end connection provisioning and network auditing.
This chapter explains how to start, monitor, and stop the WSA Control System in the following sections:
•
Starting the WSA Control System
•
•
•
Note
Starting the WSA Control System
Follow these steps to invoke the WSA Control System:
Step 1
Step 2
$WSA_start
Note
WSA_start is the main shell script that runs and configures the WSA control system server processes.
This script invokes the following three processes.
Note
1
WSA_Dispatcher -v &
This process talks to the network via a Control Processor Module. This process is responsible for network control message flow to and from WSA and from and to the network.
The -v flag indicates verbose mode such that all information is logged into a file logfile within the same directory.
2
WSA_Scheduler -i -s +sched1 -c 30 &
This process sends tasks to the dispatcher at the appropriate date and time. This process also polls the dispatcher periodically for notification of task status and annotates the tasks in the WSA database.
The interval between task progress checks is 30 seconds, as supplied by the -c option.
3
WSA_WatchDog -u -l -v -i 300 -z 180 &
When the WatchDog process is invoked with the previous flags, tasks are generated for connection provisioning and the task completion status is updated.
The interval between creating tasks is five minutes, as supplied by the -i option (default is 20 minutes).
The interval between task status updates is three minutes, as supplied by the -z option (default is five minutes).
The above options on the WatchDog process indicate that the WatchDog process runs every five minutes to pick up tasks to be provisioned and every three minutes to update any pending task status.
Monitoring the WSA Control System
Follow these steps to monitor a running WSA Control System:
Step 1
Step 2
$/opt/CSCOwsa/bin/WSA_psThis script displays all the WSA server processes.
The output should list at least one WSA_Scheduler, WSA_Dispatcher, and WSA_WatchDog process.
Stopping the WSA Control System
Follow these steps to perform a graceful shutdown of the WSA server processes:
Step 1
Step 2
$/opt/CSCOwsa/bin/WSA_kill
Caution
Starting and Stopping the WSA Discovery Server
The WSA Discovery Server runs on the SV+ Solaris Server and starts requests from WSA for discovering SV+ managed networks. This server, wsadisc, needs to be running for WSA_Probe, WSA_Loader, and WSA_Audit to work.
Starting the WSA Discovery Server
To start the WSA Discovery Server, telnet to the SV+ Solaris server as user svplus.
Then execute the following:
ps -ef | grep wsadisc
If the output from the previous command contains the words scotty wsadisc at the end, as shown next, then the WSA Discovery Server is running on that machine.
svplus 1007 984 0 14:23:19 pts/6 0:00 scotty wsadisc
If you do not see the previous line, then you need to start the WSA Discovery Server as follows:
cd ~svplus/wsa
source .wsarc
cd bin
wsadisc
The following message appears:
WSA Discovery Server: Setting Server port to 5000
*************************************
* WSA Discovery Server 1.1 *
* (c) Cisco Systems Inc. 1998, 1999 *
*************************************
Note
Stopping the WSA Discovery Server
To stop the WSA Discovery Server, telnet to the SV+ Solaris server and kill the scotty wsadisc process by either interrupting (Ctrl-C) or using the UNIX kill command.
Discovering SV+ Networks
To discover one or more networks managed by SV+ using WSA, do the following steps:
Step 1
Step 2
Step 3
For example, to generate the network probe file from Network Network1 using ultra30qa as the SV+ database host with user name svplus and password svplus, run WSA_Probe as follows:
WSA_Probe -n Network1 -a ultra30qa -u svplus -p svplus -R public -W private -o probe.dat
Note
Loading Networks
WSA allows users to load a network from a file created by WSA_Probe or directly from a network using an SV+ database. The following information is loaded: nodes, cards within nodes, ports, trunks, and connections.
Loading a Network from a File
To load a network from a file, do the following:
Step 1
Step 2
Step 3
WSA_Loader -i probe.dat.Network1
If you supply a network name using the -n option, then all network data entries contained in the probe file are mapped to the new network name within the WSA database.
Launch the WSA Administration application on the PC and authorize yourself to view the network and region created by WSA_Loader. Then, launch the WSA Explorer application to view the loaded network.
Loading a Network from a Live Network
To load a network from a live network using a SV+ database, do the following:
Step 1
Step 2
Step 3
Step 4
WSA_Loader
Launch the WSA Administration application on the PC and authorize yourself to view the network and region created by WSA_Loader. Then, launch the WSA Explorer application to view the loaded network.
