|
|
November 9, 2000
These release notes for the Cisco 6700 Series support software release 1.3(2). These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and related documents.
For a list of the software caveats that apply to release 1.3(2), see the "Caveats" section.
These release notes discuss the following topics:
This section describes system requirements for software release 1.3(2) and includes the following:
Software release 1.3(2) supports the Cisco 6705 and Cisco 6732 integrated access devices.
The following table lists Cisco 6700 Series service modules and line interface modules supported by release 1.3(2):
| Module Name | Supported Platforms | Ordering Number |
|---|---|---|
BPS-AC | Cisco 6705 | 6705-PWR-AC= |
MCC-INT | Cisco 6705 | 6705-SM-MCCINT= |
BPS-HP | Cisco 6732 | 6732-PWR-HP= |
MCC-STR3 | Cisco 6732 | 6732-SM-MCC3= |
MCC-STR4 | Cisco 6732 | 6732-SM-MCC4= |
MTAC-TEI | Cisco 6732 | 6700-SM-MTAC-TEI= |
AMM | Cisco 6732 | 6700-SM-AMM= |
BRG | Cisco 6705 and Cisco 6732 | 6700-SM-BRG= |
RUVG/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-RUVG-8= |
FXS/16 | Cisco 6705 and Cisco 6732 | 6700-LIM-FXS-16= |
DSX1/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-DS1= |
T1-2-V35 | Cisco 6705 and Cisco 6732 | 6700-LIM-T1-2-V35= |
DSX3/CHNL | Cisco 6705 and Cisco 6732 | 6700-LIM-DS3-C= |
STSX1/CHNL | Cisco 6705 and Cisco 6732 | 6700-LIM-STS-1= |
OC3c-UNI | Cisco 6705 and Cisco 6732 | 6700-LIM-OC3-UNI |
RPOTS/16 | Cisco 6705 and Cisco 6732 | 6700-LIM-RPOTS-16= |
MSDSL-2W | Cisco 6705 and Cisco 6732 | 6700-LIM-MSDSL-2W= |
ISDN-BRI/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-BRI-8= |
The Cisco 6700 series software release 1.3(2) should be used in conjunction with version 1.3 of the Element Management System (EMS) software.
To determine the version of software currently running on the Cisco 6700 Series device, you must connect the chassis to a workstation with EMS installed. For more information about installing EMS, see the "EMS Installation" section of the Cisco 6700 Series Element Management System User Guide .
Step 2 In the EMS root view, double click on the node icon representing the Cisco 6705 or Cisco 6732 chassis. EMS launches the node view for the chassis.
Step 3 In node view, double click on the nameplate button (located near the top of the window). EMS launches the NE provision window.
Step 4 The software release is listed in the NE Loaded Software Version field.
Use the following procedure to upgrade the software image on the Cisco 6732.
 |
Caution Cisco recommends that you perform a local software upgrade, with a local EMS workstation directly connected to the Cisco 6732 chassis. |
Before beginning the embedded software upgrade, complete the following tasks:
 |
Note When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of COT is mishandled, the entire network may be lost. Upgrade tests and sample enhancements should be made at the edge node. If the upgrade tests fail on the edge nodes, never attempt to upgrade the COT node. |
The Cisco 6732 software upgrade procedure consists of the following sections:
Step 2 Double-click the node nameplate to launch the NE Provision window.
Step 3 Click Common Control Card Switch Over in the function bar to display the switchover window.
Step 4 Look at the Active MCC field. EMS identifies the active MCC.
Step 5 The MCC that is not active is called the standby MCC. For example, if MCC-A is active, then MCC-B is the standby MCC.
Step 6 Click Exit to return to node view.
Step 2 Set the Admin Status field to OutOfService.
Step 3 Click Apply to place the MCC card out of service.
Step 4 Click Exit to return to node view.
Step 2 Click Software Upgrade in the function bar to display the Software Upgrade window.
Step 3 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 4 In the Software Image File Name field, enter SwLoad.fbx.
Step 5 In the Upgrade Software to Main Common Control Card field, select the standby MCC card.
|
Note Upgrade the MCC that is not shown in the Active Main Control Card field. For example, if EMS shows that the active main control card is A, you must select B for the upgrade field. |
Step 6 Click Apply to confirm the host IP address and path to the image filename.
Step 7 Click Upgrade to download the embedded software image into the Flash memory of the standby MCC card.
Step 8 EMS displays a progress bar. Wait until the software upgrade is complete.
|
Caution If EMS is unable to complete the embedded software upgrade, an error message will be displayed at the bottom of the NE provision window. This error message will also be displayed in the Problem List of the MCC card. In this case, do not reset the MCC card; restart the embedded software upgrade process. |
Step 9 Click Exit to return to node view.
Step 2 Right-click the node being upgraded, and select Node Critical Commands from the popup menu.
Step 3 Click MCC Reset in the function bar to open the line card reset window.
Step 4 In the Reset MCC field, select the standby MCC (A or B)
Step 5 Click Reset to reset the selected MCC. The MCC begins a reset and initialization procedure.
|
Note Allow 30 to 45 seconds for the MCC to complete the reset procedure. |
Step 6 Click Exit to return to net view.
Step 2 Double-click the standby MCC card. EMS launches the Plugin Card Provision window.
Step 3 Set the Admin Status field to InService.
Step 4 Click Apply to place the card out of service.
Step 5 Click Exit to return to node view.
Step 2 Click Common Control Card Switch Over in the function bar.
Step 3 Click Switch to switch control from the active MCC to the standby MCC.
Step 4 Click Exit to return to node view.
After performing an MCC switchover, you must upgrade the remaining MCC. Repeat the software upgrade procedure, beginning with the "Place Standby MCC Card Out of Service" section. Note that the roles of standby and active MCC have now been switched. For example, if you upgraded MCC-B during the first procedure, you must now upgrade MCC-A.
|
Caution The following procedure reboots the line interface modules and effectively takes them out of service. Any traffic being carried on the cards will be dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
Step 2 Right-click the node being upgraded, and select Node Critical Commands from the popup menu.
Step 3 Click Line Card Reset in the function bar to open the line card reset window.
Step 4 Set the Reset field to Yes.
Step 5 In the Equipped Cards list, highlight all line cards to be reset.
|
Note The BPS-HP and AMM service modules do not need to be reset. |
Step 6 Click Apply to reset all selected line cards.
The latest embedded software image is available on Cisco Connection Online (CCO).
|
Caution Cisco recommends that you perform a local software upgrade, with a local EMS workstation directly connected to the Cisco 6705 chassis. |
Before beginning the embedded software upgrade, complete the following tasks:
|
Note When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of COT is mishandled, the entire network may be lost. Upgrade tests and sample enhancements should be made at the edge node. If the upgrade tests fail on the edge nodes, never attempt to upgrade the COT node. |
Perform the following steps to upgrade or install the embedded software:
Step 2 From node view, double-click the node nameplate to launch the NE provisioning window.
Step 3 Select Software Upgrade from the function bar to display the software upgrade window.
Step 4 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 5 In the Software Image File Name field, enter SwLoad.fbx.
Step 6 The Upgrade Software to Main Common Control Card field should be set to A; the Cisco 6705 has only one MCC card, identified as A.
Step 7 Click Apply to confirm the host IP address and path to the image filename.
Step 8 Click Upgrade to download the embedded software image into the Flash memory of the MCC card.
|
Caution If EMS is unable to complete the embedded software upgrade, an error message will be displayed in the EMS NE provisioning window. In this case, do not reset the MCC card; restart the embedded software upgrade process. |
Step 9 The MCC card must be reset before the new embedded software becomes active. Use one of the following procedures to reset the MCC card:
|
Caution Resetting the MCC card causes all line cards in the Cisco 6705 to be reset as well, momentarily placing the line cards out of service. Any traffic being carried on the line cards will be lost or dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
The following sections list the new hardware and software features supported by the Cisco 6700 Series for software release 1.3(2):
The following new hardware features are supported by the Cisco 6700 Series for software release 1.3(2).
The Cisco 6732 now supports the main control card with stratum 4 clock (MCC-STR4). The MCC-STR4 provides a less expensive timing solution for use with interfaces slower than OC-3.
The OC3c-UNI line interface module offers point-to-point ATM UNI connections over a bidirectional optical interface at the SONET OC-3 rate (155.52 Mbps).
The RPOTS/16 line interface module offers 16 POTS ports. Use of this card requires a ring generator—either a bank ring generator (BRG) service module or an external ringer.
The MSDSL-2W card provides 4 independent CAP MSDSL two-wire interfaces, capable of carrying payload rates of 144 kbps to 2320 kbps. This module can be used to provide a single pair T1 or fractional T1 transport between Cisco 6732 nodes, or between a Cisco 6732 node and a Telmax CPE device.
The ISDN-BRI/8 line interface module offers eight ports supporting standard basic rate interface (BRI) with 4:1 D channel mapping. The ISDN-BRI/8 module has been certified to interoperate with Nortel and Lucent Class 5 switches over a GR-303 interface.
The metallic test access card-test equipment interface (MTAC-TEI) provides both craft access and third party test box access to the test bus in the Cisco 6732 chassis. The MTAC-TEI is used in conjunction with the Harris 107A/F remote test unit.
The Cisco 6732 now offers one to one protection (redundancy) of broadband line interface modules (DSX3/CHNL and STSX1/CHNL) located in slots 17-20.
The Cisco 6732 can now accommodate DSX3/CHNL and STSX1/CHNL line interface modules located in slots 21-32. Up to 10 DS1s are available to broadband line interface modules located in slots 21-32.
The MCC-INT service module on the Cisco 6705 supports up to 3 Mbits of user bandwidth over the Ethernet port. Implementation is RFC 1483 (PPP over ATM) standard compliant.
A Cisco 6705 chassis with a disabled Ethernet port can be accessed locally in case of inter node data link failure. See the "Ethernet Shutdown Recovery on the Cisco 6705" section for a detailed recovery procedure.
The following new software features are supported by the Cisco 6700 Series for software release 1.3(2).
The EMS client/server based network configuration server allows EMS users to remotely access Cisco 6700 network configuration data located on the server computer. Any configuration change made by an authorized EMS user will also be propagated to other concurrent EMS users.
The Cisco 6700 Series Element Management System (EMS) now offers three functional levels of user security and privileges.
Dynamic bandwidth allocation (DBA) allows ATM data to pass over idle DS0 voice channels on T1-2-V35 and MSDSL-2W line interface modules. When the voice channel becomes active, the DS0 is reallocated for voice traffic without affecting ATM data traffic.
The Cisco 6700 Series supports 100 FDL-INDLs and in addition 16 DS0 based INDLs between nodes.
The following section contains information about hardware and software limitations of your Cisco 6700 Series system for software release 1.3(2):
Inter node data links (INDLs) created on an MSDSL-2W line interface module must use the DS0 data link type if providing ISDN services on the remote node.
One to one broadband module (DSX3/CHNL and STSX1/CHNL) protection on the Cisco 6732 does not support FDL-based INDLs in a protected pair. The INDL is unavailable while the protecting (backup) module is active. Once service is restored on the protected (primary) module, the FDL INDL is reestablished. This is not traffic affecting.
Software release 1.3(2) does not support derived timing off of a DSX3/CHNL line interface module.
Loop up and loop down maintenance codes are only supported over the superframe (SF) line frame type.
The extended superframe (ESF) line frame type only supports 16-state signaling.
With an HDLU link carrying a DS0 provisioned for dynamic bandwidth allocation (DBA) from a TR-008 switch interface, groundstart operation is not supported. Groundstart operation functions normally over non-DBA DS0 channels.
A Cisco router connected to a DSX1/CHNL, T1-2-V35, or MSDSL-2W interface on the Cisco 6732 or Cisco 6705 must use extended superframe (ESF) signaling mode and bit 8 zero suppression (B8ZS) frame format.
Inter node data links with more than 2 hops (daisy-chain) which include an OC3 connection are not supported in software release 1.3(2).
Internal cross-connects between two broadband modules (DSX3/CHNL, STSX1/CHNL, or OC3c-UNI) placed in high-speed slots 17-20 can prohibit the use of certain general-purpose slots. Table 2 lists the slots that are disabled by a broadband to broadband cross-connect. If you attempt to provision a disabled slot, EMS gives an error message.
| Broadband Slot | Disabled Slots |
|---|---|
17 | 9, 10 |
18 | 11, 12 |
19 | 13, 14 |
20 | 15, 16 |
For example, if an STSX1/CHNL module in slot 17 is cross-connected to an STSX1/CHNL module in slot 19, slots 9, 10, 13, and 14 will be unavailable.
|
Note This restriction applies to both static (nailed-up) and dynamic (GR-303) cross connects. |
This section contains important information about the use of your Cisco 6700 Series system:
EMS uses password files to control access to security-sensitive operations such as resetting the MCC, erasing the system database, and shutting down the alarm server. If you attempt to execute a password-protected operation without the password file in place, EMS responds with the error message "Password file does not exist."
Contact your network administrator to obtain the password files and corresponding passwords for EMS.
|
Note The network configuration server must be launched prior to launching EMS net view. See the Cisco 6700 Series Element Management System User Guide for more information. |
From your workstation's desktop view, double-click the Cisco 6700 Netconfig Server icon to launch the alarm server. The hourglass (system busy) cursor will appear briefly, indicating that the network configuration server is being launched. The network configuration server application does not appear in the Windows taskbar or system tray when launched.
In the event of loss of communications with a Cisco 6705 node, use the following procedure to enable the Ethernet port on the Cisco 6705 MCC-INT module.
Step 2 Launch EMS net view on the workstation and log in
Step 3 Identify the node icon of the Cisco 6705 that will be recovered.
Step 4 Physically unseat the MCC-INT in the Cisco 6705 chassis by lifting the removal lever and gently pulling the module away from the backplane.
Step 5 Reseat the MCC-INT by gently sliding the module into the chassis and pressing down on the lever. The MCC-INT begins an initialization sequence.
Step 6 While the MCC-INT is initializing, double-click the Cisco 6705 icon in EMS net view. The Cisco 6705 node view appears when the MCC-INT has finished its initialization procedure.
Step 7 In the Cisco 6705 node view, double-click on the MCC Ethernet port.
|
Note You must place the Ethernet port in service no later than 30 seconds after the MCC-INT finishes its initialization procedure. |
Step 8 Set the AdminStatus of the Ethernet port to inService.
You can now use the Ethernet port on the Cisco 6705 MCC-INT module to establish communications. See the Cisco 6700 Series Element Management System User Guide for further provisioning procedures.
Use the following procedure to delete CRVs between the Cisco 6732 and a Class 5 switch:
Step 2 Delete the CRVs from the Cisco 6732 using EMS.
The Class 5 switch GR-303 interface serves as the master controller of the Cisco 6732 GR-303 database. If this procedure is not followed, the Cisco 6732 database might lose synchronization with the Class 5 switch.
Each call reference value (CRV) provisioned on an ISDN-BRI/8 module occupies three DS0 channels (one DS0 each for the B1, B2, and D channels) over the transport between the Cisco 6732 and the remote node. When provisioning CRVs for ISDN, make sure that the interface group uses enough transport lines to accommodate three DS0s for each CRV.
For example, a DS1 transport between a Cisco 6705 remote node and a Cisco 6732 local node can carry up to 8 ISDN lines (24 divided by 3) over an FDL INDL. A DS1 transport using a DS0 INDL can carry up to 7 ISDN lines, since one DS0 is used as the INDL (leaving 23 available DS0s).
When deleting an ISDN CRV, you must delete the CRV from the switch prior to deleting it in EMS. Monitor the facility service state through EMS to ensure that the CRV has been deleted from the switch side. A transition from in service to out of service will indicate that the switch has deleted the CRV from its database. After confirming its deletion from the switch side, delete the CRV in EMS.
Under heavy traffic conditions, when deleting an ISDN CRV from the Class 5 switch and the Cisco 6732, the switch might not delete the quarter DS0 carrying the D channel from the Cisco 6732 database. This issue depends on the switch scheduler for deleting CRVs; excessive traffic can delay or prohibit the removal of the quarter DS0.
When displaying the expanded line view of a cross-connected GR-303 facility, the channel with a quarter DS0 displays a small black hashmark next to the channel. In this case, use EMS to delete the quarter DS0. See the sections "Deleting a Quarter DS0 Cross Connect" and "Deleting a Quarter DS0" for detailed procedures.
Step 2 Select the line that is provisioned with the cross connect. EMS displays the internal cross-connects.
Step 3 Look for a channel with a small black hashmark to the right. This channel carries the quarter DS0. In Figure 1, channel 3 of an STS1 transport carries a quarter DS0.
Step 4 Right-click the quarter DS0 channel and select Display Quarter DS0. EMS launches the cross connect display.
Step 5 Double-click a cross connect line to launch the cross connect provisioning window.
Step 6 Click Delete.
Step 7 EMS displays a warning, recommending that this operation be performed from the switch. Click Yes to proceed.
If EMS is unable to delete the cross connect, an error message will appear.
Step 8 After deleting the cross connect, you must close and relaunch the cross connect display to reflect the changes made.
Step 2 Select the appropriate QDS0 from the pull-down menu.
Step 3 Click Delete.
Step 4 EMS displays a warning, recommending that this operation be performed from the switch. Click Yes to proceed.
|
Note EMS displays an error message if you attempt to delete a cross connected QDS0. You must delete the cross connect before deleting the QS0. |
Step 5 The cross connect box is refreshed with the current QDS0 status when the user exits from the QDS0 provisioning screen. For instance, if all QDS0s on a DS0 have been deleted, a black hash mark no longer appears on the DS0.
The install script creates two scripts—ems.csh and ems.ksh—in the EMS installation directory. If you are upgrading or reinstalling EMS on the workstation, the script files, network configuration, and alarm information will all be retained from the previous installation.
EMS may be installed in any directory in which the user has write privileges (root directory). The EMS distribution package for UNIX (ems_unix) contains three files:
To install EMS:
1. Choose whether you want to install directly from the CD-ROM or first copy the distribution into a user account. If installing directly from the CD-ROM, go to Step 3. Otherwise, enter the following commands:
# cp * <user directory>
# cd <user directory>
2. Add execute rights to the install script:
# chmod +x emsinstall
3. Execute the install script:
# ./emsinstall
EMS Unix Installation
---------------------
4. Press Return to select the default file name and location, ./ems.tar.
Enter tar file name [./ems.tar]:
Setting up installation...done.
5. Enter a fully qualified path name for the EMS Installation directory. If the B10EMS_HOME environment variable has already been set from a previous installation, the script permits the user to use that value.
Where would you like to install the EMS?
Enter fully qualified path name: /export/home0/ems
Creating /export/home0/ems...done.
Extracting EMS files...
...
Placing EMS files in /export/home0/ems...done.
6. Enter y to install the network configuration server, or enter n to skip installation.
Will this installation use the network configuration server (y/n)? [n]: y
Generating script files with environment variables...done.
Files /export/home0/ems/ems.csh
and /export/home0/ems/ems.ksh
have been created. Set the value of B10EMS_SERVER and
c6700NET_SERVER if necessary in the appropriate file and source it before running the EMS.
Hit Enter to complete the installation...
Completing installation...
EMS installation is complete. The EMS includes the 'nmtrapd' program which requires root permissions. Please get root permissions and type >> ./emsinstall root << to install it.
7. If you do not want to install the alarm server, skip to Step 11.
8. Set user to root:
# su
9. Execute the emsinstall script with root privileges:
# ./emsinstall root
10. Exit from the root login:
# exit
11. You must configure the IP addresses of the alarm server and network configuration server. Use vi or another text editor to set the B10EMS_SERVER (alarm server) and C6700NET_SERVER (network configuration server) variables. Contact your network administrator for the correct IP addresses.
# vi ems.csh
"ems.csh" 12 lines, 406 characters
setenv B10EMS_HOME /export/home0/ems
setenv B10EMS_SERVER
setenv C6700NET_SERVER
setenv TCL_LIBRARY $B10EMS_HOME/lib/tcl
setenv TK_LIBRARY $B10EMS_HOME/lib/tk
setenv TNM_LIBRARY $B10EMS_HOME/lib/tnm
setenv TNM_NMTRAPD $B10EMS_HOME/bin/nmtrapd
if (\Qsetenv | grep LD_LIBRARY_PATH\Q != "") then setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:${B10EMS_HOME}/lib
else setenv LD_LIBRARY_PATH ${B10EMS_HOME}/lib
endif
12. After editing the ems.csh or ems.ksh file, you must update the environment.
# source ems.csh
# env
...
B10EMS_HOME=/export/home0/ems
B10EMS_SERVER=171.68.205.106
C6700NET_SERVER=171.68.205.106
TCL_LIBRARY=/export/home0/ems/lib/tcl
TK_LIBRARY=/export/home0/ems/lib/tk
TNM_LIBRARY=/export/home0/ems/lib/tnm
TNM_NMTRAPD=/export/home0/ems/bin/nmtrapd
LD_LIBRARY_PATH=/export/home0/ems/lib
# exit
13. To enable the node critical commands and alarm server passwords, copy the following password files from the EMS CD to the ems/data/netconfig directory:
The Element Management System (EMS) can be loaded using C-Shell or Korn Shell. You can use your own login to execute the startEMS script.
To start the alarm server, network configuration server, and EMS net view, three scripts are provided:
|
Note The display environment has to be set when the alarm server is running, or the environment variable must point to some other display that is up. If this is not done, logging out of EMS will close the display environment and shut down the alarm server. |
|
Note The alarm server uses ports 162 and 2321 as trap daemons. These ports must not be in use when starting the alarm server. |
These programs reside in the EMS installation directory/bin directory, and they can be invoked from any directory included in the path.
All Cisco 6700 Series line interface modules are synchronized to Greenwich Mean Time (GMT), rather than the "Time of Day" setting on the EMS workstation. One-day performance monitoring (PM) tests use GMT, not the EMS time of day, to determine the start and end times of the 24-hour monitoring window.
This section contains open and resolved caveats for the current Cisco 6700 Series software release.
This section describes possibly unexpected behavior by release 1.3(2). This section describes only severity 1 and 2 caveats.
The following sections describe the documentation available for the Cisco 6700 Series. The most up-to-date documentation can be found on the web via Cisco Connection Online (CCO) and on the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard copy documents were printed. These release notes should be used in conjunction with the documents listed in the following sections:
The documents listed in Table 3 are available for the Cisco 6700 Series. These documents are also available online at Cisco Connection Online (CCO) and on the Documentation CD-ROM. To access Cisco 6700 Series documentation on CCO, follow this path:
Service and Support: Technical Documents: Documentation Home Page: DSL Products: Cisco 6700 Series
To access Cisco 6700 Series documentation on the Documentation CD-ROM, follow this path:
DSL Products: Cisco 6700 Series
| Document Title | Chapter Topics |
|---|---|
Cisco 6732 Full Access Device | Product Overview |
Cisco 6705 Integrated Access Device | Product Overview |
Cisco 6700 Series Element Management System | Overview |
For service and support for a product purchased directly from Cisco, use CCO.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Products & Technologies: Products: Technical Tips.
The following sections are provided from the Technical Tips page:
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 condition 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 reach 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.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which package that 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.
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 Nov 10 16:07:29 PST 2000
Copyright 1989-2000©Cisco Systems Inc.