|
CCO Date February 2000
Introduction
Hardware Supported
Software Compatibility
Upgrading to a New Software Release
New and Changed Information
New Software Features in Release 2.2.8.5
New Software Features in Release 2.1.3
Compatibility
Caveats
Resolved CaveatsRelease 2.2.8.5
Open CaveatsRelease 2.2.8.5
Resolved CaveatsRelease 2.2.8.4
Resolved CaveatsRelease 2.2.8.2
Resolved CaveatsRelease 2.2.8.1
Resolved CaveatsRelease 2.2.8
Resolved CaveatsRelease 2.1.3
Related Documentation
Cisco Connection Online
Documentation CD-ROM
The Virtual Command Line Interface (VCLI) is a management application that runs on UNIX. It manages the MGX 8240 switches in the network. All 8240 features are supported from the VCLI. The VCLI is independent of all other management applications that Cisco provides.
VCLI Software Release 2.2.8.5 has all the functionality of the previous VCLI software releases. The last official release of the VCLI was Release 2.1.3. There is a beta release of VCLI software that was named version 2.2.8. Two major items new to this release are support for the new IMC card in the
MGX 8240 switch, and the functionality of the background polling task has been significantly enhanced. There have also been bug fixes to the previous 2.1.3 Release.
Release 2.2.8.5 fixes problems in the area of SW upgrade for the IMC cards. Those problems are described below in the list of Caveats.
All released hardware components of the MGX 8240 are supported. This release of the VCLI will manage an Cisco MGX 8240 switch with or without an IMC card. If the Cisco MGX 8240 is still connected to a CIM, the VCLI will not have a problem managing the CES cards.
There are no compatibility problems between this VCLI release and previous ones. This release should replace all earlier releases.
This version of the VCLI is also backward compatible, in that it supports all CES and IMC card software versions at or below 2.2.X. The software versions of the CES cards can be mixed in a chassis, and still be supported by the VCLI. The VCLI continues to support the In-Band or Out-Of-Band IP management route discovery for the CES cards. When the In-Band route is up and operational, In-Band management continues to be the preferred route of all management traffic between the VCLI and the CES cards.
The VCLI software is distributed on the VCLI CD and contains three files listed below. The files that have the `.tar.Z'suffix are compressed UNIX archive files. These files are uncompressed using the UNIX "uncompress <filename>" command, and un-archived using the "tar xvf <filename>" command.
vcli-install.txt
vcli-new-VERSION-2.2.8.5.tar.Z
vcli-upgrade-VERSION-2.2.8.5.tar.Z
The vcli-install.txt file contains instructions on how to install the VCLI for the first time, or how to upgrade an existing VCLI release.
Files included in the new install tar file are
vcli
bladeMon
snmp.mgr
vpasswd
ftpImage
image
vcliSetup
vpasswd
Files included in the upgrade tar file are
vcli
bladeMon
snmp.mgr
ftpImage
This release builds upon all other features of the VCLI. No features that existed in previous releases of the VCLI have been removed. Please consult previous release notes and user guide documentation for the list of features
The features in VCLI version 2.1.3 are described below, and the descriptions apply to the features of all releases since the last major VCLI release, which was 2.0.X.
New in version 2.1.3 of the VCLI is support for both CES card hardware types. The only two types of CES cards that this version of the VCLI will support are
1. The original CES card type that supports the original I/O card with 3 channelized DS3s, and two OC3 ports.
2. The new CES (called the CS3) card type which can support the original I/O card type, as well as the new I/O card type with 4 OC3 ports (the DS3 ports are contained within the OC3 port).
This release includes two new developments: support for the IMC card in the Cisco MGX 8240 switch, and significant enhancement to the background polling task functionality. There have also been caveats resolved since the last release.
The IMC card is the management card in the chassis, and compared to the CES cards has very few features to be managed. The VCLI supports the IMC redundancy feature, the MIB II system group table, and software upgrade. The IMC card cannot be managed in-band in Release 2.2.X of the Cisco
MGX 8240 switch software. The IMC card replaces the CIM product that was shipped with all Cisco MGX 8240 switches.
New VCLI commands were added to support the IMC, including:
VCLI>> show imccard info
VCLI>> show imccard config
VCLI>> change imccard config
VCLI>> show imccard redundancy
VCLI>> change imccard redundancy
VCLI>> change imccard image
The background polling feature is referred to as BladeMonitor. In previous releases, background polling was done as part of the VCLI task process. Starting with this release, the VCLI will spawn a BladeMonitor sub-process. As a separate process, one BladeMonitor process will support all VCLI sessions that are started. The BladeMonitor process will continue to poll all cards and switches in the network while at least one VCLI session is active. The BladeMonitor process terminates itself after a few seconds when it detects all VCLI processes have been terminated. New features for the BladeMonitor are more efficient network polling, the ability to see how the BladeMonitor is interpreting network connectivity, and the BladeMonitor's own performance statistics.
New VCLI commands that were added to support the BladeMonitor include the following:
VCLI>> show blademon statistics
VCLI>> show blademon information
The features in VCLI Release 2.1.3 described here still apply. These descriptions remain as part of the VCLI 2.2.8.5 Release Notes because they still apply to all the new features since the last major VCLI release, which was 2.0.X.
New in Release 2.1.3 of the VCLI was support for both CES card hardware types. The two types of CES cards that Release 2.1.3 of the VCLI will support are
1. The original CES card type that supports the original I/O card with 3 channelized DS3s, and two OC3 ports.
2. The new CES (called the CS3) card type which can support the original I/O card type, as well as the new I/O card type with 4 OC3 ports (the DS3 ports are contained within the OC3 port).
This release of the VCLI is backward compatible; it supports all CES and IMC card software releases at or below 2.2.X. The software releases of the CES cards can be mixed in a chassis, and still be supported by the VCLI. The VCLI continues to support the in-band or out-of-band IP management route discovery for the CES cards. When the in-bandroute is up and operational, in-bandmanagement continues to be the preferred route of all management traffic between the VCLI and the CES cards.
These are known caveats for this release of the VCLI. Some of these problems are covered by DDTSs, defined in the tables below.
The VCLI allows users to change the redundancy role of primary card to a role of "none', the primary card is being forced back into service. The VCLI should not allow this change while the card is in this redundancy state. Changing the redundancy role of the primary card while in this state could cause a problem with the configuration database of the primary card. The DDTS number for this problem is CSCdm71570. There is no work-around for this problem.
The VCLI has a problem with a switched-out primary card when the primary card is not responding to SNMP PDUs. The VCLI should divert all user queries to the switched-in backup card. But instead the VCLI reports that it cannot communicate with the switched out-primary. This is most likely to occur when the primary card is pulled out of the switch. The DDTS number for this problem is CSCdp39816. The work-around for this is to explicitly specify the switched in backup card for all VCLI queries.
There is a problem for the VCLI creating Private Line circuits between two CES cards in two different switches when one card is running Release 1.1.2.10, and the other is running Release 2.X. The order of how the two endpoints are specified is important. When creating a circuit with the described scenario, the user must specify the Release 1.x version as endpoint 1. There is no problem if the two endpoints are on the same switch. DDTS CSCdp35740 identifies this problem.
To accommodate two card types in the same switch chassis, the switch software upgrade procedure was changed from previous releases of the VCLI. Previous versions of the VCLI updated the CPE card Software only. This version upgrades the Software for both IMC and CPE card types. This requires that the contents of the Tar files, which contain the Software upgrades, have a new directory format. VCLI version 2.2.8.5 cannot use a Tar file built with the old directory format. All CPE and IMC card Software upgrade Tar files, beginning with Release 2.2.0.3 (and higher) of the CPE and 2.2.0.11 (and higher) of the IMC, have this new format.
In this release of the VCLI, the background polling process is a separate task from the VCLI process. The background polling process is called the BladeMon. The BladeMon process updates a file called "blade.db." All VCLI processes read this file to get switch and blade connection information (e.g. whether to use the InBand or OutOfBand interface to a CPE card). The BladeMon process can die. It doesn't happen unless it was explicity terminated, or there was a UNIX related system problem. When BladeMon dies, the VCLI processes can't detect that it has died if the file "blade.db" remains. The VCLI processes continue to operate as before using whatever old information is in the "blade.db" file. This can remain for days, and not cause a problem. The symptom that is most common when this scenario occurs is that network additions/deletions or redundancy changes will not be reflected in the VCLI. The VCLI will continue to read the information that was present in the "blade.db" file when the BladeMon process died. This condition can be verified by using the VCLI command show blademon stat. The statistic that counts the number of polls will not increment when the BladeMon process has died. DDTS CSCdm30982 chronicles this defect.
Fixing the above problem is easy. When the problem occurs, the ".blade.pid" file must be manually removed using the UNIX command rm .blade.pid, and a VCLI restarted. When the VCLI restarts, it will restart the BladeMon process, which will read the VCLI switch database. Upon startup, the BladeMon will query all CPE and IMC cards in the network to quickly rebuild the "blade.db" file with fresh information. This should take only a few seconds. Old VCLI processes need not be terminated while this is going on. However, if they are terminated it's not a problem.
| VCLI 2.2.8.5
| ||
DDTS Number | Severity | Functional Area | Problem Description |
CSCdp72170 | High | SW Upgrade | The VCLI continues to proceed with a CES and IMC SW upgrade even though a crucial file "contents" is not found in the directory containing the new SW images. Now, if that file is not found, the VCLI stops the upgrade. |
CSCdp72169 | High | Blade Monitor | The Blade Monitor process stops polling the network. This fix was to change the UNIX function call used to pause the Blade Monitor process. |
| VCLI 2.2.8.5
|
| ||
DDTS Number | Severity | Functional Area | Problem Description | Comments |
CSCdp39816 | High | Redundancy | Unable to communicate to switched-out primary and switched-in backup when the primary card is not responding to SNMP PDUs. |
|
CSCdm73811 | High | Connection creation | Cannot make connection between CES cards running different SW versions. | This wasn't a defect. Release 1 CPE SW can't handle EPIDs as large as Rel 2 SW. |
CSCdp35740 | Medium | Connection creation | VCLI cannot create a PL circuit from a CES card running Rel 2.x SW to card on a different switch running Rel 1.x SW. |
|
CSCdm90826 | High | OC3 status | The SONET path operational status of the access side as reported by the VCLI can be incorrect if the access OC3 port is APS protection switched to the protection line. | Should be fine if APS is not enabled or the working line is active. |
CSCdm71570 | High | Redundancy | VCLI allows configuration changes to CES cards while their redundancy state is FBP (Force Back in Progress). | See note in "Caveats," above. |
CSCsn05508 | Medium | APS | VCLI displays an error if def card is invalid for command change cescard aps? | Only occurs when help requested |
CSCdp40572 | Medium | SONET Path Thresholds | VCLI cannot change the Error thresholds values for the SONET Path level on the Channelized Access OC3 ports. |
|
CSCdp34882 | Medium | Ckt BERT | VCLI cannot set the transmit and receive bit inversion attributes for PL and SegPL type circuit BERT tests. These attributes apply only to User data pattern configured BERT tests. |
|
CSCdp35483 | Medium | IMC | The command show imc info doesn't check if backup IMC is present in the switch. Consequently, if the backup card is not present, the command takes several seconds to complete. |
|
CSCdp35469 | Medium | IMC | The VCLI doesn't report the SW version of the backup IMC card from backup IMC. It displays the SW Version of the Primary card for the backup too. |
|
CSCsn05671 | Low | Performance | Request to increase VCLI performance when creating a pl type connection | Not a bug; it's just slow. |
CSCdm70079 | New feature | Show connections | Add feature to show what the default physical ports are when listing the connections on a card | Feature request |
CSCsn05455 | Low | Show cmds | Some show commands don't recognize that the user has entered invalid options. The VCLI ignores these options because they are not needed rather than tell the user that they gave options that are illegal. |
|
CSCsn04479 | New feature | usability | Curses doesn't workneed real terminal mode for line editing. An enhancement will allow true cursor controlled line edits. |
|
CSCsn04947 | New feature | Config files | Enhancements: Add capability to backup and restore config files. |
|
CSCsn04974 | New feature | Sw upgrade | Download related code should display info about user, time downloaded, downloaded from, etc., for record keeping. |
|
CSCsn05072 | Low | Switch database | For -network 1 options it would be nice if switch names are alphabetically ordered. |
|
CSCsn05073 | New feature | Trap handling | Need to integrate VCLI's trap handling with redundancy related code. This way VCLI knows when to switch between in-band and out-of-band. |
|
CSCsn05492 | New feature | Ces card info | VCLI's "sh ces inf" should display both SW as well as FW active and inactive releases so a user knows what s/he is switching to. |
|
CSCdm30982 | Medium | Background polling | When BladeMon process dies, the redundancy status of the Cisco MGX 8240 cards in the network gets stale without the VCLI being aware of it. | The fix is to remove the file `blade.pid' and restart a VCLI. |
CSCsn05494 | Low | CES card addition | If two or more users make changes database changes to the VCLI database (e.g. add/delete cards, add/delete switches), then changes can be overwritten in the VCLI database. | A single user should make all changes to the database. |
CSCdp28944 | High | SW upgrade | VCLI download command doesn't check for file types when downloading files to Cisco MGX 8240 card. It blindly FTPs files that are found in the directories specified by the value of the `imagedir' attribute. | This problem should not occur if the upgrade procedures are followed. |
CSCdp37110 | Low | Connection creation | The VCLI will create a local PL type connection without having the second endpoint specified on the command line. Both endpoints should be specified on the command line for any type of PL circuit. |
|
CSCdp08025 | Medium | Redundancy | When the CES software has a I/O card incompatibility problem, the CES card reports a redundancy role value of "3." This is not a legal value according to the SNMP definition of the redundancy Role. When the CPE card returns this value, the VCLI displays a `-' for role. | When the I/O card is incompatible, this is a serious CPE problem, and the VCLI display of a `-'is minor in comparison. |
CSCdp37110 | Low | Connection creation | The VCLI creates a local PL type connection without having the second endpoint specified on the command line. Both endpoints should be specified on the command line for any type of PL circuit. |
|
CSCdp40302 | Low | Output display | The q to quit command to cease the output of data to the screen doesn't work the first time for the command show physical oc3 stat. |
|
CSCdp23296 | Low | Chassis cmd | When a Chassis level command is given on the VCLI, the VCLI will only go so far before prompting user Hit Return to Continue, q and return to quit. For chassis commands, the VCLI should not stop to query user. |
|
CSCsn05714 | Low | Change cmd | When a required command line argument is not given, the VCLI should display the argument that is missing, not a generic message stating such. |
|
CSCdm88355 | Medium | BERT | The VCLI doesn't display any digits after the decimal point for the attribute PercentErrorFreeSeconds when viewing BERT Status for DS1 or Circuit BERT tests. |
|
CSCdp33107 | Low | Download Help | Help for the command `download -card?' doesn't inform user that IMC is card 1, and CPE are cards 2-16. |
|
CSCdp33137 | Low | Download cmd | In the download cmd, the VCLI doesn't give an informative error message, when the cardtype argument doesn't match the slot of the card. |
|
| VCLI 2.2.8.4
| ||
DDTS Number | Severity | Functional Area | Problem Description |
CSCdp36225 | High | Ascend provisioning | The stored ascend uplink string was truncated if the Cisco MGX 8240 slot was greater than 9. This caused the ascend provisioning server to fail to create the ATM connection in the ascend cloud. |
CSCdp38898 | High | BladeMon | Illegal characters in a switch name cause the BladeMonitor to cease working properly. The VCLI now checks for legal characters in switch name when users add new switches to the VCLI database. |
CSCdp38890 | Medium | BladeMon | BladeMonitor was reporting the OutOfBand link to be down when the in-bandLink was up. The OutOfBand link status should be reported regardless of the in-bandlink state. |
CSCdp38871 | Medium | BladeMon | The command show blademon info displayed the in-bandcommunication state to a card down twice if the OutOfBand and in-bandlink were down |
| VCLI 2.2.8.2
| ||
DDTS Number | Severity | Functional Area | Problem Description |
CSCdp33196 | High | IMC SW upgrade | The VCLI isn't waiting long enough for the IMC redundancy situation to settle after the backup IMC has rebooted, and is ready to become primary. The VCLI is proceeding with the upgrade of the second IMC too soon. |
CSCdp02650 | Medium | IMC redundancy | If the IMC card with a Cisco MGX 8240 chassis is not available for IP communication, then the VCLI command `show switch redundancy' shows that it is. All other IMC commands fail. |
CSCdp33191 | High | IMC SW upgrade | When the VCLI initiates the upgrade on the backup IMC, if the backup IMC returns an error to the SNMP_SET request, the VCLI didn't cease the upgrade, and continued on with by attempting to upgrade the other IMC card in the chassis. |
| VCLI 2.2.8.1
|
| ||
DDTS Number | Severity | Functional Area | Problem Description | Comment |
CSCdp02650 | Medium | IMC redundancy | If the IMC card with a Cisco MGX 8240 chassis is not available for IP communication, then the VCLI command show switch redundancy shows that it is. All other IMC commands fail. |
|
CSCdp00218 | Low | CES redundancy | In show switch redundancy command, VCLI does not differentiate between configured cards that cannot be communicated with and empty slots when it cannot communicate to these cards. The VCLI will show a `-' in both these cases. It should display `unknown' for configured cards. |
|
CSCdm73051 | Medium | Connection deletion | VCLI does not delete far end endpoint of a pl type connection, when only the near end endpoint of the connection is given. But the converse is not true: both endpoints will be deleted if the farend endpoint is given on the command line | Work Around was to delete farend, or to delete both endpoints separately. |
CSCdp01075 | Low | CES card addition | When a CES card is added to a switch, and that card already exists, the VCLI returns an uninformative error message. |
|
CSCdm73801 | High, Status is Closed | M13 IP address | Cmd `change system cescard -m13?ip 0' doesn't work.
| This was never a bug. Changing IP addresses requires a few seconds for the CPE card to make the change visible to the VCLI. Setting `0.0.0.0' always works. |
CSCdp00556 | Low | PL ckt config | The loopback state of a PL type circuit is not shown anywhere in the VCLI. This state should be displayed in the output of the command show conn pl config. |
|
| VCLI 2.2.8
| ||
DDTS Number | Severity | Functional Area | Problem Description |
CSCsn05808 | Medium | Show conn | VCLI used to display the incorrect circuit type on a backup CES card with the command show conn all sum when a backup was switched in for a primary. |
CSCdm73146 | Medium | Change BERT | User was unable to tell a circuit that was currently running a bert test to invert the transmit pattern. The command was "change connection segpl -txpattinv on -epid <endPointid>" |
CSCdm77694 | High | Show CES info | In Release 2.1.X of the VCLI, it didn't read the manufacturing related information attributes correctly for CES cards for the command show cescard info. |
CSCdm77832 | High | ATM Port stats | VCLI returned error when trying to retrieve the stats for the command show logicalport atm stat. |
CSCdm77686 | Medium | Show phy ds1 | The row label for DS1 Frame errors didn't say that Frame Errors are measured as any second that contained a frame error. Instead it led the user to believe that the count displayed was the actual number of frame errors. |
CSCsn05790 | High | Redundancy | In certain situations the VCLI used to give an error when the user attempted to put a CES card in the primary role from a role of None. A second attempt seemed to work. |
CSCdm75085 | High | Show OC3 sum | VCLI shows the operational state of the SONET Path layer on the Access OC3 to be up when either the SONET Section, SONET Line Layers are operational down. |
CSCdm82392 | Medium | Change sys switch | Using the command "change system switch -sname <new_name>" didn't update the VCLI database files. |
CSCsn05541 | Medium | BladeMon | VCLI takes a long time to establish communication with CES card after the card reboots. Now it communicates within seconds after the CES card is available for communication. |
CSCsn05684 | Medium | BladeMon | Duplicate problem of CSCsn05541. |
CSCsn05781 | Low | BladeMon | Exit and restart of VCLI causes delay in communicating with the CES cards in the network. Now the BladeMon process keeps in contact for the VCLI. |
CSCsn05736 | Low | BladeMon | Need to make BladeMonitor a stand alone application. |
| VCLI 2.1.3
| ||
DDTS Number | Severity | Functional Area | Problem Description |
CSCsn05743 | High | Connection creation | Connection created on switched out primary card, shows type Remote-Pl |
CSCsn05744 | High | Show command | Inconsistent or misleading information with cmd show cescard info |
CSCsn04734 | High | Connection deletion | When not able to delete connection, the EPID is not given |
CSCdm60856 | Medium | Switch names | Switch names cannot take the underline char. |
CSCdm59553 | High | Change OC3 | Missing feature to change the AIS to RDI flag |
CSCsn05811 | High | Switch names | Only 3 chars of switch name are displayed on error |
CSCsn05846 | High | Ds3 summary | Missing check for container down state in cmd show phy ds3 summary |
CSCsn05864 | High | Connection deletion | Can't always delete partially created circuits |
CSCsn05771 | High | Redundancy | Loss of communication when redundancy state of the CES cards is in unknown state |
CSCsn05715 | Medium | Connection creation | Can't delete an invalid connection |
CSCdm72267 | Medium | Connection creation | VCLI doesn't show the name of the cktid when a connection is created |
CSCsn05815 | Medium | User response | Acceptance of Y/y and N/n instead of complete word when user acceptance is required |
Cisco MGX 8240 Hardware Installation Guide, DOC-7810084=. Gives information on installing the MGX 8240 chassis, including physical connectivity, logical connectivity, and cabling.
Cisco MGX 8240 Hardware User's Guide, DOC-7810083=. Gives theory of operations and usage information on the MGX 8240. Details physical description, traffic management, and FDOS.
Cisco MGX 8240 VCLI User's Guide, DOC-7810082=. Gives information on installation and use of Virtual Command Line Interface (VCLI) for MGX 8240. Details installation, provisioning, and specific commands for the VCLI.
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
---|---|
English | tac@cisco.com |
Hanzi (Chinese) | chinese-tac@cisco.com |
Kanji (Japanese) | japan-tac@cisco.com |
Hangul (Korean) | korea-tac@cisco.com |
Spanish | tac@cisco.com |
Thai | thai-tac@cisco.com |
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Access Registrar, AccessPath, Any to Any, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, MultiPath Data, MultiPath Voice, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Service Node, Virtual Voice Line, VisionWay, VlanDirector, Voice LAN, WaRP, Wavelength Router, Wavelength Router Protocol, WebViewer, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (9912R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Sat Jan 13 20:22:12 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.