Table of Contents
Troubleshooting
The objective of this appendix is to provide known symptoms and recommended actions. This information is organized with an informative heading.
Provisioning a connection across NNI link(s) fails.
Do one or more of the following:
- Make sure that both the starting and ending points are available for this NNI. Be sure that node/slot/port/vpi/vci or node/slot/line/port/dlci for either the ATM or FR end is not occupied by any other connection end.
- Display the property of the connection by double clicking it. If one of the PVCs being generated is of connection type ATM-FR, make sure that the VPI is larger than or equal to one.
- Display the property of the connection by double clicking it. Skip vp,vc pair (0, 31). It was reserved for ILMI protocol. Also, skip (0, 16). It was reserved for LMI protocol.
- Assign the IP address (the IP of the machine on which the SV+ Agent is running) for each network. Go to the object Network Access Points in the Administration application and create a New Network Access Point.
- Check the NNI port configuration procedures, for example:
- upln 1.2: Up the physical line in slot one port two.
- cnfln 1.2: Set the parameters such as Loop clock, Idle code, HCS Masking, or go with the defaults for this line.
- cnfport 1.2: Assign Cell Header Format as NNI, set Protocol, and other traffic parameters.
- upport 1.2: Bring this NNI port up and trigger the NNI protocol.
- Log on to the remote end of the NNI link and take the same procedure to bring up the NNI port on the card.
- Clean each NNI port's statistic counter with the command clrportstats.
- Create NNI ports for each network under customer NNI and allocate the NNI port previously configured to each Customer Port.
- Create a New Link object under either network where the link end resides. Choose the NetLink Type as NNI. Select NNI ports previously allocated as NNI-customer's ports for both A-end and B-end for the NNI link.
- Make sure the NNIs (either FR NNI or ATM NNI) are the same type across all network clouds.
Provisioning an ATM, FR, ATM-FR or FR-ATM connection fails.
Make sure that both A_End and B_End points are available. Be sure that node/slot/port/vpi/vci or node/slot/line/port/dlci for either ATM or FR end are not occupied by any other connection end.
Provisioning a connection fails with one end residing at FRSM-4E1 non-channelized card on node AXIS.
From the SV+ Manager, configure the line, select the line-subtype E1CLRCHNL and allocate all 32 DS0 to the customer port.
Provisioning a connection fails with one end residing at UFM-8C card on node IGX.
Assign the logical port that has been assigned to map to the physical_port, starting_channel_number on the UFM card as the customer-port in WSA.
Inconsistent status shown for connection and task. Usually the status should be something like: The connection has been provisioned successfully. However, the status of the connection is shown as CANCELLED and the task is shown as COMPLETE_FAIL.
Do one or more of the following:
- Check the -i and -z flags for the WSA_WatchDog server and the -c flag for WSA_Scheduler server. Be sure that the interval for WSA_WatchDog to update the status of a connection (-z flag) could cover the interval for the WSA_Scheduler server to update the status of a task (-c flag). And be sure that the interval for the WSA_WatchDog to create the task (-i flag) can cover the update interval.
- If there are multiple tasks to be scheduled at the same time, use the -m flag (the number of tasks to send down at once to the SV+ Proxy Agent) for WSA_Scheduler and set the value to 1, because SV+ Agent is a one-threaded processor. Also, adjust the value of the -r flag (rescanning interval) according to the environment of the network.
When provisioning an ATM-ATM or FR-ATM connection with one ATM end point residing at AUSM card, one AXIS node fails.
Do one of the following:
- Assign the same physical port number to its logical port number through switch commands and use the physical port number for provisioning.
- Follow the mapping table in SV+ and use the logical port for provisioning.
WSA_Probe fails to generate a file on network configuration.
Do one or more of the following:
- Be sure that user specifies the right values of Network Access Point, User Name, and Password.
- Be sure that wsadisc is installed properly and running on the remote SV+ host machine. This SV+ host machine is usually the same IP Address that the user specifies for Network Access Point.
WSA_Loader will not load data from either a file or a network.
Do one or more of the following:
- Be sure that a Network Access Point is created for each network to be loaded.
- Double-check that the values set in the Network Access Point are correct.
- Be sure that the GUI uses the same database name as specified in the backend (UNIX) side.
- Be sure that the network name to be loaded into the WSA database does not already exist.
- Be sure that the User Properties are set up correctly from the WSA Administration application.
WSA_Audit fails to report the discrepancy between the WSA database and the actual network.
Do one or more of the following:
- Consider each step described in the WSA_Probe and WSA_Loader trouble shooting tips.
- Double-check the setup of Audit Schedule and Network names.
Unable to connect to the server database from the PC.
Recommended Action
Do one or more of the following:
- Ping the server from the PC to be sure that it is alive.
- Check the c:/windows/services file and ensure that an entry for wsatcp socket exists: wsatcp 1531/tcp
- Check the Informix client install setup. The main things to verify are:
- The server name or ip address
- The login name wsauser and its password. Neither will be displayed, so it may be advisable to enter these again. The password field is in overwrite mode.
- The Service name is wsatcp and the Protocolname is olsoctcp.
Posted: Fri Apr 23 14:14:55 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
