|
|
This appendix describes the commands and processes used by CiscoWorks Blue Maps and SNA View, and contains the following major sections:
The core of the DLSw and RSRB applications is a set of daemons and database tables. This section lists the daemons, describes how to start and stop the daemons, and it describes the role of daemons in the operation of DLSw and RSRB Maps applications. (The database tables are described in the appendix "Database Tables.") The daemon names are shown in Table D-1.
| Daemon Name | Description |
|---|---|
cwbmonitord | DLSw and RSRB monitor daemon. |
cwbdlswpollerd | DLSw poller daemon. |
cwbrsrbpollerd | RSRB poller daemon. |
cwbtrapd | DLSw and RSRB trap daemon. |
You can start and stop each daemon using the Process Manager, as described in "Using Process Manager" or with the cwb start command shown here:
cd /opt/CSCOcb/bin
cwb start maps_daemon_command
Where:
maps_daemon_command is a Maps daemon startup command, as shown, in the following sections, for each Maps daemon.
1. Only one copy of any specific daemon can be running at a time on the same workstation.
2. A daemon can be stopped and restarted only by a user who has the correct permissions.
3. You really should use the Process Manager to start and stop daemons.
This section describes how to control the daemons that are common to both DLSw and RSRB; it contains the following subsections:
The monitor daemon saves the list of GUI clients (for example, RSRB and DLSW) in the database. When the monitor daemon is reset, it sends updates to the applications in this list.
If you start the monitor daemon with no options, it starts with default options using port 6000.
You can stop the monitor daemon to avoid automatic updates to displayed graphical maps.
Use the cwb start and cwb stop commands to start and stop the monitor daemon:
Command |
cwb {start | stop} cwbmonitord |
Optional Arguments -h |
Displays a help message. |
-v | Displays the version. |
-c | Starts with an empty client list. Without this option, the monitor daemon reestablishes the list of GUI application clients that were registered when it was last run. See the "Client List Table" section. |
-t sleep_time | Specifies the number of seconds the daemon waits from when it completes one cycle until it starts the next cycle. |
UDPport | Specifies the User Datagram Protocol port to which the monitor daemon listens for communication from the GUI client applications. The default is port 6000. If you want the monitor daemon to listen to a different port number, enter that number here. If you change the port number here, you must also change it in the runprocess script. |
The trap daemon (cwbtrapd) registers with the network management system's trap process to receive unsolicited status messages from routers. It should run at all times unless the routers are not configured to send traps. When a device generates a trap, the trap daemon updates device information in the database.
The trap daemon reports changes to the following states:
If you start the trap daemon with no options, it starts with default options. Use the cwb start and cwb stop commands to start and stop the trap daemon.
Command | |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
This section describes the RSRB daemons in the following subsections:
The RSRB poller daemon (cwbrsrbpollerd) continuously polls the MIBs in discovered routers for their ever-changing status. If you start the poller daemon with no options, it starts with default options. Use the cwb start and cwb stop commands to start and stop the RSRB poller daemon.
Command |
cwb start cwbrsrbpollerd [-h | -v] [PollerSleepTime] |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
PollerSleepTime | Specifies a slow polling timer value, which is the number of seconds the daemon can wait from when it completes one cycle until it starts the next cycle. The default PollerSleepTime is 600 seconds. |
The poller daemon queries the following MIB variables in known RSRB-enabled devices (those in the Devices table that are flagged "discovered"):
If a known RSRB-enabled (discovered) device does not respond to the poller's SNMP query, the poller daemon sets that device status to "Inactive." If the device responds with its current Peer table, the Peer table is updated in the database. The monitor daemon monitors the database and sends any changes to the GUI applications.
This section describes the DLSw daemons in the following subsections:
The DLSw poller daemon (cwbdlswpollerd) continuously polls the MIBs in discovered routers for their status. If you start the poller daemon with no options, it starts with default options. Use the cwb start and cwb stop commands to start and stop the DSLw poller daemon.
Command |
cwb start cwbdlswpollerd [-h | -v] [-P PollingSleepTime] [-C PollingSleepTime] [PollingSleepTime] |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
-P PollingSleepTime | Specifies the non-key-peer polling timer value in seconds; the number of seconds the poller waits from when it completes one cycle until it starts the next cycle. The -P option starts the poller daemon for non-key-peer polling and sets the sleep-time value. If you omit the -P PollingSleepTime value, the default is 600 seconds. |
-C PollingSleepTime | Specifies the key-circuit polling timer value, in seconds; the number of seconds the poller waits from when it completes one cycle until it starts the next cycle. The -C option starts the poller daemon for circuit polling and sets the sleep-time value. If you omit the -C PollingSleepTime value, the default is 1200 seconds. |
PollingSleepTime | This option starts the poller daemon for key-peer polling and sets the sleep-time value. If you omit the PollingSleepTime value, the default is 600 seconds. |
The following MIB variables are used by the DLSw poller daemon:
You can configure the DLSw application to poll DLSw routers for peer information and for circuit information at different intervals. For information about polling intervals, see the section "Using the CWBINIT Preferences File" in the CiscoWorks Blue Maps and SNA View User Guide. You can set the following polling intervals.
When you start the poller daemon from the command line, you can start the following polling timers by specifying them in hte runprocess script, as described in the section Changing Parameters on Process Calls.
The sleep-time values determine how many seconds the poller daemon waits after polling is complete before it starts polling again.
The APPN Poller Server provides polling of APPN devices for cwbsnamapsd. There is no reason to start this process on its own. If APPN is configured, AppnPollerServer becomes a prerequisite for cwbsnamapsd.
Command |
AppnPollerServer |
The APPN poller (or the APPN application, whichever is running) polls the following variables for local topology:
If the appn_pu_polling parameter in cwbinit is set to ON, the following MIB variables are also polled:
The first time a device is polled, the following MIB variables are polled:
For network topology polling, the following MIB variables are polled initially:
For network topology polling, the following variables are polled at each poll interval to detect changes in network topology:
If changes are detected, the initial variables are polled for the changed resources.
This section describes the host connection daemons used to process messages and commands between the workstation and the SNA mainframe computer.
Command |
cwb start cwbhcid [ -h | -v] domain_name |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
domain_name | Enter the name of the host domain. |
Command |
cwbhcmdd [-h | -v] domain_name |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
domain_name | Enter the name of the host domain. |
Command |
cwbhmond [-h | -v] domain_name |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
domain_name | Enter the name of the host domain. |
This section describes the cwb command script that you run from /opt/CSCOcb/bin to start the CiscoWorks Blue applications, and includes the following subsections:
The cwb command starts and stops the CiscoWorks Blue Process manager and Name servers. You must be the root user to start and stop servers.
Command |
cwb {start | stop} [pm | name] cwb start servers |
Syntax Description start |
Starts the specified process by the process_name. |
stop | Stops the specified process by the process_name. |
pm | Starts or stops the Process Manager server. The Process manager, in turn, starts all Maps and SNA View autostarted processes. |
name | Starts or stops the CiscoWorks Blue (corba osagent) name server, which is required for using the Process Manager and Message Logger. When Process manager starts, it automatically starts the name server. |
start servers | Starts all autostartable servers. |
The cwb start command can be used to start and stop the CiscoWorks Blue discovery processes. Each discovery process starts, discovers the devices, then stops.
To run these discovery processes periodically to automatically discover new devices, you should run the cwb start command as a UNIX cron job (a chronologically started job) job. Set the cron job to run at night or when system and network activity are low.
We do not recommend running discovery from the command line because you will not see a progress indicator until discovery is complete. Use the cwb start admin command to start the Administration application and run discovery from there.
Use the discovery processes to determine whether each IP device in your network is active and to verify which routers are enabled for each protocol. In addition to discovering the devices, the discovery process also sets the status and protocol fields in the Devices table.
If you have a dynamic network and expect to configure new or existing routers with DLSw, start the discovery process to ensure that the database used for your selected protocols reflects your current network topology.
When executed, the discovery process queries all IP devices in the database flagged "not discovered." A device is set to "not discovered" when one of the following occur:
If there is a network management system installed, the discover process can use the NMS database to synchronize the Maps database with the network management system's database. If not, the discover process requires a seed file to be specified to add new devices to the database.
Command |
cwb start discover_process [-r read_community_string [-s seed_file_name]] [-h] [-v] |
Syntax Description discover_process |
Specifies the name of the discover process to start: · cwbdlswdiscover discovers devices running the DLSw protocol. · cwbrsrbdiscover discovers devices running the RSRB protocol. · cwbappndiscover discovers devices running the APPN protocol. · cwbtn3270discover discovers devices running the TN3270 protocol. |
-r read_community_string | Specifies a global read community string for all devices in the seed file that do not specify a read community string. If all read community strings are the same, you can just put the device name in the seed file and specify the read community string on the command line. |
-s seed_file_name | Specifies a seed file. Replace seed_file_name with the seed file name. |
-h | Displays a help message. |
-v | Displays the version. |
If the device responds to the RSRB MIB variables (shown with an asterisk), the discovery daemon updates the RSRB Devices table to indicate that the node is an RSRB node. If the device does not respond to RSRB MIB, it is flagged as "not discovered."
For each device that is "not discovered," the discovery daemon queries the device to determine whether it is configured with following DLSw MIB variables. The variables shown with an asterisk (*) are unique to DLSw.
The cwb command starts and stops the CiscoWorks Blue processes.
Command |
cwb {start | stop} process_name cwb stop all |
Syntax Description start |
Requests the Process Manager to start a process using a process_name. |
stop | Requests the Process Manager to stop one or more processes. |
process_name | Specifies the process name of the process to stop or start. |
stop all | Requests the Process Manager to: · Stop all running CiscoWorks Blue processes, including all clients and servers. · Stop the Process Manager and Name servers. |
This section describes how to start and stop user applications with the cwb command, and contains the following main subsections:
The cwb start admin command starts the CiscoWorks Blue Administration application.
Command |
cwb start admin [-p portno] [-v] [-h] |
Syntax Description start |
Starts the specified application. |
admin | Starts the CiscoWorks Blue Administration application (cwbadmin), which lets you start and stop Maps and SNA View processes and discover network devices. |
[-p portno] | Specifies a port number for discovery work-in-progress information. The first discovery process spawned uses the specified port number or the default port number. The default is 57193. For each subsequent spawned discover process, the port number is increment by 1. Subsequent discover processes are spawned when you select a protocol (say RSRB) first and start discover, then select another protocol (say DLSw) and start discover again. The second discover process uses a port number 1 greater than the first. |
[-v] | Displays the version. |
[-h] | Displays a usage statement. |
The cwb start dlsw command starts the CiscoWorks Blue Maps DLSw Motif application.
Command |
cwb start dlsw [-u portno] [-p portno] [ -k | -g ] [-f device_name][ -v ] [ -h ] |
Syntax Description start |
Starts the specified user application. |
dlsw | Starts the DLSw GUI application, the DLSW executable, the DLSw poller daemon (cwbdlswpollerd), and the monitor daemon (cwbmonitord). |
-u portno | Specifies a port for socket communications with the monitor daemon. The runprocess script defaults to port 6000. If the monitor daemon has been changed to listen to another port, make the same change in this option in the script. |
-p portno | Specifies a port for socket communications with the discovery process when it is launched by the dlsw application. The runprocess script defaults to port 6011. If another application is using this port, you can specify another port with this option. |
-k | Starts with the key devices view. This is the default. |
-g | Starts with the global view. |
-f device_name | Starts with the focus view for the specified device. |
-v | Displays the version. |
-h | Displays a usage help statement. |
The cwb start rsrb command starts the CiscoWorks Blue Maps RSRB Motif application.
Command |
cwb start rsrb [-u portno] [-p portno] [-g] [-f device_name] [-v] [-h] |
Syntax Description start |
Starts the specified user application. |
rsrb | Starts the RSRB GUI application, the RSRB executable, the RSRB poller daemon (cwbrsrbpollerd), and the monitor daemon (cwbmonitord). |
-u portno | Specifies a port for socket communications with the monitor process. The script defaults to port 6000. If the monitor daemon has been changed to listen to another port, make the same change in this option in the script. |
-p portno | Specifies a port for socket communications with the discovery process when it is launched by the rsrb application. The script defaults to port 6001. If another application is using this port, you can specify another port with this option. |
-g | Starts with the global view. |
-f device_name | Starts with the focus view for the specified device. |
-v | Displays the version. |
-h | Displays a usage help statement. |
The cwb start appn command starts the CiscoWorks Blue Maps APPN Motif application.
Command |
cwb start appn [-f device_name [-r ead_community_string]] [-v] [-h] |
Syntax Description start |
Starts the specified user application. |
appn | Starts the APPN GUI application, the APPN executable, and the APPN poller server daemon (AppnPollerServer). |
-f device_name | Specifies the host name or IP address of an APPN node to be used as the network topology agent. You must either identify a network topology agent with this option or in the cwbinit file. If you do not name a network topology agent, the APPN poller will terminate. |
-r read_community_string | Specifies the read community string for the router specified by device_name. APPN uses the read_community_string when communicating with an APPN node. If you do not enter a read community string, the APPN application uses the default read community string specified in the cwbinit file or, if there is not one there, the default string "public." |
-v | Displays the version. |
-h | Displays a usage help statement. |
The cwb start MsgLogClient command starts the Message Log display application.
Command |
cwb start MsgLogClient |
Syntax Description start |
Starts the specified user application. |
MsgLogClient | Starts the Message Log client (viewer) application. |
The cwb start ProcMgrClient command starts the Process Manager display application.
Command |
cwb start ProcMgrClient |
Syntax Description start |
Starts the specified user application. |
ProcMgrClient | Starts the Process Manager client (viewer) application. |
The cwb kill all command kills all running CiscoWorks Blue processes and servers. You must be the root user to use the cwb kill all command.
Command |
cwb kill all |
The cwb show command displays information about the CiscoWorks Blue servers.
Command |
cwb show {versions | status} |
Syntax Description |
Displays the version information about all CiscoWorks Blue servers. |
Displays the current status of all CiscoWorks Blue servers and processes. |
The cwb command runs the suite of miscellaneous CiscoWorks Blue applications.
Command |
cwb {create seed | clear db | config | verify | tac} |
Syntax Description create seed [-s seedfile] |
Creates a seed file from the devices in the CiscoWorks Blue database. -s seedfile specifies the name of the seed file to create. If you omit this parameter, the seed file is named seed.file. |
Clears the CiscoWorks Blue Database. All data will be lost. To regenerate, discovery must be run for all protocols. You must be the root user to use the cwb clear db command. The cwb clear db command stops all clients and servers, clears the database, then restarts all servers. | |
Runs the cwbconfig application to configure CiscoWorks Blue. You must be the root user to use the cwb config command. | |
Runs the CiscoWorks Blue verification program to verify that you installed the applications correctly, and to check your configuration files and the database. | |
Runs the CiscoWorks Blue tac collection program to collect and zip all the information you will need when you call the Cisco TAC. You must be the root user to use the cwb tac command. |
This section describes the following utilities and commands:
The uninstall.sh command deinstalls Maps applications. After you enter the uninstall.sh command, it detects all the installed Maps files and asks you whether you want to delete them.
Command |
uninstall.sh |
To deinstall the installed Maps applications, use the following command:
cd /opt/CSCOcb/install
./uninstall.sh
The cgisnamaps process is a cgi-bin program that is started when a CWBlue web page is launched. It passes data between the web browser and cwbsnamapsd. There are no operands and it is not to be run by the user.
Commands |
cwb start cwbsnamapsd [-h | -v] [interval] cwb stop cwbsnamapsd |
Syntax Description -h |
Displays a help message. |
-v | Displays the version. |
interval | Specifies the number of seconds the daemon can wait from when it completes one cycle until it starts the next cycle. |
The runprocess command, in the $CWBROOT/etc directory, sets appropriate environment variables and then executes a command. You should not use runprocess directly, but you might want to edit the script to change selected arguments.
Command |
runprocess process_name |
Syntax Description process_name |
The name of the Maps process to be executed. |
Most CiscoWorks Blue processes and executables, by default, store Error, Warning, and Info messages in the message log. The Error and Info messages are logged automatically. A parameter in the /opt/CSCOcb/etc/runprocess script sets additional default values for the level of debugging messages that each process logs in the message log. At installation, each process is set to also log Warning messages. If you really want to change these default values, you can edit the STD_DBG_PARAM statements in /opt/CSCOcb/etc/runprocess.
For each CiscoWorks Blue process, there is an entry in /opt/CSCOcb/etc/runprocess that starts with a case statement. For example, the entry for the DLSw poller daemon (cwbdlswpollerd) looks like this:
case cwbdlswpollerd:
set STD_DBG_PARAM="-MLCenableFilters Warning"
set GIVEN_PARAM="${GIVEN_PARAM} ${STD_DBG_PARAM}"
set PARAMETERS="${PM_PARAM} ${ML_PARAM} ${ORB_PARAM} ${GIVEN_PARAM}"
eval exec $CWBROOT/dlsw/bin/cwbdlswpollerd $PARAMETERS
breaksw
Look at the highlighted line that contains the STD_DBG_PARAM statement. The -MLCenableFilters parameter, in this case, specifies that Warning messages are to be logged.
The format of the MLCenableFilters parameter is shown below.
Parameter |
-MLCenableFilters token1[:token2 ... :tokenn] |
Syntax Description token1[:token2 ... :tokenn] |
One or more message severity codes separated by colons(:). The allowable message severity codes are: Debug---Useful when debugging a problem in conjunction with Cisco's Technical Assistance Center. Error---Generates messages when any operational error condition occurs. Warning---Generates messages when an error condition occurs that is not fatal. Info---Generates messages to notify you of status information. Trace---Generates detailed operational log messages. SNMP Trace---Generates detailed SNMP trace log messages. UITrace---Generates trace log messages from user interface. IPCTrace---Generates detailed log messages for socket operations and interprocess communication. Dump---Generates dumps. InternalTrace---Generates internal operational log messages. The Error and Info message categories are enabled automatically. |
For example, to enable the logging of Warning, Debug, and Dump messages, in addition to the default Error and Info messages, for the DLSw poller daemon, you might edit /opt/CSCOcb/etc/runprocess and change the case statement for cwbdlswpollerd to look like this:
case cwbdlswpollerd:
set STD_DBG_PARAM="-MLCenableFilters Warning:Debug:Dump"
set GIVEN_PARAM="${GIVEN_PARAM} ${STD_DBG_PARAM}"
set PARAMETERS="${PM_PARAM} ${ML_PARAM} ${ORB_PARAM} ${GIVEN_PARAM}"
eval exec $CWBROOT/dlsw/bin/cwbdlswpollerd $PARAMETERS
breaksw
The following CiscoWorks Blue processes do not support the MLCenableFilters parameter:
If you just want to make the process calls use the -h (help) and -v (version) arguments, issue one of these commands directly instead of editing the script:
/opt/CSCOcb/etc/runprocess pnam -h
/opt/CSCOcb/etc/runprocess pnam -v
All the CiscoWorks Blue applications are started with the runprocess script. If you want to change parameters with which an application is started, you can edit the runprocess script to change the arguments.
Step 1 First see if the arguments you want to change are in the cwbinit file. If so, change them there instead.
Step 2 Before you change runprocess, make a backup copy.
Step 3 Edit the /opt/CSCOcb/etc/runprocess file.
Step 4 Search for the line that begins with the word case and contains the name of the application you want to change. For example, the line for the RSRB poller is as follows:
case cwbrsrbpollerd:
Step 5 Look after the case line for the line that starts set PARAMETERS. For the DLSw poller, that line looks like the following:
set PARAMETERS="${PM_PARAM} ${ML_PARAM} ${ORB_PARAM} ${GIVEN_PARAM}"
Step 6 Insert the arguments at the end of the set PARAMETERS line, just before the closing double quotes, and after leaving a space. For example, to change the polling sleep time for the RSRB poller to 600 seconds, you would add the value 600 to the set PARAMETERS line as follows:
set PARAMETERS="${PM_PARAM} ${ML_PARAM} ${ORB_PARAM} ${GIVEN_PARAM} 600"
Step 7 Save the file.
Posted: Wed Jun 30 06:33:55 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.