Table Of Contents
Cisco 6400 NSP - Release Notes for Cisco IOS Release 12.1(5)DB
Determining the Software Version
Upgrading to a New Software Release
New Hardware and Software Features in Cisco IOS Release 12.1(5)DB1
New Features in Release 12.1(5)DB
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—Cisco IOS Release 12.1(5)DB1
Resolved Caveats—Cisco IOS Release 12.1(5)DB1
Open Caveats—Release 12.1(5)DB
Closed and Resolved Caveats—Release 12.1(5)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(5)DB
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(5)DB1. These release notes are updated as needed.
For a list of the software caveats that apply to Release 12.1(5)DB1, 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:
•
•
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(5)DB1 and includes the following sections:
•
•
Memory Recommendations
Table 1 lists the memory recommendations for the NSP.
Table 1 Memory Recommendations for the Cisco 6400 NSP
IOS FOR NSPc6400s-wp-mz
c6400s-html.tarThe standard 64 MB DRAM memory configuration supports up to 12K virtual circuits (VCs).
128 MB DRAM is recommended for supporting up to 32K VCs, or for using ATM RMON or ATM Accounting.
128 MB DRAM is also recommended for an upgrade from an earlier release to Cisco IOS Release 12.1(5)DB.20 MB or 32 MB 1
350 MB is recommended for NRP-2 configurations
1 The 20 MB Flash Disk is no longer available; the 32 MB Flash Disk is now the default Flash configuration.
Supported Hardware
Cisco IOS Release 12.1(5)DB1 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(5)DB1 be used concurrently with Cisco IOS Release 12.1(5)DC for the Cisco 6400 node route processor (NRP). For information about Release 12.1(5)DC for the NRP, see the Release Notes for Cisco 6400 Node Route Processor (NRP) for Cisco IOS Release 12.1(5)DC.
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(5)DB, 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
Table 2 Features Supported by the Cisco 6400 NSP in Cisco IOS Release 12.1(5)DC
F4 and F5 Operation, administration, and maintenance (OAM) cell segment and end-to-end flows
12.0(4)DB
Hierarchical virtual private (VP) tunnels
12.0(4)DB
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint virtual circuits [VCs])
12.0(4)DB
Multipoint-to-point User-Network Interface (UNI) signaling
12.0(4)DB
Point-to-Point and Point-to-Multipoint VCs
12.0(4)DB
Permanent virtual circuit (PVC), Soft PVC, Soft permanent virtual path (PVP), and switched virtual circuit (SVC)
12.0(4)DB
Soft virtual channel connections (VCCs) and virtual path connections (VPCs)
12.0(4)DB
VC Merge
12.0(4)DB
VP and VC switching
12.0(4)DB
VP multiplexing
12.0(4)DB
VP tunneling
12.0(4)DB
LAN Emulation Server (LES) and LAN Emulation Configuration Server (LECS)
12.0(4)DB
RFC 1577 (Classical IP over ATM) ATM Address Resolution Protocol (ARP) server/client
12.0(4)DB
Dual leaky bucket policing (ITU-T I.371and ATM Forum UNI specifications)
12.0(4)DB
Intelligent early packet discard (EPD)
12.0(4)DB
Intelligent partial (tail) packet discard
12.0(4)DB
Multiple, weighted (dynamic) thresholds for selective packet marking and discard
12.0(4)DB
Per-VC or per-VP output queuing
12.0(4)DB
Strict priority, rate, or weighted round robin scheduling algorithms
12.0(4)DB
Available bit rate (ABR) (EFCI 1 + RR 2 ) + minimum cell rate (MCR)
12.0(4)DB
Constant bit rate (CBR)
12.0(4)DB
Per-VC or per-VP CBR traffic shaping
12.0(4)DB
Shaped CBR VP tunnels (up to 128)
12.0(4)DB
Substitution of other service categories in shaped VP tunnels
12.0(4)DB
Support for non-zero MCR on ABR connections
12.0(4)DB
Unspecified bit rate (UBR)
12.0(4)DB
UBR + MCR
12.0(4)DB
Variable bit rate-non-real time (VBR-NRT)
12.0(4)DB
VBR-real time (RT)
12.0(4)DB
ATM access lists on Interim Local Management Interface (ILMI) registration
12.0(4)DB
ATM soft restart
12.0(4)DB
PCMCIA3 Disk Mirroring
12.1(5)DB
Per-VC or per-VP nondisruptive port snooping
12.0(4)DB
1+1 Slot Redundancy (EHSA 4 )
12.0(4)DB
Network Management Ethernet (NME)
12.0(5)DB
NRP-2 support
12.1(4)DB
NSP 1+1 Redundancy
12.0(4)DB
Synchronous Optical Network (SONET) automatic protection switching (APS) support
12.0(4)DB
Stratum 3/BITS
12.0(7)DB
Telco alarms
12.0(4)DB
Dynamic Host Configuration Protocol (DHCP) client support
12.0(4)DB
Internet Protocol (IP)
12.0(4)DB
Network Time Protocol (NTP)
12.0(4)DB
Telnet
12.0(4)DB
ATM accounting enhancements
12.0(4)DB
ATM Accounting Management Information Base (MIB)
12.0(4)DB
ATM remote monitoring (RMON) MIB
12.0(4)DB
Signaling diagnostics and MIB
12.0(4)DB
Simple Network Management Protocol (SNMP)
12.0(4)DB
Web Console
12.0(4)DB
Terminal Access Controller Access Control System Plus (TACACS+) (admin login only)
12.0(4)DB
Capability to view used/unused Input Translation Table (ITT) blocks
12.1(4)DB
Fragmentation minimization
12.1(4)DB
ITT block shrinking
12.1(4)DB
ATM Network Service Access Point (NSAP) and left-justified E.164 address support
12.0(4)DB
Closed user groups (CUGs) for ATM VPNs
12.0(4)DB
E.164 address translation and autoconversion
12.0(4)DB
Hierarchical Private Network Node Interface (PNNI)
12.0(4)DB
Interim-Interswitch Signaling Protocol (IISP)
12.0(4)DB
ILMI 4.0
12.0(4)DB
VPI/VCI 5 range support in ILMI 4.0
12.0(4)DB
UNI 3.0, UNI 3.1, and UNI 4.0
12.0(4)DB
1 EFCI = Explicit Forward Congestion Indication
2 RR = relative rate
3 PCMCIA = Personal Computer Memory Card International Association
4 EHSA = Enhanced High System Availability
5 VPI/VCI = virtual path identifier/virtual channel identifier
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco 6400 NSP for Release 12.1 DB.
New Hardware and Software Features in Cisco IOS Release 12.1(5)DB1
No new hardware and software features are supported by the Cisco 6400 series for Cisco IOS Release 12.1(5)DB1.
New Features in Release 12.1(5)DB
PCMCIA Disk Mirroring
The PCMCIA disk mirroring feature enables automatic data synchronization between the PCMCIA disks of two redundant Cisco 6400 NSPs. Disk synchronization is the act of copying data from one disk to another.
The NRP-2 has no local image or file storage. The NSP stores the following NRP-2 files on the PCMCIA disk installed in disk slot 0: software images, startup configurations, ROM state information, and crash information.
Before the support of disk mirroring, NRP-2 support was not seamless after an NSP failover and could have required operator intervention to restore the NRP-2 to its state before the NSP failover. Now the NRP-2 will have continued support from the NSP, except during the relatively short NSP failover period.
PCMCIA disk mirroring is enabled by default, and disk synchronization is initiated each time one of the following events occurs:
•
•
•
•
•
–
–
–
For more information about the PCMCIA disk mirroring feature, see the PCMCIA Disk Mirroring feature module.
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:
•
•
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
Location of software images, configurations, and crash information
PCMCIA 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
ROMMON1
NRP-2 ROM state information is stored on the NSP PCMCIA disk.
NRP-1 ROM state information stored locally on NRP-1
SNMP2
Standard SNMP services
Standard SNMP services, or can use the NSP as the proxy forwarder
1 ROMMON = ROM Monitor
2 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:
•
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.•
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.•
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
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:
•
•
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)DB1.
Table 4 VP Switching Session Scalability Commands with Recommended Settings for the NSP
Setting 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(5)DB.
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.
Note
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
Open Caveats—Cisco IOS Release 12.1(5)DB1
There are no open caveats specific to Cisco IOS Release 12.1(5)DB1 that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.1(5)DB1
All the caveats listed in this section are resolved in Cisco IOS Release 12.1(5)DB1. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
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(5)DB
This section describes possibly unexpected behavior by Cisco IOS Release 12.1(5)DB. This section describes severity 1 and 2, and selected severity 3 and 4 caveats.
•
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.
•
The Interim Local Management Interface cannot be brought up on DS3 interfaces. This causes the interfaces on a Cisco 6400 NSP to stay in the User-Network Interface. If the Cisco 6400 connects to a Cisco LightStream 1010, the Private Network Node Interface will never come up.
Workaround: Configure a well-known VC manually.
•
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.
•
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.
•
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.
•
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.
•
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.
•
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.
•
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.
•
Upon NSP switchover, the Interim Local Management Interface (ILMI) will not come up on the CPU port of the newly active NSP.
Workaround: Reload both NSPs simultaneously.
•
Facility alarms from the NRP might not be correctly reported when the NSP fails over from primary to secondary.
Workaround: issue a hw-module slot x reset command, where "x" is the slot in which the NRP is installed.
•
Performing port scans on a Cisco 6400 may cause "ALIGN-3-READEXCEPTION" messages on the console. There is no workaround to prevent these messages.
If the volume of these messages is too high, the NSP might become unresponsive to the console for up to 20 seconds, as the Cisco IOS software ensures that all messages are forwarded to the serial console. During this time, you cannot Telnet or ping the router, nor make a connection through the console port. This is standard Cisco IOS software behavior during the process of forwarding messages to the serial console.
Workaround: Configure the console logging rate as limiting, or issue the no logging console command.
•
A secondary NSP might pause indefinitely during a forced failover. This problem appears to be related to the disk. There is no workaround.
•
Under stress scenarios in which a high number (>1000) of Tag Virtual Circuits (TVCs) is set up on an interface, some TVCs might not be set up successfully and the following message is printed:
%TCATM-4-RESOURCE_LIMIT: VC resource exhausted (for the interface that is used)There is no workaround.
•
In a configuration that uses the NSP as a Label Switch Router (LSR) and the NRP as a Label Edge Router (LER), if the NSP is reloaded while the NRP is up, two problems might be observed:
a.
b.
Both symptoms disappear if the NRP is reloaded subsequently. Occasionally, the NSP reload causes an unexpected reload of the NRP.
Workaround: Reload the NRPs after a NSP reload.
•
An NSP switchover might cause an NRP installed in slots 5, 6, 7, and/or 8 to reset.
Workaround: do not install NRPs in slots 5 through 8 but use other slots.
•
An NSP OC-12 interface is configured for unidirectional automatic protection switching (APS). If the working, transmit side on a Cisco 6400 is disconnected, the NSP switches over to the protect side. This is bidirectional APS behavior and is contrary to the GR-253-CORE Telcordia specification. Although there is no workaround, this is not a service-impacting issue.
•
An NSP OC12 interface is configured for unidirectional APS. If the protect side is non-functional, the user can still initiate a forced switch from the working side to the protect side. This is contrary to the GR-253-CORE Telcordia specification.
Workaround: Before initiating a forced switch from the working side, manually verify the integrity of the protect side, using the show aps command.
•
PVCs on an NSP subinterface stops passing traffic after a reload or failover.
Workaround: Delete and re-add the PVCs.
Closed and Resolved Caveats—Release 12.1(5)DB
This section describes caveats that have been closed and resolved in Cisco IOS Release 12.1(5)DB.
•
A Border Gateway Protocol (BGP) UPDATE contains Network Layer Reachability Information (NLRI) and attributes that describe the path to the destination. Each path attribute is a type, length, value (TLV) object.
The type is a two-octet field that includes the attribute flags and the type code. The fourth high-order bit (bit 3) of the attribute flags is the Extended Length bit. It defines whether the attribute length is one octet (if set to 0) or two octets (if set to 1). The extended length bit is used only if the length of the attribute value is greater than 255 octets.
The AS_PATH (type code 2) is represented by a series of TLVs (or path segments). The path segment type indicates whether the content is an AS_SET or AS_SEQUENCE. The path segment length indicates the number of autonomous systems (ASes) in the segment. The path segment value contains the list of ASes (each AS is represented by two octets).
The total length of the attribute depends on the number of path segments and the number of ASes in them. For example, if the AS_PATH contains only an AS_SEQUENCE, then the maximum number of ASes (without having to use the extended length bit) is 126 [= (255-2)/2]. If the UPDATE is propagated across an AS boundary, then the local Abstract Syntax Notation (ASN) must be appended and the extended length bit used.
The caveat was caused by the mishandling of the operation during which the length of the attribute was truncated to only one octet. Because of the internal operation of the code, the receiving border router would not be affected, but its iBGP peers would detect the mismatch and issue a NOTIFICATION message (update malformed) to reset their session.
The average maximum AS_PATH length in the Internet is between 15 and 20 ASes, so there is no need to use the extended length. The failure was discovered because of a malfunction in the BGP implementation of another vendor. There is no workaround.
This caveat was already resolved in Cisco IOS Release 12.1(4)DB.
•
Cisco IOS software contains a flaw that permits the successful prediction of TCP Initial Sequence Numbers.
This vulnerability is present in all released versions of Cisco IOS software running on Cisco routers and switches. It only affects the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device in transit between two other hosts.
To remove the vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is described in DDTS record CSCds04747.
Workarounds are available that limit or deny successful exploitation of the vulnerability by filtering traffic containing forged IP source addresses at the perimeter of a network or directly on individual devices.
This notice will be posted at http://www.cisco.com/warp/public/707/ios-tcp-isn-random-pub.shtml.
This caveat was already resolved in Cisco IOS Release 12.1(4)DB1.
•
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 an 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.
This caveat is resolved in Cisco IOS Release 12.1(5)DB.
•
Multiple Cisco IOS software and CatOS software releases contain several independent but related vulnerabilities involving the unexpected creation and exposure of SNMP community strings. These vulnerabilities can be exploited to permit the unauthorized viewing or modification of affected devices.
To remove the vulnerabilities, Cisco is offering free software upgrades for all affected platforms. The defects are documented in DDTS records CSCds32217, CSCds16384, CSCds19674, CSCdr59314, CSCdr61016, and CSCds49183.
In addition to specific workarounds for each vulnerability, affected systems can be protected by preventing SNMP access.
This notice will be posted at http://www.cisco.com/warp/public/707/ios-snmp-community-vulns-pub.shtml.
CSCdr61016 was already resolved in Cisco IOS Release 12.1(4)DB and CSCds32217 was already resolved in Cisco IOS Release 12.1(4)DB1.
•
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.
This caveat is resolved in Cisco IOS Release 12.1(5)DB.
•
A Cisco NSP might drop cells when processing traffic at full linerate on an OC-3 interface. There is no workaround.
This caveat is resolved in Cisco IOS Release 12.1(5)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.
•
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.•
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.
•
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.
•
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.•
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):
–
–
–
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:
•
•
•
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 2
Note
Note
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:
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:
•
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
•
Technical Documents
•
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
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
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
Guest
