cc/td/doc/product/rtrmgmt/wsa/1_1_1
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Cisco
WAN Service Administrator 1.1.1

Release Notes for Cisco
WAN Service Administrator 1.1.1

The information in this Release Notes for Cisco WAN Service Administrator 1.1.1 supersedes all information in the Cisco WAN Service Administrator (WSA) documentation set.

The information in this release note is organized into the following sections:

Related Documentation

The WSA documentation set includes the following manuals:

Documentation Erratum

There is a correction to Cisco WAN Service Administrator Installation and Control System Configuration, Release 1.1, on page 4-6. The first time that the destination directory is chosen, the Browse button must be used to set to c:\informix.

System Requirements

This section describes the minimum system requirements needed to install WSA.

The categories of the system requirements are as follows:

Minimum UNIX System Requirements

The following are the minimum UNIX system requirements:


Note A Sun Ultra 2 is the minimum UNIX system recommended when creating more than 30 permanent virtual circuits (PVCs) at the same time.

Note The required Y2000 patch cluster for Solaris 2.5.1 can be found at: http://sunsolve.Sun.COM/pub-cgi/us/pubpatchpage.pl

Minimum PC Client System Requirements

The following are the minimum PC client system requirements:


Note The required Y2000 patch for Microsoft Windows 95 is Win95y2k.exe. Refer to the Microsoft web site, http://microsoft.com, and search for this program.

Informix Database Engine Requirement

Informix 7.2.3 is the required version of the Informix database engine. This version is distributed on the WSA CD-ROM.

Cisco StrataView Plus Requirement

A requirement to use WSA is that any 9.1.xx release of Cisco StrataView Plus (SV+) version 9.1.06 and later must be installed properly and tested.

The SV+ Solaris server must also have libresolv.so.2 in /usr/lib.

Warning
Cisco WSA and Cisco SV+ can not reside on the same machine. Do not attempt to install Cisco WSA on a system that already has Cisco SV+ installed.

Switch Release Requirements

WSA supports the same switch versions as supported by any 9.1.xx release of SV+ version 9.1.06 and later.

The following switch software versions have been tested with WSA:

WSA Provisioning Details

The WSA back-end Control Processor module talks to the SV+ SNMP Proxy Agent. For more information about the SV+ Proxy Agent, refer to Cisco StrataView Plus SNMP Proxy Agent.

Caveats

The following caveats are applicable to WSA 1.1.1:


Table 1:
End Point A End Point B

FR

FR

ATM

ATM

FR

ATM

One Network

Table 2:
Two Networks
End Point A NNI1 Link End Point B

FR

FR-FR

FR

ATM

FR-FR

ATM

FR

FR-FR

ATM

FR

ATM-ATM

FR

ATM

ATM-ATM

ATM

FR

ATM-ATM

ATM


Table 3:
End Point A NNI1 Link NNI2 Link End Point B

FR

FR-FR

FR-FR

FR

ATM

FR-FR

FR-FR

ATM

FR

FR-FR

FR-FR

ATM

FR

ATM-ATM

ATM-ATM

FR

ATM

ATM-ATM

ATM-ATM

ATM

FR

ATM-ATM

ATM-ATM

ATM

Three Networks
The first command line is needed to reflect PVCs that are live on the switch, which WSA could not destroy. The second command line is needed to reflect PVCs that are live on the switch for which WSA did not have the opportunity to update the status when the control processes were shut down. These command lines must be executed prior to restarting the WSA Control Processes.


Table 4: Recommended Configuration Parameters for Time Intensive Provisioning Activity
Platform Tasks (PVCs) Relating to Customer Connection Requests WSA_Scheduler Configuration WSA_WatchDog Configuration

Sun Ultra 10
128 MB RAM
603 MB Swap

150 (3 networks/2 NNIs)

-c 910 -m 1 -r 300

-i 51000 -z 50000

Sun Ultra 2
393 MB RAM
1100 MB Swap

150 (3 networks/2 NNIs)

-c 310 -m 1 -r 310

-i 15550 -z 15500

Sun Ultra 10
128 MB RAM
603 MB Swap

300 (3 networks/2 NNIs)

-c 1810 -m 1 -r 600

-i 95500 -z 95000

Sun Ultra 2
393 MB RAM
1100 MB Swap

300 (3 networks/2 NNIs)

-c 610 -m 1 -r 200

-i 30510 -z 30500

The "tasks" are the tasks to be executed at the same time.
The numbers in this table do not guarantee 100% accuracy due to network conditions that might exist. The values are guidelines and should be adjusted to meet network conditions.

In the case of any data contention error messages, refer to the section Known Problems in Cisco WSA 1.1.1, CSCdm27551 and CSCdm27561.

Problems Fixed Since Cisco WSA 1.1

CSCdm02961

Problem: When BXM cards configured as TRUNK-ATM to a non-AXIS node are loaded into the database, the GUI displays them as ATM, instead of as TRUNK-ATM.

Resolution: WSA_Probe and WSA_Loader now appropriately recognize BXM cards in ATM or TRUNK-ATM mode.

CSCdm12339

Problem: The wsamain database is shipped with a number of unlinked templates, associated parameters, and connection subtype defaults for service levels that no longer exist. When new service levels are created, this data can become relinked. This can lead to confusion, because data not created by the user suddenly appears.

Resolution: The wsamain database does not have unlinked templates in WSA 1.1.1.

CSCdm12368

Problem: When you invoke the Template Editor from the WSA Administration Tools bar, select the type as connection, and right click to create a New template with a newly created Service Level, the GUI automatically generates extra templates.

Resolution: WSA 1.1.1 does not automatically create extra templates.

CSCdm12558

Problem: When the NNI connection is ceased, only one PVC is deleted.

Resolution: In WSA 1.1.1 all PVC segments are deleted when an NNI connection is ceased.

Known Problems in Cisco WSA 1.1.1

CSCdk55643

Problem: Once created, nodes cannot be relocated to a different network or site, though they can be allocated to a different administrative region.

Workaround: None.

CSCdm05484

Problem: Listing ports in the Network or Location view under a node may take a long time.

Workaround: Listing time for ports is proportional to the number of ports under a node.

CSCdm06650

Problem: Starting DS0 number other than 1 for provisioning connections on non-channelized FRSM cards causes SV+ to fail.

Workaround: Always use starting DS0 to be 1 while provisioning connections with SV+ Proxy Agent for non-channelized FRSM cards.

CSCdm07313

Problem: When the connection to the server is broken while the Administrator or Explorer is running, an SQL error followed by a run time error is generated.

Workaround: When connectivity to the Informix server is broken, restart WSA applications.

CSCdm08944

Problem: The Loader assigns only some ports to Audit customer.

Workaround: The Probe discovers nodes, cards, ports, trunks, and connections using an SV+ database. The Loader loads those based upon information returned by SV+.

CSCdm09443

Problem: When you try to change the live/cease times by manually typing digits in the Add Connection Wizard, the numbers are not correctly displayed.

Workaround: Use the increment/decrement buttons to select the times.

CSCdm10328

Problem: The loader sometimes loads an incorrect trunk speed.

Workaround: None.

CSCdm11254

Problem: WSA can only support one slot type per slot, even though, in some cases, switches support multiple slot types per slot.

Workaround: Mixing slot types is not supported. Do not mix slot types on a single slot.

CSCdm11695

Problem: The Loader fails to report some IGX-ended FR-FR connections. For the ones it does report, the GUI does not correctly show the DLCI at the IGX end.

Workaround: Delete the unreported connection and manually insert a new connection through the Add Connection Wizard.

CSCdm12322

Problem: WSA cannot support channelized and non-channelized ports on the same card.

Workaround: Be sure to understand the predefined setting of channelized or non-channelized for each specific card. The following cards are set as channelized:

CSCdm27551

Problem: Database contention errors and SQL error messages occur upon refreshing a task list or within the Add Connection Wizard in the WSA Administration and Explorer GUIs, respectively.

Workaround: Do not refresh the task list during heavy traffic for WSA Control Processes, when many tasks are in WAIT/PROGRESS states. Also, create connection records in advance, using the Add Connection Wizard, during light traffic for WSA Control Processes when only a few or no tasks are in WAIT/PROGRESS states. This eliminates the database resource contention error messages and SQL error messages with codes 243, 400, and other SQL errors.

CSCdm27561

Problem: The WSA Control Processes WSA_Scheduler and WSA_WatchDog run into a database resource contention issue depending upon their command line option values.

Workaround: The default values for the Control Server options are (Korn shell syntax shown):

$ WSA_Scheduler -i -s +sched1 -c 15 -m 1 -r 30

$ WSA_WatchDog -u -l -v -i 120 -z 45

The Scheduler updates the status of the tasks every 15 seconds, based on the -c flag setting. The WatchDog updates the status of the connections every 45 seconds, based on the -z flag setting. Also, the WatchDog generates new tasks every 120 seconds, based on the -i flag setting. Based upon the installed network environment and provisioning traffic, these flags must be specified to describe the accuracy/interval with which the WSA Control Processes execute. This helps minimize or eliminate database resource contentions and SQL errors 244, 271, and other SQL errors.

Table 5, "Recommended Configuration Parameters for Provisioning Activity", presents a recommended guideline set of configuration parameters for the WSA Control Processes for provisioning activity.


Table 5: Recommended Configuration Parameters for Provisioning Activity
Platform Tasks (PVCs) Relating to Customer Connection Requests WSA_Scheduler Configuration WSA_WatchDog Configuration

Sun Ultra 10
256 MB RAM
500 MB Swap

20 (1 network)

-c 59 -m 1 -r 10

-i 360 -z 35

Sun Ultra 10
256 MB RAM
500 MB Swap

40 (2 networks/1 NNI)

-c 90 -m 1 -r 10

-i 360 -z 60

Sun Ultra 10
256 MB RAM
500 MB Swap

60 (3 networks/2 NNIs)

-c 90 -m 2 -r 5

-i 360 -z 60


The numbers in this table do not guarantee 100% accuracy due to network conditions that might exist. The values are guidelines and should be adjusted to meet network conditions.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Apr 26 14:10:30 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.