Cisco 2650 and Cisco 2651 - Cisco IOS Release 12.2(4)MB
Available Languages
Table Of Contents
Release Notes for Cisco 2650 and Cisco 2651 Routers for Cisco IOS Release 12.2(4)MB13c
Determining the Software Version
Upgrading to a New Software Release
New Hardware Features in Cisco IOS Release 12.2(4) MB11
New Software Features in Cisco IOS Release 12.2(4) MB11
New Hardware Features in Cisco IOS Release 12.2(4) MB10
New Software Features in Cisco IOS Release 12.2(4) MB10
Multi-Layer Short Message Service Routing Feature
New Hardware Features from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a
New Software Features from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a
New Hardware Features in Cisco IOS Release 12.2(4) MB5
New Software Features in Cisco IOS Release 12.2(4) MB5
ITP M3UA/SUA Signaling Gateway
New Hardware Features in Cisco IOS Release 12.2(4) MB4
New Software Features in Cisco IOS Release 12.2(4) MB4
New Hardware and Software Features in Cisco IOS Release 12.2(4) MB3
New Hardware Features in Cisco IOS Release 12.2(4) MB2
New Software Features in Cisco IOS Release 12.2(4) MB2
New Hardware Features in Cisco IOS Release 12.2(4) MB1
New Software Features in Cisco IOS Release 12.2(4) MB1
New Hardware Features in Cisco IOS Release 12.2(1) MB1
New Software Features in Cisco IOS Release 12.2(1) MB1
Deprecated and Replacement MIBs
Modification of cs7 local-peer Command for Cisco 2600 Series Routers
Addition of squeeze Command for Cisco 2600 Series Routers
Caveats for Cisco IOS Release 12.2 MB
Open Caveats—Cisco IOS Release 12.2(4) MB13c
Resolved Caveats—Cisco IOS Release 12.2(4) MB13c
Open Caveats—Cisco IOS Release 12.2(4) MB13b
Resolved Caveats—Cisco IOS Release 12.2(4) MB13b
Caveat Advisory - Resolved Caveats Cisco IOS Release 12.2(4)MB13
Open Caveats—Cisco IOS Release 12.2(4) MB13
Resolved Caveats—Cisco IOS Release 12.2(4) MB13
Open Caveats—Cisco IOS Release 12.2(4) MB12
Resolved Caveats—Cisco IOS Release 12.2(4) MB12
Open Caveats—Cisco IOS Release 12.2(4) MB11
Resolved Caveats—Cisco IOS Release 12.2(4) MB11
Open Caveats—Cisco IOS Release 12.2(4) MB10
Resolved Caveats—Cisco IOS Release 12.2(4) MB10
Open Caveats—Cisco IOS Release 12.2(4) MB9a
Resolved Caveats—Cisco IOS Release 12.2(4) MB9a
Open Caveats—Cisco IOS Release 12.2(4) MB9
Resolved Caveats—Cisco IOS Release 12.2(4) MB9
Open Caveats—Cisco IOS Release 12.2(4) MB8
Resolved Caveats—Cisco IOS Release 12.2(4) MB8
Open Caveats—Cisco IOS Release 12.2(4) MB7
Resolved Caveats—Cisco IOS Release 12.2(4) MB7
Open Caveats—Cisco IOS Release 12.2(4) MB6
Resolved Caveats—Cisco IOS Release 12.2(4) MB6
Open Caveats—Cisco IOS Release 12.2(4) MB5
Resolved Caveats—Cisco IOS Release 12.2(4) MB5
Open Caveats—Cisco IOS Release 12.2(4) MB4
Resolved Caveats—Cisco IOS Release 12.2(4) MB4
Open Caveats—Cisco IOS Release 12.2(4) MB3
Resolved Caveats—Cisco IOS Release 12.2(4) MB3
Open Caveats—Cisco IOS Release 12.2(4)MB2
Resolved Caveats—Cisco IOS Release 12.2(4)MB2
Open Caveats—Cisco IOS Release 12.2(1)MB1
Resolved Caveats—Cisco IOS Release 12.2(1)MB1
Cisco IOS Software Documentation Set
Cisco IOS Release 12.2 Documentation Set Contents
Obtaining Technical Assistance
Release Notes for Cisco 2650 and Cisco 2651 Routers for Cisco IOS Release 12.2(4)MB13c
November 2, 2005
Cisco IOS Release 12.2(4)MB13c
OL-1865-01 Rev. N2
These release notes for Cisco 2650, Cisco 2651, Cisco 2650XM, and Cisco 2651XM series routers describe the enhancements provided in Cisco IOS Release 12.2(4)MB13c. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.2(4)MB13c, see the "Caveats for Cisco IOS Release 12.2 MB" section and Caveats for Cisco IOS Release 12.2. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.2 located on Cisco.com and the Documentation CD-ROM.
Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.
Contents
These release notes describe the following topics:
•
MIBs
•
•
Introduction
The Cisco 2650 and Cisco 2651 are part of the Cisco 2600 series modular access router family. With the Cisco 2600 series, Cisco Systems extends enterprise-class and managed services customer premise equipment (CPE) versatility, integration, and power to branch offices. The widely deployed Cisco 2600 series modular access routers are designed to enable customers to easily adopt future technologies and to scale network expansion.
The Cisco 2600 series modular architecture provides the versatility needed to adapt to changes in network technology as new services and applications become available. Driven by a powerful reduced instruction set computer (RISC) processor, the Cisco 2600 series supports the advanced quality of service (QoS), security, and network integration features required in evolving enterprise networks.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.2(4)MB13c:
•
•
Memory Recommendations
Supported Hardware
Cisco IOS Release 12.2(4)MB13c supports the following Cisco 2600 series modular access routers:
•
•
•
•
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
For additional information about supported hardware for this platform and release, refer to the Hardware/Software Compatibility Matrix at the following URL:
http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi
Determining the Software Version
To determine the version of Cisco IOS software running on a Cisco 2600 series router, log in to the router and enter the show version EXEC command:
Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 2600 Software (c2600-itp-mz), Version 12.2(4)MB13c, RELEASE SOFTWAREUpgrading to a New Software Release
For general information about upgrading to a new software release, refer to the Software Upgrade Procedure located at the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps259/products_tech_note09186a00801fc986.shtml
Feature Set Tables
Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.
Cisco IOS Release 12.2(4)MB13c supports the feature set found in the Cisco IOS Release 12.2(4)T IP image.
Caution
Table 3 lists the features and feature sets supported by the Cisco 2600 series in Cisco IOS Release 12.2(4)MB13c and uses the following conventions:
•
•
•
Note
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco 2600 series for Cisco IOS Release 12.2(4)MB13c.
New Hardware and Software Features in Cisco IOS Release 12.2(4)MB12 and Cisco IOS Release 12.2(4)MB13
No new hardware or software features are supported by the Cisco 2600 series routers for Cisco IOS Release 12.2(4)MB12 and Cisco IOS Release 12.2(4)MB13.
New Hardware Features in Cisco IOS Release 12.2(4) MB11
No new hardware features are supported in Cisco IOS Release 12.2(4) MB11.
New Software Features in Cisco IOS Release 12.2(4) MB11
ITP Packet Logging Facility
Cisco IOS Release 12.2(4)MB11 supports the ITP Packet Logging facility uses the Berkeley Standard Distribution (BSD) Syslog protocol (RFC 3164) to send selected Message Signal Units (MSUs) to a user-selected monitoring tool via the UDP connectionless protocol (RFC 768). You must select and install a monitoring tool to receive and decode messages that are sent by the ITP Packet Logging facility. We do not provide this monitoring tool.
New Hardware Features in Cisco IOS Release 12.2(4) MB10
No new hardware features are supported in Cisco IOS Release 12.2(4) MB10.
New Software Features in Cisco IOS Release 12.2(4) MB10
Multi-Layer Short Message Service Routing Feature
The IP Transfer Point (ITP) Multi-Layer Routing (MLR) feature enables intelligent routing of Short Message Service - Mobile Originated (SMS MO) messages based on the application or service from where they originated, or to which they are destined. The MLR feature can make SMS message routing decisions based on information that is found in the Transaction Capabilities Applications Part (TCAP), Mobile Application Part (MAP), and MAP-user layers.
Multiple Instances Feature
The Multiple Instance feature enables multiple variant and network indicator combinations to run concurrently on one ITP. You can configure up to 8 instances.
Instance Translation Feature
The Instance Translation feature enables the conversion of packets between instances on the ITP. Each instance is a separate domain with a defined variant, network indicator, ITP point code, optional capability point code, and optional secondary point code. Multiple Instance support is required if you configure the Instance Translation feature.
New Hardware Features from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a
No new hardware features are supported from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a.
New Software Features from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a
No new software features are supported from Cisco IOS Release 12.2(4) MB6 to Cisco IOS Release 12.2(4) MB9a, except for the following new feature introduced in Cisco IOS Release 12.2(4)MB7.
Cisco IOS Release 12.2(4)MB7
Cisco IOS Release 12.2(4)MB7 adds the following capabilities to the IP Transfer Point (ITP) product: support for Set Initialization Mode (SIM) Authentication/Authorization for Cisco WLAN Solution Architecture for laboratory and demonstration purposes. This feature is not licensed on the Cisco 2600 series platform for production environments.
New Hardware Features in Cisco IOS Release 12.2(4) MB5
No new hardware features are supported in Cisco IOS Release 12.2(4) MB5.
New Software Features in Cisco IOS Release 12.2(4) MB5
ITP M3UA/SUA Signaling Gateway
Based on open industry standards, the Cisco IP Transfer Point (ITP) product is designed for transporting Signaling System 7 (SS7) traffic over IP (SS7oIP) networks. The ITP product's design provides significant cost efficiencies and scalability enhancements over legacy SS7 networks. Using the Internet Engineering Task Force (IETF) M2PA and Stream Control Transmission Protocol (SCTP) protocols, the initial release of the ITP product provided the base functionality to off load SS7 traffic to IP. Subsequent releases provided the full functionality found in typical legacy signaling transfer point (STP) nodes, such as global title translation (GTT), gateway screening, and ISDN User Part (ISUP) transport. In addition, support for high-speed links (HSL) was added.
MTP3 User Adaptation (M3UA) and Signaling Connection Control Protocol (SCCP) User Adaptation (SUA) Signaling Gateway:
•
•
•
Refer to New Features in Release 12.2(4)MB5 for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/1224mb5 /index.htm
New Hardware Features in Cisco IOS Release 12.2(4) MB4
No new hardware features are supported in Cisco IOS Release 12.2(4) MB4.
New Software Features in Cisco IOS Release 12.2(4) MB4
MIB and Command Enhancements
The IP Transfer Point feature has been updated to include MIB and command changes. Refer to the document at the following location for information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/1224mb4 /index.htm
New Hardware and Software Features in Cisco IOS Release 12.2(4) MB3
No new hardware or software features are supported in Cisco IOS Release 12.2(4) MB3.
New Hardware Features in Cisco IOS Release 12.2(4) MB2
No new hardware features are supported in Cisco IOS Release 12.2(4) MB2.
New Software Features in Cisco IOS Release 12.2(4) MB2
The following new software enhancements have been made to the IP Transfer Point feature introduced in Cisco IOS Release 12.2(4) MB1:
•
HSL allows full bandwidth utilization of a 1.55-Mbps T1 or a 2.048-Mbps E1 for a single SS7 link. ITP HSL is compliant with both ANSI per Telcordia Technologies GR-2878-CORE and ITU per Q.2100, and includes the following protocol stack components: AAL5, SSCOP, SSCF-NNI, and MTP3b.
•
The SCCP Load Balancing enhancements include GTT address conversion, enhanced SCCP cost routing, and SCCP SLS loadsharing for Class 1 traffic.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/122mb2/index.htm
New Hardware Features in Cisco IOS Release 12.2(4) MB1
No new hardware features are supported in Cisco IOS Release 12.2(4) MB1.
New Software Features in Cisco IOS Release 12.2(4) MB1
The following new features are supported in Cisco IOS Release 12.2(4) MB1:
GTT and SCCP Support
The following new software enhancements have been made to the IP Transfer Point (ITP) feature introduced in Cisco IOS Release 12.2(1) MB1:
•
A global title is an application address, such as an 800 number, calling card number, or mobile subscriber identification number. Global Title Translation (GTT) is the process by which the SCCP translates a global title into the point code and subsystem number of the destination service switching point (SSP) where the higher-layer protocol processing occurs.
The two forms of GTT are as follows:
–
–
•
Quality of service (QoS) refers to the performance of packet flow through networks. The goal in a QoS-enabled environment is to enable predictable service delivery to certain traffic classes or types regardless of other traffic flowing through the network at any given time. ITP QoS provides the framework that allows end-to-end QoS for SS7 packet flow through SS7-over-IP (SS7oIP) networks. End-to-end QoS is the ability of the network to deliver service required by specific network traffic from one end of the network to another. In particular, QoS features ensure improved and more predictable network service by providing the following services:
–
–
–
–
–
QoS enables networks to control and predictably service a variety of network applications and traffic types. SS7 networks generally achieve QoS capabilities by over-provisioning bandwidth. Conventional SS7 networks lack the ability to identify different traffic types and provide network prioritization based on these traffic types. For instance, SS7 networks cannot separate ISUP and SCCP traffic and route this traffic over specific output links.
•
SCCP screening is a method of screening message signal units (MSUs) on inbound and outbound linksets. If the access list is inbound when the ITP receives a packet, the ITP checks the access list criteria statements for a match. If the packet is permitted, the ITP continues to process the packet. If the packet is denied, the ITP discards it.
If the access list is outbound after receiving and routing a packet to the outbound interface, the ITP checks the access list criteria statements for a match. If the packet is permitted, the ITP transmits the packet. If the packet is denied, the ITP discards it.
•
•
•
•
•
Refer to the document at the following URL for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/122_4mb1/itp20/index.htm
New Hardware Features in Cisco IOS Release 12.2(1) MB1
No new hardware features are supported in Cisco IOS Release 12.2(1) MB1.
New Software Features in Cisco IOS Release 12.2(1) MB1
The following new feature is supported in Cisco IOS Release 12.2(1) MB1:
IP Transfer Point
Cisco IP Transfer Point (ITP) is an SS7oIP software solution. ITP provides a highly reliable, cost-effective medium for migrating Signaling System 7 (SS7) and the telecommunications network signaling technology to the mobile wireless industry IP environment.
Cisco has leveraged its leadership role in the high-end switch and router industry and has created a carrier class router with a transparent SS7oIP convergence solution. The result is a seamless solution that is managed identically to other Cisco devices in large wide-area networks and leverages existing Cisco skill sets within the service provider's organization. In many cases, the provisioning, management, and tools training are already in place.
Refer to IP Transfer Point (ITP) for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/122mb1/itp.htm
MIBs
Current MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Deprecated and Replacement MIBs
Old Cisco MIBs will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBs without affecting existing Cisco IOS products or network management system (NMS) applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 4.
Important Notes
The following information applies to Cisco IOS Release 12.2(4)MB13c.
Field Notices and Bulletins
For general information about the types of documents listed in this section, refer to the following document:
http://www.cisco.com/en/US/products/hw/routers/ps259/prod_field_notices_list.html
•
•
•
•
Modification of cs7 local-peer Command for Cisco 2600 Series Routers
The cs7 local-peer command is modified in Cisco IOS Release 12.2(4)MB8 for the range of valid port numbers. The previous range was 4096 to 32761. The new range is 1024 to 49151. Refer to the documents at the following URL for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122mb/1224mb8/index.htm
Addition of squeeze Command for Cisco 2600 Series Routers
The squeeze command, which is used to erase all files marked for deletion on a Flash file system, is now available on Cisco 2600 series routers.
Caveats for Cisco IOS Release 12.2 MB
Caveats describe unexpected behavior 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.
This section contains only open and resolved caveats for the current Cisco IOS maintenance release.
All caveats in Cisco IOS Release 12.2 and Cisco IOS Release 12.2 T are also in Cisco IOS Release 12.2(4)MB13c.
For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2.
For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
Note
Open Caveats—Cisco IOS Release 12.2(4) MB13c
There are no open caveats specific to Cisco IOS Release 12.2(4) MB13c that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB13c
•
Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.
Cisco has made free software available that includes the additional integrity checks for affected customers.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml
•
Through normal software maintenance processes, Cisco is removing deprecated functionality. These changes have no impact on system operation or feature availability.
Open Caveats—Cisco IOS Release 12.2(4) MB13b
There are no open caveats specific to Cisco IOS Release 12.2(4) MB13b that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB13b
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB13b. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Cisco Internetwork Operating System (IOS) software is vulnerable to a Denial of Service (DoS) and potentially an arbitrary code execution attack from a specifically crafted IPv6 packet. The packet must be sent from a local network segment. Only devices that have been explicitly configured to process IPv6 traffic are affected. Upon successful exploitation, the device may reload or be open to further exploitation.
Cisco has made free software available to address this vulnerability for all affected customers.
More details can be found in the security advisory that is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050729-ipv6.shtml.
Caveat Advisory - Resolved Caveats Cisco IOS Release 12.2(4)MB13
•
NetFlow Feature Acceleration has been deprecated and removed from Cisco IOS. The global command ip flow-cache feature-accelerate will no longer be recognized in any IOS configuration.
If your router configuration does not currently contain the command ip flow-cache feature-accelerate, this change does not affect you.
The removal of NetFlow Feature Acceleration does not affect any other aspects of Netflow operation, for example Access-list processing. The features are separate and distinct.
Cisco Express Forwarding (CEF) supersedes the deprecated NetFlow Feature Acceleration.
Additionally, the following MIB objects and OIDs have been deprecated and removed from the netflow mib (CISCO-NETFLOW-MIB):
cnfFeatureAcceleration 1.3.6.1.4.1.9.9.99999.1.3cnfFeatureAccelerationEnable 1.3.6.1.4.1.9.9.99999.1.3.1cnfFeatureAvailableSlot 1.3.6.1.4.1.9.9.99999.1.3.2cnfFeatureActiveSlot 1.3.6.1.4.1.9.9.99999.1.3.3cnfFeatureTable 1.3.6.1.4.1.9.9.99999.1.3.4cnfFeatureEntry 1.3.6.1.4.1.9.9.99999.1.3.4.1cnfFeatureType 1.3.6.1.4.1.9.9.99999.1.3.4.1.1cnfFeatureSlot 1.3.6.1.4.1.9.9.99999.1.3.4.1.2cnfFeatureActive 1.3.6.1.4.1.9.9.99999.1.3.4.1.3cnfFeatureAttaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.4cnfFeatureDetaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.5cnfFeatureConfigChanges 1.3.6.1.4.1.9.9.99999.1.3.4.1.6Open Caveats—Cisco IOS Release 12.2(4) MB13
There are no open caveats specific to Cisco IOS Release 12.2(4) MB13 that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB13
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB13. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: When the ITP SUA Signaling Gateway is converting an extended unitdata (XUDT) with segmentation information to the connectionless data transfer (CLDT) message, the gateway does not convert the segmentation information present in the XUDT message to the corresponding SUA field in the CLDT message.
Condition: This defect only occurs when the ITP is configured for the ANSI variant.
Workaround: There is no workaround.
•
Symptom: The router (or Versatile Interface Processor (VIP) if MTP3 offload is configured) crashes during global title translation (GTT) processing.
Condition: The crash only happens when GTT is performed and the result is a GTT application group containing at least 1 member (PC or PC/SSN) in the congested state.
Workaround: Use GTT without using an Application-Group or use GTT with traffic rates that ensure no members get congested.
•
Symptom: Incorrectly formatted cSctpExtDestAddressStateChange notification occurs when SCTP association is offloaded to Versatile Interface Processor (VIP).
Conditions: This problem occurs on a Cisco 2600 or 7500 series router that is running Cisco IOS 12.2(4)MB12.
Workaround: Do not offload Signaling System 7 (SS7) links or disable notification.
Further Problem Description: Use the following commands to configure the SS7 link that is running on VIP and enable the destination address notification.
cs7 local-peer 5002 offload 3local-ip 172.18.16.26local-ip 172.18.16.250!cs7 linkset to-STP 1.1.1link 0 sctp 172.18.16.27 5002 5002!snmp-server enable traps sctp dest-address•
This DDTS integrates the security resolutions of caveats CSCdz71127 and CSCea02355 into the ITP software.
Open Caveats—Cisco IOS Release 12.2(4) MB12
There are no open caveats specific to Cisco IOS Release 12.2(4) MB12 that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB12
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB12. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Cisco routers and switches that are running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices that are running only IP version 6 (IPv6) are not affected. A workaround is available.
Cisco has made software available, free of charge, to correct the problem.
This advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
•
Cisco routers and switches that are running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices that are running only IP version 6 (IPv6) are not affected. A workaround is available.
Cisco has made software available, free of charge, to correct the problem.
This advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
•
Symptom: Traceback or system failure with mgd_timer_start in the traceback after termination of a locally multihomed SCTP association.
Conditions: Occurs on Cisco 2600 or Cisco 7500 series routers that are running Cisco IOS Release 12.2(4)MB10 or Cisco IOS 12.2(4)MB11. Termination of a locally multihomed SCTP association with at least one other active association may trigger this system failure.
Workaround: Disable local multihoming by configuring only a single IP address for local SCTP endpoints.
•
Symptom: Memory leak when cs7 link is mis-configured to incorrect variant or adjacent signalling point.
Conditions: Occurs on Cisco 2600 or Cisco 7500 series routers that are running Cisco IOS 12.2(4)MB10 or Cisco IOS 12.2(4)MB11 release of the ITP product.
Workaround: Correctly configure links.
•
Symptom: A Cisco ITP may switch over to the secondary processor if an x-listed route is removed while an operator views the route table using the show cs7 route command.
Workaround: Do not page through the route table. Setting the terminal length to zero prevents this.
•
Symptom: System failure with block overrun of the redzone using SCTP bundling over IP interfaces that have a MTU size greater than 1500 bytes.
Conditions: Occurs on Cisco 2600 or Cisco 7500 series routers that are running Cisco IOS 12.2(4)MB4-MB11. The IP interfaces with MTU sizes greater than 1500 bytes allows SCTP to bundle more than 1500 bytes into a 1500 byte buffer. Bundling more than 1500 bytes causes a memory overwrite of adjacent memory blocks, which then causes this system failure.
Workaround: On IP interfaces with MTU sizes that are greater than 1500 bytes, reduce the MTU sizes to 1500 bytes.
•
Symptom: ITP system failure when configuring a port adapter that is removed from the system or is not properly seated after OIR.
Workaround: Make sure that the port adapter is correctly seated within the Versatile Interface Processor (VIP). Do not attempt to configure hardware that is removed.
Open Caveats—Cisco IOS Release 12.2(4) MB11
No open caveats specific to Cisco IOS Release 12.2(4) MB11 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB11
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB11. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: Global title translation (GTT) MAP entries have the PC in the unavail state even though the MTP3 route table has summary routes that match the MAP entry in the avail state.
Conditions: The situation would occur whenever summary routes are used in conjunction with GTT MAP entries that match those summary routes.
Workaround: Ensure that for each GTT entry a non summary route exists.
•
Symptom: System failure can occur when link planning capacity is incorrectly configured.
Conditions: On Cisco 7500 series routers that are running Cisco IOS Release 12.2(4)MB10, the following conditions produce the problem:
–
–
–
–
The following is an example of an incorrect configuration:
conf tcs7 instance 0 linkset to-STP1link 0 sctp 10.2.3.4 10.4.5.6 5000 5000plan-capacity-send 100000The following is an example of a correct configuration:
conf tcs7 util-plan-capacityOr
conf tcs7 instance 0 linkset to-STP1link 0 sctp 10.2.3.4 10.4.5.6 5000 5000plan-capacity-send 100000plan-capacity-rcvd 100000Workaround: Always specify a send and receive planning capacity or use the global default.
•
Symptom: If an adjacent node sends the ITP an RCP (routeset cluster prohibited test) message or RCR, the ITP will not respond with a TCA or TCR. This occurs when the concerned cluster is not configured on the ITP, and there are one or more members within that cluster configured, and available or restricted on the ITP. As a result, the adjacent node will not be able to route messages for those members to the ITP.
Conditions: This happens only in ANSI networks where cluster routes are in use. It occurs when a node adjacent to the ITP has cluster routes toward the ITP, and the ITP has only member routes configured within that cluster.
Since the ITP has no cluster route configured, it would not have sent a TCP or TCR in the first place to the adjacent node. The adjacent node is not expected to spontaneously send RCP or RCR without first receiving TCP or TCR. Therefore, the likelihood of the occurrence of this caveat is tied to the behavior of the adjacent node.
Workaround: There is no workaround.
•
Symptom: show cs7 linkset command displays linksets with adjacent pc 0.0.0 that are unexpected
Conditions: When user modifies the startup_config file to include routes that reference linksets that are not listed in the startup_config file.
Workaround: Modify the startup_config file to NOT include routes that reference linksets that are not listed in the startup_config. Reload the box after modifying the startup_config.
•
Symptom: The show cs7 accounting commands when used with the point code filter display options do not show accounting data for all linksets.
Workaround: Do not use the point code filter option when displaying the accounting data or, as an alternative, use the include filter option.
•
Symptom: Under high link utilization, Signaling System 7 (SS7) links may drop because of corruption in FISU/LSSU. This problem is particularly more prevalent on the 2600.
Workaround: There is no workaround.
•
Symptom: The ITP can lose memory and the routing table will not allow changes when an adjacent destination changes status rapidly between Prohibited and Allowed or Restricted. For this to happen:
–
–
–
Workaround: There is no workaround.
•
Symptom: A Cisco Internet Transfer Point may print the following malformatted message:
%CS7MTP3-5-NONADJSIG: Received 3-4-1 message from non adjacent node OPC =The message should read as follows:
%CS7MTP3-5-NONADJSIG: Received TFP message from non adjacent node OPC = 3-4-1Workaround: There is no workaround.
•
Symptom: The following symptoms would occur if multiple instances are configured:
–
–
–
Workaround:
–
–
–
•
Symptom: ITPs that are running MB10 images are susceptible to a caveat if using ANSI cluster routing in situations in which a member of a cluster becomes restricted while the overall cluster remains available. The result of this caveat is a RSP software reload.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(4) MB10
No open caveats specific to Cisco IOS Release 12.2(4) MB10 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB10
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB10. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: The IP Transfer Point (ITP) is inserting a random signalling link selector value into non link-related Message Transfer Part Level 3 (MTP3) management messages such as TFA, TFP, TFR, and TRA.
ITU Q-704 requires such messages to be send with an SLS value of zero. However ANSI specifications do not require the use of an SLS value of zero for non link-related messages.
This causes severe interoperability problems with Lucent DNCP and Comverse SMV. Both devices discard all TFx messages send by the ITP.
Workaround: There is no workaround.
•
Symptom: If a Route-Set-Test (RST) message is received by the ITP shortly (less than two seconds) after the Transfer-Prohibited (TFP) message, then the ITP responds wrongly with a Transfer-Allowed (TFA) message.
The ITP sends broadcast Transfer-Prohibited (TFP) messages when the destination become unavailable due to a signalling link failure. A signalling point receiving such messages will start a Route-Set-Test procedure as described in Q-704. Part of that procedure is an RST message from the signalling end point to the ITP to verify the status of the affected destination.
Workaround: There is no workaround.
•
Symptom: A Cisco ITP reloads when a shutdown command is issued on an M2PA link while that link is in the process of connecting to the remote ITP. This problem is very rarely seen.
Workaround: There is no workaround.
•
Symptom: When walking the cItpRouteTable in the CISCO-ITP-RT-MIB, routes may be missing in certain configurations.
The show cs7 route detail command displays the following output:
13/14 INACC 1 itp-d UNAVAIL allowed UNAVAIL14/14 INACC 1 sp-2a UNAVAIL allowed UNAVAIL14/14 1 sp-a UNAVAIL allowed UNAVAIL15/14 INACC 1 itp-d UNAVAIL allowed UNAVAILThe following is output from an SNMP walk of the ItpRouteTable in the CISCO-ITP-RT-MIB.my Management Information Base:
system : 13 : 16383 : 1 : itp-d : 2<== sp-a should heresystem : 14 : 16383 : 1 : sp-2a : 4system : 15 : 16383 : 1 : itp-d : 2system : 15 : 16383 : 1 : stp-c : 2Conditions: On Cisco 2600 series routers that are running Cisco IOS 12.2(4)MB5 release and Cisco IOS 12.2(4)MB9 release of the ITP product.
When routes with the same priority are specified using secondary point code, the route may be skipped during a walk of the cItpRouteTable.
Workaround: Reorder the configuration statements for the involved linkset or rename them to have equal length names. You can avoid the problem by renaming the "sp-a" linkset to "sp-1a" so that the names are the same length.
•
Symptom: Concurrent transmission facility failures and SNMP polls can cause the ITP to report a linkset as available while no links in that linkset are active.
Workaround: Performing a shut and no shut of linkset or links sometimes, but not always, recovers from this situation. If this occurs, then switching over to the secondary processor or a reload is necessary.
Open Caveats—Cisco IOS Release 12.2(4) MB9a
No open caveats specific to Cisco IOS Release 12.2(4) MB9a require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB9a
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB9a. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: ITP: Linkset stuck in available without active links
Concurrent transmission facility failures and SNMP polls can cause the ITP to report a linkset as available while no links in that linkset are active.
Shut and no shut of linkset or links sometimes but not always recovers from this situation. If this occurs, then switching over to the secondary processor or a reload is necessary.
Workaround: There is no workaround.
•
Symptom: ITP: Links remain permanently in FAILED state
Under rare circumstances, a Signaling System 7 (SS7) link may get stuck in state FAILED.
Workaround: Perform a switch-over to a secondary processor or to reload the ITP.
•
Symptom: ITP sends TFx mgmt msg with wrong SLS value (ITU only)
The ITP is inserting a random signaling link selector (SLS) value into non link-related mtp3 management messages such as TFA, TFP, TFR, TRA. ITU Q-704 requires such messages to be sent with an SLS value of zero.
ANSI specifications do not require using SLS zero for non link-related messages. Doing so causes severe interoperability problems with Lucent DNCP and Comverse SMV. Both devices discard all TFx messages sent by the ITP.
Workaround: There is no workaround.
•
Symptom: TFA sent if RST is received immediately after broadcast TFP
The ITP sends broadcast Transfer-Prohibited (TFP) messages when the destination becomes unavailable due to a signaling link failure. A signaling point receiving such messages starts a Route-Set-Test (RST) procedure as described in ITU Q-704. Part of that procedure sends an RST message from the signaling end point to the ITP to verify the status of the affected destination.
If the RST message is received by the ITP shortly (less than two seconds) after the TFP then the ITP responds wrongly with a Transfer-Allowed (TFA) message.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(4) MB9
No open caveats specific to Cisco IOS Release 12.2(4) MB9 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB9
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB9. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: When a remote process outage occurs at an adjacent node for a duration less than the ITP T1 timer defined for the link to the adjacent node, the link may stay unavailable indefinitely. If this occurs, the link will remain in this state until the link is shut down and restarted. This issue will only occur when the CS7 variant is configured for ITU.
Workaround: There is no workaround.
•
On a Cisco 2600 or Cisco 7500 series router that is running Cisco IOS Release 12.2(4)MB4 or Cisco IOS Release 12.2(4)MB8 release of the ITP product, a MIB variable returns an incorrect value for the network indicator if the network indicator is not set to the default value of national.
cs7 network-indicator ?international International networknational National networkreserved Reserved for national usespare Spare (for international use only)Workaround: Ignore the index value returned from the cItpSpPointCodeNi table and use the network indicator specified on the linkset (cItpSpLinksetNi).
•
Symptom: When the first link in the second linkset of a combined linkset is activated, a changeback declaration (CBD) MSU is erroneously sent on the link being activated. The erroneous CBD is causes the adjacent node to respond with a changeback acknowledgement (CBA) MSU which is correctly ignored by the ITP. This message exchange is harmless.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(4) MB8
No open caveats specific to Cisco IOS Release 12.2(4) MB8 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB8
No resolved caveats specific to Cisco IOS Release 12.2(4) MB8 require documentation in the release notes.
Open Caveats—Cisco IOS Release 12.2(4) MB7
This section documents possible unexpected behavior by Cisco IOS Release 12.2(4)MB7 and describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Symptom: The ITP may send excessive transfer-prohibited messages to an adjacent node during an adjacent SP restart when both cluster routes and member routes exist to the same destination and use the same route.
Workaround: Remove the member routes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB7
No resolved caveats specific to Cisco IOS Release 12.2(4) MB7 require documentation in the release notes.
Open Caveats—Cisco IOS Release 12.2(4) MB6
No open caveats specific to Cisco IOS Release 12.2(4) MB6 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB6
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB6. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Under rare circumstances, it is possible for a linkset to remain unavailable, although the links in the linkset are available. This may occur if the adjacent node does not send a TRA in response to an adjacent SP restart, the ITP was not configured to disable adjacent SP restart for the adjacent node by using the no adjacent-sp-restart configuration command, and an alternate route to the adjacent node became available after the adjacent SP restart began.
Workaround: Remove the linkset definition to the adjacent node, add it back again, and then activate the linkset.
•
When low-speed links are not aligned, MTP2 LSSU messages are constantly sent from the adjacent node. These are short messages and they constantly repeat on the wire/channel. The processing of these link proving messages can drive Versatile Interface Processor (VIP) CPU up and under extreme conditions can make it difficult for the VIP to service other low-speed links. Unless there are error conditions that cause eight or more low-speed links to be in the LSSU proving state at the same time, the VIP CPU is not a concern.
Workaround: A software change allows the PA-MCX-8TE1-M to filter duplicate LSSU messages, thereby avoiding VIP CPU spikes.
•
An ambiguous error is displayed when running the clear cs7 as and clear cs7 asroute commands.
Workaround: Use the clear cs7 all command.
•
The ITP's Global Title Address Conversion feature does not translate addresses correctly when the output address prefix is null (that is, no out-address parameter was specified on the update command in global title translation (GTT) address conversion submode). The absence of an output address prefix is intended to delete the input address prefix. Instead, the GTT address is corrupted and contains the characters "DEFA" in the first four digit positions.
Workaround: Configure the translation feature in such a way that it can be accomplished with output address prefixes that are not null.
•
When ITP runs low of usable system memory, it is possible for a Signaling System 7 (SS7) route to buffer for controlled rerouting indefinitely. The symptom is that message signaling units queue towards the impacted destination will be lost, resulting in application timeouts.
Workaround: Removing and re-adding the impacted route clears the problem.
•
Upon reconfiguration of ITP, including point-code and variant, global title translation (GTT) routing failures may occur. SCCP processing of the MTP3 restart did not completely update the status of MAP entries for newly restarted links.
•
Memory leak causing router to eventually fail. Occurs when traffic arrives via M3UA to be sent out on MTP3 linksets to route that cannot be accessed. This could occur because of remote congestion or no route in the routing table.
Workaround: If the conditions described occur, upgrade the software.
•
The ITP may reload when the global title translation (GTT) configuration is deleted after ITP variant changes. The following message is displayed before the system failure:
%SYS-2-CHUNKFREE: Attempted to free nonchunk memory, chunk <address>, data <address>This may occur when GTT tables are configured and the ITP variant is changed by using the cs7 variant command. Another scenario involves deleting the ITP variant by using the no cs7 variant command and then issuing the cs7 variant command.
Workaround: Delete the GTT configuration before changing the variant or deleting the variant.
•
The clear cs7 all command does not clear ITP access violation statistics.
Workaround: These statistics can be cleared by issuing a clear cs7 accounting access-violations command.
Open Caveats—Cisco IOS Release 12.2(4) MB5
This section documents possible unexpected behavior by Cisco IOS Release 12.2(4)MB5 and describes only severity 1 and 2 caveats and select severity 3 caveats.
•
When no IP routing is entered and there are more than five links in the linkset, the links may flap.
Workaround: Leave IP routing on as the default.
Resolved Caveats—Cisco IOS Release 12.2(4) MB5
No resolved caveats specific to Cisco IOS Release 12.2(4) MB5 require documentation in the release notes.
Open Caveats—Cisco IOS Release 12.2(4) MB4
No open caveats specific to Cisco IOS Release 12.2(4) MB4 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB4
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB4. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Under very heavy load, a Cisco 2600 series router that is running ITP software may drop Signaling System 7 (SS7) links if the commands show running-config or write memory are used.
•
The ITP waits during a full MTP3 restart for response from all adjacent Signaling System 7 (SS7) nodes. If an adjacent node does not support the MTP3 restart protocol, then the ITP waits as specified in timer T23 before putting any linkset into service.
Using the "no adjacent-restart" linkset configuration also during full MTP3 restart decreases the waiting time for a full restart to finish. This also decreases the downtime after switchover between Route Switch Processors (RSPs).
•
The ITP does not provide measurements of how often mated applications have been used while performing global title translation.
•
When a QoS class becomes unavailable, SS7oIP traffic is discarded. The traffic should be reclassified as "best-effort" and use the default QoS class (class 0).
•
The cs7 inhibit and uninhibit link commands should not be allowed without entering enable mode first.
Open Caveats—Cisco IOS Release 12.2(4) MB3
No open caveats specific to Cisco IOS Release 12.2(4) MB3 require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(4) MB3
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(4) MB3. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
An error can occur with management protocol processing. Go to the following URL for further information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Open Caveats—Cisco IOS Release 12.2(4)MB2
This section documents possible unexpected behavior by Cisco IOS Release 12.2(4)MB2 and describes only severity 1 and 2 caveats and select severity 3 caveats.
•
The ITP reports a route table successfully loaded from file, even if a previous error message indicates the file could not be accessed. This happens if a filename is spelled wrong, or file access through TFTP is not possible.
Workaround: Load the route table from local Flash memory and use the correct spelling.
Resolved Caveats—Cisco IOS Release 12.2(4)MB2
No resolved caveats specific to Cisco IOS Release 12.2(4)MB2 require documentation in the release notes.
Open Caveats—Cisco IOS Release 12.2(1)MB1
This section documents possible unexpected behavior by Cisco IOS Release 12.2(4)MB2 and describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Under a very heavy load, a Cisco 2600 series router that is running ITP software may drop Signaling System 7 (SS7) links if the commands show running-config or write memory are used.
Resolved Caveats—Cisco IOS Release 12.2(1)MB1
No resolved caveats specific to Cisco IOS Release 12.2(1)MB1 require documentation in the release notes.
Related Documentation
The following sections describe the documentation available for the Cisco 2600 series. These documents consist of hardware and software installation guides, Cisco IOS configuration guides 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 Cisco.com and the Documentation CD-ROM.
Use these release notes with these documents:
•
Release-Specific Documents
•
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: Release Notes: Cross-Platform Release Notes
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Release Notes: Cross-Platform Release Notes
•
Technical Documents
•
As a supplement to the caveats listed in "Caveats for Cisco IOS Release 12.2 MB" in these release notes, see Caveats for Cisco IOS Release 12.2 and Caveats for Cisco IOS Release 12.2 T, which contain caveats applicable to all platforms for all maintenance releases of Cisco IOS Release 12.2 and Cisco IOS Release 12.2 T.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: Release Notes: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Caveats
Note
Platform-Specific Documents
These documents are available for the Cisco 2600 series on Cisco.com and the Documentation CD-ROM:
•
•
•
•
On Cisco.com at:
Technical Documents: Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 2600 Series Routers
Feature Modules
Feature modules describe new features supported by Cisco IOS Release 12.2(4)MB13c 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 Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: New Feature Documentation
Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://www.cisco.com/cgi-bin/Support/FeatureNav/FN.pl
Cisco IOS Software Documentation Set
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents. The Cisco IOS software documentation set is shipped with your order in electronic form on the Documentation CD-ROM—unless you specifically ordered the printed versions.
Documentation Modules
Each module in the Cisco IOS documentation set consists of one or more configuration guides and one or more corresponding command references. 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. Use each configuration guide with its corresponding command reference.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Configuration Guides and Command References
Cisco IOS Release 12.2 Documentation Set Contents
Table 5 lists the contents of the Cisco IOS Release 12.2 software documentation set, which is available in electronic form and in printed form if ordered.
Note
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2
Obtaining Documentation
The sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Feedback