|
|
 |
Note The information in this chapter applies to UNIX workstations (Maps and SNA View) only. |
This appendix provides a list of the commands and processes used by CiscoWorks Blue Maps and SNA View.
This appendix contains the following main sections:
The core of the DLSw and RSRB applications is a set of daemons and database tables.
This section discusses the following information about daemons:
The daemon names are shown in Figure 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 the Process Manager" or with the following cwb start command:
cd /opt/CSCOcb/binWhere:
maps_daemon_command is a Maps daemon startup command for each Maps daemon, as shown in the following sections.
Usage Guidelines
This section describes how to control daemons that are common to both DLSw and RSRB. This section covers the following daemons:
The monitor daemon saves the list of GUI clients in the database. For example, RSRB and DLSW. When the monitor daemon is reset, it sends updates to the applications in this list.
cwb {start | stop} cwbmonitord
Syntax Description
-h -v -c -t sleep_time UDPport
Defaults
If you start the monitor daemon with no options, it starts with default options using port 6000.
Usage Guidelines
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.
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.
cwb start cwbtrapd [-h | -v]The trap daemon reports changes to the following states:
Syntax Description
-h -v
Defaults
If you start the trap daemon with no options, it starts with default options.
This section describes the RSRB daemons in the following subsections:
Syntax Description .
-h -v PollerSleepTime
Defaults
The default PollerSleepTime is 600 seconds.
Usage Guidelines
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.
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 and contains the following subsections:
To continuously poll the MIBs in discovered routers for their status, use the DLSw poller daemon cwbdlswpollerd command.
cwb start cwbdlswpollerd [-h | -v] [-P PollingSleepTime] [-C PollingSleepTime] [PollingSleepTime]
Syntax Description .
-h -v -P PollingSleepTime -C PollingSleepTime PollingSleepTime
Defaults
If you start the poller daemon with no options, it starts with default options.
Usage Guidelines
Use the cwb start and cwb stop commands to start and stop the DSLw poller daemon.
During DLSw polling, the poller queries the MIB that was discovered for DLSw. If the Cisco IOS release changed so that MIB support was changed, you must rediscover this device.
The following DLSw MIB variables are queried during polling:
DLSW-MIB (RFC 2024) | CISCO-DLSW-MIB |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 the runprocess script, as described in the "Changing Parameters on Process Calls" section.
The sleep-time values determine how many seconds the poller daemon waits after polling is complete before it starts polling again.
|
Note If you start the poller daemon from the command line and specify just the -C polling option, the poller does only key-circuit polling. It does not perform peer polling. |
The polling of APPN devices is performed as a thread of cwbsnamapsd. If the APPN protocol is not configured, APPN polling is not performed.
During APPN polling, the poller queries the MIB that was discovered for APPN. If the Cisco IOS release changed so that MIB support was changed, you must rediscover this device. The following APPN-MIB variables are queried during polling:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
|
|
|
|
The process next queries the following variables from the DLUR MIB:
dlurDlusSessnStatus dlurDlusSessnStatus dlurDlusName
DLUR-MIB (RFC2232)
OLD-DLUR-MIB
If the appn_pu_polling parameter in cwbinit is set to ON, the following DLUR-MIB (RFC 2232) variables are also polled:
DLUR-MIB (RFC2232) | OLD-DLUR-MIB |
|---|---|
|
|
|
|
|
|
If appn_port_polling parameter in cwbinit is set to ON, the following APPN-MIB variables are also polled:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
If appn_link_polling parameter in cwbinit is set to ON, the following APPN-MIB variables are also polled:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
|
|
|
The first time a device is polled, the following APPN MIB variables are also polled:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
|
If appn_port_polling parameter in cwbinit is set to ON, the following APPN MIB variables are also polled the first time:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
If appn_link_polling parameter in cwbinit is set to ON, the following APPN MIB variables are also polled the first time:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
|
|
For network topology polling, the following IBM-6611-APPN-MIB variables are polled initially and as changes are detected (APPN-MIB variables are not queried during network topology polling):
|
|
|
|
|
|
|
|
|
|
|
|
For network topology polling, the following IBM-6611-APPN-MIB variables are polled at each poll interval to detect changes in network topology (APPN-MIB variables are not queried during network topology polling):
|
|
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. This section covers the following daemons:
Syntax Description
-h -v domain_name
Defaults
No default behavior or values.
Syntax Description
-h -v domain_name
Defaults
No default behavior or values.
The Host Discovery/Poller daemon (cwbhmond) runs in the workstation to coordinate SNA mainframe discovery and polling. It is started by cwbhcid and should not be started by the user.
cwbhmond [-h | -v] domain_name
Syntax Description
-h -v domain_name
Defaults
No default behavior or values.
This section describes the cwb command script that you run from /opt/CSCOcb/bin to start the CiscoWorks Blue applications on UNIX workstations, and includes the following subsections:
To start and stop the CiscoWorks Blue Process Manager and Name servers, use the cwb command.
cwb {start | stop} [pm | name]
Syntax Description
start stop pm name start servers
Defaults
No default behavior or values.
Usage Guidelines
You must be the root user to start and stop servers.
Cisco does not recommend that you start the discovery process from the command line because you will not see a progress indicator until discovery is complete. Instead, use the cwb start admin command to start the Administration application and run discovery from the Administration application.
If you want to use the command-line interface, then use the cwb start cwbdiscover command to start and stop the CiscoWorks Blue discovery processes. Each discovery process starts, discovers the devices, then stops.
To periodically run discovery processes to automatically discover new devices, run the cwb start cwbdiscover command as a UNIX cron job (chronologically started). Set the cron job to run at night or when system and network activity is low.
Use the discover 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.
After execution, the discover process queries all IP devices in the database that are flagged not discovered. A device is set to not discovered when one of the following occurs:
If there is a NMS 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 used to add new devices to the database.
cwb start cwbdiscover [-d [d][r][a][t]]
Syntax Description
-d [d][r][a][t]
-r read_community_string -s seed_file_name -h -v
Defaults
No default behavior or values.
This section lists the MIB variables queried during discovery. Maps and SNA View support the following MIBs:
This section contains these main topics:
|
Note If you see SNMP failures when querying MIB variables during discovery, polling, or other user queries, which require SNMP responses (such as DLSw peer statistics), a malfunction may exist at the queried router. Please check with the manufacturer of the router being queried for MIB. |
The following variables are queried whenever discovery is run, no matter which protocol is being discovered:
sysObjectID | ipAdEntIfIndex |
ifIndex | ipAdEntNetMask |
ifType | dot1dSrPortLocalSegment |
ifPhysAddress | dot1dSrPortBridgeNum |
ipAdEntAddr | dot1dSrPortTargetSegment |
|
|
|
|
|
|
|
DLSW-MIB (RFC 2024) | CISCO-DLSW-MIB |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following APPN MIB variables are queried during discovery:
APPN-MIB (RFC 2455) | IBM-6611-APPN-MIB |
|---|---|
|
|
|
|
|
To start and stop CiscoWorks Blue processes, use the cwb command.
cwb {start | stop} process_name
Syntax Description
start stop process_name stop all
Defaults
No default behavior or values.
This section describes how to start and stop user applications with the cwb command. This section contains the following information:
To start the CiscoWorks Blue Administration application, use the cwb start admin command.
cwb start admin [-p portno] [-v] [-h]
Syntax Description
start admin [-p portno] [-v] [-h]
Defaults
No default behavior or values.
To start the CiscoWorks Blue Maps DLSw Motif application, use the cwb start dlsw command.
cwb start dlsw [-u portno] [-p portno] [-k | -g] [-f device_name] [-v] [-h]
Syntax Description
start dlsw -u portno -p portno -k -g -f device_name -v -h
Defaults
No default behavior values.
To start the CiscoWorks Blue Maps RSRB Motif application, use the cwb start rsrb command.
cwb start rsrb [-u portno] [-p portno] [-g] [-f device_name] [-v] [-h]
Syntax Description
start rsrb -u portno -p portno -g -f device_name -v -h
Defaults
No default behavior or values.
To start the CiscoWorks Blue Maps APPN Motif application, use the cwb start appn command.
cwb start appn [-f device_name [-r read_community_string]] [-v] [-h]
Syntax Description
start appn -f device_name -r read_community_string -v -h
Defaults
No default behavior or values.
To start the Message Log display client application, use the cwb start MsgLogClient command.
cwb start MsgLogClient
Syntax Description
start MsgLogClient
Defaults
No default behavior or values.
To start the Process Manager display client application, use the cwb start ProcMgrClient command.
cwb start ProcMgrClient
Syntax Description
start ProcMgrClient
Defaults
No default behavior or values.
To terminate all running CiscoWorks Blue processes and servers, use the cwb kill all command.
cwb kill allSyntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Usage Guidelines
You must be the root user to use the cwb kill all command.
The cwb kill all command is intended for situations when processes or servers appear to be stuck in a transitional state (for example, starting or stopping) and do not appear to respond to the normal cwb start and cwb stop commands.
To display information about the CiscoWorks Blue servers, use the cwb show command.
cwb show {versions | status}
Syntax Description
Defaults
No default behavior or values.
The cwb tac command 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.
cwb tac [-o outputdirectory]
Syntax Description
Specifies a directory where the command output is saved. If you omit this operand, the output is saved as file cwbtac_n.tar.Z in a temporary directory, where the n is incremented for each successive use. The cwb tac command searches for a temporary directory in this order: /usr/tmp, /var/tmp, /tmp. You can specify an output directory in which to save the output of the cwb tac command: · You can specify an absolute directory by preceding the path with a / character. If the specified directory does not exist, the cwb tac command prompts you to create it. The following command saves the zipped file as /usr/cwblue/cwbtac_1.tar.Z. cwb tac -o /usr/cwblue
· You can specify a relative directory. This directory is always relative to /opt/CSCOcb/etc. The following command saves the zipped file as /opt/CSCOcb/etc/tac/cwbtac_1.tar.Z. cwb tac -o tac
Defaults
No default behavior or values.
The cwb command runs the suite of miscellaneous CiscoWorks Blue applications.
cwb {create seed | clear db | config | verify | tac}
Syntax Description
create seed [-s seedfile]
Defaults
No default behavior or values.
This section describes the following utilities and commands:
This section describes the following procedures:
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Usage Guidelines
To uninstall the installed Maps applications, use the following command:
cd /opt/CSCOcb/installOn Windows NT systems, use the Control Panel > Add/Remove function to uninstall CiscoWorks Blue using the Install Shield program. For more information, see "Installing CiscoWorks Blue SNA View on Windows NT."
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 should not be run by the user.
To get information from the database for distribution by the web server, run the cwbsnamapsd command in the workstation. You might want to stop and restart the web daemon for the following reasons:
Syntax Description
-h -v interval
Defaults
No default behavior or values.
Usage Guidelines
After you change the doDNSSearch parameter in the cwbinit file, you should stop and restart cwbsnamapsd.
On UNIX systems, the runprocess command, in the $CWBROOT/etc directory, sets appropriate environment variables and then executes a command.
runprocess process_name
Syntax Description
Defaults
No default behavior or values.
Usage Guidelines
You should not use runprocess directly, but you might want to edit the script to change selected arguments.
To have the system prompt you to enter the Maps and SNA View license keys after installation, use the cwbupgrade.sh command.
cwbupgrade.shSyntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
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 log Warning messages. If you must change these default values, you can edit the STD_DBG_PARAM statements in /opt/CSCOcb/etc/runprocess.
On Windows NT systems, update the NT Registry. For more information, see "Commands and Processes for Windows NT."
|
Note The normal mode of operation is to use the Message Log client to dynamically control message logging for each process. To control message logging during process startup, or if you want to make message log changes permanent, modify the runprocess script as described. Enabling additional message logging can hurt performance and cause web time outs. Enable additional message logging only when necessary or when requested by Cisco TAC. |
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.
| MLCenableFilters token1[:token2 ... :tokenn] |
|
|
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 the parameters with which an application is started, you can edit the runprocess script to change the arguments.
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 with 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: Mon Sep 4 10:49:36 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.