cc/td/doc/product/rtrmgmt/bluelist/cwblue30
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Commands and Processes for Windows NT

Commands and Processes for Windows NT

Note   The information in this chapter applies to Windows NT systems (SNA View) only.

This appendix provides a list of the commands and processes used by CiscoWorks Blue SNA View for Windows NT.

This chapter includes 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 lists the daemons. (For information on the database tables, see "Database Tables.") The daemon names are shown in Table E-1.


Table E-1: Daemon Names
Daemon Name Description

CWBMONITORD

DLSw and RSRB monitor daemons

cwbdlswpollerd

DLSw poller daemon.

cwbrsrbpollerd

RSRB poller daemon.

cwbtrapd

DLSw and RSRB trap 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"):

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 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

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-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 then only 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.

MIB Variables Queried During Discovery

This section lists the MIB variables queried during discovery. SNA View support the following MIBs:

This section contains information about the following 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: 
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.

Services and Processes

CiscoWorks Blue SNA View for Windows NT runs the services and processes listed in this section.

CiscoWorks Blue SNA View is designed such that Windows NT services automatically run some of CiscoWorks Blue SNA View processes. The following processes are automatically started after reboot.

This section also describes the following commands and processes:

cwb

To launch cwb processes from the command line interface, use the cwb command.

cwb

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Usage Guidelines

Displays a list of the cwb commands you can use with CiscoWorks Blue SNA View for Windows NT.

Serves as a launching point for running processes.

cwbw

To launch cwbw processes from the command line interface, use the cwbw command.

cwbw

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Usage Guidelines

The cwbw process is the launching point for all processes for Windows NT. This process is the Windows version of cwb.

cwb clear db

To initialize the CiscoWorks Blue SNA View database, use the cwb clear command.

cwb clear db

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

cwb config

To start the CiscoWorks Blue SNA View Configuration application, use the cwb config command. The Configuration application lets you configure CiscoWorks Blue SNA View host connection and port usage.

cwb config

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

cwb kill

To terminate various CiscoWorks Blue SNA View processes, use the cwb kill command.

cwb kill {all | PID | ProcessName}

Syntax Description

all

  Terminates all CiscoWorks BLue SNA View daemon processes.

PID

  Terminates processes with the specified PID.

ProcessName

  Terminates any process containing STR in its module name.

Defaults

No default behavior or values.

Usage Guidelines

You must have administrator privileges to use the cwb kill PID and cwb kill ProcessName commands.

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 view version and status information about CiscoWorks Blue SNA View servers, use the cwb show command.

cwb show {versions | status}

Syntax Description

versions

  Displays the version information about all CiscoWorks Blue SNA View servers.

status

  Displays the current status and process IDs of all CiscoWorks Blue SNA View 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 stop

To terminate a selected process, use the cwb stop command.

cwb stop {all | Apache | db | name | pm | ProcessName | web}

Syntax Description

all

  Stops all CiscoWorks BLue SNA View daemon processes.

Apache

  Stops the Apache web server.

db

  Stops the CiscoWorks Blue SNA View database server when there are no active connections. This command does not stop the database if there are active connections.

name

  Stops the Visibroker naming server.

pm

  Stops the process manager.

ProcessName

  Stops any registered process containing STR in its name.

web

  Stops the Apache web server.

Defaults

No default behavior or values.

cwb start

To start CiscoWorks Blue SNA View processes and servers, use the cwb start command.

cwb start {admin | Apache | db | debug | MsgLogClient | name | osagent | pm | pmstatus | ProcessKey | ProcMgrClient | servers | web}

Syntax Description

admin

  Starts the CiscoWorks Blue SNA View Administration application.

Apache

  Starts the Apache web server.

db

  Starts the CiscoWorks Blue SNA View database server.

debug

  Starts a message log client display.

MsgLogClient

  Starts a message log client display.
  install_directory\CSCOcb\bin\cwb start MsgLogClient
  where install_directory is the directory in which you installed the product

name

  Starts the Visibroker naming server.

osagent

  Starts the Visibroker naming server.

pm

  Starts just the Process Manager server.
  install_directory\CSCOcb\bin\cwb start pm
  where install_directory is the directory in which you installed the product.

pmstatus

  Starts a process manager client display.

ProcessKey

  Starts any registered process.

ProcMgrClient

  Starts a process manager client display.
  install_directory\CSCOcb\bin\cwb start ProcMgrClient
  where install_directory is the directory in which you installed the product.

servers

  Starts all CiscoWorks Blue SNA View server processes.
  install_directory\CSCOcb\bin\cwb start servers
  where install_directory is the directory in which you installed the product.

web

  Starts the Apache web server.

Defaults

No default behavior or values.

cwb tac

To run the CiscoWorks Blue TAC collection program to collect and zip all the information you will need when you call the Cisco TAC, 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 verify

To start the verification tool from the command line interface, use the cwb verify command. The verification tool verifies that the installation was successful and to check the configuration files and database.

cwb verify

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

cwbdiscover

To start the discovery process, use the cwbdiscover command. 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 be specified 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

-d [d][r][a][t]

  Specifies one or more protocols to discover:

  • d discovers devices running the DLSw protocol.

  • r discovers devices running the RSRB protocol.

  • a discovers devices running the APPN protocol.

  • t discovers devices running the TN3270 protocol.

  If you specified the -d switch with no protocols, all protocols are discovered.
  If you enter multiple protocols, do not separate them with spaces.

-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, 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.

Usage Guidelines

Cisco does not recommend running discovery from the command line because you will not see a progress indicator until discovery is complete. Right-click the CiscoWorks Blue icon in the taskbar and choose Administration or use Start > Programs > CiscoWorks Blue > Administration to start the Administration application and run discovery from there. For more information, see "The information in this chapter applies to Windows NT systems (SNA View) only.."

If you want to use the command line interface, use the cwb start cwbdiscover command to start and stop the CiscoWorks Blue discovery processes. Each discovery process starts, discovers the devices, then stops.

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:

CWBHTTPAdapter

To start and monitor the web servers, use the CWBHTTPAdapter command.

CWBHTTAdapter

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

cwbsnamapsd

To run the Web daemon in the workstation to get information from the database for distribution by the web server, use the cwbsnamapsd command.

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

You might want to stop and restart the web daemon for the following reasons:

After you change the doDNSSearch parameter in the cwbinit file , you should stop and restart cwbsnamapsd.

Cisco recommends that you use the Configuration application to make these changes. For more information, see "Using CiscoWorks Blue SNA View Configuration for Windows NT."

cwbsrbpollerd

To poll the MIBs in discovered routers for their ever-changing status, use the cwbsrbpollerd command.

cwb start cwbrsrbpollerd [-h | -v] [PollerSleepTime]

cwb stop cwbrsrbpollerd

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.

Defaults

If you start the poller daemon with no options, it starts with default options.

cwbdlswpollerd

To poll the MIBs in discovered routers for their status, use the cwbdlswpoller command.

cwb start cwbdlswpollerd [-h | -v] [-P PollingSleepTime] [-C PollingSleepTime] [PollingSleepTime]

cwb stop cwbdlswpollerd

Syntax Description

-h

  Displays a help message.

-v

  Displays the version.

-PPollingSleepTime

  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.

-CPollingSleepTime

  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.

cwbhcid

To run the host connection interface daemons, use the cwbhcid command. cwbhcid

cwbhcid

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Usage Guidelines

The Host Connection Interface daemon 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 started, it starts the following daemons:

CWBDBAdapter

To start and monitor the database engine, use the CWBDBAdapter command.

cwb start CWBDBAdapter

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

itsh

To start processes in the background, use the itsh /c command.

itsh /c "command"

Syntax Description

itsh /c

  The itsh process is used internally by process management.

command

  Specifies the command to use to start a process in the background.

Defaults

No default behavior or values.

jre and jrew

To run the jre or jrew command, refer to Java documentation.

jre

jrew

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 executable, by default, store Error, Warning, and Info messages in the message log. The Error and Info messages are logged automatically. A parameter in the registry 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. I

To change message logging for a process, update the NT Registry using the following procedure.

Step 1   From the Start menu, select Run and then enter regedit.


Figure E-1: Run Window


Step 2   Click OK. The Registry Editor window is displayed.

Step 3   Open the following folders: HKEY_LOCAL_MACHINE > SOFTWARE > Cisco Systems > CiscoWorks Blue.


Figure E-2: Registry Editor


Step 4   CiscoWorks Blue contains a list of folders in which each folder represents a process and command. Select the folder containing the process you want to edit.

Step 5   Double-click the COMMAND file for the selected process. The Edit String window is displayed.


Figure E-3: Edit String Window


Step 6   Edit the string and then click OK.

Changing Parameters on Process Calls

If you 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:

All the CiscoWorks Blue applications are started with cwb. If you want to change parameters with which an application is started, you can make your changes in the Registry Editor.

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 make any changes, make a backup copy of the process you want to change.

Step 3   Display the Edit String Window.

For more information on how to display the Edit String window, see "Changing Message Logging For Each Process" section.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Sep 4 10:49:31 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.