|
|
 |
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. |
|
Note See Important Notes 72 for information concerning Cisco IOS Release 12.1(5)T. |
These release notes for the Cisco 3600 series support Cisco IOS Release 12.1(5)T. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.
For a list of the software caveats that apply to Release 12.1(5)T, see Caveats for Cisco IOS Release 12.1 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:
The Cisco 3600 series includes the Cisco 3620, Cisco 3640, and Cisco 3660 routers. As modular solutions, the Cisco 3600 series routers enable corporations to increase dial-up density and take advantage of current and emerging WAN technologies and networking capabilities. The Cisco 3600 series routers are fully supported by Cisco IOS software, which includes dial-up connectivity, LAN-to-LAN routing, data and access security, WAN optimization, and multimedia features.
This section describes the system requirements for Release 12.1(5)T:
Table 1 lists recommended minimum memory for the Cisco 3600 series routers.
Table 1 Minimum Memory Recommendations for the Cisco 3600 Series
| Feature Set by Platform | Image Name | Minimum Flash Memory | Minimum DRAM Memory | Runs from | |
|---|---|---|---|---|---|
| Cisco 3620 | |||||
| Cisco 3620 (continued) | |||||
| Cisco 3640 | |||||
| Cisco 36601 | |||||
Telco Plus2 |
|||||
| 1The Cisco 3660 uses SDRAM.
2The Telco images only run on the 3660-AC-CO and 3660-DC-CO. |
Cisco IOS Release 12.1(5)T supports the Cisco 3600 series routers:
Table 2 lists the supported interfaces for the Cisco 3600 series routers for Cisco IOS Release 12.1(5)T.
Table 2 Supported Interfaces for the Cisco 3600 Series
| Interface, Network Module, or Data Rate | Platforms Supported | |
|---|---|---|
| Dial Access Network Modules | ||
6- to 30-port integrated digital modems network modules (NM-6DM, NM-12-DM, NM-18DM, NM-24DM, NM-40DM) |
||
8- or 16-port integrated analog network modules (NM-8AM and NM16AM) |
||
| LAN Interfaces | ||
1-port Fast Ethernet (100BaseTX and 100BaseFX, NM-1FE-TX and NM-1FE-FX) |
||
| Mixed Media Network Modules | 1-port 10/100BaseTX with 1-port channelized/PRI /E1 balanced mode (NM-1FE1CE1B) |
|
1-port 10/100BaseTX with 1-port channelized/PRI/E1 unbalanced mode (NM-1FE1CE1U) |
||
1-port 10/100BaseTX with 1-port channelized/PRI/T1(NM-1FE1CT1) |
||
1-port 10/100BaseTX with 1-port channelized/PRI /T1 with CSU (NM-1FE1CT1-CSU) |
||
1-port 10/100BaseTX with 2-port channelized/PRI/ E1 balanced mode (NM-1FE2CE1B) |
||
1-port 10/100BaseTX with 2-port Channelized/PRI /E1 unbalanced mode (NM-1FE2CE1U) |
||
1-port 10/100BaseTX with 2-port channelized/PRI /T1 (NM-1FE2CT1) |
||
1-port 10/100BaseTX with 2-port channelized/PRI/ T1 with CSU (NM-1FE2CT1-CSU) |
||
1-port fast Ethernet, 1-port Token Ring with 2 WAN card slots (NM-1FE1R2W[=]) |
||
| Multiport T1/E1 ATM Network Modules with Inverse Multiplexing over ATM (IMA)1 | ||
| Digital T1/E1 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-T12. Part number: NM-HDV-1T1-24 |
|
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-T12. Part number: NM-HDV-1T1-24E |
||
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-DI2. Part number: NM-HDV-2T1-48 |
||
1-port, 30-channel E1 voice/fax module, supports 30 channels of G.729a/b, G.726, G.711 and fax or 18 channels of G.726, G.729, G.723.1, G.728, G.729a/b, G.711, and fax. Consists of one NM-HDV, three PVDM-12s, and one VWIC-1MFT-E12. (NM-HDV-1E1-30[=]) |
||
1-port, enhanced 30-channel E1 voice/fax module, supports 30 channels of G.729a/b, G.726, G.729, G.728, G.723.1, G.711, and fax. Consists of one NM-HDV, five PVDM-12s, and one VWIC-1MFT-E12. (NM-HDV-1E1-30E[=]) |
||
2-port, 60-channel E1 voice/fax module, supports add/drop multiplexing (drop and insert); 60 channels of G.729a/b, G.726, G.711, and fax or 30 channels of G.726, G.729, G.723.1, G.728, G.729a/b, G.711, and fax. Consists of one NM-HDV, five PVDM-12s, and one VWIC-2MFT-E1-D12. (NM-HDV-2E1-60[=]) |
||
Digital T1 Packet Voice Trunk Network Modules spare component |
||
Digital T1 Packet Voice Trunk Network Modules spare component |
||
| Digital T1/E1 Packet Voice Trunk Network Modules and Spare Components (Continued) | Digital T1 Packet Voice Trunk Network Modules spare component |
|
Digital T1 Packet Voice Trunk Network Modules spare component |
||
2-port RJ-48 multiflex trunk with drop and insert—T1 (VWIC-2MFT-T1-DI(=))2 |
Digital T1 Packet Voice Trunk Network Modules spare component |
|
| T1/E1 Multiflex Voice/WAN Interface Cards | ||
2-port T1 multiflex trunk interface with drop and insert (VWIC-2MFT-T1-DI)3 |
||
2-port E1 multiflex trunk interface with drop and insert (VWIC-2MFT-E1-DI) |
||
| Voice/Fax Interfaces and Network Modules1 | ||
All Cisco 3600 series platforms with Voice/Fax network module |
||
2-port FXO voice interface card (VIC-2FXO, VIC-2FXO-M3, and VIC-2FXO-EU) |
All Cisco 3600 series platforms with Voice/Fax network module |
|
All Cisco 3600 series platforms with Voice/Fax network module |
||
| WAN Data Rates | ||
| Network Modules | 1- and 2-port channelized T1 modules without CSUs (NM-1CT1 and NM-1CT1) |
|
1- and 2-port channelized T1 network modules with CSUs (NM-1CT1-CSU and NM-2CT1-CSU) |
||
1- and 2-port E1 network modules unbalanced mode NM-1CE1U and NM-2CE1U) |
||
1- and 2-port E1 network modules balanced mode (NM-1CE1B and NM-2CE1B) |
||
1-port ATM T3 network module (NM-1A-T3)1 |
||
| Network Modules (Continued) | 1-port ATM E3 network module (NM-1A-E3)1 |
|
4- and 8-port BRI network module with NT1 (NM-4B-U and NM-8B-U) |
||
4- and 8-port BRI network module with S/T interface (NM-4B-S/T and NM-8B-S/T |
||
4- and 8-port synchronous/asynchronous (NM-4A/S and NM-8A/S) |
||
1-port ATM OC-3 network module with multimode fiber (NM-1A-OC3MM) |
||
1-port ATM OC-3 network module with single-mode intermediate reach fiber (NM-1A-OC3SMI) |
||
1-port ATM OC-3 network module with single-mode long reach fiber (NM-1A-OC3SML) |
||
1-port ATM OC-3 multimode network module and circuit emulation service (NM-1A-OC3MM-1V)4 |
||
1-port ATM OC-3 single-mode, intermediate reach network module and circuit emulation service (NM-1A-OC3SMI-1V)4 |
||
1-port ATM OC-3 single-mode, long reach network module and circuit emulation service (NM-1A-OC3SML-1V)4 |
||
| Other Network Modules | ||
4 E1 data compression Advanced Integration Module (AIM-COMPR4) |
||
| WAN Interface Cards | 1-port T1/Fractional T1/DSU/CSU WAN interface card (WIC-1DSU-T1) |
|
1-port T1/Fractional T1 56/64 kbps DSU/CSU WAN interface card (WIC-1DSU-56K4) |
||
| 1Requires the Cisco IOS Plus feature sets.
2See T1/E1 Multiflex Voice/WAN Interface Cards in this table. 3For Cisco 3660 series, only supported in T1/E1 digital packet voice trunk network modules and new Fast Ethernet mixed media network modules: NM-1FE2W, NM-2FE2W, NM-1FE1R2W, NM-2W. For Cisco 3620 and 3640, supported in T1/E1 digital packet voice trunk network modules or in 1- or 2-port Ethernet and Fast Ethernet network module (NM-1E2W, NM-2E2W, NM-1E1R2W, NM-1FE2W, NM-2FE2W, NM-1FE1R2W, NM-2W) 4For the Cisco 3660 series only, online insertion and removal (OIR) is now supported in Cisco IOS Release 12.1(5)T. 5Supported in Fast Ethernet mixed media network modules: NM-1FE2W, NM-2FE2W, NM-1FE1R2W, NM-2W. |
To determine the version of Cisco IOS software running on a Cisco 3600 series router, log in to the router and enter the show version EXEC command:
For general information about upgrading to a new software release, see the product bulletin Cisco IOS Upgrade Ordering Instructions on CCO located at:
http://www.cisco.com/warp/public/cc/cisco/mkt/ios/prodlit/957_pp.htm
Service & Support: Software Center: Cisco IOS Software: Product Bulletins: Software
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, as shown in Table 3.
Table 3 Feature Sets Supported by the Cisco 3600 Series
| Feature Set | Feature Set Matrix Term | Software Image | Platforms | |
|---|---|---|---|---|
| 1This feature set is offered in the basic feature set.
2This feature set is offered in the Plus feature set. 3This feature set is offered in the encryption feature sets which consist of IPSec 56-bit (Plus IPSec 56) data encryption feature sets. 4This feature set is offered in the encryption feature sets which consist of Triple DES (3DES) Encryption data encryption feature sets. 5For 3662-xC-CO chassis only. |
 |
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, purchaser/user 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, 5, 6 and 7 list the features and feature sets supported by the Cisco 3600 series in Cisco IOS Release 12.1(5)T 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. |
Table 4 Feature Lists by Feature Sets for the Cisco 3620 and 3640 Routers, Part 1 of 2
| Features | In | Feature Sets | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IP | IP H.323 | IP Plus | IP Plus IPSec 56 | IP/ FW/ IDS |
IP/ FW/IDS Plus IPSec 56 |
IP Plus IPSec 3DES1 | IP/FW/ IDS Plus IPSec 3DES | IP/IPX/ AT/ DEC |
IP/ IPX/ AT/ DEC Plus |
IP/IPX/AT/ DEC/ FW/ IDS Plus |
||
| New Features in 12.1(5)T | ||||||||||||
Inter-Autonomous Systems MPLS VPN Support1 |
||||||||||||
ISDN Progress Indicator Support for SIP Using using 183 Session Protocol |
||||||||||||
Leased Line Support for 2600/3600 Analog Modems 3600 Analog Modems NM-16AM and NM-8AM |
||||||||||||
NAT—Support for NetMeeting Directory (Internet Locator Service - ILS) |
||||||||||||
| Connectivity | ||||||||||||
| IBM Support | ||||||||||||
| IP/IPX Routing | ||||||||||||
| IP Multicast | ||||||||||||
| Management | ||||||||||||
| Quality of Service | ||||||||||||
| Security | ||||||||||||
| Switching | ||||||||||||
| Voice and Multimedia | ||||||||||||
Voice over Frame Relay Configuration Updates (FRF.11 and FRF.12) |
||||||||||||
H.235 Accounting and Security Enhancements for Cisco Gateways |
||||||||||||
| WAN Services | ||||||||||||
ISDN Dynamic Multiple Encaps for Dial-in with Frame Relay Support |
||||||||||||
Multiport T1/E1 ATM Network Module with Inverse Multiplexing over ATM |
||||||||||||
| 1This image was introduced in Release 12.0(2)T.
2Cisco 3640 routers only. 3Cisco 3640 routers only. 4Cisco 3660 routers only. 5Cisco 3640 and 3660 routers only. |
Table 5 Feature Lists by Feature Sets for the Cisco 3620 and 3640 Routers, Part 2 of 2
| 1This image was introduced in Cisco IOS Release 12.0(2)T.
2Cisco 3640 routers only. 3Cisco 3640 routers only. 4Cisco 3620 and 3660 routers only. 5Cisco 3660 routers only. 6 Cisco 3640 and 3660 routers only. |
Table 6 Feature Lists by Feature Sets for the Cisco 3661 and 3662 Routers, Part 1 of 2
| 1Cisco 3620 and 3660 routers only.
2Cisco 3660 routers only. |
Table 7 Feature Lists by Feature Sets for the Cisco 3661 and 3662 Routers, Part 2 of 2
| 1Cisco 3620 and 3660 routers only.
2Cisco 3660 routers only. |
The following is a list of the new hardware and software features supported by the Cisco 3600 series for Release 12.1(5)T. These features are broken down by feature in Tables 4, 5, 6 and 7.
The following new hardware is supported by the Cisco 3600 series for Cisco IOS Release 12.1(5)T.
The data encryption AIM (Advanced Integration Module) and NM (Network Module) modules are hardware Layer 3 (IPSec) encryption modules and provide DES (56-bit) and 3DES (168-bit) IPsec encryption for multiple T1s or E1s of bandwidth. This level of performance is a dramatic increase over that achievable when running IPSec in software on the main CPU of the Cisco 3600. These products also have hardware support for DH, RSA, and DSA key generation.
In addition to encryption, the data encryption AIM is intended to increase the security of passwords and various encryption keys over that provided by IOS software and the platform hardware. Specifically, these products have been submitted for Level 2 of the Federal Information Processing Standard (FIPS) 140-1 in general as well as more stringent levels for some parameters such as Level 3 tamper resistance. For more information see Installing the Data Encryption AIM in Cisco 2600 Series and Cisco 3600 Series Routers on CCO.
The ISDN BRI NT/TE voice interface card (VIC-2BRI-NT/TE) for the Cisco 2600 series enables Cisco IOS software to replicate the public switched network interface to a PBX that is compatible with European Telecommunications Standards Institute (ETSI) NET3 and QSIG switch types.
In the past, customers with PBXs that implement only the BRI TE interface have had to make substantial hardware and software changes on the PBX to implement the NT interface. The implementation of an NT interface on the router allows the customer to connect ISDN PBXs and key systems to a multiservice network with a minimum of configuration changes on the PBX.
The following new hardware features are supported by the Cisco 3600 series for Cisco IOS Release 12.1(2)T.
Circuit emulation is a service based on ATM Forum standards that allows communications to occur between AAL1 CES and ATM UNI interfaces, that is, between non-ATM telephony devices (such as classic PBXs or TDMs) and ATM devices (such as Cisco 2600 and 3600 series routers). Thus, a Cisco 2600 or 3600 series router equipped with an ATM OC-3 network module with circuit emulation service offers a migration path from classic T1/E1 data communications services to emulated CES T1/E1 unstructured (clear channel) services or structured (N x 64) services in an ATM network.
The following network modules are available:
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 queuing 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 3600 series for Cisco IOS Release 12.1(5)T.
The AutoInstall Using DHCP for LAN Interfaces feature replaces the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces. AutoInstall is a Cisco IOS software feature which provides for the configuration of a new routing device automatically when the device is initialized. DHCP (defined in RFC 2131) is based on the Bootstrap Protocol, which provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options. In Cisco IOS release 12.1(5)T, the IP address procurement phase of the AutoInstall process is now accomplished using DHCP for LAN interfaces. Prior to this release, IP addresses for LAN interfaces were obtained using BOOTP during the AutoInstall process. The AutoInstall Using DHCP for LAN Interfaces feature also allows the routing device to recognize IP address allocation messages coming from regular BOOTP servers, providing a seamless transition for those devices already using BOOTP servers for AutoInstall. Additionally, this feature allows for the uploading of configuration files using unicast TFTP.
The CEF Switching for Routed Bridge Encapsulation feature adds Cisco Express Forwarding (CEF) switching support to ATM routed bridge encapsulation (RBE) on the Cisco 3640 series. Prior to this release, ATM RBE supported only fast switching and process switching. The ATM RBE feature is used to route IP over bridged RFC 1483 Ethernet traffic from a stub-bridged LAN.
QDM is a web-based Java application that allows users to configure and monitor advanced IP-based Quality of Service (QoS) functionality within Cisco routers using a graphical user interface (GUI).
QDM 2.0 is available as a separate product download and is free of charge. If you elected to have QDM installed when you purchased your router, QDM is already installed on your router. If you would like to install or reinstall QDM, see the Release and Installation Notes for Cisco Quality of Service Device Manager 2.0 on CCO and the Documentation CD-ROM.
If you ordered your router with QDM pre-installed, see the "QuickStarting QDM 2.0" section in the Installation and Release Notes for Quality of Service Device Manager 2.0 before using the QDM 2.0 application.
The Class-Based Ethernet CoS Matching and Marking (801.1p & ISL CoS) feature (which is also called Class-Based Marking or QoS Packet Marking in some Cisco documentation) has been enhanced for the Cisco 3640 routers to include the ability to mark and match Class of Service values and to set the ATM cell lose priority (CLP) bit value on packets.
Associating a packet with a local CoS value enables users to associate a Layer 2 Class of Service (CoS) value with a packet. The value can then be used to classify packets based on user-defined requirements. Layer 2 to Layer 3 mapping can also be configured by matching on the CoS value, since switches already have the capability to match and set CoS values. If a packet that needs to be marked to differentiate user-defined QoS services is leaving a router and entering a switch, the router should set the CoS value of the packet, since the switch can process the Layer 2 CoS header marking.
Changing the CLP bit setting in the ATM header of a cell provides a method of controlling the discarding of cells in congested ATM environments. A CLP bit contains two settings: 0 or 1. Cells with a CLP bit setting of 1 are discarded before cells with a CLP bit setting of 0. Before users had the ability to change the CLP bit setting in the ATM header, the CLP bit was automatically set to 0 on packets leaving Cisco routers that were converted into ATM cells for ATM networks. The CLP bit on packets leaving Cisco routers for ATM networks can now be set to 1.
For additional information on Class-Based Packet Marking, including information on the new enhancements, see the Class-Based Packet Marking feature module on CCO and the Documentation CD-ROM.
The Class-Based Policer for the DiffServ AF PHB is based on RFC 2697 - "A Single Rate Three Color Marker". The packet stream is metered and packets are marked either "conform", "exceed", or "violate". Marking is based on a Committed Information Rate (CIR) and two associated burst sizes, a Committed Burst Size (CBS) and an Excess Burst Size (EBS). A packet is marked "conform" if it doesn't exceed the CBS," exceed" if it exceeds the CBS, but not the EBS, and "violate" otherwise.
The Class-Based Quality of Service Management Information Base (Class-Based QoS MIB) provides read access to class-based QoS configurations. This MIB also provides QoS statistics information based on the Modular QoS CLI, including information regarding class map and policy map parameters.
This Class-Based QoS MIB is actually two MIBs: CISCO-CLASS-BASED-QOS-MIB and CISCO-CLASS-BASED-QOS-CAPABILITY-MIB.
A closed user group (CUG) selection facility is a specific encoding element that allows a destination data terminal equipment (DTE) to identify the CUG to which the source and destination DTEs belong. The Closed User Group Selection Facility Suppress Option feature enables a user to configure an X.25 data communications equipment (DCE) interface or X.25 profile with a DCE station type to remove the CUG selection facility from incoming call packets destined for the preferential CUG only or for all CUGs. You can also remove the selection facility from a CUG with outgoing access (CUG/OA).
This feature allows customers to specify the number of packets contained in the hold queue, per virtual circuit (VC), on ATM adapters that support per-VC queueing. By default, the queueing mechanism in use determines the size of the hold queue, and, therefore, the number of packets contained in the queue. This feature allows customers to expand the default hold queue size and change (or vary) the number of packets the queue can contain. With this new feature, the hold queue can contain a maximum of 1024 packets. This feature provides a new command, called vc-hold-queue, that allows the customer to specify the number of packets contained in the per-VC hold queue. This can be a number from 5 to 1024.
A closed user group (CUG) selection facility is a specific encoding element that allows a destination data terminal equipment (DTE) to identify the CUG to which the source and destination DTEs belong. The Closed User Group Selection Facility Suppress Option feature enables a user to configure an X.25 data communications equipment (DCE) interface or X.25 profile with a DCE station type to remove the CUG selection facility from incoming call packets destined for the preferential CUG only or for all CUGs. You can also remove the selection facility from a CUG with outgoing access (CUG/OA).
This feature supports the data encryption Advanced Integration Modules (AIM) and Network Module (NM) to provide hardware-based encryption for the Cisco 2600 and 3600 series routers. This feature requires both Cisco IOS Release 12.1(3a) XI1, or later, and one of the Cisco IOS feature sets that includes IPSec.
This feature extends the functionality of WRED (Weighted Random Early Detection) to enable support for Differentiated Services (DiffServ) and Assured Forwarding (AF) Per Hop Behavior (PHB). This feature enables WRED to be compliant with the DiffServ standard and the AF PHB standard being developed by the Internet Engineering Task Force (IETF). This feature enables customers to implement AF PHB by coloring packets according to DSCP values and then assigning preferential drop probabilities to those packets.This feature adds two new commands, random-detect dscp and dscp. It also adds two new arguments, dscp-based and prec-based, to two existing WRED-related commands—the random-detect (interface) command and the random-detect-group command.
The Frame Relay Fragmentation with Hardware Compression feature introduces the following functionality:
This new feature enables FRF.12, FRF.11 Annex C, and Cisco proprietary fragmentation to work with hardware compression on interfaces and virtual circuits (VCs) using Cisco proprietary or Internet Engineering Task Force (IETF) encapsulation types.
The Frame Relay Fragmentation with Hardware Compression feature introduces a new, proprietary hardware and software compression protocol called data-stream compression, which can be used on the same VC or interface as header compression. Data-stream compression is functionally equivalent to FRF.9 compression and must be used with Cisco proprietary encapsulation. Frame Relay fragmentation can also be enabled.
The Frame Relay Fragmentation with Hardware Compression feature provides hardware and software compression interoperability when hardware compression is configured on one side of the link and software compression is configured on the other side.
Internet Group Management Protocol (IGMP) is a protocol used by IPv4 systems to report IP multicast group memberships to neighboring multicast routers. On networks with hosts directly attached, IGMP Version 3 (IGMPv3) adds support for "source filtering" which enables a multicast receiver to signal to a router which groups it wants to receive multicast traffic from, and from which source(s) this traffic is expected. Based on this membership information, Cisco IOS software only forwards traffic that is requested by the host (or by other routers via Protocol Independent Multicast (PIM)) to that network. In addition to restricting traffic on the network of the receiver host, IGMPv3 membership information may also be propagated to multicast routing protocols to enable the forwarding of traffic from permitted sources or to restrict traffic from denied sources along the entire multicast data delivery path.
In the Source Specific Multicast feature, introduced in Cisco IOS Release 12.1(3)T, hosts must explicitly include sources when joining a multicast group (this is known as "channel subscription"). IGMPv3 is the industry-designated standard protocol for hosts to signal channel subscriptions in SSM. In deployment cases where IGMPv3 cannot be used (for example, if it is not supported by the receiver host or its applications), there are two other mechanisms to enable Source Specific Multicast (SSM): URL Rendezvous Directory (URD) and IGMP v3lite. Both of these features were introduced with SSM in Cisco IOS Release 12.1(3)T.
The Inter-Autonomous Systems MPLS VPN Support feature on the Cisco 3620 and 3660 series platforms provides a seamless integration of autonomous systems and service providers. Separate autonomous systems from different service providers can communicate by exchanging IPv4 network layer reachability information (NLRI) in the form of VPN-IPv4 addresses. The autonomous systems' border edge routers use exterior border gateway protocol (EBGP) to exchange that information. Then, an interior gateway protocol (IGP) distributes the network layer information for VPN-IPv4 prefixes throughout each VPN and each autonomous system.
One of the most commonly used identifiers used in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface; as far as most software is concerned, the ifIndex is the "name" of the interface. Although there is no requirement in the relevant RFCs that the correspondence between particular ifIndex values and their interfaces be maintained across reboots, applications such as device inventory, billing, and fault detection increasingly depend on the maintenance of this correspondence.
Cisco IOS Release 12.1(5)T adds support for an ifIndex value that can persist across reboots, allowing users to avoid the workarounds previously required for consistent interface identification. The Interface Index Persistence feature allows for greater accuracy when collecting and processing network management data by uniquely identifying input and output interfaces for traffic flows and SNMP statistics. Relating each interface to a known entity (such as an ISP customer) allows network management data to be more effectively utilized. See the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt5ifidx.htm
The Interworking Signaling Enhancements for H.323 and SIP VoIP feature enables VoIP networks to properly signal the setup and tear-down of calls when interworking with PSTN networks. These enhancements ensure that in-band tones and announcements are generated when needed so that the voice path is cut-through at the appropriate point of call setup and that early alerting (ringing) does not occur. In addition, support for network-side ISDN and the reducing of speech clipping is addressed.
The IP over a CLNS Tunnel feature lets you transport IP traffic over CLNS, for instance, on the data communications channel (DCC) of a SONET ring.
The IP over CLNS Tunnel is a virtual interface that enhances interactions with CLNS networks, allowing IP packets to be tunneled through the Connectionless Network Protocol (CLNP) to preserve TCP/IP services.
The IP over a CLNS Tunnel feature lets you transport IP traffic over CLNS, for instance, on the data communications channel (DCC) of a SONET ring.
The IP over CLNS Tunnel is a virtual interface that enhances interactions with CLNS networks, allowing IP packets to be tunneled through the Connectionless Network Protocol (CLNP) to preserve TCP/IP services.
Configuring an IP over CLNS tunnel (CTunnel) allows you to telnet to a remote router that has only CLNS connectivity. Other management facilities can also be used, such as SNMP, TFTP, and so on, which otherwise would not be available over a CLNS network.
This feature enhancement adds session initiation protocol (SIP) 183 Session Progress and Ringing messages to better map to ISND/CAS messages.
This feature requires a modem firmware upgrade to provide 2-wire leased-line support for the current Cisco analog modems (NM-8AM and NM-16AM) for enterprise customers who require point-to-point connections between locations and for enterprise customers with medium to high data transfer requirements without access to other technologies or with access to only low-grade phone lines. Loop current is required.
The Multicast Source Discovery Protocol (MSDP) MIB feature adds support in Cisco IOS software for the MSDP MIB. This MIB describes objects used for managing MSDP operations using Simple Network Management Protocol (SNMP). Documentation for this MIB exists in the form of an Internet Draft titled "Multicast Source Discovery Protocol MIB" (draft-ietf-msdp-mib-03.txt) and is available through the Internet Engineering Task Force (IETF) at http://www.ietf.org. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt5msdp.htm
During the call setup between H.323 terminals, H.225/H.245 protocols are used. The protocol messages contain embedded IP addresses and ports. If a message passes through a NAT router, it has be be decoded, translated and encoded back to the packet. This enhancement extends support to all messages in H.225/H.245 protocols and all embedded addresses.
Microsoft NetMeeting is a Windows-based application that enables multi-user interaction and collaboration from a users PC over the Internet or an intranet. Support for the NetMeeting Directory (ILS) allows connections by name from the directory built into the NetMeeting application. Destination IP addresses do not need to be known in order for a connection to be made.
Cisco IOS Network Address Translation (NAT) supports all H.225 and H.245 message types, including Fast Connect and Alerting as part of H.323 v2. Any product that makes use of these message types will be able to pass through a Cisco IOS NAT configuration without any static configuration.
Cisco IP Phones use the Selsius Skinny Station Protocol to connect with and register to the Cisco Call Manager (CCM). Messages flow back and forth that include IP address and Port information which is used to identify other IP Phone users with which a call can be placed.
To be able to deploy Cisco IOS Network Address Translation (NAT) between the IP Phone and CCM in a scalable environment, NAT needs to be able to detect the Selsius Skinny Station Protocol and understand the information passed within the messages.
When an IP Phone attempts to connect to the CCM and it matches the configured NAT translation rules, NAT will translate the original source IP address and replace it with one from the configured pool. This new address is what will be reflected in the CCM and be visible to other IP Phone users.
NBAR is a classification engine that recognizes a wide variety of applications, including web-based and other difficult-to-classify protocols that utilize dynamic TCP/UDP port assignments. When an application is recognized and classified by NBAR, a network can invoke services for that specific application. NBAR ensures that network bandwidth is used efficiently by working with QoS features to provide bandwidth guarantees and limits, traffic shaping, and packet marking.
NBAR introduces several new classification features:
NBAR can also classify static port protocols. Although Access Control Lists (ACLs) can also be used for this purpose, NBAR is easier to configure and can provide classification statistics that are not available when using ACLs.
NBAR provides a special Protocol Discovery feature that determines which application protocols are traversing a network at any given time. The Protocol Discovery feature captures key statistics associated with each protocol in a network. These statistics can be used to define traffic classes and QoS policies for each traffic class.
For additional information on NBAR, see the Network-Based Application Recognition feature module on CCO and the Documentation CD-ROM.
This feature adds online insertion and removal (OIR) support for ATM OC-3 with CES network modules on the Cisco 3660 Series.
The Network Time Protocol (NTP) is used to synchronize timekeeping among a set of distributed time servers and clients. The Cisco NTP MIB enables users to remotely monitor an NTP server using the Simple Network Management Protocol (SNMP), provided the MIB itself is implemented on that server. Use of the NTP MIB to monitor the NTP status of routing devices is accomplished using software on a Network Management System (NMS). There are no new or modified Cisco IOS software commands associated with this feature.
The Cisco implementation of the NTP MIB is based on NTP version 3 (RFC-1305). The MIB objects are all read-only. SNMP requests are processed by reading the corresponding variables from the NTP subsystem and returning them in the response. The NTP MIB defines a set of NTP server system objects, including an NTP server peers table and an NTP server filter register table. For complete details on the Cisco implementation of the NTP MIB, see the MIB file itself ("CISCO-NTP-MIB.my", available through Cisco Connection Online at http://www.cisco.com/public/mibs/v2/).
The Parser Cache feature optimizes the parsing (translation) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature was developed to improve the the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files. This improvement is especially useful for those cases in which thousands of virtual circuits must be configured for interfaces, or hundreds of access lists (ACLs) are required. The parser chain cache can rapidly recognize and translate configuration lines which differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on). Testing indicates an improvement to load time of between 30% and 36% for large configuration files when using the parser cache.
The parser cache is enabled by default on all platforms using Cisco IOS 12.1(5)T or later. A new command, [no] parser cache, allows the disabling or re-enabling of this feature.
The PIM Dense Mode State Refresh feature keeps the pruned state in PIM dense mode from timing out by periodically forwarding a control message down the source-based distribution tree. The control message refreshes the prune state on the outgoing interfaces of each router in the distribution tree.
The PPPoE Over IEEE 802.1Q VLANs feature adds support for running PPP over ethernet over IEEE 802.1 Q virtual local area networks (VLANs). IEEE 802.1Q is used to interconnect a VLAN-capable router with another VLAN-capable device. The packets on the 802.1Q link contain a standard (fast) Ethernet frame and the VLAN information associated with that frame.
This feature adds RADIUS port identification information when using point to point protocol over Ethernet (PPPoE) over ATM, Ethernet, and 802.1Q VLANs.
The Router-Port Group Management Protocol (RGMP) feature introduces a Cisco protocol that restricts IP multicast traffic in switched networks. RGMP is a Layer 2 protocol that enables a router to communicate to a switch (or a networking device that is functioning as a Layer 2 switch) the multicast group for which the router would like to receive or forward traffic.
Queueing manages congestion on a router interface or a virtual circuit (VC). In a Frame Relay environment, the congestion point may not be the interface itself, but it may be the VC because of the committed information rate (CIR). For real-time traffic (voice flows) to be transmitted in a timely manner, the data rate must not exceed the CIR or packets might be dropped causing voice quality issues. Frame Relay traffic shaping (FRTS) is configured on the interfaces to control the outbound traffic rate by preventing the router from exceeding the CIR. This means that fancy queueing such as class-based weighted fair queueing (CBWFQ), low latency queueing (LLQ), and weighted fair queueing (WFQ), can run on the VC to provide the quality of service (QoS) guarantees for the traffic.
Previously, RSVP reservations were not constrained by the CIR of the flow's outbound VC. As a result, oversubscription could occur when the sum of the RSVP traffic and other traffic exceeded the CIR.
The RSVP support for Frame Relay feature allows RSVP to work with per VC (data link connection identifier (DLCI)) queueing for voice-like flows. Traffic shaping must be enabled in a Frame Relay environment for accurate admission control of resources (bandwidth and queues) at the congestion point; that is, the VC itself. Specifically, RSVP can work with VCs defined at the interface and subinterface levels. There is no limit to the number of VCs that can be configured per interface or subinterface.
The SDLC SNRM Timer and Window Size Enhancements feature in Cisco IOS Release 12.1(5)T introduces a new window size setting for SDLC configurations, and a new timeout setting for the response to a SNRM frame.
Prior to this feature, all SDLC addresses on a serial interface had the same window count. Now the window count can be configured on a Physical Unit (PU) or SDLC address level. This enhancement allows each device attached to the serial interface to have different bandwidth based on the priority of device.
Cisco IOS software SDLC implementation currently utilizes a common response timer (T1) for all outstanding commands. To determine the minimum value for the response timer for data frames, the maximum frame size and line speed must be calculated with the formula: max framesize * 8/linespeed (bits per second). This can produce a minimum response timer that is very large.
This same timer is also used for link activation. This is a problem on a multidrop, because stations that do not respond to the SNRM will cause a delay before the next active station can be polled. This enhancement helps reduce the amount of time the SDLC network is idle.
Most protocols in the Internet assume that links are bidirectional. In particular, routing protocols used by directly connected routers no longer behave properly in the presence of a unidirectional link, such as a satellite link. The Unidirectional Link Routing feature, introduced in Cisco IOS Release 12.0(3)T, enables a router to emulate the behavior of a bidirectional link for operation of IP over unidirectional links.
The unidirectional link routing (UDLR) enhancements introduced for the Cisco 3660 series in Cisco IOS Release 12.1(5)T, include enhancements to the existing UDLR tunnel mechanism and the addition of the Internet Group Management Protocol (IGMP) proxy mechanism.
Networks that use a Cisco 3660 Multiservice Platform as a VoIP gateway can now offer uOne, or unified messaging, service to subscribers. uOne consolidates voice and e-mail services on a single IP network, allowing subscribers to send, receive, and manage messages from any access device—whether telephone or PC—regardless of message type and independent of location or time. It allows the user to access, send, forward, and reply to messages, make calls, and provision options. Calls to uOne terminate on a PC called the Gateserver, which is the unified messaging application server. This server then interfaces with a message store and a directory. uOne is based on a standards-based, open-protocol infrastructure and is highly scalable. Note that fax messaging is not supported on the Cisco 3660 at this time.
This feature implements the V.110 protocol on the digital modem network modules.
The ISDN BRI NT/TE voice interface card (VIC-2BRI-NT/TE) for the Cisco 2600 and Cisco 3600 series and the ISDN BRI Voice Module (BVM4-NT/TE) for the Cisco MC3810 enable Cisco IOS software to replicate the public switched network interface to a PBX that is compatible with European Telecommunications Standards Institute (ETSI) NET3 and QSIG switch types.
Before this feature, customers with PBXs that implement only the BRI TE interface, have had to make substantial hardware and software changes on the PBX to implement the NT interface. The implementation of an NT interface on the router allows the customer to connect ISDN PBXs and Key Systems to a multiservice network with a minimum of configuration changes on the PBX.
The VoIP Call Admission Control using RSVP feature synchronizes Resource Reservation Protocol (RSVP) procedures with H.323 Version 2 (Fast Connect) setup procedures to guarantee that the required Quality of Service (QoS) for VoIP calls is maintained across the IP network. Prior to Cisco IOS Release 12.1(3)XI, VoIP gateways used H.323 Version 1 (Slow Connect) procedures when initiating calls requiring bandwidth reservation. This feature, which is enabled by default, allows gateways to use H.323 Version 2 (Fast Connect) for all calls, including those requiring RSVP.
The following new software features are supported by the Cisco 3600 series for Cisco IOS Release 12.1(3a)T1.
The CEF Support for IP Routing between IEEE 802.1Q vLANs feature provides the support needed for a CEF feature module.
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.
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.
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.
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 PSTN or reject calls based on the network congestion. PSTN Fallback does not provide assurances that a call that 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 low latency queueing (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 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.
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.
SSH is supported on DES (56-bit) data encryption and 3DES (168-bit) data encryption software images only. In the DES software images, DES is the only encryption algorithm available. In the 3DES software images, both DES and 3DES encryption are available.
The Event MIB is an asynchronous notification mechanism standardized for use by network management systems using Simple Network Management Protocol (SNMP). The Event MIB provides the ability to monitor Management Information Base (MIB) objects on a local or remote system using SNMP and initiate simple actions whenever a trigger condition is met (for example, an SNMP trap can be generated when an object is modified). By allowing notifications based on events, the Network Management System (NMS) does not need to constantly poll managed devices to find out if something has changed. When combined with the Expression MIB support introduced in Cisco IOS Release 12.0(5)T, Event MIB support in Cisco IOS software provides a flexible and efficient way to monitor complex conditions on network devices.
T.38 Fax Relay for VoIP H.323 provides standards-based fax relay protocol support for H.323 gateways and gatekeepers. T.38 is an ITU-T recommended standard for fax relay and has been implemented on Cisco 2600, Cisco 3640, and Cisco MC3810 multiservice gateways. Since T.38 is a standards-based implementation for fax relay, Cisco gateways and gatekeepers are able to interwork with third-party H.323 devices that support T.38 protocol.
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.
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:
Session Initiation Protocol enhancements include:
Adds Feature Group D Support on Digital T1/E1 Packet Voice Trunk Network Modules.
PPP over ATM SVC implements standards-based PPP over ATM AAL5.
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 Identification MIB (CISCO-CIRCUIT-INTERFACE-MIB) provides a MIB object that 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 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.
This enhancement provides sparse table support for fastethernet subinterfaces similar to what is currently provided for frame-relay subinterfaces.
The HSRP (Hot Standby Router Protocol) Support for ICMP Redirect Messages feature enables ICMP redirects on interfaces configured with HSRP. This functionality works by filtering outgoing ICMP redirect messages through HSRP, where the next-hop IP address may be changed to an HSRP virtual IP address.
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.
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(3)T, 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 3600 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 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 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 H.323 Support for Virtual Interfaces feature allows users to configure the IP address of the gateway, so that the IP address include 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 signalling traffic, and a PVC transporting signalling 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:
Voice over ATM on Cisco 3600 series routers extends support for Voice over ATM, previously available only on the Cisco MC3810 to the Cisco 3600 series routers. Voice over ATM enables a Cisco 3600 series router to carry voice traffic (for example, telephone calls and faxes) over an ATM network.
Voice over ATM enables a Cisco 3600 to carry voice traffic, (for example, telephone calls and faxes) over an ATM network by using ATM encapsulation AAL5.
Voice over ATM on the Cisco 3600 series requires that you install one of the following modules:
The Multiport T1/E1 ATM network module with IMA supports up to 8 T1/E1 lines. For more information, see the Cisco IOS Release 12.0(5)T online document Configuring Multiport T1/E1 ATM Network Modules with Inverse Multiplexing over ATM on Cisco 2600 and 3600 Series Routers.
The OC3 ATM Network Module supports one OC3 line. For more information about the Digital T1 packet voice trunk network modules, see the Cisco IOS Release 12.0(3)T online document ATM OC-3 Network Module for the Cisco 3600 Series Routers.
Simple Gateway Control Protocol (SGCP) enables intelligent external call agents to control gateways in Voice over IP (VoIP) environments. Gateways include trunking and residential gateways. Call agents include Telecordia SM 1.5 and third-party products. This release supports SGCP Version 1.1+.
SGCP is used in large IP networks typical of competitive local exchange carriers (CLECs) and Internet exchange carriers (IXCs).
The following new software features are supported by the Cisco 3600 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 Queuing 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 queuing 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.
The PPP over Ethernet (PPPoE) on ATM feature provides the ability to connect a network of hosts over a simple bridging-access device to a remote access concentrator. With this model, each host utilizes its own PPPoE stack and the user is presented with a familiar user interface. Access control, billing and type of service can be done on a per-user, rather than a per-site, basis. Before a point-to-point connection over Ethernet can be provided, each PPP session must learn the Ethernet address of the remote peer and establish a unique session identifier. A unique session identifier is provided by the PPPoE Discovery Stage protocol.
The PPPoE on ATM feature provides service-provider digital subscriber line (DSL) support. As service providers begin DSL deployments, two of their most significant goals are to ease and facilitate consumer end adoption and to preserve as much of the dialup model as possible. PPPoE serves to advance both of these goals by leveraging ethernet scale curves and embedded base (such as ATM NICs) and by preserving the point-to-point session used by internet service providers (ISPs) in today's dialup model.
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.
The roaming feature is configured by:
The multiple roots feature allows a settlement server to use one certificate for a Secure Socket Layer (SSL) handshake and a different certificate for token signing.
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.
A defect in multiple releases of Cisco IOS software will cause a Cisco router or switch to halt and reload if the Cisco IOS HTTP service is enabled, browsing to http://router-ip/anytext?/ is attempted, and the enable password is supplied when requested. This defect can be exploited to produce a denial of service (DoS) attack.
The vulnerability, identified as Cisco bug ID CSCdr91706, affects virtually all mainstream Cisco routers and switches running Cisco IOS software releases 12.0 through 12.1, inclusive. This is not the same defect as CSCdr36952.
The vulnerability has been corrected and Cisco is making fixed releases available for free to replace all affected Cisco IOS releases. Customers are urged to upgrade to releases that are not vulnerable to this defect as shown in detail below.
This vulnerability can only be exploited if the enable password is known or not set.
You are strongly encouraged to read the complete advisory, which is available at
http://www.cisco.com/warp/public/707/ioshttpserverquery-pub.shtml
The last maintenance release of the 12.1 T release train is 12.1(5)T. The migration path for customers who need bug fixes for the 12.1 T features is the 12.2 mainline release. The 12.2 mainline release has the complete feature content of 12.1 T and will eventually reach general deployment (GD).
The last maintenance release was renamed from 12.1(4)T to 12.1(5)T to synchronize with its parent software base, the 12.1(5) mainline release, and to reflect that 12.1(5)T has all the bug fixes of the 12.1(5) mainline release. The 12.1 T release train is a superset of the 12.1 mainline release; hence any defect fixed in the 12.1 mainline is also fixed in 12.1 T. The set of features for 12.1(4)T is the same as that for 12.1(5)T. There was no change in the feature content of the release. The release was renamed so that the releases would be consistent with the Cisco release process.
This section contains important information about use of your Cisco IOS Release 12.1(5)T software.
The last maintenance release of the Cisco IOS Release 12.0T release train is 12.0(7)T. The migration path for customers needing bug fixes for Cisco IOS Release 12.0 T features is 12.1 Mainline. Cisco IOS Release 12.1 Mainline has the complete feature content of 12.0T and this release will eventually reach General Deployment (GD).
Cisco IOS Release 12.1 T begins with the same set of features as the Cisco IOS Release 12.1 mainline but will continue to add features.
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.1T, 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 you use 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. OLD-CISCO-* MIBS are currently migrated 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 9.
Table 8 Deprecated MIBs
| Deprecated MIB | Replacement |
|---|---|
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. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
For information on caveats in Cisco IOS Release 12.1(5)T, see Caveats for Cisco IOS Release , which lists severity 1 and 2 caveats, and select severity 3 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 caveats listed in this section are open in Release 12.1(3a)T1.
When initializing a Cisco router, the PRI receives the following message:
Channel State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Service State (0=Inservice 1=Maint 2=Outofservice)
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
E1 and primary-net5 will not work.
Workaround: Enter the <CmdBold>isdn service dsl<CmdArg>0<noCmdArg> b_channel <CmdArg>0<noCmdArg> state <CmdArg>0<noCmdArg><noCmdBold> interface configuration command. Though doing so clears the problem, the initial situation recurs after reloading. E1 is not accessible unless you perform this workaround or the alternative workaround (below). If you reload the router, E1 will be inaccessible again.
Alternative workaround: Perform a shut/no shut sequence of the controller. Though doing so clears the problem, the initial situation recurs after reloading.
When voice and data are both running in Frame Relay Low Latency Queuing (FR LLQ) configuration, some of the data packets are being classified as voice. This will result in police and consequent drops for the packets in the priority queue and hence cause bad voice quality. The workaround is to turn on process-switching on the incoming interfaces for voice and data.
The following caveats are specific to the Cisco 3600 Series platform:
Because of a known issue with the CES hardware, a structured T1 CES connection might not maintain synchronization across multiple timeslots for a T1 connection. Applications that require synchronous multiple timeslots (video, data) could be affected. This issue does not affect structured or unstructured E1 CES or unstructured T1 CES.
For a workaround perform the following steps:
1) remove the connect statement
4) reconfigure the connect statement
This sequence may need to be repeated.
The ATM OC-3 Network Module and OC-3/STM-1 ATM Circuit Emulation Service Network Module do not comply with ATM Forum specification 3.1. There is no workaround.
The following sections describe the documentation available for the Cisco 3600 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(5)T and are located on CCO and the Documentation CD-ROM:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
On CCO, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Caveats: Caveats for Cisco IOS Release 12.1
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS 12.1: Release Notes: Caveats: Caveats for Cisco IOS Release 12.1
|
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 documents listed below are available for the Cisco 3600 series routers and are also available on CCO and on 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 3600 Series Routers
Access Servers and Access Routers: Modular Access Routers: Cisco 3600 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. 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 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
Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 9 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
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
Table 9 Cisco IOS Software Release 12.1 Documentation Set
For service and support for a product purchased from a reseller, contact the reseller, who offers a wide variety of Cisco service and support programs described in "Service and Support" of Cisco Information Packet 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.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/technotes/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Products & Technologies: Products: Technical Tips.
The following sections are provided from the Technical Tips page:
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtm
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 TAC 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 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: Wed Apr 9 18:35:18 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.