Using the Administration Application

This chapter provides information on using the Administration application on UNIX workstations. Use the CiscoWorks Blue Administration application to add, delete, modify, and discover devices in your CiscoWorks Blue database, and to select DLSw key devices. DLSw key devices are described in the "Specifying the Status of Aggregated Peers" section.

Starting CiscoWorks Blue Administration

This section covers starting the CiscoWorks Blue Administration application. You can start the Administration application from the following locations:

Starting Administration From a Network Management System

You can start the CiscoWorks Blue Administration application from a NMS, such as NetView for AIX.

Starting Administration From a System Prompt

On a UNIX workstation, the CiscoWorks Blue Administration application is accessible from /opt/CSCOcb/bin/. To start the application from a system prompt, enter the following commands:

Starting Administration From a Remote Workstation

You can log in to a remote UNIX host from your own local UNIX workstation, export the remote host display to your local workstation, and then run the application from the remote host. To start the remote host's CiscoWorks Blue Administration application from your local workstation, use the following procedure:

Step 2 Log in to the remote UNIX host as root (or with a username of your own choosing).

Step 3 Set your DISPLAY environment variable to export the display from the remote host to your local workstation. Depending on which shell you are using, use one of the following commands:

Step 4 To start the CiscoWorks Blue Administration application, enter the following commands:

Using the Main Administration Window

When you start the CiscoWorks Blue Administration application, the CiscoWorks Blue Administration window is displayed. Use the CiscoWorks Blue Administration window to add, delete, modify, and discover devices in your CiscoWorks Blue database, and to select DLSw key devices.

Main Administration Window

Edit Devices Area

The Edit Devices area allows you to manipulates the devices in the database and includes the following buttons:

Buttons

Button	Description
Add	Add adds one or more devices, separated by spaces, to the database.
Delete	Delete deletes one or more devices from the database.
Modify	Modify changes the read community string for one or more devices.
Rediscover	Rediscover rediscovers one or more devices in the database.
DLSw Key	DLSw Key designates or removes one or more devices as DLSw key devices

Discover Area

The Discover area allows you to discover DLSw, RSRB, APPN/SNASw, or TN3270 devices using either a seed file or an NMS database, and adds the discovered devices to the CiscoWorks Blue database. Discover performs a common discovery process, which includes any SRB rings. Discover queries routers for the protocols you select.

Buttons

Button	Description
RSRB	RSRB discovers RSRB devices.
DLSw	DLSw discovers DLSw devices.
TN3270	TN3270 discovers TN3270 devices. (To use this function, you must have a valid license for the SNA View application.)
APPN/SNASw	APPN discovers APPN/SNASw devices.

Check Boxes

Check Box	Description
By Seed File	By Seed File starts discovery using a seed file. You are prompted for the seed file name.
By NMS	By NMS starts discovery using an NMS database. (This option is available only when an NMS was selected during installation.)

Launch Area

Buttons

Button	Description
Process Manager	Process Manager starts the Process Manager client application.
Message Log	Message Log starts the Message Log viewer client application.
Verification	Verification starts a web browser and displays the Verification web page.

Administration Window

Buttons

Button	Description
Exit	Exits the CiscoWorks Blue Administration application.
Help	Displays online help in a web browser window.

Buttons in Other Windows

Buttons

Other windows in the Administration application may have one or more of the following buttons:

Button	Description
OK	Designates the devices in the Selected list as DLSw key devices. The devices in the Devices list remain unchanged.
Cancel	Cancels the operation and returns to the previous window.
Help	Displays online help for the Key Device Selection window.
<< and >>	Moves devices between the Devices list and the Selected list.

Discovering the Network

Discovering DLSw Devices in the Network

This section describes how to discover the Cisco DLSw-enabled routers in your SNA network.

Discovery is the process by which the DLSw application queries each device in the network to determine whether it is enabled for DLSw networking. Each time the DLSw application finds a router, it performs one of the following actions:

If the router is enabled for DLSw and SNMP, the discover process adds the router name as a DLSw router in the database, and it polls that router.
If the router is not enabled for DLSw, the discover process stores that router name as a non-DLSw router in the database, and it does not poll that router. Every time the process runs, it tries to discover these non-DLSw routers.
If a router cannot be accessed by SNMP, the discover process tries to reach that router each time discovery is run.

There are several ways in which the DLSw application can discover the routers in a network. You can provide a list of enabled routers in a special file called a seed file. Or you can let the Maps application get its information from an NMS database.

Discovering the Network with a Seed File

If your NMS is incapable of providing an accurate list of Cisco routers, or if you want to provide a list of routers to limit discovery, you can create a seed file for the Maps application.

Seed File Format

Each record in the seed file can be either a comment or a router specification. You can list the routers in any order within the seed file.

A comment is a single line of text that begins with the pound (#) character, as shown below.

The delimiter can be a space or a colon (:).
router can be either a host name or the IP address of a DLSw-enabled router in the network. This is the same label that marks the router on a map.
ReadCommunityString is the read community string for the router. If you do not include this, the default read community string of "public" is used. If you want to designate this router as a key device while still using the default read community string, use the asterisk (*) to represent the default read community string (public). You can omit this value if you do not want to use the key value.
key indicates that this is a DLSw key device. If you omit the word "key," the router is not considered a DLSw key device. This option is used only by the DLSw application. It is ignored by APPN/SNASw, RSRB, and TN3270. For information about key devices, read the "Specifying the Status of Aggregated Peers" section and the "Define Key Devices" section.

Sample Router Specification in a Seed File

The following sample router specification designates router west.cisco.com as a key device with the read community string "public":

Cross-Application Use

Because the key parameter is used only for DLSw and is ignored for APPN/SNASw and RSRB, you can use the same seed file for all three Maps applications. The following lines are from a sample seed file:

Using the Seed File for Discovery

To use a seed file to provide the information to the application, use the following procedure:

Step 2 Start DLSw and select Admin > Discover > Seed File to display the Seed File Discover window.

Step 3 Enter the name of the seed file, verify the correct read community string, and click Discover. Discovery takes place while you wait.

After loading the database using the seed file, the DLSw application operates normally until a router is taken off line or a new router is configured. At that time, you can perform one of the following actions:

Create a new seed file for the new router.
Add the new routers to the existing seed file and rerun discovery from the seed file. DLSw ignores already discovered routers and discovers just the added routers.
Add one or more devices directly to the global map, as described in CiscoWorks Blue Maps and SNA View User Guide.

Discovering the Network with a Network Management System Database

The NMS maintains a database, which includes all SNMP-managed routers in your network. You can use that database to provide the Maps application with the information it needs to discover the DLSw-enabled routers in the network. You can do this manually or automatically.

Discovering the Network Manually

To have the Maps application discover the network from the NMS database manually, select Admin > Discover > Database from the Maps application menu bar. The Maps application adds the routers found by the NMS to the database. The Maps application checks the database for new routers, polls their MIBs, and updates the database with the new MIB information.

Discovering the Network Automatically

You can have Maps check the NMS database automatically. This is called automatic discovery mode; you might want to use it if you expect to install or reconfigure routers often. To use automatic discovery mode, use the cwb start cwbdiscover command as a UNIX cron job (a chronologically started job). Set the cron job to run at night or when system and network activity are low.

Discovering Individual DLSw Routers

If you want to add only one or a few routers to your network, you can discover each router individually using the following procedure:

Step 2 When prompted, enter the router's device name and its read community string.

The DLSw application adds the router to the database, polls the router's MIB, and adds the MIB information to the database. Watch the status area to see a message indicating the success or failure of this polling.

Rediscovering Individual DLSw Routers

It is sometimes useful to rediscover a DLSw router, especially if one of the following events occurs:

A message appears in the status area indicating that the device already exists in the database.
A router was just configured with DLSw.
A later version of the Cisco IOS software was installed on the router, and the DLSw MIB is now supported.
Router interfaces have been reconfigured.

You can select Edit > Rediscover Device(s) from the DLSw menu bar.
You can select a router icon on the map, click the right mouse button, and select Rediscover from the popup menu.
You can use the Administration application.

Correlating SNA Resources with DLSw Routers

The following conditions must be met to have SNA PUs and LUs correlated with the DLSw routers that support them:

The DLSw Maps application must poll routers for the DLSw circuits to obtain the latest SNA information.
At least one of the polled routers, through which a circuit passes, must be designated as a key device.

Specifying the Status of Aggregated Peers

In a key devices view of the network, each key router is shown connected to one icon that represents all of that router's peers. This icon is called an aggregated peer router. The connection from the key router to its aggregated peer router is called an aggregated peer connection. Each aggregated peer connection and each aggregated peer router is displayed in a color that indicates its status. The status shown for the aggregated peer or peer connection represents the status of each component that makes up the aggregate. You can specify how to choose the color in which the aggregated status is displayed. There are two ways to choose the status of an aggregated peer or peer connection: using the worst-case status or using a calculated status.

Using the Worst-Case Status

You can choose to have all aggregated peers displayed in the color that is used for the peer with the worst status. For example, if the worst peer connection represented in the aggregated peer connection is inactive, then the aggregated peer connection is displayed as a red line and its aggregated peer router is also displayed in red.

Using a Calculated Status

A peer connection can have one of four statuses: active, degraded, inactive, or unknown. Degraded, and inactive statuses are considered abnormal. When all peer connections have unknown status, the aggregate status is "unknown."

You can choose to have the aggregated peers displayed in a color that represents a status calculated from that of the individual peers which make up the aggregation. The calculation is based on the percentage of peers in the aggregation whose condition is abnormal. An abnormal condition is based on the reported status of the peer.

To determine how to display an aggregated peer, look at the percentage of individual peers with an abnormal condition in the aggregated peer. Once that percentage is determined, you define two threshold values: the Marginal% value and the Critical% value.

Specifying the Threshold Percentages

To specify percentages for the Marginal% value and Critical% value, use the following procedure:

Step 2 Select Threshold Value (%) and enter the values in the Critical% and Marginal% fields.

Defining the Marginal% Threshold

The Marginal% value is a threshold value that the DLSw application uses to determine which aggregated peers are in a degraded state or an active state. When the percentage of abnormal peers in the aggregation exceeds this threshold value, the aggregated peer status is considered degraded and is displayed in yellow. When the percentage of abnormal peers in the aggregation is less than or equal to this Marginal% value, the aggregated peer status is considered active and is displayed in green.

You define the Marginal% value for your network. The default Marginal% value for DLSw aggregated peers is 0 percent.

Defining the Critical% Threshold

The Critical% value is a threshold value that is used to determine which aggregated peers are in the inactive state. When the percentage of abnormal peers in an aggregation exceeds the critical% threshold value, the aggregated peer status is considered inactive and is displayed in red.

You define the Critical% value for your network. The default Critical% value for DLSw aggregated peers is 20 percent.

A special case occurs when all peers are unknown. In this case, the aggregated peer is considered unknown and is displayed in blue.

Calculating the Status for Peer Connections

DLSw calculates the status of an aggregated peer connection using the following method:

Step 2 DLSw compares the percentage of abnormal peer connections (x percent) to the Critical% value and to the Marginal% value.

If x percent is greater than or equal to 0 percent, but less than or equal to the Marginal% value, then the aggregated peer connection is considered active and is colored green.
If x percent is greater than the Marginal% value, but less than or equal to the Critical% value, then the aggregated peer connection is considered degraded and is colored yellow.
If x percent is greater than the Critical% value, then the aggregated peer connection is considered inactive and is colored red.

For example, there is a key router with six peer connections: three connections are active; one connection is unknown; and two connections are inactive. That means that 50 percent of the peer connections have abnormal status. Here are some scenarios:

If we set the Marginal% value to 0 percent and the Critical% value to
20 percent (which are the default values), the 50 percent abnormal number falls above the Critical% value. The status of the aggregated peer connection is inactive and is displayed in red.
If we set the Marginal% value to 30 percent and the Critical% value to
80 percent, the 50 percent abnormal number falls between the Critical% value and the Marginal% value. The status of the aggregated peer connection is degraded and is displayed in yellow.
If we set the Marginal% value to 60 percent and the Critical% value to
80 percent, the 50 percent abnormal number falls below the Marginal% value. The status of the aggregated peer connection is active and is displayed in green.

Discovering RSRB in the Network

This section describes how to discover the RSRB-enabled routers in your SNA network. Discovery is the process by which the RSRB application queries each device in the network to determine whether it is enabled for RSRB networking. Each time the RSRB application finds a router, it does one of the following actions:

If the router is enabled for RSRB, the discover process stores that router name as an RSRB router in the database, and it polls that router.
If the router is not enabled for RSRB, the discover process stores that router name as a non-RSRB router in the database, and it does not poll that router.
If a router cannot be accessed by SNMP, the discover process continues trying to reach that router on every discovery iteration until it can determine whether the router is enabled for RSRB.

There are several ways that the RSRB application can discover the routers in a network. You can provide a list of enabled routers in a special file called a seed file. Or you can let the Maps application get its information from the NMS database.

Discovering the Network with a Seed File

If your NMS is incapable of providing an accurate list of Cisco routers, or if you want to provide a list of routers that will limit discovery to just a limited set of routers, you can create a seed file for the Maps application.

Seed File Format

Each record in the seed file can be either a comment or a router specification. You can list the routers in any order within the seed file.

Comments

A comment is a single line of text that begins with the pound (#) character, as shown in the following line:

Router Specifications

The delimiter can be a space or a colon (:).
router can be either a host name or the IP address of a router in the network. This is the same label that marks the router on a map.
ReadCommunityString is the read community string for that router. If you do not include this, the default read community string of "public" is used. You can use an asterisk (*) as a place holder for the default read community string, or you can just omit it.

Cross-Application Use

You can use the same seed file for all three Maps applications (DLSw, RSRB, and APPN/SNASw). Although the DLSw application uses a third parameter on each router entry to identify a router as a DLSw key device, that parameter is ignored for the RSRB and APPN/SNASw applications. The following lines are from a sample seed file:

Using the Seed File for Discovery

Step 2 Start RSRB and select Admin > Discover > Seed File to display the Seed File Discover window.

Step 3 Enter the name of the seed file, verify the correct read community string, and click Discover. Discovery takes place while you wait.

After loading the database using the seed file, the application operates normally until a router is taken off line or a new router is configured. If a new router is added to the network, you can perform one of the following tasks:

Create a new seed file for the new router.
Add the new routers to the existing seed file and rerun discovery from the seed file. RSRB ignores already discovered routers and discovers just the added routers.
Add one or more devices directly to the global map, as described in the "Discovering Individual RSRB Routers" section.
Add one or more devices using the Administration application.

Discovering with a Network Management System Database

The NMS maintains a database which includes all SNMP-managed routers in your network. You can use that database to provide the Maps application with the information it needs to discover the routers in the network.

Discovering the Network Manually

To have the RSRB application discover the network from the NMS database manually, select Admin > Discover > Database from the Maps application menu bar. The Maps application adds the routers found by the NMS to the database. The Maps application checks the database for new routers, polls their MIBs, and updates the database with the new MIB information.

Discovering the Network Automatically

Discovering Individual RSRB Routers

If you want to add only one or several routers to your network, you can discover each router individually by using the following procedure:

Step 2 When prompted, enter the router's device name and its read community string.

Step 3 Click OK. The Maps application adds the router to the database, polls the router's MIB, and adds the MIB information to the database.

Watch the status area for a message indicating the success or failure of this polling.

Rediscovering Individual RSRB Routers

It is sometimes useful to rediscover an RSRB router, especially if one of the following events occurs:

A message appears in the status area indicating that the device already exists in the database.
A router was just configured with RSRB.
A later version of the Cisco IOS software was installed on the router so that the RSRB MIB is now supported.
Router interfaces have been reconfigured or IP addresses have changed.

To rediscover individual routers you can select Edit > Rediscover Device(s) from the RSRB menu bar.

Discovering APPN/SNASw in the Network

This section describes the APPN/SNASw discovery process and includes the following subsections:

Understanding APPN/SNASw Discovery

APPN/SNASw finds IP addresses and maintains a correlation of IP addresses and APPN/SNASw CP names. APPN/SNASw starts with a network management database, or with a seed file, or just IP addresses. For each address, APPN/SNASw finds an APPN/SNASw name and correlates the device's IP address with its APPN/SNASw name in the correlation table.
APPN discovers APPN/SNASw nodes. As it checks each IP address, APPN/SNASw looks for the APPN MIB to determine whether that device is APPN/SNASw-enabled.
APPN discovers network topology agents. As it finds APPN/SNASw-enabled devices, APPN/SNASw checks whether each APPN/SNASw network node can be a network topology agent. APPN/SNASw uses the first network topology agent it finds.

APPN identifies nodes using their APPN/SNASw names, which are in the form NETID.CPNAME. NETID is the network ID; CPNAME is the control point name. To query and collect management data from nodes, APPN/SNASw must also know the IP address for each node (because the APPN/SNASw application manages APPN/SNASw nodes using the SNMP protocol).

The process of finding an IP address for each APPN/SNASw node is called discovery. APPN/SNASw starts with the APPN/SNASw CP name for each node. Then it discovers the IP address by prompting you to enter an IP address or device name (and read community string) for each CP name the first time you request a view. The APPN/SNASw application maintains this correlation between IP address and CP name for subsequent sessions.

To avoid being prompted for IP addresses or host names, you can perform a one-time discovery of the entire APPN/SNASw network. For APPN/SNASw, this discovery is the process of querying all IP devices in the network to determine whether they are also APPN/SNASw network nodes, and, if so, to get their APPN/SNASw names.

The APPN/SNASw application stores the correlation data in a binary file named
/opt/CSCOcb/etc/appnfile. You should not edit this file, but you can delete it to force the APPN/SNASw application to lose all its correlation data and rediscover the network. You can delete this file to force rediscovery when CP names or IP addresses are changed or reassigned.

Launching Discovery

You can launch the discovery process by selecting Admin > Discover item on the menu bar or from an NMS.

Launching Discovery from the Admin Menu

You can launch discovery using a seed file. Select Admin > Discover > Seed File. In the Seed File Discover window, select the seed file to start discovery.
You can launch discovery using a database. Select Admin > Discover > Database. The application reminds you that the process could take some time to complete. Click Yes if you want to continue.

This process discovers all the devices in the seed file or database. After discovery is complete, select View > Global to display the global view.

Launching Discovery Using a Network Management System

We recommend that you do not launch the discovery process using an NMS because the NMS selects a topology agent at random. It is better to explicitly select a topology agent or to use a seed file of network nodes from which to select a network topology agent. APPN/SNASw queries the devices from the seed file in the order in which they are listed. You can launch discovery using an NMS to correlate the IP addresses with CP names for the remaining nodes.

Discovering the Network with a Seed File

An APPN/SNASw seed file is a list of IP devices to be queried for a network topology agent. The APPN/SNASw application uses a seed file in the following situations:

If your NMS cannot be relied upon for an accurate list of Cisco routers, or if you want to provide a special list of routers, you can create a seed file for the APPN/SNASw application.

Seed File Format

Each record in the seed file can be a comment or a router specification. You can list the routers in any order within the seed file, but the order of routers in the seed file determines the order in which the routers are discovered to select a network topology agent.

Comments

A comment is a single line of text that begins with the pound (#) character, as follows:

Router Specifications

read_community_string is the read community string for that router. To use the default string (public), you can omit the read_community_string or you can use just an asterisk (*) as a place holder for the default read community string. If a read community string is missing for a device, the APPN/SNASw application uses the default read community string specified by the rdcommstr parameter in the cwbinit file. You can create the APPN/SNASw seed file with a text editor, and then save it as the appnseed file. The recommended location for the seed file is $HOME/.appn/appnseed.

Cross-Application Use

You can use the same seed file for all three Maps applications (DLSw, RSRB, and APPN/SNASw). Although DLSw has a third parameter on each router entry to identify a router as a key device, that parameter is ignored for the APPN/SNASw and RSRB applications. The following lines are from a sample seed file:

Using the Seed File for Discovery

To use a seed file to provide the information to the application, use the following procedure:

Step 2 Start APPN/SNASw and select Admin > Discover > Seed File. to display the Seed File Discover window.

Step 3 Enter the name of the seed file, verify the correct read community string, and click Discover. Discovery takes place while you wait.

After loading the database using the seed file, the application operates normally until a router is taken off line or a new router is configured. At that time, you can perform one of the following actions:

Create a new seed file to add the new router.
Add the new routers to the existing seed file and rerun discovery from the seed file. APPN/SNASw ignores already discovered routers and discovers just the added routers.

Discovering Devices for the Database

Use the CiscoWorks Blue Administration application to discover devices for the database. Use the following procedure to discover devices in the database:

Step 2 In the Discover list, select one or more of the following protocol types:

RSRB to discover devices running the RSRB protocol.
DLSw to discover devices running the DLSw protocol.
Tn3270 to discover devices running the TN3270 protocol. To use this function, you must have a valid license for the SNA View application.
APPN/SNASw to discover devices running the APPN/SNASw protocol.

Click By Seed File to discover the devices using a seed file. You are prompted for the seed file name. When you select this option, the Seed File Discover Window is displayed.
Click By NMS to discover devices using the NMS database. (This option is available only if an NMS was selected during installation.)

The appropriate processes are started to discover and then add enabled devices to the CiscoWorks Blue database during which time the screen displays a work in a Discovery in Progress window. This window is shown in Figure 7-4.

Seed File Discover Window

Fields

Field	Description
Filter	Allows you to construct a filter rule that controls the paths and files displayed in the Directories and Files fields.
Directories	Displays the directories that meet the filter requirements.
Files	Displays the files that meet the filter requirements.
Selected Seed File	Displays the seed file you selected.
Default Read Community	Displays the default read community string for this seed file. You can change this value.

Buttons

Button	Description
Discover	Starts the discover process from the selected seed file.
Filter	Applies the path and file name rule from the Filter field to the Directories and Files fields.

Adding Devices to the Database

You can add one or more devices to the database manually in the following instances:

You want to add a device that is newly connected to the network.
You want to add a device to update a set of devices on a map, perhaps because automatic update is disabled, or is set to an infrequent interval and you have not chosen to list target devices in a seed file.

If a Cisco device does not appear on a map or web page, but you know that the device exists in the network, you can add the device using the Add button.

When you add a device, the application prompts you for the device's host name or IP address and read community string. The application then places the new device in the database.

Step 2 In the Device name field, enter the host names or IP addresses, separated by spaces, of the devices that you want to add.

Step 3 In the Read Community field, enter the read community string of the device that you want to add.

After you add new devices, the DLSw poller and cwbsnamapsd are automatically restarted to update the following:

Deleting a Device From the Database

From the CiscoWorks Blue Administration application, you can use the Delete button to remove devices from the database. You might want to delete devices for the following reasons:

The devices might be in the database because you entered incorrect names in a seed file.
The devices are no longer running any of the managed protocols (DLSw, RSRB, APPN/SNASw, or TN3270).
You now discover devices from the NMS and have several devices that will never run a managed protocol.
You have a device that is running a managed protocol but you do not want to manage (poll) that device.
You want to speed up the discovery process by deleting devices that are not running any of the managed protocols (the discovery process always tries to rediscover devices that are in the database, but not running the selected protocol).

Step 2 The Devices list all the devices (routers) in the database. Select all the devices you want to delete.

Step 3 Click the >> button to move the selected devices into the Selected list.

The Selected list displays the devices to be deleted. Use the >> and << buttons to move devices between the Devices list and the Selected list.

If you inadvertently move devices to the Selected list which you do not want to delete, select those devices and click the << button to move them back to the Devices list.

Step 4 Click OK to delete the selected devices. The selected devices are deleted from the database.

Modifying a Device in the Database

Change the read community string for one or more devices using the following procedure:

Step 2 The Devices list box displays the devices currently in the database. Select all the devices you want to modify.

Step 3 Click the >> button to move the selected devices into the Selected list. The selected list box displays the devices to be modified. Use the >> and << buttons to move devices between the Devices list and the Selected list.

If you inadvertently move devices which you do not want modified to the Selected list, select those devices and click the << button to move them back to the
Devices list.

Step 4 The Read Community string specifies the new read community string for the selected devices. Enter a new read community string to be applied to all the selected devices.

Step 5 Click OK to change the read community string for the selected devices. The read community string is changed in the CiscoWorks Blue database (not in the router itself) for the selected devices.

Rediscovering a Device

You may want the discovery process to rediscover a device if that device is now running different protocols; or you may want to update the database information about that device but do not want to wait until the next polling interval. Use the following procedure to rediscover a device:

Step 2 The Devices list displays the devices currently in the database. Select all the devices you want to rediscover.

If you select more than one device by pressing the Ctrl or Shift key, all selected devices must have the same read community string.

Step 3 Click the >> button to move the selected devices into the Selected list. The Selected list box displays the devices to be rediscovered.

If you inadvertently move devices which you do not want rediscovered, select those devices and click the << button to move them back to the Devices list.

Step 4 The Read Community String field specifies the read community string fort the selected devices. Enter a new read community string to be applied to all the selected devices.

After you rediscover devices, the DLSw poller and cwbsnamapsd are automatically restarted to update the database with circuit information used in SNA correlation and to update the cwbsnamapsd cache with current TN3270 and APPN/SNASw information.

Specifying DLSw Key Devices

Use the DLSw Key Devices Selection window to designate DLSw key devices from the CiscoWorks Blue database, or to deselect current key devices. You can specify one or more devices as DLSw key devices using the following procedure:

Step 2 The Devices list displays the DLSw devices that are not key devices. Select all the devices that you want to make key devices.

Step 3 Click the >> button to move the selected devices into the Selected list. The Selected list box displays the DLSw devices that are designated as key devices.

If you inadvertently move devices to the Selected list which you do not want designated as key devices, select those devices and click the << button to move them back to the Devices list.

Step 4 Click OK. The devices in the Selected list become DLSw key devices. The devices in the Devices list remain unchanged.

After you add key devices, the DLSw poller is automatically restarted, updating the database with circuit information used in SNA correlation.

Launching the Process Manager Client

You can launch the Process Manager client from the Administration window. From the CiscoWorks Blue Administration window, click Process Manager. The Process Manager client application starts and the Process Manager window is displayed.

Launching the Message Log Client

You can launch the Message Log client from the Administration window. From the CiscoWorks Blue Administration window, click Message Log. The Message Log client window is displayed.

Launching the Installation Verification Web Page

You can launch the Installation Verification web page from the Administration window. From the CiscoWorks Blue Administration window, click Verification. The web browser is started, which displays the Verification web page. The Verification web page verifies the protocols you configured during installation, checks the cwbinit configuration file, and checks the CiscoWorks Blue databas

Table of Contents