|
|
This chapter describes how to detect and correct problems with a CiscoWorks Blue application. It includes the following major sections:
When you have isolated an error to one of the CiscoWorks Blue applications, you usually 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:
cd /opt/CSCOcb/bin
./cwb tac
The cwb tac command copies information from key files and from the CiscoWorks Blue database, and packages it in the file /usr/tmp/cwbtac_X.tar.Z (where X is a number to create a unique file name). Submit this file, along with any other pertinent information, when you open a case with the Cisco TAC.
If the application fails to operate correctly, first perform the generalized diagnostic tasks, described in the following sections, as the root user.
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 may need more physical memory or 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 cwb show status command in the /opt/CSCOcb/bin directory to verify that all the servers and processes are active:
cd /opt/CSCOcb/bin
./cwb show status
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 Process Manager client (cwb start ProcMgrClient) to verify that all required processes are running.
Use the Message log client (cwb start MsgLogClient) to view messages as they are logged by the CiscoWorks Blue processes.
Use the cwb verify command in the /opt/CSCOcb/bin directory to verify that all the installation tasks were completed successfully.
The Process Manager is running, but when you issue the cwb show status command, the output shows all CWBlue processes in the Initial state but CWBMsgLogServer is in the Starting state. The MsgLogServer gets the following message during startup:
Unable to bind to Process Manager Server
This message is followed by a detailed CORBA System Exception information.
The problem appears to be a third-party package error. A workaround may 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:
# comment line in hosts file
127.0.0.1 localhost loghost
or
127.0.0.1 localhost
To make the localhost entry the first entry, change the /etc/hosts file as shown below:
Step 1 Become the root user:
su root
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.
127.0.0.1 localhost [loghost]
Step 4 Stop all servers:
/opt/CSCOcb/bin/cwb stop all
Step 5 Start all servers:
/opt/CSCOcb/bin/cwb start servers
This section describes some general DLSw and RSRB troubleshooting procedures for initial problem resolution, and then lists specific symptoms and possible remedies.
snmp-server community read_community_string RO
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 may 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 the Cisco IOS Software" section and use the Process Manager to see the status of the cwbtrapd process.
Table 11-1 lists symptoms that your DLSw or RSRB application might demonstrate, and it refers you to various chapter sections for diagnostic techniques to resolve the problems.
| For this symptom... | See this section... |
|---|---|
Device does not appear on the map | |
Incorrect device information | |
Nodes not synchronized | |
Unexpected dialog box prompt appears |
If the RSRB or DLSw map is blank, synchronization with the network management system or seed file may have failed. Ensure that network devices have been 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.
You can also 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.
First, issue the source command to set the database environment variables:
source /opt/CSCOcwbC/db/CSCOcwb/dbenv
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.
Then issue the isql command:
$SYBASE/bin/isql -Usnasuper -Psnarsrb
1> select * from snasuper.devices
2> go
You should see all devices that are in your seed file.
If a device fails to appear on the map, the discovery daemon may have failed. Perform the following steps:
Step 1 Use the isql command, as shown below, to verify the device's entry in the Sybase Devices table. This example is for a database named SNA.
$SYBASE/bin/isql -Usnasuper -Psnarsrb
1> select * from snasuper.devices where device_name=device_name
2> go
1> quit
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 the device 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.
Step 1 Select Edit>Rediscover Device(s) to rediscover the device.
Step 2 Use Process Manager to reset the poller and monitor daemons.
If the problem still has not been resolved, 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. See the section "DLSw and RSRB Error Messages" for more information.
Select all the devices on the map and rediscover them:
Step 1 Select Layout>See All.
Step 2 Select all the devices on the map.
Step 3 Select Edit>Rediscover Device(s).
Use the following commands to remove all entries from the database tables:
cd /opt/CSCOCB/bin
./cwb clear db
For information about the cwb clear db command, see the appendix "Commands and Processes." Rerun the discovery processes to repopulate the database tables. In Maps, select Admin>Discover from the menu bar.
The following error messages are issued to the message box in the RSRB and DLSw Motif applications and to the message log:
Error Message
Cannot log into the database.
Explanation
RSRB or DLSw either cannot get to the data server or cannot log in.
Recommended 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.
Error Message
Current view_name view type conflicts with reserved name prefix of file.Where:
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:
Recommended Action Do not use File>Save As to save to a file with one of the reserved prefixes.
Error Message
Database initialization failure.
Explanation
RSRB or DLSw failed to connect to the network management system database before starting the discovery daemon.
Recommended Action
Verify the integrity of the network management processes. If you have HP OpenView or NetView installed, you can use the ovstatus command, which is typically 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.
Error Message
device_name already exists.
Explanation
When you tried to add a device to the database, the device you specified already has an entry in the database.
Recommended Action
You can delete the device and add it again using the Edit item on the Motif menu bar or using the Administration application.
Error Message
device_name no such device.
Explanation
The device_name is not known to the operating system or to the domain name server.
Recommended 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.
Error Message
Discovery failed.
Explanation
RSRB or DLSw failed to query network devices.
Recommended Action
If you have HP OpenView or NetView installed, you can use the ovstatus command, which is typically 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.
Error Message
Invalid view typeExplanation 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.
Recommended Action Delete or move the particular map file.
Error Message
No community string
Explanation
RSRB or DLSw does not know the community string for this router.
Recommended Action
Use the Edit>Modify menu item or the Administration application to set the correct community string.
Error Message
No response from update server.
Explanation
The monitor daemon is not running.
Recommended Action
Use the Process Manager or the cwb start command to start the monitor daemon.
Error Message
Port already in use.
Explanation
A copy of the monitor daemon is already running on the workstation, or some other program is using this port.
Recommended 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.
Error Message
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.
Recommended Action Delete or move the particular map file.
Error Message
Rediscover Device(s) failed.
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 1 Use the ping command to see whether the router is active.
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 that you are using, that the router is configured for SNMP, and that the read community string is correct.
This section contains the following major topics:
CWC0006W Socket connect failed, will retry momentarily.
This chapter provides a detailed description of each message and, if appropriate, a recommended user response.
If the Host Connection Interface or the Host Command Server will not initialize successfully, perhaps because of communications problems between the workstation and mainframe, perform the following procedures.
Step 1 Verify that the SVMF_AGENT_ADDR configuration parameter (in the /opt/CSCOcb/etc/svopen_config_domain file) is set to the correct IP address or host name of the mainframe.
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 1 For IBM TCP/IP connections, verify that the TCP subtask for your requested ports is active. Issue the F NSPOPEN,SHOW TASK command and look for the desired ports to confirm that the TCP subtask's state is READY. If the TCP subtask's state is not READY, use the INIT command to activate the TCP subtask.
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 messages 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.
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 may 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 set correctly, can keep workstation processes from executing properly.
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 (/opt/CSCOcb/snahost).
If this variable is not properly set to the home directory, as defined during installation, workstation processes will not be able to 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 not successfully initialize when using TCP/IP 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:
CWC0037E client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
CWC0043E Unable to obtain host TCP/IP address from host name: mickey
CWC0048I client_bind_udp_socket() process has exited.
If, however, 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:
CWC0001E server_connect_tcp_socket() failed calling connect(), reason: Connection refused.
Similar error messages will also 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 timeout 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:
CWC0061W Timed out waiting for command response from Command Server.
CWC0064W Command not processed. Verify that the HCI and Command Servers are active.
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 may be set too low. See your mainframe system administrator or see the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for assistance.
The Host Connection Interface communicates with the VTAM and MVS Servers, and the cwbhmond process, over these defined ports. Ensure that 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:
CWC0001E server_connect_tcp_socket() failed calling connect(), reason: Connection refused.
CWC0007E Socket connect failed, no retry will be attempted.
CWC0048I server_connect_tcp_socket() process has exited.
This section explains the messages generated by the workstation program. Each message number ends with one of the following error codes:
Error Message
CWC0001E process failed calling function, reason: explanationWhere:
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 that is essential to the process is missing. Without it, the process cannot continue and will exit with an error.
Recommended 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 may be caused by the system load, and the process will run properly if restarted.
Error Message
CWC0002E Unable to open protocol method socket.Where:
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.
Recommended Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
Error Message
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.
Recommended Action In some cases, the error is caused by the system load, and the process will run properly if you restart it.
Error Message
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.
Recommended Action No user action is required.
Error Message
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.
Recommended Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
Error Message
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 wait momentarily and then reissue the connection attempt.
Recommended Action No user action is required.
Error Message
CWC0007E Socket connect failed, no retry will be attempted.Explanation A process attempted to connect to another process via socket communications and failed. The process that detected the error will terminate.
Recommended 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.
Error Message
CWC0008E Unable to get socket option: socket.Where:
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.
Recommended Action Attempt to restart the failing process.
Error Message
CWC0009E Unable to set socket option: socket.Where:
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.
Recommended Action Attempt to restart the failing process.
Error Message
CWC0010E process failed reading HCI socket, reason: explanation.Where:
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.
Recommended 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.
Error Message
CWC0011E Failure reading process client UDP socket.Where:
process is the client process name.
Explanation A server process failed while reading a client's socket. The server process will terminate.
Recommended Action In some cases, the error is caused by the system load, and the process will run properly if restarted.
Error Message
CWC0012E Failure reading process server UDP socket, entire message not received.Where:
process is the server process.
Explanation A client process attempted to read from an server process and received only a partial message. The detecting client process will terminate.
Recommended 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.
Error Message
CWC0013E Failure writing to process client UDP socket.Where:
process is the client process.
Explanation A server process failed while writing data to an client process. A server process will continue processing if a write to a client process fails.
Recommended Action Verify that the client process is still active and, if not, restart the client process repeating the desired action.
Error Message
CWC0014E Failure writing to process client UDP socket, entire message not sent.Where:
process is the client process.
Explanation An 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.
Recommended Action Verify that the client process is still active and, if not, restart the client process.
Error Message
CWC0015E Failure reading SView/Open Mainframe Message Server, reason: explanation.Where:
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.
Recommended Action Review text explanation of the error and verify TCP/IP support between the workstation and the mainframe in question.
Error Message
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.
Recommended Action Verify the status of the mainframe application and the TCP/IP support.
Error Message
CWC0017E process has exited due to read failure on HCI connection.Where:
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.
Recommended Action Verify that the Host Connection Interface for that domain is active.
Error Message
CWC0018E process has exited due to loss of connection with the HCI.Where:
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.
Recommended Action Verify that the Host Connection Interface for that domain is active.
Error Message
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.
Recommended 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.
Error Message
CWC0020E process failed calling name with errno: error_numberWhere:
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.
Recommended 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.
Error Message
CWC0021E Failure opening direction LU 6.2 conversation.Where:
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.
Recommended 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.
Error Message
CWC0022E Failure allocating direction LU 6.2 conversation.Where:
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.
Recommended 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.
Error Message
CWC0023E Failure reading over direction LU 6.2 conversation.Where:
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.
Recommended 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.
Error Message
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.
Recommended 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.
Error Message
CWC0025E Failure confirming conversation LU 6.2 conversation read.Where:
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.
Recommended 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.
Error Message
CWC0026E Failure sending over conversation LU 6.2 conversation.Where:
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.
Recommended 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.
Error Message
CWC0027E Failure closing conversation LU 6.2 conversation.Where:
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.
Recommended 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.
Error Message
CWC0028I process initialized successfully for domain name.Where:
process is the process.
name is the defined domain name.
Explanation A process has initialized successfully for the domain. The SNA host process will continue with execution.
Recommended Action No user action is required.
Error Message
CWC0029E process started with invalid argument count.Where:
process is the process.
Explanation A process was started with an incorrect number of command line arguments. The process will terminate.
Recommended 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.
Error Message
CWC0030E Domain name must be passed in to the process.Where:
process is a 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.
Recommended Action Verify that the following files were not incorrectly modified:
Error Message
CWC0031E Invalid transaction program name executable used to startExplanation 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.
Recommended Action Verify that the following files were not incorrectly modified:
Error Message
CWC0032E process encountered invalid value for configuration parameter parameter_nameWhere:
process is the process 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.
Recommended Action Set the configuration parameter with the proper value and restart the process.
Error Message
CWC0033E process needs the variable environment variable set properly.Where:
process is the process.
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.
Recommended Action Set the environment variable with the proper value and restart the process.
Error Message
CWC0035E process failed calling functionWhere:
process is the process or function.
function is the function.
Explanation A process or function has failed in its call to a function. In most cases the process or function will terminate.
Recommended Action Normally, more detailed error messages will accompany this message. Review all generated error messages in an effort to resolve the error.
Error Message
CWC0036E process failed calling function with rc: rcnumberWhere:
process is the process or function.
function is the 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.
Recommended Action Normally, more detailed error messages will accompany this message. Review all generated error messages in an effort to resolve the error.
Error Message
CWC0037E process failed calling function, reason: messageWhere:
process is the process or function.
function is the 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.
Recommended Action Normally, more detailed error messages will accompany this message. Review all generated error messages.
Error Message
CWC0038I process for domain domain will terminate after waiting for other processes to end.Where:
process is the process or function.
domain is the domain name.
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.
Recommended Action No user action is required.
Error Message
CWC0039W An instance of process for domain domain is already running.Where:
process is the process or function.
domain is the domain name.
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.
Recommended Action No user action is required.
Error Message
CWC0040E process failed to open file path, reason: messageWhere:
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.
Recommended Action Check file permissions to ensure that the process has the ability to read and write to the file.
Error Message
CWC0041W Attempt to connect to process failed, retrying.Where:
process is the process or function.
Explanation An attempt to setup a socket connection to the specified daemon failed.
Recommended Action No action is necessary. An attempt to connect will be retried.
Error Message
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.
Recommended Action Verify that available memory requirements on the workstation have not been exceeded.
Error Message
CWC0043E Unable to obtain host TCP/IP address from host name: host.Where:
host is the TCP/IP host name.
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.
Recommended Action 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.
Error Message
CWC0044W Waiting for previous instance of process for domain domain to end.Where:
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.
Recommended Action No action is necessary.
Error Message
CWC0045E process for domain domain detected an unsupported mainframe version.Where:
process is the name of the process.
domain is the name of the domain.
Explanation The mainframe and workstation versions are not comparable.
Recommended Action Install the correct level of software on both the mainframe and workstation.
Error Message
CWC0046E process for domain domain failed to receive a response for the version request.Where:
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 request.
Recommended Action Ensure that the correct level of mainframe software is installed and running on the mainframe. You might need to adjust the mainframe command timeout value (SVCMD_TIMEOUT).
Error Message
CWC0047E process for domain domain lost mainframe connection; will try to re-establish. Code code.Where:
process is the name of the process.
domain is the name of the domain.
code is the error code.
Explanation The workstation lost its connection to the mainframe.
Recommended Action No action is required. The workstation will periodically try to reestablish a connection to the mainframe.
Error Message
CWC0048I process process has exited.Where:
process is the process that exited.
Explanation A process has terminated.
Recommended Action Review any generated error messages to determine the cause of the process termination if the termination was abnormal.
Error Message
CWC0049I process process of domain name has exited.Where:
process is the process that exited.
name is the domain name.
Explanation 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.
Recommended Action Review any generated error messages to determine the cause of the process termination if the termination was abnormal.
Error Message
CWC0050I process process of domain name has exited with code code.Where:
process is the process that exited.
name is the defined domain name.
code is the error code.
Explanation The named process has exited.
Recommended 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.
Error Message
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.
Recommended Action Ensure that the mainframe STATUS and DISCOVERY subtasks are configured and active.
Error Message
CWC0052E Invalid buffer size for process message. Domain: domainWhere:
domain is the domain name.
message is the message.
Explanation The named process has received a invalid buffer. The process will end.
Recommended Action Use the cwb tac command and notify the Cisco TAC.
Error Message
CWC0053E Invalid buffer structure. Domain: domainWhere:
domain is the domain name.
Explanation An invalid buffer was received. The process will end.
Recommended Action Use the cwb tac command and notify the Cisco TAC.
Error Message
CWC0054W Connection to command server daemon failed for domain.Where:
domain is the domain name.
Explanation The Host Connection Interface was unable to connect to the Host Command Server.
Recommended Action Other messages may accompany this message. Attempt to resolve the problem based on these messages. Ensure that the product has been properly installed and configured. If the error persists, use the cwb tac command and notify the Cisco TAC.
Error Message
CWC0055W Connection to Status Monitor daemon failed for domain domain.Where:
domain is the domain name.
Explanation The Host Connection interface was unable to connect to the Status Monitor.
Other messages may accompany this message. Attempt to resolve the problem based on these messages. Ensure that the product has been properly installed and configured. If the error persists, use the cwb tac command and notify the Cisco TAC.
Error Message
CWC0056E Invalid message type received by process1 from process2: typeWhere:
process1 and process2 are processes.
type is the message type.
Explanation A process received an invalid message type from another process. The invalid message will be ignored, and processing will continue.
Recommended Action If this message persists, note the message contents, use the cwb tac command, and notify the Cisco TAC.
Error Message
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. The server process will reject the client process's filter request.
Recommended Action No user action is required.
Error Message
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.
Recommended Action No user action is required.
Error Message
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. The server process will reject the client's register request.
Recommended Action No user action is required.
Error Message
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.
Recommended 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.
Error Message
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.
Recommended 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.
Error Message
CWC0062E process error message: message.Where:
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.
Recommended Action Review the error message to determine the cause of the error and correct the problem.
Error Message
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 may have terminated.
Recommended 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.
Error Message
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, Host Command Server, or both may no longer be active and functioning properly. No further processing for the issued command will take place.
Recommended 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.
Error Message
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.
Recommended 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 troubleshooting procedures for initial problem resolution, and then lists specific symptoms and possible remedies.
If the APPN application fails to operate correctly, verify that the environment variables are set in the runprocess script according to the values in the "Installing and Configuring CiscoWorks Blue" chapter.
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-2 lists symptoms that your APPN application might demonstrate and refers you to some diagnostic techniques to resolve the problems.
| For this symptom | See this section |
|---|---|
Cannot find LU | |
Global view is empty | |
Good connection displayed as degraded | |
Incorrect status | |
Link station is not displayed | |
Network node status is unknown |
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 could have been stopped in that device, or the SNMP request may 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 protocol.
If APPN cannot find a known LU, use the following procedure:
Step 1 Select each node on the map, one at a time.
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 1 Close the List TGs and Links window.
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 may exist in the network topology agent's database. In some number of days, according to an APPN algorithm, the network topology agent will delete the defunct number. When you start the APPN 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 1 On the map, select the owning node.
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 application. They are displayed in the APPN Motif message box and written to the message log.
Error Message
Current view_name view type conflicts with reserved name prefix of file.Where:
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:
Recommended Action Do not use File>Save As to save to a file with one of the reserved prefixes.
Error Message
Database initialization failure
Explanation
APPN failed to connect to the network management system database before discovery.
Recommended Action
If you have HP OpenView or NetView installed, you can use the ovstatus command, which is typically 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.
Error Message
Device name & read community required
Explanation
APPN must send an SNMP MIB request to a node, but no device name is known for this node.
Recommended 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.
Error Message
Invalid view typeExplanation 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.
Recommended Action Delete or move the particular map file.
Error Message
No APPN NNs discovered
Explanation
Discovery was completed but a network topology agent was not found.
Recommended Action
Review the devices in the seed file or network management system database to ensure that at least one active APPN network node exists. Then use Admin>Discover to retry the request, or exit the application and restart it. In the Startup Query window, specify a topology agent that is known to be reliable.
Error Message
No devices discovered
Explanation
No devices were available to be discovered.
Recommended Action
Review the device list in the seed file or network management system database so that discovery has a chance of success. Then use Admin>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.
Error Message
Reading map file filename. Incorrect format or version.Where:
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.
Recommended Action Delete or move the particular map file.
Error Message
Startup input required
Explanation
The Startup Query window is being displayed because the application has not yet accessed a network topology agent. If a valid CP name is displayed in the window, perhaps the device name is also needed.
Recommended Action
Enter a valid CP name or device name or discover a network topology agent. To prevent this dialog box from being shown in the future, specify a network topology agent in the cwbinit file.
Error Message
View could not be retrieved
Explanation
A map view requires data that is not available to the APPN application. This happens typically when you request the ports and links view but local topology is not available from the target node.
Recommended Action
If the target node can act as a network 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.
Error Message
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.
Recommended 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.
Error Message
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.
Recommended Action
Perform the following steps in order. Stop when one is successful.
Step 1 Select Admin>Discovery to discover a new network topology agent.
Step 2 Ensure that the selected network topology agent is an APPN network node with the APPN MIB, and that the IP address or device name you specified is correct. If not, stop the APPN application and restart it with a new network topology agent.
Step 3 Ensure that the APPN 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. 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.
You can also 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, perhaps 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 is 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
Where:
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 sucessfully, 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 Sep 9 08:55:25 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.