An audit trail can be created for logging all CiscoWorks Blue commands. The audit trail can be useful for diagnosing problems encountered while running CiscoWorks Blue. The audit trail is automatically saved in /opt/CSCOcb/logs/cwbcmd.log.
Database and Log File Maintenance
Database maintenance is performed using the cwb maintenance command. The cwb maintentance command is used to perform the following functions:
Stop CiscoWorks Blue processes so that the database can be backed up safely.
Back up the database file and database log
Back up the apache and cwb command log files and clear the current logs to control the size of the log file.
Start CiscoWorks Blue processes.
Using the cwb maintenance start Command
The cwb maintenance start command schedules a cron job to perform the maintenance processing. The schedule is set according to the HOUR, MINUTE, DATE, MONTH, and DAY parameters in the cwbinit file. Note that CiscoWorks Blue processes will be stopped while maintenance is done, and restarted afterwards.
The cwb maintenance stop command removes the cron job so that the CiscoWorks Blue maintenance will no longer run as scheduled.
The /opt/CSCOcb/etc/cwbinit file has been modified so that the scheduling of the cron job can be scheduled.
Setting the CiscoWorks Blue Maintenance Schedule
The options described in this section specify the time and frequency that automatic maintenance will be initiated through a cron job. To enable the scheduling, enter the /opt/CSCOcb/bin/cwb maintenance start command. You will be prompted to specify the times for the cron job to run
.
Table 0-1 Maintenance Schedule Options
Field
Value
HOUR
0 to 23
MINUTE
0 to 59
DATE
1 to 31
MONTH
1 to 12
DAY
0 to 6 for Monday through Saturday, respectively; * for Sunday
The following excerpt from the cwbinit file shows possible settings for the maintenance schedule.
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. It will also resend DLSw and APPN/SNASw traps back to the NMS in a human readable format. See (the Event Notification section) for more details
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
-h
Displays a help message.
-v
Displays the version.
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:
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.
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:
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.
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:
DLSW-MIB (RFC 2024)
CISCO-DLSW-MIB
dlswNodeUpTime
ciscoDlswUpTime
dlswTConnOperLocalTAddr
ciscoDlswTConnOperLocalTAddr
dlswTConnOperConnectTime
ciscoDlswTConnOperConnectTime
dlswTConnOperState
ciscoDlswTConnOperState
dlswCircuitS1DlcType
ciscoDlswCircuitS1DlcType
dlswCircuitS1RouteInfo
ciscoDlswCircuitS1RouteInfo
dlswCircuitS2TDomain
ciscoDlswCircuitS2TDomain
dlswCircuitS2TAddress
ciscoDlswCircuitS2TAddress
dlswCircuitState
ciscoDlswCircuitState
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 pollingpolls just key routers for peer connection information. Peer polling looks for a router state change and a peer-connection state change.
Non-Key-Peer pollingpolls 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 pollingpolls 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.
-PPollingSleepTimestarts 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/SNASw Polling
The polling of APPN/SNASw devices is performed as a thread of cwbsnamapsd. If the APPN/SNASw protocol is not configured, APPN/SNASw 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-MIB
appnNodeCpName
ibmappnNodeCpName
appnNodeType
ibmappnNodeType
appnLocalTgOperational
ibmappnLocalTgOperational
appnLocalTgCpCpSession
The process next queries the following variables from the DLUR MIB:
DLUR-MIB (RFC2232)
OLD-DLUR-MIB
dlurDlusSessnStatus
dlurDlusSessnStatus
dlurDlusName
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
dlurPuSscpSuppliedName
dlurPuName
dlurPuStatus
dlurPuStatus
dlurPuActiveDlusName
dlurPuActiveDlusName
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
appnPortOperState
ibmappnNodePortState
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
appnLsOperState
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-MIB
appnLocalTgDestVirtual
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:
APPN-MIB (RFC 2455)
IBM-6611-APPN-MIB
appnPortDlcType
ibmappnNodePortDlcType
appnVrnPortName
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
appnLsPortName
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):
ibmappnNnNodeFRName
ibmappnNnNodeFRFrsn
ibmappnNnNodeFRType
ibmappnNnNodeFRCongested
ibmappnNnNodeFRQuiescing
ibmappnNnTgFROwner
ibmappnNnTgFRDest
ibmappnNnTgFRNum
ibmappnNnTgFRFrsn
ibmappnNnTgFRDestVirtual
ibmappnNnTgFROperational
ibmappnNnTgFRCpCpSession
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):
ibmappnNodeUpTime
ibmappnNodeNnFrsn
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:
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 cwbhcidis 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
-h
Displays a help message.
-v
Displays the version.
domain_name
Enter the name of the host domain.
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
-h
Displays a help message.
-v
Displays the version.
domain_name
Enter the name of the host domain.
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
-h
Displays a help message.
-v
Displays the version.
domain_name
Enter the name of the host domain.
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 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]
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, starts all Maps and SNA View autostartable 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 servers.
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 startcwbdiscover 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 discoveredwhen 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.
If you specified the -d switch with no protocols, all protocols are discovered.
If you enter multiple protocols, do not separate them with spaces.
-rread_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, enter 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.
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:
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:
DLSW-MIB (RFC 2024)
CISCO-DLSW-MIB
dlswNodeStatus
ciscoDlswStatus
dlswTConnOperLocalTAddr
ciscoDlswTConnOperLocalTAddr
dlswTConnOperConnectTime
ciscoDlswTConnOperConnectTime
dlswTConnOperState
ciscoDlswTConnOperState
dlswTConnOperConfigIndex
ciscoDlswTConnOperConfigIndex
dlswTConnConfigTDomain
ciscoDlswTConnConfigTDomain
dlswTConnConfigLocalTAddr
ciscoDlswTConnConfigLocalTAddr
dlswTConnConfigRemoteTAddr
ciscoDlswTConnConfigRemoteTAddr
dlswCircuitS1DlcType
ciscoDlswCircuitS1DlcType
dlswCircuitS1RouteInfo
ciscoDlswCircuitS1RouteInfo
dlswCircuitS2TDomain
ciscoDlswCircuitS2TDomain
dlswCircuitS2TAddress
ciscoDlswCircuitS2TAddress
dlswCircuitState
ciscoDlswCircuitState
APPN Discovery MIB Variables
The following APPN MIB variables are queried during discovery:
APPN-MIB (RFC 2455)
IBM-6611-APPN-MIB
appnNodeCpName
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 stopall
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.
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:
To start the CiscoWorks Blue Administration application, use the cwb start admin command.
cwb start admin[-pportno][-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.
[-pportno]
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.
Defaults
No default behavior or values.
cwb start dlsw
To start the CiscoWorks Blue Maps DLSw Motif application, use the cwb start dlsw command.
Starts the DLSw GUI application, the DLSW executable, the DLSw poller daemon (cwbdlswpollerd), and the monitor daemon (cwbmonitord).
-uportno
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.
-pportno
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.
Defaults
No default behavior values.
cwb start rsrb
To start the CiscoWorks Blue Maps RSRB Motif application, use the cwb start rsrb command.
Starts the RSRB GUI application, the RSRB executable, the RSRB poller daemon (cwbrsrbpollerd), and the monitor daemon (cwbmonitord).
-uportno
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.
-pportno
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.
Defaults
No default behavior or values.
cwb start appn
To start the CiscoWorks Blue Maps APPN Motif application, use the cwb start appn command.
Starts the APPN GUI application, the APPN executable, and the APPN poller server daemon (AppnPollerServer).
-fdevice_name
Specifies the host name or IP address of an APPN node to be used as the network topology agent. This network topology agent also can be specified in the cwbinit file or omitted.
-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.
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
versions
Displays the version information about all CiscoWorks Blue servers.
status
Displays the current status and process IDs of all CiscoWorks Blue servers and processes. The last message column displays the last message sent by the processes to the Process Manager.
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
-o outputdirectory
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.
cwb—Running Miscellaneous Applications
The cwb command runs the suite of miscellaneous CiscoWorks Blue applications.
cwb {create seed| clear db | check 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.
clear db
Clears the CiscoWorks Blue Database and the appnfile file. 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 and the appnfile file, then restarts all servers.
check db
Checks the integrity of the database and offers alternatives if it is found to be suspect. The database can be synchronized with the log file and restored from a backup taken the last time the router discover process was performed or the cwb maintenance command was run. The database can be cleared completely to a point at which discovery must be rerun to restore the data.
The cwb check db command runs automatically whenever the CiscoWorks Blue process manager is restarted with the cwb start servers command.
config
Runs the cwbconfig application to configure CiscoWorks Blue host connection and port usage. You must be the root user to use the cwb config command.
verify
Runs the CiscoWorks Blue verification program to verify that you installed the applications correctly, and to check your configuration files and the database.
Defaults
No default behavior or values.
Utilities and Commands
This section describes the following utilities and commands:
Use the uninstall.sh command to uninstall 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
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
Use the runprocess command, in the $CWBROOT/etc directory to set appropriate environment variables and then execute a command.
runprocess process_name
Syntax Description
process_name
The name of the Maps process to be executed.
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_PARAMstatements in /opt/CSCOcb/etc/runprocess.
Using Message Log Client to Control Message Logging
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.
Example CiscoWorks Blue Process
For each CiscoWorks Blue process, there is an entry in /opt/CSCOcb/etc/runprocess that starts with a case statement. This example shows the entry for the DLSw poller daemon (cwbdlswpollerd):
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}"
Look at the highlighted line that contains the STD_DBG_PARAMstatement. 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.
Parameter
MLCenableFilters token1[:token2 ... :tokenn]
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, which is not fatal occurs.
Info—Generates messages to notify you of status information.
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}"
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"
