Monitoring and Controlling CiscoWorks Blue Applications

This chapter presents an overview of the procedures necessary to administer the CiscoWorks Blue Maps and SNA View user applications. As administrator, your job entails using the various CiscoWorks Blue administration programs to:

Start and stop the CiscoWorks Blue daemons and processes
Control the message log and view the error messages
Ensure that all the configuration files are correct
Specify DLSw key devices and discover the network devices (routers) that support the SNA and TCP/IP protocols
Use the product verification utility to ensure that everything is ready for the users to run the Maps and SNA View Motif and web-based applications
Use the cwb command scripts to perform many administrative tasks
Start and control the CiscoWorks Blue web server

This chapter includes the following main sections:

Starting Processes and Servers During Installation

At the end of product installation, you are asked whether you want to start the CiscoWorks Blue servers and processes. If you answered Yes, the following servers are started:

Naming server
Process Manager server

Any processes marked as autostart are started by the Process Manager. You can see which programs have been started by using the cwb show status command:

: /opt/CSCOcb/bin/cwb show status

The output from this command shows you the status and process ID of all servers and processes. The Last Message column displays the last message sent by the process to the Process Manager.

CiscoWorks Blue Naming Server Started.
CiscoWorks Blue Process Manager Started.
Process Manager running with processes:

PROCESS              STATE    PID        Last Message

CWBHTTPAdapter       Ready    45818      Running

CWBOSAMonitor        Ready    25078      Running

cwbhcid_MVSDTCP      Ready    26162      Running

  cwbhcmdd             Ready    17106      Running

  cwbhmond             Ready    18690      Domain Discovered : Mon Aug  2 17:189

CWBPMMonitor         Ready    19262      Running

cwbrsrbpollerd       Ready    27004      Running

cwbsnamapsd          Ready    26422      Ready for client requests

cwbtrapd             Ready    15548      Running

CWBMsgLogServer      Ready    40696      Running

AppnPollerServer     Ready    21386      Connection opened with cwbsnamapsd

cwbdlswpollerd       Ready    29058      Running

cwbhci_server_MVSDLU62 Initial

cwbhcmd_server_MVSDLU62 Initial

CWBDBAdapter         Ready    33598      Running

cwbmonitord          Initial

Administering CiscoWorks Blue after Installation

This section describes the ongoing administration tasks that you will perform after successful installation of the CiscoWorks Blue products. This section includes the following information:

Applying the CiscoWorks Blue Licenses

To run the CiscoWorks Blue Maps and SNA View applications and their supporting servers and processes, you must obtain and apply the appropriate license information. You obtain licenses from Cisco to run Maps and SNA View and you apply the license information in one of the following two ways:

During the installation process, you can provide the license keys in answer to the questions asked by the installation script.
After installation is complete, you can use the cwbupgrade.sh command as described in the "Applying Licenses after Installation" section.

Monitoring and Controlling Processes

The Process Manager client lets you view the status of processes and daemons and it lets you start and stop the processes and daemons. You can start the Process Manager client in one of the following ways:

From the Administration application, as described in "Using the Administration Application"
Enter the cwb start ProcMgrClient command:

: /opt/CSCOcb/bin/cwb start ProcMgrClient

Use the cwb show status command to monitor the status of the CiscoWorks Blue servers and processes:

: /opt/CSCOcb/bin/cwb show status

For information about using the Process Manager, see "Using the Process Manager."

You can also use the cwb script to start processes, daemons, user applications, and other administrative programs from the command line, as described in "CiscoWorks Blue Commands and Processes."

Viewing the Message Log

The Message Log client lets you view the messages that are logged by CiscoWorks Blue processes and control the kind of messages that are logged. You can start the Message Log client in one of the following ways:

From the Administration application, (as described in "Using the Administration Application")
Enter the cwb start MsgLogClient command:

: /opt/CSCOcb/bin/cwb start MsgLogClient

For information about using the Message Log, see "Using the Message Log Viewer."

Completing the cwbinit File

The /opt/CSCOcb/etc/cwbinit file contains default values used by most of the CiscoWorks Blue applications.

Specifying an APPN/SNASw Network Topology Agent

In most cases you will not be able to specify a network topology agent because SNASw as a branch network node does not have the complete APPN topology. Leave this field blank in the APPN motif startup and the /opt/CSCOcb/etc/cwbinit file unless you have an APPN Network Node that supports the APPN-MIB in your network. Even without a network topology agent, the network topology views will be avilable, populated from the information retrieved from the managed SNASw routers.

For more information about specifying a network topology agent, see the "Selecting a Network Topology Agent" section.

Specifying NetView and CiscoWorks 2000 Web Addresses

If you also use Cisco View or CiscoWorks 2000, you must access those software packages at the following URL:

http://<CiscoWorks URL or IP Address>:<CiscoWorks Port>/CSCOnm/servlet/ com.cisco.nm.cvw.servlet.CvServlet?csUser=autoLogin&Device=<device name or IP Address>

CiscoWorks Blue fully qualifies device domain names to CiscoWorks 2000, including the Cisco View feature, to ensure that the resource is correctly identified in CiscoWorks 2000.

To link from the CiscoWorks Blue web page to web pages for NetView for OS/390 and CiscoWorks 2000, you can set these URLs in cwbinit, as described in the "Starting and Stopping the Web Server" section.

Setting DLSw and RSRB Polling Intervals

Use the cwbinit file to set polling intervals for DLSw and RSRM devices, as described in the "Starting and Stopping the Web Server" section.

Specifying Values for the cwbsnamapsd Web Daemon

Use the cwbinit file to specify values to control the cwbsnamapsd web daemon, as described in the "Starting and Stopping the Web Server" section.

Starting Host Discovery

To correlate the SNA PUs with the TCP/IP routers, you must run the SNA host discovery process. If, during installation, you select a TCP connection to the mainframe, then the Process Manager automatically starts the cwbhcid daemon to start a host connection.

To start the daemon in the Process Manager, click cwbhcid_domain and click Start. If you selected an LU 6.2 connection to the mainframe, you must first configure the LU 6.2 transaction programs as described in the section "Configuring the Host Connection" section. The CiscoWorks Blue mainframe application will actually start the connection to the workstation.

Creating a Seed File

You can use a seed file for discovering routers and for specifying DLSw key routers. A seed file is a file that contains a list of routers to be discovered. You can list the routers in either of two formats:

router [ReadCommunityString] [key]

router:[ReadCommunityString]:[key]

Where key indicates that this is a DLSw key device. If you omit the word key, the router is not considered a DLSw key device.

For information about creating a seed file, see the "Discovering the Network" section and view the subsections specific for each protocol (DLSw, RSRB, TN3270, and APPN/SNASw).

Specifying DLSw Key Devices

For DLSw applications, whether web-based or Motif applications, you should select several routers as key devices. For information about key devices, see the "Specifying the Status of Aggregated Peers" section.

Select key devices in one of the following ways:

Before you run the discovery process, you can specify key devices in a seed file using the key parameter to designate that router as a key device. For information about the seed file, see the "Discovering the Network with a Seed File" section.
After you run the discovery process, you can specify key devices using the CiscoWorks Blue Administration application, as described in the "Launching the Process Manager Client" section.
After you run discovery, from the Motif-based DLSw application, you can specify key devices by selecting Edit > Key Device(s) from the menu bar, as described in "Starting the User Applications." (This option is available only if you have licensed CiscoWorks Blue Maps.)

Discovering the Routers

You discover the TCP/IP-managed devices (routers) in the network to populate the CiscoWorks Blue database. During this time, the discovery process discovers and records every device in the network that supports any of the supported protocols (DLSw, RSRB, APPN/SNASw, or TN3270).

Discover the network devices using the following applications:

From the CiscoWorks Blue Administration application, as described in "Using the Administration Application."

Note To see SRB rings in DLSw views, including the SNA dependency views, use RSRB/SRB discovery from the Administration application.

From the Motif applications, by selecting Tools > Discover from one of the Maps Motif applications (DLSw, APPN/SNASw, or RSRB), as described in "Starting the User Applications." (This option is available only if you have licensed CiscoWorks Blue Maps.)

Discover the network devices in one of the following ways:

Use the database maintained by a network management system (NMS), such as NetView for AIX, HP OpenView, and SunNet Manager. For more information, see the "Discovering the Network" section and review the subsection for each protocol (DLSw, RSRB, and APPN/SNASw).
Use a list of routers that you create in a seed file. For more information, see the "Discovering the Network" section and review the subsection for each protocol (DLSw, RSRB, and APPN/SNASw).

Note If you discover DLSw devices from a seed file, you should specify key devices in the seed file.

Setting a Password for the cwblue User

During installation, (if CiscoWorks is also installed) user ID cwblue is created for running CiscoWorks Blue applications. The user ID is created without a password, so you may want to create a password for cwblue before you let users log in with it.

Verifying That CiscoWorks Blue Is Ready

Run the product verification program to ensure that all the preceding tasks were done correctly. The verification program checks the contents of the configuration files and the CiscoWorks Blue database for accuracy and completeness and ensures that all the required servers and processes are running so that users can log in to the web page and use the Motif applications.

You can run the verification program from the administration program, as described in "Using the Administration Application," or by issuing the following command:

: /opt/CSCOcb/bin/cwb verify

Using the cwb Command

The cwb command performs a variety of related administration tasks, such as starting and stopping servers and processes and displaying status. The cwb command is summarized here, but is explained in full, with command line options, in "CiscoWorks Blue Commands and Processes."

To start and stop specific servers, use one of the following commands:

: cwb {start | stop} [ pm | name]
: cwb start servers

To start and stop processes, use one of the following commands:

: cwb {start | stop} process_name
: cwb stop all

See "CiscoWorks Blue Commands and Processes" for information about the processes that you can start and stop. The cwb stop all command stops the Process Manager too. Use the cwb kill all command only when you cannot stop processes normally.

To kill all CiscoWorks Blue processes, use the following command:

: cwb kill all

To start the Administration application, use the following command:

: cwb start admin

To start the discovery application, use the following command:

: cwb start cwbdiscover [-d [d][r][a][t]]

To start the DLSw Motif application, use the following command:

: cwb start dlsw

To start the RSRB Motif application, use the following command:

: cwb start rsrb

To start the APPN Motif application, use the following command:

: cwb start appn

To start the Message Log client, use the following command:

: cwb start MsgLogClient

To start the Process Manager client, use the following command:

: cwb start ProcMgrClient

To display status and version information, use the following command:

: cwb show {versions | status}

To create a seed file from the CiscoWorks Blue database, use the following command:

: cwb create seed

To clear all data from the CiscoWorks Blue database and the appnfile file, use the following command:

: cwb clear db

To run the CiscoWorks Blue configuration program to reconfigure host connection and port usage, use the following command:

: cwb config

To verify successful installation of CiscoWorks Blue products, use the following command:

: cwb verify

To collect information for reporting to Cisco TAC, use the following command:

: cwb tac [-o outputdirectory]

Toperform maintenance or to start the maintenance schedule, use the following command:

: cwb maintenance [start | stop]

Starting and Stopping the Web Server

Before you access the CiscoWorks Blue web page from a web browser, ensure that the web server is running on the workstation on which the CiscoWorks Blue applications are installed. To determine whether a web server is running, enter the following commands:

: cd /opt/CSCOcb/bin
: ./cwb show status

If the CiscoWorks Blue web server is not running, you can start it using the Process Manager.

The CiscoWorks Blue web server starts using the port that was configured during installation and configuration. The order of port selection is as follows:

1. Use port 80.

2. Use port 8080.

3. Ask installer for unused port.

Browse the file /opt/CSCOcwbC/apache/etc/httpd.conf to find the port being used.

Using the cwbinit File

The cwbinit file contains a set of startup options and variables with which the cwbsnamapsd application starts.

The first set of parameters in the cwbinit file are used only by the cwbsnamapsd application.
The second set of parameters in the cwbinit file are used by both the cwbsnamapsd application and the APPN/SNASw application.

If you change the cwbinit file while the application is running, you must reset the process to activate the changes to cwbinit.

Parameters for cwbsnamapsd Only

The following sample of the cwbinit file shows just the values that apply to the cwbsnamapsd application:

# ******************************************************************** 

# This section is used by the cwbsnamapsd server process, which 
# handles requests from the web interface.

# default socket number for communication with cgi-bin programs

socketCgi-AppServer = 51999

# default number of threads for cwbsnamapsd.

# Valid range of values is 1 to 30.

# Increase the number to allow more concurrent web browser users, 

# decrease the number to limit CPU utilization on the server.

socketPoolThread = 10

# cgi-bin wait time on response from cwbsnamapsd, in seconds.

# This is used to clean up outstanding requests in case of a hang or 
# other problems with cwbsnamapsd.

# Increase this value only if time outs occur because of extremely

# slow network (snmp) or database responses.

cgiBinWaitTimeOut = 120

# TME 10 NetView for OS/390 Web Interfaces

#

# This is used to configure the NetView Web Interfaces used by the 

# Maps/SNA View.  Each NetView login must contain a name and URL

# separated by a '^' character.

#

# The name is any identifier that you want to associate with the

# NetView login.  The URL is the fully-qualified address of the

# NetView web interface.

#

# You may specify multiple NetView logins, each of which must be

# separated by a ',' character: 

# netViewInterfaces = name^url,name^url,name^url

# For example:

# netViewInterfaces = Joe's NetView^www.myhost.com,Bob's 
# NetView^www.myhost.com/~bob

netViewInterfaces =

# CiscoWorks 2K Web Interface

# This is used to indicate the URL of the CiscoWorks 2000 Resource 
# Manager Essentials

# package:

# ciscoWorksURL = http: //<host name>:<port>  

ciscoWorksURL =

# SNA Filter Request Database Limit

#

# Whenever you make a request to the database, the application first 
# calculates the amount of data that needs to be processed to service # the request.  This parameter indicates at what point the request is # considered too big and should not be processed.

#

# When you submit a request, the 'cgiBinWaitTimeOut' parameter 
# controls how long the browser will wait until it times out. If you 
# submit a huge request to the database (like 'LU Name=*'), the web

# server will most likely timeout before the database ever finishes 
# processing the request. This parameter is used to filter out those 
# requests that will probably never finish before the web browser 

# times out. You will get a message on the web interface informing 
# you that this limit has been reached, and you should refine your 
# search.

#

# You can adjust this parameter to suit your needs. The higher the 
# number, the larger the request the database will try to handle. 
# Keep in mind, however, that a larger number will cause the database 
# to work harder, thereby affecting system performance and blocking 
# database access to other users of this application.

#

# In the normal course of operations, the requests to the database 
# should not be all that large.  If they are, then the users of the 
# product should 

# narrow down their requests to the database by specifying more 
# precise data in the SNA Filter search screens.

maxRowCount = 5000

# SNA View Sessions and Session Connectivity Field Suppression  

#

# The following allow the indicated field name and the related 
# contents to be suppressed in the Sessions table and on the Session 
# Connectivity display. By default, all fields and their associated 
# values are displayed. 

# To suppress a field and its contents, uncomment the field entry. You

# may want to do this to reduce the Sessions table width or to block

# sensitive data from being displayed to SNA View users.

#

# To turn on the field name suppression, set the associated variable = # on. Valid values : on/off. default value : off.

#suppressLUName = on

#suppressPU2Name = on

#suppressFEPName = on

#suppressLogicalLineInfo = on

#suppressPhysicalLineInfo = on

#suppressClientIP = on

#suppressMACSAP = on

#suppressIDBLKNUM = on

#suppressCPName = on

#suppressDLURName = on

#suppressDLUSName = on

#suppressNodeName = on

socketCgi-AppServer

Use the socketCgi-AppServer value to specify the socket number to use when communicating with cgi-bin web programs. The default socket number is 51999.

socketPoolThread

Use the socketPoolThread value to specify the number of threads for cwbsnamapsd. The valid range of values is 1 to 30. The default is 10 threads. You can increase the number of threads to allow more concurrent web browser users, and you can decrease the number of threads to limit CPU use on the server.

cgiBinWaitTimeOut

Use the cgiBinWaitTimeOut value to specify the cgi-bin wait time on response from cwbsnamapsd, in seconds. This value is used to clean up outstanding requests in case of a hang or other problems with cwbsnamapsd. Increase this value only if time outs occur because of extremely slow network (snmp) or database responses. The default value is 120 seconds.

netViewInterfaces

Use the netViewInterfaces value to configure the NetView web interfaces used by the CiscoWorks Blue web page. Each NetView login must contain a name and URL separated by a "^" character.

The name is any identifier that you want to associate with the NetView login.
The URL is the fully-qualified address of the NetView web interface.

You can specify multiple NetView logins, each of which must be separated by a comma (,) in the following format:

netViewInterfaces = name^url,name^url,name^url

For example, you might enter the following:

netViewInterfaces = Joe's NetView^www.myhost.com,Bob's NetView^www.myhost.com/~bob

ciscoWorksURL

Use the ciscoWorksURL value to configure a CiscoWorks 2000 web Interface. This value is used to indicate the URL of the CiscoWorks 2000 Resource Manager Essentials package. Use the following format:

ciscoWorksURL = http: //  host_name[:port]

Where:

host_name is the host name of the host running the CiscoWorks 2000 web Interface.

port is the port number on that host, if it is not port 80.

Session Field Suppression

Use the set of "SNA View Sessions and Session Connectivity Field Suppression" variables to do the following:

Configure the fields that can be suppressed on the SNA View Sessions tables.
Configure the information that is suppressed in a dependency view.

Initially, the session suppression entries are set as comments so they are not active. Each value lets you suppress one or more related fields. For example, to suppress the display of the IDBLK/IDNUM field, you would uncomment the suppressIDBLKNUM line, as shown below:

suppressIDBLKNUM = on

This parameter...	Suppresses these fields...
suppressLUName = on	LU Name
suppressPU2Name = on	PU2 Name
suppressFEPName = on	FEP Names
suppressLogicalLineInfo = on	Logical Line PU field and logical line information in the dependency view
suppressPhysicalLineInfo = on	Physical line information in the dependency view
suppressClientIP = on	Client IP address
suppressMACSAP = on	Client MAC/SAP and destination MAC/SAP or MAC1/SAP1 and MAC2/SAP2
suppressIDBLKNUM = on	IDBLK/IDNUM
suppressCPName = on	CPNAME
suppressDLURName = on	DLUR Name
suppressDLUSName = on	DLUS Name
suppressNodeName = on	Node Name

You can suppress displaying fields, as shown in the following table:

Parameters for cwbsnamapsd and APPN/SNASw

The following sample of the cwbinit file shows the values that apply to the cwbsnamapsd application and to APPN/SNASw.

[cwbsnamapsd and  APPN/SNASw Parameters Begin Here]

# *********************** 

# ***  APPN/SNASw parameters ***

# *********************** 

# These parameters are used by both  APPN/SNASw and cwbsnamapsd. If either 

# is already running, they must be stopped and restarted for changes

# to take effect.  

# Selection of the network topology agent is done in this order:

# 1) command line parameters, if any;

# 2) parse this config file.

# 3) user will be prompted to run discovery or enter agent information

#

# 3 applies to  appn only. No prompt dialog is given in cwbsnamapsd.

# network topology agent ip address or device name (NOT  appn cpname)

nettopoagentdevname =

# network topology agent read community string

nettopordcommstr = 

# network topology agent  appn control point name (NETID.CPNAME format)

nettopoagentcpname = 

# backup network topology agent ip address or device name (NOT  appn

# cpname)

backupnettopoagentdevname =

# backup network topology agent read community string

backupnettopordcommstr = 

# backup network topology agent  appn control point name (NETID.CPNAME # format)

backupnettopoagentcpname = 

# default read community string

rdcommstr = public

# automatic collection of local topology (NONE, NN_ONLY, ALL)

autolocaltopo = ALL

# network topology polling interval, in seconds

nettopopoll = 15

# backup network topology polling interval, in seconds

# (in backup mode only, when primary agent fails, backup uses nettopopoll)

backupnettopopoll = 600

# local topology polling interval, in seconds 

loctopopoll = 600

# control whether  APPN/SNASw polls the DLUR PU table as part of local 
# topology polling. To turn off polling for PUs, set appn_pu_polling = # off

appn_pu_polling = on

# control whether  APPN/SNASw polls the  APPN/SNASw port table as part of local 
# topology polling. To turn off polling for ports, set 
# appn_port_polling = off

appn_port_polling = on

# control whether  APPN/SNASw polls the  APPN/SNASw link table as part of local 
# topology polling. To turn off polling for links, set 
# appn_link_polling = off

appn_link_polling = on

# This option controls TG event generation.

# To turn off TG event generation, set eventgen_tg = off.

# To generate event for existing TGs when an operational state change

# is detected, set eventgen_tg = on.

# To generate events for existing TGs when an operational state change

# is detected and for newly created operational (active) TGs,

# set eventgen_tg = all.

# Exception: No events are generated for TGs created on

# the first poll cycle. This avoids a storm of events during

# process startup.

# valid values: on/off/all

eventgen_tg = on

# To turn off dlur session event generation, set eventgen_dlur = off

# valid values : on/off

eventgen_dlur = on

# To turn on port event generation, set eventgen_port = on

# valid values : on/off

eventgen_port = off

# To turn on link event generation, set eventgen_link = on

# valid values : on/off

eventgen_link = off

# This option controls the CWBlue cache deletion of TGs that are no 
# longer reported by local topology agents. A Cisco IOS change was 
# made to delete inactive dynamic TGs from the router database.

# To delete TGs that are no longer reported by the agent,

# set this parameter to 'off'. 

# To keep those TGs in the CWBlue cache, set this parameter to 'on'. 

If TG 

# events are enabled, this will trigger an event if the TG becomes

# operational again.  

# valid values:on/off

keep_deleted_tgs = off

Controlling Access to the CiscoWorks Blue Web Page

You can use various methods to control access to the CiscoWorks Blue web page. You can find documentation about Apache HTTP server Version 1.3.26 security features at the following web sites:

http://www.apacheweek.com/features/userauth
http://www.apacheweek.com/features/dbmauth

The CiscoWorks Blue web server supports both htpasswd and dbmmanage methods of user authentication documented in these URLs.

Communicating the Maps and SNA View URL

After you install Maps and SNA View, your Maps and SNA View users can elect to use a web browser to access the applications. These users start their web browsers and type the URL of the CiscoWorks Blue web server:

http ://host_name[:port_number]/

Where:

host_name is the name of the host on which you installed Maps or SNA View.

port_number is the number of the port used by the web server. If port 80 is used, the port number can be omitted.

For example, if your host name is host.cisco.com, and the port is 8080, users would type:

http ://host.cisco.com:8080/

If your host name is host.cisco.com, and the port is 80, users would type:

http ://host.cisco.com/

Enabling DNS Lookups for Device Queries

The doDNSSearch variable in the cwbinit file lets you specify that a domain name server (DNS) lookup will be done for queries to routers during discovery and polling. For example, using DNS lookup, a device that was discovered as heritage.cisco.com could also be referred to as heritage. You can set this variable so that you can enter a different name that will be resolved by a DNS lookup. This variable is used when you do the following:

Discover devices with the Maps and SNA View web interface
Use the Administration program to discover, rediscover, and add devices
Use the cwb start cwbdiscover command
Use discovery or add devices in the Maps Motif application
Use the web interface that relies on cwbsnamapsd to provide updated information

The following new section of the cwbinit file provides the doDNSSearch variable:

# *****************************************************************

# boolean value is used by both the cwbsnamapsd server process 

# and other processes such as cwbadmin, cwbdiscover, dlsw and rsrb to 

# add devices to the database.

# When adding a device to the database, this value is used to decide 

# whether to do a DNS lookup on the name of the device being added,

# storing the DNS name in the DNS database table.

#

# cwbsnamapsd uses this value to decide whether to do a DNS lookup on

# a device name supplied in a user's request, if the request could

# not be satisfied with a device name or IP address lookup.

# The default value is "false", DNS lookups are not enabled. Set this

# value to "true" to enable DNS lookups.

doDNSSearch = false

You can set the doDNSSearch variable in the cwbinit file to true to discover and query routers by any valid name. Now you can enter the discovered name, a valid IP address, or any valid name for the router. For example, you could enter cwb-c5 in the input field for a DLSw focus view even if the router was discovered as cwb-c5.cisco.com. To enable domain name server lookup for routers, change the doDNSSearch value to true:

doDNSSearch = true

The DNS lookup is performed when the router is added to the database and any time a device cannot be found by the discovered name or IP address. This lookup might impact performance.

Note After you change the doDNSSearch parameter, you should stop and restart cwbsnamapsd.

Changing the Local Workstation IP Address or Host Name

During installation, the CiscoWorks Blue products save the host name of the workstation in a set of files for use during processing. If you later change the host name of the workstation, you must also change the host name in those files.

To change the host name, use the following procedure:

Step 1 Use the following command to stop all CiscoWorks Blue processes:

: /opt/CSCOcb/bin/cwb stop all

Step 2 Change the host name in the following files:

/opt/CSCOcwbC/classes/com/cisco/nm/cmf/kubit/process/

PMInstall.properties
displayMain.properties
procMgrServer.properties
processCLI.properties

/opt/CSCOcwbC/classes/com/cisco/nm/cmf/kubit/logger/ logger.properties
/opt/CSCOcwbC/etc/

Services.conf
runprocess

/opt/CSCOcwbC/apache/etc/httpd.conf
/opt/CSCOcwbC/db/ctlibs/interfaces

Step 3 Use the following command to restart all Cisco Works Blue processes:

: /opt/CSCOcb/bin/cwb start servers

The CiscoWorks Blue products do not include the local workstation's IP address in any of its files, so you can change without impact.

Table of Contents