|
|
July 24, 2000
 |
Note See Important Notes for information concerning Cisco IOS Release 12.1 (3) T and Cisco IOS Release 12.1(3a) T. |
|
Note You can find the most current Cisco IOS documentation on Cisco Connection Online (CCO). These electronic documents may contain updates and modifications made after the hardcopy documents were printed. |
These release notes for the Cisco 2600 series describe the enhancements provided in Cisco IOS Release 12.1(3a) T1. These release notes are updated as needed.
For a list of the software caveats that apply to Release 12.1(3) T, see Caveats for Cisco IOS Release 12.1T that accompanies these release notes. This caveats document is updated for every maintenance release and is also located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release located on CCO and the Documentation CD-ROM.
These release notes describe the following topics:
Cisco Systems extends enterprise-class and managed services Customer Premises Equipment (CPE) versatility, integration, and power to branch offices with the Cisco 2600 series modular access router family. The widely deployed Cisco 2600 series modular access routers are designed to enable customers to easily adopt future technologies and scale to accommodate network expansion. The Cisco 2600 series shares modular interfaces with the Cisco 1600, Cisco 1700, and Cisco 3600 series, providing a solution to meet today's branch office needs for applications such as:
The Cisco 2600 series modular architecture provides the versatility needed to adapt to changes in network technology as new services and applications become available. Driven by a powerful RISC processor, the Cisco 2600 series supports the advanced Quality of Service (QoS), security, and network integration features required in today's evolving enterprise networks.
For information on new features and Cisco IOS commands supported by Cisco IOS Release 12.1(3) T, see "New and Changed Information" section and "Related Documentation" section.
This section describes the system requirements for Release 12.1(3) T:
| Platforms | Image Name | Software Image | Flash Memory Recommended | DRAM Memory Recommended | Runs From |
|---|---|---|---|---|---|
Cisco 2600 | IP | c2600-i-mz | 8 MB | 24 MB | RAM |
IP Plus | c2600-is-mz | 16 MB | 40 MB | RAM | |
IP Plus IPSec 3DES | c2600-ik2s-mz | 16 MB | 40 MB | RAM | |
IP/FW/IDS Plus IPSec 3DES | c2600-ik2o3s-mz | 16 MB | 48 MB | RAM | |
IP Plus IPSec 56 | c2600-is56i-mz | 16 MB | 40 MB | RAM | |
IP/FW/IDS | c2600-io3-mz | 8 MB | 32 MB | RAM | |
IP/FW/IDS Plus IPSec 56 | c2600-io3s56i-mz | 16 MB | 48 MB | RAM | |
IP/H323 | c2600-ix-mz | 8 MB | 32 MB | RAM | |
IP/IPX/AT/DEC | c2600-d-mz | 8 MB | 32 MB | RAM | |
IP/IPX/AT/DEC Plus | c2600-ds-mz | 16 MB | 40 MB | RAM | |
IP/IPX/AT/DEC/FW/IDS Plus | c2600-do3s-mz | 16 MB | 48 MB | RAM | |
Enterprise Plus | c2600-js-mz | 16 MB | 48 MB | RAM | |
Enterprise Plus IPSec 3DES | c2600-jk2s-mz | 16 MB | 48 MB | RAM | |
Enterprise Plus IPSec 56 | c2600-js56i-mz | 16 MB | 48 MB | RAM | |
Enterprise/SNASw Plus | c2600-a3js-mz | 16 MB | 48 MB | RAM | |
Enterprise/SNASw Plus IPSec 3DES | c2600-a3jk2s-mz | 16 MB | 48 MB | RAM | |
Enterprise/SNASw Plus IPsec 56 | c2600-a3js56i-mz | 16 MB | 48 MB | RAM | |
Enterprise/FW/IDS Plus IPSec 3DES | c2600-jk2o3s-mz | 16 MB | 48 MB | RAM | |
Enterprise/FW/IDS Plus IPSec 56 | c2600-jo3s56i-mz | 16 MB | 48 MB | RAM | |
Remote Access Server | c2600-c-mz | 8 MB | 24 MB | RAM |
Cisco IOS Release 12.1(3) T supports the Cisco 2600 series routers:
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
| Interface, Network Module, or Data Rate1 | Platforms Supported | |
|---|---|---|
| LAN Interfaces2 | 1- or 2-port Ethernet (10BaseT) | All Cisco 2600 series platforms |
1-port Token Ring (RJ-45) | Cisco 2612, Cisco 2613 | |
1- or 2-port 10/100 Mbps Ethernet | Cisco 2620, Cisco 2621 | |
| LAN Network Modules | 1-port Ethernet | All Cisco 2600 series platforms |
4-port Ethernet | All Cisco 2600 series platforms | |
1-port ATM-25 RJ-45 interface | All Cisco 2600 series platforms | |
| Serial Network Modules | 16- or 32-port asynchronous/synchronous serial low speed (128 kbps max) | All Cisco 2600 series platforms |
4- or 8-port asynchronous/ synchronous serial low speed | All Cisco 2600 series platforms | |
| Multiport T1/E1 ATM Network Modules with Inverse Multiplexing over ATM (IMA)3 | 4-port T1 ATM network module with IMA (NM-4T1-IMA) | All Cisco 2600 series platforms |
4-port E1 ATM network module with IMA (NM-4E1-IMA) | All Cisco 2600 series platforms | |
8-port T1 ATM network module with IMA (NM-8T1-IMA) | All Cisco 2600 series platforms | |
8-port E1 ATM network module with IMA (NM-8E1-IMA) | All Cisco 2600 series platforms | |
| ATM Network Modules3 | 1-port ATM T3 network module (NM-1A-T3) | All Cisco 2600 series platforms |
1-port ATM E3 network module (NM-1A-E3) | All Cisco 2600 series platforms | |
| Digital T1 Packet Voice Trunk Network Modules and Spare Components | 1-port, 24-channel T1 voice/fax module, supports 24 channels of medium-complexity codecs: G.729a/b, G.726, G.711 and fax or 12 channels of G.726, G.729, G.723.1, G.728, G.729a/b, G.711, and fax. Consists of one NM-HDV, two PVDM-12s, and one VWIC-1MFT-T14. Part number: NM-HDV-1T1-24 | All Cisco 2600 series platforms |
1-port, enhanced 24-channel T1 voice/fax module, supports 24 channels of high- and medium-complexity codecs: G.729a/b, G.726, G.729, G.728, G.723.1, G.711, and fax. Consists of one NM-HDV, four PVDM-12s, and one VWIC-1MFT-T14. Part number: NM-HDV-1T1-24E | All Cisco 2600 series platforms | |
2-port, 48-channel T1 voice/fax module, supports add/drop multiplexing (drop and insert); 48 channels of medium-complexity codecs: G.729a/b, G.726,G.711, and fax; or 24 channels of G726, G729, G723.1, G.728, G729a/b, G711, and fax. Consists of one NM-HDV, four PVDM-12, and one VWIC-2MFT-T1-DI4. Part number: NM-HDV-2T1-48 | All Cisco 2600 series platforms | |
High-density voice/fax network module spare (NM-HDV) | Digital T1/E1 packet voice trunk network modules spare component | |
12-channel packet voice DSP module upgrade spare (PVDM-12) | Digital T1/E1 packet voice trunk network modules spare component | |
1-port RJ-48 multiflex trunk - T1 (VWIC-1MFT-T1)4 | Digital T1/E1 packet voice trunk network modules spare component | |
2-port RJ-48 multiflex trunk - T1 (VWIC-2MFT-T1)4 | Digital T1/E1 packet voice trunk network modules spare component | |
2-port RJ-48 multiflex trunk with drop and insert - T1 (VWIC-2MFT-T1-DI)4 | Digital T1/E1 packet voice trunk network modules spare component | |
| Digital E1 Packet Voice Network Modules | 1-port 30 Channel E1 High-Density Voice Network Module (NM-HDV-1E1-30) | All Cisco 2600 series platforms |
1-port Enhanced 30 Channel E1 High-Density Voice Network Module (NM-HDV-1E130E) | All Cisco 2600 series platforms | |
2-port 60 Channel High-Density Voice Network Module (NM-HDV-2E1-60) | All Cisco 2600 series platforms | |
| Dial, ISDN and Channelized Serial Network Modules | 1- or 2-port channelized T1/ISDN PRI | All Cisco 2600 series platforms |
1- or 2-port channelized T1/ISDN PRI with CSU | All Cisco 2600 series platforms | |
1- or 2-port channelized E1/ISDN PRI balanced | All Cisco 2600 series platforms | |
1- or 2-port channelized E1/ISDN PRI unbalanced | All Cisco 2600 series platforms | |
4-or 8-port ISDN BRI S/T interface | All Cisco 2600 series platforms | |
4- or 8-port ISDN BRI U (NT1) interface | All Cisco 2600 series platforms | |
8- or 16-port analog modems | All Cisco 2600 series platforms | |
| T1/E1 Multiflex Voice/WAN Interface Cards5 | 1-port T1 multiflex trunk interface (VWIC-1MFT-T1) | All Cisco 2600 series platforms |
1-port E1 multiflex trunk interface (VWIC-1MFT-E1) | All Cisco 2600 series platforms | |
2-port T1 multiflex trunk interface (VWIC-2MFT-T1) | All Cisco 2600 series platforms | |
2-port E1 multiflex trunk interface (VWIC-2MFT-E1) | All Cisco 2600 series platforms | |
2-port T1 multiflex trunk interface with Drop and Insert (VWIC-2MFT-T1-DI) | All Cisco 2600 series platforms | |
2-port E1 multiflex trunk interface with Drop and Insert (VWIC-2MFT-E1-DI) | All Cisco 2600 series platforms | |
| Voice/Fax Interface Cards | 1- or 2- voice interface card slots | All Cisco 2600 series platforms |
1-slot high-density T1/E1 voice interface card slots6 | All Cisco 2600 series platforms | |
2-port FXS voice/fax interface card7 | All Cisco 2600 series platforms with voice/fax network modules | |
2-port E&M voice/fax interface card3 | All Cisco 2600 series platforms with voice/fax network modules | |
2-port FXO voice/fax interface card3 | All Cisco 2600 series platforms voice/fax network modules | |
| WAN Interface Cards | 1-port ISDN BRI S/T interface (requires external NT1) | All Cisco 2600 series platforms |
1-port ISDN BRI (NT1) U | All Cisco 2600 series platforms | |
1-port 56/64-kbps DSU/CSU | All Cisco 2600 series platforms | |
1-port T1/Fractional T1 with DSU/CSU | All Cisco 2600 series platforms | |
1-port high-speed serial (up to 2.048 Mbps) | All Cisco 2600 series platforms | |
2-port dual high-speed serial (up to 2.048 Mbps; asynchronous/ synchronous support) | All Cisco 2600 series platforms | |
2-port asynchronous/ synchronous (up to 128 kbps) | All Cisco 2600 series platforms | |
| Advanced Integration Module | Data compression AIM (up to 8.192 Mbps) | All Cisco 2600 series platforms |
| 1The voice/fax and ATM-25 network modules require Cisco IOS Plus feature sets. 2The 1- or 2-port 10/100 Ethernet LAN interface for the Cisco 2621 and Cisco 2621 series routers is only available in Cisco IOS Release 12.0 XC and later. 3Requires the Cisco IOS Plus feature sets. 4See T1/E1 multiflex voice/WAN interface cards in this table. 5T1 multiflex voice/WAN interface cards can be used in a chassis slot or installed in a digital T1 packet voice trunk module. E1 multiflex voice/WAN interface cards can be installed in a chassis slot. 6Uses the VWIC-MFT T1/E1 interface cards. 7Requires the NM-1V or NM-2V network module. |
To determine the version of Cisco IOS software running on a Cisco 2600 series router, log in to the router and enter the show version EXEC command:
router> show version Cisco Internetwork Operating System Software IOS (tm) 2600 Software (c2600-i-mz), Version 12.1(3) T, RELEASE SOFTWARE
For general information about upgrading to a new software release, see Upgrading the Cisco IOS Software Release in Cisco Routers and Modems located at:
http://www.cisco.com/warp/public/620/6.html
The latest version of analog modem firmware for the Cisco 2600 series supports the internal analog modems (both NM-16AM and NM-8AM) in a wide range of countries, starting with Cisco IOS Release 11.3(5)T and later releases. The latest firmware (version 1.2.0) also supports dial-out and fax-out.
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers: Analog Modem Firmware
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers: Analog Modem Firmware
Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Cisco IOS Release 12.1(3) T supports the same feature sets as Cisco IOS Release 12.1, but Cisco IOS Release 12.1(3) T can include new features supported by the Cisco 2600 series.
| Feature Sets | Feature Set Matrix Term | Software Image | Platforms | |
|---|---|---|---|---|
| IP Standard Feature Sets | IP |
| c2600-i-mz | All Cisco 2600 series platforms |
IP Plus |
| c2600-is-mz | All Cisco 2600 series platforms | |
IP Plus IPSec 3DES |
| c2600-ik2s-mz | All Cisco 2600 series platforms | |
IP Plus IPSec 56 |
| c2600-is56i-mz | All Cisco 2600 series platforms | |
IP/FW/IDS |
| c2600-io3-mz | All Cisco 2600 series platforms | |
IP/FW/IDS Plus IPSec 3DES |
| c2600-ik2o3s-mz | All Cisco 2600 series platforms | |
IP/FW/IDS Plus IPSec 56 |
| c2600-io3s56i-mz | All Cisco 2600 series platforms | |
IP H.323 |
| c2600-ix-mz | All Cisco 2600 series platforms | |
| IP/IPX/AppleTalk/ DEC Standard Feature Sets | IP/IPX/AT/DEC |
| c2600-d-mz | All Cisco 2600 series platforms |
IP/IPX/AT/DEC Plus |
| c2600-ds-mz | All Cisco 2600 series platforms | |
IP/IPX/AT/DEC/ FW/IDS Plus |
| c2600-do3s-mz | All Cisco 2600 series platforms | |
| Enterprise Standard Feature Sets | Enterprise Plus |
| c2600-js-mz | All Cisco 2600 series platforms |
Enterprise Plus IPSec 3DES |
| c2600-jk2s-mz | All Cisco 2600 series platforms | |
Enterprise Plus IPSec 56 |
| c2600-js56i-mz | All Cisco 2600 series platforms | |
Enterprise/FW/IDS Plus IPSec 56 |
| c2600-jo3s56i-mz | All Cisco 2600 series platforms | |
Enterprise/FW/IDS Plus IPSec 3DES |
| c2600-jk2o3s-mz | All Cisco 2600 series platforms | |
| Enterprise/SNASw Standard Feature Sets | Enterprise/SNASw Plus |
| c2600-a3js-mz | All Cisco 2600 series platforms |
Enterprise/SNASw Plus IPSec 3DES |
| c2600-a3jk2s-mz | All Cisco 2600 series platforms | |
Enterprise/SNASw Plus IPSec 56 |
| c2600-a3js56i-mz | All Cisco 2600 series platforms | |
| Remote Access Server Feature Set | Remote Access Server |
| c2600-c-mz | All Cisco 2600 series platforms |
 |
Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, you must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com. |
Tables 4 and 5 list the features and feature sets supported by the Cisco 2600 series in Cisco IOS Release 12.1(3a) T1 and use the following conventions:
|
Note These feature set tables only contain a selected list of features. The tables are not cumulative—nor do they list all the features in each image. |
| Features | Feature Sets | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| In | IP | IP/ FW/ IDS | IP/ FW/IDS Plus IPSec 56 | IP H323 | IP/ IPX/ AT/ DEC | IP Plus | IP Plus IPSec 3DES | IP Plus IPSec 56 | IP/ FW/IDS Plus IPSec 3DES | IP/ IPX/ AT/ DEC Plus | IP/ IPX/ AT/ DEC/ FW/ IDS Plus | |
| New Features | ||||||||||||
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | No | No | No | No | No | No | No | No | No |
| (3) | No | No | No | No | No | No | No | No | No | No | No |
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No |
| Connectivity | ||||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| IBM Support | ||||||||||||
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No | No | No | No | No |
| IP/IPX Routing | ||||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | No | No | No | No | No | No | No | No | No | No | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | Yes | No | No | No | No | Yes | Yes |
|
| No | No | No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Management | ||||||||||||
|
| No | No | Yes | No | No | No | No | Yes | Yes | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Multimedia and Quality of Service | ||||||||||||
| (1) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | No | Yes | No | No | No | No | No | No | No |
| (1) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | Yes | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | Yes | No | No | No | No | No | No | No |
|
| No | No | No | Yes | No | No | No | No | No | No | No |
|
| No | No | No | Yes | No | No | No | No | No | No | No |
|
| No | No | No | Yes | No | No | No | No | No | No | No |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| Security | ||||||||||||
| (1) | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No |
| (1) | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No |
| (1) | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | Yes | Yes | Yes | No | No |
|
| No | Yes | Yes | No | No | No | No | No | Yes | No | Yes |
|
| No | Yes | Yes | No | No | No | No | No | Yes | No | Yes |
|
| No | Yes | Yes | No | No | No | No | No | Yes | No | Yes |
| Switching | ||||||||||||
|
| No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Voice | ||||||||||||
| (1) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN Optimization | ||||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN Services | ||||||||||||
| (1) | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No |
| (1) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | Yes | No | No | No | No | Yes | Yes |
|
| No | No | No | No | Yes | No | No | No | No | Yes | Yes |
|
| No | No | No | No | Yes | No | No | No | No | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | No | No | No | No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1Cisco 2620 and 2621 only |
| Features | Feature Sets | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| In | Enter- prise Plus | Enter- prise Plus IPSec 3DES | Enter- prise Plus IPSec 56 | Enter- prise/ SNASw Plus | Enter- prise/ SNASw Plus IPSec 3DES | Enter- prise/ SNASw Plus IPSec 56 | Enter- prise/ FW/IDS Plus IPSec 3DES | Enter- prise/ FW/IDS Plus IPSec 56 | Remote Access Server | |
| New Features | ||||||||||
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No |
| Connectivity | ||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| IBM Support | ||||||||||
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | No | No | Yes | Yes | Yes | No | No | No |
| IP/IPX Routing | ||||||||||
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Management | ||||||||||
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Multimedia and Quality of Service | ||||||||||
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | No | No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| Security | ||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (1) | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No |
| (1) | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No |
| (1) | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | Yes | No | No | Yes | No | Yes | No | No |
|
| No | No | No | Yes | Yes | No | No | No | No |
|
| No | No | No | No | No | No | Yes | Yes | No |
|
| No | No | No | No | No | No | Yes | Yes | No |
| Switching | ||||||||||
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| Voice | ||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| WAN Optimization | ||||||||||
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN Services | ||||||||||
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
|
| No | No | No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1Cisco 2620 and 2621 only |
The following sections list the new hardware and software features supported by the Cisco 2600 series for Release 12.1(3a) T1. These features are broken down by feature in Tables 4, 5, 6, and 7.
The following new hardware features are supported by the Cisco 2600 series for Cisco IOS Release 12.1(3a) T1.
The Cisco 2650 and 2651 series routers are performance enhanced versions of the Cisco 2620 and 2621 modular routers. Increased performance is achieved through the utilization of a faster platform processor and faster system memory. Additionally, SDRAM replaces EDO DRAM and flash memory is increased. All current hardware and software features supported on the Cisco 262x platform will be supported on the Cisco 2650 and 2651 routers.
The new performance features are:
The following new fixed LAN configurations are available:
Two fixed ports, 10/100 Mbps Fast Ethernet (2FE2W1NM)
The following new hardware features are supported by the Cisco 2600 series for Cisco IOS Release 12.1(2) T.
Digital E1 packet voice trunk network modules for Cisco 2600 and 3600 series routers allow enterprises or service providers, using the equipped routers as customer premises equipment, to deploy digital voice and fax relay. These modules receive constant bit-rate telephony information over E1 interfaces and can convert that information to a compressed format, so that it can be transmitted as Voice over IP (VoIP), Voice over Frame Relay (VoFR), and Voice over ATM (VoATM).
Cisco IOS software configuration allows you to set up a variety of applications. Here are a few examples:
The following network modules are available:
Restrictions
The following restrictions apply to digital E1 packet voice trunk network module configuration:
Two new ATM network modules are supported on the Cisco 2600 Series and Cisco 3600 Series routers in this release. These network modules support ATM Adaptation Layer 5 (AAL5) and will provide North American 44.736 Mbps ATM T3 services, and European 34.368 Mbps E3 services.
These network modules provide DS3 and E3 ATM connectivity for the Cisco 2600 and 3600 Series routers. These network modules can be used to provide connectivity with campus networks and LAN switches, and long-haul WAN applications. These network modules include support for ATM LANE, RFC1577, RFC1483, TAG switching, and PPP over ATM with full support for both client and server functions. The modules support up to 1,024 simultaneous virtual circuits (VCs) and provide extensive traffic shaping and rate queueing capabilities on a per- VC basis. Use of these modules requires using one of the Cisco IOS Plus feature sets.
The following modules are available:
The following new software features are supported by the Cisco 2600 series for Cisco IOS Release 12.1(3a) T1.
This feature extends the functionality available with low latency queueing (LLQ). This feature allows customers to specify the Committed Burst (Bc) size in low latency queueing and, therefore, configures the network to accommodate temporary bursts of traffic.
The Source Specific Multicast (SSM) feature is an extension of IP multicast, where datagram traffic is forwarded to receivers from only those multicast sources to which the receivers have explicitly joined. When SSM is used, only source-specific multicast distribution trees (no shared trees) are created.
Source specific multicast (SSM) is a datagram delivery model that best supports one-to-many applications, also known as broadcast applications. SSM is the core networking technology for the Cisco implementation of the IP Multicast lite suite of solutions targeted for audio and video broadcast application environments.
This feature module introduces the following Cisco IOS components that support SSM:
Trunk Conditioning for FRF.11 and Cisco Trunks is an enhancement that adds the following capabilities to the trunk conditioning feature on the Cisco 2600 and 3600 series routers and Cisco MC3810 series concentrators:
This feature applies to analog telephony connections and digital T1/E1 using CAS/robbed-bit "ABCD" signaling. It does not apply to digital T1/E1 connections using CCS type signaling.
PSTN Fallback provides a mechanism to monitor congestion in the IP network and either redirect calls to the Public Switched Telephone Network (PSTN) or reject calls based on the network congestion. PSTN Fallback does not provide assurances that a call which proceeds over the IP network is protected from the effects of congestion. This is the function of the other QoS mechanisms such as IP RTP Priority or LLQ.
Caller ID (sometimes called CLID or ICLID for incoming call line identification) is an analog service offered by a Central Office (CO), which supplies calling party information to subscribers. Typically, the calling party number, and sometimes the name, appears on a station (also called extension) device such as a PC telephony software application screen or the display on a telephone. Type 1 Caller ID provides the calling party information while the call is ringing, and Type 2 Caller ID provides the additional convenience of calling number display while the recipient is on another call. In this release, Cisco provides only Type 1 Caller ID support.
RSVP Support for LLQ (low latency queueing) is a network-control protocol that provides a means for reserving network resources—primarily bandwidth—to guarantee that applications transmitting end-to-end across networks achieve the desired quality of service (QoS).
RSVP enables real-time traffic (which includes voice flows) to reserve resources necessary for low latency and bandwidth guarantees. RSVP uses weighted fair queuing (WFQ) to provide fairness among flows and to assign a low weight to a packet to attain priority. However, the preferential treatment provided by RSVP is insufficient to minimize the jitter because of the nature of the queuing algorithm itself. As a result, the low latency and jitter requirements of voice flows might not be met in the prior implementation of RSVP and WFQ.
Consequently, a new queuing implementation, referred to as LLQ, was put in place. However, this new queuing implementation, by itself, is not sufficient to provide QoS for VoIP calls. Since the priority queue (PQ) in the queuing system does not distinguish between a VoIP packet of an existing call and a new call (as the queue does not keep the flow state), the queue may drop the packet of the existing call and service the packet of the new call due to strict policing. This means that RSVP is needed to perform admission control to avoid oversubscription of the priority queues.
Secure Shell (SSH) is a protocol that provides a secure remote connection to another router. There are currently two versions of SSH available, SSH Version 1 and SSH Version 2. Only SSH Version 1 is implemented in Cisco IOS software.
The Secure Shell Version 1 Integrated Client feature is an application running over TCP/IP to provide strong authentication and encryption. The SSH client enables a Cisco router to make a secure, encrypted connection to another Cisco router or device running an SSH Version 1 server. This connection provides functionality that is similar to that of an outbound Telnet connection except that the connection is encrypted. With authentication and encryption, the SSH client allows for a secure communication over an insecure network. The SSH client in Cisco IOS software works with publicly and commercially available SSH servers.
The Frame Relay ELMI Address Registration feature enables a network management system (NMS) to detect connectivity among the switches and routers in a network using the Enhanced Local Management Interface (ELMI) protocol. During ELMI version negotiation, neighboring devices exchange their management IP addresses and ifIndex. The NMS polls the devices to collect this connectivity information.
Before this feature was introduced, NMS could detect only the topology of routers or the topology of switches. This new feature enables the NMS to detect switch and router interconnection and create an end-to-end network topology map for network administrators.
The Cisco Frame Relay MIB has been enhanced to support the new ELMI information. The NMS uses the MIB to extract the IP address and ifIndex of devices neighboring the managed device.
This feature supports integrated routing and bridging, transparent bridging, and PVST+ between vLANs (virtual LANs) with IEEE 802.1Q encapsulation features. It provides the ability to connect a network of hosts over a simple bridging-access device to a remote access concentrator. This feature supports the following IEEE 802.1Q (Dot1q) functionality:
Enhancements to the Session Initiation Protocol (SIP) for VoIP on Cisco Access Platforms enhancements include:
Codec | SDP |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
The T1/E1 Alarm Conditioning for Switched Calls and Permanent Connection Trunks feature provides status monitoring on T1/E1 PBX voice interfaces for permanent trunk connections created using the Cisco connection trunk command (private lines and tie-lines) and for switched calls. The feature supports operation with channel associated signaling (CAS) only; it does not support common channel signaling (CCS).
If the FXO Supervisory Disconnect Tone feature is configured and a detectable tone from the PSTN or PBX is detected by the digital signal processor (DSP), the analog FXO port goes on-hook. This feature prevents an analog FXO port from remaining in an off-hook state after an incoming call is ended. You can configure a voice port to detect either of the following tone types:
As part of the tone detection process by the DSP, a DSP event is reported to the host software.
Detection of any tone is effective only during call set-up (before a call is answered), and echo cancellation must be enabled to prevent disconnection due to detection of the router's own ringback tone.
This feature enables ICMP (Internet Control Message Protocol) redirection on interfaces configured with the Hot Standby Router Protocol (HSRP). HSRP provides network redundancy in a way that ensures that user traffic will immediately and transparently recover from "first hop" failures in network edge devices. By sharing an IP address and a MAC (layer 2) address, two or more routers can act as a single "virtual router" to the hosts on a LAN. The HSRP group may consist of an active router, a standby router to replace the active router should it fail, and one or more listening routers. The active and standby routers periodically exchange status messages in order to detect when a router goes down. The address of this HSRP group is referred to as the "virtual ip address."
Media Gateway Control Protocol Residential Gateway Support is a merge of two protocol sets: SGCP 1.1 and MGCP 0.1. The protocols describe the types of calls a network gateway can accept and what it does with the calls it receives. The merged set enables a single gateway to receive commands from either protocol.
As in the earlier implementations of the two protocols, a gateway handles the translation between audio signals and the packet network and interacts with a Call Agent, or Media Gateway Controller, which performs signal and call processing on the gateway's calls. This feature supports two types of gateway configurations:
Adds MGCP support to IOS gateway to provide Supplementary Services with CallManager.
Multiprotocol label switching (MPLS) on Cisco Routers combines the performance and capabilities of Layer 2 (data link layer) switching with the proven scalability of Layer 3 (network layer) routing. MPLS enables service providers to meet the challenges of explosive growth in network utilization while providing the opportunity to differentiate services without sacrificing the existing network infrastructure. The MPLS architecture is flexible and can be employed in any combination of Layer 2 technologies. MPLS support is offered for all Layer 3 protocols, and scaling is possible well beyond that typically offered in today's networks.
MPLS efficiently enables the delivery of IP services over an ATM switched network. MPLS supports the creation of different routes between a source and a destination on a purely router-based Internet backbone. By incorporating MPLS into their network architecture, service providers can save money, increase revenue and productivity, provide differentiated services, and gain competitive advantages.
This enhancement provides sparse table support for fastethernet subinterfaces similar to what is currently provided for frame-relay subinterfaces.
The CEF Support for IP Routing between IEEE 802.1Q vLANs feature provides the support needed for a CEF feature module.
The Individual SNMP Trap Support feature adds the ability to enable or disable SNMP system management notifications (traps) individually. SNMP traps that can be specified are "authentication", "linkup", "linkdown", and "coldstart". This feature expands the functionality of the "snmp-server enable traps snmp" command.
Transparent Common Channel Signalling (T-CCS) allows the connection of two PBXs with digital interfaces that use a proprietary or unsupported CCS protocol without the need for interpretation of CCS signaling for call processing. T1/E1 traffic is transported transparently through the data network and the feature preserves proprietary signaling. From the PBX standpoint, this is accomplished through a point-to-point connection. Calls from the PBXs are not routed, but follow a preconfigured route to the destination.
Cisco Hoot and Holler Conferencing over IP is powered using Cisco's VoIP technology, Cisco's IP multicast and Cisco's new DSP audio mixing. This solution provides the ability to transport Hoot and Holler traffic over Cisco equipment. Traditional Hoot and Holler networks are a point-to-multipoint voice applications and are commonly used by brokerage and trading firms to advise brokers and traders on market movements. Brokerage and trading firms can spend millions of dollars in monthly leased line charges to pay for dedicated circuit-switched leased Hoot and Holler long distance connections. The Cisco Hoot and Holler over IP solution enables customers to eliminate these expensive charges while protecting investments in existing Hoot and Holler equipment such as turrets, bridges and four wire phones. The Cisco Hoot and Holler over IP features are implemented with a Cisco IOS software upgrade and is supported over voice-enabled Cisco 2600 and 3600 modular multiservice platforms.
Configuration through SNMP creates messages that are printed to the console when configuration occurs using SNMP (for example, configuration done from a NMS). Previously notifications were only sent to the console when the configuration was changed from the IOS command-line interface.
The Circuit Interface Identification MIB feature adds support for a new Cisco enterprise MIB, used for monitoring individual circuits using SNMP. The Circuit Interface Description MIB (CISCO-CIRCUIT-INTERFACE-MIB) provides a MIB object which can be used to provide a description of individual circuit-based interfaces (for example, interfaces using ATM or Frame-Relay). This description will then be returned when linkup and linkdown SNMP traps are generated for the described interface.
The WCCP Redirection on Inbound Interfaces feature adds support to Cisco IOS software for the redirection of Web Cache Coordination Protocol (WCCP) traffic on inbound interfaces. Prior to this release, WCCP Version 2 was implemented as an output feature only, with packets classified by WCCP after a routing table lookup. With Cisco IOS release 12.1(3a) T1, you can now configure an interface for inbound redirection using CEF, dCEF, Fast forwarding, and Process forwarding paths. WCCP redirection on inbound interfaces avoids the processing overhead created by CEF on outbound interfaces.
The following new software features are supported by the Cisco 2600 series for Cisco IOS Release 12.1(2) T.
Bidir-PIM is a variant of the Protocol Independent Multicast (PIM) suite of routing protocols for IP multicast. In PIM, packet traffic for a multicast group is routed according to the rules of the mode configured for that multicast group. The Cisco IOS implementation of PIM supports three modes for a multicast group:
A router can simultaneously support all three modes or any combination of them for different multicast groups. In bidirectional mode, traffic is only routed along a bidirectional shared tree that is rooted at the rendezvous point (RP) for the group. In bidir-PIM, the IP address of the RP acts as the key to having all routers establish a loop-free spanning tree topology rooted in that IP address. This IP address does not need to be a router, but can be an unassigned IP address on a network that is reachable throughout the PIM domain. Using this technique is actually the preferred configuration for establishing a redundant RP configuration for bidir-PIM.
QSIG protocol support allows Cisco voice switching services to connect private branch exchanges (PBXs), key systems (KTs), and central office switches (COs) that communicate by using the QSIG protocol, which is becoming the standard for PBX interoperability in Europe and North America. QSIG is a variant of ISDN D-channel signaling. With QSIG, Cisco networks emulate the functionality of the public-switched telephone network (PSTN), and QSIG signaling messages allow the dynamic establishment of voice connections across a Cisco wide-area network (WAN) to a peer router, which can then transport the signaling and voice packets to a second private integrated services network exchange (PINX).
QSIG support includes the following capabilities:
The Frame Relay Switching Enhancements: Shaping and Policing feature enables a router in a Frame Relay network to be used as a Frame Relay switch.
This feature includes the following Frame Relay switching enhancements:
The dial peer configuration enhancements were previously implemented in 12.1(1) T for Voice over IP on several platforms. In the 12.1(2) T release, these same enhancements are now supported on additional platforms for Voice over Frame Relay and Voice over ATM. In addition, these enhancements are now supported on the Cisco MC3810 for Voice over IP.
The local voice busyout feature provides a way to busy out a voice port if a monitored network interface changes state. When a monitored interface changes to a specified state—to out-of-service or in-service —the voice port presents a seized/busyout condition to the attached PBX or other customer premises equipment (CPE). The PBX or other CPE can then attempt to select an alternate route.
Local voice busyout is supported on analog and digital voice ports using channel associated signaling (CAS).
This feature allows you to perform the following tasks:
|
Note This feature is different from busy-back, the signal sent from the network to the calling party to indicate a busy (or congested) state along the route. |
Voice over Frame Relay functionality has been updated in this release, so that configuration on all supported platforms is nearly identical. In Cisco IOS Release 12.0(4)T, when support for Voice over Frame Relay Using FRF.11 and FRF.12 was introduced, configuration procedures were different depending on the router platform used.
Some commands introduced in earlier Cisco IOS releases have been removed or modified. This document describes the configuration procedures effective in this release.
In addition, this release provides support for digital voice calls for Voice over Frame Relay on the Cisco 2600 and 3600 series routers. In previous releases, the Cisco 2600 and 3600 series only supported analog voice calls for Voice over Frame Relay.
The ALPS Enhancements feature in Cisco IOS Release 12.1(2) T introduces additions to the ALPS service messages and extensions to the ALPS P1024B Airline Control (ALC) protocol support. This feature includes customized options to configure the format, address, and transmission of service messages. The ALPS ALC support is extended to be more scalable. This feature is an enhancement to the existing ALPS technology.
|
Note Remote routers must have the Cirrus Logic CD2430 chipset on a synchronous serial interface module to connect to the ALC or UTS ASCUs. |
The H.323 Support for Virtual Interfaces feature allows users to configure the IP address of the gateway, so that the IP address included in the H.323 packet is deterministic and consistently indicates the same address for the source.
In previous releases of the Cisco IOS software, the source address included in the H.323 packet could vary depending on the protocol (RAS, H.225, H.245, or RTP). This makes it difficult to configure firewall applications to work with H.323 messages.
The H.323 Support for Virtual Interfaces feature addresses that difficulty by allowing the user to explicitly configure an IP address to be used for all protocols
The explosive growth of the Internet has placed the focus on the scalability of Interior Gateway Protocols such as OSPF. The networks using OSPF are becoming larger every day and will continue to expand to accommodate the demand to connect to the Internet.
Internet Service Providers and customers with large networks have regularly complained that OSPF has a traffic overhead, even when the network topology is stable.
By design, OSPF requires link-state advertisements (LSAs) to be refreshed as they expire after 3600 seconds. Some implementations have tried to improve the flooding by reducing the frequency to refresh from 30 minutes to around 50 minutes. This solution reduces the amount of refresh traffic but requires at least one refresh before the LSA expires.
The OSPF Flooding Reduction feature works by reducing unnecessary refreshing and flooding of already known and unchanged information. To achieve this reduction, the LSAs are now flooded with the higher bit set, thus making them Do Not Age (DNA) LSAs.
The AAA Server Group Deadtimer feature allows each authentication, authorization, and accounting (AAA) server to be fully configured in the server group. Thus, it allows you to direct AAA traffic to separate groups of servers that have different operational characteristics.
With the introduction of this feature, deadtime has been added as a new attribute to the server group structure. In addition, a separate timer has been attached to each server host in every server group. Therefore, when a server is found to be unresponsive after numerous retransmissions and time-outs, the server is assumed to be dead. The timers attached to each server host in all server groups are triggered. In essence, the timers are checked and subsequent requests to a server (once it is assumed to be dead) are directed to alternate timers, if configured. When the network access server receives a reply from the server, it checks and stops all configured timers (if running) for that server in all server groups.
If the timer has expired, only the server to which the timer is attached is assumed to be alive. This becomes the only server that can be tried for later AAA requests using the server groups to which the timer belongs.
|
Note The deadtime attribute is supported only for RADIUS hosts. |
The Configurable Timers in H.225 feature allows users to configure the H.255 TCP connection timeout value for all out-going call attempts (on a per VoIP dial-peer basis).
In previous releases of the Cisco IOS software, the call attempt timeout was 15 seconds and could not be changed. In some cases, however, users might need a shorter timeout value to facilitate a faster fail-over. In other cases, users might need a greater timeout value.
The Configurable Timers in H.225 feature addresses those needs by allowing the user to override the default of 15 seconds and configure the timeout value.
The FR PIPQ feature provides an interface-level priority queueing scheme in which prioritization is based on destination PVC rather than packet contents. For example, FR PIPQ allows you to configure a PVC transporting voice traffic to have absolute priority over a PVC transporting signaling traffic, and a PVC transporting signaling traffic to have absolute priority over a PVC transporting data.
FR PIPQ provides four levels of priority: high, medium, normal, and low. The Frame Relay packet is examined at the interface for the data-link connection identifier (DLCI) value. The packet is then sent to the correct priority queue based on the priority level configured for that DLCI
Low Latency Queueing for Frame Relay is a new feature that provides a strict priority queue (PQ) for voice traffic and weighted fair queues for other classes of traffic. Before the release of this feature, low latency queueing was available at the interface and ATM virtual circuit (VC) levels. It is now available at the Frame Relay VC level when Frame Relay traffic shaping is configured.
Low Latency Queueing, also called priority queueing/class-based weighted fair queueing (PQ/CBWFQ), is a superset of and more flexible than previous Frame Relay Quality of Service offerings, in particular Real-Time Transport Protocol (RTP) prioritization and priority queueing/weighted fair queueing (PQ/WFQ).
The Ecosystem Gatekeeper Interoperability Enhancements: Phase 2 feature, supplements the existing support for alternate gatekeepers and adds support for the alternate gatekeeper field (altGKInfo) to the admission rejection (ARJ). This allows a gateway to move between gatekeepers during the admission request (ARQ) phase.
The Ecosystem Gatekeeper Interoperability Enhancements: Phase 2 allows gateways to move between gatekeepers without requiring a reconfiguration of the gateway or a gatekeeper failover in the gateway.
Gateways can be configured to switch from their primary gatekeeper to an alternate gatekeeper if a failure or outage occurs. If an outage occurs and gateways move from one gatekeeper to another, there may be an imbalance in the number of gateways registered to each gatekeeper. The Ecosystem Gatekeeper Interoperability Enhancements: Phase 2 helps to restore the balance (when the outage has been corrected) by allowing some of the gateways to be moved back to their proper gatekeepers.
The Gatekeeper to Gatekeeper Redundancy and Load-Sharing Mechanism feature expands the capability that is provided by the Redundant H.323 Zone Support feature. The Redundant H.323 Zone Support feature, which was introduced in Cisco IOS Software release 12.1(1) T, allows users to configure multiple gatekeepers to service the same zone or technology prefix by sending location requests (LRQs) to two or more gatekeepers.
With the Redundant H.323 Zone Support feature, the LRQs are sent simultaneously (in a "blast" fashion) to all of the gatekeepers in the list. The gateway registers with the gatekeeper that responds first. Then, if that gatekeeper becomes unavailable, the gateway registers with another gatekeeper from the list.
The Gatekeeper to Gatekeeper Redundancy and Load-Sharing Mechanism feature enhances this capability by allowing the user to choose whether the LRQs are sent simultaneously or sequentially (one-at-a-time) to the remote gatekeepers in the list. If the LRQs are sent sequentially, a delay is inserted after the first LRQ and before the next LRQ is sent. This delay allows the first gatekeeper to respond before the LRQ is sent to the next gatekeeper. The order in which LRQs are sent to the gatekeepers is based on the order in which the gatekeepers are listed (using either the zone prefix or the gw-type-prefix command).
Once the local gatekeeper has sent LRQs to all the remote gatekeepers in the list (either simultaneously or sequentially), if it has not yet received a location confirmation (LCFs) then it opens a "window". During this window, the local gatekeeper waits to see if a location confirmation (LCF) is subsequently received from any of the remote gatekeepers. If no LFC is received from any of the remote gatekeepers while the window is open, then the call is rejected.
Common Open Policy Service (COPS) is a protocol for communicating network traffic policy information to network devices. Resource ReSerVation Protocol (RSVP) is a means for reserving network resources—primarily bandwidth—to guarantee that applications transmitting across the internet will perform at the desired speed and quality. COPS with RSVP gives network managers centralized monitoring and control of RSVP, including the ability to:
The following new software features are supported by the Cisco 2600 series for Cisco IOS Release 12.1(1) T.
The AAA Broadcast Accounting feature allows accounting information to be sent to multiple authentication, authorization, and accounting (AAA) servers at the same time; that is, accounting information can be broadcast to one or more AAA servers simultaneously. This functionality allows service providers to send accounting information to their own private AAA servers and to the AAA servers of their end customers. It also provides redundant billing information for voice applications.
With the introduction of this feature, broadcasting is now allowed among groups of servers. The server groups can be either RADIUS or TACACS+. And each server group can define its backup servers for fail over independently of other groups. (Fail over is a process that may occur when more than one server has been defined within a server group. Fail over refers to the process by which information is sent to the first server in a server group; if the first server is unavailable, the information is sent to the next server in the server group. This process continues until the information is successfully sent to one of the servers within the server group or until the list of available servers within the server group is exhausted.)
The Answer Supervision Report feature is an enhancement to the information request (IRR) Registration, Admission, and Status protocol (RAS) message that enables Gatekeepers to maintain call accounting information by reporting the call connection time of connected calls to the Gatekeeper.
In H.323 configurations, direct call-routed signaling is utilized by the endpoint (Gateway). Gatekeepers do not have real-time knowledge or control over the state of a call and are dependent on the endpoints to provide them the necessary real-time information, such as the call connect time, call termination time, and call termination reason.
When a call ends, the Gateway sends a Disengage Request (DRQ) message with the BillingInformationToken (which contains the duration of the call) to the Gatekeeper. However, if the Gatekeeper does not receive the DRQ message for some reason, the Gatekeeper will not have the information about when the call started or the duration of the call, which is necessary to maintain accounting information.
The Answer Supervision Reporting feature addresses the need to report the call connection time to the Gatekeeper upon the connection of a call and at periodic intervals thereafter. The Answer Supervisor Reporting feature adds a proprietary Cisco parameter, the call connection time parameter, to the perCallInfo parameter in the nonStandardData field, which is located in the IRR message. When a CONNECT message is received, the originating Gateway sends the unsolicited IRR message to its Gatekeeper. On sending a CONNECT message, the terminating Gateway sends the unsolicited IRR message to its Gatekeeper. If the admission confirmation (ACF) message has a nonzero value for the IRR frequency parameter, the Gateway sends the unsolicited IRR message to its Gatekeeper at periodic intervals, which are determined by the value in the IRRfrequency parameter.
The Cisco IOS software Asynchronous Rotary Line Queueing feature allows Telnet connection requests to busy asynchronous rotary groups to be queued so that users automatically obtain the next available line, rather than needing to try repeatedly to open a Telnet connection. The Cisco IOS software sends a periodic message to the user to update progress in the connection queue.
Connections are authenticated using the method specified for the line configurations for the asynchronous rotary group. If a connection is queued, authentication is done prior to queueing and no authentication is done when the connection is later established.
Cisco H.323 Version 2 Phase 2 adds the following benefits to Cisco H.323 Gatekeepers, gateways, and proxies:
The following enhancements to dial peer configuration lower complexity of dial planning and reduces the amount of effort in creating dial peer entries:
The Ecosystem Gatekeeper Interoperability Enhancements feature allows gateways to move between gatekeepers without requiring a reconfiguration of the gateway or a gatekeeper failover in the gateway.
Gateways can be configured to switch from their primary gatekeeper to an alternate gatekeeper if a failure or outage occurs. If an outage occurs and gateways move from one gatekeeper to another, there may be an imbalance in the number of gateways registered to each gatekeeper. The Ecosystem Gatekeeper Interoperability Enhancements helps to restore the balance (when the outage has been corrected) by allowing some of the gateways to be moved back to their proper gatekeepers.
The Ecosystem Gatekeeper Interoperability Enhancements feature supplements the existing support for alternate gatekeepers and adds support for the alternate gatekeeper field (altGKInfo) to the gatekeeper rejection (GRJ) and registration rejection (RRJ) messages. This allows a gateway to move between gatekeepers during the gatekeeper request (GRQ) and registration request (RRQ) phases.
The Gateway-to-Gatekeeper Billing Redundancy feature enhances the accounting capabilities of the Cisco H.323 Gateway and provides support for Vocaltec Gatekeepers. The Gateway-to-Gatekeeper Billing Redundancy feature provides redundant billing information to an alternate gatekeeper if the primary Gatekeeper to which a Gateway is registered becomes unavailable.
During the process of establishing a call, the primary Gatekeeper sends an admission confirmation (ACF) message to the registered Gateway. The ACF message includes the user's billing information and an access token. To provide the billing information to an alternate gatekeeper if the primary Gatekeeper is unavailable when the call session ends, the access token information sent in the ACF message in now also included in the disengage request (DRQ) message that is sent to the alternate Gatekeeper.
This features enables the alternate Gatekeeper to obtain the billing information required to successfully complete the transaction.
IKE Extended Authentication (Xauth) is a draft RFC developed by the Internet Engineering Task Force (IETF) based on the Internet Key Exchange (IKE) protocol. The Xauth feature is an enhancement to the existing Internet Key Exchange (IKE) Protocol feature. Xauth allows all Cisco IOS software AAA authentication methods to perform user authentication in a separate phase after the IKE authentication phase 1 exchange. The AAA configuration list-name must match the Xauth configuration list-name for user authentication to occur.
The Xauth feature is an extension to the IKE feature, and does not replace IKE authentication.
The IKE Shared Secret Using AAA Server feature enables key lookup from a AAA server. Pre-shared keys do not scale well when trying to deploy a large scale Virtual Private Network (VPN) without using a certification authority (CA). When using dynamic IP addressing such as DHCP or PPP dialups, the changing IP address can make key lookup difficult or impossible unless wildcard pre-shared key is used.
In the IKE Shared Secret Using AAA Server feature, the shared secret is accessed during the aggressive mode of IKE negotiation through the AAA server. The ID of the exchange is used as the username to query AAA if no local key can be found on the Cisco IOS router to which the user is trying to connect.
The ISDN Network Side for ETSI Net5 PRI feature enables Cisco IOS to replicate the public switched network interface to a PBX that is compatible with the ETSI Net5 switch type.
Routers and PBXs are both traditionally CPE with respect to the public switched network interfaces. For Voice over IP (VoIP) applications, it is desirable to interface access servers to PBXs with the access server representing the public switched network.
Enterprise organizations use the current VoIP features with Cisco products as a method to reduce long distance costs for phone calls within and outside of their organizations. However, there are times that a call cannot go over VoIP and the call needs to be placed using the PSTN. The customer then must have two devices connected to a PBX to allow some calls to be placed using VoIP and some calls to be placed over the Public Switched Telephone Network (PSTN). In contrast, this feature allows Cisco access servers to connect directly to user-side CPE devices such as PBXs and allows voice calls and data calls to be placed without requiring two different devices to be connected to the PBXs.
This feature enables the access server to provide a standard ISDN PRI network side interface to the PBXs and to mimic the behavior of legacy phone switches. To a PBX, the access server functions as a Net5 PRI switch. No change in PBX capability or behavior is required.
Pragmatic General Multicast (PGM) is a reliable multicast transport protocol for multicast applications that require reliable, ordered, duplicate-free multicast data delivery from multiple sources to multiple receivers. PGM guarantees that a receiver in a multicast group either receives all data packets from transmissions and retransmissions, or can detect unrecoverable data packet loss. PGM is intended as a solution for multicast applications with basic reliability requirements.
The SA Agent Enhancements feature enhances the management and measurement of enterprise and service provider networks. Service Level Agreements (SLA) are useful for managed network services such as managed WAN access and managed virtual private network (VPN) services. The SA Agent Enhancement feature provides tools for measuring network performance using FTP, which is one of the most popular traffic types in Internet service provider (ISP) networks, and jitter (one-way delay), which is important for applications such as Voice over IP (VoIP).
Voice over Internet Protocol (VoIP) currently implements ITU's H.323 specification within Internet Telephony Gateways (ITGs) to signal voice call setup. Session Initiation Protocol (SIP) is a new protocol developed by the Internet Engineering Task Force (IETF) Multiparty Multimedia Session Control (MMUSIC) Working Group as an alternative to H.323. SIP features are compliant with IETF RFC 2543, published in March 1999.
The Cisco SIP functionality equips the Cisco AS5300 access server, and the Cisco 2600 and Cisco 3600 series routers to signal the setup of voice and multimedia calls over IP networks; therefore, the SIP feature, introduced in Cisco IOS Release 12.1(1) T, provides an alternative to H.323 within the VoIP internetworking software.
This is the second release of Cisco's Open Settlement Protocol (OSP) features. Some settlement vendors have required roaming users to be authenticated and accounted for by the settlement clearinghouse. Therefore, this IOS Release 12.1.(1)T introduces two new features, roaming and multiple roots.
A wildcard pre-shared key allows a group of remote users with the same level of authentication to share an IKE pre-shared key. The remote peer's pre-shared key must match the local peer's pre-shared key for IKE authentication to occur. The term wildcard means that any remote peer with the pre-shared key can access the local peer, regardless of the remote peer's IP address assignment. The term pre-shared key is a shared secret key exchanged during IKE negotiation.
A wildcard pre-shared key is usually distributed through a secure out-of-band channel. In a remote peer-to-local peer scenario, any remote peer with the IKE pre-shared key configured can establish IKE security associations (SAs) with the local peer.
The wildcard pre-shared key feature is an enhancement to the crypto isakmp key global configuration command. With a wildcard IP address of 0.0.0.0 and pre-shared key authentication method configured on the local router, the local router can authenticate the IKE SA with any remote peer that has a matching wildcard pre-shared key.
The following sections contain important notes about Cisco IOS Release 12.1(3) T that can apply to the Cisco 2600 series.
Because of a number of issues with H.323 and SIP voice support on the Cisco AS5300, Cisco AS5800, Cisco 2600 series, Cisco 3600 series, and Cisco MC3810 which arose in Cisco IOS Release 12.1 T, use of 12.1(3) T and 12.1(3a) T1 is strongly discouraged.
Cisco IOS Release 12.1(3) T and 12.1(3a) T1 is being made available for dial applications only. The problems with voice in this release are being tracked in the following DDTS reports:
For a more detailed Field Notice report see: http://www.cisco.com/warp/public/770/45.html
Beginning with Cisco IOS Release 12.0(7) XK, Cisco changed the product numbers used to order a specific Cisco IOS software image. In short, Cisco will remove the periods separating the release train, maintenance release, and build number. The following table provides some examples.
Old Product Number | New Product Number | Release | Image Description |
|---|---|---|---|
|
|
|
|
|
|
|
|
Old Cisco Management Information Bases (MIBs) will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBs—without affecting existing Cisco IOS products or NMS applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 6.
| Deprecated MIB | Replacement |
|---|---|
OLD-CISCO-APPLETALK-MIB | RFC1243-MIB |
OLD-CISCO-CHASSIS-MIB | ENTITY-MIB |
OLD-CISCO-CPUK-MIB | To be decided |
OLD-CISCO-DECNET-MIB | To be decided |
OLD-CISCO-ENV-MIB | CISCO-ENVMON-MIB |
OLD-CISCO-FLASH-MIB | CISCO-FLASH-MIB |
OLD-CISCO-INTERFACES-MIB | IF-MIB CISCO-QUEUE-MIB |
OLD-CISCO-IP-MIB | To be decided |
OLD-CISCO-MEMORY-MIB | CISCO-MEMORY-POOL-MIB |
OLD-CISCO-NOVELL-MIB | NOVELL-IPX-MIB |
OLD-CISCO-SYS-MIB | (Compilation of other OLD* MIBS) |
OLD-CISCO-SYSTEM-MIB | CISCO-CONFIG-COPY-MIB |
OLD-CISCO-TCP-MIB | CISCO-TCP-MIB |
OLD-CISCO-TS-MIB | To be decided |
OLD-CISCO-VINES-MIB | CISCO-VINES-MIB |
OLD-CISCO-XNS-MIB | To be decided |
|
Note Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. If you have an account with CCO, you can find the current list of MIBs supported by Cisco. To reach the Cisco Network Management Toolkit, go to CCO, press Login, and click to Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
Caveats describe unexpected behavior or defects in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
For information on caveats in Cisco IOS Release 12.1(3) T, see Caveats for Cisco IOS Release 12.1T that accompanies these release notes. This document lists severity 1 and 2 caveats for Cisco IOS Release 12.1.
All caveats in Cisco IOS Release 12.1 are also in Cisco IOS Release 12.1T.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1 , which lists severity 1 and 2 caveats and is located on CCO and the Documentation CD-ROM.
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. Click on this path: Software Center: Cisco IOS Software: Cisco IOS Bug Toolkit: Cisco Bug Navigator II. You can also find Bug Navigator II at http://www.cisco.com/support/bugtools |
The following sections describe the documentation available for the Cisco 2600 series. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.
Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online on CCO and the Documentation CD-ROM.
Use these release notes with these documents:
The following documents are specific to or support Cisco IOS Release 12.1 and are located on CCO and the Documentation CD-ROM:
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. Click on this path: Software Center: Cisco IOS Software: Cisco IOS Bug Toolkit: Cisco Bug Navigator II. You can also find Bug Navigator II at http://www.cisco.com/support/bugtools |
These documents are available for the Cisco 2600 on CCO and the Documentation CD-ROM:
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers
Feature modules describe new features supported by Cisco IOS Release 12.1T, and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1T
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1T
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents which 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, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 7 describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form upon request.
|
Note You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. |
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
You can reach the Cisco IOS documentation set on the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
| Books | Chapter Topics |
|---|---|
| Configuration Fundamentals Overview |
| Transparent Bridging |
| X.25 over ISDN |
| Interface Configuration Overview |
| IP Overview |
| AppleTalk |
| Network Protocols Overview |
| AAA Security Services |
| Switching Services |
| Wide-Area Network Overview |
| Voice over IP |
| Policy-Based Routing |
|
|
|
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. For the latest list of MIBs supported by Cisco, see Cisco Network Management Toolkit on Cisco Connection Online. From CCO, click on the following path: Service & Support: Software Center: Network Mgmt Products: Cisco Network management Toolkit: Cisco MIB. |
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 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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 have a CCO log-in account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/technotes/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO, press Login, and click on this path: Technical Assistance Center: Technical Tips.
The following sections are provided from the Technical Tips page:
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.
|
Note |
Posted: Tue Sep 5 11:49:36 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
