|
|
The information in this Release Notes for Cisco WAN Service Administrator 1.1 supersedes all information in the WAN Service Administrator (WSA) documentation set.
The information in this release note is organized into the following sections:
The WSA documentation set includes the following manuals:
This section describes the minimum system requirements needed to install Cisco WAN Service Administrator (WSA).
The categories of the system requirements are as follows:
The following are the minimum UNIX system requirements:
The following are the minimum PC client system requirements:
Informix 7.2.3 is the required version of the Informix database engine. This version is distributed on the CD-ROM for WSA.
A requirement to use WSA is that any 9.1.xx release of 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.
 | Caution 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. |
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:
The WSA back-end Control Processor module talks to Cisco StrataView Plus (SV+).
The following caveats are applicable to Cisco WSA 1.1:
Step 1 Log in to the WSA Solaris server as wsa.
Step 2 echo "delete from command; delete from task" | dbaccess wsadisp
Step 3 echo "delete from task_command; delete from task" | dbaccess wsamain
| End Point A | End Point B |
|---|---|
FR | FR |
ATM | ATM |
FR | ATM |
| 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 |
| 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 |
setenv WSADATABASE wsamain
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.
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.
Workaround: Delete the incorrect card and then use the Add Card Wizard to create a new card. Be sure to select the correct port type in the GUI.
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.
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.
Problem: When the connection to the server is broken while the Administrator or Explorer is running, it generates a SQL error followed by a run time error.
Workaround: When connectivity to the Informix server is broken, restart WSA applications.
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+.
Problem: When the user is in the Add Connection Wizard and tries to change the live/cease times by manually typing in digits, the numbers are not correctly displayed.
Workaround: Use the increment/decrement buttons to select the times.
Problem: The loader loads an incorrect trunk speed.
Workaround: None.
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.
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 Add Connection Wizard.
Problem: When requesting a logical port number for a UFM card, the GUI does not check whether a logical port has already been used.
Workaround: Be sure that the logical port number being requested has not been previously used.
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:
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. If new service levels are created, this data can become relinked. This can lead to confusion, because data not created by the user suddenly appears.
Workaround: Upon creating new service levels, launch the template editor and delete any template that shows up for that new service level or other service levels that you have not entered. This ensures that any extraneous templates generated by the GUI do not interfere with new service level template generation. Once all the extraneous templates have been deleted, new desired templates can be created for that service level.
Problem: When you bring up the Template Editor in 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 will automatically generate some extra templates.
Workaround: Delete the automatically created extra templates.
Problem: When the NNI connection is ceased, only one PVC is deleted.
Workaround: Follow these steps:
Step 1 Find the connection across the NNI that is LIVE.
Step 2 Double-click on that LIVE connection and change the status to CEASED.
Step 3 Note the individual PVCs that show in the bottom of the Connection Properties window.
Step 4 Use SV+ to locate and delete the noted PVCs on the respective networks.
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.
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.
Posted: Fri Apr 23 14:07:35 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.