|
|
These release notes describe new features for the Cisco IOS Release 12.0(2a)T1 feature packs for Cisco MC3810 multiservice access concentrators.
These release notes contain the following topics:
This section explains how to use this document, describes feature pack components, and has tables that define the aspects of a feature pack.
The tables in these release notes contain details about the Cisco feature packs. Use these tables to perform the following tasks before loading a software image onto a router:
1. Use Table 1, "Feature Pack Product Numbers Quick-Reference List," to identify the software image you want to load.
2. Use Table 2, "Cisco MC3810 Feature Packs," to identify your feature pack and the memory required for your feature set, based on the image you load.
3. Use Table 4, "Cisco MC3810 Series Default Memory and Upgrade Options", to check the memory required for your feature set, and determine the factory-default memory on the router and the available memory upgrades.
4. Use the "Feature Set Tables" to identify which features are supported in a feature set image.
A feature pack is a small box that contains the following items:
The heart of a feature pack is the CD-ROM that contains software images and the Router Software Loader (RSL), which is a Windows 95 application that loads an image onto an access router or server. Each feature pack CD-ROM contains at least one Cisco IOS feature set. The CD booklet, Getting Started with the Router Software Loader, explains how to use the RSL to install the router image. If you cannot use the RSL to load images, you can follow the instructions in the "Alternatives to the RSL" section.
Before running the RSL, read the "Installing Software Images Using the RSL" section. If you are loading software on a preconfigured router, you should save the router configuration file on your PC before beginning the image download process, as described in Getting Started with the Router Software Loader.
Table 1 lists the Cisco product numbers of the feature packs supported in this release.
Table 2 identifies each feature pack as specified on the router software CD-ROM label, describes the feature sets in each feature pack, and lists the following: UNIX and DOS filenames of the images, memory requirements, and RSL installer description.
The Cisco IOS software is packaged into "feature sets" (also called "images"). Many different feature sets are available, and each feature set contains a specific subset of Cisco IOS features. The following conventions are used to identify feature sets:
The following list shows which feature sets are supported on the Cisco MC3810 multiservice access concentrator. These feature sets only apply to Cisco IOS Release 12.0(2a)T1:
To determine what features are available with each feature set (software image), see Table 3. The table summarizes the features you can use when running a specific feature set on the Cisco MC3810 multiservice access concentrator for Cisco IOS Release 12.0(2a)T1. Table 3 uses these terms:
| 1When the older motherboard (SCB 6.06) is used with this feature, serial port 1 cannot be used. When the new motherboard (SCB 6.07) is used, serial port 1 can be used, clocked at speeds up to 192 kbps.
2Voice signaling on CES is not available. 3ATM PVCs only. SVCs are not supported. 4Includes T1 CAS protocols, plus UK Standard CAS (Mercury protocol) and CEPT standard E&M. 5Applicable to data-only interfaces. 6Applicable to data-only interfaces. |
This section describes the system requirements for Release 12.0(2a)T1 and includes the following sections:
Table 4 lists the memory delivered by the default and the available memory upgrades. See also the "Feature Pack Overview Table" section for more memory requirements information.
| Memory Type | Cisco MC3810 Defaults | Upgrade Options |
|---|---|---|
4-MB upgrade: MEM-381-1X4F= |
||
| 1Cisco MC3810 Access Concentrators using Cisco IOS Release 12.0 or higher require at least 8 MB of Flash memory. Flash memory of 16 MB is required for running dual Cisco IOS Images.
2The Cisco MC3810 Access Concentrator has a DRAM SIMM socket that can hold a 16- or 32-MB DRAM SIMM. |
Cisco IOS Release 12.0(2a)T1 supports the following platform:
The feature packs described in these release notes contain Cisco IOS Release 12.0(2a)T1 software images, some earlier images, and Router Software Loader (RSL) Version 7.3. Before running RSL, read the "Installing Software Images Using the RSL" section.
To make file management easier, the Cisco MC3810 provides a complete file system for software images, message files and reports. The standard Flash memory size is 8 MB, and a 16-MB upgrade option is available. The 16-MB version can hold two code images simultaneously for fail-safe upgrades.
Management and configuration of the Cisco MC3810 should be familiar to the Cisco IOS user and compatible with existing management systems. As such, it provides a superset of the Cisco command-line interface (CLI). The Cisco MC3810 can be managed by standard Cisco management platforms and facilities. The Cisco MC3810 can be managed by CiscoView in addition to the native remote login facilities provided by Telnet and rlogin. Three types of configuration interfaces are provided:
The HTTP-based interface allows configuration from any Web browser such as Netscape Navigator or Microsoft Explorer. The SNMP MIB allows management of the Cisco MC3810 from SNMP managers (for example, HP OpenView).
To determine the version of Cisco IOS software currently running on the Cisco MC3810 multiservice access concentrator, log into the platform and use the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:
Additional command output lines include more information such as processor revision numbers, memory amounts, hardware IDs, and partition information.
This section provides solutions to problems you might encounter when using the RSL to load Cisco IOS software on the Cisco MC3810 multiservice access concentrator.
This section describes some solutions to problems you might encounter when using the RSL. These solutions are additions to RSL online help.
This installation tip provides a possible recovery solution if you are unable to connect to your access server or router. You can skip this section unless you are experiencing a connection error.
In some cases, you might receive the following error message while connecting to the target access server:
If you encounter this message, try increasing the Short Timeout value, which is set to 25 seconds, in the Options dialog box, especially if one of the following situations applies:
Note Increasing the Short Timeout value might increase the time it takes for RSL to connect to the target access server.
In some cases, the RSL is unable to restore the startup configuration. If this happens, take the following steps:
Step 2 Restart the RSL, and connect by using the Preconfigured router option.
Step 3 When asked if you want to overwrite the existing startup configuration file, choose no.
Step 4 When asked if you want to continue, choose yes.
Step 5 When the router is connected, select Download Router Configuration in the Router Software Loader dialog box.
Step 6 Select the appropriate file, and click the radio button beside Copy configuration to the router nonvolatile memory.
The router should now contain the startup configuration it had before the initial RSL connection. You can now exit the RSL.
Note In the previous situation, the router configuration register (config-register 0xnnnn) is not restored.
Note If you press Ctrl-Alt-Delete to terminate the RSL, the router configuration and configuration register are not restored. However, in this case the configuration file is not deleted from the PC, so you can restore it using the previous steps, beginning with Step 2.
The following information about RSL operations can help you with the installation process:
The RSL is designed to work with a PC running Microsoft Windows 95 and is the recommended method for downloading software to the router. The booklet included with the CD-ROM explains how to perform this simple install process. However, two alternatives are available for installing router software:
This section explains how to use the copy xmodem flash command to install the router software from the CD-ROM onto the router.
Note The transfer takes place only on the port at which you issue the command. If you download via the console, all console output is discarded for the duration of the transfer. You can only download files to the router; you cannot copy files from the router. Cisco recommends using the auxiliary port for this type of software download. The auxiliary port has hardware flow control and full modem control. In addition, the transfer does not occupy the system console so it is free for other uses.
The following example shows how to use the copy xmodem flash command on a Cisco MC3810 multiservice access concentrator.
Use this TFTP server application method as an alternative to using the RSL to install the router software from the CD-ROM. You can perform this procedure using a PC (running Microsoft Windows 95 or Microsoft Windows 3.1), a Macintosh, or a UNIX system. You can use either the copy tftp flash or copy rcp flash command to download the router software to the router.
First, obtain a TFTP application or a remote copy protocol (rcp) application to set up your computer as a TFTP server or an rcp server. Use the RSL or the TFTP server included on the feature pack CD-ROM to install the router software only if you are using a PC running Windows 95. For other operating systems, a number of TFTP or rcp applications are available from independent software vendors or available as shareware from public sources on the World Wide Web.
Note To use an rcp application, follow the same procedure, and substitute rcp for TFTP in the instructions. Use the copy rcp flash command instead of the copy tftp flash command.
Step 2 Launch the TFTP server application on the PC, usually by double-clicking the application icon or its .exe filename.
Step 3 Set up the PC as a TFTP server by using the TFTP server application setup or configuration facility.
Most TFTP server applications include a setup facility that allows you to specify the PC as a server. For example, from the TFTP menu of one application, you can select Settings to display a panel that includes a check box beside the word Server. To configure the local PC as a server, select this check box.
The TFTP server also allows the selection of a "root" directory. You must select the directory in which the Cisco IOS files reside, for example, d:\cpswinst\images.
Caution Make sure you set up your local PC as a TFTP server. If you overlook this step, you cannot perform the copy procedure. This reminder also applies if you are using rcp instead of TFTP. |
Step 4 Establish a console session from your local PC (which is now configured as a TFTP server) to the Cisco router by using one of these methods:
This is the recommended method. When you reload the router with the new image in Step 16, you remain connected to the router. (If you use Telnet, you lose connection to the router.)
Step 5 Connect your PC Ethernet port to the corresponding router LAN port. Use the 10BaseT crossover cable to connect to an Ethernet port. Use straight-through cables if you are connecting via a 10BaseT hub or a 100BaseT hub.
Note We recommend that you back up the router configuration before upgrading the router software.
Step 6 Enter the following commands to set the configuration register to 0x2101 and reload to the bootstrap image:
Step 7 Enter yes in response to the prompt asking if the system configuration has been modified:
Step 8 If the password prompt appears, enter the password.
Step 9 At the router prompt, enter enable and then the password:
Step 10 At the router prompt, enter the following command to copy the new software image from the PC CD-ROM drive to the router:
Router(boot)(config)# copy tftp flash
In the next series of steps, you download the Cisco IOS Release 12.0(2a)T1 images that you want installed on your router.
Step 11 When prompted, enter the IP address of your PC, as in the following example:
Address or name of remote host [255.255.255.255]? 131.108.1.1
This is the IP address of your local PC, not that of the router.
Step 12 When prompted, enter the filename of the Cisco IOS Release 12.0(2a)T1 image to be copied to the router, as in the following example:
This example specifies the DOS image name of the IP feature set for Cisco MC3810 multiservice access coucentrator (as shown in Table 2 in the section, "Feature Pack Overview Table").
Step 13 In response to the prompt, enter the destination UNIX image filename, and press Enter.
This is the name of the image file on the router, not the full pathname of the image on the CD-ROM attached to the PC. Refer to Table 2 in the section, "Feature Pack Overview Table" for the UNIX image filename.
During the transfer process, the software displays messages indicating that it has accessed the file you have specified and is loading it.
Step 14 Enter yes in response to the prompt asking if you want to erase the existing image copy resident in the router Flash memory before copying the new one.
Erase flash device before writing? [confirm] yes
The entire copying process takes several minutes and differs from network to network.
The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory.
Step 15 Enter the following commands to reset the configuration register to 0x2102.
Step 16 Enter the reload command to reload the router:
After reload is complete, the router should be running the required Cisco IOS image. Use the show version command to verify.
This section contains important information about the use of your Cisco IOS Release 12.0 software.
In Cisco IOS Release 11.3(1) MA, serial 2 was a valid port number. Beginning with Cisco IOS Release 12.0(1), the interface serial 2 designation on the Cisco MC3810 is no longer valid. Depending on the application, you enter different designations for this interface as follows:
Because the older Cisco Management Information Bases (MIBs) do not scale well across Cisco products, they will be replaced in a future release. As an initial step toward this, the OLD-CISCO-* MIBS are being deprecated now. This has no immediate impact on any existing Cisco IOS product or network management system (NMS) application. Application developers need to be aware that the following MIBS are being discontinued and update their applications accordingly. Table 5 lists the deprecated MIBs.
| Deprecated MIB | Replacement |
|---|---|
This section describes important notes regarding use of the Cisco MC3810 with the Public Switched Telephone Network (PSTN).
Care should be exercised when connecting switched voice ports on the Cisco MC3810 directly to the PSTN because improper configurations can expose the corporate network to telephone fraud.
The Cisco MC3810 has the capability to connect a user from the PSTN directly to the corporate wide-area telephone network. As a phone switch, the Cisco MC3810 can be configured to switch the user to any location in that network, even remote locations that are connected again to another PSTN. However, the Cisco MC3810 does not provide any mechanism to restrict users from calling after they are connected. Without proper network design, this condition could result in the unauthorized use of the corporate network for making calls at the corporation's expense. To prevent this from occurring, Cisco does not recommend connecting a switched voice interface on the Cisco MC3810 directly to the PSTN. Instead, it should be connected to a PBX that implements a security scheme that prevents unauthorized use.
The same opportunity for illicit use does not exist for non-switched call types such as pass-through connections (although the possibility for fraud does exist at the direct contact point). Pass-through calls create a path to only a single location specified by the network administrator. For example, a pass-through connection might be used to pass a trunk from a PBX to the PSTN. In this case, the trunk on the PBX will always pass straight through the Cisco MC3810 to the PSTN. As a result, the necessary security is provided by the PBX.
This section describes possibly unexpected behavior by Cisco IOS Release 12.0(1a)T1. This section describes only severity 1 and 3 caveats.
Slow switching fails in the inbound direction on Ethernet 0 to atm0 for Appletalk pings, where ethernet0 is configured for no appletalk route-cache and atm0 is configured for appletalk route-cache.
When E1 0 is configured for ATM, the bandwidth is set to 1920 Kb but when the command default bandwidth is entered for interface ATM0, the bandwidth is changed to 1544 KB, which is correct for T1 but not for E1.
If a PVC is created while ATM0 is shut down and then a no shutdown command is performed on ATM0, the PVC becomes active but does not increment the current VCC count. If the PVC is then deleted, the current VCC count goes to 4294967295 and an SNMP browser query on number-of-VCCs receives a value of -1.
When loading an image from a TFTP server via the copy tftp flash command, if the line quality is bad and the copy encounters timeouts during transfers, the display might not indicate that the load had not transferred all data and the image is corrupt.
Fast switching does not work properly on s0 and s0:0 interfaces for the Enterprise protocols: Decnet, CLNS, Vines, XNS, AT2-Phy, AT2-AT1.
The state of s0:0 or atm0 interface is not reflected correctly after the interface goes down from a failure at the remote end or from a shutdown command. The CiscoView state indication does reflect UP and DOWN conditions correctly.
Use of an invalid interface in a command such as:
connect sw 0 dlci 200 s0:0 conn 150
will be accepted at the command line instead of rejected. This is not a valid combination, however, and will not work.
If a clock rate is configured for interface serial 0 and the running configuration is copied to the startup configuration, then the Cisco MC3810 is reloaded. When it comes up the, the clock rate is not applied to interface serial 0.
The workaround is to manually configure the interface again, or the startup configuration must be copied again to the running configuration.
Configuring bsc primary on serial1 causes an error message to be displayed:
A debug message might be displayed under certain circumstances:
Normal operation is not affected.
The Lex option is listed under help on a config interface command but is not currently supported and causes a syntax error when entered.
The valid range for mtu on interface serial1 when configured for clear-channel is different based on the current setting of the MTU. The range shown is 64 to a maximum of (18000 + configured-value - 1500). The actual range is 64 to 18000.
When an interface is set for encap clear-channel with an mtu setting, and the interface is then reconfigured to no encap, the previous setting for mtu is retained instead of being set to the default.
A show isdn status can give incorrect information if the controller is not receiving frames with correct clocking or other configuration. The controller should be configured completely and checked for valid operation before proceeding to configure layer 2 or layer 3 functions.
If a serial interface configured for pri-group operation is configured for isdn switch operation before configuring the isdn calling number, an SNMP browser will receive error when querying for the value of the isdn-physical-address.
Debug messages are displayed on an ISDN BRI0 interface when the cable is removed. Operation is not affected.
When an SNMP set to ifLinkUpDownTrapEnable with value "disabled" is received by the system for an analog voice port, the impedance of the voice port is also changed to UNKNOWN.
CiscoView will display N/A for an interface that has been configured for E1 then reconfigured to atm0 or vice-versa. The workaround is to advance to the next index to see the new data.
When a shutdown followed by a no shutdown is performed on S0 at the remote end, the syslog message LINK-UPDOWN indicating the link has come up is missing, only the LINEPROTO-UPDOWN message is logged.
Since some customers configure their network management stations to only display higher syslog severity messages, no indication of the interface state change might appear since the severity of the LINEPROTO-UPDOWN message is low (for example, severity 5 as opposed to the higher severity 3 of the LINK-UPDOWN message which would likely be displayed if it was generated.)
An SNMP browser can receive data for a non-existent controller (T1 1 or E1 1) on Cisco MC3810 concentrators equipped with an AVM when querying the system.
An SNMP browser query on FXO signal-type returns fxoLoopStart for voice ports of type EXT-SIGN-SLAVE. A query on FXS signal-type returns fxsLoopStart for voice ports of type EXT-SIGN-MASTER.
After a PRI group is configured, the resulting voice ports are of type FXO-NULL. A query on FXO signal-type returns fxoLoopStart for the voice port.
Ciscoview does not display Configuration Status and Configuration History categories and associated data in the configuration device window that appears when the user double-clicks on the representation of the chassis.
A shutdown on an interface dialer is invalid from the CLI but is accepted from an SNMP browser.
Voice ports remain configured after the voice-groups are deleted.
The num-exp command does not operate correctly in configurations using either PLAR or TIE features on voice ports. Use of number-expansion in these cases might result in a crash due to memory allocation failure.
If a trunk interface is configured for ppp, the line protocol will come up but the NCP will not open up. The workaround is to shutdown and then no shutdown the interface.
There is a limit of 5 sessions supported for X.25 when tunneling PPP over an X.25 connection.
If interface s0:0 is first configured for X25, or any other encapsulation and then the encapsulation is changed to bstun, a message is displayed indicating bstun is not allowed on the interface.
However, the encapsulation is then changed to no encapsulation in show run. Checking show interface s0:0 the correct encapsulation (for example, X25) is indicated. The interface also goes down after this action, and it is necessary to reconfigure the original encapsulation then do a shutdown and no shutdown on s0:0 to get it to come up again.
All the caveats listed in this section are resolved in Release 12.0(1)XA for the Cisco MC3810. This section describes only severity 1, 2 and 3 caveats.
When a channel-group is deleted from the T1 0 controller, the associated sub-interface Serial 0:x is also deleted but it is not automatically shutdown. This can cause incorrect behavior of many types, including 100% CPU utilization under apparently light load, system crash and forced crashes and others.
You should always shut down an interface before deleting it from a configuration.
Due to a production problem, many source-route bridging commands were omitted from the printed version of the Cisco IOS Software Command Summary (78-4746-xx, DOC-CIOSCS11.3=). For complete documentation of all source-route bridging commands, refer to the Bridging and IBM Networking Command Reference (78-4743-xx). You can also obtain the most current documentation on the Documentation CD-ROM or Cisco Connection Online (CCO).
The following sections describe the documentation available for the Cisco MC3810 multiservice access concentrator. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules. Feature modules are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents. Feature modules are available online only.
The most up-to-date documentation can be found on the Web via Cisco Connection Online (CCO) and on the latest Documentation CD-ROM. These electronic documents might contain updates and modifications made after the paper documents were printed. For information on CCO, refer to the "Cisco Connection Online" section. For more information on the CD-ROM, refer to the "Documentation CD-ROM" section
This section contains the following subsections:
To access the cross-platform Release Notes for Cisco IOS Release 12.0T on CCO, follow this path: Software and Support: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release
To access the cross-platform Release Notes for Cisco IOS Release 12.0 T on the Documentation CD-ROM, follow this path: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Cross-Platform Release Notes for Cisco IOS Release 12.0 T
To access these documents, refer to the Software Center at this path on CCO: Software & Support: Software Center: Cisco IOS Software
As a supplement to the caveats listed in the "Caveats" section in these release notes, see the Caveats for Cisco IOS Release12.0 T document, which contains caveats applicable to all platforms for all maintenance releases of Release 12.0 T.
To access the caveat document on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Caveats: Caveats for Cisco IOS Release 12.0 T
To access the caveat document on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS 12.0: Caveats: Caveats for Cisco IOS Release 12.0 T
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. Bug Navigator II can be found at http://www.cisco.com/support/bugtools, or from CCO, select Software & Support: Tools: Bug Toolkit II.
The following Cisco MC3810 multiservice access concentrator documents are available:
To access platform documents on CCO, follow this path:
Products and Ordering: Cisco Documentation: Access Servers and Access Routers: Multiservice Access Concentrators
To access platform documents on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Access Servers and Access Routers: Multiservice Access Concentrators
Feature modules describe new features supported by Release 12.0, and are an update to the Cisco IOS documentation set. As updates, the feature modules are available online only. The feature module information is included in the next printing of the Cisco IOS documentation set. Each feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference.
To access the feature modules on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS 12.0(1) New Features
To access the feature modules on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS 12.0(1) New Features
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents. These documents are shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Each configuration guide can be used in conjunction with its corresponding command reference.
To access these documents on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS Release 12.0 Configuration Guides and Command References
To access these documents on the Documentation CD-ROM, follow this path:
Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS Release 12.0 Configuration Guides and Command References
Table 6 details the contents of the Cisco IOS Release 12.0 software documentation set. The document set is available in electronic form, and also in printed form upon request.
Note The most current Cisco IOS documentation can be found on the latest Documentation CD-ROM and on the Web. These electronic documents might contain updates and modifications made after the paper documents were printed.
To access the Cisco IOS documentation set on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0
To access the Cisco IOS documentation set on the Documentation CD-ROM, follow this path:
Cisco IOS Software Configuration: Cisco IOS Release 12.0
Note The Cisco Management Information Base (MIB) User Quick Reference publication is no longer being published. For the latest list of MIBs supported by Cisco, see the Cisco Network Management Toolkit on Cisco Connection Online. On CCO, use the following path: Software and Support: Software Center: Network Management Products: Cisco Network Management Toolkit: Cisco MIBs.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.
For service and support for a product purchased directly from Cisco, use CCO.
For helpful tips on configuring Cisco products, follow this path on CCO:
Software & Support: Technical Tips (button on left margin)
Hot Tips are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 415-596-4408.
The following sections are provided from the Technical Tips page:
For information on upgrading to a new software release, refer to the Cisco IOS Software Release Upgrade Paths and Packaging Simplification product bulletin #703 located on CCO. On CCO, follow this path: Products and Ordering: More Information: Product Bulletins. Scroll to Software. Under Cisco IOS 12.0, click the Upgrade Paths bulletin.
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.
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 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 Jan 17 16:46:22 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
