|
Table Of Contents
Commands and Processes for UNIX Systems
Stopping and Starting DLSw and RSRB Daemons
Daemons Common to DLSw and RSRB
APPN MIB Variables Queried During Polling
MIB Variables Queried During Discovery
Starting and Stopping Processes
Starting and Stopping User Applications
cwb—Running Miscellaneous Applications
Changing Message Logging For Each Process
Changing Parameters on Process Calls
Commands and Processes for UNIX Systems
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:
DLSw and RSRB Daemons
The core of the DLSw and RSRB applications is a set of daemons and database tables.
This section discusses the following information about daemons:
•Name of daemon
•Starting and stopping daemons
•Role of daemons in the operation of DLSw and RSRB Maps applications
The daemon names are shown in Figure D-1.
Figure D-1 Daemon Names
Daemon Name Descriptioncwbmonitord
DLSw and RSRB monitor daemon.
cwbdlswpollerd
DLSw poller daemon.
cwbrsrbpollerd
RSRB poller daemon.
cwbtrapd
DLSw and RSRB trap daemon.
Stopping and Starting DLSw and RSRB Daemons
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/bin
cwb start maps_daemon_command
Where:
maps_daemon_command is a Maps daemon startup command for each Maps daemon, as shown in the following sections.
Usage Guidelines
•Only one copy at a time of any specific daemon can be run on the same workstation.
•A daemon can be stopped and restarted only by a user who has the correct permissions.
•Cisco recommends using the Process Manager to start and stop daemons.
Daemons Common to DLSw and RSRB
This section describes how to control daemons that are common to both DLSw and RSRB. This section covers the following daemons:
• cwbtrapd
cwbmonitord
The monitor daemon (cwbmonitord) sends an update to the graphical map when it detects a change in the database. Primarily, the monitor daemon relies on the poller daemon and the trap daemon to update the database. The monitor daemon must be running for changes to appear on the graphical map.
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
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.
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.
cwbtrapd
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]
cwb stop cwbtrapd
The trap daemon reports changes to the following states:
•RSRB Peer state
•DLSw Peer state
•DLSw Circuit state
Syntax Description
Defaults
If you start the trap daemon with no options, it starts with default options.
RSRB Daemons
This section describes the RSRB daemons in the following subsections:
cwbrsrbpollerd
To continuously poll the MIBs in discovered routers for their ever-changing status, use the RSRB poller daemon cwbrsrbpollerd command.
cwb start cwbrsrbpollerd [-h | -v] [PollerSleepTime]
cwb stop cwbrsrbpollerd
Syntax Description.
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.
Poller MIB Variables
The poller daemon queries the following MIB variables in known RSRB-enabled devices (those in the Devices table that are flagged "discovered"):
•rsrbRemotePeerEncapsulation
•rsrbRemotePeerIPAddr
•rsrbRemotePeerState
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.
DLSw Daemons
This section describes the DLSw daemons and contains the following subsections:
• DLSw MIB Variables Queried During Polling
cwbdlswpollerd
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]
cwb stop cwbdlswpollerd
Syntax Description.
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.
DLSw MIB Variables Queried During Polling
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:
Setting DLSw Poller Timers
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.
•Key-Peer polling polls just key routers for peer connection information. Peer polling looks for a router state change and a peer-connection state change.
•Non-Key-Peer polling polls just the non-key routers for peer connection information. Peer polling looks for a router state change and a peer-connection state change.
•Key-Circuit polling polls the key routers for circuit information. Circuit polling looks for a router becoming unreachable, a new or lost circuit, and a circuit state change.
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.
•-P PollingSleepTime 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 starts the poller daemon for key-circuit polling and sets the sleep-time value. If you omit the -C PollingSleepTime value, the default is 1200 seconds.
•PollingSleepTime 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 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.
APPN 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.
APPN MIB Variables Queried During Polling
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-MIBappnNodeCpName
ibmappnNodeCpName
appnNodeType
ibmappnNodeType
appnLocalTgOperational
ibmappnLocalTgOperational
appnLocalTgCpCpSession
The process next queries the following variables from the 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-MIBdlurPuSscpSuppliedName
dlurPuName
dlurPuStatus
dlurPuStatus
dlurPuActiveDlusName
dlurPuActiveDlusName
If appn_port_polling parameter in cwbinit is set to ON, the following APPN-MIB variables are also polled:
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-MIBappnLsOperState
ibmappnNodeLsState
appnLsAdjCpName
ibmappnNodeLsCpName
appnLsTgNum
ibmappnNodeLsTgNum
First Time Polling
The first time a device is polled, the following APPN MIB variables are also polled:
APPN-MIB (RFC 2455) IBM-6611-APPN-MIBappnLocalTgDestVirtual
ibmappnLocalTgDestVirtual
appnNodeBrNn
ibmappnLocalTgCpCpSession
If appn_port_polling parameter in cwbinit is set to ON, the following APPN MIB variables are also polled the first time:
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-MIBappnLsPortName
ibmappnNodeLsPortName
appnLsCpCpSessionSupport
ibmappnNodeLsCpCpSession
ibmappnNodeLsDlcType
Network Topology Polling
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.
Host Connection Daemons
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:
• cwbhcid
• cwbhcmdd
• cwbhmond
cwbhcid
The Host Connection Interface daemon (cwbhcid) runs in the workstation to control all communications with the SNA mainframe component. It gets messages from the mainframe, sends commands to the mainframe, and coordinates mainframe discovery and polling. After cwbhcid is initiated, it starts the following daemons:
•cwbhcmdd—Sends commands to the mainframe.
•cwbhmond—Coordinates mainframe discovery and polling.
cwb start cwbhcid [ -h | -v] domain_name
Syntax Description
Defaults
No default behavior or values.
cwbhcmdd
The Host Command Interface daemon (cwbhcmdd) runs in the workstation to send commands to the SNA mainframe. It is started by cwbhcid and should not be started by the user.
cwbhcmdd [-h | -v] domain_name
Syntax Description
Defaults
No default behavior or values.
cwbhmond
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
Defaults
No default behavior or values.
CWB Command Script
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:
• Starting and Stopping Servers
• MIB Variables Queried During Discovery
• Starting and Stopping Processes
• Starting and Stopping User Applications
Starting and Stopping Servers
To start and stop the CiscoWorks Blue Process Manager and Name servers, use the cwb command.
cwb {start | stop} [pm | name]
cwb start servers
Syntax Description
Defaults
No default behavior or values.
Usage Guidelines
You must be the root user to start and stop servers.
cwbdiscover
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:
•The newly-added device has never been discovered for a specific protocol.
•A trap received from the device causes the Peer table to be updated.
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]]
[-r read_community_string [-s seed_file_name]]
[-h] [-v]Syntax Description
Defaults
No default behavior or values.
MIB Variables Queried During Discovery
This section lists the MIB variables queried during discovery. Maps and SNA View support the following MIBs:
•CISCO-RSRB-MIB
•CISCO-DLSW-MIB
•IBM-6611-APPN-MIB
•OLD-DLUR-MIB
•CISCO-TN3270-SERVER-MIB
•IETF draft standard DLSw MIB (RFC 2024)
•IETF draft standard APPN MIB (RFC 2455)
•IETF draft standard DLUR MIB (RFC 2232)
This section contains these main topics:
• Base Discovery MIB Variables
• RSRB Discovery MIB Variables
• DLSw Discovery MIB Variables
• APPN Discovery MIB Variables
•TN3270 Discovery MIB Variables
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.
Base Discovery MIB Variables
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
RSRB Discovery MIB Variables
The RSRB discovery process queries the following CISCO-RSRB-MIB variables in addition to the base MIB variables. These variables are unique to RSRB:
rsrbRemotePeerEncapsulation
rsrbRemotePeerState
rsrbRingLocal
rsrbVirtRingIPAddr
rsrbRemotePeerIPAddr
rsrbRingBridge
rsrbRingType
DLSw Discovery MIB Variables
The DLSw discovery process first queries the standard DLSW-MIB (RFC 2024). If that fails, the DLSw discovery process queries the CISCO-DLSW-MIB. The following DLSw MIB variables (unique to DLSw) are queried in addition to the base MIB variables:
APPN Discovery MIB Variables
The following APPN MIB variables are queried during discovery:
APPN-MIB (RFC 2455) IBM-6611-APPN-MIBappnNodeCpName
ibmappnNodeCpName
appnNodeType
ibmappnNodeType
appnNodeBrNn
TN3270 Discovery MIB Variables
The discovery process queries the device to determine whether it is configured with the tn3270sCpuCard TN3270 MIB variable.
Starting and Stopping Processes
To start and stop CiscoWorks Blue processes, use the cwb command.
cwb {start | stop} process_name
cwb stop all
Syntax Description
Defaults
No default behavior or values.
Starting and Stopping User Applications
This section describes how to start and stop user applications with the cwb command. This section contains the following information:
• cwb—Running Miscellaneous Applications
cwb start admin
To start the CiscoWorks Blue Administration application, use the cwb start admin command.
cwb start admin [-p portno] [-v] [-h]
Syntax Description
Defaults
No default behavior or values.
cwb start dlsw
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
Defaults
No default behavior values.
cwb start rsrb
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
Defaults
No default behavior or values.
cwb start appn
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
Defaults
No default behavior or values.
MsgLogClient
To start the Message Log display client application, use the cwb start MsgLogClient command.
cwb start MsgLogClient
Syntax Description
start
Starts the specified user application.
MsgLogClient
Starts the Message Log client (viewer) application.
Defaults
No default behavior or values.
ProcMgrClient
To start the Process Manager display client application, use the cwb start ProcMgrClient command.
cwb start ProcMgrClient
Syntax Description
start
Starts the specified user application.
ProcMgrClient
Starts the Process Manager client (viewer) application.
Defaults
No default behavior or values.
cwb kill all Command
To terminate all running CiscoWorks Blue processes and servers, use the cwb kill all command.
cwb kill all
Syntax 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.
cwb show
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.
cwb tac
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
Defaults
No default behavior or values.
cwb—Running Miscellaneous Applications
The cwb command runs the suite of miscellaneous CiscoWorks Blue applications.
cwb {create seed | clear db | config | verify | tac}
Syntax Description
Defaults
No default behavior or values.
Utilities and Commands
This section describes the following utilities and commands:
This section describes the following procedures:
• Changing Message Logging For Each Process
• Changing Parameters on Process Calls
uninstall.sh
On UNIX systems, the uninstall.sh command uninstalls CiscoWorks Blue Maps and SNA View applications. After you enter the uninstall.sh command, it detects all the installed Maps and SNA View files and asks you whether you want to delete them.
uninstall.sh
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/install
./uninstall.sh
On 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"
cgisnamaps Process
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.
cwbsnamapsd
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:
•To obtain information about any newly-defined TN3270 PUs
•To use a different APPN network topology agent
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.
Defaults
No default behavior or values.
Usage Guidelines
After you change the doDNSSearch parameter in the cwbinit file, you should stop and restart cwbsnamapsd.
runprocess
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.
cwbupgrade.sh
To have the system prompt you to enter the Maps and SNA View license keys after installation, use the cwbupgrade.sh command.
cwbupgrade.sh
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Changing Message Logging For Each Process
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.
MLCenableFilters Syntax
The format of the MLCenableFilters parameter is shown below.
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
Exceptions
The following CiscoWorks Blue processes do not support the MLCenableFilters parameter:
•CreateSeedFile
•The HP versions of the appn, dlsw, and rsrb executables and PollerServer.
Changing Parameters on Process Calls
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 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 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: Wed Aug 25 17:21:50 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.