|
This chapter provides information on detecting and correcting problems with a CiscoWorks Blue application on UNIX workstations.
This chapter includes the following main sections:
When you have isolated an error to one of the CiscoWorks Blue applications, typically you notify the Cisco TAC of the problem. Before you call the Cisco TAC, use the cwb tac command to collect the appropriate diagnostic data and zip it for transmission to Cisco.
To collect and zip the diagnostic data, enter the following commands:
The cwb tac command copies information from key files and from the CiscoWorks Blue database, and packages it in the following file: /usr/tmp/cwbtac_hostname_index.tar.Z
hostname is the actual hostname. If you set the environment variable CWB_TAC_CLIENT_ID to some value, then the hostname should be the value of this variable.
index is the next available counting number, starting with 1, for the first execution of cwb tac. The index value for the second execution of cwb tac is 2, and so on. This number is generated by looking at the existing file names; therefore, if you delete a file or change the hostname value, the counting restarts at 1. For example:
Submit this file, along with any other pertinent information, when you open a case with the Cisco TAC.
The cwb tac command lets you specify a directory for saving the command output.
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.
If the application fails to operate correctly, perform the generalized diagnostic tasks as the root user. The diagnostic tasks are described in the following section.
If you are collecting data for TAC and osfind displays the following exception error message, you can ignore the message:
VTAM provides customers with the ability to define additional information about dynamic PUs by using the ISTEXCCS configuration exit. This exit can select which type of information it will receive from VTAM and can elect to receive information on dynamic or static resources. The exit manager provided with the CiscoWorks Blue products may incorrectly drive customer exits with information the exit did not request from VTAM.
For example: A customer exit registers to receive only information on dynamic resources may receive information on static resources once the CiscoWorks Blue products have been installed on the system.
Customer can modify their exit to ignore unrequested types of resources.
During installation, you are prompted to select an installation directory. If you do not accept the default directory and choose to create a new directory, use valid naming conventions, such as 8-character names without any spaces. An error can occur in which the installer indicates the directory name is invalid but it still creates the directory.
Informational messages, NSP040 and NSP041, can appear indicating that physical units (PU) are missing or are displayed incorrectly. These messages are provided by the NSPOPEN application and appear in the mainframe system log. SNA View determines the underlying resources used to connect these PUs to the mainframe.
For more information on these messages, see Chapter 6 in CiscoWorks Blue Maps and SNA View Mainframe Installation Guide.
In certain cases, CiscoWorks Blue SNA View is unable to collect status changes dynamically on certain types of logical units (LU). Status information on dynamically-defined LUs is collected only when a host discovery is requested or a VTAM message has indicated a state change has occurred on the PU.
To maintain information on dynamic LUs, you can recycle the host connection by using the stop cwbhcid and start cwbhcid commands. Or you can set up the host connection to periodically activate (v net,act,id=puname) PUs that support dynamic LUs.
Customers can create PUs dynamically without using the ISTEXCCS exit to define additional information on these types of PUs. In this case, the CiscoWorks Blue exit may incorrectly act as the primary exit and reject the creation of the PU.
None. Contact TAC to install the latest version of CiscoWorks Blue exits that support this configuration.
The status of an LU is incorrect in a Session Connectivity page. The CiscoWorks Blue SNA Resource Information page produces session lists that contain the status of LUs at the time the request was issued. If the status of the affected LU changes while either the Session List or Session Connectivity page are displayed, the changed status of the LU is not updated and displayed.
You can click the Reload button from the Session List or the Session Connectivity page to update the LU status or you can re-issue the entire request from the SNA Resource Information page.
In some cases, CiscoWorks Blue SNA View may provide incorrect information on switch PUs. This problem appears as PUs displayed with incorrect or incomplete session path information. In addition, the NSPOPEN mainframe application will generate messages NSP040 and NSP04 to the system log for these resources. These messages are generated when the CiscoWorks Blue ISTEXCCS exit fails to collect the necessary information on the switched resources.
This exit failure can occur when a customer exit is present and is being used to define additional information on dynamic PUs. If the customer exit provides a vector to define in which major node to create the new PU, the CiscoWorks Blue exit may reject the processing for this PU.
None. Contact TAC to install the latest version of CiscoWorks Blue exits that support this configuration.
An early release of HPOV, version 6, might set the SNMP port to 8161 in the services file. This port number change causes other SNMP-based applications, such as CiscoWorks Blue Maps and SNA View to fail.
You can use the following workarounds:
Step 2 Change the SNMP port from 8161 to 161. Or apply the latest HPOV consolidated patch.
In some cases, TCP/IP failure on the mainframe requires that you restart the NSPOPEN application. This problem can occur only for those using TCP/IP. If you are using LU 6.2, you can ignore this problem.
You can automate NetView to detect a failure in TCP/IP and issue the command to stop NSPOPEN. You can automate NetView to detect when TCP/IP is restarted and issue the command to start NSPOPEN.
If you want to use the Tools menu in the Administration application to collect diagnostic data for TAC, but are unable to launch the Administration application, use the following workaround:
Step 2 Change the directory to the installation directory by entering the following:
Step 3 Enter the following command:
If you installed CiscoWorks 2000 and then CiscoWorks Blue in the same shell on UNIX systems, you can receive an error in which CiscoWorks Blue points to the CiscoWorks 2000 database. If this error occurs, the SQLAnywhere DB processes will not start and you will receive the following message:
To recover, exit the shell in which you installed the applications and run the cwb stop all command followed by the cwb start servers command. This action will point CiscoWorks Blue to the appropriate database and start the servers.
If you are unable to start the Process Manager, if you get "out of space" errors trying to start other CiscoWorks Blue processes, or if you get java exceptions with the message "out of memory," you might need more physical memory, or to swap space in the workstation. Alternatively, especially on HP-UX because of low defaults, try increasing the kernel parameters beyond the minimal values required by Maps and SNA View.
Use the Process Manager client (cwb start ProcMgrClient) or launch from the Administration application to verify that all required processes are running.
Use the cwb show status command as a UNIX command line alternative to using the PM client. On UNIX workstations, use the cwb show status command in the /opt/CSCOcb/bin directory to verify that all the servers and processes are active:
You can then use the cwb start command to start any servers or processes that are not running, and you can start the Process Manager client to monitor them, as described in "Monitoring and Controlling CiscoWorks Blue Applications."
Use the Message Log Client (cwb start MsgLogClient) or launch the Message Log Client from the Administration application to view messages as they are logged by CiscoWorks Blue processes.
If you have not already started the Message Log client, you will have to view these messages in the message log files in /opt/CSCOcb/logs on UNIX workstations.
Use the cwb verify command in the /opt/CSCOcb/bin directory on UNIX workstations or launch the verification tool from the Administration application to verify that all the installation tasks were completed successfully.
While starting the web server, an error may occur in which CWBHTTPAdapter or CWBDBAdapter does not start. However, after automatic retries, the CWBHTTPAdapter or CWBDBAdapter process starts.
If the adapters start after some automatic retries, this errors indicate a temporary condition that has been automatically corrected.
The Process Manager is running, but when you issue the cwb show status command, the output shows all CWBlue processes in the Initial state whereas the CWBMsgLogServer is in the Starting state. The MsgLogServer gets the following message during startup:
This message is followed by a detailed CORBA System Exception information.
The problem appears to be a third-party package error. A workaround might be available by changing the localhost entry in the /etc/hosts file. Check the /etc/hosts file. The localhost entry should be the first uncommented entry in the /etc/hosts file as shown in the following examples:
To make the localhost entry the first entry, change the /etc/hosts file as shown below:
Step 2 Edit the /etc/hosts file.
Step 3 Either add this line as the first entry or move this line to the first entry.
Note If this entry exists in the file, there might be additional aliases on this line, before or after the localhost entry, such as the loghost alias. Keep the line intact when you move it to the first entry position. |
Step 4 Stop all servers:
Step 5 Start all servers:
This section describes some general DLSw and RSRB troubleshooting procedures for initial problem resolution for those using UNIX workstations, and then lists specific symptoms and possible remedies.
If there is an SNMP error while requesting information from the router, log on to the router and check for the following command in the current configuration:
The read_community_string should match the read community string used by Maps. You can check and edit this value by clicking a router icon with the right mouse button, and then selecting Edit > Modify.
The default SNMP server packet size is 1500. If the packet size is too low, then some commands might fail. If commands fail, you can raise the packet size to 8192.
You can use the Maps application menu bar to rediscover, add, or delete the router, as shown below.
If a trap occurs, but the status change is not reflected in the map, check the router configuration, as described in the "Configuring Trap Destinations in Cisco IOS Routers" section and use the Process Manager to see the status of the cwbtrapd process.
For those using UNIX workstations, Figure 11-1 lists symptoms that your DLSw or RSRB application might demonstrates and refers you to various chapter sections for diagnostic techniques to resolve the problems.
If the RSRB or DLSw map is blank, synchronization with the network management system or seed file might have failed. Ensure that network devices were discovered by the network management system.
If a DLSw key routers view is blank, select Edit > Key Devices from the menu bar to ensure that you have designated routers as key devices in the seed file. If the key routers view is still blank, select View > Global to display a global view.
SunNet Manager maintains a separate device database for each user. In this case, you must use the RSRB or DLSw application from the username whose database you want to synchronize.
Also, you can try logging in to the Sybase server to check whether the devices in the seed file are also in the database. The following procedure describes how to check the database with the isql command.
If the source command produces errors, you must manually set the database environment variables as they are set in the /opt/CSCOcwbC/db/CSCOcwb/dbenv script.
Step 2 Then issue the isql command:
You should see all devices that are in your seed file.
If a device fails to appear on the map, the discovery daemon might have failed. Perform the following steps:
Step 2 If the device named device_name is not in the Devices table, check for its existence in the network management system database or the seed file. If the device is in the Devices table, verify that it is running the correct release of Cisco IOS software and that you can ping the device from the network management system. Select Edit > Modify and enter the device name and correct read community string.
Step 3 Use Edit > Add Device to add the device to the map. The RSRB or DLSw application attempts to discover a newly added device automatically.
Step 4 Use the ping command to verify that you can locate the device.
Step 5 Check whether SNMP is configured on the router and verify the read community string. SNMP must be configured on the router for DLSw and RSRB.
Step 6 Check the access list in the router configuration to verify that the IP address can be reached.
If a device appears on the map but the information about it appears to be out of date, use the following procedure to delete the obsolete information:
Step 2 Use the Process Manager to reset the poller and monitor daemons.
If the problem remains unresolved, ensure that the poller is active. If a network management system is present, ensure that both the network management system trap daemon and the cwbtrapd process are active. For more information, see the "DLSw and RSRB Error Messages on UNIX Workstations" section.
If the nodes in your network are not synchronized with your database, try one of the following procedures.
Step 2 Select Layout > See All.
Step 3 Select all the devices on the map.
Step 4 Select Edit > Rediscover Device(s).
Use the following commands to remove all entries from the database tables:
For information about the cwb clear db command, see "CiscoWorks Blue Commands and Processes." Rerun the discovery processes to repopulate the database tables. In Maps, select Administration > Discover from the menu bar.
For those using UNIX workstations, the following error messages are issued to the message box in the RSRB and DLSw Motif applications and to the message log:
Explanation
RSRB or DLSw either cannot get to the data server or cannot log in.
Action
Check the environment variables in /opt/CSCOcb/etc/runprocess; try to log in to the database server from a separate window and check the transaction log. Then try to restart the application.
Current view_name view type conflicts with reserved name prefix
of file.
Save map file filename Failed!
view_name is the name of the view that you are trying to save to a file:
filename is the name of the file in which you are trying to save the view.
Explanation You tried to use File > Save As to save a map to a file, but the file prefix is one of the reserved Maps file prefixes. Maps reserves the following file prefixes:
Action Do not use File > Save As to save to a file with one of the reserved prefixes.
Database initialization failure.
Explanation
RSRB or DLSw failed to connect to the network management system database before starting the discovery daemon.
Action
Verify the integrity of the network management processes. If you have HP OpenView or NetView installed, you can use the ovstatus command, which typically is located in the /usr/OV/bin or /opt/OV/bin directory. The ovstatus command displays the status of daemons and processes. You can ensure that all network management daemons are running, and restart those that are not.
Explanation
When you tried to add a device to the database, the device you specified already had an entry in the database.
Action
You can delete the device and add it again using the Edit item on the Motif menu bar or using the Administration application.
device_name no such device.
device_name failed to add.
Explanation
The device_name is not known to the operating system or to the domain name server.
Action
Try to ping the device. If that fails, check for the correct case. Check to see whether the domain name server has been configured. Verify that the device name is in the /etc/hosts file.
Explanation
RSRB or DLSw failed to query network devices.
Action
If you have HP OpenView or NetView installed, you can use the ovstatus command, which typically is located in the /usr/OV/bin or /opt/OV/bin directory. The ovstatus command displays the status of daemons and processes. You can ensure that all network management daemons are running, and restart those that are not running.
Explanation When switching views, for example from global view to focus view, a correct filename and format is read, but the view type in the file is wrong. For example, the map is changing to a focus view, but the view type says it is a virtual ring view.
Action Delete or move the particular map file.
Explanation
RSRB or DLSw does not know the community string for this router.
Action
Use the Edit > Modify menu item or the Administration application to set the correct community string.
No response from update server.
Explanation
The monitor daemon is not running.
Action
Use the Process Manager or the cwb start command to start the monitor daemon.
Explanation
A copy of the monitor daemon is already running on the workstation, or some other program is using this port.
Action
If another copy of the monitor daemon is already running, this is an informational message. No action is necessary. If another program is using this port, you can edit the runprocess script and change the setting of the -u monitor port option for the case dlsw or case rsrb sections.
Reading map file filename. Incorrect
format or version.
Open file Failed!
Explanation You are reading a map file with an incorrect format or version. This happens when a map file format changes between versions of Maps and an attempt is made to try to read the incompatible format.
Action Delete or move the particular map file.
Explanation
The SNMP query to a device was not successful. Either the device is no longer reachable from the network management workstation or it is not responding to the SNMP query.
Step 2 Use the telnet command to log in to the router to check the router configuration. Ensure that the router is configured for the protocol you are using and configured for SNMP, and that the read community string is correct.
This section contains the following information:
The LU and PU processes relay operating and error messages to the Message Log Server in which the management platform was started. You can view these messages, as they are logged, using the Message Log client.
All SNA host LU and PU errors are in the following form:
xxx is a 2- or 3-letter message category.
nnn is a 3-digit numeric identifier.
This chapter provides a detailed description of each message and, if appropriate, a recommended user response.
This section describes problems related to communications between the mainframe and workstation components in TCP/IP and LU 6.2 environments.
If the Host Connection Interface or the Host Command Server will not initialize successfully, perhaps due to communications problems between the workstation and mainframe. Perform the following procedures.
Step 2 Verify the network connection from the workstation to the mainframe by issuing a TCP/IP ping command.
Step 3 Verify that the SVMF_HCI_AGENT_PORT and the SVMF_CMDS_AGENT_PORT configuration parameters (in the /opt/CSCOcb/etc/svopen_config_domain file) are set correctly on the workstation. These configuration parameter values must match the parameter card values for the TCP subtask on the mainframe.
Step 2 Verify that another workstation is not connected to the TCP subtask. Issue the F NSPOPEN,SHOW CONN command to confirm that there is no connection for the relevant TCP subtask. If another workstation is connected, choose a different pair of port numbers and reconfigure.
The best source of information for debugging LU 6.2 problems is the job log of the CiscoWorks Blue mainframe component. It will contain error messages written by the SERVER subtask.
For LU 6.2 connections, verify that the associated SERVER subtask is active. Issue the F NSPOPEN,SHOW TASK command to confirm that the SERVER subtask's states are UP. See the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for more details on problems and solutions with the SERVER subtask and LU 6.2 communications.
You can find helpful information for troubleshooting LU 6.2 connectivity problems in audit message logs, error message logs, and link traces.
The SNA communications software generates audit and error messages during operation and writes them to files specified during configuration. See the product documentation for more details on specifying log files and message severity levels.
When you start tracing, tracing information is written to the trace files (*.tr) in addition to the diagnostic messages written to the audit and error logs. See the product documentation for more details.
Note You must have root user authority on the workstation to complete many of the tasks described here. |
Problems relating to discovery and status management are described in the following sections:
Discovery is a process that gathers the information on PUs and LUs for a specific domain and stores that information in the CiscoWorks Blue database. The following problems can occur:
The cwbhmond process receives updated PU information from the mainframe when a status change occurs or when a new PU is discovered. If status updates are not being received at the workstation (that is, when the status of a PU changes but the change is not reflected when the PU information is displayed), messages might not be flowing from VTAM to the mainframe application. Ask your mainframe administrator to use the following commands:
This problem is described in the "Troubleshooting the Mainframe Application" chapter of the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide.
Configuration file errors are common sources of application failures. Each managed SNA domain has a configuration file in the /etc directory. Each domain configuration file name is in the format svopen_config_ domain. These configuration files contain parameters that affect almost every aspect of SNA host functionality. Several configuration file parameters, if not correctly set, can keep workstation processes from executing properly.
Note Workstation processes retrieve parameters only once (during initialization). Therefore, after you make modifications to a configuration file, stop and restart the processes for the changes to take effect. |
The following sections describe the configuration file parameters and the problems that can arise if they are not set correctly.
SVPATH is the path to the home directory on UNIX (/opt/CSCOcb/snahost).
If this variable is not properly set to the home directory, as defined during installation, workstation processes cannot locate necessary help, log, and parameter files. Most workstation processes will not initialize without a valid SVPATH parameter value.
SVMF_AGENT_ADDR is the TCP/IP host name of the IBM mainframe running the mainframe application.
If this configuration parameter is not properly set, the Host Connection Interface and the Host Command Server will fail to initialize when TCP/IP is for communications between mainframe and workstation.
For example, if the value of this configuration parameter is mickey, but mickey is not a valid machine on the network, you will get the following error messages written to the Message Logger when you attempt to start the Host Connection Interface or Host Command Server:
However, if mickey is a valid machine name, but the TCP subtask of the mainframe component is not currently running, these error messages are written to the message log if the IPCTrace message category is enabled:
Similar error messages will be generated if the SVMF_HCI_AGENT_PORT and SVMF_CMDS_AGENT_PORT values are not set properly. These configuration parameters must match the ports defined on the mainframe program's TCP parameter card. See the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for more details.
SVCMD_TIMEOUT is the time out period, in seconds, for mainframe commands.
If this configuration parameter is set too low, then mainframe commands issued from the workstation can time out. Try to increase this parameter value.
The default value of this configuration parameter is 30 seconds. In most cases this value is sufficient. However, when the workstation-to-mainframe connection is very slow, you might need to increase this value. If this configuration parameter is set too low, the following error messages will be issued to standard error:
If increasing this configuration parameter does not prevent commands from timing out, ensure that the Host Connection Interface and Host Command Server are active. If they are inactive, activate them. If they are active, check the mainframe performance group, which might be set too low. See your mainframe system administrator or see the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for assistance.
The server and client processes use this port for socket communications. Ensure the port is not used twice, and that it is not used by some other process.
The Host Connection Interface communicates with the VTAM and MVS Servers, and the cwbhmond process, over these defined ports. Ensure the port is not used twice and that it is not used by some other process.
These configuration parameters define the port values used for TCP/IP communications between the workstation and mainframe components. The Host Connection Interface and Host Command Server use these port values to establish socket communications with the TCP subtask on the mainframe. The port values specified in the configuration file on the workstation must match those defined on the TCP subtask parameter card in the mainframe component's SYSIN parameter card file. See the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for more information on the TCP subtask and SYSIN parameter card file.
If these configuration parameters do not match those defined on the mainframe, the workstation application will generate the following error messages on standard error when starting the Host Connection Interface and Host Command Server:
This section explains the messages generated by the workstation program. Each message number ends with one of the following error codes:
CWC0001E process failed calling function,
reason: explanation
process is the process or routine.
function is the system socket function.
explanation is the text that explains the error.
Explanation A process has called a system function and that function has failed. The reason is given in the explanation field. In most cases, a system function essential to the process is missing. Without it, the process cannot continue and will exit with an error.
Action If the explanation is not clear, check to make sure the configuration file for that particular domain is defined correctly. In some cases, the error might be caused by the system load, and the process will run properly if restarted.
CWC0002E Unable to open protocol method
socket.
protocol is the socket protocol.
method is either the stream or datagram method.
Explanation A process was unable to open a socket type with the indicated communication method. The process that attempted to open the socket will terminate.
Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0003E Unable to bind socket.
Explanation A process was unable to bind an open socket. The process that attempted to bind the socket will terminate.
Action In some cases, the error is caused by the system load, and the process will run properly if you restart it.
CWC0004E Unable to set socket to
non-blocking mode.
Explanation A process was unable to set the mode of a socket to nonblocking. Processing continues.
Action No user action is required.
CWC0005E Error on listen for socket
connection.
Explanation A process was unable to activate a socket for connection. The process that attempted to listen for the socket connection will terminate.
Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0006W Socket connect failed, will retry
momentarily.
Explanation A process attempted to connect to another process via socket communications and failed. In most cases, the other process has not had enough time to initialize and establish the socket properly. The process will pause briefly and then reissue the connection attempt.
Action No user action is required.
CWC0007E Socket connect failed, no retry
will be attempted.
Explanation One process attempted to connect to another process via socket communications and failed. The process that detected the error will terminate.
Action Make sure that both processes involved in the connection are executing. Make sure the configuration file for that particular domain is correctly defined. In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0008E Unable to get socket option:
socket.
socket is the specific socket option.
Explanation A process attempted to obtain the socket option and failed. The process that detected the error will terminate.
Action Attempt to restart the failing process.
CWC0009E Unable to set socket option:
socket.
socket is the specific socket option.
Explanation A process attempted to set the socket option and failed. The process that detected the error will terminate.
Action Attempt to restart the failing process.
CWC0010E process failed reading HCI
socket, reason: explanation.
process is the server process.
explanation is text that explains the error.
Explanation A server attempted to read from the Host Command Interface and failed. The server will notify its clients and then terminate.
Action Verify that the Host Command Interface server is active. In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0011E Failure reading process client
UDP socket.
process is the client process name.
Explanation A server process failed while reading a client's socket. The server process will terminate.
Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0012E Failure reading process server
UDP socket, entire message not received.
process is the server process.
Explanation A client process attempted to read from a server process and received only a partial message. The detecting client process will terminate.
Action Verify that the client's server process is still active and functioning properly. In some cases, the error is caused by the system load, and the process will run properly if restarted.
CWC0013E Failure writing to process client
UDP socket.
process is the client process.
Explanation A server process failed while writing data to a client process. A server process will continue processing if a write to a client process fails.
Action Verify that the client process is still active and, if not, restart the client process repeating the desired action.
CWC0014E Failure writing to process client
UDP socket, entire message not sent.
process is the client process.
Explanation A server process failed to send the entire data buffer to an SNA host client process. A server process will continue processing if a write to a client process fails.
Action Verify that the client process is still active and, if not, restart the client process.
CWC0015E Failure reading SView/Open
Mainframe Message Server, reason: explanation.
explanation is text that explains the error.
Explanation The Host Connection Interface failed while attempting to read from its socket connection with the Mainframe Message Server. The Host Connection Interface server will exit, causing the termination of the majority of all SNA host processes.
Action Review text explanation of the error and verify TCP/IP support between the workstation and the mainframe in question.
CWC0016E Lost connection with SView/Open
Mainframe Message Server.
Explanation The Host Connection Interface lost connection with the SNA host Mainframe Message Server. This message indicates that some vital process or processes on the mainframe have terminated or become unavailable. The Host Connection Interface server will exit, causing the termination of the majority of the processes.
Action Verify the status of the mainframe application and the TCP/IP support.
CWC0017E process has exited due to read
failure on HCI connection.
process is the server process.
Explanation A server process exited because it received an error return code when it attempted to read from the Host Connection Interface socket. The server process will terminate.
Action Verify that the Host Connection Interface for that domain is active.
CWC0018E process has exited due to loss of
connection with the HCI.
process is the server process.
Explanation A server process exited because it lost connection with the Host Connection Interface. This message indicates that the Host Connection Interface process has terminated and is no longer available. The server process terminates.
Action Verify that the Host Connection Interface for that domain is active.
CWC0019E HCI failed sending command
response to the Command Server.
Explanation The Host Connection Interface could not send the response, to a mainframe command, back to the Host Command Server.
Action Ensure that the Host Command Server process is active on the workstation. If it is not active, start the process. If it is active, stop and restart the process.
CWC0020E process failed calling name with
errno: error_number
process is the process or routine.
name is the LU 6.2 system routine name.
error_number is the error return.
Explanation The process or routine failed calling the LU 6.2 system routine and returned an error code. The process that detected the error will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0021E Failure opening direction LU 6.2
conversation.
direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to open the LU 6.2 conversation with the mainframe system. The process that detected the error will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0022E Failure allocating direction LU
6.2 conversation.
direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to allocate the LU 6.2 conversation with the mainframe. The process that detected the error will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0023E Failure reading over direction LU
6.2 conversation.
direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to read from the LU 6.2 connection that exists between it and the mainframe code. The process that detected the error will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0024I Control received value from
mainframe signals termination.
Explanation The Host Connection Interface or Host Command Server process received a code format value from the mainframe, indicating that termination was necessary. The detecting server process will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0025E Failure confirming conversation
LU 6.2 conversation read.
conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server failed to confirm that the conversation was read as requested by the mainframe program. The process that detected this failure will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
CWC0026E Failure sending over conversation
LU 6.2 conversation.
conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server detected a failure while attempting to send over the LU 6.2 conversation with the mainframe. The process that detected this failure will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 SNA profiles are configured properly.
CWC0027E Failure closing conversation LU
6.2 conversation.
conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server detected a failure while attempting to close the LU 6.2 conversation with the mainframe. The SNA host process that detected this failure will terminate.
Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 SNA profiles are configured properly.
CWC0028I process initialized successfully
for domain name.
name is the defined domain name.
Explanation A process has initialized successfully for the domain. The SNA host process will continue with execution.
Action No user action is required.
CWC0029E process started with invalid
argument count.
Explanation A process was started with an incorrect number of command line arguments. The process will terminate.
Action Verify that you entered the correct options. If you have entered the correct options on the command line or in the /opt/CSCOcb/etc/runprocess script. Use the cwb tac command and notify the Cisco TAC.
CWC0030E Domain name must be passed in to
the process.
Explanation A process was started without the domain name passed as an argument. The process requires the domain name argument to determine the proper configuration file to use. The process will terminate.
This message is displayed if the cwbhmond process is not given a domain name on the command line as its first command argument.
Verify that the following UNIX files were not incorrectly modified:
CWC0031E Invalid transaction program name
executable used to start HCI.
Explanation The Host Command Interface was started with an invalid transaction program name. The transaction program name did not have the domain name (for which the servers are being started) appended to the executable name. The process that detected this failure will terminate.
Action Verify that the following UNIX files were not incorrectly modified:
CWC0032E process encountered invalid value
for configuration parameter parameter_name
parameter_name is the Maps SNA host configuration parameter.
Explanation An SNA host process was started but the specified configuration parameter is set incorrectly. The specified configuration parameter is critical to the operation of the process. The process that detected this failure will terminate.
Action Set the configuration parameter with the proper value and restart the process.
CWC0033E process needs the variable
environment variable set properly.
variable is the environment variable.
Explanation A process was started without the environment variable set. The specified environment variable is critical to the operation of the process. The process that detected this failure will terminate.
Action Set the environment variable with the proper value and restart the process.
CWC0035E process failed calling function
process is the process or function.
Explanation A process or function has failed in its call to a function. In most cases the process or function will terminate.
Action Normally, more detailed error messages will accompany this message. Review all generated error messages in an effort to resolve the error.
CWC0036E process failed calling function
with rc: rcnumber
process is the process or function.
rcnumber is the integer return code.
Explanation A process or function has failed in its call to a function and received a return code. In most cases, the process or function will terminate.
Action Normally, more detailed error messages will accompany this message. Review all generated error messages in an effort to resolve the error.
CWC0037E process failed calling function,
reason: message
process is the process or function.
message is the text of the error message.
Explanation A process or function has failed in its call to a function and received an error message. Usually, the process or function will terminate.
Action Normally, more detailed error messages will accompany this message. Review all generated error messages.
CWC0038I process for domain domain will
terminate after waiting for other processes to end.
process is the process or function.
Explanation The listed process will terminate as soon as its dependent processes terminate. Normally other messages will accompany this message to explain why the process is ending.
Action No user action is required.
CWC0039W An instance of process for domain
domain is already running.
process is the process or function.
Explanation A process or function is already running for the domain. Perhaps you tried to start a daemon (such as cwbhcid, cwbhcmdd, or cwbhmond), but it is already running. The process will not be restarted.
Action No user action is required.
CWC0040E process failed to open file path,
reason: message
process is the process or function.
path is the full file path, including the file name.
message is the text of the error message.
Explanation A process or function has failed to open a file and received an error message. The process that detected the error will terminate.
Action Check file permissions to ensure that the process has the ability to read and write to the file.
CWC0041W Attempt to connect to process
failed, retrying.
process is the process or function.
Explanation An attempt to setup a socket connection to the specified daemon failed.
Action No action is necessary. An attempt to connect will be retried.
CWC0042E Memory allocation failure, check
available memory.
Explanation A process attempted to obtain more memory from the operating system and failed. The process that detected the error will terminate.
Action Verify that available memory requirements on the workstation have not been exceeded.
CWC0043E Unable to obtain host TCP/IP
address from host name: host.
Explanation A process attempted to get the TCP/IP address for the TCP/IP host machine and failed. The process that detected the error will terminate.
Explanation If the machine uses the /etc/hosts file to resolve TCP/IP addresses, make certain that the specified host name has an entry. If the machine uses a name server to resolve addresses, verify that the name server knows the host name.
CWC0044W Waiting for previous instance of
process for domain domain to end.
process is the name of the process.
domain is the name of the domain.
Explanation A previous instance of the indicated daemon is still running.
Action No action is necessary.
CWC0045E process for domain domain
detected an unsupported mainframe version.
process is the name of the process.
domain is the name of the domain.
Explanation The mainframe and workstation versions are not comparable.
Action Install the correct level of software on both the mainframe and workstation.
CWC0046E process for domain domain failed
to receive a response for the version request.
process is the name of the process.
domain is the name of the domain.
Explanation The workstation did not receive a response from the mainframe for the version requested.
Action Ensure that the correct level of mainframe software is installed and running on the mainframe. You might need to adjust the mainframe command time out value (SVCMD_TIMEOUT).
CWC0047E process for domain domain lost
mainframe connection; will try to re-establish. Code code.
process is the name of the process.
domain is the name of the domain.
Explanation The workstation lost its connection to the mainframe.
Action No action is required. The workstation periodically will try to reestablish a connection to the mainframe.
CWC0048I process process has exited.
process is the process that exited.
Explanation A process has terminated.
Action Review any generated error messages to determine the cause of the process termination if the termination was abnormal.
CWC0049I process process of domain name has
exited.
process is the process that exited.
A process of a domain has terminated.
For example, if the cwbhmond process fails to initiate a session with the Sybase application program interface (API), this error message is logged.
Action Review any generated error messages to determine the cause of the process termination if the termination was abnormal.
CWC0050I process process of domain name has
exited with code code.
process is the process that exited.
name is the defined domain name.
Explanation The named process has exited.
Action Review any generated error messages to determine the cause of the process termination if the termination was abnormal. If the program termination was not intended, examine these messages to resolve the problem.
CWC0051W Status and/or Discover task not
active on mainframe.
Explanation The Status and Discovery subtasks on the mainframe are not running. No SNA correlation information is being sent from the mainframe.
Action Ensure that the mainframe STATUS and DISCOVERY subtasks are configured and active.
CWC0052E Invalid buffer size for process
message. Domain: domain
Explanation The named process has received a invalid buffer. The process will end.
Action Use the cwb tac command and notify the Cisco TAC.
CWC0053E Invalid buffer structure. Domain:
domain
Explanation An invalid buffer was received. The process will end.
Action Use the cwb tac command and notify the Cisco TAC.
CWC0054W Connection to command server
daemon failed for domain.
Explanation The Host Connection Interface was unable to connect to the Host Command Server.
Action Other messages might accompany this message. Attempt to resolve the problem based on these messages. Ensure that the product was properly installed and configured. If the error persists, use the cwb tac command and notify the Cisco TAC.
CWC0055W Connection to Status Monitor
daemon failed for domain domain.
Explanation The Host Connection interface was unable to connect to the Status Monitor.
Other messages might accompany this message. Attempt to resolve the problem based on these messages. Ensure that the product was properly installed and configured. If the error persists, use the cwb tac command and notify the Cisco TAC.
CWC0056E Invalid message type received by
process1 from process2: type
process1 and process2 are processes.
Explanation A process received an invalid message type from another process. The invalid message will be ignored, and processing will continue.
Action If this message persists, note the message contents, use the cwb tac command, and notify the Cisco TAC.
CWC0057W Client is not currently
registered, filter request rejected.
Explanation A client process attempted to send a filter request to a server process to which the client process was not properly registered. The filter request was rejected for this reason by the server.
Action No user action is required.
CWC0058W Client is not currently
registered, command not submitted to mainframe.
Explanation A client process attempted to send a mainframe command to the Host Command Server process to which the client process was not properly registered. Host Command Server will reject the client's mainframe command request.
Action No user action is required.
CWC0059W Maximum number of clients already
registered, request rejected.
Explanation A client process attempted to register with a server process, but the server process already had the maximum number of 100 clients it was permitted to serve. The server process rejected the client's request.
Action No user action is required.
CWC0060W Timed out waiting for server
registration response.
Explanation A client process issued a registration request to its server process and no registration response has been received by the client in the provided time. The client will either continue to wait or exit depending upon the user action chosen.
Action You can continue waiting for the registration response or exit the client process. Verify that the proper server process is active and that the configuration parameters for the appropriate domain are correct.
CWC0061W Timed out waiting for command
response from Command Server.
Explanation A client process issued a registration request to the Host Command Server process and no registration response has been received by the client in the provided time. The client will either continue to wait or exit depending upon the user action chosen.
Action Verify that the Host Command Server (HCS) process on the workstation is active. If it is not active, start it. If it is active, re-issue the failing command.
CWC0062E process error message: message.
process is the server process that detected the error.
message is the text of the error message.
Explanation The server process detected a critical error and notified the client of the error.
Action Review the error message to determine the cause of the error and correct the problem.
CWC0063E Verify that the HCI and Command
Servers are active.
Explanation The process has detected a possible problem with connection to the mainframe, indicating that the Host Command Interface and Host Command Server might have terminated.
Action Ensure that the Host Command Interface and Host Command Server are active and functioning properly. If they are not active, review all error messages and restart them once any problems have been corrected. If they are still active, attempt to rerun the failing process.
CWC0064W Command not processed. Verify
that the HCI and Command Servers are active.
Explanation A mainframe command was issued but the mainframe application was unable to process it. The Host Command Interface or Host Command Server, or both might be no longer active or function properly. No further processing for the issued command will take place.
Action Verify that the Host Command Interface and Host Command Server are up and functioning properly. If they are not active, restart them. If they do not restart, use the cwb tac command and notify the Cisco TAC.
CWC0065W Sybase database login failure.
Explanation The workstation application could not log in to the CiscoWorks Blue database using the ID and password defined during configuration. Either Sybase is not running, or the ID and password are invalid.
Action Determine whether the database is running on the workstation. Determine whether the ID and password, defined during workstation configuration, are correct.
This section describes some general APPN/SNASw troubleshooting procedures for initial problem resolution, and then lists specific symptoms and possible remedies.
If the APPN/SNASw application fails to operate correctly, verify that the environment variables are set in the cwbinit script according to the values in "Installing and Configuring CiscoWorks Blue."
Go to another view, then return to this view. If the problem has not cleared up, exit the application, remove the Map files again, and restart the application.
Table 11-1 lists symptoms that your APPN/SNASw application might demonstrate and refers you to some diagnostic techniques to resolve the problems.
Table 11-1 APPN/SNASw Troubleshooting Symptoms
If the global map is blank, you might have one of the following problems:
To resolve this problem, perform one or more of the following:
If the status of all network nodes is unknown to the application, the network topology agent could have failed, or APPN/SNASw could have been stopped in that device, or the SNMP request might have failed. Use the ping command or select Tools > PathTool from the menu bar to verify that the network topology agent is accessible. If necessary, use the telnet command to log in to the agent to start the APPN/SNASw protocol.
If APPN/SNASw cannot find a known LU, use the following procedure:
Step 2 At each node, click the right mouse button.
Step 3 Select Get Directory from the menu.
Step 4 Repeat Step 1 through Step 3 for the next node.
If a known link station does not appear in the List TGs and Links window, use the following procedure:
Step 2 Select the node on which the missing link is defined.
Step 3 Click the right mouse button.
Step 4 Select Get Local Topology from the menu.
Step 5 Reopen the List TGs and Links window to see if the link is listed. Or, set the autolocaltopo variable in the cwbinit file to ALL or NN_ONLY and restart the application.
If a known good connection appears degraded (yellow), a defunct TG number might exist in the network topology agent's database. According to an APPN/SNASw algorithm, the network topology agent will delete the defunct number within a few days. When you start the APPN/SNASw application after that deletion occurs, the connection does not appear degraded.
If the status of a port, link, or transmission group is reported incorrectly, refresh the information by using the following procedure:
Step 2 Click the right mouse button.
Step 3 Select Get Local Topology from the menu.
The following error messages are unique to the APPN/SNASw application. They are displayed in the APPN/SNASw Motif message box and written to the message log.
Current view_name view type conflicts with reserved name prefix
of file.
Save map file filename Failed!
view_name is the name of the view that you are trying to save to a file.
filename is the name of the file in which you are trying to save the view.
Explanation You tried to use File > Save As to save a map to a file, but the file prefix is one of the reserved Maps file prefixes. Maps reserves the following file prefixes:
Action Do not use File > Save As to save to a file with one of the reserved prefixes.
Database initialization failure
Explanation
APPN/SNASw failed to connect to the network management system database before discovery.
Action
If you have HP OpenView or NetView installed, you can use the ovstatus command, which typically is located in the /usr/OV/bin or /opt/OV/bin directory. The ovstatus command displays the status of daemons and processes. Ensure that all network management daemons are running and restart those that are not running.
Device name & read community required
Explanation
APPN/SNASw must send an SNMP MIB request to a node, but no device name is known for this node.
Action
If the displayed default device name is not correct, enter the correct device name and read community string. Your input also establishes the default name for future SNMP MIB requests. If you do not know the device name, or if the node cannot be an SNMP agent, click Cancel to terminate the request.
Invalid view type
Explanation When switching views, for example from global view to focus view, a correct filename and format is read but the view type in the file is wrong. For example, the map is changing to a focus view, but the view type says it is a Virtual Ring view.
Action Delete or move the particular map file.
No devices discovered
Explanation
No devices were available to be discovered.
Action
Review the device list in the seed file or network management system database so that discovery has a chance of success. Then use Administration > Discover to retry the discovery, or exit the application and restart it. In the Startup Query window, specify a topology agent that is known to be reliable.
Reading map file filename. Incorrect format or version.
Open file Failed!
filename is the name of a map file.
Explanation You are reading a map file with an incorrect format or version. This error occurs when a map file format changes between versions of Maps and you attempt to read the incompatible format.
Action Delete or move the particular map file.
View could not be retrieved
Explanation
A map view requires data that is not available to the APPN/SNASw application. Typically, this happens when you request the ports and links view but local topology is not available from the target node.
Action
If the target node can act as a topology agent, and you know its IP address or its device name and read community string, select Get Local Topology from its popup menu. Get Local Topology collects the local topology.
View may be incomplete
Explanation
An Adjacent Nodes view is shown for a node that does not have local topology information available. Only adjacent nodes learned from the global view or from local topology collection from other nodes are displayed. Adjacent EN and LEN nodes are, most likely, not shown.
Action
If this node can act as an agent and you know its IP address or its device name and read community string, collect its local topology now.
Will retry by polling
Explanation
A network topology agent has been selected but is not returning network topology information. No global map is currently available. The application will retry this agent at the network topology polling rate.
Action
Perform the following steps in order. Stop when one is successful.
Step 2 Ensure that the selected network topology agent is an APPN/SNASw network node with the APPN/SNASw MIB, and that the IP address or device name you specified is correct. If not, stop the APPN/SNASw application and restart it with a new network topology agent.
Step 3 Ensure that the APPN/SNASw protocol is active on the target agent.
Step 4 Use the ping command to see if the agent is alive and accessible.
This section presents troubleshooting techniques for the web browser.
If your web browser cannot access the web server, try one of the following:
If the web browser cannot access the web server, look at the web server's log files. The CiscoWorks Blue web server log files are /opt/CSCOcwbC/apache/var/log/access_log and /opt/CSCOcwbC/apache/var/log/error_log on UNIX. The access_log file lists all accesses to the web server. The error_log file lists individual errors in accessing the web server.
If selecting Tools > Web Browser from a Motif application fails, look at the /opt/CSCOcb/etc/runweb file and ensure that the environment variables are set correctly for your directory structure. Verify that Netscape is installed. If you installed Netscape after you installed CiscoWorks Blue, Netscape must be in the PATH.
Also, you can try turning off proxy server use at the web browser. Check with your system administrator before you do this. To turn off proxy use for the Netscape browser, for example, select Options > Network Preferences. Select the Proxies tab, and click No Proxies. Click OK and try to access the web server again.
If you cannot access the CiscoWorks Blue web pages, use the Process Manager to ensure that the CWBHTTPDAdapter is running.
If you accessed the CiscoWorks Blue web server but saw some other page, this means another web server is already using port 80. For example, when you installed CiscoWorks Blue Maps, no other web server was running, so the CiscoWorks Blue web server was configured for port 80. But later, when you started the CiscoWorks Blue web server or tried to display the CiscoWorks Blue web page, some other web server was already using port 80. If you need to use a different port, you must reinstall the CiscoWorks Blue products.
To specify port 8080 in the web browser, enter the following URL in the browser:
http:// workstation_name:8080
workstation_name is the name of the workstation where the Maps web server is installed.
If the online help for the web browser, the Administration program, the Process Manager, or the Message Logger does not launch successfully, edit the following files to ensure that the path to the Netscape executable is correct:
The installation program asks you for this path. If you enter the wrong path, the online HTML help might not work.
Posted: Thu Jul 31 16:06:26 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.