Table Of Contents
Cisco 6400 NSP - Release Notes for Cisco IOS Release 12.1(4)DB2
Determining the Software Version
Upgrading to a New Software Release
No New Features in Release 12.1(4)DB2
New Features in Release 12.1(4)DB1
Input Translation Table Enhancements
No New Features in Release 12.1(3)DB
No New Features in Release 12.1(1)DB1
ATM Generic Flow Control Field
Microsoft Internet Explorer 4.x
Open Caveats—Release 12.1(4)DB2
Closed and Resolved Caveats—Release 12.1(4)DB2
Open Caveats—Release 12.1(4)DB1
Closed and Resolved Caveats—Release 12.1(4)DB1
Closed and Resolved Caveats—Release 12.1(4)DB
Preexisting NSP Hardware Caveats
Determining Your NSP Part Number and Hardware Version
Cisco IOS Software Documentation Set
Cisco IOS Release 12.1 Documentation Set Contents
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Cisco 6400 NSP - Release Notes for Cisco IOS Release 12.1(4)DB2
February 16, 2002
Note
You can find the most current Cisco IOS documentation on Cisco.com. This set of electronic documents might contain updates and modifications made after the hard-copy documents were printed.
These release notes for the Cisco 6400 node switch processor (NSP) describe the enhancements provided in Cisco IOS Release 12.1(4)DB2. These release notes are updated as needed.
For a list of the software caveats that apply to Release 12.1(4)DB2, see the "Preexisting NSP Hardware Caveats" section and Caveats for Cisco IOS Release 12.1 T. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.
Use these release notes in conjunction with the cross-platform Release Notes for Cisco IOS
Release 12.1 located on Cisco.com and the Documentation CD-ROM.Contents
These release notes describe the following topics:
•
Preexisting NSP Hardware Caveats
•
Obtaining Technical Assistance
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(4)DB2 and includes the following sections:
•
Determining the Software Version
•
Upgrading to a New Software Release
Memory Recommendations
Table 1 lists the memory recommendations for the NSP.
Supported Hardware
Cisco IOS Release 12.1(4)DB2 supports the Cisco 6400 NSP and the NSP with Stratum 3/BITS (NSP-S3B). The NSP-S3B, otherwise identical to the NSP, is required to use the Building Integrated Timing Supply (BITS) Network Clocking software feature. For detailed descriptions of the new hardware features, see the "New and Changed Information" section and the "Related Documentation" section.
Software Compatibility
Cisco recommends that Cisco IOS Release 12.1(4)DB be used concurrently with Cisco IOS Release 12.1(4)DC2 for the Cisco 6400 node route processor (NRP). For information about Release 12.1(4)DC2 for the NRP, see the Release Notes for Cisco 6400 Node Route Processor (NRP) for Cisco IOS Release 12.1(4)DC2.
Determining the Software Version
To determine the version of Cisco IOS software currently running on the Cisco 6400 NSP, log in to the NSP and enter the show version EXEC command:
Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) C6400 Software (C6400S-WP-M), Version 12.1(4)DB2, EARLY DEPLOYMENTRELEASE SOFTWARE (fc1)The output includes additional information including processor revision numbers, memory amounts, hardware IDs, and partition information.
Upgrading to a New Software Release
For information about upgrading software on the Cisco 6400 Universal Access Concentrator (UAC), including upgrading a single- or dual-NSP system to a new software release, see the software note Upgrading Software on the 6400 UAC located at http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/6400/softnote/upgradsw.htm
For general information about upgrading to a new software release, see the product bulletin Cisco IOS Upgrade Ordering Instructions located at http://www.cisco.com/warp/public/cc/cisco/mkt/ios/prodlit/957_pp.htm
If you do not have an account on Cisco.com and want general information about upgrading to a new software release, see the product bulletin Cisco IOS Software Release 11.3 Upgrade Paths and Packaging Simplification (#703: 12/97) on Cisco.com at:
Technical Documents: Product Bulletins: Software:Cisco IOS 11.3:
Cisco IOS Software Release 11.3 Upgrade Paths No. 703This product bulletin does not contain information specific to Cisco IOS Release 12.1 DB but provides generic upgrade information that may apply to Cisco IOS Release 12.1 DB.
Feature Table
The Cisco IOS software is packaged in software images. Each image contains a specific set of Cisco IOS features. Table 2 lists the features supported by the Cisco 6400 NSP image called c6400s-wp-mz in this release.
Note
This table might not be cumulative or list all the features in each image. You can find the most current Cisco IOS documentation on Cisco.com. This set of electronic documents might contain updates and modifications made after the hard-copy documents were printed. If you have a Cisco.com login account, you can find image and release information regarding features prior to Cisco IOS Release 12.1(4)DB2 by using the Feature Navigator tool at: http://www.cisco.com/go/fn.
Table 2 Features Supported by the Cisco 6400 NSP in Cisco IOS Release 12.1(4)DB2
Access lists on Interim Local Management Interface (ILMI) registration
Asynchronous Transfer Mode (ATM) access lists
ATM accounting
ATM accounting enhancements
ATM Address Resolution Protocol (ARP) client on NSP
ATM ARP server on NSP
ATM remote monitoring (RMON)
ATM soft restart
BITS External Network Clock Source
Closed user groups (CUGs)
Dual leaky bucket policing
Dynamic Host Configuration Protocol (DHCP) client support
E.164 address translation and autoconversion
Hardware redundancy
Interim-Interswitch Signaling Protocol (IISP)
ILMI version 4.0
Input Translation Table (ITT) enhancements
Internet Protocol (IP)
LANE1 client (LEC) and LANE Services (LES2 /BUS3 /LECS4 ) on NSP
Left-justified E.164 authority and format identifier (AFI) support
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint virtual circuits [VCs])
Multiple, weighted, dynamic thresholds for selective packet marking and discard
Multipoint-to-point User-Network Interface (UNI) signaling
Multiprotocol Label Switching (MPLS) Label Switch Router (LSR)
Network clocking enhancements for smooth switchover
Network Time Protocol (NTP)
Operation, administration, and maintenance (OAM) F4 and F5
Per-VC or per-VP nondisruptive snooping
Private Network Node Interface (PNNI) hierarchy
Point-to-point and point-to-multipoint permanent virtual channel connections (VCCs) and virtual path connections (VPCs)
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.0)
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)
Port snooping
Scheduler/Service Class/permanent virtual circuit (PVC) configuration
Shaped virtual private tunnels for constant bit rate (CBR) traffic
Signaling diagnostics and Management Information Base (MIB)
Simple Network Management Protocol (SNMP)
Soft VCCs and VPCs
Stratum 3 Internal Clock Accuracy
Substitution of other service categories in shaped virtual private tunnels
Support for nonzero minimum cell rate (MCR) on available bit rate (ABR) connections
Synchronous Optical Network (SONET) automatic protection switching (APS) support
Telco alarm support
Telnet
Terminal Access Controller Access Control System Plus (TACACS+)
Token Ring LANE services
Virtual path identifier/virtual channel identifier (VPI/VCI) range support in ILMI 4.0
Virtual private tunneling
Web-based configuration
1 LANE = LAN emulation
2 LES = LAN Emulation Server
3 BUS = broadcast and unknown server
4 LECS = LAN Emulation Configuration Server
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco 6400 NSP for Cisco IOS Release 12.1 DB1.
No New Features in Release 12.1(4)DB2
There are no new hardware and software features in Cisco IOS Release 12.1 DB2.
New Features in Release 12.1(4)DB1
NRP-2 Support
The NSP provides support for the second-generation node route processor (NRP-2) for the Cisco 6400 platform, which is introduced in Cisco IOS Release 12.1(4) DC.
The NSP performs the following functions for the NRP-2:
•
Switching of incoming virtual paths (VPs) to the appropriate NRP-2.
•
Controlling of configuration storage, console traffic, and network management. This provides a more manageable and integrated platform. You can use a single console port on the NSP to access the console lines of all NRP-2s in the Cisco 6400 chassis, and use a single management Ethernet interface on the NSP to monitor all NRP-2s in the system.
The NSP also supports the NRP-1, but does not perform the above-mentioned functions for the NRP-1. These functions are performed by the NRP-1 itself. Table 3 lists the functions that the NSP performs for the NRP-2 and shows how the NRP-1 performs these functions.
Table 3 NSP Support for the NRP-2 in Comparison to the NRP-1
Characteristic Supported by NSP for NRP-2 Supported by NRP-1Location of software images, configurations, and crash information
PCMCIA1 disk on NSP
NRP-1 memory (built-in or internal Flash)
Message logging
NRP-2 messages are logged on both the NSP and NRP-2. NRP-2 messages on the NSP include the NRP-2 slot number.
Messages are logged on the NRP-1 as local messages.
Console line access
Indirect external connection via the NSP. NSP contains a virtual communication server to access the NRP-2 console.
Direct external connection to NRP-1 console port or auxiliary port
ROMMON2
NRP-2 ROM state information is stored on the NSP PCMCIA disk.
NRP-1 ROM state information stored locally on NRP-1
SNMP3
Standard SNMP services
Standard SNMP services, or can use the NSP as the proxy forwarder
1 PCMCIA = Personal Computer Memory Card International Association
2 ROMMON = ROM Monitor
3 SNMP = Simple Network Management Protocol
For more information about how the NSP supports the NRP-2, see the NRP-2 feature module.
Input Translation Table Enhancements
This software feature adds three enhancements that display and alter switch behavior in managing the input translation table (ITT) resource.
The ITT is a hardware data structure used in the NSP for handling the incoming cells. It consists of entries that, for virtual circuit (VC) switching, are allocated in contiguous blocks, while each block is dedicated to a virtual path identifier (VPI) on an interface. Each entry specifies whether a virtual channel identifier (VCI) is valid within a VPI. The allocated blocks must be a power of two in sizes such as 16, 32, 64, and so on. The ITT is used only when both interfaces that the VC transits through are up.
The NSP has a single ITT, organized in two banks of 32K entries each. When a VC is created, a block of entries is allocated in the ITT for that VPI. The block size should be a power of two that is greater than or equal to the VCI value. This limits the use of large VCI values and also the distribution of VCIs on VPIs as the number of VCs approaches 32K. When an additional VC is added to a VPI that requires a larger block size than the current block, the current block is copied to a new larger block, and the original block is freed. This leaves a series of small-sized blocks that are unused. ITT memory is fragmented due to this growing technique.
In Release 12.1(4)DB1, the NSP has the following three new functions:
•
Fragmentation minimization
New configuration commands to minimize fragmentation enable the NSP to automatically determine the minimum ITT block size needed to support the PVCs configured for each interface and VPI. When an interface comes up, the minblock command specifies the ITT block size requested for a VPI on that interface.•
ITT block shrinking
By default, the ITT blocks grow as necessary to accommodate high VCI values for a given port VPI, but ITT space is not returned unless the entire ITT block is free. A new command is introduced that reduces the size of an ITT block when a VC with a high-numbered VCI is deleted.•
Capability to view used/unused ITT blocks
A command to display details of the used and unused ITT blocks is also added. This gives a picture of the quantity and quality of ITT utilization at a given time. The output of the show command allows you to view details of the free blocks by size and bank, the aggregate free space left, and the location of blocks that are in use.
Note
The new configuration commands for this feature require additional processing, which slightly reduces call setup rates and slightly increases memory usage when the modes are enabled.
For more information, see the Input Translation Table Management Enhancements feature module.
No New Features in Release 12.1(3)DB
There are no new features in Cisco IOS Release 12.1(3)DB
No New Features in Release 12.1(1)DB1
There are no new features in Cisco IOS Release 12.1(1)DB1
Important Notes
The following sections contain important information about the use of your Cisco 6400 UAC NSP.
ATM Generic Flow Control Field
When an ATM cell is received on the NSP, the generic flow control (GFC) field of the ATM cell is passed without modification to the outbound virtual circuit. This is not compliant with the ATM Forum UNI specification, version 3.1, which requires all bits of the GCF field to be reset to zero.
NSP Disk Backup
The Cisco IOS disk file system is based on the DOS ATA file system. As with DOS Windows systems, the contents of the disk might become corrupted with improper system shutdown. Make sure to back up the contents of your NSP disk to avoid data loss.
Backups can be made to a second flash disk in your primary NSP, to a flash disk in your secondary NSP, or to an off-system server (via FTP, TFTP, or RCP).
If the flash disk does become corrupted, there are two recovery options:
•
Remove the disk, install it in a laptop PC, and run chkdsk on the disk.
•
Reformat the disk in Cisco IOS and restore the data from your backup source.
NSP Disk Mirroring Feature
The NSP disk mirroring feature is not yet supported in Cisco IOS Release 12.1(4)DB2. However, a preliminary version of the feature is included in this release and you are free to experiment with the feature. If you do so, make sure to back up all disk data before doing any tests.
The following steps show you how to enable the disk mirroring feature:
Switch#
Switch#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#redundancy
Switch(config-r)#main-cpu
Switch(config-r-mc)#mirror
Switch(config-r-mc)#end
Switch#After completing the above-mentioned steps, the primary and secondary disks will automatically be synchronized. To display the sync status, use the following CLI command:
Switch#sh redundancy sync-statusTo write to disks in the mirrored fashion, use the "mirrored disk label", which is "mir-disk0:" and "mir-disk1:" respectively, as opposed to the original "disk0:" and "disk1:"—for example:
Switch#copy tftp:my_file mir-disk0:Session Scalability Commands
Table 4 lists VP switching session scalability commands with recommended settings that apply to the NSP in Cisco IOS Release 12.1(4)DB2.
Table 4 VP Switching Session Scalability Commands with Recommended Settings for the NSP
Configuration Task and Commands GuidelinesSetting the EFCI and ABR Marking Threshold:
NSP(config)# atm threshold-group number marking-threshold pct
1. Purpose
Specifies the threshold at which the per-connection queue is considered full for EFCI1 marking and ABR2 relative-rate marking.
2. Symptoms
Use when the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value) and the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit. As the queue size changes, the marking threshold changes, and the installed threshold is made as close as possible to the percent of queue-full specified.
3. Recommended Settings
To achieve a large number of sessions, Cisco recommends a setting of 80% on the NSP.
Setting the Largest per-VC Queue Limit:
NSP(config)# atm threshold-group number max-queue-limit cells
1. Purpose
Specifies the largest per-VC queue limit for a specified threshold group.
2. Symptoms
Use when the threshold group becomes congested (the cumulative number of cells on the queues of the VCs in the threshold group approaches the configured max-cells value) and the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit.
3. Recommended Settings
To achieve a large number of sessions, Cisco recommends a setting of 16,383 (that is, the value for cells) on the NSP.
Setting the Smallest per-VC Queue Limit:
NSP(config)# atm threshold-group number min-queue-limit cells
1. Purpose
Specifies the smallest per-VC queue limit for a specified threshold group.
2. Symptoms
Use when the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value) and the maximum number of cells per-queue shrinks from the threshold group max-queue-limit to the min-queue-limit.
3. Recommended Settings
To achieve a large number of sessions, Cisco recommends a setting of 1023 (that is, the value for cells) on the NSP.
1 EFCI = explicit forward congestion indication
2 ABR = Available Bit Rate
Using Verbose Debug Options
On a dual-NSP system, switchovers can occur if verbose debugging commands, such as debug all or debug oir commands, are used. To avoid this situation when using verbose debug commands, execute the redundancy keepalive disable command at the EXEC prompt prior to turning on the debug command. After debugging is disabled, enter the redundancy keepalive enable command to restore normal system operation.
Web Console Issues
The Web Console application is designed to use JavaScript, which is available with both Netscape Navigator and Microsoft Internet Explorer. However, a number of issues are present when using either application. To date, using Netscape Navigator 4.x has resulted in fewer issues than Microsoft Internet Explorer 4.x.
Before using the Web Console application, verify that your browser is set to use at least 4 MB (4096 KB) of cache memory.
The following sections tell how to deal with some of the browser issues affecting each application.
Microsoft Internet Explorer 4.x
Web Console might not reflect the most current redundancy status and autosynchronization setting because the check box and option buttons are not displayed properly. Therefore, you must verify your configuration by viewing the configuration file.
An empty dialog box might display after you apply new settings in any of the Web Console pages. If an empty dialog box is displayed, click the Internet Explorer Refresh button to view your new settings.
The show interface command on the Status page fails with Internet Explorer. There is no workaround, so this function is not available.
Netscape Navigator 4.x
If a blank window is displayed after you resize your Navigator window, click the Reload button to redisplay the page. Frequent and rapid clicking on the Web Console Status page can cause syntax and LED errors. This problem is eliminated if the browser cache is set to 4096 KB.
Software Caveats
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.
All caveats in Cisco IOS Release 12.1 and Cisco IOS Release 12.1 T are also in Cisco IOS Release 12.1(4)DB2.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1.
For information on caveats in Cisco IOS Release 12.1 T, see the Caveats for Cisco IOS Release 12.1 T, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
This section contains open caveats for the current Cisco 6400 NSP Cisco IOS release only and includes severity 1, severity 2, and select severity 3 and severity 4 caveats (severity 4 caveats are minor caveats).
Note
If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, log in to Cisco.com and click Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools.
Open Caveats—Release 12.1(4)DB2
There are no open caveats specific to Cisco IOS Release 12.1(4)DB2 that require documentation in the release notes.
Closed and Resolved Caveats—Release 12.1(4)DB2
This section describes caveats that have been closed and resolved in Cisco IOS Release 12.1(4)DB2. This section describes severity 1, 2, and select severity 3 and 4 caveats.
•
CSCdw65903
An error can occur with management protocol processing. Please use the following URL for further information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Open Caveats—Release 12.1(4)DB1
This section describes possibly unexpected behavior by Cisco IOS Release 12.1(4)DB1. This section describes severity 1, 2, and select severity 3 and 4 caveats.
•
CSCdr55905
The NRP-2 configuration is held on the NSP PCMCIA Disk. When you attempt to save the configuration on the NRP-2, the process on the NSP currently does not check for available disk space before trying to write the configuration to the disk. This might cause the file to be stored on the disk incompletely, or not at all. Generally this is not an issue, because a chassis alarm is generated when the disk space gets low.
Workaround: Check the disk space on the NSP and check any disk alarms before saving NRP-2 configurations.
•
CSCdr61244
Opening a console connection to a chassis slot that is empty or that does not contain an NRP-2 yields a traceback message such as the following:
%ALIGN-3-READEXCEPTION: Warning : read access failed at physical addrAs an example, the following situation would cause such a message to come up:
The NSP IP address is 10.1.5.4 and there is no NRP-2 in slot 4. If the user does a "telnet 10.1.5.4 2004", the traceback message above will appear on the NSP console and in the message log (if the message log is enabled). The traceback message is harmless.
Workaround: Do not attempt to open console connections to empty slots.
•
CSCdr76980
The NSP disk-format operations to the PCMCIA disk in slot 1 might affect concurrent disk operations to the disk in slot 0.
Workaround: As the disk in slot 0 is used for storing NRP-2 system configuration, the user should not perform formatting operations on disk 1 while the NRP-2 uses disk 0.
•
CSCdr83804
The NRP-2 booting and configuration operations depend on the presence of the PCMCIA disk in slot 0 of the NSP. Removal of that disk during NRP-2 disk operations, including booting and the saving of configurations, may result in an unexpected reload of the NRP-2.
Workaround: Assure that no NRP-2 disk operations are in progress before removing the PCMCIA disk from slot 0 of the NSP.
•
CSCdr88742
The NRP-2 running configuration is saved on the NSP PCMCIA disk. If that disk is not present, the configuration cannot be saved. The current NRP-2 software does not warn the user if the configuration has not been saved correctly.
Workaround: Make sure that the PCMCIA disk is present on the NSP before saving the NRP-2 running configuration.
•
CSCds02020
Resetting the NRP-2 with the hw-module slot x reset NSP command while the NRP-2 has pending console output, causes bus error warning messages to appear on the NSP console and in the NSP error log. Although there is no workaround, the messages are simply a warning and are harmless.
•
CSCds24164
After inserting an NRP-2 into the Cisco 6400 chassis, the NSP console will stall for 10 to 30 seconds. The NSP prevents user input and stalls preexisting user input in order to assure internal data consistency and to properly bring the NRP-2 card online. There is no workaround.
•
CSCds27879 and CSCds67665
If the NRP-2 is reset or loses power while the configuration is being saved to a storage medium, the configuration file might become corrupted. Attempting to restart the NRP-2 might cause the NRP-2 to reload unexpectedly.
Workaround: Do not reset the NRP-2 after issuing a command that saves the configuration file, but wait until the saving process has been completed.
If the problem occurs due to a power loss or accident, the storage medium needs to be formatted after the NRP-2 has been rebooted. Formatting the storage medium causes all data on the storage medium to be lost. If possible, before starting the formatting process, copy the data on the storage medium that needs to be formatted to another storage medium. When the formatting process has been completed, copy the data back to the storage medium that has been formatted and restore the corrupt configuration file from a backup copy.
•
CSCds51415
During a power-on condition, if an NRP-2 is in a lower-numbered slot than an NRP-1, the user might see the following message on the NRP-1 console and the NRP-1 might reboot:
platform_interface_init: PAM mailbox Config not valid yet, pausing before re-readingThe NRP-1 will then boot correctly. There is no workaround.
•
CSCds61145
When the atm snoop command is enabled on a Cisco 6400, issuing a shutdown command on the interface which has been configured with the atm snoop command might cause some cells to drop from the interface that is being snooped (that is, being monitored).
For example, if the command atm snoop is enabled on the "atm1/0/0" interface to monitor the "atm1/0/1" interface and the "atm1/0/0"interface is shutdown, some cells might be dropped from interface "atm1/0/1." There is no other workaround than to keep the snooping interface always active.
•
CSCds73398
When removing the disk from the secondary NSP, the alarm LEDs are activated on that secondary NSP. The LEDs should remain unlit. There is no workaround.
Closed and Resolved Caveats—Release 12.1(4)DB1
This section describes caveats that have been closed and resolved in Cisco IOS Release 12.1(4)DB. This section describes severity 1, 2, and select severity 3 and 4 caveats.
•
CSCds04747
Connection setup improvements.
This improvement has been included in Cisco IOS Release 12.1(4)DB1.
Closed and Resolved Caveats—Release 12.1(4)DB
This section describes caveats that have been closed and resolved in Cisco IOS Release 12.1(4)DB. This section describes severity 1, 2, and select severity 3 and 4 caveats.
•
CSCdr88996
During the NRP boot/initialization cycle, memory may be allocated to the Point-to-Point Protocol (PPP) process. This memory may be held onto for a long time, while subsequent system attempts to acquire additional memory fail resulting in messages that indicate that malloc failed.
This behavior occurs due to a lock in an internal communication path between the NRP and the NSP. Messages back up on the NRP and are never transmitted to the NSP. The response of these messages is required to free the memory held by the PPP process.
To detect the locked-up communication path, execute the show buffers command on the NRP. If the section "PAM Mbox Pak buffers" shows a value with more buffers than the maximum allowed and that value is growing, the lock condition has occurred. There is no workaround.
This caveat has been resolved in Cisco IOS Release 12.1(1)DB1.
•
CSCdr91706 and Cisco IOS HTTP Vulnerability
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 caveat 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.
This caveat has been resolved in Cisco IOS Release 12.1(4)DB.
Preexisting NSP Hardware Caveats
This section describes possible unexpected behavior by earlier hardware versions of the NSP. To determine your NSP part number (P/N) and hardware version, see the "Determining Your NSP Part Number and Hardware Version" section.
•
CSCdk47837—NRPs reset when you reload or reset a nonredundant NSP in Slot 0A.
Affected Part Number:
800-03785-03Symptom:
While the NSP is in Slot 0A of a single NSP system, the NRPs reset during NSP reloads or resets.Workaround:
In a nonredundant system using an NSP of P/N 800-03785-03, place the NSP in Slot 0B.•
CSCdk55268—After a bus error, the system does not reboot with autoboot enabled.
Affected Part Number:
800-03785-03Symptom:
The system remains at the ROMMON prompt after a crash instead of rebooting automatically.Workaround:
To prevent this problem, set the config register boot field to 0x2.If the workaround does not work, replace the NSP with P/N 800-03785-04 or higher.
•
CSCdm55885—NSPs might experience dropped cells.
A small percentage of NSPs might experience dropped cells. To determine if your NSP is affected, use the show controllers atm 0/0/0 EXEC command and check the values in the TPE column.
This field counts the number of transmit parity errors and should display all zeros for a good system. If a non-zero value is displayed in the TPE column, replace the NSP with P/N 800-03785-05 or higher.
•
CSCdm78716—NME cable consolidation feature hardware requirement.
Affected Part Numbers:
800-03785-03 (without Deviation D99-3628), 800-03785-04, 800-03785-05Symptoms:
The NSP's network management Ethernet (NME) interface might lock up and require a reset with a "shut" and "no shut" sequence or a complete board reset.The NSP might crash with a "Write Exception," "Bus Exception," or "System Reserved Exception" error message.
Because these symptoms might be caused by other problems, use the following table to determine the likelihood of this particular problem:
Workaround:
If you experience this problem, replace your NSP with P/N 800-03785-06 or higher, or with P/N 800-03785-03 with deviation sticker D99-3628 applied.•
CSCdr16154—NRP unrecognized card type.
Affected Part Numbers:
800-03785-01, 800-03785-02, 800-03785-03, 800-03785-04, 800-03785-05, 800-03785-06, 800-03785-07Symptom:
NSP reports unknown cardtype when the chassis is populated primarily with NRPs.Workaround (use one of the following):
–
Reduce the number of NRPs in the system
–
Make sure all the NRPs are P/N 800-03655-09 or higher
–
Make sure the NSP is P/N 800-03785-08 or higher.
Determining Your NSP Part Number and Hardware Version
To determine the part number and hardware version of the NSP, use one of the following methods with information from Table 5:
•
If you are holding the board, look at the 800- part number label on the back of the NSP.
•
If you can only view the faceplate of the NSP, look at the CLEI code label.
•
Enter the show hardware EXEC command to display the NSP-PC and NSP-SC part numbers and hardware versions.
The following example displays the show hardware command output for an NSP:
Switch# show hardware6400 named Switch, Date:17:51:21 UTC Thu Mar 9 2000Feature Card's FPGA Download Version:0Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP----- ------------ ---------- -- -------- --------- -------- ------- --- ---1/0 NRP 73-3082-08 F0 17827878 Feb 02 00 00-00-00 4.255 0 22/0 NRP 73-3082-08 F0 17828272 Feb 02 00 00-00-00 4.255 0 23/0 NRP 73-3082-08 F0 17800617 Feb 16 00 00-00-00 4.255 0 24/0 NRP 73-3082-08 F0 17801802 Feb 22 00 00-00-00 4.255 0 25/0 NRP 73-3082-08 F0 17828075 Feb 06 00 00-00-00 4.255 0 27/0 NRP 73-3082-08 F0 17800637 Feb 16 00 00-00-00 4.255 0 28/0 622SM NLC 73-3868-02 A0 14327690 Oct 15 99 00-00-00 1.0 0 20B/FC NSP-PC 73-2996-06 A0 15794042 Mar 05 00 00-00-00 1.1 0 2
0B/PC FC-PFQ 73-2281-04 B0 17803407 Mar 05 00 00-00-00 4.1 0 20B/PC NSP-SC 73-2997-06 A0 17826384 Mar 05 00 00-00-00 1.0 0 2
Primary NSP:Slot 0BDS1201 Backplane EEPROM:Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date------- ---- -------- ------------ -------- --- ---------- -----------C6400 2 17900239 000142C04900 128 0 0 Mar 04 2000Switch#
Note
If your show hardware output shows the NSP-PC Part No. as 73-2996-03 and the NSP-SC Part No. as 73-2997-02, you have an NSP on which the part numbers were incorrectly programmed. Use the CLEI code to determine your NSP part number. If you cannot physically see the NSP, assume you have P/N 800-03785-03.
Note
Deviation labels might not be visible. If you cannot verify that your NSP has a particular deviation, assume it does not.
Related Documentation
The following sections describe the documentation available for the Cisco 6400 universal access concentrator. 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:
•
Cisco IOS Software Documentation Set
Release-Specific Documents
The following documents are specific to Cisco IOS Release 12.1 and are located on Cisco.com and the Documentation CD-ROM:
•
Cross-Platform Release Notes
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
On the Documentation CD-ROM at:
Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
•
Product bulletins, field notices, and other release-specific documents on Cisco.com at:
Technical Documents
•
Caveats for Cisco IOS Release 12.1 and Caveats for Cisco IOS Release 12.1 T
As a supplement to the caveats listed in the "Software Caveats" section in these release notes, 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.
On Cisco.com:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Caveats
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
Note
If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, log in to Cisco.com and click Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools.
Platform-Specific Documents
The documents listed in Table 6 are available for the Cisco 6400 UAC on Cisco.com and the Documentation CD-ROM.
To access Cisco 6400 documentation on Cisco.com, follow this path:
Technical Documents: Documentation Home Page: Aggregation Solutions:
Cisco 6400 Universal Access ConcentratorTo access Cisco 6400 documentation on the Documentation CD-ROM, follow this path:
Aggregation Solutions: Cisco 6400 Universal Access Concentrator
Feature Modules
Feature modules describe new features supported by Cisco IOS Release 12.1 DB 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: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in 12.1-Based Limited Lifetime Releases: New Features in Release 12.1 DB
On the Documentation CD-ROM at:
Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation:
New Features in 12.1-Based Limited Lifetime Releases: New Features in Release 12.1 DBCisco 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 and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration:
Cisco IOS Release 12.1: Configuration Guides and Command ReferencesOn the Documentation CD-ROM at:
Cisco IOS Software Configuration: Cisco IOS Release 12.1:
Configuration Guides and Command ReferencesCisco IOS Release 12.1 Documentation Set Contents
Table 7 lists the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form, if ordered.
Note
You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed.
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration:
Cisco IOS Release 12.1On the Documentation CD-ROM at:
Cisco IOS Software Configuration: Cisco IOS Release 12.1
Note
The Cisco Management Information Base (MIB) User Quick Reference publication is no longer published. For the latest list of MIBs supported by Cisco, see Cisco Network Management Toolkit on Cisco Connection Online. From Cisco.com, click on the following path: Service & Support: Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
The most current Cisco documentation is available on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtml.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•
Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
Documentation Feedback
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-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com 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.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•
P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
•
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
![]()

