|
|
 |
Note See Important Notes 24 for information concerning Cisco IOS Release 12.1(5)T. |
|
Note You can find the most current Cisco IOS documentation on Cisco Connection Online (CCO ). These electronic documents may contain updates and modifications made after the hardcopy documents were printed. |
These release notes for the Cisco 4000 series describe the enhancements provided in Cisco IOS Release 12.1(5)T. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.1T, see Caveats for Cisco IOS Release 12.1 T that accompanies these release notes. The caveats document is updated for every maintenance release and is located on CCO and the Documentation CD-ROM.
Use these release notes with the Cross-Platform Release Notes for Cisco IOS Release 12.1 located on CCO and the Documentation CD-ROM.
These release notes describe the following topics:
This section describes the system requirements for Release 12.1(5)T:
Table 1 lists the recommended minimum memory for the Cisco 4000 series for Cisco IOS Release12.1(5)T.
| Feature Set by Platform | Image Name | Recommended Flash Memory |
Recommended DRAM Memory |
Runs From | |
|---|---|---|---|---|---|
| Cisco 4500/4500-M, Cisco 4700/4700-M |
|||||
| Cisco 4700-M | |||||
Cisco IOS Release 12.1(5)T supports the Cisco 4000 series routers:
Table 2 lists the interfaces supported by the Cisco 4000 series.
| Interface, Network Module, or Data Rate | Platforms Supported | |
|---|---|---|
| LAN Interfaces | ||
| WAN Data Rates | ||
| WAN Interfaces and Network Modules | ||
To determine the version of Cisco IOS software running on your Cisco 4000 series router, log in to the router and use 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 at:
Technical Documents: Product Bulletins: Software: General System Software Bulletins
Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform, as listed in Table 3. Each feature set contains a specific set of Cisco IOS features.
| 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. |
 |
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. |
Table 4 and Table 5 list the features and feature sets images supported by Cisco IOS Release 12.1(5)T for the Cisco 4500, 4500-M, 4700, and 4700-M.
All tables use the following conventions to identify features:
| 1Available on the Cisco 4500 only. |
The following sections list the new hardware and software features supported by the Cisco 4000 series for Cisco IOS Release 12.1 T.
There are no new hardware features supported by the Cisco 4000 series in Cisco IOS Release 12.1(5)T.
There are no new hardware features supported by the Cisco 4000 series in Cisco IOS Release 12.1(3)T.
There are no new hardware features supported by the Cisco 4000 series in Cisco IOS Release 12.1(2)T.
The following new software features are supported by the Cisco 4000 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 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).
The DistributedDirector Enhancements for Cisco IOS Release 12.1(5)T feature sends event information to the IOS syslog.
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.
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 for MPLS VPN feature module explains how to provide MPLS VPN services that can span multiple autonomous systems (ASs) and VPN service providers. The inter-autonomous systems for MPLS VPNs feature 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.
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.
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.
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 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.1Q 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. PPPoE Radius Port Identification.
This feature adds RADIUS port identification information when using point to point protocol over Ethernet (PPPoE) over ATM, Ethernet, and 802.1Q VLANs.
The SDLC SNRM Timer and Window Size Enhancements feature introduces a new window size setting for SDLC configurations, and a new timeout setting for the SNRM frame. These enhancements change the operation of SDLC processing on a multidrop line.
Prior to this feature, all SDLC addresses on the multidrop had the same window count. Now the window count can be configured on a Physical Unit (PU) or SDLC address level. This enhancement gives a controller a different window size than other devices on the interface, and allows devices attached to the multidrop to be sized individually.
Cisco IOS software SDLC implementation currently utilizes a common response timer (T1) for all outstanding commands. Calculating the maximum frame size and line speed produces a minimum time of 3.5 seconds for receiving acknowledgments; thus, polling stations used for link activation utilize this 3.5-second timer. This is a problem on a multidrop, because stations that do not respond to the SNRM will have 3.5 seconds of downtime-waiting before the next station that is active is polled. This enhancement reduces the time to stations that are waiting idle, as opposed to those that are active.
The following new software features are supported by the Cisco 4000 series for Cisco IOS Release 12.1(3)T.
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:
The CEF Support for IP Routing between IEEE 802.1Q vLANs feature provides the support needed for a CEF feature module.
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.
PPP over ATM SVC implements standards-based PPP over ATM AAL5.
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.
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.
The Secure Shell Version 1 Integrated Client feature is an application that runs on a reliable transport layer, such as TCP/IP, and provides 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 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 will work with publicly and commercially available SSH servers. The SSH client supports DES, 3DES, and password authentication.
The HSRP (Hot Standby Router Protocol) Support for ICMP Redirect Message 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.
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 following new software features are supported by the Cisco 4000 series for Cisco IOS Release 12.1(2)T.
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 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.
Bidirectional PIM (bidir-PIM) is a variant of the Protocol Independent Multicast (PIM) suite of routing protocols for IP multicast. Bidir-PIM is derived from the mechanisms of Protocol Independent Multicast sparse mode (PIM SM) and shares many of its protocol elements. In short, bidir-PIM is PIM SM with shared tree, but no shortest path tree operations. Bidir-PIM also has unconditional forwarding of source traffic toward the RP upstream on the shared tree, but no registering process for sources as in PIM SM. These modifications are necessary and sufficient to allow forwarding of traffic in all routers solely based on the (*, G) multicast routing entries. This feature eliminates any source-specific state and allows scaling capability to an arbitrary number of sources.
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 end-to-end across the Internet will perform at the desired speed and quality.
Combined, COPS with RSVP gives network managers centralized monitoring and control of RSVP, including the ability to:
In so doing, COPS for RSVP supports the following crucial RSVP features:
You can now configure frame relay (FR) traffic shaping on switched PVCs. By applying traffic shaping to switched PVCs you enable a router to be used as a FR port concentrator in front of an FR switch. The FR switch will shape the concentrated traffic before sending it into the FR network.
The explosive growth of the Internet has placed the focus on the scalability of Interior Gateway Protocols such as OSPF. 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 sec. Some implementations have tried to improve the flooding by reducing the frequency to refresh from 30 min to around 50 min or so. 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.
There are no new hardware features supported by the Cisco 4000 series in Cisco IOS Release 12.1(1)T.
The following new software features are supported by the Cisco 4000 series for Cisco IOS Release 12.1(1)T.
Before Cisco IOS Release 12.0(7)T, if compression of TCP or Real-Time Transport Protocol (RTP) headers was enabled, compression was performed in the process switching path. That meant that packets traversing interfaces that had TCP or RTP header compression enabled were queued and passed up to the process to be switched. This procedure slowed down transmission of the packet, and therefore some users preferred to fast switch uncompressed TCP and RTP packets.
Now, if TCP or RTP header compression is enabled, it occurs by default in the fast-switched path or the Cisco Express Forwarding-switched (CEF-switched) path, depending on which switching method is enabled on the interface. Furthermore, the number of TCP and RTP header compression connections was increased to 1000 connections each.
If neither fast switching nor CEF switching is enabled, then if TCP or RTP header compression is enabled, it will occur in the process-switched path as before.
The Point-to-Point Protocol over Ethernet (PPPoE) for 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.
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. PGM has two main parts: a host element (also referred to as the transport layer of the PGM protocol) and a network element (also referred to as the network layer of the PGM protocol).
The transport layer of the PGM protocol consists of two main parts: a source part and a receiver part. The transport layer defines how multicast applications send and receive reliable, ordered, duplicate-free multicast data from multiple sources to multiple receivers. The PGM Host feature is the Cisco implementation of the transport layer of the PGM protocol.
The network layer of the PGM protocol defines how intermediate network devices (such as routers and switches) handle PGM transport data as the data flows through a network. The PGM Router Assist feature is the Cisco implementation of the network layer of the PGM protocol. Refer to the "IP Multicast" part of the Cisco IOS IP and IP Routing Configuration Guide for information about the PGM Router Assist feature.
The Service Assurance (SA) Agent is an both an enhancement to and a new name for the Response Time Reporter (RTR) feature that was introduced in Cisco IOS Release 11.2. The feature allows you to monitor network performance between a Cisco router and a remote device (which can be another Cisco router, an IP host or a mainframe host by measuring key Service Level Agreement (SLA) metrics such as response time, network resources, availability, jitter, connect time, packet loss and application performance.This feature enables you to perform troubleshooting, problem analysis, and notification based on the statistics collected by the SA Agent.
The SA Agent Enhancements feature introduces new performance measurement operations and enhancements to assist in the measurement of SLAs. With Cisco IOS Release 12.1(1)T, the SA Agent provides new capabilities that enable you to:
This section contains important information about the use of your Cisco IOS Release 12.1(5)T software.
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.
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 6.
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 about caveats in Cisco IOS Release 12.1 T, see Caveats for Cisco IOS Release 12.1 T .
All caveats in Cisco IOS Release 12.1 are also in Release 12.1 T.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats, and is located on CCO and the Documentation CD-ROM.
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on CCO at: Software Center: Cisco IOS Software: Cisco Bug Toolkit: Cisco Bugtool Navigator II or at http://www.cisco.com/support/bugtools. |
The following sections describe the documentation available for Cisco 4000 series routers. 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.
Use these release notes with these documents:
The following documents are specific to 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:
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes for Cisco IOS Release 12.1
See Caveats for Cisco IOS Release 12.1 , and Caveats for Cisco IOS Release 12.1 T , which contain caveats applicable to all platforms for all maintenance releases of Release 12.1 and Release 12.1 T.
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats: Caveats for Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS 12.1: 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. You can reach Bug Navigator II on CCO at: Software Center: Cisco IOS Software: Cisco Bug Toolkit: Cisco Bugtool Navigator II or at http://www.cisco.com/support/bugtools. |
These documents are available for the Cisco 4000 series on CCO and the Documentation CD-ROM:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 4000 Series Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 4000 Series Routers
Feature modules describe new features supported by Release 12.1(3)T and are an update 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 on CCO or the documentation CD-ROM. The feature module information is incorporated in the next printing of the Cisco IOS documentation set.
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that 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. You can use each configuration guide in conjunction 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.
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Cisco Products Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 7 describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form, and also 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 paper documents were printed. |
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
|
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. For the latest list of MIBs supported by Cisco, see Cisco Network Management Toolkit on Cisco Connection Online. From CCO, click on the following path: Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com. 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 the 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 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: Technical Assistance Center: Technical Tips. (You must have a CCO account to access this link.)
The following sections are provided from the Technical Tips page:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Thu Jan 16 12:57:51 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.