cc/td/doc/product/software/ios113ed
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Important Notes and Caveats for Release 11.3

Important Notes and Caveats for Release 11.3

This section describes important notes and caveats related to Cisco IOS Release 11.3.

Important Notes

This section describes warnings and cautions about using the Cisco IOS Release 11.3 software. It discusses the following topics:

Upgrading to a New Software Release

If you are upgrading to Cisco IOS Release 11.3 from an earlier Cisco IOS software release, you should save your current configuration file before installing Release 11.3 software on your router.

Refer to Product Bulletin 703, Cisco IOS Software Release Upgrade Paths and Packaging Simplification for more information regarding software upgrades.

Channel Interface Processor (CIP) Microcode

CIP microcode is now available as a separate image, unbundled from the Cisco IOS image. CIP microcode (for the CIP or Second-Generation CIP [CIP2] card) resides only in router Flash memory as multiple files. The router loads a "kernel" to the CIP (based upon hardware revision), and the CIP selectively loads and relocates the software it requires from the router's Flash memory. The CIP image is available on preloaded Flash memory cards, on diskette, or via FTP from Cisco. Every version of Cisco IOS Release 11.3 has a corresponding version of CIP microcode. Refer to the Channel Interface Processor (CIP) Microcode Release Note and Microcode Upgrade Requirements publication (Document Number 78-4715-xx) for information about the recommended pairs of Cisco IOS Release 11.3 and CIP microcode.

Consider the following before using Cisco IOS Release 11.3 and CIP microcode:

When the CIP image is copied to an existing Flash memory card, the existing flash copy commands are used, just as before. If a CIP image other than the default for the release is being used, then the microcode cip flash configuration command must be issued.

The show microcode command has been expanded to display the default CIP image name for the Cisco IOS release.

Note The router must already be running Cisco IOS Release 11.3 before performing a copy of the CIP image to Flash memory because the CIP image must be "exploded" from the single image file on the TFTP server to multiple files in Flash memory. This capability was first available in Release 11.1.

There are a number of ways to determine what is loaded on each CIP:

Multiple CIP cards of different hardware revisions can run in the same router.

Cisco 7500 Series High System Availability (HSA)

To successfully use the HSA feature, you should take note of the following:

Netbooting from VIP

To netboot from Ethernet or Fast Ethernet ports on a VIP card, the system must contain version 11.1 boot ROMs. If the system contains version 11.0 boot ROMs, you can work around this requirement by using the boot bootldr device:filename global configuration command to load a bootstrap image from Flash memory.

Source-Route Bridging (SRB) over FDDI

This feature supports forwarding of source-route bridged traffic between Token Ring and FDDI interfaces on the Cisco 7000, Cisco 7010, and Cisco 7500 series routers. Previously, the only way to transport SNA and NetBIOS over FDDI was with remote source-route bridging (RSRB), which is either fast switched (direct or Fast-Sequence Transport [FST] encapsulation) or process switched (TCP encapsulation). With SRB over FDDI, traffic can be autonomously switched, greatly improving performance for SRB traffic that uses FDDI as a backbone. This feature eliminates the need for RSRB peer definitions to connect Token Ring networks over the FDDI backbone.

Note SRB over FDDI does not support RSRB traffic forwarded to RSRB peers. Routers that have connections to local Token Ring networks as well as RSRB connections to remote networks cannot use this feature. The workaround is to move the RSRB connections to routers that are not connected to the FDDI backbone.

Enabling IPX Routing

The Token Ring interface is reset whenever IPX routing is enabled on that interface.

Using AIP Cards

Cisco 7000 series ATM Interface Processor (AIP) cards that support E3, DS3, or Transport Asynchronous Transmitter/Receiver Interface (TAXI) connections and that were shipped after February 22, 1995, require Cisco IOS Release 10.0(9), 10.2(5), 10.3(1), or later.

Booting Cisco 4000 Routers

You must use the Release 9.14 rxboot image for Cisco 4000 routers because the Release 11.0 rxboot image is too large to fit in the ROMs. (Note that rxboot image size is not a problem for Cisco 4500 routers.) However, because the Release 9.14 rxboot image does not recognize new network processor modules, such as the Multiport Basic Rate Interface (MBRI), its use causes two problems:

Bad interface specification
No interface specified - IP address
Bad interface specification
No interface specified - IP address

Using LAN Emulation (LANE)

Note the following information regarding the LAN Emulation (LANE) feature in Cisco IOS Release 11.3:

Forwarding of Locally Sourced AppleTalk Packets

Our implementation of AppleTalk does not forward packets with local-source and destination network addresses. This behavior does not conform to the definition of AppleTalk in Apple Computer's Inside AppleTalk publication. However, this behavior is designed to prevent any possible corruption of the AppleTalk Address Resolution Protocol (AARP) table in any AppleTalk node that is performing MAC-address gleaning.

Using Source-Route Transparent Bridging (SRT) and Source-Route Bridging (SRB) on Cisco 2500 and Cisco 4000 Routers

Certain products containing the Texas Instruments TMS380C26 Token Ring controller do not support SRT. SRT is the concurrent operation of SRB and transparent bridging on the same interface. The affected products, shipped between March 30, 1994, and January 16, 1995, are the Cisco 4000 NP-1R, Cisco 4000 NP-2R, Cisco 2502, Cisco 2504, Cisco 2510, Cisco 2512, Cisco 2513, and Cisco 2515.

Units shipped before March 30, 1994, or after January 16, 1995, are not affected. They use the Texas Instruments TMS380C16 Token Ring controller, which supports SRT.

SRT support is necessary in two situations. In one, Token Ring networks are configured to SRB protocols such as SNA and NetBIOS, and they transparently bridge other protocols, such as IPX. In the other situation, SNA or NetBIOS uses SRB, and Windows NT is configured to use NetBIOS over IP. Certain other configuration alternatives do not require SRT (contact the Technical Assistance Center for more information).

As of Release 10.3(1), SRB in the following Cisco IOS feature sets is no longer supported: IP, IP/IPX, and Desktop. To use SRB, you need one of the following feature sets: IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN. In most non-IBM Token Ring environments, the multiring feature in IP, IP/IPX, and Desktop eliminates the need for IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN.

Cisco 7000/7500/RSPx Series

The Cisco 7000 series previously included the Cisco 7000 and Cisco 7010. These products are not supported in Cisco IOS Release 11.3. The Cisco 7000 series now includes the Cisco 7000 equipped with RSP7000 processor and the Cisco 7010 equipped with RSP7000 processor, which are supported in Cisco IOS Release 11.3. In Release 11.3, all commands supported on the Cisco 7500 series are also supported on the Cisco 7000 series.

The Cisco RSPx series includes the Cisco 7000 equipped with RSP7000 processor, the Cisco 7010 equipped with RSP7000 processor, and the Cisco 7500 series routers.

Caveats for Release 11.3(1)

This section describes possibly unexpected behavior by Release 11.3(1). Unless otherwise noted, these caveats apply to all 11.3 and 11.3 T releases up to and including 11.3(1) and 11.3(1)T. The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.3, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" at the end of this document.

Access Server

%CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry
%CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry
%CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry
The Call Management (CM) code maintains a circular buffer from which it retrieves space for its process queue entry. Under normal operating conditions, there is enough space on this buffer to accommodate CM. However, during system start-up, if start-up tests are enabled for a modem, it will behave as if it is connecting a call. This causes messages to be sent to CM. While CM will be able to recognize that no actual call is being set up, the sheer number of messages sent by 48 modems (Brasil) in parallel could result in overflows and thus cause corruptions in the buffer. The manifestation of this problem is the display of the following messages during system startup:
%CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry %CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry %CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry %CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry %CALLS_MGMT-1-CPM_Q_POOL: Cannot get memory for process watched queue entry
If you are running an image that does not have the fix for this problem (CSCdj22879), the workaround would be to disable the startup tests for the modems. This problem has been observed with Microcom modems. Amazon modems are not yet available for testing. [CSCdj22879]
To identify the problem, issue the debug serial interface and show cont t1 commands. You will see a message that txA and txB are all set to one. In normal conditions when there is no call, the values should be txA=txB=0, the same as rxA and rxB.
#show cont t1
T1 0 is up.
No alarms detected.
Version info of slot 0: HW: 1, Firmware: 13, NEAT PLD: 12, NR Bus PLD: 19
Framing is SF, Line Code is AMI, Clock Source is Line Primary.
Data in current interval (418 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 1 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Robbed bit signals state: timeslots rxA rxB txA txB
1 0 0 1 1
2 0 0 1 1
[CSCdj53511]

AppleTalk

To work around this problem, do one of the following:
- Remove autoselect and use ARAP dedicated.
- Use the ARAP 2.0.1 client instead.
- Turn on MNP10 on the ARAP 2.1 client.
- Modify the client CCL script to extend the pause to 3 seconds before exiting. [CSCdj09817]

Basic System Services

If the interface-config AV-pair has no errors, no reload occurs. [CSCdj08374]
- The router is resolving host names via an external DNS server.
- The TACACS server is down.
- The user gains access to the router via the backup "enable" method.
- The user attempts to Telnet from the router to a host on the network.
After the Telnet is initiated, the router will immediately reload.
The workaround for this problem is to not configure the ip identd command or to disable the identd process with the global command no ip identd (which is the default).
[CSCdj19961]
interface BRI0:0
ip address 7.1.1.2 255.255.255.0
x25 address 2222
x25 map ip 7.1.1.1 1111 method ietf
This should provide better recovery from corrupted packets. [CSCdj21710]
abort
crashdump
process_run_degraded_or_crash
process_ok_to_reschedule
process_suspend
process_may_suspend
doprintc
_doprnt
[CSCdj29706]
Decoded stack trace from CCO tool:
_slow_check
_etext
_check_access
_open_connection
_telnet_multiproto_open
_connect_multiproto
_connect_command
_parse_cmd
This problem has been seen only with Cisco IOS Release 11.2 and later releases. [CSCdj36356]
The following are known workarounds:
- Increase the input queue to 175. ([75]Original Queue amount + [100] per exception dump x.x.x.x command.)
- Remove the exception dump x.x.x.x command.
[CSCdj58035]
The workaround is to remove and then reenable Frame Relay traffic shaping to clear its counters. [CSCdj65742]

EXEC and Configuration Parser

IBM Connectivity

The problem is related to the way DLSw backup peers are configured. This problem will only occur if the local router is configured with backup peer commands and the remote router also has a configured peer and is not promiscuous.
The workaround is to remove the DLSw backup peer configuration. [CSCdj21664]
interface TokenRing0/0
ip address <ip-address>
multiring ip
source-bridge proxy-explorer
Note the absence of the source-bridge locRn bn remRn command.
The source-bridge proxy-explorer statement will not show up in the configuration unless the SRB triplet is configured.
A workaround for this problem is to configure the no source-bridge proxy-explorer command. [CSCdj51631]

Interfaces and Bridging

%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot x, cmd code 0
A possible workaround is to issue a microcode reload command or load a new system image and corresponding bootloader (rsp-boot-mz...) image that has the fix for this bug. [CSCdj00013]
A workaround for the second problem is to turn off CDP globally or on individual interfaces. In this case, the user can turn off CDP on the serial interface before adding or removing subinterfaces. [CSCdj07291]
To examine that, issue the show controller cbus command and check the txacc value and the txlimit. The two values should always be equal if the interface is up and no traffic is going through the interface. This problem has not been reproduced in the lab. [CSCdj22296]
During bootup when the configuration is being applied to the interfaces, the asynchronous interfaces change state and these messages are put in the logger's queue.
[CSCdj25814]
The workaround is to enable the interface to run in full duplex or DTE mode. [CSCdj36625]
Symptoms include the following message being displayed:
%CBUS-3-CATMREJCMD: ATM0/0 Teardown VC command failed (error code 0x0008)
Saving the RSM configuration and reloading its image will clear the error condition. [CSCdj41802]

IP Routing Protocols

The router can be forced to install the matching route by using the clear ip route * command. [CSCdj32471]
A workaround is to configure a loopback on the interface whose address is greater than any other address on the router. [CSCdj37962]
When enabled, SPD now works as follows:

  • When the ip spd mode aggressive command is issued, IP packets that fail sanity checks are classified as aggressive droppable packets.

  • When the IP input queue reaches SPD min-threshold (specified by ip spd queue min-threshold n), all aggressive droppable packets are dropped immediately while normal IP packets (not high-priority SPD packets) are dropped with increasing probability as the length of the IP input queue grows.

  • When the IP input queue reaches SPD max-threshold (specified by ip spd queue max-threshold n), all normal IP packets are dropped at 100 percent.

  • The default SPD min-threshold is 10 while the default max-threshold is 75.

  • To avoid an input interface that takes too many router resources, new packets (SPD or not) received from that interface are dropped when the interface has more than the input hold queue limit of input packets floating somewhere in the router. [CSCdj45202]

When the serial interface was used for incoming packets and the ATM interface for outgoing packets, there was no problem. Incoming packets on the ATM interface and outgoing packets on the serial interface also experiences this problem.
Several Cisco IOS releases were tried, with always the same effect. It appears that incoming packets are not fast switched. [CSCdj59076]

ISO CLNS

Miscellaneous

As a workaround, configure no ip route-cache on the virtual-template that is cloned on the home gateway. [CSCdi84459]
The workaround is to manually enable HSRP first and then PIM. This capability is lost if the router is reloaded because PIM is configured before HSRP. [CSCdj20961]
Packets are discarded since an incorrect address is used to encapsulate the ASP packets. The address should be picked up from the poll message rather than the first byte of the response.
Note that this fix does not apply to adt vari-poll. [CSCdj24774]
This bug addresses HSRP scalability. The workaround is to reduce the HSRP groups, and/or increase the HSRP hello and hold time. One other symptom of this bug is that interface resets go up until HSRP is stabilized. [CSCdj29595]
Network instability can cause a FDDI ring to partition or be disrupted in a manner that causes HSRP peers to not receive hellos from their neighbors and therefore become active.
HSRP routers send hello packets from a virtual MAC address, which is a function of the standby group number. When the ring heals, both routers are active and sourcing hellos from the same (virtual) MAC address.
FDDI devices must strip their frames off the ring. One method of doing this is to recognize frames by source MAC address. When the problem occurs, the FDDI PAs will mistakenly strip the other router's packets from the FDDI ring without processing them. This causes both routers to remain active since they do not hear hellos from their neighbors.
This problem can also occur when FDDI PAs are used in conjunction with other FDDI interfaces such at the FIP or 4000 series FDDI module.
Workarounds: If only one standby group is in use, the standby use-bia command can be used on both routers to cause hellos to be sourced from the burned in address instead of the virtual MAC address. This will prevent the problem.
If the problem is occurring, performing an interface reset by issuing the shut and no shut commands will return the routers to a normal state.
Increasing the HSRP hello intervals will cause the problem to occur less often since the routers will be able to tolerate a longer period of instability before missing enough hellos to go active. [CSCdj30049]
%RSP-3-ERROR: CyBus0 error 10 %RSP-3-ERROR: command/address mismatch %RSP-3-ERROR: bus command read 8bytes (0x1)
%RSP-3-ERROR: address offset (bits 3:1) 0
%RSP-3-ERROR: virtual address (bits 23:17) 000000
%RSP-3-ERROR: MEMD parity error condition
%RSP-2-QAERROR: reused or zero link error, write at addr 0100 (QA) log 22010000, data 00000000 00000000
%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF20, slot 0, cmd code 32
The configuration consists of 40 to 50 RSM VLAN interfaces.
Only creating new RSM VLAN interfaces during low traffic load conditions will prevent the defect from occurring. If the defect does occur, issuing the microcode reload command will recover the c5ip. [CSCdj59535]

Novell IPX, XNS, and Apollo Domain

This could happen if the commands ipx down and no ipx network are given in the same or reverse order, with very little time in between. [CSCdi91755]
Symptoms of this problem could be loss of network connectivity, or a slow memory leakage that occurs until the router cannot allocate any more memory and the router needs to be reloaded in order to correct this situation. [CSCdj57257]

Protocol Translation

TCP/IP Host-Mode Services

With the enable mode debug ip tcp transactions command you will see a false sequence number of 4278386749.
The current workaround is to either disable Multilink PPP or set the interface command multilink max-fragments 1. [CSCdj66824]

Wide-Area Networking

See associated caveat: CSCdi52882. [CSCdi52067]
%SCHED-2-WATCH: Attempt to enqueue uninitialized watched queue (address 0).
-Process= "<interrupt level", ipl= 1, pid= 2
This message means Frame Relay InARP packets are received before InARP input queue is initialized.
This is harmless, but the InARP input queue is initialized right away. You will not see this message except at the boot up time. Frame Relay Inverse ARP function will not be affected. [CSCdi75843]
This bug was introduced by CSCdi92810 and is largely fixed by CSCdj02528 and CSCdj03924. [CSCdj00650]
The workaround is to allow the entry to timeout or not to issue the command. [CSCdj03433]
%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = Framer background [CSCdj04848]
During normal behavior, the point-to-point subinterface should go down when the primary DLCI fails. If a secondary DLCI fails, the subinterface stays up, but traffic destined for that DLCI only will fail. [CSCdj11056]
This problem applies to Release 11.2 F and may apply to Release 11.3. No current workaround is known. [CSCdj13222]
%SYS-2-LINKED: Bad enqueue of 8F3288 in queue 9570C8
-Process= "LAPF Input", ipl= 6, pid= 36
-Traceback= EBE30 EAA88 4A73B4 4A8E10 [CSCdj29721]
The workaround is to set the timeout values the same using the lmi-t392dce parameter. [CSCdj53354]
The only workaround seems to be to delete the configuration on the router, reload it, and restore the configuration. [CSCdj61097]
There are no known workarounds at this time. [CSCdj63173]
A workaround is to configure no dialer hold-queue on the DDR interface. [CSCdj65756]

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.