11.0(18) Caveats

This section describes possibly unexpected behavior by Release 11.0(18). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(18).

AppleTalk

• Workaround is to explicitly remove the appletalk address from the subinterface (e.g. "no app cable"). This problem is fixed in 11.2. [CSCdi52725]

Basic System Services

• A defect in the FSIP firmware causes ciscoBus buffers to be lost. When enough buffers are lost, the interface becomes unusable. This problem is fixed in FSIP Microcode Version 10.10 and later. [CSCdi39024]

• The "Tx Queue Limit" for a Cisco 7000 serial interface, as shown by the show controller cbus command, does not change to the correct value when weighted fair queueing is disabled on the interface. This does not affect packet forwarding. See also CSCdi39438. [CSCdi39026]

• The "TX queue limit" for an AGS serial interface, as shown by the show controller mci command, does not change when weighted fair queueing is disabled. This does not affect packet forwarding. See also CSCdi39438. [CSCdi39427]

• When the fair-queue interface configuration command is executed on an interface with traffic flowing through it, the router may fail. The workaround is to first shut down the interface, change queuing, and then start the interface by issuing a no shutdown command. Messages are not enqueued to an interface that is shut down. [CSCdi39556]

• If connection accounting is enabled without also enabling exec accounting, the system unexpectedly reloads when a user attempts their second connection. [CSCdi42252]

• On a Cisco 7000 series router, if you replace one interface processor (for example, a TRIP or an FSIP) with a different type of interface processor online, the show ip interface brief and show interface commands display information for both the old and new controllers. Rarely, this also results in the continual reinitialization of the newly inserted controller.

The only known workaround is to completely unconfigure the old card before replacing it with the new card. Sometimes, it might even be necessary to issue a write erase command, reboot the router, and then redefine the existing interfaces to completely remove all configuration traces of the old card. Once the information that is displayed by the show commands is self-consistent, the newly inserted card behaves normally. [CSCdi49800]

• The DHCP proxy client feature should send unicast Discover messages to the DHCP servers. [CSCdi52819]

• If you issue a boot system command to boot a Cisco 7000 router image on a Cisco 7500, the router reboots forever, reporting a "bad file magic number" each time. [CSCdi52921]

• DHCP proxy-client feature does not accept DHCP packets from the DHCP server with any DHCP option that has a length of 0. [CSCdi60953]

• When the service password-encryption command is configured in Release 11.0, all passwords are truncated to a maximum length of 11 characters. [CSCdi62344]

• CyBus errors were being displayed for an unknown reason. The error messages disappeared when the RSP and later the chassis were replaced. The arbiter may be the cause of the problem. [CSCdi66068]

• The show stacks command fails to report the correct version of code running at the time of the last reload. This problem occurs when the Flash version of the Cisco IOS software does not match the running version of code. [CSCdi74380]

• Encrypted Password bug (CSCdi75034) ------------------------------------ A bug occurs when the enable password is encrypted and is more than 11 chararacters long. When system flash is upgraded from and 11.0(8) rsp image to an 11.1(6) rsp image, and if the encrypted enable password is greater than 11 chars then the password is truncated to the first 11 chars of the original password.

Central Issue ------------- In actuality, the encrypted password is not truncated in revision 11.1(6). In fact the encrypted password was actually truncated in rsp revision 11.0(8). Bug fix CSCdi13190 was made to correct the maximum lengths of encrypted passwords. Originally the maximum length of a non encrypted password was 25 characters while an ecrypted password was restricted to 11 characters. The parser would allow the user to enter more characters but would truncate them internally at the maximum length.

What does this mean to customers upgrading from 110-8? ------------------------------------------------------ According to DDTS, the code for CSCdi13190 was checked into releases: 11.1(1.0.1) 11.1(1.0.3) 10.3(13.0.1)

If a router is running a release without this fix and the enable password is "secretpassword" (14 characters) and password encryption is enabled. Internally that ecnrypted password is truncated to "secretpassw" (11 characters) and stored this way in the config file (NVRAM). Unfortunately, at this revision the user may not understand this truncation is going on.

If the router is upgraded to a release containing bug fix CSCdi13190. When the user enters "secretpassword" as the enable password, the full 14 bytes are encrypted and compared against the config. Unfortunately the two will not match and the verification will fail with message similar to the following.

"% Bad passwords"

Only when the user explicitly enters only the first 11 characters of the password will the encrypted password match the encrypted password in NVRAM.

What about downgrading? ----------------------- The situation can be even worse when downgrading from a revision containing fix CSCdi13190 to a revision without it.

If the encrypted password is "secretpassword". The fully encrypted password is now in NVRAM. Then the rsp release is downgraded to the earlier revision.

When the user enters the password they will have an issue. At this rev only a maximum of 11 characters can be encrypted, the rest is truncated and ignored. Therefore, it will be impossible for the user to ever match the 14 character encrypted password stored in NVRAM and they will not be able to log in. [CSCdi75034]

• Fastboot was successfully implemented for the AS-5200 platform; there is now a call for full support of this feature on other platforms. Fastboot can be invoked by turning on bit 4 of the configuration register; when fully functional, the router boots directly to the IOS by skipping the loading of a boot image. The chief advantage would be to conserve memory; however, on a 7000, three minor errors have been discovered. [CSCdj54935]

EXEC and Configuration Parser

• "SETUP" mode for async does not support the new features available in version 11.0 of the IOS. [CSCdi45894]

• The setup script prompts users with bogus ip addresses and then allows him to use them. The workaound for this bug is to make sure all IP addresses are valid while using the setup script. [CSCdi87847]

• In cisco IOS, a user may not lower the level of the command "show running-config" to a level lower then 15 and give some users the abilitity to see the running config and not be able to change it. The work-around is to lower the level of "show config" and make sure the last changes were saved to NVRAM. [CSCdi90481]

• ip mtu on a dvmrp tunnel interface on a 7500 gets set to 9160 automatically. [CSCdj09584]

• The IOS contains invalid routing processes options in it's parser. The invalid options are: static, hello, conected, mobile and floating-static.

There is no operational impact due to their presence and/or use. This is a cosmetic problem. [CSCdj18849]

IBM Connectivity

• NCP V7 requires the following PTF to be applied before non-activation XID3 processing can proceed.

APAR Identifier ...... IR30678 Last Changed ........ 95/11/02 CPCP SESSION WON'T ACTIVATE AFTER TAKEOVER CONTACT.

Symptom ...... IN INCORROUT Status ........... CLOSED PER Severity ................... 4 Date Closed ......... 95/09/27 Component .......... 564806300 Duplicate of ........ Reported Release ......... 303 Fixed Release ............ 999 Component Name NCP V7 Special Notice Current Target Date ..95/11/13 Flags SCP ................... Platform ............

Status Detail: APARCLOSURE - APAR is being closed.

PE PTF List:

PTF List: Release 303 : UR44944 available 95/10/23 (F510 ) Release 732 : UR44945 available 95/10/19 (9510 )

Parent APAR: Child APAR list:

ERROR DESCRIPTION: CPCP session won't activate after takeover contact. The logic in the code comparing the ACTPU requirements in the XID(NA) to the initial XID is bad causing the XID(NA) to be rejected with a CV22. LOCAL FIX:

PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All SNA * **************************************************************** * PROBLEM DESCRIPTION: Session won't activate after takeover * * contact. XID(NA) is rejected with * * CV22. * **************************************************************** * RECOMMENDATION: Apply appropriate PTF. * **************************************************************** CPCP sessions won't activate after takeover contact. The logic in the code comparing the ACTPU requirements in the XID(NA) to the initial XID is bad causing the XID(NA) to be rejected with a CV22. The CV22 is as follows: 2203000900.

PROBLEM CONCLUSION: The incorrect logic was caused by a compiler problem. To correct the problem, the CHKCV61 routine was moved from CXDXIDV to CXDDUM1.

TEMPORARY FIX:

COMMENTS:

MODULES/MACROS: CXDDUM1 CXDXIDV SRLS: NONE

RTN CODES:

CIRCUMVENTION:

MESSAGE TO SUBMITTER: [CSCdi31041]

• During extreme heavy APPN traffic on the network, doing a harsh shut down on tokenring interfaces may cause router to crash. [CSCdi39723]

• On a Cisco 4500 router, issuing the appn link-station command followed by the no complete command may cause the router to reset unexpectedly with the message "ALIGN-1-FATAL: Corrupted program counter." [CSCdi40790]

• [CSCdi41288]

• When sdlc port and link are defined on an 4500 image, appn start will display Alignment correction error messages. [CSCdi41484]

• In cases where an EN(OLU), maybe also NN(OLU), sends a LOCATE to us, NNS(OLU), we will ignore the transmission priority set in the COS/TPF (X'2C') control vector and assign it LOW reagardless.

This can be seen when querying the APPN MIB. For exmaple, an ISR using COS #INTER will have TP of LOW vs. HIGH.

This should also be seen when multiple sessions of different COSs are passing through our node and they are each getting equal bandwidth. [CSCdi42514]

• When running APPN/DLUR, DSPU, and FRAS downstream PUs on SDLC may have lower than expected performance due to excessive segmentation on the SDLC line. A workaround is to code 'sdlc sdlc-largest-frame' on the sdlc interface. [CSCdi44102]

• When running APPN/DLUR, if a session is attempted with invalid session parameters (for example, an incorrect logmode), the USS10 message may fail to appear after the failed session, causing the terminal screen to be unusable. [CSCdi44103]

• When using APPN/DLUR, if the downstream PU served by DLUR is connected over an RSRB port, the PU will not come active and an assert message will be displayed by the dlur router. [CSCdi44481]

• When using Cisco APPN NN, the Cisco NN will not accept a link activation attempt from a migration device which sends an XID3 but does not include a CV0EF4 on the XID3. [CSCdi44482]

• Hub terminals manufactured by HOB expect a Receive Ready (RR) to be sent after the SABME is sent. This is not required by the 802.2 standard. After the HOB sends a SABME to the CIP LLC stack, the CIP LLC stack should respond with an RR and then assume that the terminal is in normal transfer mode. [CSCdi45083]

• When configuring multiple DLUS (node default primary and backup DLUS and/or link default primary and backup) and DLUR attempts an activation to a DLUS other than the node default, the show appn dlus exec command may incorrectly display DLUS information. [CSCdi45125]

• DLUR fails to account for Session Control (SC) RUs which include sense codes. The message is a warning that the code received an unexpected SC RU. [CSCdi45176]

• When using APPN/DLUR, the DLUR may retry the DLUR/DLUS connection with the DLUS at an excessive rate when the DLUS is unavailable.

Takeover and giveback of a DLUR owned PU does not function correctly. [CSCdi45263]

• We incorrectly flag RSRB port configuration errors. We detect duplicate port definitions incorrectly and we incorrectly disallow two RSRB ports with the same virtual mac address, but differing local ring numbers. [CSCdi46023]

• XID3 sent by the Cisco APPN node indicates that we support SIM/RIM, when we really don't. It also indicates that we only support TWA (two way alternate), when we really support TWS (two way simultaneous), on all media except SDLC. [CSCdi47166]

• When using APPN/DLUR on a Cisco 4500, a Cisco 4700, or on Cisco 7500 series routers, DLUR may accept only one downstream PU for dependent session activation at a time. [CSCdi47584]

• Useing APPN/DLUR, dlur may reject or hang a session which specifies an RU size greater than 4096 bytes. [CSCdi47589]

• When using APPN/DLUR, if a dependent session (non LU6.2) session is established with a maximum ru size specified in the bind which is larger than 4096 bytes, and and actual ru is received which is larger than 4096 bytes and must be segmented to fit on a link with a smaller btu than it arrived on, the session may terminate or pause indefinately. [CSCdi48050]

• The dlsw remote-peer frame-relay interface serial command does not work on a point-to-point subinterface. The workaround is to use multipoint and to do LLC mapping. [CSCdi55085]

• User was not able to query CIP LLC stats for memd waits/drops from RP console or SNMP. [CSCdi57533]

• Shut/No shut of the virtual interface can crobbed the command tables. This will cause the CIP went into a tight loop when process any CIP console command.

This fix address the above problem. [CSCdi57749]

• The RNR counter will not increment on a THEMBUSY status. The THEMBUSY is set by the secondary send us an RNR, you may see this if you catch the status at the right time. [CSCdi60197]

• This problem occurs in some versions of 11.0, and has been fixed by the commit of CSCdi67725 in 11.1. In the event that this problem is occuring in your 11.0 images, please upgrade to 11.1 GD [CSCdi76393]

• The TDU count kept by the APPN MIB, may not be correct. [CSCdi76866]

• MGDTIMER and QLLC traceback messages may cause memory leaks when using QLLC. The memory leaks may occur over a period of two to three weeks. To clear this condition, reload the router. [CSCdj07862]

• When doing source-route translation bridging from a FDDI to another FDDI, the TEST final is dropped. [CSCdj11695]

• Parser is being modified to allow sr/tlb from fddi to fddi [CSCdj11700]

• The SHOW INTERFACE ACCOUNTING command would incorrectly show NO traffic sent for RSRB SDLLC configurations,and no transmit packets/frames for STUN. STUN incorrectly shows only the receive side information. [CSCdj23788]

• On a sdllc serial line between c2504 and 3174 the performance degrade of a factor of 3 if using DTE or DCE definition on the serial interface. [CSCdj44910]

• Executing a show source command may cause the router to restart unexpectedly if a virtual ring group or remote peer is deconfigured when the source source bridge command output is waiting at the -- more -- prompt.

The workaround is do not reconfigure virtual rings or remote peers while executing a show source command. [CSCdj49973]

• In a rare timing situation, an APPN/DLUR router may reload due to a bus error/segV exception at ndr_sndtp_encap_mu. [CSCdj59639]

• When an actpu is followed by a dactpu from VTAM and there has been no response from the downstream device to either flow, after a disconnect is received from the downstream device, DLUR will send a -rsp(actpu) upstream instead if the proper flow, a +rsp(dactpu). This can cause the PU from the DLUS perspective to hang in PDACP state. [CSCdj61872]

• It is rare, but possible, for DLUS to send a -rsp(REQDACTPU). When this happens it indicates that VTAM has already cleaned up the PU in question. When receiving this response, DLUR must clean up the PU it avoid the PU from being stuck in 'stopping' state. [CSCdj61879]

• When using APPN/DLUR with a large number of LUs (over 1000), a memory spike can occur during the processing of a downstream PU outage. In extream cases, this memory spike can be large enough to exhaust memory in the APPN/DLUR router, which can cause a reload. [CSCdj61908]

• If an RSRB session is disconnected by the local LAN side at exactly the same time as a data message is received from a remote host, a situation can occur which will lead to a crash in llc_get_oqueue_status().

There is no workaround. [CSCdj62026]

• Session attempts fail with DLUR generating a sense 08060000 in a rare case where the LU name list gets corrupted. This problem is easily identified by the VTAM LU showing "active" state, while the show appn dlur-lu name display does not show the lu. [CSCdj62172]

• When source route translational bridging is used, llc sessions which are initiated from the transparent domain will result in the source route largest frame to be incorrectly set to 4472 instead of 1500. The result is that SNA and Netbios sessions may fail if the source route station sends a frame with a payload which exceeds the maximum allowable size of 1500 for ethernet media.

The problem typically occurs when Netbios is utilized to allow workstations to communicate between ethernet and token ring. It will also occur when SNA is used.

The workaround is to disable fast-switching by using the command no source-bridge transparent fastswitch or configure the end stations to use frames with a payload of less than or equal to 1500 bytes. [CSCdj62385]

• DLUR pipe seesions goes on cpsvrmg mode. This mode supports only two sessions. Under some condition, before DLUS cleans up its dlur pipe seesion, it may get request for another session from same DLUR. This time DLUS send +RSP(BIND) followed by UNBIND request. This may cause race condtion in dlur subsystem and causes DLUR FSM in hung state. [CSCdj67223]

• APPN/DLUR: In the rare case due to a protocol violation caused by another node (sending data on a lfsid that is not in use), a reload can occur in the Cisco APPN/DLUR router due to trying to look up the unallocated lfsid. [CSCdj67431]

• Any dlur installation with over 800-1000 downstream PUs can may experience a reload with the following backtrace:

[abort(0x601f2c3c)+0x8] [crashdump(0x601f0b20)+0x94] [process_handle_watchdog(0x601c2f08)+0xb4] [signal_receive(0x601b7d58)+0xa8] [process_forced_here(0x60169424)+0x68] [locate_node_index(0x607dbcc0)+0x64] [etext(0x60849e00)+0xcbee04] [CSCdj67966]

• When, i.e. due to a network error, a group of llc2 sessions got disconnected the router may under certain circumstances not clean up the llc2 control blocks properly.

The display show llc2 shows this llc2 session in state ADM, but we have no i.e. dlsw circuit associated with it.

Due to this the end system assosiated with this control block, dmac smac dsap ssap, can not reconnect the llc2 session.

Workaround is either to change one of the addresses or the saps or to reload the router. [CSCdj69274]

• APPN router may reload in rare situations with the following backtrace:

RA: 0x607E1724[find_matching_row(0x607e16ec)+0x38] RA: 0x607E1B9C[Tfind_next(0x607e1b70)+0x2c] RA: 0x6071182C[DBfind_next_directory_entry(0x60711814)+0x18] RA: 0x6070BAD8[CPdelete_men(0x6070ba90)+0x48] RA: 0x6070BA78[CPupdate_cp_status(0x6070b9c0)+0xb8] RA: 0x6070B40C[CPmain(0x6070b300)+0x10c] RA: 0x6070AC2C[newdss00(0x6070ab60)+0xcc] RA: 0x60183F80[r4k_process_dispatch(0x60183f6c)+0x14] [CSCdj70817]

• APPN leaks memory when directory services processing unknown locate replies. [CSCdj70886]

• Under certain circumstances, issuing appn ping commands may crash router. [CSCdj73921]

Interfaces and Bridging

• Autoselect ppp and slip feature is not usable without an "Async Default IP address" on the corresponding Async Interface. The system should check and warn for the lack of "Async Default IP address" when configuring Autoselct ppp or slip. [CSCdi30012]

• If a serial interface is set to loopback via a hardware signal, the interface will remain in loopback until the hardware signal is dropped and a no loopback interface configuration command is issued. [CSCdi47768]

• fixed with integration of CSCdi52904 [CSCdi47976]

• show ip local pool [poolname] does not paginate if the length of the output exceeds a single screen. [CSCdi48996]

• Issuing the ip-cache optimum command on an FDDI interface and then rebooting might add the no ip-cache optimum command to the configuration instead. [CSCdi50778]

• Version 1.6 Revision C0 EIP cards might cause cache parity errors on all Cisco 7500 series and Cisco RSP7000 systems. The cache parity errors can cause system reloads. The hardware revision and version can be determined from the show diagbus command output. This problem is resolved in RSP EIP microcode version 20.2 and higher. The microcode has been changed to alleviate the hardware problem with the "f" transceivers. The board has been revised to 1.6 D0 to replace the "f" transceivers with the "fr" part. [CSCdi52082]

• Under very rare circumstances, when using software flow control on the AUX port under heavy load, the line may end up in a hung 0 state. The output of a show line command indicates "Status: Ready, Connected, Active, Waiting for XON, Sent XOFF." If XOFF has been sent and the device is waiting for XON, issue a clear line command to recover. [CSCdi56432]

• When the user types the command "show controller tokenring ..." the values of the following 10 'since last reboot' error counters may be less than the actual counts:

Internal controller counts:

line errors: 0/1309, internal errors: 0/0 ^^^^ ^ burst errors: 0/11224, ari/fci errors: 0/0 ^^^^^ ^ abort errors: 0/0, lost frame: 0/2 ^ ^ copy errors: 0/0, rcvr congestion: 0/0 ^ ^ token errors: 0/16575, frequency errors: 0/0 ^^^^^ ^ [CSCdi62392]

• Bridged traffic is not currently payload-compressed when compression is enabled. This is due to problems caused in some instances by the combination of software bridging and payload compression. [CSCdi63268]

• Under a sudden burst of moderate load, MIP controllers cycle, taking all attached interfaces down. This behavior is sporadic (that is, it does not usually occur), and the router recovers without any user intervention within a few minutes. [CSCdi65044]

• When processing IPX (NCP) keepalive (watchdog) packets, the router adds an extra byte to the packet when SSE switching is enabled. [CSCdi66651]

• When upgrading from 10.3(8) to 11.0(8) on an AGS+, we get excessive ethernet drops when fast-switching is enabled. Drops disappear when fast-switching is disabled. [CSCdi68395]

• "show compression" does not recognize subinterfaces of a frame relay circuit. No meaningful data would show up by the command. No workaround. [CSCdi74351]

• On an RSP router, the "%CBUS-3-CTRUCHECK" error message is displayed and the Token Ring interface resets. To correct this problem, upgrade to RSP TRIP Microcode Version 20.1. [CSCdi74639]

• When enabling payload compression on a point-to-point frame-relay sub-interface with cisco encapsulation, the "show frame-relay map" command doesn't display the compression type although the compression is active according to the output of the "show compress" command. [CSCdi78274]

• LMI becomes unknown to remote DTE with 2 or more frame-relay sub-interfaces - configured with - apparently after traffic transported over the link (before traffic sent - all stable). All DLCI's under physical interface are subsequently deleted. [CSCdi81761]

• The statistics for the second bri channel in the 'show compress' output can be inaccurate. [CSCdi83087]

• Cannot ping/telnet to HSRP virtual address on FastEthernet that is multiprotocol running.

I checked 'show smf'. When 16 MAC addresses is registered on FE, I cannot ping/telnet HSRP virtual address. But HSRP replies ARP request. If I delete or disable any protocol, and the number of MAC decrease less than 16 (i.e. 15 or fewer), HSRP works fine. [CSCdi92485]

• A Cisco 7500 series router might resign its active HSRP status when configured on an FEIP, if no other router is on the segment. The workaround is to turn off HSRP. [CSCdi93012]

• The Token Ring interface comes up with output stuck messages and resets, causing sessions to be lost. This problem occurs intermittently on a number of Token Ring interfaces on a Cisco 7500. [CSCdj10797]

• When transparent bridging to a tokenring interface it is possible for the interface to read in a frame it has forwarded onto the tokenring interface. This will cause the bridge table to be incorrect.

The problem only affects the mid-range and low-end platforms. [CSCdj41666]

IP Routing Protocols

• Fast switching of multicast packets from GRE tunnels to DVMRP tunnels is non-functional on the 4000 platform. [CSCdi37850]

• IP packets sent to the Hot Standby Router Protocol (HSRP) virtual MAC address are not received if the packet is Subnetwork Access Protocol (SNAP)-encapsulated and the receiving interface is part of the ciscoBus or Switch Processor (SP) complex. [CSCdi39274]

• A router in host mode or a router trying to tftpboot an image may have problems obtaining the correct ARP MAC address entry if other routers on the network are configured with "ip proxy-arp" (the default).

In the following case, rtrA is either configured for "no ip routing" or is trying to boot a new image. In both instances, rtrA needs to obtain the correct ARP entry for the workstation located on the 171.69.214.24 subnet. Router, rtrB, is configure with "ip proxy-arp" on the 171.69.214.17 interface and it is provided with a default route.

workstation(.28) to default net | | 171.69.214.24 171.69.214.8 --------+--------- ---------+---------- |.27 |.10 +----+-----+ | +----+----+ | |.18 | .17| | | rtrA +-------+---------+ rtrB | | | | | | +----------+ | +---------+ 171.69.214.16

When rtrA sends out an ARP request for the workstation, it will be sent out all rtrA interfaces. Although rtrA will receive a response from the workstation, it will also receive a proxy-arp response from rtrB which will overwrite the workstation response giving rtrA an incorrect entry.

There is little reason to run a router in host mode in this network topology, however, if you do, proxy-arp must be turned off on rtrB. If you are trying to netboot from the workstation, you may turn off proxy-arp on rtrB or do not specify the workstation's IP address in the boot command (ie "b image" vs "b image addres>") so the tftpboot request will be broadcast. [CSCdi41856]

• The router will send ICMP redirects on point to point interfaces when it may not make sense to do so. This behavior may be defeated by the interface subcommand no ip redirects. [CSCdi45535]

• Without periodic registers, the (S,G) state in the RP has to be kept alive by other means, such as (S,G) joins/prunes. [CSCdi59021]

• When configuring match ip next-hop or match community-list exact in an outbound route map with BGP, the following messages might be displayed:

% "map1" used as BGP outbound route-map, nexthop match not supported % "map2" used as BGP outbound route-map, exact community match not supported

This is a cosmetic error message as both next hop and community exact matching are supported. [CSCdi66245]

• When using , only one entry in the route-map is deleted (the one with the lowest sequence number).

The workaround is to issue the command once for every entry in the route-map. [CSCdi74893]

• For Cisco routers that have Lance Ethernet controllers, such as Cisco 2000, Cisco 3000, and Cisco 4000 series routers, a ping or any connection between two routers fails if one router is active on an interface, the other router is active on another interface, and both use the same standby group. A workaround is to use different standby groups. [CSCdi75944]

• If a multicast mtrace request is received from the interface that toward the requested (source,group), the mtrace request is not dropped but forwarded back on the incoming interface. [CSCdi78092]

• Fast switching from Ethernet to FDDI does not work on the AGS router. [CSCdj02233]

• Duplicate bgp neighbor entries after downloading the config from another router , the bogus one will make the *real* tcp peer to go up/down and disappears only if removing bgp entirely . [CSCdj21752]

• When policy routing is added to an interface, we appear to forward pakcets destined for EIGRP multicast 224.0.0.10, rather than processing the packets. Subsequently, EIGRP neighbors do not form on those interfaces. [CSCdj22555]

• CPUHOG with process= virtual exec. [CSCdj24345]

• A router may crash with a "System restarted by bus error at PC 0x60394488, address 0xD0D0D0D" message when running Cisco IOS 11.1(9) RSP with a heavy load of EIGRP and CSNA traffic. [CSCdj29447]

• Router running eigrp will occasionally spit out an error message indicating it is stuck in an active state [CSCdj32248]

• Under EIGRP, when the router clears a route using the host ip address, the router fails to bring back the route on that subnet into the routing table. The route, howeber, is still in the topology table but not in the routing table. [CSCdj52415]

• When you have a 7000 running EIGRP on two EIP6s, a TRIP4 and a FIP. EIGRP runs on all these interfaces. All connected networks are in the EIGRP topology, until... One adds a third EIP6. In the EIGRP toplology we may loose some of the connected networks that connect to the existing ethernet interfaces. The ip routing table still shows the routes.

Result: not all connected networks may be advertised in EIGRP.

Workaround: redistribute connected [CSCdj57362]

ISO CLNS

• If secondary addresses are configured on an unnumbered interface, the interface routes corresponding to these addresses are not advertised in IS-IS. A workaround is to number the interface. [CSCdi60673]

Novell IPX, XNS, and Apollo Domain

• When a Service down notification arrives on an interface, the router might send another down notification back out the same interface it first arrived on appearing to violate the split-horizon rule. [CSCdi72848]

Protocol Translation

• To increase the timeout time between the CONFREQ sent during PPP negotiation, configure the hidden PPP option restart-timeout msec in the translate command. The following example increases the timeout between CONFREQ retransmissions from the default of 2 seconds to 5 seconds:

translate x25 12345 ppp ip-pool restart 5000

This is implemented only on one-step connections. [CSCdi35040]

• A router configured for protocol translation from X.25 to another protocol may reload when the inbound PAD connection is closed unexpectedly. [CSCdi54692]

TCP/IP Host-Mode Services

• Under certain circumstances, router reports Alignment Correction messages. This message has minimal impact on the performance of the router. [CSCdj32238]

• Somebody has released a program, known as land.c, which⁺ can be used to launch denial of service attacks against various TCP implementations. The program sends a TCP SYN packet (a connection initiation), giving the target host's address as both source and destination, and using the same port on the target host as both source and destination.

For in-depth information including workarounds and information on other Cisco product vulnerabilities, please see:

http://www.cisco.com/warp/customer/770/land-pub.shtml [CSCdj61324]

TN3270

• When using TN3270 under low memory conditions, the router can run out of DRAM memory. Reloading is the only way to recover. [CSCdi77852]

Wide-Area Networking

• PPP reliable mode does not operate correctly when configured on asynchronous network interfaces. [CSCdi33977]

• While multi-LIS is recommended through an intermediate router, the vehicle for rfc1577 clients to understand about other subnets of "peer" routers across the atm cloud is not specified in rfc1577 (one can argue it's outside the scope of the document). Therefore, although defeating the purpose of 1577, static routes can be implemented as the vehicle for implementing multi-LIS. This being noted as limitations, issue is closed. [CSCdi37302]

• X.25 encapsulation of CLNS that specify use of the SNAP encoding method will generate a protocol identification value that is not interoperable. [CSCdi38553]

• The display of show x25 vc is not correct for incoming CMNS calls. [CSCdi40724]

• This causes calls to be placed to reestablish a connection to the ARP Server after we tear an idle one down. Given that we will reestablish anyways, there is no point in tearing down the idle one.

This will have no effect on connectivity, unless the ARP Server is too busy to accept our follow-on call. But then there are bigger problems to worry about in the network. [CSCdi40765]

• This causes some non-critical sections of the Classic IP over ATM code to run slower than they should on 4500 and 7500 routers. [CSCdi41247]

• Using RFC 1577 Classic IP over ATM, it is possible to end up with a connection to a remote host which you don't use, so an unnecessary VC is created. [CSCdi41248]

• A new command will be added to allow the CHAP Challenge name to be common across multiple boxes in a rotary group. The new command will be 'ppp chap hostname xyz'. [CSCdi44884]

• The "no cdp enabled" command configured on async interfaces will disappear from the running-config when a SLIP connection to the async port is made. Saving the configuration at this moment will therefore remove the command from the startup-config. PPP connections do not exhibit this behaviour. [CSCdi45094]

• When using IPX with multilink PPP, the router may experience high CPU utilization and network drive connectivity loss. This problem occurs with Novell 3.12 with Pburst enabled. A Novell patch must be applied to the server to resolve it. A bug in multilink PPP causes additional packets to be dropped unnecessarily. This has been resolved under CSCdi48424. [CSCdi47777]

• The AIP cannot be configured to issue idle cells instead of unassigned cells. [CSCdi48069]

• Download of image over X25 link fails when using Fash-Helper - Works OK when running RXBOOT image. [CSCdi49983]

• When traffic prioritization is configured on a Frame Relay interface with the command frame-relay priority-dlci-group, the command no fair-queuing should be also configured on the serial interface to achieve effective traffic prioritization.

See associated BUG CSCdi52882 [CSCdi52067]

• If extended access-lists are used to prioritize traffic over two DLCI's with the command frame-relay priority-dlci-group, then fast-switching must be disabled with a commands such as no ip route-cache or priority-group on the serial interface to achieve prioritization as designed by the access-list.

See associated bug CSCdi52087 [CSCdi52882]

• The received packet/byte counts for interfaces on which a LANE BUS is running will be low - the counts do not include packets/bytes received by the BUS. The output packet/byte counts are correct. [CSCdi52914]

• The interface configuration command ppp chap password password has been added. This command allows a router to respond to multiple unconfigured peers with a single common CHAP secret. [CSCdi54088]

• On the AIP when trying to setup a VC, the AIP-3-AIPREJCMD error message may occasionally reject the setup. This was sometimes observed on the 7500. The setup will succeed at next attempt. [CSCdi54829]

• Messages such as the following are printed to the console if data is received on a remotely switched permanent virtual circuit before the tunnel is established:

%SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level -Traceback= 107EA 1D190C 1EA92 342D2E 34188E 32F100 330378 3328F2 %X25-3-INTIMEQ: Interface Serial1, LCN 2 already in timer queue, new time 310620 -Process= "interrupt level", ipl= 4 -Traceback= 333396 330618 3328F2 332348 331E06 34FA74 6DE0C 1158F2 [CSCdi57343]

• The parser does not show the ppp quality command as an option. However, you can enter the ppp quality percentage command. [CSCdi61507]

• Router adds transit delay facility information to CALL ACCEPT packets resulting in call clearing. Should only add this facility to CALL CONNECT packets. [CSCdi61748]

• Incorrect handling of the X25 CLAM facility - router inserts the called number present in the original CALL REQUEST packet - instead of the new number - into CALL ACCEPT packets. [CSCdi61750]

• PPP callback over ISDN using a PRI line sometimes fails when the originating call is received by the PRI on channel 31. The PRI router then terminates the call, initiates PPP callback, and returns the error messages "callback timer expired" and "no interface available." [CSCdi65216]

• Ascend bug number TR#1168 in their 4.6b and 4.6c software releases may cause multilink PPP connections between an Ascend and a cisco router to freeze while attempting to transfer data packets. [CSCdi65291]

• When configuring PVCs on the AIP, you may observe a failure to create more PVCs when the number of VCCs configured is well below the maximum allowed. This failure occurs when the number of VPI values used exceeds a limit. The messages that occur due to this type of failure include the following:

%AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Setup VC command (error code 0x0008)

%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1500, VPI=10, VCI=257) on Interface ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC)

The limit to the number of VPI values used depends on the configuration of the vc-per-vp configuration parameter. When vc-per-vp is 1024 (the default), 33 VPI values can be used. To work around this limitation, implement the atm vc-per-vp command on the particular ATM interface, which lowers the number of VCs per VP. This results in a corresponding increase in the number of VPI values that can be used. [CSCdi67839]

• This problems occurs on a 4500/4000/7200's bri interface (routers with the Siemens Munich32 HDLC controller). After the router is reloaded, the bri interface's line protocol does not come up.

The 'show interface bri x' command shows BRIx is up, line protocol is down. The work around is to do a clear interface bri x after the system comes up. The correct behavior would be for the system to come up with BRIx is up, line protocol is up(spoofing). [CSCdi68484]

• When the MTU on an interface is set to the same value as the X.25 data packet size, X.25 incorrectly calculates buffer space while reassembling packets. The result is a memory corruption, causing the router to crash. [CSCdi89471]

• A problem seems to exist with the lower bound of the frame-relay broadcast queue parameters. [CSCdj04561]

• CSCdi54554 has already fixed on 11.0(9). But almost the same probrem is occured when we use 11.0(13), 11.0(14). But this case we are using a C1003 router. [CSCdj07260]

• The debug command "debug isdn q931" displays "Mandatory IE missing" when disconnecting a call and "IE out of order or end of 'private' IEs" when receiving a call. This is due to that the code in 11.0(12) doesn't like the Display information in the Release message, which is sent from the switch.

This problem is cosmetic as we accept calls and we clear calls due to load activity timeout(idle timeout). [CSCdj07324]

• When using DLCI prioritization on a point-to-point Frame Relay subinterface and one of the DLCIs fail, the subinterface may bounce once or continually bounce during LMI full status reports, depending on whether LMI reports the DLCI as being DELETED or INACTIVE. This behavior is the same for every DLCI defined in the priority-dlci-group.

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]

• ATM E3 interface shows Unexpected payload Type flag set to ON on 4000 [CSCdj13486]

• If an asynchronous interface is configured with encapsulation slip (the default), and if it is currently up and running with encapsulation ppp, then the configuration command "encapsulation ppp" will not be saved in the running or nonvolatile configuration. [CSCdj38128]

• LES not listening on the LECS address. workaround is to configure the LECS with the Well Known Address. [CSCdj39323]

• A remote DLSw peering router may send a DM response just after the LLC2 connection is established if the router is very busy and the PC station responds immediately to the UA with a RR. The client will need to reestablish the connection. [CSCdj47782]

11.0(17) Caveats/11.0(18) Modifications

This section describes possibly unexpected behavior by Release 11.0(17). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(17). For additional caveats applicable to Release 11.0(17), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(18).

Basic System Services

• On Single Flash Bank 2500 devices, when the device is running from the image on flash (RFF), SNMP operation of copy to flash using CISCO-FLASH-MIB doesn't work.

The work around is to use the (C)ommand (L)ine (I)nterface: "copy tftp flash" This CLI command invokes the FLH interface and the file is copied successfully to the device. [CSCdj27438]

• When custom or priority queueing is turned off on an interface that does not support fair queueing, the queueing data structures associated with the interface are left in an incosistent state.

In particular the enqueue and the dequeue routines are not reset and this causes the box to crash, the moment the routines are invoked next time. However, once the box is rebooted the inconsistency is cleared. [CSCdj29439]

• 4500 running 11.0.13 crashes in fr_fair_queue_flow_id .

The crash occured in the frame-relay packet classifier fuction called by the WFQ routine. The work around of this problem will be to disable wfq on the interfafce with frame-relay encapsulation. [CSCdj45516]

• The input queue may be wedged with ip packets if the exception dump command is configured.

The Known workarounds are: 1)Increase the input queue to 175 ([75]Original Queue amount+[100] per exception dump x.x.x.x cmd) 2)Remove exception dump x.x.x.x command [CSCdj58035]

IBM Connectivity

• When an LNM queries the router with a report station address, the router answers correctly with a report station address. However, 0.001 seconds later, the router sends a second report station address to the LNM with all zeros in the frame. This causes the LNM to work incorrectly. [CSCdj04559]

• A 1500-byte frame sent to the srtlb code is dropped because the srtlb mtu is set to 1492. [CSCdj18838]

• To avoid getting bad refcount message at the time of router boot. [CSCdj23422]

• A small window exists in which it is possible after a transmission group reinitialization that only one CP-CP session is established between the router and a neighboring node. In this case, the contention winner session from the perspective of the router is not activated. Once this occurs, the CP-CP contention winner session will only activate if the APPN subsystem is stopped and started.

There is no known workaround. [CSCdj25859]

• appn image may restart because of a CPU HOG problem in processing a link failure event by the Directory Service appn process (xxxdns00) in an extreme condition when a lot of locate requests were pending with the node with which link failure has occurred.

There is no alternative workaround when this happens. The router is forced to restart by the system watchdog process (software-forced reload event).

The fix is to give up the cpu by the xxxdns00 process after processing certain number of requests at a time. [CSCdj26423]

• The APPN router may display the following "Unanticipated CP_STATUS" message when the conloser cp-cp session goes down and comes back up without the conwinner session being deactivated.

%APPN-6-APPNSENDMSG: Ended DLUR connection with DLUS NETA.SJMVS1 %APPN-7-MSALERT: Alert LU62004 issued with sense code 0x8A00008 by XXXSMPUN %APPN-6-APPNSENDMSG: Starting DLUR connection with DLUS NETA.SJMVS4 %APPN-7-APPNETERROR: CP_STATUS FSM: Unanticipated CP_STATUS message received

Each subsequent broadcast locate received by this router causes the following messages to be displayed and about 1920 bytes of appn memory to be leaked.

%APPN-7-APPNETERROR: MAP_INPUT_SET_TO_ROW: invalid input value=0x80200080 %APPN-7-APPNETERROR: State Error lcb: 60C05CC0 pcid: DA839C70FB1548CB row: 22 col: 0

This problem was found when 2 links were active to the same node, and the cp-cp sessions were split between these 2 links. The problem would occur if the link with conloser was stopped.

The appn subsystem should be stopped and restarted to clear this problem. If these cp-cp sessions are between the router and the host, terminating either cp-cp session on the host will also clear this problem. [CSCdj33718]

• If the DLUR router received fixed session-level pacing values on the primary stage, it may modify these pacing values before forwarding the bind to the secondary stage. [CSCdj36195]

• The APPN router may crash during an snmp access to the appn mib. This problem only occurs after an unused appn node is garbage collected. The crash has the following backtrace.

System was restarted by bus error at PC 0x8B5902, address 0x4AFC4AFC PC: process_snmp_trs_tg_inc

0x8B5CAC:_process_ms_data_req_trs(0x8b5aaa)+0x202 0x87E5FE:_xxxtos00(0x87d6b0)+0xf4e 0x180E5C:_process_hari_kari(0x180e5c)+0x0 [CSCdj36824]

• APPN dlur router may reload with SegV exception in ndr_sndtp_encap_mu in a timing window where the DLUR supported device disconnects before a request_actpu is sent to the dlus for that device. [CSCdj37172]

• The problem would appear to be when a LU node specific node attempts to start a session with a set of invalid Bind parameters. This results in a locate-find ( with the bind in the CDINIT ) being sent through the Cisco APPN network to the end VTAM CP who rejects the Locate-Find with a 0835003A sense and sends this back with a control vector CV35 of minimum length 8 bytes to the originator via the Cisco APPN NN.. The APPN NN then rejects the frame with a 08953500 sense and drops the CP-CP session between the CISCO and VTAM CP's. [CSCdj37479]

• APPN enforces the maximum size of a CV10 (product set identifer) on XID to not exceed 60 bytes. Some products include a CV10 which is larger than the 60 byte value. These products will fail xid negotiation with APPN. [CSCdj40144]

• In the event that APPN/DLUR has processed and sent a bind request to a downstream device, and that device has not responded to the bind, a vary,inact on the host for the lu name that the bind is destined for will not completely clean up the session as it should. [CSCdj40147]

• appn TPsend_search leaks memory while sending locate search requests to adjacent nodes at certain condition (when lik failure occurred). [CSCdj40915]

• When RSRB with TCP encapsulation is configured and remwait/dead peers exist, an explorer packet may continuously try to open the remwait/dead peer.

After several tries, the router may crash with memory corruption.

The workaround is to remove any remwait/dead peer statements. [CSCdj42427]

• The APPN router may crash with a bus error if a race condition is hit during cleanup processing. The stacktrace shows the crash occurred in Qfind_front while executing a psp00 function. The stacktrace for this particular crash is shown below.

System was restarted by bus error at PC 0x3784864, address 0xF0110208 PC 0x3784864[_Qfind_front(0x3040a04+0x743e44)+0x1c] RA: 0x36C1F2E[_queue_find_front(0x3040a04+0x68151c)+0xe] RA: 0x36CC554[_psbmfrm(0x3040a04+0x68bb30)+0x20] RA: 0x36CDAF6[_psp00(0x3040a04+0x68cfd4)+0x11e] RA: 0x314BD78[_process_hari_kari(0x3040a04+0x10b374)+0x0] [CSCdj44198]

• APPN crashed when it received a CV35 without the Termination Procedure Origin Name (TPON) field. [CSCdj44661]

• DLUR bind processing can cause stack corruption which leads to a reload with PC 0x0. This is caused by attempting to parse the user data subfields beyond the location where the subfields exist. The reload will only occur of the byte two bytes beyond the end of the user data area is 0x3 or 0x4. This is a very rare occurance. [CSCdj45676]

• In recent versions in 11.0 could see problems when appn cp/cp session are split across multiple tgs. Workaround is to force cp/cp session to use a single tg. [CSCdj46413]

• The message %APPN-0-APPNEMERG: Mfreeing bad storage, addr = 60BB7188, header = 60BB6B20, 00000218 -Process= "ndrmain", ipl= 0, pid= 62 may be issued when a dlur served PU disconnects. This defect was caused by the fix for CSCdj37172. [CSCdj46783]

• Some 68K-based routers (7000, 4000, 2500) running APPN may crash with the following stacktrace. This memory corruption may occur after a rare combination of appn detail displays, following by a "show appn stat" display.

PC 0x1EA33A[_crashdump(0x1ea2b8)+0x82] FP: 0xA6D9F0[_etext(0x8f2d38)+0x17acb8], RA: 0x1660DE[_validate_sum(0x16602a)+0xb4] FP: 0xA6DA14[_etext(0x8f2d38)+0x17acdc], RA: 0x141154[_checkheaps_process(0x1410b2)+0xa2] FP: 0xA6DA30[_etext(0x8f2d38)+0x17acf8], RA: 0x180FB8[_process_hari_kari(0x180fb8)+0x0] [CSCdj47941]

• An APPN router may fail the ACT_ROUTE if using parallel TGs. This problem may occur when an APPN router has two parallel links defined with the adjacent node. If the adjacent node activated a link to the network node (NN) requesting a TG number that had previously been used for a different defined link activation, the NN may fail the ACTIVATE_ROUTE. The APPN router sometimes tried to incorrectly activate the route using the other inactive link which still had the same TG number. [CSCdj49814]

• Normal non-extended unbind (0x3201) was extended with corrupted information which caused rejection by the host. As far as the host is concerned, the session is still active. User can not cleanup this session without bringing down the link. [CSCdj50581]

• Under certain circumstances, APPN may crash with the following stack trace.

> System was restarted by bus error at PC 0x6C75DC[_Mfree(0x6c75b6)+0x26], address 0xFFFFFFF8[_etext(0x73ab50)+0xff8c54a8] > Image text-base: 0x00012000[__start(0x12000)+0x0], data-base: 0x0073AB50[__etext(0x73ab50)+0x0] > FP: 0x872C74[_etext(0x73ab50)+0x138124], RA: 0x6588BC[_session_failure_clean_up(0x658502)+0x3ba] > FP: 0x872EB8[_etext(0x73ab50)+0x138368], RA: 0x65C6E6[_process_cp_status_sig(0x65c2da)+0x40c] > FP: 0x8730F0[_etext(0x73ab50)+0x1385a0], RA: 0x64D820[_xxxmss00(0x64d64e)+0x1d2] > FP: 0x873210[_etext(0x73ab50)+0x1386c0], RA: 0xB720C[_process_hari_kari(0xb720c)+0x0] [CSCdj51051]

Interfaces and Bridging

• Removes the auto-enable feature for packet-by-packet frame-relay compression, and allows this form of compression to be manually enabled. [CSCdi85183]

• Please note that ppp-compression and custom-queueing are not compatible features. We are currently trying to reproduce this bug with all forms of fancy queueing turned off.

Assuming we cannot reproduce, this bug will be reclassified at a lower priority, with the trust being to do a command-parser change to prevent use of fancy queueing and ppp-compression.

Please note, however, that we ackowledge that use of mutually- incompatible features should not cause the router to crash. Further, why the crash is occuring in the compression engine is something we do not currently understand.

For the present, please turn off all fancy queueing. [CSCdj25503]

• A bug in the fddi driver is hogging the CPU for up to 1.5 seconds, while waiting for the ucode to bring up CMT. [CSCdj47916]

IP Routing Protocols

• "clear ip rout *" does not clear redistributed routes. [CSCdj30913]

• Router crashes on receiving multicast packets with illegal source address 0.0.0.0. The work around is to configure access list to filter out packets with source ip address 0.0.0.0. [CSCdj32995]

• On a 4700, RIP can't handle more than 1800 routes received back to back without inter-frame gap. [CSCdj40042]

• If the OSPF summary host route is overwritten by a route from another routing process which has lower administrative distance, it is possible that the OSPF summary host route will not be reinstalled after the latter route is removed. In particular, it only happens if the host route address is also the router ID of some ASBR. [CSCdj49161]

Novell IPX, XNS, and Apollo Domain

• Using any of the xns flooding command may cause the router to reload, give alignment, bad pool, or buffer warnings. [CSCdj23479]

• If a route goes away via aging (180 seconds) and the default route is known a cache entry may be installed for this network using the default route path. If the network comes back within the next 60 seconds a new cache entry pointing to the now valid path may not be installed, the cache will still point to the default route path for this network. Workaround is to clear ipx route-cache, or run without using the default route. [CSCdj47705]

TCP/IP Host-Mode Services

• Memory allocated for a new TCP connection will not be freed after receiving an ICMP unreachble if the new connection has it's own listeners for processing of incoming connections. [CSCdj07761]

VINES

• If the system has corrupt vines access lists, show vines access displays debug information. To suppress this debug information, added a new hidden command. Use show vines bad-access [] to display corrupt vines access lists. [CSCdj37856]

• A router may unexpectedly reload when VINES SRTP routing is configured. The workaround is to remove the vines srtp-enabled command. [CSCdj37888]

Wide-Area Networking

• PPP IPCP negotiation will be changed after Cisco IOS Release 11.0(11).

In Cisco IOS Release 11.0(11) the software accepts the remote peer's "Her" proposed address regardless, and the "Her" address is subsequently added to the IP routing table as a host route.

With Cisco IOS Releases later than 11.0(11) the software will check the "Her" address against the corresponding dialer map and if the address is different than the IP address detailed within the dialer map, a NAK will be sent and the dialer map IP address will be added as a host route in the IP routing table.

It is possible to revert to the previous operation using the hidden interface command ppp ipcp accept-address. When enabled the peer IP address will be accepted but is still subject to AAA verification, it will have precedence over any local address pool however. [CSCdj04128]

• On a Cisco 4500 running Cisco IOS Release 11.0(11) and RSRB, there may be a crash in the "llc2_timer" routine causing a system reload. [CSCdj13175]

• The patch prevents the use of an invalid pak->info_start pointer when doing payload compression on RSP platforms, thus avoiding a crash. [CSCdj43332]

• A boot image without a subsystem containing IPCP will restart the router.

There is no workaround. [CSCdj48085]

• A boot image for version 11.003(000.012) will cause the router to reload if a variant of the "compress" command is configured for a PPP encapsulated interface.

This has not been observed on any other release. [CSCdj56450]

11.0(16) Caveats/11.0(17) Modifications

This section describes possibly unexpected behavior by Release 11.0(16). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(16). For additional caveats applicable to Release 11.0(16), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(17).

Basic System Services

• When using AAA, it is not possible to duplicate the precise sequence of prompts that dialup users have become accustomed to from using XTACACS. This makes moving from XTACACS to AAA problematic for users who do not wish to rewrite their dial-in scripts. [CSCdi42842]

• The system may reload when writing a core file via tftp if the core file already exists on the tftp server. [CSCdi83485]

• The router may reload inadvertently if you respond improperly to extended ping dialog prompts. [CSCdi88443]

• An ARAP session attempt causes NAS to reload when running AAA accounting with ARAP. [CSCdj21751]

IBM Connectivity

• When Netbios name caching is used, it is possible that that the RIF in SRB spanning explorers is not knocked down to the lowest MTU on local token ring interfaces. The result is that Netbios stations that use a frame size larger than the MTU size on a token ring interface will not maintain sessions.

This problem has only been seen with local SRB. It has not been seen with RSRB or DLSW.

Serveral workarounds are: increase the MTU size on the local TR interfaces to be greater than or equal to the transmitting station, lower the MTU size of t the transmitting station to be less than or equal to the MTU on the token ring interface, or disable netbios name caching. [CSCdi86423]

• Issuing the show lnm station command may cause the routers to reload, especially when the stations are getting in and out of the ring. [CSCdj09905]

• During certain race conditions, the DLUR router may hang the dlur/dlus pipe in a "pending inactive" or "pending active" state. [CSCdj10176]

• Continuously issuing the appn ping command causes the router to hang indefinitely. [CSCdj19525]

• Using the dlsw ring-list or dlsw port-list configuration commands can cause a SegV exception when executing the show dlsw reachability command. [CSCdj21894]

• The DLUR router may get into a tight loop, in which it continuously retries to start the DLUR/DLUS pipe to the same DLUS without waiting the specified retry time. This problem could cause the router to crash or continuously display pipe retry messages without waiting the specified retry time. It may also result in high CPU usage. [CSCdj22330]

• When establishing a DLSw session, the circuit priority field in the SSP header of the CUR_cs, ICR_cs, and/or REACH_ACK SSP frames may be set to a reserved value (5, 6, or 7). While this value will not cause problems when sent to a Cisco router peer, it may cause interoperability problems when peering to another vendor's equipment. This problem may manifest itself as an inability to start the circuit. [CSCdj22482]

• Under certain circumstances, the router will fail to create a dynamic link station. The workaround is to restart APPN on the router. This is caused by a small buffer leak that occurs for each actpu processed by DLUR. After some time, enough buffers may be lost as to cause session failures and dynamic link station failures due to insufficent buffers. [CSCdj23782]

• During certain race conditions, an APPN router may crash with the following stack trace:

PC= 0x606079a4[psbmfrm(0x60607930)+0x74], 32 bytes

PC= 0x606094d0[psp00(0x60609380)+0x150], 320 bytes [CSCdj25484]

• ReqActPU continuously fails with sense 8170001. This problem may occur when there are two parallel links to the same adjacent CP and the links are frequently stopped and started. The reason this may occur is because someone could try to activate a route over an inactive link. [CSCdj26027]

• When promiscuous or peer-on-demand peers are used and there are more than 100 circuits connected, a memory corruption crash may result when the promiscuous or peer-on-demand peers disconnect. The corruption occurs when circuit cleanup is delayed due to end station delay, LAN network delay, or high router CPU usage. [CSCdj26284]

• When a Cisco DLSw router starts a circuit (by sending CUR_cs) to another vendor's DLSw implementation, the Cisco DLSw incorrectly sets the lf bits in the CUR_cs header. [CSCdj26402]

• Using 11.2.4 with qllc, npsi-poll, and rsrb, the router does not forward the null-xid from the host. The LLC session fails to establish.

Workaround is to configure using dlsw. [CSCdj26404]

• An APPN router may crash with the following stack trace:

606CD174[Qfind_front+0x24]

606C7D80[timer_process+0x300]

606C8070[csweotsk+0x1d0]

A router may experience this problem after displaying several messages when the output buffer was full. If the crash was related to displaying "incomplete definition in configuration" warnings, the workaround is too remove these incomplete definitions. [CSCdj26701]

• The timer that controls the daily cleanup of APPN topology and the 5-day rebroadcast of topology resources owned by this APPN node can fail after 45 days. At this time, other nodes where the timer is still functioning properly may age out the topology of the node with the failed timer after 15 days. Thus, after a total of 60 days, APPN routing failures and failed CP-CP sessions may result between APPN network nodes.

Because other network events (link outages, and so forth) can trigger a node to send a TDU, this problem will not necessarily appear exactly after a 60-day uptime -- it may occur much later or not at all. However, any APPN router running in the network for over 60 days is at risk for seeing this problem.

Stopping and restarting APPN will work around this problem until the next timer wrap, which can be up to 45 days, but may be less depending on the current value of the timer. Reloading the router will reset the timer and avoid the problem for an additional 60 days. [CSCdj29014]

• A router configured for RSRB may crash with a watchdog timeout during low memory conditions and/or continual peer state changes. [CSCdj30381]

• A DLUR router may reject unbind requests from the host if it has not received a bind response from the downstream LU.

If the downstream device never responds to the outstanding bind, the DLUR router will wait indefinitely and not free the local-form session ID (lfsid). This may cause a situation in which the host tries to reuse a lfsid after it has sent an unbind request, but the DLUR rejects the new bind request because it believes that this lfsid is in use. If the host continuously tries to use this lfsid which the DLUR believes is in use, then no new sessions can be established. This problem occurs only when the downstream device does not respond to a bind request. [CSCdj30386]

• Sometimes the linkstations may get stuck in a XIDSENT state when an APPN linkstation fails and recovery is attempted.

Caveat CSCdi77040 provides a fix for this problem in the system side. This caveat provides the corresponding fix for APPN. [CSCdj30552]

• Any device connecting to APPN/DLUR that does not carry a cv0E with a CPname specified on XID (any PU2.0 and some older PU2.1 implementations) causes APPN to fail to release 536 bytes of memory each time the device disconnects and reconnects. Any device connecting on a port with LEN-connection defined also exhibits this behavior.

When memory is exhausted, the APPN subsystem may stop or the router may reload. [CSCdj33429]

Interfaces and Bridging

• On Cisco 7500 RSP platforms, FSIP serial interfaces may display the following panic messages on the RSP console:

%RSP-3-IP_PANIC: Panic: Serial12/2 800003E8 00000120 0000800D 0000534C

%DBUS-3-CXBUSERR: Slot 12, CBus Error

%RSP-3-RESTART: cbus complex

If the string "0000800D" is included in the panic message, the problem is related to this bug. The workaround is to load a new image that contains the fix for this bug. [CSCdi78086]

• A Cisco 4700 Token Ring interface appears to intermittently stream "claim tokens" followed by streaming beacons when AM is lost. [CSCdj22150]

• Transparent bridging does not work with SMDS subinterfaces in Cisco IOS Release 11.0. Cisco IOS Release 11.1 is not affected.

Frames are not bridged properly through the SMDS subinterface. Issuing the show bridge command will not show any bridge table entries for hosts through the SMDS subinterface. [CSCdj23544]

IP Routing Protocols

• Under unusual circumstances, EIGRP may reinitialize multiple peers when a stuck-in-active condition occurs, instead of just the peer through which the route was stuck. [CSCdi83660]

• Under certain conditions, the EIGRP variance command may not remove routes that have a higher next hop metric. To resolve the problem, issue the clear ip route command. [CSCdj19634]

• Regression bugs found by ARF requre us to do a paritial backout of CSCdi73194 until all regression problems have been found and fixed.

The following Cisco IOS Releases are affected: 011.001(012.004) 011.002(007.002) 11.2(07.02)P 011.000(016.001) 11.1(12.04)AA 11.2(07.02)F 11.0(16.01)BT 11.1(12.04)IA 11.1(12.05)CA and subsequent versions of those releases until this fix is integrated. Also relevant are other releases where the fix for CSCdi73194 got integrated. [CSCdj31496]

LAT

• Illegal LAT STOP slots may be sent if a line is disconnected immediately after initiating a LAT connection. This is more likely to be seen when using protocol translation. These illegal slots cause the LAT virtual circuit to be disconnected, affecting all connections to the host. [CSCdj09876]

Novell IPX, XNS, and Apollo Domain

• IPX fast switching might fail over a PRI interface, resulting in IPX client connections not being established over the PRI even though the IPX servers are visible. The workaround is to configure no ipx route-cache on the PRI interface. [CSCdj29133]

TCP/IP Host-Mode Services

• New TCP connections may become stuck in SYNSENT state when router is low on memory. [CSCdj30008]

VINES

• Issuing the write memory command may cause the system to reload while writing the VINES access list to memory. Issuing the write terminal or show vines acc commands may also halt the system. The workaround is to delete the configuration file and reconfigure the system. [CSCdi49737]

Wide-Area Networking

• PPP CHAP authentication has a serious security vulnerability that allows a moderately sophisticated programmer, armed with knowledge of the vulnerability and some basic information about the network to be attacked, to set up unauthorized PPP connections. There is no workaround. Customers who rely on CHAP authentication should upgrade their software to avoid this problem. More information is available on the Worldwide Web at http://www.cisco.com/warp/public/770/chapvuln-pub.shtml. [CSCdi91594]

• Under a high CPU load, it may be possible for the number of active calls and the number of available B channels displayed by the show isdn status command to be incorrect. Duplicate caveats are CSCdj23944, CSCdj27419, CSCdj15811, CSCdi82010 and CSCdj28147. [CSCdj18895]

• Routers running with x25 routing enabled on releases after 11.0(14.1), 11.1(10.1) and 11.2(4.4) are susceptible to the router processor pausing indefinitely when malformed connections are made to the X25-Over-TCP (XOT) port. If this occurs, the router must be reloaded to recover.

The following error message can be seen scrolling on the console if the router is in the above state:

%X25-4-VCLOSTSYNC: Interface TCP/PVC, VC 0 TCP connection corrupted

This does not seem to occur in a normal XOT switching environment. [CSCdj25846]

• The CHAP debug message which includes the text "Waiting for peer to authenticate first" will be output with an invalid interface name. [CSCdj27861]

11.0(15) Caveats/11.0(16) Modifications

This section describes possibly unexpected behavior by Release 11.0(15). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(15). For additional caveats applicable to Release 11.0(15), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(16).

Basic System Services

• If a Cisco Catalyst 3000 on an adjacent network does not have a protocol address configured and it sends CDP updates, the router may be reset when the show cdp neighbor detail command is used. [CSCdj15708]

IBM Connectivity

• APPN/DLUR downstream PU may get stuck in a "stopping" state in a timing situation when a dactlu is outstanding to a downstream PU and the the PU disconnects. After this point, the PU may no longer be able to connect. [CSCdj08833]

• The APPN router may crash with a SegV exception in ptp06a. [CSCdj09026]

• release note

LOCACK: recv DM, bogus, state NO_ONES_HOME can prevent netbios sessions from coming up in a busy system. [CSCdj11152]

• A system was restarted by the error "Software forced crash." The stack trace points to the LAN Manager process.

The current workaround is to disable LNM.

> [CSCdj11711]

• When modifying a peer statement for a DLSw remote peer we added a cost parameter and the cost parameter was not accepted by the parser and saved in the config. Even when a "wr mem" was executed the router did not save the cost statement in the config. The cost statement did work as designed and this can be observed when looking at the sh dls capabilities command but if the router is reloaded the command must be reentered to get it to work. [CSCdj16627]

• Cisco DLSw appears to shift the lf bits in the SSP header when peering to other vendors DLSw implementations. This may cause circuits to connect using a (smaller) non-optimal largest frame size or may cause cicruits not to be able to connect at all. [CSCdj17372]

• Cisco 2522 routers running Cisco IOS Release 11.0(11) may have problems with the SDLC state machine. When a large amount of data is input into the router from a PU (for example, during a file transfer), the router may poll the next PU without receiving a poll final in a frame and without T1 expiring. The router may also expect data from the PU, even though it did not poll the PU.

A workaround is to ensure there are no unnecessary PUs configured on a line that is continually sending SNRMs. [CSCdj17630]

• When in the network with a VTAM4.4 node, Cisco APPN improperly clears a bit in the TDU CV45 which is set by VTAM 4.4. This can cause improper tdu information to be dispersed to the network and can cause a topology trashing condition in some situations where a router is positioned between two vtam 4.4 nodes. [CSCdj18360]

• An APPN router may fail with a SegV exception when reporting an xid negotiation error during appn link activation. The decoded PC is in cs_send_alert. [CSCdj18565]

• The DLUR router may display an Mfree error in the ndrmain process when issuing an "appn stop". This message does not effect the performance of the DLUR router. [CSCdj19884]

• When a directory cache entry exists for a resource and a broadcast search arrives for that same resource name, the intermediate node broadcast processing will delete the valid cache entry that existed previously. This defect will cause excessive locate broadcast traffic. [CSCdj21343]

• With APPN/DLUR, caveat CSCdj18360 caused a regression in APPN images, which creates thrashing topology updates (topology war) for any topology with more than one CP-CP session. Cisco recommends that an image containing CSCdj18360 should not be used in an APPN network without also having this fix applied. All APPN images containing CSCdj18360 and not this fix have been deferred as production images. [CSCdj23165]

Interfaces and Bridging

• A Cisco 7500 series router may report spurious errors such as the following:

*Dec 20 06:53:08: %RSP-3-ERROR: CyBus0 error 78

*Dec 20 06:53:08: %RSP-3-ERROR: invalid page map register

*Dec 20 06:53:08: %RSP-3-ERROR: command/address mismatch

*Dec 20 06:53:08: %RSP-3-ERROR: invalid command

*Dec 20 06:53:08: %RSP-3-ERROR: address parity error

*Dec 20 06:53:08: %RSP-3-ERROR: address parity error 23:16 1, 15:8 1, 7:0 1

*Dec 20 06:53:08: %RSP-3-ERROR: bus command invalid (0xF)

*Dec 20 06:53:08: %RSP-3-ERROR: address offset (bits 3:1) 14

*Dec 20 06:53:08: %RSP-3-ERROR: virtual address (bits 23:17) FE0000

*Dec 20 06:53:09: %RSP-3-RESTART: cbus complex

or

09:53:32.607 EST: %RSP-3-ERROR: MD error 0080008030003000

09:53:32.607 EST: %RSP-3-ERROR: SRAM parity error (bytes 0:7) 0F

09:53:33.363 EST: %RSP-3-RESTART: cbus complex

CyBus errors similar to the above errors have two known causes. If there are HIPs in the router and on the bus reporting the CyBus error, a race condition may exist with the HIP microcode on an oversubscribed bus. The workaround on dual-CyBus platforms is to move all the HIPs onto a CyBus that is not oversubscribed.

The errors can also be caused by the failure of a marginal CI arbiter board or an RSP board. As a result of this problem, all interfaces are reset, causing forwarding to be stopped for a few seconds. [CSCdj06566]

IP Routing Protocols

• Cisco 4500 routers may not correctly policy-route when serial subinterfaces are configured and the fast-switching cache is populated. The workaround is to disable fast switching on all interfaces. [CSCdi86063]

• icmp redirect is not sent if icmp type of incoming packet is echo-reply [CSCdj00809]

• Under certain conditions a static route with a next hop reachable via a static interface route is not installed in the routing table. [CSCdj08220]

Novell IPX, XNS, and Apollo Domain

• When two routers are connected to the same destination, outbound IPX fast switching on dialer interfaces does not work on the more recently connected interface. Under certain circumstances a system reload may occur with traceback pointing to ipx fastswitching. The workaround is to turn off fast switching on the DDR interfaces using the no ipx route-cache command. [CSCdi78766]

• When using weighted fair queueing IP RIP, and IPX RIP/SAP packets may be dropped, this might lead to losses of connectivity if three updates in a row are dropped. [CSCdj18092]

TCP/IP Host-Mode Services

• Previously, DLWS connect to a down interface on the peer succeeded. This has been fixed so that a DLSW connect to a down interface on the peer will not succeed. This is the correct behavior. [CSCdj00448]

VINES

• When 'no vines time participate' is configured on the router, the router no longer responds correctly to vines time requests. This results in mail messages from clients on serverless segments having timestamps that are 3 hours earlier than the time configured on the router and vines server. [CSCdj13232]

Wide-Area Networking

• The problem described by this DDTS and duplicates CSCdj02168, CSCdj07119, CSCdj08187 and CSCdi82010 results on AS5200 platforms in hung calls, ISDN data structure memory leaks and inability to either call out or accept incoming calls.

Other ISDN platforms are affected largely by that described in CSCdj07119 or CSCdi82010 depending upon their particular ISDN usage characteristics. [CSCdj05355]

11.0(14) Caveats/11.0(15) Modifications

This section describes possibly unexpected behavior by Release 11.0(14). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(14). For additional caveats applicable to Release 11.0(14), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(15).

AppleTalk

• When using ARAP on a terminal server users may experience issues with modem answering calls with no connection. Messages similar to the following may be displayed on the console:

%SYS-2-MALLOCFAIL: Memory allocation of 41394 bytes failed from 0x35DD24E Traceback= 30E83CC 30E94CA 35DD25 35D8CBE 35DCD5C 35D9CF0

This occurs primarily under heavy load. [CSCdi79459]

Basic System Services

• When running the TN3270 client to a slow TN3270 server, the router might reload. The following error will be seen on the console or in the logs prior to the reload:

%SCHED-3-PAGEZERO: Low memory modified by Exec

Issuing the show version command after the reload displays the following:

System restarted by unknown reload cause - ptr to non-ascii bytes 0x4 [CSCdi73404]

• When using RSP code with HIP, TRIP, or FIP interfaces, and when the MTU is larger than 4096 bytes on TRIP or FIP interfaces or larger than 8192 on HIP interfaces, there is a rare chance that a system error might occur. When this happens, the error message "CYBus error 8" or "CYBus error 10" is displayed. [CSCdi75522]

• A memeory leak was introduced whenever Tacacs+ was enabled. The memory is released to the exec process as seen on the sh memory. The leak does not appear in 11.0.9 only 11.0.10 and above. [CSCdi89479]

• Under unknown circumstances, the router may restart due to a Bus Error. This defect will be fixed in a future release of IOS. [CSCdj02493]

• When ntp broadcast client is enabled, packet buffer leaks may occur unexpectedly. Deconfigure the command if this condition occurs. [CSCdj03162]

• On RSP systems, when maximum-size MTU packets are received by serial interface processors (including the FSIP, HIP, MIP, POSIP, and serial port adapters on VIPs that forward data to the RSP to be routed), up to 8 bytes of data might be written into the next datagram's packet memory. This could result in anomalous system behavior, including software-caused system crashes and dropped datagrams. This problem is never seen on RSP systems that do not have serial interfaces. [CSCdj08573]

• Under certain circumstances alignment warnings may appear when fastswitching with custom or priority queueing enabled.These warnings signal that extra CPU cycles are necessary to process the packet. Despite the warnings, the packet is still switched correctly. [CSCdj12269]

EXEC and Configuration Parser

• The output of the show tech-support command displays some potentially sensitive SNMP data, such as the SNMP community strings, SNMP MD5 keys, and SNMP user IDs and passwords. If these data refer to read-write communities or views, they can be used to reconfigure the Cisco IOS software, providing the same level of access to the Cisco IOS software as is available with the enable password. Take care when sending show tech-support command output across insecure channels. For example, remove the community strings, keys, and user IDs and passwords before sending. [CSCdj06881]

IBM Connectivity

• On very rare occasions, issuing the command show source can cause the IOS software to reload. [CSCdi35216]

• This crash is caused by the SP microcode on the C7000 whereby a buffer copy by the SP makes the RP wait too long and it takes a bus error.

There is precedence for this problem and the fix is to lower the size of the block of data being copied at any one time. [CSCdi77785]

• When certain flow control situations occur between LLC2 partners, a message indicating that the T1 timer should be increased is printed. This is usually misleading. When the message is printed, the retransmission cycle is delayed by a T1 interval. This is wrong, and may lead to delays. This fix corrects the problem. [CSCdi84471]

• QLLC: Connection using a virtual Mac Address from a pool of virtual mac addresses may get connected to the wrong resource on the mainframe. [CSCdi86358]

• When using SDLC via DLSW in IOS release 11.0 and 11.0, the command SDLC address XID PASSTHRU always disappears from the router config after a router reload. It sometimes also disappears from the config during normal operation (without reload). [CSCdi88796]

• QLLC tries to activate an LLC-2 session to the host after receiving a RESET with a cause of NETWORK_OUT_OF_ORDER or OUT_OF_ORDER. [CSCdi90114]

• The DLUR router may start failing to establish new lu lu sessions after hitting a race condition during session activation and deactivation. Messages similar to the following may be displayed on the router console when attempting to start new sessions. APPN must be stopped and restarted to clear the problem.

IPS ID: 1400 QUEUE: 2 ORIGIN: xxxpcs00 MUTYPE: C5 %APPN-0-APPNEMERG: Assertion failed in ../scm/xxximndr.c at line 158 -Process= "xxxims00", ipl= 0, pid= 58 -Traceback= 606C3488 606879EC 606818C8 606810E4 6067AF90 6019AB08 6019AAF4 [CSCdi90117]

• The router might crash if you enter the debug source error, debug llc2, or debug local command. [CSCdi92503]

• Removeing dead peers bu the config comamnd 'no source-bridge remote-peer...' can sometimes cause the router to crash, if that peer is trying to open up. [CSCdi93052]

• When ruuning dlsw on a 7500 with 11.0(13) it is posible for entries in the reachabilty cache to stay in a searching or found state beyond the default 16 minute timeout. If you enter this condition issue a "clear dlsw reach" command to clear the entries. [CSCdj01288]

• The SDLC output queue can get stuck if the sdlc line-speed command is not set or if it is set to an incorrect value. The symptom is that the router stops sending SDLC frames out the serial interface, resulting in SNA session drops. The interface needs to be recycled or reset to clear the condition. The workaround is to configure the sdlc line-speed parameter to be equal to the actual line speed being used. [CSCdj01434]

• The Cisco 2520, 2521, 2522, and 2523 routers may report SDLC abort frames on low-speed ports that do not get reported on the high-speed ports or other platforms. This is because the low-speed ports count all aborts and the high-speed ports and other platforms count only aborts that are longer than 2 bytes. This is cosmetic and does not result in retransmitted frames. There is no performance impact. It is merely an indication that the transmitting device is sending erroneous bits after the trailing flag. These bits are simply ignored. No workaround is necessary. [CSCdj01488]

• A router configured for DSPU may crash with the error "Software forced crash, PC 0x31598BC" if end stations are continually activating and deactivating. [CSCdj02005]

• A race condition may occur during session cleanup which causes the DLUR router to crash or display a "Mfreeing bad storage" message for the "psp00" process. [CSCdj02249]

• This shows up on any router on whcih the service point name is configured using the "sna host" or "dspu host" command. When the router generates an NMVT alert, the alerts use the host name of the router, not the service point name.

After the fix, the router will correctly send the service point name in the NMVT alert [CSCdj02382]

• Original complaint:

The value returned from an SNMP get for the oid:

.iso.org.dod.internet.private.enterprise.cisco.ciscoMgmt.channel. cipCard.cipCardTable.cipCardEntry.cipCardEntryCpuUtilization (.1.3.6.1.4.1.9.9.20.1.1.1.5)

is a constant 89 (also observerd was the value 90), regardless of the real CIP CPU utilization. The 'show controller cbus' command can be used to retrieve the real CPU utilization on the Channel Interface Processor.

Fix provided:

The SNMP MIB has been enhanced to return the CIP Load Metrics for CPU Load, DMA Load, and Channel Adapter Load. The old value for CPU Utilization is retained but has been marked in the MIB as deprecated. The MIB was also brought up to date with respect to the reporting of Broadcast Enable and Row Status for the CIP Claw Config. [CSCdj04309]

• RSRB lack was wrongly freeing a packet if RSRB local-ack state ever enters a busy/await state. The traceback would only occur, if there are packet drops or congestion, since then this path would be executed, wherein the rsrb lack code frees the packet that llc2 code has already freed. [CSCdj05810]

• SDLC on serial interface(s) s2 though s9 on a 25xx router will use a shared trailing and starting flag between frames. This is valid SDLC, however, some older equipment does not operate with shared flags. The symptom is that some frames will be ignored by the receiving station, resulting in retransmissions and poor performance. The workaround it to configure transmitter-delay 2 on the interface. This will cause the router to include separate trailing and starting flags between frames. [CSCdj06044]

• Dlsw circuit is staying in a remote_resolve state. This is an uncommon state for dlsw to stay in, if you encounter this do a dlsw disable and then re-enable dlsw and this will correct the problem [CSCdj07098]

• Details:

The router crashes when either a no fras backup dlsw ... or no fras backup rsrb ...

command is issued ONLY WHEN the backup code is invoked. For example, when the serial line to the FR cloud is lost, and backup is configured.

When the no backup command is invoked, the cleanup for the backup functions are invoked. The bug in the code is that the backup function removes the lan-cep, instead of the backup-cep. When the lan-cep structure is referenced, the structure is garbage, and the router crashes.

No workaround at this point in the code. [CSCdj08577]

• A DLUR router (which has PU2.0 pus connecting in) may try to start the dlur/dlus pipe connection repeatedly, instead of waiting 30 seconds (default) between attempts. This condition may occur if ANS=CONTINUE is coded for an nsp pu, and the host link is stopped. [CSCdj10157]

• Buffer leak causes crash when NSP is used over DLUR. [CSCdj10387]

• The DLUR router may send a corrupt APPC frame to a DLUS if a timing window is hit when accessing multiple DLUSs. This problem may occur if there is both a primary and a backup dlus configured and at least one pu that cannot get in to the primary dlus (pu inactive) while other pus are active with the primary dlus.

This problem may cause vtam to refuse to activate subsequent dlur/dlus pipes for all dlur NNs. "/d net,dlurs" shows the dlus conwinner state as reset and the conloser as active.

The workaround is to prevent the dlur router from sending this corrupt frame is to reconfigure the DLUR routers without a backup dlus coded. [CSCdj10485]

• Under certain circumstances, particularly when there is race condition due to different link speeds between downstream and upstream routers, certain UNBINDs are not getting to the router of a lower speed link. This causes subsequent session failure with sense code LFSID_IN_USE. [CSCdj12673]

• When issueing a vary inact,giveback to a DLUR served PU (or entire DLUR), the DLUR will put the PU in timer retry and may retry the original DLUS instead of retrying the next-best dlus. [CSCdj14214]

• When RSRB with TCP encapsulation is configured and there are dead peers, an explorer packet may continuously try to open the dead peer. After several tries, the router may crash with memory corruption. The workaround is to remove any dead peer statements. [CSCdj24658]

Interfaces and Bridging

• When TRANSIT FAST bridging from frame-relay ietf (rfc1490) atm(rfc1483) or smds encapsulating FDDI or token ring MAC packets (ethernet not affected) TO a process switched bridging mode (X25, ppp, isdn, atm_dxi (a frame relay derivative)), the FDDI or token ring MAC packet address structure will become corrupted (byte shifted) in the transition on the bridge translation resulting in bridge table and packet data corruption on this bridge transition (on the process switched link). Bridging the other way (slowswitch TO frame-relay ietf, atm, or smds) has always worked properly. There are no workarounds to this specific issue, but user may consider bridging FROM atm, frame relay, or smds TO another fast bridged wan link (such as atm, frame relay, or hdlc) instead of a process switched bridge mode.

Note: In 11.0 smds is process bridged on input to bridge and therefore does not exhibit issue (but in 11.0 still issue for frame_relay ietf and atm) [CSCdi71927]

• When a router is configured as a RARP server and is also configured for transparent bridging on the same interface, the router does not respond to reverse ARP requests.

After the fix, the router box can provide RARP service if configured as a RARP server regardless of it's being configured as later 2 bridge only [CSCdi83480]

• When a FIP FDDI interface is under very heavy load, the FIP may not reply to queries resulting from 'show controller fddi' or 'show interface fddi' commands soon enough, causing a command timeout, causing the software to unnecessarily reset the FDDI interface. [CSCdi87020]

• OIR removal of a FIP from one slot into another will cause the FDDI to permanently remain in DOWN/DOWN. A reload is needed to get it up. OIR removal and putting it back into the same slot works fine. [CSCdi87221]

• As system resources become maximized FDDI interfaces stop accepting multicast packets. [CSCdi92156]

• Async controller hang and causes four modems to go into hang state [CSCdj01441]

• Transparent bridging may cause high CPU utilization in 11.1(8) IOS. A SHOW ALIGN can be used to confirm whether large 'counts' of alignment errors are the source of the problem. The SHOW ALIGN will also yield TRACE information which can be decode to determine the source of the problem. [CSCdj03267]

• Low-speed sync/async ports are unable to receive packets with size greater than 1500 bytes. The workaround is to set the MTU on both sides of the link to less than 1498. [CSCdj11304]

• When a serial is configured as half-duplex a 4000 series, but that some other serial used in full duplex is shut/no shut, then a cisco router may happen to appear totally non responsive. A power-cycling of the router is required. [CSCdj13056]

IP Routing Protocols

• Systems running OSPF might experience a software-forced crash. There is no known workaround. [CSCdi81510]

• In very obscure cases involving equal-cost backup routes to a failing route, it is possible for EIGRP to be caught in a "stuck in active" state (self-correcting after several minutes). There is no workaround to this problem. [CSCdi81791]

• The router does not forward BOOTP request broadcasts when the broadcast address is 0.0.0.0. [CSCdi88723]

• Cisco 4500 running IOS version 10.3(16) reloads and provides stack trace:

System was restarted by bus error at PC 0x601E4CD0, address 0xD0D0D0D 4500 Software (C4500-P-M), Version 10.3(16), RELEASE SOFTWARE (fc1) Compiled Thu 24-Oct-96 18:32 by richardd (current version) Image text-base: 0x600087E0, data-base: 0x60370000

Stack trace from system failure: FP: 0x605D46B8, RA: 0x601E4CD0 FP: 0x605D46D8, RA: 0x601E4D88 FP: 0x605D46F8, RA: 0x601E50EC FP: 0x605D4710, RA: 0x601C88E0 FP: 0x605D4740, RA: 0x601E4998 FP: 0x605D4760, RA: 0x601E5174 FP: 0x605D4778, RA: 0x60081D04 FP: 0x605D47B8, RA: 0x6006C8A4

Which decodes as follows:

Symbols

nhrp_cache_clear_nei nhrp_cache_clear_nei nhrp_cache_delete_subr nhrp_cache_age_subr rn_walktree_blocking_list nhrp_cache_walk nhrp_cache_age registry_list net_oneminute [CSCdi90523]

• The header details stored in the ip route-cache do not correctly reflect the MAC details of the next hop for remote destinations if the next hop MAC address changes. [CSCdi92668]

• After 'clear ip route ', where is a host route, EIGRP will not reinstall the associated route.

'clear ip route *' will force EIGRP to reinstall it. [CSCdi92753]

• An extented access-list that denies IP traffic and that does not require transport layer information may let fragments go through if the log option is configured. As a workaround, do not configure the log option. [CSCdj00711]

• When set interface selects a multiacess network there should be a route in the routing table that matches the interface to determine the next hop. If the interface is point to point, there is no reason for the routing table entry. The workaround is to use set ip next-hop. [CSCdj01894]

• Potential memory corruption and memory leaks when send PIM packets out. [CSCdj02092]

• When igrp installs a majornet route it could possibly black hole the majornet for unknown subnet routes. [CSCdj03421]

• A byte can be added to packets moving from serial to fddi interfaces [CSCdj06246]

• static routes entered in the form:

ip route

may not appear in the eigrp topology table .

The routes can be 'recovered' (reinstalled in the topology table) by either using or by unconfiguring the redistribution and configuring it again.

In the first case (), the routes go away again after a short time. In the second case, the routes are present in the topology table for a longer period, but eventually go away too. [CSCdj09571]

• PIM RP Reachable packets are unexpectedly ignored if the input interface on the (*,G) entry is empty. As a result, the RP for the group may never be learned. Issuing a clear ip mroutegroup to clear the entry should restore RP information for the group. [CSCdj11339]

• The reception of a DVMRP Graft for a group for which an administrative multicast boundary has been defined may unexpectedly halt the system. [CSCdj12029]

• After OSPF received a its own router LSA from its neighbor and that LSA has a higher sequence number than the one OSPF have currently, it is possible for OSPF to corrupt its router LSA for at most 5 sec (the minimal interval between LSA generation). If this corrupted LSA is sent to other neighbor, and the neighbor would generate OSPF-4-BADLSATYPE message about bad LSA checksum. This is no workaround but the corruption will be corrected when the next router LSA is created within 5 sec. The same problem can happen with network LSA too. [CSCdj16784]

• OSPF will not be able to form adjacency because the neighbor list is corrupted. It could lead to router crash too. [CSCdj16875]

• When the LSA with the host bits is generated, OSPF ABR handles the LSA incorrectly and reports the "OSPF-3-DBEXIST" error message for type 3 LSAs. [CSCdj21392]

LAT

• The following message may be erroneously displayed:

%LAT-3-BADDATA: Tty124, Data pointer does not correspond to current packet

When many LAT sessions are active, and a received data slot starts in the last 14 bytes of a full ethernet frame. Data for the slot is discarded. [CSCdi82343]

• When performing protocol translation from X.25 to LAT, spurious memory accesses may be seen in console messages as well as in the output from the show alignment EXEC command. [CSCdj18470]

Novell IPX, XNS, and Apollo Domain

• Routers configuring for IPX Enhanced IGRP with parallel paths might reload. The workaround is to run IPX RIP. [CSCdi84739]

• If IPXWAN is configured and the remote router is configured to allow IPXWAN Client mode the local router will reset the link upon receiving the IPXWAN Timer Reuqest. IPXWAN debugging will show "IPXWAN: Rcv TIMER_REQ reject Router asking for Client mode". The workaround is to disable IXPWAN Client mode negotiation on the remote router. [CSCdi93285]

• Under certain circumstance alignment warnings may be reported in conjunction with CDR and IPX RIP. [CSCdj09921]

TCP/IP Host-Mode Services

• Customer has a crash that looks similar CSCdi61278 [CSCdj01350]

• A TCP packet still in use may accidentally get freed in IP when the packet is going out a Frame Relay interface on which TCP header compression is configured. When this happens, the following messages are logged on console:

Mar 19 08:41:23: %TCP-2-BADREFCNT: Tty0: Bad refcnt for packet 0x608F9C2C during retransmit, 135.135.100.1:1998 to 135.135.105.1:11000, state 4 -Traceback= 601EEB7C 601EEEA4 601F1B68 601F1E4C 6013F140 6013F12C Mar 19 08:41:50: %X25-4-VCLOSTSYNC: Interface Serial3, VC 82 TCP connection corrupted Mar 19 08:41:52: TCP0: extra packet reference for pak 0x60A031D8 found: Mar 19 08:41:52: %TCP-2-BADQUEUE: Multiple entry for packet 60A031D8 -Process= "TCP Driver", ipl= 0, pid= 26 -Traceback= 601F3384 601F5408 6023CCB4 6023D214 6013F140 6013F12C Mar 19 08:41:52: pak: 135.135.100.1:1998, 135.135.1.4:11137, seq 1668710213 length 47 Mar 19 08:41:52: TCB: 135.135.100.1:1998, 135.135.1.13:11137, sendnext 1668710220, state 4 [CSCdj06781]

Wide-Area Networking

• This is a display error. The counters are not actually negative. [CSCdi68753]

• This problems occurs on a 25xx/1003's bri interface (with hdlc encaps) After the router is reloaded, the bri interface's line protocol does not come up.

The show interface bri 0 command shows BRI0 is up, line protocol is down. The work around is to do a clear interface bri 0 after the system comes up. The correct behavior would be for the system to come up with BRI0 is up, line protocol is up(spoofing) [CSCdi78255]

• In certain environments, I/O and processor memory are being consumed by processes in the router, primarily the Critical Background process, and the router runs out of memory after 29 hours of operation. [CSCdi80450]

• Under unknown circumstances, the router may be restarted by a bus error. This problem occurs only if PPP is configured. [CSCdi89566]

• When running over X25, ISIS should extract the called X.121 address and use it as the SNPA. If the x25 suppress-calling command is configured on the router, ISIS does not seem to find any called address, nor can it find the SNPA. Apparently, the routine that extracts the X.121 address fails if the calling address is not present. [CSCdj00315]

• Last X25 fragment has the M-Bit set improperly when the packet is full, but no additional data is to be sent. [CSCdj03488]

• Deleting a subinterface causes the main interface and associated subinterfaces to vanish from the configuration. This happens when the main interface uses Frame Relay encapsulation and is a member of a channel group. A workaround is to re-create the main interface by issuing the interface serial command. [CSCdj05415]

• For TS014 (Australia, PRI) switchtypes: When a clear collision occurs between the CE and the network simulteneously transfering a DISCONNECT message specifying the same call, the call is not properly cleared. Neither side sends the RELEASE message to release the call, and hence the call reference and the associated call control block (CCB). [CSCdj06157]

• A router may reload without producing a stack trace or otherwise behave unpredictably on routing an X25 call that contains 16 bytes of Call User Data. There is no known work-around. [CSCdj10216]

• The number of available B channels is incorrectly incremented by the total number of B channels per interface whenever the controller or the interface is reset. This results in dialer attempting to place calls incorrectly on resources that are actually inuse. [CSCdj11181]

• When using LAN Extender (LEX) devices on Cisco 7500, Cisco 4500, Cisco 4700, or Cisco 7200 systems, you may see a SPURIOUS error message. The LEX Host router may also crash if the LEX inteface is not bound to any serial interface. [CSCdj13342]

11.0(13) Caveats/11.0(14) Modifications

This section describes possibly unexpected behavior by Release 11.0(13). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(13). For additional caveats applicable to Release 11.0(13), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(14).

AppleTalk

• Router crash when incomplete AppleTalk fast switching cache entry is used. This happens when the cache entry is updated with another output interface and within a small timing window.

There is no workaround. Though in most cases, this scenario is unlikely. [CSCdi77772]

• Router may display assertion messages when nbp filters are activated with a dialer list. The work around is to remove nbp filters or activate nbp filters via the access-group command. [CSCdi83205]

Basic System Services

• If aaa authorization commands level methods is turned on, every command entered is authorized using methods, which includes configuration commands. Since there are some configuration commands that are identical to exec-level commands, there can be some confusion in the authorization process.

Using no aaa authorization config-commands causes the Network Access Server (NAS) not to try to authorize configuration level commands.

Care should be taken, as this reduces the administrative control that can be placed on configuration commands, i.e. it turns into an all-or-none authorization. [CSCdi36536]

• AGS+ routers with first generation FDDI cards (CSC-C2FCI) do not support translational bridging, and are no longer supported. They use encapsulated bridging. The second generation AGS+ FDDI cards (CSC-C2FCIT) support both translational and encapsulated bridging.

Encapsulated bridging does not work on the 7500 router. The workaround at this time, to bridge between the AGS+ and the 7500, is to use CSC-C2FCIT cards in the AGS+ and translational bridging.

The big disadvantage of using encapsulated bridging is that it cannot use the hardware bridge filtering capabilities of the CSC-C2FCIT cards, which have a CAM built into them which is used to do bridge filtering on the card. When encapsulated bridging is used, the main processor has to do all bridge filtering. This means that one busy encapsulated bridging FDDI network can eat the entire bandwidth of the router's main processor, just for bridge filtering. It should be no surprise that the use of encapsulated bridging is to be vigorously discouraged. [CSCdi46862]

• If the user does multiple card removals followed by multiple card insertions in the newly emptied slots with OIR, some of the replaced cards may remain in the administratively down state. For example, pull out a card from slot 1, pull another from slot 2, insert a new card in slot 1, insert another card in slot 2 is a set of actions which will trigger this bug.

The easy workaround is to simply replace cards one at a time. In the example above, pull slot 1, insert slot 1, pull slot 2, insert slot 2 will avoid the problem entirely. [CSCdi57526]

• With the configuration "aaa authentication login default local", if you press return at the username prompt, it will not regenerate a username prompt, instead it will interpret it as a null username.

To work around this, configure "aaa authentication local-override". [CSCdi76170]

• SNMP queries of objects in the MIB-II atTable may cause the device to reload if static ARP entries have been configured. This anomaly was introduced as a byproduct of the fix for CSCdi68943. [CSCdi77494]

• Issuing a copy tftp flash command and typing in a source file name with only one : in it to indicate a drive letter on the TFTP server will cause an error, and the TFTP copy will not be initiated. This occurs in all 7500 series routers. There are several workarounds. One workaround is to just specify the source file name without the drive letter (making sure the tftp server is set up to properly to accept this). Other workarounds include preceding the entire file name with the device id "tftp:". For example:

The following works: #copy tftp:D:test flash Enter destination file name [D:test]: Address or name of remote host [255.255.255.255] ?

and the following works: #copy tftp flash Enter source file name: tftp:D:test Enter destination file name [D:test]: Address or name of remote host [255.255.255.255] ? [CSCdi78276]

• When HTTP and AAA are enabled, the login is set to the default of local authentication, and the username is blank, the router enters an infinite loop that sets off the watchdog timer, causing the router to crash. [CSCdi84663]

• Accessing a non-existent interface followed by a valid interface using the http server may cause the router to crash. [CSCdi87125]

• If a hex 00 is entered as part of the name string on a Catalyst switch, IOS will incorrectly compare the name string on a received CDP packet to that of the stored CDP packet. The router will continually store the received CDP packet as a "new" device. Eventually, the router will run out of memory.

One can diagnose this problem by turning on DEBUG CDP PACKETS

If device is receiving GOOD CDP information, the output will look similar to:

CDP-PA: Packet received from 008024 3DD610 (wan-sw.3100) on interface Ethernet1 **Entry found in cache**

If the device is receiving BAD CDP packets, the entry will never be found in the cache (and thus repeatedly added).

Workarounds: 1. Turn off CDP on the router via the NO CDP RUN command. 2. Change the name on the Catalyst to a Text String; e.g. set system name foobar [CSCdi91300]

• Second Telnet session to same router VTY does not Echo characters. Possible work-around is to configure:

vty 0 telnet refuse-negotiations

This should maintain local echo for duration of Telnet session.

IF the above work-arounds are not accepted, try the following;

1/ when telnetting from a PC or Unix station go into 'line mode':

---------- len-sun% telnet bud Trying 172.17.241.23 ... Connected to bud.cisco.com. Escape character is '^]'.

User Access Verification

Password: bud>Translating "abc"...domain server (255.255.255.255) % Unknown command or computer name, or unable to find computer address bud> (===> no echo: the problem is there) (typed ^]) <=======NOTE this is control-right_square_bracket telnet> mod line

(typed CR)

bud>sho ver (echo is back) ----------------

2/ When telnetting between routers, use: telnet 'ip-address' /line and the echo is back.

---------------- bud> bud> (=> typing commands but no echo) bud>Trying 172.17.241.23 ... Open

User Access Verification

Password: bud>Translating "abcd"...domain server (255.255.255.255) % Unknown command or computer name, or unable to find computer address bud> (=>exiting) [Connection to 172.17.241.23 closed by foreign host] bud> (=> typing telnet 172.17.241.23 /line) bud>Trying 172.17.241.23 ... Open

User Access Verification

Password: ww

bud>sho line

% Type "show ?" for a list of subcommands bud>show vers Cisco Internetwork Operating System Software I [CSCdj05366]

DECnet

• DECnet is sending Phase IV prime hellos out Ethernet interfaces. [CSCdi83560]

• The command "dec advertise " (correctly) creates an entry in NVRAM. However, if there is an entry for the *same* area in the DECnet routing table and that entry was created dynamically (i.e. learned via DECnet), then issuing the command

"no dec advertise "

fails to remove the "dec advertise " line from NVRAM. [CSCdi87264]

EXEC and Configuration Parser

• Newer telnet clients which support the NAWS option cause line and width line configuration commands to appear on the vty. [CSCdi90442]

IBM Connectivity

• This problem has been more prevalent in STUN/Local-Ack scenarios involving AS/400s. The remote router expects to see an OPCODE called LINK_ESTABLISHED from the host router in order for it to transition the state from USBUSY to CONNECT. While in USBUSY state, the remote router continually sends RNR to the downstream devices. The host router will only send the OPCODE once it sees the first RR/P after a SNRM/UA exchange sequence. With other devices such as a FEP, an I-Frame can be sent out prior to the RR/P which would actually take the remote router state out of USBUSY, but the local-ack states were not corresponding to the actual situation at hand. This was the problem. The fix to CSCdi65599 actually corrected it for the most part. Additional "checking" code was added for exceptional state cases. Workarounds would be to use IOS releases that include the fix for CSCdi65599. [CSCdi61514]

• In certain configurations adding appn control-point statement can cause router to reload. [CSCdi64095]

• Cisco 4500 and 4700 router Token Ring interfaces intermittently stop working and fails to reinitialize. Problem is seen only during heavy activity and when more than one Token-Ring ports are active. This problem occurs only on the 4500 and 4700 routers. This problem doesn't occur on the 4000. [CSCdi70398]

• "no lnm rps" is only accepted when a full bridge is configured. During system releod, this command is ignored. The workaround is to configure this command again after reload. [CSCdi72702]

• When running APPN over RSRB virtual stations where rsrb local-acknolegement is being used, the secondary station may hang upon sending data. The most common symptom is only one of the two CP-CP sessions come active with the partner node. [CSCdi74906]

• The DLUR router may send a negative response to a DLUS response for a resource which is no longer available. [CSCdi75547]

• When two or more FEPs at a cental site, each with the same TIC address, are connected to a different Token Ring and a different DLSw peer router, a remote SDLC attached PU2.0 device will not establish a session to the back-up FEP if the first is taken offline. This problem does not affect PU2.1 devices. [CSCdi76575]

• When a EN connects to the Cisco APPN/DLUR function, there may be problems establishing CP-CP session connectivity if the EN's CP name was previously known to the network topology as a NN. [CSCdi77533]

• Multiple DLSw peerings to remote Routers using Frame Relay direct encapsulation and passthrough does not work.

The symptoms are sessions failing to establish and existing sessions being torn down.

The workaround is to configure TCP encapsulation. [CSCdi78017]

• When using DLSw+ to communicate with non-Cisco devices, the Cisco platform might not deal with incoming transport keepalive packets in an appropriate manner. [CSCdi78202]

• When "stun remote-peer-keepalive" is enabled in a locally acknowledged STUN over Frame-Relay configuration, STUN peers are constantly resetting due to incorrect handling of STUN keepalives. [CSCdi78480]

• If multiple DLSw remote peers advertise via capabilities exchange that they can reach the same resource, the dlsw reachability cache only indicates that one of the remote peers can reach the resource. [CSCdi78980]

• After SDLC sends 3 XID NULLs upstream to a host and receives no response, SDLC stops sending the XID NULLs and the SDLC device will never connect. This condition can occur if the remote peer conection is down because of a WAN connectivity outage or because the host or server is inactive and does not respond to XIDs. To clear this condition, remove the sdlc address address command from the configuration and then reconfigure this command on the SDLC interface. [CSCdi79498]

• SNMP GetNextRequests for cipCardDaughterBoardTable and cipCardClawXferDataStatsTable entries incorrectly reported the cip card slot# for cards installed in slots other than slot 0. For example, a card installed in slot 1 was reported as being in slot 4. [CSCdi79956]

• A SegV exception in CLSCepPongCnf can occur in a rare race condition when APPN to DLC flow control is attempted (internal to the router) simultanously with an APPN link being disconnected. This typically happens on SDLC links, but may not be limited only to SDLC. [CSCdi80473]

• [CSCdi80618]

• FST switching of DLSW through a frame-relay sub-interface is being process switched when it should be fast switched. This is seen by Show DLSW peer. [CSCdi80779]

• It is currently impossible to configure APPN 'route additional resistance' on the appn control point. If the configuration commands are entered, they are ignored and the value for route additional resistance remains the default of 128. [CSCdi81003]

• APPN/DLUR can not establish a session with a frame relay-attached downstream PU. [CSCdi81400]

• When a NN's name changes the topology database has the old NN name in the database with active TGs. [CSCdi81486]

• An APPN connection network will not properly identify a currently active connection between the mac/sap pairs if the connection network is defined over a rsrb or vdlc port ( It works fine over TR and FDDI ports). This causes the session to fail wih sense 80020000. [CSCdi81897]

• Problem happens when u try to do router commands thru nsp. When u come to the Press'Y' for more option, the router aborts the connection. This results in the 'Y' typed from the nsp to go to the run queue on the router instead of the interactive queue. This problem seems to be happening because we terminate connection when PU is not active.. we dont take care of the busy condition.. we should.

Anyways taking care of the busy condition, the router doesnt abort the conncetion and correctly passes the Y to the interactive queue. [CSCdi81927]

• A router might reload when more than 125 sessions on the router are using QLLC/DLSw+ conversion. [CSCdi84896]

• When a downstream PU2.0 stops by issuing a REQDISCONT to a DLUR router, the DLUR router may loop continuously restarting the link to a downstream PU2. In this case, the DLUR router sends a corrupted packet to the host, instead of a REQDACTPU. [CSCdi86769]

• An Invalid packet is being received from the VTAM NN and the CP-CP session is being torn down. [CSCdi87217]

• When source-route bridging is enabled on a Cisco 7500 router in a Token Ring environment, if the router receives a packet that is to be routed but that contains a RIF, the router misclassifies the packet, treating it as a source-route bridge packet, which causes it to be discarded. This may cause intermittent failures of routed protocol sessions. There is no known workaround. [CSCdi87321]

• This fixes APPN DLUR router crash and reload. There was a race condition in the APPN/DLUR code, because of which null pointer was accessed sometime casung SegV violation crash. [CSCdi87325]

• For LU0-LU0 traffic the extended BIND may contain unformatted user data fields. The NN rejects the BIND and hence the session willk never start. [CSCdi87365]

• Release-note: lsap-output-list parameter on a dlsw remote peer statement blocks sna and/or netbios if configured as such, but will only block other types of broadcast traffic from local dlsw interfaces. DLSw routers acting as border peers are not able to use lsap-output-list filters on remote peer definitions.

Workaround: Configure the required filter at the originating router, either at the interface or dlsw level. This is a large administrative task in large networks. [CSCdi87600]

• APPN show commands may cause a DLUR router console to hang. This problem occurs when a race condition is hit during dlur deactivation flows. [CSCdi88581]

• Configuring the output-lsap-list command on the local Token Ring interfaces does not block broadcast traffic from a DLSW peer. The workaround is to use a filter at the DLSW level on either router or to block the traffic with an input-lsap-filter command at the remote peer. [CSCdi88593]

• When running multiple large file transfers across DLSW using FST transport sequence errors may occur causing the job to abort. This is viewed by show dlsw peer. A sequence error occurs when a numbered FST (ip) packet is received by the DLSw peer and the sequence number does not match what the peer expects. [CSCdi89838]

• Release Note for the fix:

This fixes the APPN DLUR router crash with memory corruption. This may happen occasionally and the router often crashes in a function call Mget_x. [CSCdi90441]

• A reload can occur when using the APPN/DLUR feature in extream stress situations (typcially thousands of sessions being cleaned up). The PC (program counter) at the time of the reload will vary. [CSCdi90518]

• PEER INVALID trace messages are displayed on the console. Also, in Releases 11.1 and 11.2, the session on the peer-on-demand does not come up for quite some time. [CSCdi90953]

• A router configured for DSPU may crash with the error "Software forced crash, PC 0x31598BC" if end stations are continually activating and deactivating. [CSCdi91368]

• When running APPN/DLUR, heavy session activation can result in the router using all I/O (buffer) memory available in the router. Often the external symptom of this occurance is the APPN subsystem shutting down. This fix minimizes dlur's buffer usage allowing many more concurrent session activations before I/O memory will be exhasted. [CSCdi91380]

• When running APPN/DLUR sessions, a reload in check_heaps may occur due to a memory overwrite. The memory overwrite occurs if the amount of control vector data in an extended bind response is larger than the buffer that the bind response arrived in. [CSCdi91432]

• The DLUR router may crash with a "SegV exception" or an "Illegal access to a low address" message because of a DLUR memory corruption problem. This error results from a race condition that usually occurs when DLUR sessions are going up and down. The stack trace after the memory corruption usually indicates Mget_x. [CSCdi92947]

• DLSw+ reachability entry may get stuck in VERIFY state. This problem is timer related and likelihood of this happening are low. It will generally occur after several months of operation. [CSCdi93217]

Interfaces and Bridging

• 4000 series routers may reload due a PC error. Seems to be related to increasing the bandwidth on the serial interfaces with hardware type MK5025. [CSCdi36722]

• When "ip route-cache cbus" is configured on an interface, there is the potential for intermittent router crashes due to an incoherent cache entry data structure.

If this incoherency occurs and does not cause a router crash, it may instead cause cbus switching to be automatically disabled, and the interface would resort to fast switching (or sse switching if sse switching were also configured). [CSCdi43526]

• A Cisco 7500 series router does not display a token ring interface's "burned-in" MAC address (BIA) in the correct format. Token ring MAC addresses should be in non-canonical format. 7500 series routers incorrectly use the canonical (LSB first) format. [CSCdi48110]

• Alignment errors may possibly occur when performing transparent bridging at process level to a token ring interface. [CSCdi48465]

• Under certain circumstances, a group of four serial ports on an AS5100 or 2509/10/11/12 router can become unresponsive. Only a reload will solve the problem. [CSCdi58103]

• Kille packets when bridging on FDDI interface receives a packet with DSAP and SSAP = 0xaaaa and length less than 21 bytes, can cause havoc. running IOS 11.0(9.3) or 11.1(4) and the following message is seen:

CBUS-3-INTERR: Interface 6, Error (8011)

This is due to the bridging code was seeing aaaa and assuming it as snap encapsulated. Since SNAP encapsulated packets have a minimum length of 21, the bridging code was subtracting 21 from the original length of the packet (20) when queuing it on the outbound interface. Result. Length of outbound packet was -1 or 65535 bytes. This caused the SP to become confused and writing over low core causing the 8011 error. [CSCdi65953]

• Token ring driver misclassified ipx broadcast packets as srb explorer packets and had them flushed rather than switched while being bridged on LOW end products only (igs xx c4500 platforms). By chance no other protocol packets are affected, this is a ipx broadcast issue only by luck of the logic followed... [CSCdi75134]

• SMDS interfaces use buffers from the Very Big Buffer pool and will have 1/4 the number of buffers as other serial interfaces using different encapsulations. This may cause input drops. As a workaround, you can manually tune the number of very big buffers and the number of permanent buffers for the serial interface. [CSCdi75945]

• Release-note: asyn/sync ports on the 252x series routers will reset for a one second period under rare error conditions. [CSCdi77033]

• Policy routing on a Cisco 7000 router with silicon-switching enabled does not function correctly. As a workaround, manually disable silicon-switching on each of the interfaces with the no ip route-cache sse command. [CSCdi77492]

• This problem can be avoided by not doing a show interface command on a removed FDDI interface. Unfortunately, show techsupport will generate such a command without opportunity for intervention. This patch prevents the software from attempting to read non-existent registers and thereby avoids the errors that result. [CSCdi78254]

• On Cisco RP/SP 7000 series routers, if you reload the router after adding new interface processors or swapping interface processors, the configuration for serial interfaces may be lost. Also, the encapsulation may be lost, causing the serial interface configuration to change to the default (HDLC). You can identify this problem if your interface is a serial interface, for example, an FSIP or a HIP, and the show configuration command correctly displays the original configuration for the serial interface. As a workaround, EOIR the new card, configure it, and issue the write memory command before reloading. [CSCdi79523]

• The FDDI interface driver can interact poorly with OSPF during OIR, causing SPF recalculations. This occurs only when OSPF is running on a FDDI interface which is not being inserted or removed. This fix eliminates the spurious indication from the driver that the SPF recalculation needs to take place. [CSCdi81407]

• FDDI interface on 4x00 platform does not correctly apply/filter MAC address access list. [CSCdi83829]

• RSP routers running Release 11.0(12.3) through 11.0(13.3), including 11.0(13), ignore incoming traffic on FDDI interfaces if SRB being used anywhere in the system (either on TRIP or CIP interface cards). If this problem occurs, turn off SRB. [CSCdi92818]

IP Routing Protocols

• When sho standby command is issued on 4700 (10.3.12) with hsrp configured on fddi int, it shows wrong prioriy and tracking interface status.

After reload with standby track command configured, the tracked interface may be in a wrong state, hence the priority is wrong too.

For the first time loading the image with the fix, standby track command will be deconfigured, and need to reconfigure it again. [CSCdi72254]

• When using route-maps, if a null entry (no set/match commands) is entered under configuration mode, the entry with the lowest sequence number will be overwriten (as long as the lowest sequence number is not equal to 10).

This doesn't seem to affect the order in which the route-map is executed. [CSCdi74891]

• When using BRI IP unnumbered & static default route 0.0.0.0, the default route entry is removed from the routing table for up to 1 minute - upon ISDN B channel disconnecting.

The fix for 11.2 introduced CSCdj02347 and CSCdj02729. [CSCdi77493]

• DVMRP Tunnels that are shutdown or have no ip address configured still pass reports and accept probes, but do not forward traffic. Make sure that you have configured "ip address" or "ip unnumbered" or that the interface is "no shut" if there appears to be DVMRP traffic but no multicast data traffic. [CSCdi81183]

• When a router is the source of multicast packets, and if it is the DR with multiple interfaces, there is a chance it may only send one data register and stop sending subsequent ones. [CSCdi81305]

• This bug causes (S,G) state to be immediately deleted in the RP when a Register is received. [CSCdi82581]

• A router might advertise a combination of unicast and DVMRP routes in excess of the configured route limit (but no more that two times the limit). The workaround is to configure a lower route limit. [CSCdi85263]

• During topology changes, a lot of OSPF update packet could be generated and flooded through out the network and overload the network. This overload situation can cause OSPF to lose neigbors. [CSCdi85902]

ISO CLNS

• After removing a static CLNS route, ISO-IGRP prefix routes may be seen to count to infinity around a looped topology. The workaround is to use no clns router iso-igrp DOMAIN to break the loops in the CLNS topology untill the routes age out. [CSCdi78048]

• CSCdi78048 introduced a bug that ISO-IGRP will not redistribute the local ISIS route. [CSCdi85861]

• Router memory leaks if router receives a CLNS packet with invalid destination address length.

There is no workaround of this problem. [CSCdi90052]

Novell IPX, XNS, and Apollo Domain

• NLSP links may reflect incorrect source network/node addr in the routing tables. This does not hinder connectivity to other IPX networks when going cisco to cisco. However, certain non cisco routers may not like the incorrect address and NLSP routing may fail. NLSP routers should use the address Internal-Network.0000.0000.0001 when sending NLSP packets, therefor on WAN media which require MAPs for IPX this should be the next hop address in the map statement. [CSCdi68981]

• NLSP may reflood LSP fragments unnecessarily, including both changed and unchanged fragments. Typically this is not a problem on LAN circuits. However, this can present bandwidth-related problems on low speed WAN circuits, especially as the size of the network increases.

The flooding behavior covers up a problem where services may be missing from the SAP table until the next full SPF. This is not a problem when all neighbors are Cisco routers, but can be a problem when third party routers are present on the same link. [CSCdi74487]

• When a packet is too large for the output interface the packet is dropped per IPX specification, the debugging message associate with this action is confusing as it lists only the input interface not the output interface on which this action was taken. The debugging message should list the output interface name. [CSCdi76741]

• In a redundant ipx eigrp network running ipx incremental sap, the router's sap table sap information may contain out of date information, such as the socket number if the socket number is changed from its initial advertisement. [CSCdi85953]

• SPX keepalive spoofing will cease to spoof after a router has been up for 24+ days. Debug ipx spx-spoof will show packets being "skip"ped at the time when they should be spoofed. The only workaround is to reload the router once very 3 weeks. [CSCdi86079]

• XNS RIP requests for all networks causes normal periodic RIP updates to be delayed or skipped. [CSCdi90419]

• When IPX incremental SAP is running, the router's SAP table may not contain all the SAPs in the network if one of it interfaces goes down and comes back up later. [CSCdi90899]

• When running IPX incremental sap, the router may not remove all the SAPs that are no longer reachable via this router. [CSCdi90907]

Protocol Translation

• Protocol translation (tcp to x25) router continually tries to negotiate telnet window-size, causing high cpu utilization. [CSCdi86983]

TCP/IP Host-Mode Services

• When a Cisco 4500 or Cisco 7000 is configured to use FTP or RCP to take an exception dump and an exception happens with validblock in the stack trace, the core dump operation fails and a core file cannot be obtained. As a workaround, if validblock is in the stack trace, use TFTP to take the exception dump. This means that the exception dump is limited to 16 MB. This is a known TFTP defect. [CSCdi75757]

• Non-TCP reverse connections to lines may corrupt memory, resulting in a software-forced crash. This problem was introduced starting in Releases 10.3(15.1), 11.0(11.1), and 11.1(6.1). [CSCdi79310]

• Router will reload if TCP tries repacketize a packet that has invalid packet reference count. [CSCdi87175]

• If you have a route to the all ONES subnet via Null0, a packet that should be interpreted as an all nets broadcast (i.e., when using spanning-tree based udp flooding), is discarded. [CSCdi88587]

VINES

• If you add a vines static route of equal metric for an alternative path when vines single-route is configured, the system may reload. The workaround is to delete the static route or enter no vines single-route command. [CSCdi92190]

Wide-Area Networking

• When Insertion and Removal is applied to a VIP2 board, this may cause an ATP interface processor (AIP) to remain stuck into an uninitialised state. The following messages may appear: CBUS-3-CMD: Cmd failed: global ptrs, response 0x8010, AIP1 CBUS-3-AIPRSET: Interface ATM1/0, Error (8010) select - aip_reset() CBUS-3-AIPRSETU: Unit 32, Error (8010) enable - aip_reset() The workaround is to reload the router. [CSCdi75659]

• IPX fast switching with multiple route paths over multiple ATM/LANE interfaces/subinterfaces may cause random system reloads. Workaround is to use only one AMT/LANE IPX path, set ipx maximum-path 1, or use ipx per-host-load-balance to force only one interface to be used. [CSCdi77259]

• Deb lane cl pa / deb atm pac gives the following:

ATM3/0.2(I): VCD:0x5 Type:0x6, LANE, ETYPE:0x0006 LECID:0xFF00 Length:0x70 FF00 0101 0008 0000 0000 003A 0003 0000 0000 0000 0000 0000 0001 0000 0C07 AC00 4700 9181 0000 0000 603E 5A45 0200 000C 5B7B 1202 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

LEC ATM3/0.2: received UNKNOWN on VCD 5

0008 looks like an LE_NARP packet which is reported as UNKNOWN by deb lane client. The clearing of the LE_ARP entry occurs correctly.

During another test, we get for instance:

nestor#sho lane le-arp Hardware Addr ATM Address VCD Interface 0000.0c5b.7b12 47.00918100000000603E5A4502.00000C5B7B12.02 13 ATM3/0.2 0000.0c07.ac00 47.00918100000000603E5A4502.00000C5B7B12.02 13 ATM3/0.2 0000.0c02.7f86 47.00918100000000603E5A4502.00400BC81840.02 12 ATM3/0.2 nestor# LEC ATM3/0.2: received UNKNOWN on VCD 5 nestor#sho lane le-arp Hardware Addr ATM Address VCD Interface 0000.0c02.7f86 47.00918100000000603E5A4502.00400BC81840.02 12 ATM3/0.2

This is just a cosmetical problem. [CSCdi78737]

• In 11.0(13), routers will reload when the "no frame-relay priority-dlci-group" command is entered.

The work-around is to first remove any "frame-relay interface-dlci" commands and THEN remove the "frame-relay priority-dlci-group" command. [CSCdi85395]

• If dlci-prioritization is enabled on an interface and low/medium/normal priority DLCI is same as high priority one, router may not inverse-arp after router-reload, shut/noshut. This may cause loss of ip connectivity as frame-relay map will not exist. Workaround for this bug is to first remove the dlci prioritization and then add it back after the router has inverse-arped for the remote ip address. [CSCdi85414]

• This situation occurs when the LES tries to connect to the LECS thru its back end connection and can not, usually becoz of the fact that the LECS is not configured properly, or that the LES has been "mis-directed" to a wrong and unconfigured LECS address.

The workaround is to have the LECS configured properly before the LES attempts to connect to it.

In other words, have a completely operational LECS AND configure its address properly for the LES, before the LES comes up. [CSCdi87660]

11.0(12) Caveats/11.0(13) Modifications

This section describes possibly unexpected behavior by Release 11.0(12). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(12). For additional caveats applicable to Release 11.0(12), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(13).

AppleTalk

• When using ARAP on a terminal server you may experience issues with modem answering calls with no connection. Reloading the router will fix the problem [CSCdi73132]

Basic System Services

• When a 1000 router or a 2500 router run low on memory (less than 32K) the command 'write terminal' fails to generate any output. [CSCdi40791]

• If an snmp view which had previously been configured with the snmp-server view command is deconfigured, and then reconfigured, any snmp communities which utilized the view will no longer work. [CSCdi47796]

• The boot config nvram: configuration command, which was added for the RSP platform, interacts improperly when the service compress-config command is enabled. The boot config command causes the NVRAM to lock up, and the router must be rebooted to free the NVRAM. [CSCdi52587]

• When using a Secure Dynamics TACACS+ server for authentication, the server might ask the user to stop and wait for the next token. The user must press any key or provide some sort of input at least every 30 seconds, or the router will time out the user. [CSCdi55474]

• The verify flash command has online help documentation but is unsupported. [CSCdi62272]

• Occasional SNMP linkDown traps coming from Ethernet interfaces in which the variable locIfReason (the reason why it went down) says, "Keepalive OK." These traps are due to the interface momentarily and harmlessly losing carrier. You can ignore them. If they become a nuisance, you can remove them by issuing a no snmp trap link-status command. [CSCdi63434]

• AAA authorization and accounting transactions to the TACACS+ server can be delayed by 9 seconds if DNS is not configured on the router. Workaround is to enable the global configuration "no ip domain-lookup". Whenever the router needs to establish a connection to your Tacacs+ server, it will attempt to look up your server's IP addresses.

If the IP address of your Tacacs+ server does not exist in your local host table and you do not have DNS configured, you may experience a 9-second delay before connecting to the server.

To resolve this problem, do at least one of the following:

1) add "no ip domain-lookup" to your configuration. 2) add the IP address of your Tacacs+ server to your local host table. [CSCdi70032]

• In cases where an accountable task has a duration shorter than the time is takes to contact the tacacs+ accounting server, the stop record may be discarded by IOS without being transmitted to the server. [CSCdi70312]

• The first attempt to use a menu command fails authorization as it should, but subsequent attempts succeed. [CSCdi72822]

• for the following error messages

%RSP-3-ERROR: RP parity error %RSP-3-ERROR: SRAM parity error %RSP-3-ERROR: QA parity error %RSP-3-ERROR: CyBus0 parity error %RSP-3-ERROR: CyBus1 parity error

a bitmask follows to indicates which bytes (0-7) had bad parity. The bits indicating bytes 0 & 1 are actually in bit positions 9 & 8 instead of bit positions 7 & 6. [CSCdi74453]

• Timer-related functions, such as NTP and routing update intervals, do not work correctly in Revision D Cisco 4700 routers. Also, Revision E Cisco 4700 routers are recognized by SNMP as "4700" instead of "4700M." [CSCdi75353]

DECnet

• Allow DECnet IV router adjacencies to be added to the Phase V (OSI) data base.

The previous version of the code allowed only end-system adjacencies to be added to the Phase V data base. [CSCdi77560]

EXEC and Configuration Parser

• The router will crash if you issue a command line that is an alias and that is greater than 256 characters in length after the alias is expanded. [CSCdi63994]

IBM Connectivity

• When using APPN/DLUR and starting and stopping many sessions to downstream dependent LUs, the router may stop with a bus error at ndr_queue_handler. [CSCdi52377]

• OIR of an IP in a 75xx router equipped with a CIP and another IP that has the same size MTU as the CIP can cause the router to crash with a cbus error. [CSCdi59377]

• The following instruction disappears on reboot on a 7000 running 10.3-9: source-bridge remote-peer 1280 frame-relay interface Serial1/1.3 404 lf 4472 [CSCdi59935]

• QLLC DLSw cannot reconnect after a failure. The following assert message is displayed: %CLS-3-CLSFAIL: CLS: Assertion failed: file "../srt/qllc.c", line 4352 !"QSapAddCepFailed". [CSCdi64840]

• Router is loosing a 'fras map' statement from the config after the router reloads. In boot-up time the following error appears: fras map llc 0200.0060.0080 4 4 Serial0.1 frame-relay 100 4 4 ^ % Invalid input detected at '^' marker.

Once the router reloads a 'config mem' can be done to add the statement back. [CSCdi67719]

• This crash occurs when both SRB and other kinds of traffic are used on the same router. It causes a crash with a traceback like the following:

ALIGN-1-FATAL: Illegal access to a low address addr=0x1, pc=0x60544FE0, ra=0x60544FE8, sp=0x60AEE780

0x604C23EC:llc_store_rif(0x604c23c0)+0x2c 0x604BE390:llc2_input(0x604be128)+0x268 0x6014BD28:llc_input(0x6014bc64)+0xc4 ... Somewhere in the drivers.

It is exacerbated by increasing loads. There is no workaround. [CSCdi69234]

• APPN over FDDI support does not work correctly when SRB/FDDI is in use between the APPN endpoints of the connection to bridge either FDDI to FDDI or FDDI to Token Ring. APPN over FDDI does work when both APPN connection endpoints are on the same FDDI ring. [CSCdi69841]

• The APPN sub-system may reject a VDLC port definition when removing it and adding it back. This only occurs if you have a single VDLC port definition in APPN and no link station active and no link station definitions. To have the system accept the definition you will need to stop and start APPN. [CSCdi69930]

• If source-route bridging (SRB) explorer traffic is so low that no explorer is forwarded on a Token Ring interface for 25 days, then the Token Ring interface stops forwarding SRB explorers. The show source command shows that the "flushed" count increments for every explorer received, while no "expl_gn" explorers are counted to the remote peers. This problem causes connectivity loss. On more recent products, such as the Cisco 7500 series, these symptoms can occur on very active Token Ring interfaces after the Cisco IOS software is reloaded. A short-term workaround is to reload the affected router. [CSCdi70559]

• DLSw may fail to carry circuits when the interface command source-bridge local-ring bridge target-ring is removed and then re-added. [CSCdi70595]

• When configured for SDLLC and using 11.0(10) or 11.1(5) and the remote SDLC device goes offline, it may be necassary to clear the LLC session on host end inorder to re-establish the session. [CSCdi70911]

• An SNMP request for the cipCardEntry information will produce the following message

%ALIGN-3-SPURIOUS: Spurious memory access made at reading

on a 75xx. [CSCdi72059]

• When using RSRB with FST encapsulation, the router may crash if there is more data to forward onto the virtual ring than there is bandwidth to accept it. [CSCdi72427]

• A bug introduced by CSCdi69231 may cause NSP to stop working. The images affected are 11.0(11.2) 11.1(6.2) 11.2(1.1). The following messages may display when NSP stop working: SNA: Connection to Focal Point SSCP lost. The above message appears for no reason. SNA: MV_SendVector rc = 8001 [CSCdi72696]

• Remote source route bridged traffic using FST encapsulation will be process switched under certain circumstances on some platforms. [CSCdi72962]

• When doing RSRB with FST encapsulation in 11.0(11) the packet counts reported by the sho interface commands are not necessarily accurate. [CSCdi72968]

• A hang of APPN's APPC stack (used to send locates and TDUs) can occur in rare situations when an outbound locate or TDU is in the process of being transmitted on a CP-CP session at the exact time that session is terminated (due to link failure or other reason). The APPC component does not handle this situation properly, and after the condition occurs, APPC and all locates and TDU processing become stuck. [CSCdi73085]

• Data-link switching (DLSw) sometimes cannot handle disconnects being issued by two stations that are in session, if the stations have a requirement to re-establish a session in less than 3 seconds. The first disconnect is answered with a UA message but the second is not responded to until the station resends the disconnect message (DISC). After the DISC is resent, a DM message is sent to answer. [CSCdi73204]

• Frames coming from a High-Speed Serial Interface (HSSI) are sometimes dropped. This problem occurs when a Cisco router has remote source-route bridging (RSRB) configured direct over a HSSI interface. The HSSI interface shows that the packets are forwarded on the interface itself, but the packets are not passed to the source-route bridging (SRB) process. The show source command on FHDC-1 shows receive cnt:bytes 0, and the show interface h 5/0 command shows nonzero packets are input. [CSCdi73357]

• An APPN/DLUR router cannot establish an lu-lu session with a downstream DSPU router. The bind sent by the host is rejected by the DLUR with a x'0806002b' sense code. [CSCdi73494]

• When more than 38 sdlc devices are configured upstream and downstream using DLSw local switching, the router crashes with :

Exception: Line 1111 Emulator at 0x7E9500 (PC) [CSCdi73675]

• When many sessions are created and then torn down over an ISR network, a memory leak might occur in the router. [CSCdi73676]

• Due to a bug, appn link station can not be defined as "auto-activateable" link. [CSCdi73918]

• Show ext ch x/2 tcp-c d doesn't show the relevant output for TN3270 server related sockets and connections. [CSCdi74448]

• Release-note: In early 11.0 only IOS versions, a condition where giants are recieved at the async/sync port can cause a lockup condition at the port. [CSCdi74484]

• A Format 0 XID may be forwarded on the X.25 interface before a Null XID is received on that X.25 interface when QLLC npsi-poll is configured. [CSCdi75628]

• If SNA/DSPU receives a RECFMS frame that contains control vectors and the RECFMS cannot be forwarded to the focal point host for any reason (for instance, the focal point is inactive), the negative response sent by DSPU causes the router to display the BADSHARE error and deactivate the connection. [CSCdi76030]

• If a BIND request is received before the Notify response has arrived, DSPU will reject the BIND request with sense code 0x80050000. [CSCdi76085]

• DLSw+ caches reachability entries forever in status SEARCHING if the first local exploring fails. [CSCdi76433]

• For an APPN/DLUR router, a "DLUS command" specified on the link station to the downstream DLUR device may not work correctly. The link station defined for the downstream device may repeatedly start and stop. [CSCdi76630]

• When a user writes a previously configured APPN configuration, and then reloads it, the following message may be displayed for each link station defined:

dlur-dspu-name > % Incomplete command.

This message, while a nuisance, does not cause any problems. [CSCdi76709]

• DSPU configuration of contiguous, dedicated LUs on separate hosts is not written to NVRAM correctly.

e.g.

dspu pu TESTPU xid 05d00001 dspu lu 1 1 host host1 1 dspu lu 2 2 host host1 2

...is written to NVRAM as...

dspu pu TESTPU xid 05d00001 dspu lu 1 2 host host2 1 [CSCdi76858]

• show dlsw reachability exec command causes the router to crash if a resource like netbios name is reachable through multiple peers or ports and the reacability entry for the resource goes into a VERIFY state. [CSCdi77667]

Interfaces and Bridging

• In rare situations, on ciscoBus interfaces on a Cisco AGS+ router, the router might stop accepting packets after you enable transparent bridging. Issuing the show controllers cbus command shows a Receive Queue Limit (RQL) of 0 for the affected interface and an unusually large RQL value for other interfaces. Issuing the show interface type number command shows an Ignore counted for every packet received on the affected interfaces. To recover from this problem, reload the router. To work around the problem, disable transparent bridging on the affected interfaces. [CSCdi54727]

• The variable locIfotherInPkts in SNMP might not reflect a correct value compared to the total packets counted. [CSCdi56828]

• Bridging between sde encaps and atm (or any encap that we define interface flag span_process_bridge_force such as smds frame relay, X25 )such that slowswitching is the forced output bridging mode, the transition from sde encaps TO a forced slowswitch output encaps (such as atm in 103 code) does not properly prepare this packet for process level. [CSCdi65959]

• Under certain conditions Spanning Tree Protocol can cause a memory leak.

You'll see the small buffers being created but not released (Created is going up and Trims doesn't in the show buffer) and the show memory will show the memory available going down.

Spanning Tree BPDUs are handled by small buffers , so when a BPDU comes in a small buffer is used , if at the same time the interface is going down , this small buffer should be released, and that was not the case...

This problem has been fixed in the IOS software code. [CSCdi72783]

• The cxBus controller may end up in an output hung state when using a MIP under moderate load. As a workaround, you can set the MIP tql (tx-queue-limit) to greater than 32 and make sure that fancy queueing (WFQ/CQ/PQ) is not use on the MIP interface. To stop the outhung message cycling, clear the affected T1 controller (clear controller t1 x/y). [CSCdi73106]

• In Cisco 7500 series routers, the following error message might be displayed while booting the system image from TFTP or Flash memory, or when changing the serial encapsulation (for example, from HDLC to SMDS) or when doing OIR of another card in the chassis:

%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot x, cmd code 0

The show diag x command reports that the board is disabled, wedged. The show version command does not show the card in the specified slot. The write terminal command does not show the configuration for the card in the slot. A possible workaround is to issue a microcode reload command or load a new system image that has the fix for this bug. [CSCdi73130]

IP Routing Protocols

• The show ip eigrp topology command should show the administrator tag.

Also need DDTS CSCdi77369. [CSCdi34362]

• IP multicast fast switching may stop switching traffic through an AGS+ router. To work around, configure no ip mroute-cache on all interfaces forwarding IP multicast packets. [CSCdi45353]

• The command show ip ospf database database-summary can intermittently cause router reloads. [CSCdi63817]

• The spurious access errors occur due to a race condition in the intialization code.

It does not affect the normal running of the router. [CSCdi64005]

• Routes learned over dialer interfaces may not go away after the interface goes down. The workaround is to issue the clear ip route command. [CSCdi65211]

• This affects only multicast packets. When multicast fastwitching is enabled on a 7000, and the input rate results in output queue build up, packets are incorrectly dropped and the statistics are not correct. Workaround is to turn off multicast fastswitching on the outgoing interface. [CSCdi65568]

• A Management Information Base (MIB) query of the ospfLsdbTable fails because no MIB objects are found under the ospfLsdbTable subtree. However, some subtrees under OSPF can be successfully queried, such as ospfGeneralGroup, ospfAreaTable, and ospfIfTable. [CSCdi69097]

• show align reports misaligned memory accesses. This error is reported on a 7513 with a token-ring interface installed. This bug is automaticly detected and corrected by the router. It will not inhibit the normal operation of the router. [CSCdi69939]

• Clearing an IP host route (i.e. 10.1.1.1/32) learned by OSPF out of the IP routing table can take a long time for the network route (i.e. 10.1.1.0/24) to reappear in the table when done on a stable network, and when only the net route, not the host route, exists in the table. To avoid this problem, clear the network route exactly as it appears in the IP route table; do not clear the host route. [CSCdi70175]

• EIGRP may not retain the best route from topology into routing table when variance and metric weights are configured. [CSCdi72459]

• Router running IRDP & IGMP won't accept IGMP reports after a reload.

Workaround is to issue shut and no shut commands to the interface which isn't receiving the IGMP reports. [CSCdi72642]

• The system suffers a gradual loss of free memory whenever ip sd listen or ip sdr listen are enabled. [CSCdi72863]

• Use of the DNS Name Service for alias lookups causes the router to reload. Lookups of canonical names do not exhibit this problem. [CSCdi73022]

• The password configured in a BGP peer-group will not be used by members of that peer-group. The workaround is to manually configure the password for each neighbor in that peer-group. [CSCdi73179]

• On AGS+, MGS, or CGS routers configured with CSC-1R or CSC-2R token-ring interfaces, IP fastswitching can fail under some circumstances. As a workaround, one can disable weighted fair-queuing on all interfaces with the "no fair-queue" interface command and reload the router. [CSCdi73785]

• When OSPF hello timer, and hence the dead timer, is changed, the wait timer is not changed accordiingly to match the dead timer's value.

This fix resolves the problem. [CSCdi74009]

• This crash happens only in 11.2. In previous releases, this bug causes spurious access.

The problem happens only when the router have a single interface with OSPF running over it as broadcast/non-broadcast network. If the single interface is shutdown and is brought back up within a 5 seconds interval, it creates a race condition which causes the crash (or spurious access). [CSCdi74044]

• Using the "talk" keyword when specifying an ip extended access-list is not functional. Workaround is to use the udp or tcp port number (517) specifically. [CSCdi74214]

• When the cache is populated, the system will not perform correctly policy routing on subinterfaces. This has been produced on 4500 with atm lane subinterfaces. The problem does not occur when ip route cache is cleared. [CSCdi74375]

• ARP debugging messages that indicate an ARP response was filtered for being on the wrong cable do not contain information about the source interface making it impossible to troubleshoot. [CSCdi75342]

ISO CLNS

• If encapsulation changes after configuring static CLNS adjacency, it is required to delete the adjacency and reconfigure it. [CSCdi60457]

• If an interface is down when it is configured as passive for IS-IS, it will not be advertised in IS-IS link state packets when the interface comes up. The workaround is to unconfigure the interface and then reconfigure it as passive after it is up. [CSCdi76431]

Novell IPX, XNS, and Apollo Domain

• Every time the router receives a sap update..the age timer in show ipx serv det' resets to 0. This is a cosmetic bug does not affect any performance. [CSCdi66723]

• Some Service Advertisement Protocols (SAPs) might not be seen if an interface is flapping while running IPX Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) and the ipx sap-incremental command is configured. As a work around, clear the IPX Enhanced IGRP neighbors. [CSCdi72438]

• If the ISIS or NLSP LSP refresh interval and LSP lifetime values are both reduced from the default value, the LSP lifetime will be ignored when the system is restarted.

The workaround is to hand-configure the parameters in the reverse order. [CSCdi72691]

Protocol Translation

• Under some conditions, the X.29 profile may not be set on a call to a Virtual Async protocol translation address. This may result in the communication failing, if the calling PAD does not already have the correct parameters for transparent communication. [CSCdi73090]

• A protocol translator may unexpectedly restart when a translation entry is configured but fails to be successfully added due to system limitations, such as exceeding the number of LAT services that can be advertised. [CSCdi76145]

TCP/IP Host-Mode Services

• Cust is seeing a crash in 11.1.5 code PC 0x12CFA8, address 0xD0D0D11 [CSCdi70432]

VINES

• VINES broadcast packets are forwarded away from the source. If the immediate router toward the source of a broadcast packet has a neighbor entry but no associated path, the system may halt. This kind of dangling route is rare and is considered a timing-related issue. [CSCdi75345]

Wide-Area Networking

• PRI ISDN calls may be dropped on heavily loaded Cisco 7513 routers with multiple PRIs. The following error is displayed when this occurs: BRI Error: isdn_fromrouter() msg dequeue NULL. [CSCdi66816]

• 4500/4700 unable to get complete large (Problem already appears with 1500 bytes frames) if no traffic shaping is performed on the incoming atm traffic. The system will report CRC errors even for a traffic of 500 pps and will only forward 100...300 pps. When traffic shaping is applied on the traffic generated, we get a throughput superior to 2000 pps. [CSCdi68586]

• ATM interface on 4x00 may go down in a down/down state with the atm error of "atmzr_dumb_inhand(ATM0):Secondary port error". The interface will not come up untill a reboot is done or interface is flapped by doing a Shutdown and no shutdown. [CSCdi72769]

• An async PPP interfaace does not correctly support a reduced MTU using the 'mtu xxx' interface configuration command. Problems will appear when attempting to upload files or other large transactions. [CSCdi72866]

• The interface command:

mac-address XXXX.XXXX.XXXX

now MAY affect any LANE components' atm and/or mac addresses, since the esi portion of an auto generated atm address is created using the mac address of the interface.

Also note that this command actually causes a hardware reset on the card that is being executed. Hence, all LANE components on such a card will recycle anyway. But as to whether the atm addresses they listen on after they come back up again will change, actually depends on how those addresses were defined in the first place.

If they were defined using the "auto" addressing method, obviously their esi portions will be affected.

In the case of an LEC (LANE Client), the mac address of the client will also change as well.

****** Note that this fix broke DECNET, which is now fixed. So, the correct version that has BOTH the fixes in is 11.2 (2.2) ****** [CSCdi73530]

• PAD connections made from lines configured with session-timeout values can be incorrectly closed, because data sent or received on the line does not restart the session-timeout timer. [CSCdi74095]

• After a number of days PRI calls may be dropped, high ISDN CPU utilization may be seen. There may be some discrepancy between 'show dialer' which indicates free B channels available and 'show isdn service' which shows all channels busy. Ultimately, a software forced crash occurs. [CSCdi75167]

• If a PAP Authentication Request is resent because of a timeout or missed response and is received after the router has completed processing of the first request, then it will repeat the authentication process. It should not repeat the authentication process. Instead it should send back the same response message that it did for the first message, regardless of the contents of the second (or subsequent PAP Authentication Requests). This defect will be fixed in a future release of IOS. [CSCdi76763]

• The negotiation of a PPP Callback option, passing a dial string or E.164 number, will fail due to a defect that was introduced into 11.2(1.4), 11.1(7.1), 11.2(1.4)P, 11.2(1.4)F, and 11.0(12.1). The negotiation will appear to complete successfully, but the callback will not succeed. The failure can be seen if 'debug ppp negotiation' is set. The callback option will be marked 'acked', but there will typically be garbage on the debug line between 'allocated' and 'acked', eg 'PPP Callback string allocated ^]" acked'. There is no workaround for this defect. The defect will be fixed in a future release of IOS. [CSCdi77739]

11.0(11) Caveats/11.0(12) Modifications

This section describes possibly unexpected behavior by Release 11.0(11). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(11). For additional caveats applicable to Release 11.0(11), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(12).

AppleTalk

• It is not possible to connect an ara client using a username with 'nopassword' or without a password configured in the router. [CSCdi53202]

• Over a period of three to five weeks, an active commserver will slowly run out of I/O memory. This may be related to ARAP or Tacacs+ usage. [CSCdi61152]

• There has been a request for additional debugging messages for the arap logging command. The requested command is arap logging debug-extensions, which enables seven advanced debugging messages in addition to the traditional ARAP logging messages. [CSCdi68276]

• AppleTalk domains do not operate correctly when configured on subinterfaces. The domain properties will be applied to the main interface rather than it's subinterface(s). The workaround is to disable AppleTalk fast-switching. [CSCdi69886]

• The AT Domain system process is always started on system bootup, whether or not it is needed. There is no operational impact. [CSCdi71120]

Basic System Services

• The copy startup-config tftp command is an interactive command. You cannot specify a filename on the command line. [CSCdi38765]

• The router may reboot when the following snmp variables are used:

writeNet, hostConfigSet, netConfigSet [CSCdi50407]

• If you see the message "%RSP-3-RESTART: interface Serial x/y, output stuck" on an RSP-based platform, you might have problems with the output interfaces. This problem can occur when bursty traffic is optimum-switched to an output interface on which either fair queue or transmit-buffers backing-store is enabled. A possible workaround is to disable optimum switching. [CSCdi56782]

• When "hold-queue out" command is entered, "show int" reflects the new hold queue value. After "wri mem" and reloading the router, "hold-queue out" disappears from the configuration and "show int" shows the default hold-queue out setting of 40. The "hold-queue out" command has to be reentered everytime a reload happens. [CSCdi58292]

• When using AAA authentication for enable passwords, the HTTP server in the IOS will never allow a user to access it. [CSCdi66938]

• If a system is configured with "ntp master" and has no other NTP associations, it may eventually report that it is unsynchronized.

A workaround is to ensure that there is at least one other NTP association (by configuring an "ntp server" or "ntp peer" on the system, or by changing one of the other systems to use "ntp peer" with the master rather than "ntp server"). [CSCdi67635]

• When service compress-config is configured, accessing the configuration stored in NVRAM from simultaneous Exec sessions might leave the NVRAM locked and inaccessible. The only recourse is to reload the software. [CSCdi68092]

• 'telnet transparent' in 'line vty' settings causes HTML pages to appear to lose some of the characters in the displayed page due to null characters in the page output. [CSCdi68224]

• When a server has multiple entries defined in the DNS, Tacacs+ will normally try each of these aliases in turn when trying to open a connection to a daemon.

If a daemon returns an error after a connection has been successfully established however, no more aliases for that daemon will be tried. Instead the daemon will try the next server configured in its list of servers.

One workaround is to order the list of tacacs-server hosts configured on the NAS to increase the likelihood that the desired daemon will always be selected. [CSCdi68816]

• The command debug chat line x and parser do not display the chat script components correctly if the octal 7 or 8 bit xxx format is used to specify a byte greater than 0 x7f. [CSCdi69149]

• The IP address of the dialup interface that is trying to acquire a temporary IP address for the peer, is not being used as the source of the DHCP proxy client packets sent from the Access Server. [CSCdi69448]

• TACACS+ accounting will include an attribute "address", which is not defined in the tacacs+ specification. The correct attibute name is "addr". [CSCdi70146]

• Chat scripts cannot send a NULL byte out on the async line. IOS chat scripts do not support N escape-sequence which has been used conventionally for this purpose. [CSCdi70330]

• If you have a standard SunOS/Solaris Telnet server, and if the NAWS option is mistakenly sent, the Telnet server hangs instead of ignoring NAWS. [CSCdi71067]

• A problem has been found in RSP code within Cisco IOS releases 10.3, 11.0, 11.1, and 11.2. The failure condition can occur when BACKING-STORE or fair queuing are enabled. The conditions that could cause one of the above behaviors to occur are expected to be extremely rare. However, to avoid these problems, all Cisco IOS RSP releases previous to those listed in the chart below are no longer available.

Cisco highly recommends upgrading all RSP-based systems to one of the Cisco IOS release identified below. For those systems that cannot upgrade, this problem can be avoided by disabling both BACKING-STORE and fair queuing. Please see instructions for this at the end of this message.

When packet load on RSP-equipped systems causes datagrams to be forwarded from SRAM to DRAM, a function of BACKING-STORE, 32 bytes of data may be randomly written into DRAM. This could result in several anomalous system behaviors including: - Software-induced system crashes - Dropped datagrams - Other anomalous errors

To eliminate this problem, Cisco highly recommends downloading and installing one of the following Cisco IOS releases:

Base Rel. Maint Rel. On CCO 10.3 10.3(16a) 11/15 11.0 11.0(12a) 11/22 11.1 11.1(7)CA1 11/18 11.2 11.2(1a) 12/9

The default Cisco IOS image for all new RSP-based router shipments is Cisco IOS release 10.3(16a) effective immediately.

SOLUTION:

FOR CUSTOMERS WITH RELEASE 10.3 Option #1: Cisco highly recommends the installation of one of the above listed Cisco IOS releases.

Option #2: Below are options to work around this bug.

1) Simply disable backing store on each interface with IOS command 'no transmit-buffers backing-store' Please note each interface needs this disabled.

Backing store defaulted to OFF in images beginning with ... 10.3 (12.3 ) 11.0 ( 9.2 ) 11.1 ( 4.1 ) 11.2 ( 0.14) from ddts CSCdi57740.

However, it is important to look at the current configuration. An image configured before backing-store defaulted to OFF may have it ON for router interfaces.

FOR CUSTOMERS WITH RELEASE 11.0, 11.1 or 11.2

Option #1: Cisco highly recommends the installation of one of the above listed Cisco IOS releases.

Option #2: Below are options to work around this bug.

1) Disable backing store AND fair queuing on each interface with IOS commands

'no transmit-buffers backing-store' 'no fair-queue'

ALSO disable udp-turbo flooding if the image is 11.0 or later The IOS command to disable UDP turbo flooding is 'no ip forward-protocol turbo-flood' which is OFF by default in all releases.

Backing store defaulted to OFF in images beginning with ... 10.3 (12.3 ) 11.0 ( 9.2 ) 11.1 ( 4.1 ) 11.2 ( 0.14) from ddts CSCdi57740.

However, it is important to look at the current configuration. An image configured before backing-store defaulted to OFF may have it ON for router interfaces. [CSCdi71609]

• The system may occasionally produce the following error message:

%SYS-3-MGDTIMER: Running parent with no child

This message is cosmetic in nature and has no impact on the health of the system. There is no workaround to this problem. [CSCdi72401]

• If a system is configured to be both an NTP broadcast client (using the "ntp broadcast client" configuration) as well as an NTP unicast client (using the "ntp server" configuration), and the unicast server is also acting as a broadcast server, the system will not synchronize with the server at all.

The workaround is to configure the client as either unicast or broadcast, but not both. It may also be necessary to remove and reconfigure the "ntp server" configuration if the system is to be a unicast client. [CSCdi72452]

DECnet

• DECnet may fail to work properly when using an area number of 63 for L2 routers. The symptoms are being unable to ping (decnet) between two area routers, one of which is using area 63.x, and having the show dec command report that the 'attached' flag is false even though the show dec route command shows routes to it. The workaround is to use the decnet attach override command to force the router into an attached state. This command is available in Releases 10.2(7.3), 10.3(4.4), 11.0(0.13), and all versions of Release 11.1 and higher. [CSCdi69247]

EXEC and Configuration Parser

• Under some circumstances, the AS5200 may run low on memory or may run out of memory after processing more than 11,000 calls. A small amount of memory may be lost under two conditions, only when aaa new-model is configured: when a user hangs up at the "Username:" prompt, or when a user successfully autoselects with the autoselect during-login command configured. [CSCdi67371]

• When a show ip arp command is executed on the router, the router sends DNS lookups under following conditions. This is a cosmetic bug in the parser code.

Router#sh ip arp ? Ethernet IEEE 802.3 H.H.H 48-bit hardware address of ARP entry Hostname or A.B.C.D IP address or hostname of ARP entry Null Null interface Serial Serial cr

RioGrande#sh ip arp Protocol Address Age (min) Hardware Addr Type Interface Internet 10.6.1.51 - 0000.0ca0.5d00 ARPA Ethernet0/0 Internet 10.6.1.71 1 0000.0c07.9b41 ARPA Ethernet0/0

RioGrande#sh ip arp 0000.0c07.9b41 Translating "c07.9b41"...domain server (255.255.255.255)

Protocol Address Age (min) Hardware Addr Type Interface Internet 10.6.1.71 1 0000.0c07.9b41 ARPA Ethernet0/0

Router#sh ip arp 10.6.1.71 Protocol Address Age (min) Hardware Addr Type Interface Internet 10.6.1.71 2 0000.0c07.9b41 ARPA Ethernet0/0 RioGrande#

Router#sh ip arp e 0/0 Translating "e"...domain server (255.255.255.255)

Protocol Address Age (min) Hardware Addr Type Interface Internet 10.6.1.51 - 0000.0ca0.5d00 ARPA Ethernet0/0 Internet 10.6.1.71 8 0000.0c07.9b41 ARPA Ethernet0/0 [CSCdi68767]

IBM Connectivity

• An APPN/DLUR router does not work with FDDI-attached downstream PUs. Vtam displays a '10010000' sense code. [CSCdi48489]

• An SDLC PU2.0 link station on an APPN DLUR router may get stuck in the "starting" state if "no connect-at-startup" is not specified on the link station definition. (If the user does not configure the PU2.0 link stations, they will be dynamically created.) [CSCdi56633]

• With Release 11.0 and a direct Escon-attached CIP, the host may "box" the CIP if the router is reloaded without the CIP being varied offline. This problem has not been seen with CIPs connected through a director or if the CIP is taken offline before the router is reloaded. The workaround is to vary the device offline before reloading the router. [CSCdi59440]

• When the PS/2 Link Station Role is configured as Negotiable, the XID(3) Negotiation may not complete. The workaround is to configure the PS/2 Link Station Role as Secondary. [CSCdi60999]

• When running CIP SNA over DLSw, the LLC2 control blocks may not get freed even when the LLC2 session is lost and the DLSw circuit is gone. The workaround is to reload the router. [CSCdi62627]

• Extraneous XID packets could cause the following message to be displayed:

%CLS-3-CLSFAIL CLS Assertion failed file "../cls/cls_entitymanager.c", line 2985 this->fCepState == kCepStateIdReqPending -Traceback= 3272892 304084A 33B8156 33B96E6 3040832 3271056 327118C 326ED4A

This was an annoyance and the message was eliminated. [CSCdi64207]

• LSAP filters and NetBIOS host filters that are applied to the DLSw remote-peer statements do not work on DLSw border routers. [CSCdi66251]

• In certain situations, DLSw+ backup peer definitions may be written to NVRAM before the definition of the peer they are backing up. When this happens, the backup-peer definition will not be recognized upon router reload. [CSCdi67272]

• When cfg-ing an APPN class of service (COS), you may get the following error:

% Error (0x0001,0x00000807) defining class of service.

If so, here is a workaround until the code is fixed to match what the help says are correct values.

1) When cfg-ing a tg-row's prop_delay, only these enumerated values are allowed, not the 0-255 implied by the help:

AP_PROP_DELAY_MINIMUM (0x00) = 0 AP_PROP_DELAY_LAN (0x4C) = 76 AP_PROP_DELAY_TELEPHONE (0x71) = 113 AP_PROP_DELAY_PKT_SWITCHED_NET (0x91) = 145 AP_PROP_DELAY_SATELLITE (0x99) = 153 AP_PROP_DELAY_MAXIMUM (0xFF) = 255

2) When cfg-ing a tg-row's security, only these enumerated values are allowed, not the 0-255 implied by the help:

AP_SEC_NONSECURE (0x01) = 1 AP_SEC_PUBLIC_SWITCHED_NETWORK (0x20) = 32 AP_SEC_UNDERGROUND_CABLE (0x40) = 64 AP_SEC_SECURE_CONDUIT (0x60) = 96 AP_SEC_GUARDED_CONDUIT (0x80) = 128 AP_SEC_ENCRYPTED (0xA0) = 160 AP_SEC_GUARDED_RADIATION (0xC0) = 192 AP_SEC_MAXIMUM (0xFF) = 255

3) 'show appn class det' will show zero values for all values of a TG row of any new COSs. [CSCdi67560]

• dlsw with frame relay pass-thru fails to bring up a netbios windows nt session. [CSCdi68970]

• The router crashes when NSP is configured and is trying to connect back to the owning host. [CSCdi69231]

• When reassembly is involved in a DLUR managed LU-LU session (i.e. the mtu for the downstream link to the PU is smaller than the mtu for the upstream link toward the host) and the ru size is larger than can be transmitted in a single frame, (most common with IND$FILE transfers from a PU to the host), the router may reload with "checkheaps" stack trace indicating memory corruption has occured. [CSCdi69283]

• SNA and NetBIOS session do not connect using DLSw FST (Fast Sequenced Transport) over SMDS WAN media. [CSCdi69766]

• When segmentation or reassembly is involved in a DLUR managed LU-LU session (i.e. the mtu for the downstream link to the PU is smaller than the mtu for the upstream link toward the host) and the ru size is larger than can be transmitted in a single frame, (most common with IND$FILE transfers from a PU to the host), the router may reload with "checkheaps" stack trace indicating memory corruption has occured.

This ddts the complete fix for CSCdi69283. [CSCdi70232]

• APPN/DLUR is not working with versions of CM/2 which set the extended binds supported flag in the actlu response. The downstream CM/2 cannot establish an lu-lu session through the DLUR router. [CSCdi70506]

• Router interface operating in an SDLC secondary role will not respond to TEST P. [CSCdi70562]

• When using DLSw FST, end user sessions may not switch over to an alternate lan or peer path following a connectivity failure. [CSCdi70709]

• The lnm disable global command sometimes prevents stations from inserting into the ring. The workaround is to issue the no lnm rps or no lnm rem interface command. [CSCdi70962]

• When establishing an LU session with the APPN/DLUR router, the downstream LU session may display a x'20110000' pacing protocol error and unbind the session. The APPN/DLUR router was performing pacing incorrectly on the secondary stage. [CSCdi71834]

• DLSw+ responds to pending explorers as soon as the first response is received from the peers. This may result in DLSw using a peer with a higher cost to setup a circuit.

This is fixed by providing the user with the following command to set up the amount of time DLSw should wait for responses from other peers. [no] dlsw timer explorer-wait-time seconds

The default value of the timer is zero. This causes DLSw to respond as soon a response is received (current behaviour).

Note 1: This may cause the first circuit (when the cache is NOT fresh) to be delayed by the amount of time configured. Once the cache is fresh, circuits will come up normally.

Note 2: If this timer is changed, DLSw will use the new value only for new explorers and the old explorers pending if any will contine to have the old value.

This provides the same functionality in IOS 11.0 as CSCdi59181 provides in IOS 11.1 and later. [CSCdi72231]

• When segmentation or reassembly is involved in a DLUR-managed LU-LU session (that is, the MTU for the downstream link to the PU is smaller than the MTU for the upstream link toward the host) and the RU size is larger than can be transmitted in a single frame (most common with IND$FILE transfers from a PU to the host), the router may reload with an "intermediate_reassembly" or a memory corruption stack trace. [CSCdi72260]

• When using APPN RSRB ports you do not have the ability to configure some key LLC2 parameters. Namely, when a DLUR router activates 4000 downstream PUs over an RSRB port, the CPU will spend considerable time maintaining the LLC2 connections active especially when there is no traffic. That is, the CPU will be spending considerable cycles sending keepalives to all 4000 PUs. [CSCdi72397]

• APPN/DLUR does not provide you the ability to limit the number of dependent PUs it may support. This may be desirable when designing networks using some of the fault-tolerant and redundancy features available to you when using APPN/DLUR in conjunction with RSRB or DLSW+. [CSCdi72398]

• If the ABM indicator (async balanced mode) differs between the way the APPN/DLUR feature sets the indicator and the way the attached node sets the indicator, the xid will fail with sense 10160010. While there is technically a mismatch, this problem is usually caused by incorrect xid3 implementations or bridge implementations which do not convert the indicator appropriately. Cisco NN DLUR is removing the check since it can fail a connection unnecessarily when the xid3 would otherwise succeed. [CSCdi73143]

Interfaces and Bridging

• There is a problem with the SNMP Packets in counter on token ring interfaces of Cisco access routers (4000, 2500 series) which can cause these counts to be inaccurate on the low side. In the case of relatively inactive token rings, this counter can actually underflow, causing SNMP to report that a very large number of frames have come into the interface. [CSCdi21699]

• Customer is trying to migrate from ags+ to 4700. They have know problem(s) with excessive collisions on 2 ethernet segments.

However, interfaces did not go down on AGS+ or other 7000 routers (showing excessive collissions, (rate in excess of 10%) as is the case with the 4700 router with NP-6E card.

Using AM79970 chipset. Also seeing similiar manifestations as in CSCdi51927 where output of 'sh cont eth is showing 'link state down' while sh int eth sho up/up for state and we're seeing packets inbound/outbound on the interfaces respectively. [CSCdi49380]

• For the AGS+ and probably for Cisco 7000 series routers, IP routing has problems with 1500-bytes packets following a serial-to-router-to-FDDI path. Packets of 1499 bytes get 1524 bytes on the FDDI network, and IP packets of 1500 bytes get 1526 bytes. This breaks communication between the router and switches such as the Cisco 1200. The routers on the FDDI network continue to understand these packets. [CSCdi62156]

• When you perform buffer changes on a serial interface with SMDS encapsulation, the changes are not taken into account after a reload. [CSCdi62516]

• The source-bridge ring-number command allows you to configure a ring-number mismatch. The workaround is to make sure that all bridge devices on ring use same ring number. [CSCdi63700]

• In Cisco 7500 series routers, the following error message might be displayed while booting the system image from TFTP or Flash memory, or when changing the serial encapsulation (for example, from HDLC to SMDS):

%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot x, cmd code 0

The show diagnostics x command reports that the board is disabled. The show version command does not show the card in the specified slot. The write terminal command does not show the configuration for the card in the slot. A possible workaround is to issue a microcode reload command or load a new system image that has the fix for this bug. [CSCdi66450]

• ppp encapsulation config erased when MIP card is reseated. This occured on version 010.003.007 010.003.008 010.003.012 011.000.009 and 011.001.004. [CSCdi66915]

• Alignment warning message can occur at bridge_enq resulting from source-route bridging:

%ALIGN-3-CORRECT: Alignment correction made at 0x60399C74 reading 0x40002165 [CSCdi68947]

• Small and middle buffers leak when transparent bridging on ATM is enabled. [CSCdi69237]

• Misaligned data accesses in the packet data may negatively affect CPU usage on RSP based platforms when handling SAP or SNAP frames. [CSCdi70402]

• When an arp packet is received from the ATM interface, the router sends out a total of two arp packets to the Ethernet interface. [CSCdi70533]

• In some cases, a Cisco 4000 router with Token Ring NIM and running xx-p-mz image displays the "%SYS-3-SUPNONE: Registry 6 doesn't exist" error message repeatedly on the console after bootup. [CSCdi70834]

IP Routing Protocols

• Router does not retain the OSPF dead-interval setting after a reload even though the NVRAM config shows the dead-interval set properly. The router sets a default value to the dead-interval instead of what is set under the NVRAM config.

The problem only happens if the configured value of the dead-interval is the same as the original default - 40 for broadcast network and 120 for non-broadcast network - and the hello-interval is not default.

The workaround is not setting the dead-interval the same as the original default.

When the fixed image is first loaded, the problem still happens. To resolve the problem, reconfigure the dead-interval again and do write memory. Then the problem will not happens again with subsequent reloads. [CSCdi62640]

• This problem happens with IP tunnel. When the route used to reach the tunnel's destination is pointing to the Null interface, SYS-2-GETBUF messages will appear whenever a packet is sent over the tunnel.

Besides the messages, there is no bad effect on the network.

The workaround is to remove the route pointing to the Null interface. [CSCdi65475]

• IPX Enhanced IGRP updates do not propagate if the MTU size is less than the IPX Enhanced IGRP packet size. [CSCdi65486]

• Processing of input offset lists in Enhanced IGRP was disabled erroneously, so offset list processing is not available. There is no workaround. [CSCdi65889]

• When the router performs DNS name lookups of nicknames, the canonical name is stored in the host name cache, so repeated uses of the nickname will require queries to the name server rather than being satisfied from the name cache.

Note that releases 11.0(11.1) and 11.1(6.1) contain the fix for this ddts may reload when doing DNS name validation. Check CSCdi70707 and CSCdi71158. Releases 11.0(11.2), 11.1(6.2) and any 11.2 are fine. [CSCdi66910]

• When running 10.3(13) IOS, if you have neighbor statements pointing to a subnet broadcast address, it may fail to send updates to that broadcast address. [CSCdi67411]

• PIM-NBMA mode will not allow population of outgoing interface list with neighbors that are also on the incoming interface list. The result is that joiners on a single NBMA interface may not be able to exchange traffic with other joiners on the same interface. This only affects interfaces in sparse-mode. [CSCdi69298]

• BGP will not be able to establish a password-protected session with a peer when service password-encryption is configured, the configuration is written to NVRAM, and the router is reloaded. A workaround is to remove the password encrytion and re-enter the passwords as cleartext. [CSCdi69978]

• OSPF ABR will generate summary for subnet of connected point-to-point interface with wrong cost. The wrong cost is twice as much as the actual OSPF cost of the interface. In topology with more that one ABR, this could create routing loop for the point-to-point interface subnet. In order words, attempt to telnet or to ping the point-to-point interface address from a different area could fail, but the router could still be accessed through other non-point-to-point interface addresses on the router.

There is no workaround. [CSCdi70406]

• If bridge is enabled on an interface where HSRP is also configured, both active and standby routers start to forward packets when primary active router that has gone down comes back to life . [CSCdi70693]

• Static hosts can only be displayed but will not be used or deleted.

The patch for this ddts causes CSCdi73022. [CSCdi71096]

ISO CLNS

• If the IS-IS or NLSP Designated Router goes down, there may be a delay of 10 seconds or more before routing converges again. There is no workaround to this problem. [CSCdi72234]

LAT

• When translating LAT to PPP under Protocol Translation, data sent from translator may be lost, causing the PPP negotiation to fail and the LAT session to be disconnected. [CSCdi46164]

Novell IPX, XNS, and Apollo Domain

• The IPX SPX spoofing table entries might not begin to age out until sometime after the SPX age timer has gone expired. [CSCdi67901]

• SPX spoofing might cause a reload due to a software-forced crash. A workaround is to disable aging of the SPX table by entering the following commands: ipx spx-spoof session-clear 0 and ipx spx-spoof table-clear 0. [CSCdi68150]

• When using the 'ipx route default' command, IPX Netbios (type 20) packets are still dropped on a router if the source route is not known and the default route is known. It is strongly recommended that when forwarding IPX NetBIOS broadcasts that the extra input and output checking be enabled. The commands to do this are ipx type-20-output-checks and ipx type20-input-checks. [CSCdi68151]

• Valid services may be lost on NLSP routers as a result of normal SAP activity (especially when large numbers of services are poisoned via a RIP/SAP interface on a neighboring router). [CSCdi68274]

• If SPX spoofing fails to send a keepalive a traceback message will be display on the system console. [CSCdi69062]

• IPX NetBIOS packets which are filtered by router netbios filters do not get freed and may stay in system memory. [CSCdi69212]

• When using EIGRP as a routing protocol show ipx server may display an incorrect negative metric. This error in the display does not affect operations. [CSCdi69226]

• Under certain circumstances, some IPX services learned via NLSP may not appear in the service table. There is no workaround to this problem. [CSCdi71036]

• Once the apollo network number is configured in the interface, it cannot be removed or modified. [CSCdi71716]

• XNS RIP periodic routing updates may not be sent at regular 30 second intervals. [CSCdi72104]

Protocol Translation

• "show translate" may incorrectly indicate the number of active users for translations using TCP as the inbound protocol, if TCP connections fail to be set up properly. [CSCdi70265]

• Using one-step Virtual Async Protocol Translation, the PPP/SLIP banner will not display (IP address, MTU size, etc.) but the PPP/SLIP link comes up fine. There does not seem to be a pattern although it happens sporadically. [CSCdi71495]

TCP/IP Host-Mode Services

• RSH commands executed to the router without a controlling shell only return the first 1608 bytes of data. [CSCdi69424]

• The fix of CSCdi66910 introduced this bug and CSCdi71158, system may reload when doing DNS name validation. There is no workaround. [CSCdi70707]

• Certain invalid TCP SYN packets can cause infinite looping in the TCP code, either within a single system or involving continuous packet exchange between two systems. This results in serious performance degradation or complete system lockup. Such SYN packets are not sent by normally functioning TCP implementations, and would be unlikely to be generated by any innocent TCP bug or misconfiguration... but might easily be generated by malicious system abusers. One particular case of such a packet is the attack packet sent by the "land.c" program. See http://www.cisco.com/warp/public/770/land-pub.shtml for more information on the land.c attack. [CSCdi71085]

Wide-Area Networking

• Under certain unknown circumstances, a neighbor route will not be installed for a SLIP or PPP connection. Debugging output (debug ppp negotiate) indicates that the route was added, but it will not appear in the IP routing table nor be seen in the debug ip rout trace messages. [CSCdi50490]

• 4500 with ATM card blocking with the following message: atmzr_hi_irq_hand(ATM0): Secondary port error [CSCdi58134]

• X25 parameters ignored at startup in some cases. Config is still correct though. [CSCdi60529]

• RFC 1577 and LANE applications get blocked because of a difference between the VCD known by different parts of the software. This problem has been reported with both RFC 1577 and LANE applciations and in Releases 11.0(8) and 11.1(4). [CSCdi61979]

• When the router is acting as an X.25 DCE, it will sometimes fail to encode a facilities length field in a switched call connected packet. Some attached DTE's may then clear the call with a diagnostic code of 38, packet too short. This behavior was introduced in 10.3(12), 11.0(9), and 11.1(4). [CSCdi63831]

• Exec command Slip /compress and the exec command PPP /compress don't correctly turn on TCP/IP header compression if configuration command service old-slip-prompts is in use, with the async interface configured with ip tcp header-compression passive. [CSCdi64325]

• aip20-8 microcode may cause the AIP board to lock into a state where it transmits corrupted packets, causing debug atm error showing: ATM(ATM9/0.1): VC(1) Bad SAP ... at the receive side of the ATM VC. The transmission of data is usually affected in one direction only. The problem may occur when the input traffic exceeds the average rate configured on the ATM VC, when the bandwidth of the incoming interfaces exceeds the average Rate on the outgoing VC or SVC. A workaround is either to downgrade the AIP microcode to aip20-6 or to upgrade the AIP microcode to rsp_aip205-5, or aip20-9 when available. A short term workaround is clear int atm 5/0 on the transmit side.

The same problem applies for aip10-15 on RP based platforms. [CSCdi67812]

• When parallel, non-multilink connections exist in a dialer group, the loss of one connection will remove the route to the peer address even though one or more connections exist to forward packets to the destination. This defect occurred as a side-effect of the fixing of CSCdi59425 and will be fixed in a future release of IOS. [CSCdi67844]

• LANE does not set up the data direct again after it has been established the first time. This problem was introduced as a result of the commit of the fix for CSCdi61979.

Any release containing this bug should NOT be used in sites using LANE. The following releases are affected: 11.0(10.3), 11.1(5.3), 11.1(5.4), 11.2(0.23), and 11.2(0.24).

Note that for 11.0, only the 7000 image will be affected, as the 4500 and rsp platforms do not run LANE in 11.0. [CSCdi68089]

• An APPN/DLUR router may not establish a link to an ethernet-attached 3270 workstation which sends tests and xids in both 802.3 format and ethernet 80D5 type format. [CSCdi68201]

• When dialing into the AS5200 from an I-Courier modem over sync ISDN and then starting a PPP session, the router may crash. This occurs only when login is done on a non-async interface and when extended TACACS is enabled. A workaround for non-async interfaces is to use AAA/TACACS+. [CSCdi68257]

• Under most conditions, dialer maps will be ignored when negotiating the peer's IP address, if a peer IP address pool is configured on an ISDN or Dialer interface. Instead of using the IP address from the dialer map, an address would be acquired from the address pool. This prevents a user from supporting dial-up routers with assigned IP addresses and dial-up clients requiring dynamic IP address assignment. [CSCdi68441]

• If multiple, parallel connections to the same peer are made and one connection drops, the remaining connections may be unusable as packets will not be forwarded over them. [CSCdi68456]

• This problem is that an AAL5-ABORT frame is always followed an OAM cell. This problem happens on 4500 and 4700 when a F5 cell is sent out. This problem is known and to be fixed in the future release. [CSCdi68675]

• On a Cisco 4500 or Cisco 4700, a packet may be registered in both the input and output hold queues on when going from ATM to other network links. This may affect the values of the input and output queue length fields in the output of the show interface command. On a Cisco 4500 or Cisco 4700 configured with ATM, another fast network link, and a slow network link, this behavior may have some impact on the overall throughput of the traffic from ATM to another fast network link when the slow link is flooded with too many packets from ATM. However, we are unaware of any environments in which network functionality could be seriously impaired by this. The correct router behavior would be to drop packets over the slow link without affecting the traffic from ATM to another fast link. [CSCdi69441]

• ATM F5 OAM segment cells are received by c4500/c4700 as user data cells. As a result, an F5-segment-loopback ping will not succeed. In ATM LANE environment, LE Client up/down state change may occur if a c4500/c4700 receives a F5 OAM segment cell. But Cisco Systems is unaware of any other environments in which network function is seriously impaired. The correct router behavior would identify ATM F5 OAM segment cells and support F5 OAM segment loopback service. Cisco Systems expects to resolve this behavior in a future maintenance release. [CSCdi69513]

• DlSw router with token-ring starts sending frmr responses without i-field, to sna devices, bringing down the llc2 sessions. Reload temporarily fixes. [CSCdi69576]

• On certain platforms, entering a ip address configuration command while the interface is connected to a SLIP or PPP peer may cause a software-forced reload. [CSCdi69809]

• A neighbor route is not installed for PPP connections over an async or a vty-async connection. This defect was introduced by the fix for CSCdi50490. [CSCdi69919]

• The system can unexpectedly restart if an outgoing PAD call is placed on an X.25 logical channel that experiences a call collision, when acting as an X.25 DCE. [CSCdi69963]

• Using TACACS+ with dialback over a rotary group causes the authorization to fail for the user when the callback script aborts or finishes incorrectly, so failover to another line of the rotary occurs. The call is made, but an internal error occurs when debugging TACACS+. [CSCdi70549]

• ISDN BRI routers may have problems bringing up multiple B-channels to the same destination. The router and PBX may also get into a Layer 3 state mismatch and continuously exchange Layer 3 messages. [CSCdi71333]

• the restart ack messge we sent out in responsding to the incoming restart message with global call reference, we did not set the call reference value flag to 1. we did set the flag correct if it's not a global call reference. [CSCdi71883]

• When configured on a point-to-point subinterface, the frame-relay ip tcp header-compression introduces an extraneous no ip route-cache command in the main interface configuration. The workaround is to re-enable the route cache manually. [CSCdi71935]

11.0(10) Caveats/11.0(11) Modifications

This section describes possibly unexpected behavior by Release 11.0(10). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(10). For additional caveats applicable to Release 11.0(10), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(11).

AppleTalk

• A router configured with AppleTalk Enhanced IGRP takes too long to age-out routes even when the link is down, causing a long convergence time for features such as backup interface. [CSCdi62796]

• This corrects a problem when ARAP is configured and under some conditions the following messages occured:

%SYS-2-INPUTQ: INPUTQ set, but no idb, ptr=xxxxx %SYS-2-LINKED: Bad enqueue of xxxxx in queue yyyyy

After which a router reload could occur. [CSCdi63635]

• IPTalk does not function correctly. IPTalk-speaking CAP servers cannot communicate and is not recognized on the network. [CSCdi64165]

• Due to the way nbp packets get processed, it is possible that inbound nbp filters may affect outbound nbps. [CSCdi65598]

Basic System Services

• When using 10.3 and cbus1 cards in an AGS+, some of the interface counters can be inaccurate. The counters affected are FDDI ignores, FDDI frame errors, and Ethernet collisions. There is no workaround. [CSCdi39273]

• [CSCdi42087]

• For Release 10.3(9.3) or earlier, if a microcode reload command is issued over a Telnet connection, the router may enter an infinite loop Otherwise, the message "%SYS-3-INTPRINT: Illegal printing attempt from interrupt level" may be displayed whenever microcode is downloaded. You can ignore this message; it indicates a cosmetic problem. [CSCdi47580]

• If you set login local on a line, then try to reverse-telnet to it, the router opens the connection without authenticating. The workaround is to include a password entry on the line. If you do this, the login local command is evaluated and you must enter your user name and password (not the password you set on the line). [CSCdi49270]

• Nondefault method lists are not supporrted on dialer interfaces. [CSCdi49718]

• Under some conditions, the SEEQ will incorrectly pass up runt ethernet packets. We did not previously check for them, and so incorrectly received ethernet runt packets. [CSCdi55978]

• If an interface is clocking faster than the configured bandwidth, the load computation is erroneous. [CSCdi57534]

• An RSP router can crash with a "reserved exception" error because of a software error or an error in the microcode for an interface processor. More than one problem can generate a similar error message and stack trace, which can make this problem hard to track down. See also CSCdi58999, CSCdi60952, and CSCdi60921. [CSCdi58658]

• Cisco 7500 series routers cannot fast switch packets larager than 8192 bytes. These packets are switched at process level, a slower performance path. [CSCdi60295]

• Added the following images for CIP2 support:

10.2 - gs7-k2 gs7-p2 10.3 - gs7-k2 gs7-p2 rsp-k2 rsp-p2 11.0 - gs7-k2-mz gs7-p2-mz gs7-ak2-mz rsp-k2-mz rsp-ak2-mz rsp-p2-mz

CIP2 is a new hardware version that requires one of the previously listed images for a particular release of IOS. [CSCdi61227]

• Control characters are not interpreted properly in chat scripts. [CSCdi62960]

• DHCP Proxy client support for IP address pooling does not always get back responses from the DHCP server. IP helper addresses are needed on the intermediate routers if broadcast address is used. In the case of configured DHCP servers the unicasts back from the DHCP server, are sometimes lost. [CSCdi63267]

• In some cases the snmp-server party and snmp-server context configuration commands may cause a system reload. Neither of these commands verify that the configured OID is not already in use, permitting multiple records to be configured with the same OID, violating the rule that each record must have a unique OID. A common occurrence is to attempt to configure an initialPartyIdentity or initialContextIdentity that conflicts with the OIDs that are automaticially preconfigured per RFC 1447. A workaround is to not configure OIDs that conflict with the initial party and context OIDs specified in RFC 1447. [CSCdi63694]

• Cisco routers with Motorola 68000 microprocessors (such as the Cisco 7000 and Cisco 2500 series) cannot fast switch packets larager than 8192 bytes. These packets are switched at process level, a slower performance path. [CSCdi63695]

• Debugging information about telnet subnegotiations is incorrectly sent to the telnet user's line rather than to the console and lines that are monitoring debug output. [CSCdi63963]

• Chat scripts are not sending special characters embedded in send strings. The ignored characters are "
  ", "
  ", "s", " " . [CSCdi64886]

• When using the autocommand or callback-dialstring options of the username command, extra information will be produced when the configuration is saved. [CSCdi65014]

• Bug fix CSCdi55978, which was integrated into the builds 10.003(012.006), 11.001(004.005), 11.000(009.006), 11.000(010.000.001), 11.001(005.000.001), 11.002(000.018), 10.003(013.000.001), introduced the following problems. Cisco 7500 family processors (RSP1, RSP2, and RSP7000) encounter a Reserved Exception crash or encounter a QAERROR causing a switching complex restart when receiving a runt from an Ethernet interface. The Ethernet interfaces are supposed to filter and count the runt packets, so we are never supposed to see them.

The Reserved Exception crash looks like this:

Queued messages: Aug 14 10:44:16: %RSP-3-ERROR: memd write exception, addr 08000000 Aug 14 10:44:16: %RSP-3-ERROR: RSP alignment error on write to QA, addr 08000000 *** System received a reserved exception *** signal= 0x9, code= 0x0, context= 0x60c72fd0 PC = 0x60107514, Cause = 0x2020, Status Reg = 0x34008702 DCL Masked Interrupt Register = 0x000000ff DCL Interrupt Value Register = 0x00000000 MEMD Int 6 Status Register = 0x00000000

The QAERROR looks something like this:

Jun 17 10:50:23.329: %RSP-2-QAERROR: reused or zero link error, write at addr 0308 (QA) log 260308C0, data A816FFFF 00000000 [CSCdi66673]

EXEC and Configuration Parser

• hold-queue is deleted from config upon reload in 11.0. and 11.1 on serial lines. [CSCdi52618]

IBM Connectivity

• On a c70x0 router installed with a CIP running CSNA, explorers that are not destined for one of the configured CIP internal LAN MAC addresses cause the explorer ouput counter to get incremented erroneously. [CSCdi46834]

• In some configurations of DLSW with local ack, the router does not answer the SABME P from an end station properly. The problem manifests itself when the PC sends SABME P (out) and the router sends UA (in). Some end stations treat this as a violation of the LLC2 specification.

In most instances, the PC sends another SABME P and the router responds appropriately with a UA F.

The workaround is to ensure that the end station (PC) makes more than one attempt to connect to the host by sending at least two SABME Ps. [CSCdi46918]

• DLSW flow control allow max/min flow control window sizes [CSCdi48010]

• When multiple Remote Source-Route Bridging virtual interfaces are created by a DLU using CLSI, only one of the virtual interfaces will closed and cleaned up upon termination. The others will be left in an undetermined state and attempts to reopen them will result in ALREADY_ENABLED error codes. [CSCdi49060]

• Some IBM llc2 implementation devices send a RNR when they run out of buffer and drops the frame. This will cause no data traffic flow for 30 seconds. Non IBM llc2 devices use IEEE llc2 will send REJ rather than RNR and no delay will be noticed. [CSCdi49447]

• When autonomous switching is enabled on a CIP interface and the packet is larger than the CIP MTU, the packet is not fragmented.

If this is occurring, use fast switching instead of autonomous switching. [CSCdi52884]

• If the message

%SCHED-2-NOTWATCHTIMER: simple timer 2CFBF8 not being watched. -Process= "BSTUN Background", ipl= 0, pid= 19 -Traceback= F336E 27A0C2 E677E E67F8 EF50E A0BA0 F25B8 27A15C

appears, as long as bstun is never to be used on the router before the next reload then the router should be fine. If bstun is to be configured again it would be safer to reload the router. [CSCdi53010]

• Doing a no fras map sdlc can cause the router to reload. [CSCdi53909]

• The SDLLC secondary router fails to respond to SNRM input frames. This problem was introduced by CSCdi51341. [CSCdi56398]

• Four changes need to be made in the support for show dlsw commands: show dlsw peer needs to be modified so the fields line up properly when using frame-relay direct encapsulation peers. show dlsw reachability requires the ability to search the reachability cache for a particular MAC address or Netbios Name. show dlsw circuit requires the ability to show all circuits matching a particular MAC address or SAP. In addition, an option will be added to allow show dlsw circuit detail , which will show additional information about the circuit. show dlsw local-circuit also requires the ability to show all circuits matching a particular MAC address or SAP. [CSCdi59064]

• The problem is that valid multicast explorers that should be handed to the protocol stack are instead being diverted to the srb module and are being flushed by the srb explorer control mechanism.

This problem was introduced by some changes to the token ring interrupt handler in 11.0 and later.

There is no workaround for the diversion, though the flushing can be avoided by raising the explorer maxrate value to some high number. However, this may cause instability in the network.

Note that this bug fix is comprehensive in that several issues regarding multicast explorers and inbound remote explorers have now been resolved.

Paul S. [CSCdi59090]

• FRAS remote source-route bridging dial backup fails on SDLC-attached devices if more than one SDLC device is configured. [CSCdi61179]

• Parser help for "fras map" commands is not working perfectly. Workaround is to use manuals. [CSCdi61263]

• If the vmac parameter is not specified in the qllc dlsw command, a Cisco 4500, Cisco 4700, or Cisco 7500 router may crash in the function QLLCTestStnReq(). [CSCdi61562]

• It is not possible to configure more than 10 saps in the command syntax of 'dlsw icannotreach saps xx xx ....'. There is no work-around for this. [CSCdi61887]

• QLLC may try to initate a connection in the middle of activating a connection. [CSCdi62155]

• When configured on a Channel Interface Processor (CIP) interface, the ip mtu command is removed from the configuration after a microcode reload or EOIR event. [CSCdi62273]

• A Cisco router may eventually crash if configured with a STUN TCP peer which suffers from hardware issues. [CSCdi62480]

• During LLC2 connection failure between CIP and RP, the DISC from RP to CIP may be dropped. However, CIP may continue to send RR_Cmds to its endstation. The RP would attempt to respond to the RR_Cmds resulting alignment and spurious access errors on the RP. This would also cause CIP to generate BADVCN error messages for the virtual port 2. [CSCdi62629]

• Connections cannot be established when using IBM process-switched features (e.g. RSRB/TCP, DLSw+/TCP, etc) because of dropped packets

Symptom is "dropped Routed protocol" messages are output when "debug source-bridge error" is enabled

This behavior was introduced by CSCdi61267. Integrated into 11.0(9.4) and 11.1(4.3). [CSCdi62738]

• DLSW netbios can't connect windows NT. [CSCdi62784]

• FastEthernet and FDDI interfaces are not supported on the interface parm of the "dspu host/pu" and "sna host" commands [CSCdi62916]

• When using SDLC with a CLS DLU (e.g. APPN, DSPU, etc), a CLS_ASSERT traceback message may be displayed on the console in cases where there is a race condition of data received at the same time the sdlc connection is being disconnected. [CSCdi63154]

• DLSw+/QLLC circuits would not activate if a QSM was sent without XIDs being exchanged. [CSCdi63350]

• The message "IBM: Unknown L3 PID, fr_doencap failed" is displayed with DLSw. This is caused by race condition when one DLSw peer has come up while other DLSW peer is in the process of coming up. It is a warning message that does not prevent the DLSw peers from coming up. [CSCdi63658]

• When activating more than 8000 LUs, PUs and DLUSs combined, it is possible for the DLUR feature to corrupt storage and cause a router failure. [CSCdi63903]

• When you remove a csna path device command from the configuration and then try and display the remaining devices, using the command:

show ext channel x/0 path stat

the channels do not appear as expected. [CSCdi64003]

• When you issue the show controller cxbus command, the CIP utilization and memory statistics are not shown if all the CIP interfaces are down, or if no device is configured on either the channel slot/0 or channel slot/1 interface.

In version 11.0 and greater, a workaround is to no shut the CIP virtual interface, channel slot/2 [CSCdi64004]

• In extreamly stressful locate traffic scenerios, it is possible for the APPC function in the router to discard APPN locate searches and cause the search proceedure to hang at other nodes. At least several hundred simultanious locates proceedures are required to cause this problem. [CSCdi64045]

• APPN: SNA Service Point configured to use an APPN/DLUR link may fails during the xid3 negotiation with a 0x0891004 (invalid netid). [CSCdi64111]

• A memory leak in QLLC can result in buffer starvation on the serial interface, and LAPB on the serial interface gets stuck in the RNRSENT state. [CSCdi64333]

• Configuring the dlsw remote-peer cost command has no effect on peer selection. All peers displayed in the show dlsw capabilites command show equal costs. [CSCdi64537]

• When using APPN-DLUR, if a downstream PU sends a SNA level REQDISCONT on the SSCP-PU session and the device is a PU2.0 device on SDLC, a link level disconnect (X'53') will not be forwarded to the device by DLUR unless the DLUR first receives a link level Request Disconnect (X'53') from the device. This may cause a very limited number of devices that send sna level REQDISCONT but don't send link level RD to hang pending a disconnect. [CSCdi64791]

• QLLC may incorrectly set the ABM bit to 0, instead of 1 on Format 3 XIDs that it sends to Token Ring or RSRB. [CSCdi64913]

• When the host pu is not activated, the connect in from DSPU is either sent too fast or sent once only. The configuration parameters RETRIES and RETRY-TIMEOUT in the pu configuration are used to control the number of retries and the period of retry. [CSCdi65090]

• If infinite retries is enabled for SNA Service Point using an APPN/DLUR link, some routers (4000, 2500, 7000) may fail with a bus error. The "Stack for process TTY Background running low, 0/2000" message is displayed.

As a temporary work-around, you can specify "retries 1" on the sna host definition. [CSCdi65375]

• On the "show dlsw peer" command, if a peer's state is WAN_BUSY, the tcp queue depth and peer uptime are not displayed. [CSCdi65588]

• CSCdi58658 caused DLSw FST on the RSP to break. CSCdi58658 was integrated into 011.011(004.005)

In addition, DLSw FST is not supported on a Channel Interface Processor (CIP) LAN interface.

This error caused by CSCdi58658 will result in a buffer leak in the RSP's Token Ring interface buffer pool and the Token Ring interface will eventually hang when it runs out of buffers. Issuing a show controller cbus command will show how many buffers the interfaces thinks are still available in the system.

The following error messages will occur :

*Aug 7 11:48:33 mst: %SYS-2-LINKED: Bad enqueue of 60AE6FC0 in queue 60B0EB60 -Process= "interrupt level", ipl= 5 -Traceback= 60110530 6016901C 60169070 60211C8C 600F2E70 600F2B70 600F06D4 601B78E0 60188EB0

boxer% rsym rsp-j-mz.111-5.0.1.symbols Reading rsp-j-mz.111-5.0.1.symbols rsp-j-mz.111-5.0.1.symbols read in Enter hex value: 60110530 0 x 60110530:p_enqueue(0 x 601104d0)+0 x 60 Enter hex value: 6016901C 0 x 6016901C:process_enqueue_common(0 x 60168fb4)+0 x 68 Enter hex value: 60169070 0 x 60169070:process_enqueue_pak(0 x 6016905c)+0 x 14 Enter hex value: 60211C8C 0 x 60211C8C:ip_simple_enqueue(0 x 60211c74)+0 x 18 Enter hex value: 600F2E70 0 x 600F2E70:dlsw_lan2fst(0 x 600f2c1c)+0 x 254 Enter hex value: 600F2B70 0 x 600F2B70:dlsw_srb_input(0 x 600f2ab0)+0 x c0 Enter hex value: 600F06D4 0 x 600F06D4:fs_srb_to_vring(0 x 600f054c)+0 x 188 Enter hex value: 601B78E0 0 x 601B78E0:rsp_process_rawq(0 x 601b673c)+0 x 11a4 Enter hex value: 60188EB0 0 x 60188EB0:rsp_qa_intr(0 x 60188dec)+0 x c4 [CSCdi65603]

• APPN/DLUR service TPs are at risk of hanging indefinately if another node behaves badly (e.g. fails to send pacing responses. Enabled path to deactivate the CP-CP session if a APPC call hangs for 30 seconds or longer. [CSCdi65880]

• Route cache counters in "show interface x/x stats" command are incorrect when router is switching R/SRB packets [CSCdi65943]

• SNA sessions using QLLC over X.25 PVCs do not become active. The following tracebacks are a symptom of this problem:

%SYS-2-LINKED: Bad enqueue of 9600E8 in queue 88380. SNA: Alert xxxxx not sent, Focal point buffer overflowed. [CSCdi66340]

• If the Channel Interface Processor (CIP) card on a Cisco 7000 router is in a hung state, the Cisco IOS software may enter a loop trying to reset it. The following messages will be repeated:

%CBUS-3-CIPRSET: Interface Channelslot/port, Error (8010) disable - cip_reset() %CBUS-3-INITERR: Interface decimal, Error (8004), idb hex decimal cmd_select - cbus_init() %CBUS-3-INITERR: Interface decimal, Error (8004), idb hex decimal cmd_select -cbus_init() %CBUS-3-CTRLRCMDFAIL1: Controller decimal , cmd (128 hex) failed (0x8010)count (16) %CBUS-3-FCICMDFAIL1: Controller decimal, cmd (32 0x00000001) failed (0x8010) count (1)

Looping may be severe enough to require a router reboot.

The looping messages may overrun the logging buffer and thus obviate the reason for the initial attempt to reset the CIP. [CSCdi66420]

• When you issue the show controller cxbus command, the CIP utilization and memory statistics are not shown if the router uptime is 49 days. [CSCdi66467]

• In extraordinary circumstances, the APPN/DLUR feature may stop abnormally with the following message: %APPN-6-APPNLOGMSG: APPN Process ended abnormally. Name: xxxcss00. RC: C3E2F0F6. [CSCdi66995]

• Reloads due to a Seg-V violation at 0x0 are occurring, but the tracebacks are pointing at DLSw. [CSCdi67085]

• The router may reload when a second device tries to connect for reverse QLLC with DLSw+ local switching. [CSCdi67189]

• When the run commmand Telnet is issued from netview with an address will lock up your session with Netview. [CSCdi67280]

• APPN/DLUR NN with connection network defined on a port that has no other defined links and no active dynamic links can cause a reload when the connection network dynamic links are stopped and then restarted [CSCdi67419]

Interfaces and Bridging

• Incomming packets to the Hot Standby Router Protocol (HSRP) MAC address are process-switched, regardless of the route cache status on the interface. [CSCdi44437]

• The "hybridge_input" message may be seen when running bridging over a serial link. This should not be seen any longer since how the message is generated has changed. A rate limited "BAD_ENCAP" message is now generated. [CSCdi48388]

• If AAA new-model is configured and an attempt is made to allocate an IP address after the 'ppp' or 'slip command is entered, the address allocated may not be the last address the user was allocated, even if that address is available. [CSCdi49571]

• Show controller t1 after a clear conters shows that there is remote loss of signal when the t-1 is up. This is a display problem only as the pri can be used to place outbound calls. Resetting the csu clears the problem. [CSCdi52688]

• Add code to display the active state of payload compression for the "show frame map" command. [CSCdi61758]

• Cisco intends to fix the bug in the future releases of the IOS. [CSCdi62177]

• On an async interface, configuring the no keepalive command sets keepalive 10 instead. [CSCdi62199]

• Router sends repeated Babble errors without an apparent cause in sniffer traces. [CSCdi62232]

• -- Release-note --

On RSP-ONLY : If HSRP and bridging is configured on a Token Ring interface, the active router fails to forward ip routed packets which arrive at the Token Ring for the standby ip address. [CSCdi63104]

• A router running Frame Relay crashes at bridge_enq even when bridging is not configured. The fix put in for this bug does not fix the crash. The fix for CSCdi67157 is the correct fix. [CSCdi63140]

• When passing compressed bridged traffic on HDLC WAN links, many errors of the type "Decompression size error" occur. The router sometimes crashes when processing these packets. This fix causes bridged traffic not to be compressed. The fix is considered temporary until process-level bridging can be made compatible with payload compression. [CSCdi63245]

• Call "reg_invoke_fast_setup()" when disabling payload compression in order to give fast-switching a chance to re-enable. [CSCdi63479]

• On Cisco 2520 through Cisco 2523 router models, which have dual-mode sync/async interfaces, LAPB frames are infrequently sent out of order on X.25 links. This occurs only when two of the async/sync ports are used in sync mode at the same time. [CSCdi64284]

• In DTE mode, FSIP was looking for DCD and DSR up before declaring the Line UP. In the new ucode, now FSIP will only look for DCD. This behaviour is same as our low end serials. [CSCdi64735]

• On the AS5200, the performance does not scale well when additional async interfaces are deployed. The symptoms include the Ethernet interface showing input drops and frequent throttles. [CSCdi65706]

IP Routing Protocols

• The HSRP command standby track interface priority cannot track the status of a subinterface. [CSCdi54969]

• In Release 11.0, a customer has trouble forwarding IP packets with options. [CSCdi59020]

• Deconfiguring an IP output access-group on a subinterface causes the IP output access-list checks to be disabled for other subinterfaces of the same hardware interface. [CSCdi60685]

• Input queues may become full running IP multicats. The only way to clear them is to reload the router. [CSCdi61826]

• A problem introduced in Releases 10.3(11.1), 11.0(7.3), 11.1(2.3), and 11.2(0.5) causes OSPF to crash when an OSPF external LSA with a nonzero forwarding address exists and the router has a non-OSPF route for the forwarding address. If the non-OSPF route is removed, OSPF crashes when it reprocesses the external LSA. There is no workaround for the problem. However, in general, no more than one routing protocol should be run over the same topology. If you follow this guideline, no non-OSPF route for forwarding address will exist and the router will not crash. [CSCdi61864]

• OSPF corrupts memory thus possibly causing the system to reload. [CSCdi61956]

• Regression introduced by CSCdi61328 (in 10.3(12.4), 11.0(9.3), 11.1(4.2) and 11.2(0.14)): A router running OSPF may reload if there are parallel intra-area paths. [CSCdi62870]

• Shutdown interfaces with IP addresses or static routes which point to down next-hops or interfaces may cause the IP cache to be partially invalidated more frequently than necessary. This is particularly evident when there are multiple paths. Workaround by removing IP addresses from down interfaces and/or removing static routes through down interfaces. [CSCdi62877]

• A Macintosh that receives its IP address from a router acting as a MacIP server is unable to ping any IP interface on that router. There is no other operational impact from this caveat. [CSCdi63477]

• The router responds to a Telnet request when the destination of the Telnet is a broadcast address. [CSCdi63787]

• The router configuration command neighbor x.x.x.x remove-private-AS could be used to remove Private AS numbers from AS path while sending updates to External neighbors. If the AS-path includes Private and Public AS numbers, Private AS numbers will not be removed.

When used with neighbors external to the Confederation, Private AS numbers will be removed if it is after the Confederation part of the AS path. [CSCdi64489]

• Entries in the IP fast-switching cache can be aged prematurely in some cases. [CSCdi65058]

• With IGRP and RIP, IP unnumbered interfaces using PPP encapsulation receive but do not process routing updates of Major Network Summaries correctly. The major networks appear as host routes instead of network routes. This affects all IP unnumbered interfaces using PPP encapsulation that are pointing to different major networks. This affects dedicated links as well as DDR links using RIP or IGRP.

It is also possible for a race condition to occur, where the majornet route is lost, even after it has been received and installed into the routing table.

The workaround for this problem is a floating static route for the majornet matching the PPP-created host route using a majornet mask pointing to the PPP-created host route. For example, if the host route is 192.1.1.1, then using the command ip route 192.1.1.0 255.255.255. 0 192.1.1.1 250 should solve the problem. [CSCdi65258]

• A directly connected route may disappear from the IPX Enhanced IGRP topology table if the interface that is configured for IPX Enhanced IGRP goes down and comes back up in in brief period of time, on the order of 2 seconds. The workaround is to issue the shut and no shut commands on the interface. [CSCdi65345]

ISO CLNS

• The LSP lifetime and LSP refresh intervals are not currently configurable in IS-IS. This can result in high LSP traffic in very large networks.

There is no workaround for this problem. [CSCdi64256]

• This is a refinement on CSCdi57308 (ISIS could detect duplicate system IDs).

The routers will now make a distinction between possible duplicate system IDs, and spurious LSP purges, which are probably caused by LSP corruption somewhere in the network. [CSCdi64266]

• On some media/encapsulation combinations, the system may not send an ES-IS IS Hello packet immediately in response to an ES Hello packet received from a new End System. The normally scheduled IS Hello will eventually be sent. There is no workaround to this problem. [CSCdi64354]

• If an IS-IS router is generating a significant number of LSPs, the following erroneous error message may appear when the system is first started:

%CLNS-4-DUPSYSTEM: ISIS: possible duplicate system ID xxxx.xxxx.xxxx detected

This is a cosmetic problem only. There is no workaround to this problem. [CSCdi65078]

• Under some conditions, purged IS-IS and NLSP link state packets may persist in a network longer than necessary. This has no impact on calculated routes. There is no workaround to this problem. [CSCdi65479]

• When configuring the isis router-subcommands max-lsp-lifetime and lsp-refresh-interval, these two lines are saved in the wrong order in NVRAM. This will cause the lsp-refresh-interval to be ignored after a reload (though it stays in NVRAM). During reload the following warning will show up:

%ISIS: Refresh time must be less than LSP lifetime

This bug will cause no real harm, as the router will only fall back to the default lsp-refresh-interval of 15 minutes. There is no workaround for this bug. [CSCdi66787]

Novell IPX, XNS, and Apollo Domain

• IPXWAN Client mode fails to negotiate properly. [CSCdi42325]

• In rare circumstances, NLSP may not report information learned from RIP and SAP. There is no workaround to this problem. [CSCdi45425]

• The behavior of the "ipx route-cache" command is inconsistent when IPX is not configured on the interface. In particular, when IPX is configured only on subinterfaces, "ipx route-cache cbus" is lost from the primary interface following a reload with this message:

%Invalid IPX command - IPX not enabled on interface

Note that this can be corrected by issuing a "config mem". A workaround is to always configure at least one IPX network on the primary interface. [CSCdi45840]

• The IPX SAP poison and the RIP poison sent counters on the Show IPX Traffic display are not being incremented.

There is no way to correctly count these packets any longer (since 9.21). Therefore these counters are being removed. [CSCdi58345]

• This bug would have slowed down the cpu a little in doing the alignment correction. Other than that, it wasn't really a bug. [CSCdi61153]

• Under certain conditions an IPX packet may be received which has an incorrect IPX length in the IPX header, the CRC is good and we process this packet. We incorrectly pad the packet to the length specified in the IPX header instead of throwing the malformed packet away. [CSCdi63412]

• The SPX spoofing code does not automatically age out old entries from the SPX spoofing table. Over time, this table can grow very large. Some customer sites have reported that when the table is very large, the routers cease to send SPX keepalive acknowledgement spoof packets. At that time, reloading the router is the only way to get SPX spoofing functioning again. The workaround is to issue the command clear ipx spx spoof on a regular basis to clear the SPX spoofing table.

Commands added to facilitate the timeout process are:

ipx spx-spoof session-clear [minutes] (default 60) and ipx spx-spoof table-clear [hours] (default 16).

[CSCdi64010]

• When using network 'A', it was clashing with the keyword "ALL". So network 'A' could not be used in eigrp routing. This fix will remove that limitation. [CSCdi64830]

• After upgrading from Release 10.2(11) to Release 11.0(9), a show processor memory command indicated that the IPX SAP table memory usage grew by almost 300%. [CSCdi65740]

• Using IPX Enhanced IGRP can cause a memory leak when a link with an Enhanced IGRP neighbor is flapping. The SAP updates are queued and backed up, thus using increasingly more memory. [CSCdi66169]

• Directly connected SAP's which do not have a internal network numbers are being learned via EIGRP interfaces (i.e via serial interfaces) instead of interfaces from which they were originally heard.

It appears as though the router learns the SAP, sends it into the EIGRP cloud and if the other routers in the cloud do not split-horizon SAP's prefers the SAP being seen from the EIGRP cloud. Once this is created, in certain circumstances it is impossible to remove these SAP's from the table.

The workaround is to have all routers split-horizon SAP's. [CSCdi66719]

• When configuring the nlsp router-subcommands max-lsp-lifetime and lsp-refresh-interval, these two lines are saved in the wrong order in NVRAM. This will cause the lsp-refresh-interval to be ignored after a reload (though it stays in NVRAM). During reload the following warning will show up:

%NLSP: Refresh time must be less than LSP lifetime

This bug will cause no real harm, as the router will only fall back to the default lsp-refresh-interval of 15 minutes. There is no workaround for this bug. [CSCdi66788]

Protocol Translation

• On TCP-X25 one step translations, data is not dispatched to the pad connection when the idle timer set by X.3 parameter 4 expires. A workaround is to use two step translation. [CSCdi64955]

VINES

• VINES time server service may get out of synch when the system runs over 49 days. This is because only the low 32 bits of the internal clock counter are used when VINES computes network time. To give accurate time, the total elapsed time since system boot is now taken into account. This problem does not exist post-10.3 releases. When network time is out of synch, it is recommended that you either disable VINES time server service for Cisco IOS Releases 10.2 and 10.3, or upgrade to Cisco IOS Release 11.0 or 11.1. [CSCdi58105]

• VINES clients running Oracle application program can not make connection to a server due to packet reordering when vines route cache is enabled. This problem has been addressed in 10.3(13). A suggested workaround is to use process switching for those applications which can not handle out of sequence packets. [CSCdi59059]

• The system may halt unexpectedly when show vines interface is used. This behavior occurs when non-sequenced RTP is enabled. [CSCdi65525]

Wide-Area Networking

• PPP authentication using method none clears the line when using VTY-Async interfaces.

Workaround is being investigated. [CSCdi50049]

• ILMI has problems with sub-interfaces greater than or equal to 128 (0x80) and can confuse the switch. This problem appears with LANE on both Cisco 4500 and Cisco 7500 routers, but should not be related directly to LANE. A shut/no shut command sequence on the main interface resolves the problem. [CSCdi56903]

• ISDN NET3 cannot handle incomming FACILITY message when call is connected. [CSCdi60340]

• The Frame Relay MIB counters, including

frCircuitReceivedFECNs Counter, frCircuitReceivedBECNs Counter, frCircuitSentFrames Counter, frCircuitSentOctets Counter, frCircuitReceivedFrames Counter, frCircuitReceivedOctets Counter,

would be reset resulted by the "clear counters" exec level command for the interface over which the FR circuits were established. [CSCdi60658]

• Serial lines with SMDS encapsulation may take SegV catstrophic failures when enabled after reboot.

There is no workaround. [CSCdi60761]

• There is no way to prevent the "Trying..." message when making a pad call using the pad exec command. A new option, /quiet, is provided to suppress these messages. [CSCdi60860]

• Due to a network outage, the router appears to use pvc 0/17 as last ressort to access the LECS. The problem is that when going to that method, the system never comes back to a classical ILMI LECS research. A clear atm-vc, shut/no shut does not help and a complete reboot is required. [CSCdi62111]

• An error in the AIP ucode introduced in aip177-2/rsp_aip205-2 causes a race condition in the microcode and commands from the RP/RSP are rejected. When this happens, the following console messages are logged:

%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1011, VPI=0, VCI=262) on Interface ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC) %AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Teard own VC command (error code 0x8000) [CSCdi62445]

• RFC 1483 transit bridging is broken. It will be fixed in the next release (112-0.17) [CSCdi62961]

• Dialing into an async line and starting a SLIP/PPP session may fail even though the same IP address was previously allocated successfully for the particular user. [CSCdi63143]

• The printer printer-name line number global command uses the newline-convert option as default. There is no way to get the router to work without either the newline-convert or formfeed option. [CSCdi63342]

• Router may crash after issuing the sh ilmi command. [CSCdi63616]

• The amount of free system memory may decrease when using the command dialer hold-queue over an ISDN interface. [CSCdi63716]

• An unxpected restart or SCHED-3-PAGEZERO error will occur if an attempt is made to delete an undefined x29 profile from the configuration using the command no x29 profile name . [CSCdi64070]

• Part of the fix for CSCdi63245 broke bridging on HDLC links. This fix returns the broken code to its original state. [CSCdi64710]

• [CSCdi64909]

• PAP authentication fails when using TACACS+ as authentication method for PPP [CSCdi66077]

• Under unknown circumstances, an IPCP neighbor route may not be dynamically created as expected. [CSCdi66132]

• Setting a group range on a pre-Release 11.2 group-async interface while calls are active causes all async modem calls to be disconnected. [CSCdi66297]

• The configuration command "no fair-queue" does not get saved to NVRAM for group-async interfaces, so the system reverts to fair-queueing after a reload.

However, due to the default bandwidth of the group async interface being greater than that for a fair queueing candidate, it is actually not configured for fair queueing which is what it reverts to after a reload.

A workaround in order to enable and disable fair queueing on the interface is to use the bandwidth command to set an applicable value such that the "fair-queue" command is meaningful thereafter. [CSCdi66301]

• 2511 may reload at _bridge_enq when no bridging is configured. [CSCdi67157]

11.0(9) Caveats/11.0(10) Modifications

This section describes possibly unexpected behavior by Release 11.0(9). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(9). For additional caveats applicable to Release 11.0(9), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(10).

AppleTalk

• ARAP connection failures resulting in BAD EXIT and FORCE QUIT error messages are occuring at higher rates in 10.3(x) releases with the use of 28,800 kbps (V.34/V.fc/V.FAST) modems. [CSCdi57713]

• Router will crash if user queries for services in the virtual zone (configured via the 'appletalk virtual-network' command) from the Mac chooser.

This only occurs in 11.2. For other releases, the source changes contain only minor internal fix. [CSCdi60845]

• MacIP server will not give out IP address to MacIP client if the next address to give out is currently being use by a genuine IP device. The problem is the MacIP server does not skip over that IP address and assign the next available address and the process stucks. [CSCdi61526]

• Router crashed when trying to send ZIP Query to a route that has been poisoned. This is a timing problem where a route comes in, ZIP Query are set to be sent out, but then the route is poisoned. Route flapping can cause this problem.

This only occurs in 11.2. There is minor internal fix to prior releases. [CSCdi61658]

• According to Inside AppleTalk, 2nd Edition, page 8-18, the router should convert NBP BrRq to NBP FwdReq packets. Instead, the router sends NBP LkUp packets for nonextended networks.

Note: For routers that are directly connected to a Phase 1 (non-Phase 2) router in compatibility mode, the appletalk proxy-nbp network zone command must be used. This will allow the router to convert the NBP FwdReq to NBP LkUp to the Phase 1 router. [CSCdi61668]

Basic System Services

• The queue-list [n] lowest-custom [m] will not appear in a write terminal although it is properly accepted and the functionality is working. [CSCdi46873]

• In extremely unusual situations the router will display the following error message on a frequent basis:

%SYS-6-STACKLOW: Stack for level CXBus Interfaces running low, 0/1000

This message may eventually lead to the router haning. [CSCdi54119]

• In some circumstances involving very large lease time values, DHCP will treat the lease as continuously expired. [CSCdi55476]

• Configuring custom/priority queueing on an MBRI interface causes performance degradation. [CSCdi56473]

• User should turn backing store ON for slow interface processors. Routers without slow interface processors suffer performance degradation during peak activity. [CSCdi57740]

• The first entry of a vty password using password encryption will fail to encrypt the password. In other words, even though password encryption is on, the un-encrypted password will be visible in the configuration. [CSCdi57850]

• RSP-3-RESTART: interface Fddix/0, output stuck might be reported when heavy traffic is switched to a FDDI or HSSI interface. txacc value would show an abnormaly low value on the affected interface. 11.0(8) is the only maintenance release where this occurs. [CSCdi58659]

• The privilege, callback-dialstring, and nocallback-verify options to the username global configuration command can be written incorrectly to nvram. [CSCdi58793]

• As of 11.1(1.3) and 11.0(7.1), the username is not displayed in the output of the show users command after Tacacs+ authentication on a vty-async connection. [CSCdi58991]

• Autoinstall is not working in RSP. It is reported only in serial media; but, the problem is there in LAN media too. No workaround. Customer needs to upgrade to newer version which includes the fix for this. [CSCdi59063]

• 7507 with reloads with Segv exception when coded for direct-encapsulated RSRB. Workaround is to use FST or TCP encapsulation. [CSCdi59082]

• - A user telnets in and enters user@host for a tacacs directed request. - The host is defined as an "ip host" in the config and there are two listed IP addresses. - If the first ip host fails to respond the request will ignore the second defined IP host address and default to the "tacacs-server x.x.x.x" IP address. The customer feels it should use the second defined ip host address.

See the attached config for "ip host ttt" [CSCdi60064]

• A prematurely-closed HTTP connection to the router may cause it to reload. [CSCdi60283]

• Configuring ip tacacs source-interfacerequires that the specified interface exist at the time of this configuration. Due to command ordering in config file, this not always the case. [CSCdi60721]

• DHCP proxy-client feature does not release address leases when the router is being reloaded. [CSCdi60979]

• An anomaly in the implementation of the Cisco IP Multicast MIB can cause spurious memory accesses, potentially resulting in a system reload. The anomaly, introduced in IOS 11.0(1.0.5), will only cause problems when IP Multicast is enabled and SNMP is used to retrieve certain instances of the ciscoIpMRouteNextHopMacHdr MIB object. Since a "MIB walk" can trigger the problem, the suggested workarounds are to either disable SNMP, or use an SNMP MIB view to exclude access to the ciscoIpMRouteNextHopMacHdr MIB object. [CSCdi61124]

DECnet

• A router should send a CLNS redirect even if the source NSAP indicates that the sender is a Phase IV host, if the destination NSEL indicates that this packet is part of intra- Phase V cluster traffic.

The fact that the NSEL indicates intra- Phase V cluster traffic and that the source was a IV host means that the packet was originated by a IV host, converted by the router and sent to one of the Phase V cluster members, who decided that this packet should be sent to one of the other cluster members. In this case, the packet is sent back to the router (since the receiver presumably has no idea where this other cluster member is), and the router should send a redirect to the cluster member who first received the packet, indicating that the intended recipient is on the same LAN. [CSCdi52326]

• A DECnet "advertise" route (i.e. one created by the command 'dec advertise..') always remains in the "Down" state even when there is an ISO-IGRP route corresponding to the DECnet area.

If there is a matching route in the CLNS prefix table, then the DECnet "advertise" route behaves correctly. [CSCdi58806]

• A router running DecNet might present ALIGN-3-SPURIOUS error messages. This condition will occur only if the adjacency between neighbors expires.

It is a cosmetic problem and has no other impact on the router. [CSCdi60716]

EXEC and Configuration Parser

• When router reloads, the parser misinterprets the second line of an interface description and issues an error message. [CSCdi53912]

• The ipx gns-response-delay command will accept a range of values from 0-4294967295. If very large values are entered the configuration will display a negative value and unexpected results will occur. There is no reason to enter such large values (greater than approximately 500 hours). [CSCdi58426]

• The envm polling has been added. It is enabled by default, which means that the CSC/4 polls the ENVM for stats every 10 minutes. When enabled, if you issue a show environment all command from the enable prompt, the current statistics are displayed. If you configure the no envm polling command, the CSC/4 no longer polls the ENVM for stats. When disabled, if you issue a show environment all command from the enable prompt, the last set of statistics is displayed. If you save the no envm polling command in the configuration and then boot the router, the show environment all command displays a message indicating that no statistics have been collected. This command is being added only as a temporary fix for CSCdi33910. [CSCdi61554]

IBM Connectivity

• In extremely rare circumstances, the router may crashed while removing RSRB peers. This might occur only when running an AGS+ and the CSC1R/CSC2R Token Ring boards. [CSCdi39270]

• When automatic spanning tree (AST) is configured on multiple routers in a high-redundancy topology, a bridge protocol data unit (BPDU) broadcast storm might be triggered. [CSCdi41851]

• A Cisco 4700 router running DLSW+ and SDLC might crash in the SDLC process. [CSCdi48414]

• When using Cisco's APPN/DLUR feature, a DLUR serviced downstream PU may have difficulty establishing a session with a VTAM host. The sense code issued is 80140001 [CSCdi50504]

• dlsw netbios slow session bring up [CSCdi50688]

• - Release Note -

SDLC test output is now sent to a telnet session when terminal monitor was turned on. If you are logged into the console, then the output is received fine. [CSCdi51539]

• When using APPN/DLUR, and using the takeover logic where DLUR attempts to find a new DLUS for its served PUs, a possibility exists that the served PU will be rejected by the dlus on the first retry attempt. Subsequent retrys will succeed.

In addition, a downstream PU may attempt to connect to a backup dlus prematurely when the primary should have been tried first. [CSCdi52060]

• When using APPN/DLUR, if the session pair between the DLUR and DLUS which transports SSCP/PU/LU data is interrupted at the exact time that the dlur is receiving data on the session, the DLUR may not recover properly, causing the new recovered dlus/dlur connection to appear up, but not transporting data correctly. [CSCdi53519]

• If a new CIP Internal LAN Interface is added following a dbus internal error, the CIP Virtual Port x/2 may not be found. The workaround is to reload the router. [CSCdi54224]

• Show Dlsw peer shows uptime zero [CSCdi54753]

• Problem fixed with this DDTS:

CIP variables not included in the CISCI-CHANNEL-MIB

Added: cipCardSubChannelCmdretries to cipCardSubChannelTable Added: cipCardDtrBrdLastStat and cipCardDtrBrdNextStat to cipCardDaughterBoardTable [CSCdi55031]

• In a parallel SDLLC network, the ACTPU RSP is never received by the host. [CSCdi55142]

• Unable to configure multiple qllc dlsw ... commands. [CSCdi55749]

• The routers APING client which is invoked by the "appn aping" exec command always terminates with a deallocate(ABEND). This will result in an FMH-7 on the session indicating that the transaction terminated abnormally, even though everything was OK.

This does not seem to have any impact on our users and the work around is to ignore the extraneous FMH-7 frame on any line traces you may be looking at. [CSCdi56698]

• On rare occassions, CSNA Virtual Port X/2 may hang in down/down state following a Shut/No Shut or Microcode Reload of the Channel Interface. The workaround is to reload the router. [CSCdi58517]

• When using APPN/DLUR in a multiple VTAM host environment, issueing v inact,force on the lu name from the DLUS host does not cause proper cleanup of the existing LU-LU session that may have been up at the time of the inactivation. When the LU is reactivated, session establishment may be impaired since the application host and the dlur believe the original session is still active. [CSCdi58699]

• If you encouter a problem with fras at a level greater that IOS 10.3(7.5) and you receive a message "IBM: Unknown L3 PID, fr_doencap failed" backoff to down to 10.3(7.5) or lower. Engineering is currently investigating. [CSCdi58769]

• The router is crashing with message System restarted by bus error at PC 0xD0D0D0D, address 0x0. The crash happens when using promiscuous TCP peers. The crash occurs when peer structures get deleted (transmission line problems, peer routers reloads etc.) while still being used by TCP. THe work around is to define static peers. The fix is now available in 10.3(12.1). If there is a stack trace action_b() will be one of the entries.

Note: CSCdi61278 is a follow on fix to this problem. [CSCdi58842]

• When a 4000 DLSw router configuration is changed to include DLSw priority, the router may reload. [CSCdi58884]

• Directed source-route bridge frames with control field of 010 instead of the more usual 010.The architecture supports a control field of 0XX for nonbroadcast frames so this appears to be a bug. [CSCdi59100]

• LNM Resync command does not work with 10.3(10.2) on 7000 if the router is configured for IBM automatic spanning tree support. [CSCdi59890]

• The QLLC features, npsi-poll and proxy XID, were not operating correctly for DLSw+. [CSCdi60002]

• DLSW LLC Ethernet 80d5 bad frames after a llc retransmission [CSCdi60102]

• The Cisco APPN feature may reject a connection attempt from a partner node which has changed its support of the parallel tgs on xid3 due to reconfiguration, software change, use of a different product, etc. [CSCdi60238]

• DLSW reachability fragments storage [CSCdi60373]

• APPN/DLUR may leak very-big buffers in some situations when it is retrying connections to a DLUS. The show buffer command will show a large number of very-big buffers have been created and relitively few will be in use. [CSCdi60931]

• stun schema cnt offset 0 length 1 format hexidecimal must be entered as stun schema cnt offset 0 length 1 format hexadecimal but is saved as stun schema cnt offset 0 length 1 format hexidecimal When the router is reloaded the following error is printed d7c#conf mem

stun schema cnt offset 0 length 1 format hexidecimal ^ % Invalid input detected at '^' marker. [CSCdi60992]

• Even if no sdlc xid is configured for SDLC support in DLSw, a null XID format 0 Type 2 is generated, with IDBLK/IDNUM of zeroes. This has the surprising effect of allow you to use DLSW as a sort of SDLC serial tunnnel without configuring XIDs. Once this bug is fixed it will be necessary to configure sdlc xid for all the stations in order to use DLSw+ to replace STUN-local-ack. [CSCdi61007]

• When using APPN/DLUR, the Cisco network node will never set the response indicator in XID frames that it generates, even if it sends the XID frame in response to a command xid received from the partner node. There are some implementations of pu2.0 and pu2.1 devices that cannot recover from this, even though most do. [CSCdi61157]

• The router is crashing with message System restarted by bus error at PC 0xD0D0D0D, address 0x0. The crash happens when using promiscuous TCP peers. The crash occurs when peer structures get deleted (transmission line problems, peer routers reloads etc.) while still being used by TCP. The work around is to define static peers. If there is a stack trace action_b() will be one of the entries.

This ddts is a follow on fix to CSCdi58842. [CSCdi61278]

• Enable DSPU/FDDI support for end-stations attached directly to FDDI media [CSCdi61351]

• This message is harmless. It was added in a previous release to detect a race condition that caused a crash. This ddts fixes the race condition.

Previous crashes that were likely caused by this race condition : CSCdi61278 CSCdi58842 [CSCdi61790]

• CM/2 1.1 has a problem setting the bind pacing indicator in the bind response which can cause 3270 sessions though Cisco's APPN/DLUR to fail with sense 10020000. Cisco is able to workaround the problem by resetting the bind pacing indicator before passing the bind response on to VTAM. [CSCdi62917]

• Several 3270 emulators cannot handle fixed pacing and require a non-paced secondary send stage to function properly. To interoperate with these emulators, Cisco APPN/DLUR must support and default to non-paced traffic on the secondary stage for dependent LU sessions managed by dlur.

Prior to this fix, an emulator session requireing non-paced traffic would fail with sense 20110005. [CSCdi63136]

• A router running remote source-route bridging where the input explorer queue overflows may crash with the message "%ALIGN-1-FATAL: Illegal access to low address from srb_enq." [CSCdi65489]

Interfaces and Bridging

• While doing "show ip cache" when autonomous switching is configured CBUS cache hits always remain at 0. [CSCdi35663]

• The line configruation command modem ri-is-cd is obscurely named. modem dialin should work instead. [CSCdi42491]

• FEIP's keepalive will not detect line protocol down (disconnected cable) when configured for full duplex so reliance on this feature to detect cable faults is inaccurate. The only known workaround is the periodic tracking of successful transmissions/reception on the suspect interface. [CSCdi48337]

• Under rare conditions packets could leak. The conditions were: - when an incoming compressed frame-relay packet was received but frame-relay compression registry was nnot available - when an incoming compressed fr packet was received but the decompression context did not exist.

Condition (1) could result in a large leak. Condition (2) would leak until the context was dynamically created, generally in about 1 second. [CSCdi54825]

• If a TRIP (token ring interface processor) is present in cisco 7000 series routers, token rings which beacon frequently may cause performance degradation of the router. The source of the problem is tql may increase when a beacon occurs, causing the interface to hold more memd buffers. Performance degradation will result. This is not a problem on cisco series 7500 routers. [CSCdi55758]

• After issuing "sh cont cam" and pressing space bar to page down, the router hangs and has to be power cycled to continue. [CSCdi56241]

• If a serial interface on FSIP sees lots of giants, then there is a chance to get %DBUS-3-CXBUSERR: Slot x, CBus Error. If Slot x has FSIP then look into sh int for this slot. If any of the serial interface on this slot shows giants, then chances are high that this bug is causing the problem. This will happen in both 7000 and RSP. If this error occurs, see sh int of the above slot. The workaround is to load the new image which contains new ucode (fsip10-15 or latter for 7000 and rsp_fsip202-5 or latter for RSP).

/Ramki [CSCdi58194]

• SABME (for Netbios) are not correctly bridged from FDDI to serial lines (using HDLC encap). The bridging of SABME from fddi to ether and reverse is Ok. The problem appears in 10.2, 10.3, 11.0 and 11.1. [CSCdi58733]

• An AGS running 11.0(8) with a CSC-C2FCI doesn't bridge ethernet packets encapsulated in a fddi frame correctly.

Work aroung is to run 10.3(x). [CSCdi59204]

• Transparent bridging over token ring on 2500, 4000, and 4500 failed due to a bug introduced in 11.0(8.4), 11.1(3.1) until today (6/5/95). [CSCdi59627]

• 7500/RSP performance is degregated with ISL,fast-switching and access-lists applied. Work-around is to disable fast-switching on the main interface.

Cisco Systems expects to resolve this caveat in a future IOS release. [CSCdi59825]

• If IPX broadcast packets are present on a token ring attached to a 4000, 4500, or 4700 router, and neither IPX routing nor bridging is configured on the router, the router will lose other broadcast packets on the token ring. This can cause secondary failures in protocols such as EIGRP and IS-IS.

A workaround is to configure "ipx routing" (it is not necessary to assign any IPX addresses in the router, so it will not actually participate in IPX.) [CSCdi61501]

IP Routing Protocols

• OSPF fail to install parallel external route, which LSA has no forwarding address set, through multiple ABRs. [CSCdi45110]

• IP accounting does not contain valid entries. The source and destination ip addresses do not exist in the network. The invalid host entries in the ip accounting table only appear at power up and only with the aip card in the 7000. This impacts the accounting and the cpu utilization goes up by approx 10%. There is no known workaround except when the customer removes the AIP. This is known the appear in releases 10.3.5.4 and 10.3.7. [CSCdi45135]

• During show ip ospf, if ospf is unconfigured, probably through a different session, the router would crash. [CSCdi58092]

• A router that receives an ICMP echo request for a network or subnet address that it is directly connected to may send an echo reply with a source address that has nothing to do with the destination network or subnet address in the initial echo request. [CSCdi58660]

• OSPF default-information originate command limits the metric value to be no larger than 65535. However, this value should be allowed to be 24 bits in length. A workaround using route maps exists. [CSCdi58666]

• When there are many HSRP groups configured on a FDDI interface, it becomes more easier to see interface resets.

When a HSRP group changes from active state to any other non-active state, HSRP will reset the interface to de-register the virtual MAC address from the address filter.

The disruption may become unexceptable if there are many HSRP groups on a fddi interface change state many times in a short period of time.

But the bad situation was seen when there were over 60 HSRP groups defined on a fddi interface.

I would say the severity of this bug depends on the number of HSRP groups defined on a fddi interface.

Now for this bug to kick in the HSRP state has to change and for that to happen we have to miss 3 HSRP hellos (9-10 secs). [CSCdi59054]

• Disabling optimum switching on an RSP platform has no effect. [CSCdi59203]

• If an EIGRP candidate default route is overwritten by another protocol, the EIGRP topology table may be left in a state where the candidate default route will not return to the routing table. A workaround to this problem is to clear all EIGRP neighbors. [CSCdi59276]

• With IGRP and RIP, IP unnumbered interfaces using PPP encapsulation receive but do not process routing updates of Major Network Summaries correctly. The major networks show up as host routes instead of network routes. This affects all ip unnumbered interfaces using PPP encapsulation which are pointing to different major networks. This affects dedicated links as well as DDR links using RIP or IGRP.

The workaround for this problem is a floating static route for the majornet matching the PPP created host route using a majornet mask pointing to the PPP created host route. i.e., if the host route is 192.1.1.1, then using 'ip route 192.1.1.0 255.255.255.0 192.1.1.1 250' should cure the problem. [CSCdi59425]

• If a non-summary route is present in the routing table that exactly matches an EIGRP summary route, but the summary route is not in use (because there are no more specific routes), the route will be advertised only on interfaces on which the summary is configured.

There is no workaround to this problem. [CSCdi59446]

• 4500/4700 - HSRP on ethernet interface may come up in a state of init with timers set to 0 upon reloading of the router.

To recover, perform a shut/no shut on the interface. [CSCdi60445]

• Under some circumstances, EIGRP summary routes may remain in the routing table even though all more specific routes that were part of the summary were deleted. The workaround is to delete and reconfigure the summary (if manual) or disable and reenable autosummarization (if automatic). [CSCdi60515]

• A router running EIGRP (Appletalk, IPX, or IP) which has input route filters configured may improperly filter routes that it should install.

Additionally, if a router running IPX-EIGRP receives an update containing an external route that was originated by the router itself, the rest of the update will be ignored.

There is no workaround to this problem. [CSCdi61491]

• IP ARP mobility causes unnecessary routing protocol updates by deleting and then re-adding the same route repeatedly (and hence wastes CPU).

Also, attempts to refresh ARP entries every minute, rather than every keepalive interval. [CSCdi61730]

• When an interface flaps, it is possible for OSPF to remove a healthy network LSA accidently and result in a missing route. This happens in the situation where a segment flaps causing the interfaces of multiple routers to flap at the same time. The DR will bounce from one interface on one router to another interface on a second router and back to the first router. During the transition the network LSA of the common segment will disappear causing that subnet not to show up in the routing tables. [CSCdi61982]

• A problem introduced in Releases 11.0(9.3), 11.1(4.2), and 11.2(0.14) might cause OSPF to fail to install an external route that has no forwarding address. This occurs if the next hop of the path to the ASBR changes and its cost increases. The workaround is to create an external LSA with forwarding address set. [CSCdi64208]

ISO CLNS

• A router reload may occur when CLNS traffic is fast-switched. This regression affects 10.3(12) and 11.0(9) maintenance releases. [CSCdi57629]

• A router running IS-IS will not clean up its adjacency database properly when switched from being a level-1/level-2 router to being level-1 only. A workaround is to manually clear the adjacency database (using the "clear clns neighbors" command) on the reconfigured router and on all of its neighboring routers, or restarting the router. [CSCdi58953]

• If IP-ISIS is configured on an unnumbered interface, the route corresponding to the numbered interface pointed to by the unnumbered interface may be reported multiple times in that system's LSP. There is no workaround for this problem. [CSCdi60661]

Novell IPX, XNS, and Apollo Domain

• The NLSP next hop uses a different addressing scheme than RIP. This may cause an issue when setting up dialer maps. A workaround for it is to configure a dialer map that uses the same addressing scheme as NLSP. [CSCdi37797]

• IPX SPX spoofing might fail when using RPRINTER across a spoofing interface. [CSCdi42806]

• On a router running both IPX RIP and IPX Enhanced IGRP, turning off IPX RIP on the router using the command no ipx router rip and then turning it back on again causes a spurious no redistribute rip command to appear under the ipx router eigrp AS command. [CSCdi47813]

• When an EIGRP route is lost, it is placed in holddown. The hold down time takes 300 seconds to expire. This DDTS reduces it to 5 seconds. It also provides a new subinterface command ipx hold-down eigrp AS# xxx where AS# is the autonomous number and xxx is the hold down time in second if the user wants a longer or shorter hold down timer. [CSCdi57042]

• IPX SNMP request sent to the router may accumulate in the input queue when SNMP is disabled, these packets are not processed, possibly causing full input queues. [CSCdi57589]

• This was because 1. we were not looking at the maximum limit on the number of parallel paths, while learning sap's. 2. we were not pruning the sap list, in case the maximum-paths is reduced. [CSCdi59116]

• Under certain conditions, an alignment error may be generated when an IPX fastswitch cache entry is created. Specifically This can occur on token ring or fddi when multiring is configured and a RIF is present for an odd number of hops. [CSCdi60014]

• Doing 'no ipx router eigrp xxx' may cause the router to reload if there is a lot of saps in the router and while the sap table was changing. [CSCdi60174]

• The following new command sets a maximum limit on the number of cache entries:

ipx route-cache max-size size

size is the maximum number of entries allowed in the IPX route cache.

If the cache already has more entries than the specified limit, the extra entries are not deleted. To remove stale entries, use the ipx route-cache inactivity-timeout time command to select a suitable value for the cache aging parameter. [CSCdi60228]

• IPX Services with a route metric of 1 tick and 1 hop away will show as "conn" in the show ipx server display. Only those directly connected services should show as "conn". [CSCdi60499]

• When the optimal sap is lost and NLSP has an alternate path to the same sap, the alternate sap was never installed. [CSCdi61173]

• If an IPX EIGRP distribute list access-list is changed EIGRP might not be notified of the change and the nieghbors may contain information which violates the filter. [CSCdi61632]

• Defining a static IPX route using the peer address of an IPXWAN neighbor may fail with a message about multicast addresses. The workaround is to avoid using eight digit IPX Internal Network numbers which have an odd numbered first byte. A 7 digit or fewer length IPX Internal Address also will not give this error message. [CSCdi61993]

• CSCdi63412 introduced an alignment error, in particular for IPX frames routed from Token Ring networks with multiring enabled. Alignment errors occur in process-switched and certain fast-switched paths. [CSCdi63741]

• CSCdi58363 introduced a problem where NLSP-learned servicex and SAP-learned services overwrite one another, causing unstable service table information. This is particularly a problem in networks with redundant paths. There is no workaround. [CSCdi63771]

Protocol Translation

• The count of active users of an inbound TCP protocol translation can be incorrect, if the printer option is used, and outgoing connections fail. [CSCdi59591]

• The tcp source-interface option is incorrectly added in NVRAM to a TCP--PPP translation if IPX is also used on the translation. [CSCdi60436]

• The stream and binary keywords do not have the correct effect on the outgoing TCP connection when translating from X.25 to TCP, if the swap global option is also used. [CSCdi60641]

VINES

• SNAP is the default vines encapsulation on a LAN Extender interface while VINES servers and clients on Ethernet support ARPA. This discrepancy causes network connectivity problem when remote LAN is connected to a core router via LAN Extender. Now the VINES router defaults to ARPA on a LEX interface and either ARPA or SNAP can be configured on LEX interfaces. [CSCdi57934]

Wide-Area Networking

• No user action is required when the ATM-4-OVERSUBSCRIBED appears, so this message has been moved to only appear during debugging. [CSCdi55228]

• The ATM Interface Processor (AIP) used with a RSP processor may stop receiving data if OAM cells are inserted in the incoming cell flow. [CSCdi55512]

• Lane interfaces (atm sub-subinterfaces used foe LEC) appear as non-broadcast. This appears for ospf (workaround is to explicitly mention it is broadcast) or with ntp. [CSCdi55849]

• When used as a LANE server (LECS, LES, BUS) as well as ARP server with RFC1577 in a network, LANE will work well. However, RFC 1577 will not work correctly. Although the MTU is set to 1500 to support both features, a CIP ARP is not possible. [CSCdi56175]

• The 7500 (rsp image tested) can block some packets in its incoming queue and after a while the atm interface won't accept new data. This occur with LANE (~50 ELANS defined) and bridging between some of them. [CSCdi56897]

• If the router receives an incoming ATM SVC call with an SDU size incompatible with the configured MTU on the ATM interface, the router may crash. The problem is present in release 11.0(8.3), 11.0(8.4), 11.1(3.1), and 11.1(3.2). If the router is generating the following warning messages in earlier releases, it is likely that the defect will affect them if the images listed above are installed:

%ATM-4-MTUCALLMISMATCH: Incoming call has mismatched maximum transmission unit

If the remote device is re-configured with the correct SDU size, the problem will not occur. [CSCdi57676]

• If two interfaces connect to the same destination but are not part of a dialer group or ISDN interface, and one interface goes down, then the neighbor route (if applicable) may be removed from both interfaces. A neighbor route is a directly connected route with zero metrics that is installed if the peer's IP address is negotiated and no other to that address exists for the interface. [CSCdi57995]

• The router may reload if you run "debug ppp negotiation" while negotiating the compression control protocol (CCP). [CSCdi58710]

• Under very rare timing circumstances, a router or c5000 running a LANE server-bus (LES/BUS) can issue

%LANE-3-LANE_SIG_INV_MSG: invalid msg received (4 A8CF4E A)

The error is harmless .... The LES/BUS continues to operate normally after this message. [CSCdi59010]

• When the atm link is up but LANE does not get operationnal to a certain point (for instace ILMI ko), the system will consider subinterfaces as up although associated LECs are not operationnal. By this way, the system will give routing problems. [CSCdi59709]

• ISDN PRI routers running primary-5ess switch type may not accept an incoming SETUP message if the Called Party Number IE has an "unknown" numbering plan. [CSCdi59816]

• Release-note This bug was cloned to CSCdi63716, and ultimately fixed in 11.0(10.3), 11.1(5.4) and 11.2(0.22).

If dialer holdqs are enabled, an outbound call could crash the box. [CSCdi60578]

• Configuring the nasi enable command will result in the following unwanted line in the config:

ipx route-cache nasi-server enable [CSCdi60747]

• It is currently not possible to fastswitch between secondary ip networks defined on LANE subinterfaces. This can make LANE less performant than ethernet. A workaround is available if only one vlan needs to be defined (one LEC). We configure it on the main interface which allows fast-switching if 'ip route-cache same-interface' is configured. [CSCdi60896]

• Receipt of a data or reset packet on an X.25 permanent virtual circuit (PVC) that is switched over a TCP connection (XOT), while it is waiting to connect with the remote TCP peer, delays the setup of the TCP connection with that peer. If data or resets are received often enough, the setup can be delayed indefinitely. [CSCdi61933]

• ISDN PRI routers running primary-5ess switch type may not accept an incoming SETUP message if the Called Party Number IE has an "unknown" numbering plan. [CSCdi65484]

11.0(8) Caveats/11.0(9) Modifications

This section describes possibly unexpected behavior by Release 11.0(8). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(8). For additional caveats applicable to Release 11.0(8), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(9).

AppleTalk

• The BADEXIT error messages for ARAP need to be more specific about the problem being encountered. [CSCdi57035]

• Users may see AT-2-ASSERTFAILED messages when router is misconfigured. [CSCdi57321]

Basic System Services

• Reloading the microcode from ROM on an Interface Processor board in a Cisco 7500 series router can cause the system to enter a rebooting loop that requires a system reload for recovery. The ROM-based microcode on the Interface Processors is only compatible with Cisco 7000 series routers. [CSCdi44138]

• A Cisco 7500 series router can crash if Frame Relay interfaces are active. [CSCdi49868]

• The command priority-list is not written correctly in NVRAM. This problem affects prioritization after reload of the router. [CSCdi51014]

• When authenticating using PAP, AAA and RADIUS or TACACS+, the remote client may retransmit an PAP repsonse if the authentication server is slow to respond. This second authentication may have unexpected side effects in the case of accounting, one-time password systems, or server performance. [CSCdi51333]

• The router may produce spurious %SCHED-2-SEMUNLOCK error messages. [CSCdi52328]

• On RSP interfaces, optimum switching is supposed to be the default. However, depending on the link order of the image, it can default to off. [CSCdi54567]

• The 32mb memory option on the 4000m splits memory up into 2 discontiguous chunks. This breaks the uncompress routine which expects memory to be contiguous as well as making the upper 16Mb of memory inaccessible. The memory test also fails to recognize the 2 chunks. [CSCdi55171]

• NTP will occasionally get a %SCHED-3-THRASHING error. There is no workaround to this problem. [CSCdi55346]

• Under some conditions SNMP queries of the CISCO-ENVMON-MIB can cause the system to reload. This occurs when an SNMP get-request is received that tries to retrieve instance 0 of an object in the ciscoEnvMonSupplyStatusTable. Since the instances of this table start with 1, the correct processing is to return a noSuchName error (or noSuchInstance if SNMPv2 is used). A workaround is to not use SNMP get-requests that specify instance 0 for objects in the CISCO-ENVMON-MIB. Instead, applications should either use SNMP get-requests starting with instance 1, or else use SNMP get-next-requests or get-bulk-requests. [CSCdi55599]

• All ATM OAM frames will be dropped on the RSP, and will not be processed. [CSCdi55969]

• A router with ip http server configured may pause indefinitely and unexpectedly restart when a connection is attempted from a chimera web browser. A workaround is to use different browser software. [CSCdi56662]

• Access to the http server on the router should be able to be limited via the use of the access-group command. [CSCdi57075]

• If you are running SNMP and have more than approximately 512 interface addresses, you may get the following error messages:

% Maximum number of parties reached. % Memory allocation failure

You can ignore this if you are not using SNMPv2 and parties. [CSCdi57672]

DECnet

• When DECnet conversion is enabled, discard routes are inserted into the Connectionless Network Service (CLNS) routing table. [CSCdi40503]

EXEC and Configuration Parser

• The exec command "show tech-support" command has been added to help collect general information about the router when reporting problems.

The command does the equivalent to the following show commands: show version show running-config show controllers show stacks show interfaces show buffers show process memory show process cpu [CSCdi47180]

• The terminal download EXEC command cannot have a privilige level assigned to it using the with the privilige command. [CSCdi52164]

• When using a backslash ("") in commands, the parser will disregard the backspace if it is preceded or followed by a space. For example, in a chat script, "ATDTT" will be interpreted correctly but "ATDT T" will not. [CSCdi55084]

• The "write memory" and "copy running-config startup-config" command now work at privilege level 15.

The remaining "write" and "copy running-config" commands still operate at the users current privilege level due to security considerations. [CSCdi55809]

• The AUX port in Cisco 2520 through Cisco 2523 routers cannot be configured for asynchronous services. [CSCdi56563]

IBM Connectivity

• When a MAC Address cache entry is configured with a mask or a NetBIOS name is added with wildcards to the cache, they are not handled correctly by the DLSw+ reachability cache. The same problem exists when the resource names are received with wild card or mask from the remote peer as part of the peer capabilities exchange process. [CSCdi36046]

• When a Synchronous Data Link Control (SDLC) device is reloaded, the connection is not automatically reestablished. To reestablish the connection, issue the configuration commands shut and no shut. [CSCdi42369]

• Qualified Logical Link Control (QLLC) devices that are connected through a router using QLLC/Logical Link Connection, type 2 (LLC2) conversion might occasionally experience poor response time. [CSCdi44923]

• We allow the definition of a link as a limited resource, but the function is not supported. [CSCdi45410]

• On a c7xxx router installed with a CIP running CSNA, if you turn on 'debug channel vlan', you get the following message

CIP ILAN(Channelx/2-TokenRing): packet dropped - vencap failed

for explorers received on the router that are not destined for any of the CIP internal LAN MAC addresses. For these explorers not destined for a CIP internal LAN MAC address, the above debug message should not be displayed. [CSCdi46832]

• Interfaces that have physical Units (PU) that are SDLC attached using DLSw+ will hang in the XIDSENT state after forwarding a non-activation XID3 message. Interfaces that have the PU token ring attached are not affected. [CSCdi47090]

• DLSW debug - change dlsw debug to allow more options - netbios, no iframes, etc [CSCdi48007]

• In some cases, the RIF of explorer frames is not checked to ensure that the ring defined as the DLSw+ ring-group has not already been traversed. In the majority of situations, this should not be an issue, but in some topologies it may result in moderately higher explorer traffic loads than are strictly required. Note, there are not any situations in which this would cause an explorer loop. [CSCdi50712]

• The following message may appear when microcode is downloaded to a CIP with 128M DRAM. DBUS-3-SW_NOTRDY: DBUS software not ready after cxbus_soft_reset(), or DBUS-3-SW_NOTRDY: DBUS software not ready after dbus_slot_enable()

The CIP will be unable to successfully initialize. This may result in other messages, like: CBUS-3-CTRLRCMDFAIL1: CBUS-3-DAUGHTER_NO_RSP:, or CBUS-3-CCBPTIMEOUT: associated with the slot that the CIP is in. [CSCdi50739]

• If the link to the host goes down while APPN is active with DLUR sessions, there may be some memory leaks. [CSCdi51537]

• A Cisco 4700 router may report intermittent "SYS-2-LINKED" error messages even though there is no memory shortage. [CSCdi52327]

• Unnecessary creation of RIF entries for bridged IPX explorers. [CSCdi52464]

• When using DLSw direct encapsulation over frame relay with pass-thru mode, SNA session between PC with Attachmate and the FEP can not established.

Work around is using direct encapsulation over frame relay with local-ack. [CSCdi52568]

• In some mixed vendor bridge environments, Automatic Spanning Tree may not become active if the Cisco platform is the root bridge. The message-age-increment option is now available as part of the source-bridge spanning command to assist with the message age count manipulation. This hidden command may be needed when the existing MAXAGE value is insufficient for network diameter and the maximium age is not configurable by the vendor bridges. [CSCdi53651]

• The LAN Network Manager (LNM) fails to link to the router's source bridge after the Token Ring interface is shut down on the remote router. The show lnm bridge command continues to display Active Link to the LNM. This problem does not occur when bridges are linked locally to the LNM. The workaround is to remove the source-bridge command from the Token Ring interface and configure it back in. [CSCdi53954]

• When local-ack is configured, and a STUN packet is received, the router displays the message "%LINK-2-NOSOURCE: Source idb not set -Process= (interrupt level), ipl= 4 -Traceback= (traceback info)." [CSCdi54162]

• There is a problem which results in token ring ports being enabled for use by DLSw even if they are not defined to bridge to a virtual ring group. [CSCdi54558]

• Some NetBIOS applications that require a UI frame in response to Add Name Query cannot connect using a DLSw peer on demand if the NetBIOS circuit is the initial circuit that triggers the peer-on-demand to connect. [CSCdi54796]

• The interface had the correct group number the first time it was configured. Do not issue the bstun group command to the same interface with the same number. [CSCdi54900]

• A Sniffer trace shows duplicate ring numbers in the RIF when proxy explorers are in use. New SNA sessions fail to connect to the FEP. The workaround is to issue the clear rif command. [CSCdi55032]

• When using "dlsw peer-on-demand-defaults fst", the FST peer-on-demand may pass user data frames before the FST peer is connected. This may result in the user session bouncing if the peer does not successfully connect. [CSCdi55172]

• When a DLSw peer router is reloaded and a DLSw peer connection is attempted while ip is converging, the peer conection may enter a connect loop that may cause a several minute delay in the peer connection process. [CSCdi55437]

• no source-bridge remote-peer may cause the router to reload. This has been rarely observed. [CSCdi55919]

• A connection to a DLU (DSPU or APPN) across RSRB may fail if the remote SAP address is not enabled at the destination router. The workaround is to enable the remote SAP address. [CSCdi56660]

• Spurious accesses when source-bridge proxy-explorer configured. [CSCdi56744]

• A problem has been discovered with the Cisco 2520, 2521, 2522, and 2523 routers where the router can experience poor Synchronous Data Link Control (SDLC) performance on the low speed asynchronous/synchronous serial ports (interfaces serial 2 through serial 9). The low speed asynchronous/synchronous serial interface has trouble maintaining clock synchronization when configured for all of the following parameters at the same time:

- encapsulation sdlc-primary or encapsulation sdlc-secondary - nrzi-encoding - The interface is configured as a DCE.

The low speed asynchronous/synchronous serial interface may drop SDLC frames with this configuration. The symptoms of this problem are poor performance and excessive Cyclic Redundancy Check (CRC) errors on the interface (as seen via the show interface command).

The fix for this problem requires: hardware version 00000002 and a software fix for this defect, which is incorporated into Cisco IOS Release 11.0(9) and 11.1(4), and later. All Cisco 2520, 2521, 2522, and 2523 routers manufactured before May 24, 1996 are subject to this problem.

To identify whether your router is affected, issue a show version command. The hardware revisions that are subject to the problem are "00000000" and "00000001". Hardware revision "00000002" contains the hardware fix that resolves this problem:

cisco 2520 (68030) processor (revision E) with 4096K/2048K bytes of memory. Processor board ID 02351913, with hardware revision 00000002 [CSCdi57040]

• DLSw FST encapsulation does not work over WAN, Token Ring, or FDDI interfaces. [CSCdi57207]

• APPN pings from this NN across a border node fail. (Sessions from attached ENs work correctly.) [CSCdi57323]

• The APPN DLUR router may unbind LU sessions with the DLUS and the downstream node if fixed pacing was enabled on the session bind request from the DLUS. If this is the case, when the user attempts to logon from the downstream device, the USS message 7 with a sensec code of 0835 0009 may be displayed. [CSCdi57729]

• An APPN router may unbind an LU6.2 session after receiving an unsolicited IPM with a nonzero next-window size. [CSCdi57730]

• For DLSw FST over WAN frame-relay, peers will connect, but user circuits will not connect. [CSCdi57997]

• In any software image with CSCdi55177 integrated, you will see the DLSw+ backup-peer brought up while the primary peer is still up, approximately 10-15 seconds later. This backup will stay active despite the fact that the primary is connected. [CSCdi58140]

Interfaces and Bridging

• Turning on ipx route-cache sse with microcode version SSP10-12 or SSP10-13 produces a mismatch between the frame length on odd-byte 802.3 IPX packets and the 802.3 length. Novell devices might not recognize these packets, resulting in communication timeouts.

The following three workarounds can be used:

-- Turn off padding on process-switched packets via the command: no ipx pad-process-switched-packets

-- Configure the router for Autonomous Switching instead of SSE switching via the commands: no ipx route-cache sse ipx route-cache cbus

-- Turn off SSE switching: no ipx route-cache sse [CSCdi42802]

• On the high-end routers, empty FDDI 17 byte frames without LLC layer were counted as runts though being enabled by the standards. [CSCdi45026]

• Groups of 4 ports on Cisco 2511 may have DSR behaving in unison on a single stimulus. Reloading the router is the only workaround. [CSCdi49127]

• Customers running with the old non EOIR capable 1.0 hardware version MIP will notice that a controller reset is necessary on the MIP for it to work again after adding or removing another card when running the new MIP EOIR capable code in the 11.0(8) and later code. This controller reset should not be necessary. [CSCdi49807]

• On a 7000 with a Silicon Switch Processor, access lists used for packet filtering which contain an entry matching all IP packets followed by two or more entries can cause the router to reload.

As a workaround, one can remove all access list entries following the entry which matches all packets. Doing so will not change the behavior of the access list.

As an example, change:

access-list 116 permit ip any any access-list 116 permit tcp any any gt 1023 access-list 116 permit tcp any any eq smtp

to:

access-list 116 permit ip any any [CSCdi50886]

• Bridging of ipx raw between ethernet and fddi on 4500 does not work in 10.2 for unicast packets. With 11.1 the problem appear for both unicast and broadcasts. 7000 bridging of ipx raw is correct for 10.2 (11.1 untested). [CSCdi53363]

• While booting a Cisco 7500 router, the FIP FDDI interface might momentarily beacon the ring, causing ring instability. [CSCdi54444]

• After starting CMT, one second is allowed for the FDDI interface to come up. For some FDDI rings that isn't long enough, and the router should wait five seconds instead. [CSCdi55837]

• Under certain conditions, a SLIP interface may show as 'looped'. SLIP does not have the ability to detect looped interfaces, so this display is incorrect. [CSCdi58271]

IP Routing Protocols

• When using Enhanced IGRP, the auto-summaries advertised could be mishandeled by the router.

This defect will not be fixed in 10.0 because of its low severity and because it was found internally. This is because 10.0 is in its Mature Maintenance Phase. [CSCdi21082]

• There is a small delay between the time OSPF marks a LSA as deleted and the time the LSA is actually removed. Within this small window, if OSPF receives an old copy of the LSA which has a higher sequence number, probably from some new neighbors through database exchange, OSPF will be confused and not able to remove the LSA. Customer will observe self-originated LSA stuck in the database. The stucked LSA would be removed automatically when the router regenerate a new instance of the LSA. This fix resolves the problem for 10.2 and later releases. [CSCdi48102]

• OSPF put incorrect information in the source field for stub route. It prevents BGP to adverstise this stub route to peer as the route will not be synchronized. This fix put the advertising router in the source field for stub route and avoid the problem. [CSCdi49377]

• The router attempts to make a routing decision assuming the broadcast packet is a directed broadcast. After the routing decision is made, it discovers that it isn't a directed broadcast and then attempts to forward the packet to the helper address(es). Unfortunately, it remembers the interface from the previous routing decision and uses that instaed of the correct path to the helper address.

The workaround for this bug is to use 255.255.255.255 as the broadcast address. [CSCdi50629]

• The error message DUAL-3-SIA may occasionally appear when route flapping occurs in a meshed EIGRP topology. The EIGRP neighgour sourcing the flapped route is reset and routing resumes. [CSCdi54781]

• Policy route matches via BRI, are load balanced with serial interface. [CSCdi57188]

• After a reload EIGRP does not redistribute static routes which are not directly connected. i.e. static routes pointing to a destination beyond another EIGRP router. The workaround is to reconfigure such static routes. [CSCdi57743]

• The system may fail when a no router eigrp as-number command is issued and there are summary routes present. A workaround is to turn off auto-summary and deconfigure all manual summaries before deconfiguring Enhanced IGRP. [CSCdi57814]

• This bug is introduced in 10.3(10.1), 11.0(7.1) and 11.1(2.0.2). The router could crash when ip address change or upon unconfiguring OSPF following the ip address change. [CSCdi58029]

• Attempting to copy an empty startup-configuration to the network will cause the router to reload. [CSCdi58040]

ISO CLNS

• There is no method for altering the transmission rate of IS-IS link state packets in cases where the rate would add undue load to the receiving system. There is no workaround for this problem. [CSCdi54576]

• When the extended option of CLNS ping is used, one of the options that can be specified is the source NSAP that is to be used in the ping packet.

The ping command does not accept any NSAP (for the source NSAP) other than the default value (i.e. the sender's own NSAP). [CSCdi54904]

• The CLNS cache gets invalidated too frequently, and in an environment with heavy traffic, can cause the CPU to spend too much time just purging and re-populating the cache.

The fix is to delay the cache invalidation, and have an appropriate knob to control the frequency of invalidation. [CSCdi56559]

• If IS-IS is running, and a CLNS static route is configured that points to a point-to-point interface on which IS-IS is not configured, and the static route is removed, the system may crash.

A workaround is to either disable IS-IS before removing the static route, or to enable IS-IS on the interface before removing the static route. [CSCdi56815]

• Under situations of extreme load, ISIS and NLSP may cause packets to be dropped unnecessarily. There is no workaround to this problem. [CSCdi58433]

• If a non-cisco router running IS-IS on a level-1-only circuit is also sending ES-IS End System Hello (ESH) messages, it is possible for the cisco router to not recognize the other router for IS-IS.

A workaround is to filter out the ESH packets using the "clns adjacency-filter es" configuration command in conjunction with an appropriate filter set (which should specify a wildcard, "**", in the last byte of the address). [CSCdi58621]

Novell IPX, XNS, and Apollo Domain

• An IPX ping sent from a router to it's own ethernet IPX address does not report successful echo on the low end routers. [CSCdi35609]

• 'show access-list xxx' may cause the router to reload while another telnet session is removing the same access list. [CSCdi51235]

• If the NLSP database is cleared using "clear ipx nlsp *", any static routes or services installed in that router will no longer be advertised via NLSP.

The workaround is to add or delete another static route or service, or restart the NLSP process by deconfiguring and then reconfiguring it. [CSCdi52574]

• Doing a "no ipx router eigrp xx" may cause the router to access illegal memory. On the 4500 and rsp, this causes an error message to be displayed. [CSCdi55250]

• If SAP entries remain to be transmitted when the last IPX-EIGRP or RSUP neighbor on an interface goes down, those SAP entries will remain enqueued, and will be transmitted when a new neighbor is detected.

There is no workaround to this problem. [CSCdi55252]

• The default for ipx eigrp-sap-split-horizon needs to be changed to off. [CSCdi55576]

• Adding the command distribute-list access-list out rip to an active IPX ROUTER NLSP process causes the router to display the following error message, after which the router reloads:

Local Timeout (control reg=0x118) Error, address: 0x4000C74 at 0x30F4D7C (PC)

The existence or absence of the access-list in the configuration does not effect the behavior of the router. [CSCdi55681]

• If there are more than 42 neighbors on a single LAN interface, ISIS and NLSP will be unable to establish neighbor adjacencies. The workaround is to limit the number of neighbors to 42 or less. [CSCdi56547]

• IPX SAP table may not accurately reflect SAP entries learned locally if IPX EIGRP and IPX RIP/SAP is configured at the same time. Some of the SAP entries may show up on the SAP table as EIGRP derived rather than RIP/SAP derived even when the local LAN where the problem SAP sourced, is not running EIGRP. [CSCdi56588]

• The router may reload when turning off and on immediately on an interface that is running IPX. [CSCdi57683]

• The router may reload when running IPX EIGRP due to illegal access to memory. [CSCdi57728]

• Under osbscure circumstances, some ISIS and NLSP link-state packets (LSPs) may not be transmitted on some point-to-point interfaces. There is no workaround to this problem. [CSCdi58613]

Protocol Translation

• Deleting a translate statement using an X.25 permanent virtual circuit as the inbound connection will cause an unscheduled restart. [CSCdi49877]

• If you perform large file transfers on VTY-asynchronous interfaces that cross an X.25 network that has a large round-trip time (RTT), a TCP implementation with a large send window can cause return traffic on the VTY-asynchronous interface to be delayed. [CSCdi54905]

VINES

• Segments running FDDI/Ethernet may experience disconnects when using certain NICs. The router is dropping packets that are being padded due to the packet length being less than 64 bytes. The fix is to check only if the data packet is greater than the actual buffer size allocated. [CSCdi55508]

• VINES Sequenced RTP (SRTP) broadcasts an RTP update with metric 0xFFFF when a existing route ages out. This is an implicit RTP request. Upon receipt of a route with metric 0xFFFF, all routers, if they know better routes, immediately generate an RTP update to the originator. However, the originator ignores these RTP updates from neighbor routers if the sequence number is older than that of the route just aged out, thus losing the route. This caveat was introduced in 10.2(11.4), 10.3(9.2), 11.0(5.2) and 11.1(1.4). The correct router behavior is to accept any route information when the route is in garbage collection state. [CSCdi58038]

Wide-Area Networking

• The calling party number field of a setup message is sometimes incorrect when using Classic IP over ATM. [CSCdi41888]

• When an ATM interface that has associated ARP cache entries resets, SYS-3-INVMEMINT error messages and Traceback messages may be observed. [CSCdi43183]

• If the cell burst size is a multiple of 64 the AIP may reset with the error: CBUS-3-OUTHUNG: ATM3/0: tx0 output hung (800E = queue full) This incurs a short temporary interruption of the ATM traffic.

The correction of this fix also enforces the parser to restrict the range allowed for the burst size parameter of the atm pvc command to the legal values [1-63]. [CSCdi45984]

• When using a MIP for ISDN in a 7507/7513, the MIP(s) must be installed in the first 5 slots of the chassis or a "Software Error: Illegal Interface # or dsl: xx" will be displayed and the MIP will not be usable. [CSCdi46413]

• When using TCP header compression with frame relay or X.25, if the router is telnetted to over the frame relay or X.25 link, the router may restart. [CSCdi47640]

• PPP Authentication Changes

Several requests have come in for modifications to the PPP Authentication feature. At the same time, a fundamental security hole (remote PAP gives away the router's hostname and matching password) was identified. Here are the changes made. Note that three DDTS were opened (CSCdi49278, CSCdi54088 and CSCdi44884). These changes were integrated into 11.0(8.1), 11.1(3.0.2) and 11.2(0.7).

For the purposes of this document, 'remote authentication' will mean authentication BY the remote PPP unit of the local router. Similarly, 'local authentication' is the authentication OF the remote PPP unit by the local router. The unit doing the authentication (the authenticator) is the unit checking the other ends password. Another way of looking at it is that the terms, 'local' and 'remote', refer to the location of the applicable 'ppp authentication {chap|pap}' configuration command. The terms 'local authentication' and 'remote authentication' are confusing but slightly better than 'inbound authentication' and 'outbound authentication'.

Goals: -disable remote PAP authentication unless explicitly configured -allow multiple servers to appear as a single server to ease configs -allow remote peer to authenticate to multiple unknown servers

New PPP Authentication Commands

ppp pap sent-username xxxx password yyyy ppp chap hostname xxxx ppp chap password [n] zzzz

All commands are interface configuration commands. Since they are PPP commands they are entered in the dialer group or async group or BRI/PRI interface as applicable.

ppp pap sent-username xxxx password yyyy

Remote PAP has been disabled by default. This command will re- enable remote PAP support for the specific interface and use the 'sent-username' and 'password' in the PAP Authentication Request packet to the peer. Remote PAP is when the peer requests that you authenticate or prove yourself to him. This change was done because a security hole exists in the present code. Prior to this change, we would send out our hostname and password in the PAP Authentication Request packet. The same password that the peer is supposed to know in order to do local CHAP authentication.

ppp chap hostname xxxx

This command is added to allow ISPs to create a pool of dial-up routers all appearing to be the same host when authenticating with CHAP. Currently, the ISP's customers need to have username entries for any possible router they might attach to. This will allow them to have a single entry as all ISP routers will challenge with a common hostname. This command is normally used with local CHAP authentication (when we are authenticating the peer) but it can also be used for remote authentication.

ppp chap password [n] zzzz

This command is added to allow a router dialing to a collection of routers not supporting the 'ppp chap hostname xxxx' command (such as units running older IOS images) to configure a common password (ie CHAP secret) to use in responding to challenges from an unknown peer. Thus a customer can replace several username/password config commands with a single copy of this command (per interface or dialer/async group interface). Note that this command is only used for remote CHAP authentication, ie. when we are authenticating for the peer. It does not affect local CHAP authentication.

Example configurations (most non-authentication details left out)

Remote router dialing multiple servers in a single rotary (w/out dialin)

hostname customer451 ! interface bri0 encap ppp ppp chap password 7 jfdjla

Central site router (one of many in a single rotary)

hostname 3rdfromtop ! username customer451 password 7 jfdjla (probably uses TACACS+ instead) ! interface dialer0 encap ppp ppp authentication chap callin ppp chap hostname ISPCorp

Central site router (as above but requiring support for older PAP clients)

hostname 3rdfromtop ! username customer451 password 7 jfdjla (probably uses TACACS+ instead) ! interface dialer0 encap ppp ppp authentication chap pap callin ppp chap hostname ISPCorp ppp pap sent-username ISPCorp password 7 fjhfeu [CSCdi49278]

• Frame Relay switching across an IP tunnel does not work if one of the Frame Relay serial interfaces is configured to be frame-relay intf-type dte.

In addition, when the serial line is configured to be frame-relay intf-type dce or frame-relay intf-type nni, if a frame-relay intf-type command is entered after the desired PVCs have been configured, then the router will fail to send the correct LMI Full Status message. [CSCdi52339]

• Unable to remove "frame-relay de-group" command from interface. [CSCdi54672]

• The interface statistic 'Last input' is not set for fast-switched IP packets on an async interface. The statistic will be set by any other traffic including link protocol keepalives. [CSCdi54972]

• The number of unicast frames forwarded by the LANE BUS is missing from the "show lane bus" output. [CSCdi55100]

• When using isdn leased lines, if the BRI is administratively shutdown, and the isdn leased-line command is issued for that BRI, it is taken out of shutdown. [CSCdi55144]

• A heavily loaded X.25 link that is experiencing congestion can, under rare conditions, enter a state where it oscilates between sending a RNR and a REJ. [CSCdi55677]

• With ILMI-resolution of the switch portion of ATM NSAP addresses, an attempt to place a multipoint call to a destination can occur (and with PIM, always will occur) before the switch part of the address is discovered. This leaves the router in a state where it will never place calls to that static map again. To work around, do not use ILMI negotiation. [CSCdi55904]

• uni 3.0 sscop will not return BeginAck PDU back if the Begin PDU is from uni 3.1 version. [CSCdi57785]

• Routers using basic-net3 switchtype may Release a call when an incoming INFORMATION message is received. [CSCdi58183]

• The system may unexpectedly restart or print error messages of the form %SCHED-3-PAGEZERO: Low memory modified by Exec, when a pad connection is made specifying an X.29 profile on the command line. A workaround is to turn on debug pad. [CSCdi58587]

• OSPF routing doesn't work over LANE subinterfaces unless "ip ospf network broadcast" is explicitly configured on the subinterface. [CSCdi58610]

• QSAAL and ILMI PVC's may only be created on the major interface, not the subinterface.

This is a change from SW Ver. 10.3.

The reason for this is because it was possible to configure multiple QSAAL and ILMI PVC's on multiple subinterfaces which lead to problems. This should not have been allowed. [CSCdi58635]

11.0(7) Caveats/11.0(8) Modifications

This section describes possibly unexpected behavior by Release 11.0(7). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(7). For additional caveats applicable to Release 11.0(7), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(8).

AppleTalk

• Multiple Cayman tunnels does not work because routes do not arrive correctly from remote side of tunnels. To workaround, use only one Cayman tunnel. [CSCdi50981]

• Adding the command appletalk virtual-net network-number zone-name to the configuration of a Cisco 4000 router running Release 11.0(5) can cause the router to reload. [CSCdi51787]

Basic System Services

• There is no way to configure an async line so that software flowcontrol may NOT be turned off by the remote tcp host.

Line command flowcontrol software lock may now be used to specify a flow control configuration that will not change when connected to remote network hosts, using telnet or rlogin protocols. [CSCdi33144]

• Netbooting an image from a tftp server that is not on a directly connected network may sometimes fail. [CSCdi43020]

• No AAA accounting records are generated for one-step protocol translation sessions, no matter what types of accounting are configured. [CSCdi44863]

• A transmit buffer mismanagement problem on the EIP on an RSP-based router can cause the message RSP-3-XBUFHDR to be generated. [CSCdi46905]

• MBRI and PRI hunt groups do not propagate queue management algorithms from the D channel to the B channels. [CSCdi47191]

• An AAA accounting record does not contain the IP address of the user if the session starts via autoselect. [CSCdi49184]

• On RSP platforms, the following message might display:

%DBUS-3-DBUSINTERR: Slot 0, Internal Error

It may also be accompanied by the following messages:

"%CBUS-3-CMDTIMEOUT: Cmd time out, CCB 0 x XXXXXXXX slot n, cmd code n"

"%DBUS-3-WCSLDERR: Slot n, error loading WCS, status 0 x XX cmd/data 0 x XX pos n"

If the WCSLDERR error displays, the RSP board is disabled and will not be displayed when you issue a write terminal command. Issue a microcode reload command to take the card out of the disabled state. [CSCdi49854]

• When trying to set the MTU on an interface in an RSP chassis (Cisco 7500 series or RSP7000) larger than 8192, the MTU change will fail and report the error message "can't carve anything." [CSCdi50133]

• Under certain circumstances, the "IP SNMP" process can consume almost all of the CPU resources, starving other processes and causing erratic behavior in the device. The most obvious symptom is the loss of TCP connections to the device. The most likely cause of the problem is a flurry of SNMP requests being sent to the device in a short period of time, retrieving large amounts of data. This behavior is usually associated with network auto-discovery mechanisms which retrieve the device's entire ARP cache and IP routing table on a periodic basis. The problem is exacerbated by the fact that some network management applications, by default, perform auto-discovery as often as every five minutes.

A partial work-around is to identify those devices which are performing auto-discovery, and modify their default behavior so that they perform auto-discover on a less frequent basis, if at all.

The permanent solution is to lower the priority of the "IP SNMP" process so that it doesn't starve other processes in the system. [CSCdi50399]

• A router containing a CIP card does not become fully operational when Cisco IOS software is loaded. [CSCdi51441]

• no linkDown trap generated in IOS 11.0(5). [CSCdi51575]

• locIfReason shows 'administratively down' for linkUp trap instead of 'up' [CSCdi51613]

• Transparent bridging with Cisco 7500 series routers may fail if frame crosses HDLC link. [CSCdi52360]

• Memory allocated at system initialization time is displayed as belonging to the "*Dead*" process when a show process memory command is issued. This memory should be displayed as belonging to "*Init*" instead. There is no workaround. [CSCdi53190]

• The cisco implementation of the SNMPv2 Simplified Security Conventions was based on the following IETF Internet Drafts: draft-waldbusser-conventions-00.txt, draft-waldbusser-ssecimpl-00.txt, and draft-waldbusser-ssecov-00.txt. These were later obsoleted by the following documents: draft-waldbusser-conventions-01.txt, draft-waldbusser-ssecimpl-01.txt, and draft-waldbusser-ssecov-01.txt.

Since the differences between the -00 and -01 versions were never incorporated, and since the -01 documents have been expired by the IETF, and since the SNMPv2 party-based model (RFCs 1445-1447) that these documents rely upon has been relegated to historic status by the IETF, support for the Simplified Security Conventions will be removed from all software images.

This is the first step in replacing all support for party-based SNMP with support for SNMPv2C as outlined in RFCs 1901-1908, as well as supporting any new secure SNMP standard produced by the IETF. [CSCdi53343]

EXEC and Configuration Parser

• Allow non-printable data to be encoded into string with the use of Quoted string and the "" prefix.

For example to set an IPX static NDS service name which contains encoded data. This presently display as:

P 26B CISCO2_______________ 307C3EC4.0000.0000.0001:0005 2/01 1 Et0 Full name: 'CISCO2__________________________^Ust^FL@@@@@D^EPJ'

The binary will now display as xXX where XX is the Hexidecimal value of that character in that quoted sting.

ipx sap 26b "CISCO2____ xXXst xXXL@@@@@D5 2

where XX are the hex values for ^U, ^F, and ^E

to enter the character "" will require using two ""s, e.g. "\" . [CSCdi53685]

IBM Connectivity

• A router running RFC 1490 support over Frame Relay does not properly swap the direction bit in the RIF frame. [CSCdi36042]

• Command syntax: netbios input-access-filter session-bytes name netbios output-access-filter session-bytes name

Example:

!to filter SMB 73 packet netbios access-list byte SMB deny 18 73

int tok 0 source-bridge 100 1 200 source-bridge spanning netbios input-access-filter session-bytes SMB

int tok 0 source-bridge 200 1 100 source-bridge spanning netbios output-access-filter session-bytes SMB [CSCdi40165]

• Input bridge access-lists applied to the virtual bridge interface in DLSw+ will cause SYS-2-SHARED error messages and Tracebacks. There is also a minor memory leak as the result of this bug. [CSCdi44347]

• When two or more routers are connected to the same Token Rings, and each uses source-route bridging (SRB), a station on one of the rings might choose a non-optimal route with a path through both routers. In typical (large) networks, this behavior might result in explorer storms as well as suboptimal routes. [CSCdi45116]

• When the dlsw icanreach mac-exclusive and dlsw icanreach mac-address mac-addr commands are issued to specify a single MAC address to be filtered, all traffic is filtered instead. [CSCdi45773]

• When an IP peering protocol is in use in the router (for example, RSRB, STUN, or BSTUN) CLS DLUS (such as APPN and DSPU) may have difficulty establishing LLC2 sessions over RSRB virtual interfaces when the LLC2 path is bridged SRB only (that is, it does not traverse an IP cloud local to this router). [CSCdi47301]

• An incorrect timer reference causes explorer frames to be flushed on interfaces, even when the maximum data rate for explorers on the interface is not exceeded. [CSCdi47456]

• When a router running DSPU over Frame Relay in communication with a frame device breaks the session, it does not try to reconnect after DM is received. [CSCdi49044]

• DLSW+ on C4700 crashes on 'show dlsw reachability' when there are a large no. of local 'icanreach' nodes. [CSCdi50102]

• Low-end platforms cache invalid RIF entries when using any form of the multiring command. This problem can also be seen in the DLSw reachability cache and with possible loops with LNM. [CSCdi50344]

• netbios dlsw should not send a test_cmd after a name recognized is received. [CSCdi50382]

• RSRB does not declare the peer dead until the keepalive times out. In order for RSRB to detect the dead peer so that the ring list can be cleaned up properly, set the keepalive value as small as possible. [CSCdi50513]

• Peer on Demand peers (peers that learn of each other through Border Peers) do not connect. The options inactivity timeout and lf lfsize should be added to the dlsw peer-on-demand-defaults command. [CSCdi50574]

• During normal operation of the APPN feature, it is possible for the following message to be displayed:

%APPN-7-APPNETERROR: Inconsistent TG information TG=21 ADJ_NODE=AWWUKIBdWdr

The ADJ_NODE name is displayed using the incorrect format.

The "Inconsistent TG info" message is displayed when the NN receives a TDU with the same sequence number that has different information. VTAM sent a tdu for a NN with a different netid. If the link to that NN was stopped and restarted, VTAM sometimes sent a TDU with the same sequence number but different information. This problem was reported to IBM. [CSCdi50674]

• This ddts adds lf options to the dlsw peer-on-demand-defaults command. This change is required to properly complete existing features.

dlsw peer-on-demand-defaults lf lf_size

lf_size is the largest frame size that circuits over this peer will negotiate down to. DEfault is 17800. Valid values are: 11407 11407 byte maximum frame size 11454 11454 byte maximum frame size 1470 1470 byte maximum frame size 1500 1500 byte maximum frame size 17800 17800 byte maximum frame size 2052 2052 byte maximum frame size 4472 4472 byte maximum frame size 516 516 byte maximum frame size 8144 8144 byte maximum frame size [CSCdi50687]

• Data Link Switching (DLSw+) will attempt to update its reachability cache based on explorers received on interfaces that have SRB configured, but are not bridged to a ring-group (port-to-port SRB). This causes some unnecessary explorer overhead in these environments. [CSCdi50717]

• This ddts allows cisco to interoperate with other vendors' DLSw 1795 compatible implementations in the area of capability exchange. cisco DLSw was not sending or receiving the Vendor Context control vector that must preceed any vendor specific control vectors. For more detail regarding the DLSw capabilities exchange, please refer to RFC1795.

This ddts also fixes a "bad p_enqueue NULL" traceback in cls_entitymanager.c that is preceeded by a CLS_ASSERT traceback with text "connInd != NULL". [CSCdi50868]

• When using the DSPU feature to map upstream LUs to downstream LUs, the downstream LU may not recover properly after the upstream LU is deactivated and reactivated.

Work-around to avoid this problem is to ensure that deactivation of the upstream LU is complete (i.e. DSPU has deactivated the downstream LU) before reactivating the upstream LU.

Work-around to recover a lost LU is to deactivate/reactivate the downstream PU. [CSCdi51042]

• Removing a DLSw configuration by configuring no dlsw local-peer and adding the DLSw configuration back can cause a memory leak in the middle buffer. [CSCdi51479]

• Applying a source-bridge output-lsap-list to a Token Ring interface when source-bridge explorer-fastswitch is enabled may cause packets permitted by the output-lsap-list to be dropped. The workaround is no source-bridge explorer-fastswitch. [CSCdi51754]

• When a very large number of I-frames are sent by an end station to a DLSw router at the same instant, the following message may appear on the console :

DLSW:CPUHOG in CLS background, PC=0x60549f3c

Since the CPU is being occupied by the CLS background process for a period of time, protocols that involve polling may lose their connections because of to poll starvation. [CSCdi52382]

• When running DLSw+ over Ethernet, the router transmits corrupted frames on retransmission. The restransmission occurs on receipt of a REJ frame from the end station or if an acknowledgement of the frame is not received within the LLC2 t1 timeout. [CSCdi52934]

• A list number greater than 255 on the dlsw remote-peer 0 tcp 172.22.12.128 lsap-output-list list_num command will not be parsed properly. [CSCdi52957]

• A configured explorer maxrate value is lost when the rsp reloads. It is replaced by the default maxrate value.

There is no workaround and the impact can be substantial for large networks, resulting in increased delays for srb connections. [CSCdi53357]

• When the router is configured to use the DSPU feature, it may crash during deactivation of multiple downstream physical units (PUs). [CSCdi54114]

• A minor formatting error may occur on the display of an appn port where the port name is 8 characters. [CSCdi54262]

• A router may crash when DSPU debugging is enabled on a Cisco 4500 or Cisco 7500 router. [CSCdi54277]

• If sdlc xid address ... command is not configured for an SDLC address, the xid-n2 option will show up on the sdlc address ... definition. [CSCdi54389]

• The connection network name is displayed incorrectly for the "Define cn" and the "Delete cn" error messages. [CSCdi54598]

• APPN/DLUR may not allow devices to connect into the router at a high enough rate if many devices are attempting to connect at the same time. [CSCdi65405]

Interfaces and Bridging

• When a Cisco 7000 router Ethernet interface is the root of a spanning tree and UDP flooding is configured with turbo flooding, packet loops occur. The workaround is to disable turbo flooding. [CSCdi45659]

• The concurrent routing and bridging (CRB) feature does not bridge IP traffic if the destination IP address is internal to the router. Also, IP packets with a destination IP address internal to the router are not responded to. [CSCdi48117]

• After an OIR of the MIP in a Cisco 7000, the first interface configured on each MIP controller remains shutdown after reinstallation. [CSCdi48767]

• If an interface processor does not respond to a DBUS access, the router will crash. The interface processor may not respond to a DBUS access if it has crashed. If the interface processor has been removed, it cannot respond to the access. The show controller cbus command on a Cisco 7000 router does not protect itself against trying to run during an OIR event, which lets it try to access a removed card over the DBUS, causing a crash. [CSCdi50481]

• This bug fixes transparently bridged arp replies that were handled slightly differently through code path in 11.0 and 11.1. Workaround is static arp entries. [CSCdi50570]

• Transparent bridge ports in the blocking state do not respond to ARP broadcasts. This problem will be acute only when there is no other IP route to the blocking port. A workaround is available in the form of a static ARP entry in the host. [CSCdi51444]

• When shutting or unshutting an interface, the driver could create a zero-length received packet. If compression was enabled on the interface, the packet length passed to the decompression engine would appear to be a very large number. The decompression engine would then proceed to overwrite memory and crash the router.

This fix prevents zero- or outlandishly-sized packets from reaching the decompression engine. [CSCdi51869]

• 3102 with IOS(tm) igs-j-l.110-5 loaded in flash would continually restart after receiving the following message on the console:

%SCHED-2-WATCH: Attempt to set uninitialized watched boolean (address 0). -Process= "*Sched*", ipl= 7 -Traceback= F82C6 11FAEA Exception: Level 3 at 0xA49F4 (PC)

Workaround: Removing the serial cable from the router allowed the machine to boot correctly. At that point, the cables could be re-attached and the machine would function normally. [CSCdi51928]

• On a Cisco 7000 series router, the show diag command incorrectly reports the Route Processor as an EIP controller. On a Cisco 7500 series router, the show diag command incorrectly reports the Route/Switch Processor and the Chassis Interface as an EIP controller. This problem has no functional impact on the router. [CSCdi52129]

• A bug exists in the MEMD carve code on the Cisco 7000 that can cause bandwidth considerations to be ignored. This might result in nonoptimal MEMD carving. [CSCdi52227]

• In a 4700 with two fddi interfaces configured for bridging, when one of the interfaces moves from a blocking state to a forwarding state that interface may fail to pass unicast traffic. This condition can be cleared by entering a clear interface fddi x, where x is the interface that moved from blocking to forwarding. [CSCdi52756]

• A router may pause indefinitely when the configuration command encapsulation ppp is entered for Async-Group Interfaces. The configuration command async mode dedicated has the same effect. [CSCdi53185]

• A Cisco 7500 router running 11.0(6) will attempt to bridge routing update broadcasts if transparent bridging is turned on and the originator of the broadcast is also routing DECnet and therefore has a DECnet MAC address. [CSCdi53321]

• The IP pooling information for the member interfaces of a dialer rotary group is configured in the dialer interface. If SLIP is started on an async interface that is part of a dialer rotary-group, the dialer interface's "peer default ip address" command will be ignored. This defect was added in 11.0(3) and will be fixed in a future release. [CSCdi53389]

• It is possible to configure to configure a specific peer address on a group-async interface with the command "peer default ip address a.b.c.d". Since the group-async interface configuration is mapped to all of its member interfaces, this will result in multiple interfaces using the same peer address. This defect will be removed in a future release by preventing the configuring of a specific peer address. [CSCdi53596]

• Asynchronous TTY lines on Cisco 2509 through Cisco 2512 devices sometimes stop answering new modem calls. The show line x command output shows the line with modem state in Idle and Hanging-up. A workaround is to configure session-timeout 0 for asynchronous lines. [CSCdi54196]

IP Routing Protocols

• Running multiple Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) autonomous systems might consume all available memory in the router. [CSCdi36031]

• Multicast fast switching is not functional for ATM subinterfaces. A workaround is to configure no ip mroute-cache on the incoming subinterface. [CSCdi51178]

• Unconfiguring OSPF can cause the router to reload. [CSCdi51283]

• BGP: backdoor does not work as expected and bgp routes are preferred over IGP routes for same network.

This bug could also cause the router crash when network command is deleted. network command with route-map option should be used to cause the crash. [CSCdi51820]

• If two IP-Enhanced IGRP autonomous systems are configured, and an interface address is changed so that the interface moves from one autonomous system to the other, Enhanced IGRP will fail to operate on that interface. The workaround is to delete the IP address (using the no ip address command) before configuring the new address. [CSCdi52078]

• BOOTP broadcasts which are forwarded from unnumbered interfaces using ip helpering do not properly populate the BOOTP giaddr field. [CSCdi52246]

• The set metric subcommand of the route-map command causes an incorrect value to be advertised for the bandwidth metric for IGRP and Enhanced IGRP. The units of the default-metric subcommand to the router eigrp are improper. An improper value is advertised for the delay metric in Enhanced IGRP if it is set using the metric option of the redistribute subcommand to the router eigrp command. There are no workarounds for these problems. [CSCdi52277]

• Under certain conditions, Enhanced IGRP may stop transmitting packets. This may manifest itself as large numbers of routes repeatedly Stuck-In-Active. The workaround is to deconfigure and restart Enhanced IGRP, or reload the system. [CSCdi53466]

• Regular expressions longer than 59 characters in the ip as-path access-list configuration command will cause the router to reload. [CSCdi53503]

• Enhanced IGRP will stop working on an interface if the interface goes down for some reason and then comes back up. There is no workaround to this problem. [CSCdi53903]

• Due to an uninitialized variable, multipoint GRE tunnels in Releases 10.3 and 11.0 may allow non-IP network protocols to be forwarded to all endpoints of the tunnel. This can give the perception that non-IP protocols are capable of being routed over the multipoint tunnel in these versions. Only IP multipoint tunnels are supported in these versions. In Release 11.1, routing IPX over GRE multipoint tunnels will fail. [CSCdi54192]

ISO CLNS

• When using RFC1490 encapsulation for OSI protocols, the system inserts an extra byte into the header. When communication is between two Cisco devices, Cisco encapsulation can be used to work around this problem. [CSCdi40775]

• If two routers running Intermediate System-to-Intermediate System protocol (IS-IS) are connected via multiple point-to-point links and one of the links fails in only one direction, it is possible for traffic to be sent down the failing link and subsequently lost. This is because of a deficiency in the IS-IS protocol specification. There is no workaround to this problem. [CSCdi48351]

• ISO-IGRP fails to install parallel routes into the CLNS prefix table under certain conditions. [CSCdi50714]

• Issuing a CLNS ping to one of the router's own address will cause the router to reload if debug clns packet is on. The workaround is to not have this particular debug on if you need to ping to one of the router's own addresses. [CSCdi50789]

• CLNS packets whose NSAP's have a non-zero N-selector byte are not fast-switched.

The result of this situation is a high CPU utilization, and is more pronounced in an environment where there is heavy CLNS traffic (e.g. large file transfers), [CSCdi52752]

• Routes that are redistributed into ISO-IGRP from another protocol (e.g. ISIS), or from another ISO-IGRP domain, are stored as prefix routes.

When the redistribution is disabled, ISO-IGRP should poison all prefix routes that were being learnt from the protocol that was being redistributed.

ISO-IGRP currently does not do this, and as a result, can cause the routes to count to infinity. [CSCdi53023]

Novell IPX, XNS, and Apollo Domain

• On a Cisco 4000 running Enhanced IGRP for IPX, the router may generate CPU-HOG messages for the IPX SAP process. [CSCdi39057]

• The IPX fastswitch cache (IPX route cache) can grow large over time if many end hosts are active and the network and configuration are stable. This is because cache entries are not normally invalidated as long as the destination network is reachable. On routers which are already low on memory, this can create various problems. A workaround is to issue the "clear ipx cache" exec command periodically. [CSCdi46978]

• IPXWAN calculates the wrong NLSP metric for the serial interface. Therefore, NLSP may use the serial interface as the next hop router instead of the LAN interface. [CSCdi48717]

• When an interfaces goes down SAP poisons for Services learned over that interface are sent twice out all other interfaces. [CSCdi50745]

• The ipx interface values of rip and sap triggered delays will get change after a system relaod if you have a global ipx default output rip/sap delay configured. [CSCdi51038]

• On RSP systems using MIP with either HDLC or PPP encapsulation can produce alignment warning message. [CSCdi51183]

• When an interface starts up IPX RIP/SAP networking extra General RIP request, General SAP request, and flash updates are sent. In addition on IPXWAN interfaces configure and negotiated for NLSP the RIP/SAP General Queries are sent which may trigger NLSP "auto" mode in our WAN neighor to switch to sending RIP/SAP packets, which in turn causes us to send RIP/SAP packets resulting in routes being learned via RIP on an NLSP interface. [CSCdi52030]

• Configure ipx update-time on the router without any ipx network number may generate traceback error messages. [CSCdi52234]

• Under conditions where many routes are changing, IPX-EIGRP can block the transmission of service information for long periods of time, resulting in excessive memory utilization. There is no workaround to this problem. [CSCdi52398]

• When using IPX static routes and services over WANs clients may receive "Error receiving from device NETWORK" messages and abort the connection process, most commonly during the attempt to download and run LOGIN.EXE. A workaround is to increase the ipx delay of the Client and Server LAN interfaces on each side of the WAN, this has the effect of increasing the metric associated with the static route and therefor increasing the timeout values used for the connection. Static routes should have a configurable routing metric. [CSCdi52606]

• IPX-EIGRP SAP packets may not be processed for all neighbors. There is no workaround to this problem. [CSCdi52997]

• Clearing the SPX spoofing table with either the clear ipx spx-spoof command or by removing the ipx spx-spoof command from the last interface left spoofing may cause a system reload. [CSCdi53070]

• RIP format error counter is displayed twice on the show ipx traffice screen. [CSCdi53167]

• The message "before is_idb" will be seen when configuring an IPX static route, it was a debugging statement accidently left in the software, it may be ignored. [CSCdi54677]

• ipx eigrp-sap-split-horizon is off by default. It should be on by default according to our documentation. [CSCdi54690]

Protocol Translation

• A traceback message, "SYS-2-NOTQ: unqueue didn't find xxx in queue yyy" is printed when closing connections to an X.25 translation using the printer option. [CSCdi38602]

• An access-class applied to a virtual terminal takes precedence over an access-class specified in a translate command. [CSCdi46038]

• A translate statement specifying ppp authentication erroneously uses an access class. The workaround is to specify an access list matching the access class, permitting all connections. [CSCdi51039]

• Release-note:

Only 5 translate statements using X.25 permanent virtual circuits can be read from non-volatile memory upon boot up. If more are required, a work around is to configure them after booting from a terminal or using TFTP. [CSCdi52043]

TCP/IP Host-Mode Services

• Forwarding of UDP broadcasts to IP multicast addresses using ip helper-address is not functional. [CSCdi49709]

TN3270

• When TN3270 goes into insert mode, it will not send feedback to the terminal. It should send the contents of vs or ve in the ttycap, like an IBM 7171 would. [CSCdi12246]

• Async lines connected via TN3270 to remote hosts, receive TN3270 Cursor-move escape strings for each data byte. [CSCdi48513]

• TN3270 should support type-ahead, accepting input while in system locked state. TN3270 should also support distinct cursor in insert-mode. TN3270 should also optimize on screen drawing for null areas. [CSCdi51821]

VINES

• VINES SRTP on serverless segements running Release 10.3(8) do not send the redirect to the correct network number (layer 3) address. The workaround is to turn off VINES redirects on the serverless segment interface. A sniffer trace of this packet will show an "abnormal end of Vines SRTP." [CSCdi50536]

• Receiving errors when enabling vines routing or applying vines metric to an ATM interface.

Mar 12 083512 143.182.21.2 117 %SYS-3-MGDTIMER Uninitialized timer, timer stop, timer = 60B117F8 Mar 12 083512 143.182.21.2 118 -Process= "VINES Protocols", ipl= 0, pid= 44 Mar 12 083512 143.182.21.2 119 -Traceback= 60112410 60113238 6034CBC0 6034D204 6034E114 6034E24C 6034E580 6033C990 6033CB10 600EC980 600EC96C [CSCdi51689]

• Vines recompute does the same calculations as enalbing VINES routing. It should do some different calculations to come up with a different network number. This gives the potential of routers with different mac addresses calculating the same network addresses. The work around is to manually enter a unique address on your network. [CSCdi51823]

Wide-Area Networking

• Removing a TRIP card and replacing it with a MIP card in the same slot of a 7000 will cause memory allocation errors. [CSCdi24243]

• VTY Async connections running PPP do not appear to close correctly if sent an LCP Terminate Request. The required Terminate ACK is not output. The peer should still drop the connection per RFC 1661, but the delay may be several seconds. [CSCdi42544]

• Under certain conditions, the router can reload with the message "System was restarted by error - Illegal Instruction, PC 0x300D646." This problem is related to ISDN. There is currently no workaround. [CSCdi45085]

• The no x25 address interface subcommand does not remove the X.121 address from an interface. The correct behavior is to remove the address, unless the interface is configured with the DDN or BFE option, in which case the correct behavior is to recalculate the default X.121 address from the IP address configured on the interface. [CSCdi45936]

• A Cisco 4000 series router with ISDN BRI interfaces can run out of timer blocks and crash. Use the show isdn memory command to see if memory is not being freed. [CSCdi47302]

• Systems using the ATM Interface Processor (AIP) card may restart with the error message "System was restarted by error - Illegal Instruction, PC 0x0." [CSCdi47523]

• When packets are lost because of hold queue overflow or line errors, multilink PPP may incorrectly discard packets that were properly received.

To prevent this behavior, remove the cause of the line errors or increase the hold-queue size. [CSCdi48424]

• The boot helper prints out a message indicating that the ILMI subsystem has been specified as a requirement for Signalling but has not been included in the boot helper image. This will lead to the signalling sub-system not being brought up. As a result it is not possible to netboot the system using Signalling/SVCs. [CSCdi48594]

• IPX packets transmitted over LANE, and then bridged onto a real ethernet, can have odd length. Some IPX clients and servers will drop ethernet packets whose length is not an even number of bytes.

There is no workaround. [CSCdi50313]

• If a backup interface is brought up, a floating static route will point through the backup interface to the remote node and network. When the original interface comes back up, the floating static route is removed. The backup interface will not see any traffic and an idle timeout will bring down the backup connection. If, however, the original interface comes back up before the backup connection is complete, the floating static route will have been removed and a neighbor route will be added to the peer address. This route will carry routing updates to the peer over the backup and thus reset the idle timeout with each packet. The backup interface will never disconnect. This behaviour was not present before Release 11.0(3). [CSCdi50489]

• A Cisco 7000 with two ATM interfaces running RFC 1577 ARP server will not register its own IP address. There are two workarounds:

-- Specify the full NSAP address of the ARP Server interface, using the atm nsap-address nsap-address command, instead of just the ESI portion. -- After boot-up, issue a no atm arp-server command and then reissue the atm arp-server command. [CSCdi50592]

• Fast switching IP traffic may fail from an ATM Interface Processor (AIP) onto an FDDI with RIF presence. [CSCdi50609]

• The dialer fails to bring up an additional BRI interface when both BRI B channels are active and the dialer load threshold load is exceeded. [CSCdi50619]

• Under some unknown circumstances, a Cisco 4000 series router with MBRI will stop transmitting on an ISDN interface. Only a reload of the router can correct this. [CSCdi50628]

• International calls being placed using the Australian Primary Rate switch type of primary-ts014 do not tag the format of the called address field correctly. This results in calls to locations outside of Australia being rejected as unassigned. [CSCdi50927]

• Cisco LANE clients will not interoperate with non-Cisco BUS's that deliver data to the client on multicast-send VCCs. Packets sent to the client on the multicast-send are discarded. In addition, the error message "%LINK-2-NOSOURCE: Source idb not set" may appear when these packets arrive. There is no workaround. [CSCdi50945]

• The ATM ARP Server will accept a badly formed ARP Response packet (one with no ATM NSAP address) and will mispopulate the ARP Server cache. This is not a problem with a correctly functioning ARP Client (such as Cisco's). [CSCdi50951]

• When an interface Group-Async is defined it may not be possible to change from an ip address pool to a peer default ip address for each member of the group. The commands will be accepted but will be lost by the running configuration. On a reload the following message may be seen: "Interface AsyncX is already a ppp-client." [CSCdi50974]

• When configuring atm rate-queue and mtu on the same time, the atm rate-queue configuration may not be processed properly, such AIP may not be able to process outgoing traffic correctly, and lead the error of %CBUS-3-OUTHUNG to occur, after the presence of traffic for a couple of minutes. However, The %CBUS-3-OUTHUNG will then result in an atm interface reset which will bring everything back to normal.

The problem will show up only when the two configuration commands are issued quick and close enough. So, the problem will most likely to occur when booting a router with such configurations. The problem will likely not to show up when these two configuration commands are issued sequentially from command line, as the two commands could not be entered so quick and so close to each other (to introduce the problem).

So, the output hang caused by this should recover without human interferring, although it may take a few minutes. On the other hand, 'shutdown' and 'no shutdown' on the atm interface with the configurations, as soon as the router is reloaded, should let everything work normally from the very beginning, without seeing the output hang. [CSCdi51013]

• Connecting a Cisco router (ARP client) to an IBM system with ATM (25 Mbits) works only when the router makes the call. The problem caused by the router's CONNECT packet, which does not include AAL5 IE. AAL5 IE is mandatory for IP according to RFC 1755. [CSCdi51037]

• This bug was introduced when atm fastbridging feature was introduced in 11.0. Since spanning tree configuration bpdus do not propogate further that peer bridges on the atm link, cisco to cisco atm spanning tree config bpdus allowed spanning tree convergence, thus no symptoms or problems in many topologies. But this bug resulted in non 1483 standard atm spanning tree bpdus that could result in non converging spanning trees over an 1483 compliant atm cloud with 1483 clients. The impact here is possible bridge loops with atm 1483 bridging applications. This fix stops potential loops by allowing the spanning tree to converge properly with all atm 1483 AAL5SNAP complient clients. [CSCdi51054]

• Asynchronous DLCI status changes from 0x02 (buffer-treshold-normal) to 0x03 (buffer-treshold-exceeded) will generate useless error messages: FR-5-DLCICHANGE: Interface Serial0 - DLCI YYY state changed to ACTIVE There is no impact on router functionality. [CSCdi51629]

• When bridging between a Cisco 7500 and an ISDN router running Cisco IOS software, data is not successfully passed if multilink PPP is used. [CSCdi51813]

• No action is taken when an X.29 Set or Set and Read message containing no parameters is received. The proper action is to reset X.3 parameters to their initial values, and, in the case of a Set and Read, to respond with an appropriate Parameter Indication message. [CSCdi52237]

• IP multicast packets do not fastswitch to LANE subinterfaces. [CSCdi52538]

• If a switched X.25 over TCP (XOT) permanent virtual circuit (PVC) receives a RESET REQUEST from the locally attached device within 2 seconds of an X.25 packet level RESTART REQUEST, the PVC will remain in an unusable state indefinitely. [CSCdi52548]

• The SHOW ATM ARP command's display output does not page to the screen, it scrolls continously until end of output is reached. [CSCdi52749]

• Changes to the primary-dms100 ISDN PRI switchtype code to make it conform with the NorTel PRI specification. Changes were not made in response to any field related problems. [CSCdi52751]

• Using multidrop lines on a 5ESS ISDN switch is not recommended. If used, they will have SPIDs. Currently, the SPIDs are send out BRI0 only, so on a router equipped with an MBRI, lines other than BRI0 will not be able to place calls. The workaround is to get point-to-point lines from the telco. [CSCdi53168]

• The state of a point-to-point subinterface may become out of sync with the state of the associated DLCI. This can occur if the subinterface is in the administrative down state prior to the DLCI being assigned to the subinterface.

For instance, assume DLCI 300 is marked DELETED and subinterface s0.300 is shut down. The commands

int s0.300 frame-relay interface-dlci 300 broadcast no shut

will result in s0.300 being shown as up while the associated DLCI is deleted.

Reversing the above commands will avoid this behavior. [CSCdi53328]

11.0(6) Caveats/11.0(7) Modifications

This section describes possibly unexpected behavior by Release 11.0(6). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(6). For additional caveats applicable to Release 11.0(6), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(7).

IBM Connectivity

• A "Mfree Error" traceback may occur when using APPN/DLUR and a link deactivation occurs over which a session is active. The error causes APPN to neglect to free the storage involved, but otherwise does not affect normal operation. [CSCdi52054]

11.0(5) Caveats/11.0(6) Modifications

This section describes possibly unexpected behavior by Release 11.0(5). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(5). For additional caveats applicable to Release 11.0(5), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(6).

AppleTalk

• ZIP Queries may unexpectedly not be sent to a neighbor if that neighbor has been up for more than approximately 3 weeks. The symptom can be seen by doing "show apple route" and "no zone set" are seen in the routing entries. [CSCdi42908]

• Due to the bug in the low end fastswitching code, the 802.3 header will contain a wrong length when small packets (less than 60 bytes) are fastswitched on the ethernet media. [CSCdi45581]

Basic System Services

• The show version output for a cisco 2500 or 3000 reports a processor memory size that is less than the actual size by 4096 bytes. The 4096 bytes are subtracted because they are used for a special purpose - as a console output logging buffer during Flash upgrades via the Flash Load Helper feature - and are unavailable for normal use as processor memory.

This size reduction is, however, a source of confusion since it is not accounted for in any of the show outputs. The show version output is therefore being changed so that it shows the true physical size of processor memory even though the 4096 byte chunk will continue to be used for the special purpose. This change is cosmetic and does not affect the operation of the system in any way. [CSCdi30593]

• Available memory will slowly decrease on a router that is bridging IP and that has more than one interface with the same IP address. [CSCdi44023]

• deleting a flash file mentioned in a "boot" config command can cause a reload [CSCdi44152]

• A Cisco 7500 that is fast switching SRB explorers, fast switching IP multicasts, or bridge-flooding packets might crash with a SEGV exception error message and a stack trace that ends in the rsp_fastsend().

A workaround is to disable fast switching of IP multicasting, or fast switching of source-route bridging (SRB) fast explorers by using the no source explorer-fastswitch command. Another possible workaround is to remove or add an IP card, particularly of a different media type. [CSCdi45887]

• Unconfiguring and then reconfiguring the timeslots on a MIP interface or a Cisco 4000 series E1/T1 interface may cause the router to hang. [CSCdi46506]

• Under unknown conditions, a non-fatal error may be displayed that an attempt was made to dismiss while 'blocking is disabled' or that an 'Invalid memory action' was attempted from interrupt level. [CSCdi47152]

• Under heavy load conditions it is possible for a Cisco 2509 through Cisco 2512 access server to pause indefinitely and report a bus error. [CSCdi47190]

• The keyword 'connection', if entered as part of a 'aaa authorization' command, was accepted, even though the keyword was not shown in the on-line help. The configuration command 'aaa authorization connection' is not currently supported. Support for this feature will be added in a future release of IOS.

The keyword 'connection', if entered as part of a 'aaa accounting' command, is not shown in the on-line help even though the command is accepted and supported. [CSCdi47394]

• If an NTP packet is sent to one of a system's secondary addresses, the system will reply with the primary address of the outgoing interface in the source address field.

There is no workaround to this problem. [CSCdi47415]

• hostname "" doesn't let router to use the default hostname of "Router". Some protocol usage in this configuration may cause router to hang. [CSCdi47506]

• When the router attempts write a core file it pauses indefinitely. [CSCdi47877]

• When configuring many different MTU sizes on an RSP based system, message %CBUS-3-NOBUF: Buffer allocation failure: can't carve anything may appear on the console. A workaround can be to use the same MTU on different interfaces. [CSCdi48055]

• The electrically eraseable programmable read-only memory (EEPROM) in some chassis interfaces is misprogrammed. A show diagbus command indicates that the chassis interface incorrectly has "07" in the first byte of the EEPROM, instead of "01." The system software does not recognize chassis interfaces that have this error. At startup, the following message appears:

%CI-3-CTRLRTYPE: Wrong controller type 10 %CI-4-NOTFOUND: Chassis Interface not found

The output of the show version command indicates:

WARNING: Chassis Interface not present

When these messages appear, the show environment commands do not work, and no environmental monitoring takes place. [CSCdi48075]

• RFC 1877 is not supported. This prevents Windows 95 and CiscoRemote from learning their DNS servers and NBNS (WINS) servers dynamically. When this feature is added, you will be able to configure the following on the Cisco:

async-bootp dns-server x.x.x.x y.y.y.y async-bootp nbns-server z.z.z.z w.w.w.w

Where:

x.x.x.x is the primary DNS server y.y.y.y is the secondary DNS server z.z.z.z is the primary NBNS/WINS server w.w.w.w is the secondary NBNS/WINS server

To tell if you version has support, issue the configuration command "async bootp ?". Is "nbns-server" appears in the list of valid completions, you have RFC 1877 support. [CSCdi48113]

• Adding a snmp-server chassis-id value gets lost when the router is rebooted. [CSCdi49086]

• In RSP equipped routers, fast switched explorers which were flushed due to maxrate exceeded, were counted as input queue drops in a show interface, in addition to incrementing the flushed explorer count in a show source. This occurred even when the size of the input queue was not exceeded, and there was no shortage of buffers. This change causes the flushed explorers to only be counted in the show source output. This is a cosmetic change only. [CSCdi49673]

• Under certain circumstances, a router will detect and report a Bus Error while attempting to output a debug message. The defect will not be seen unless 'debug aaa authorization' has been set. One case where this defect was seen occurred when a connection was dropped due to too many lost PPP echoes. On the next connection, the defect was seen. Analysis indicates that this defect is unlikely to be seen, and of course, can be avoided by not setting 'debug aaa authorization'. [CSCdi50216]

• According to documentation and online help, it's not possible to increase the queue size of output queue 0. [CSCdi50233]

DECnet

• DECnet Phase IV-to-Phase V conversion might introduce incorrect area routes into the ISO Interior Gateway Routing Protocol (IGRP), if there are DECnet L2 routes on the DECnet side. These area routes show up as "AA00" and are propagated to other routers. [CSCdi47315]

• This is a feature request to have support for DEC MOP over Frame Relay implemented. [CSCdi49406]

EXEC and Configuration Parser

• The uses statistic shown by the show line exec command does not include packet-mode uses of the line (slip, xremote, ppp, etc.) [CSCdi46565]

• Configuration line command autobaud does not appear in the output of write terminal or the nvram configuration file generated by write memory. [CSCdi48971]

• Privilege level definition cannot define 'hub ether'. [CSCdi49001]

• Many people use "u" as an alias for "undebug." This no longer works. [CSCdi49916]

IBM Connectivity

• If the router receives an LLC2 XID packet destined for an X.25 connection (QLLC) that is not yet established, it will drop the packet instead of buffering it until the X.25 connection completes. This behavior will cause connection problems for devices that do not automatically retry and resend the XID pacet. [CSCdi36695]

• You have to configure access-expression on an interface before adding source- bridge input-lsap-list; you get the error: EXPR: access-expression must be specified alone on interface in the opposite order. [CSCdi37685]

• When router is configured with SRB/RSRB it may experience loss of memory. [CSCdi40888]

• When source-route transparent (SRT) bridging is configured on the router, calls to management functions that are related to source-route bridging (SRB) might not work correctly. [CSCdi42298]

• When a front-end processor (FEP) initiates a Qualified Logical Link Control (QLLC) connection, a virtual circuit is established, but the exchange identification (XID) negotiation never proceeds to completion. The router sends XID responses as commands, rather than as responses. [CSCdi44435]

• On a c70x0 router installed with a CIP running CSNA, process and fast switching of packets to the CIP on the virtual interface (Chx/2) can cause all CSNA LLC2 sessions to be abruptly disconnected. [CSCdi45011]

• A router might crash if running QLLC and using remote source-route bridging (RSRB) over a serial line to provide the Logical Link Control, type 2 (LLC2) connection from QLLC to an end station or host. The crash only occurs if multiple changes are made to the encapsulation type on the RSRB serial line. [CSCdi45231]

• Use TRIP microcode version 10.2 for a workaround. [CSCdi46309]

• When concurrent or multiple link activations are requested from or to the same interface or service access point (SAP) of a Cisco Link Services (CLS) user (typically APPN or DSPU) to multiple devices, some of the link activations might fail in random fashion. The problem is more likely to be evident when in networks where test polls are outstanding for longer periods of time, and when many links are auto-activated at the same time. [CSCdi46491]

• A Cisco router might report inaccurate traffic statistics. In particular, non-broadcast frame counts might be incorrect if the router is acting as a source bridge on a Token Ring. [CSCdi46631]

• When configuring dspu for sdlc connection to a fep there is no way to not code a xid; code a dummy xid. The xid will not be used. [CSCdi46728]

• If a CIP is in the lowest numbered occupied slot in a 7000 or 7500 series router, it will not download microcode properly. The router will display the DBUS-3-WCSLDERR message at boot time. A subsequent "microcode reload" or EOIR of the CIP will work. [CSCdi46899]

• Router configured for DLSw+ getting repeated CLS-3-CLSFAIL and DLSWC-3-BADCLSI error messages under show log. [CSCdi46944]

• Explorers are not forwarded to the CIP CSNA feature from DLSw+. [CSCdi47239]

• A Cisco Link Services component (such as APPN or DSPU) may be unable to reconnect after it is disconneted when running over a CLS controlled locally acknowledged RSRB connection. This problem only affects reconnecting after an LLC2 outage when the RSRB peer remains up throughout the disconnect/reconnect process. [CSCdi47275]

• When configuring a name for a CIP CSNA LAN adapter, no check is done to ensure that the name does not exceed the maximum length, which is 8 characters. Configuring the adapter to have a name longer than 8 characters may produce the following message:

%CIP0-3-MSG: %MSG802-3-INVALID_VCN2: LAN has configured for vcn=decimal, adapter=decimal lan=decimal ran=decimal [CSCdi47478]

• Using a CIP with CSNA configured in a Cisco 7500 series router causes cBus complex restarts and output stuck messages for the CIP virtual inteface (ch x/2). [CSCdi47536]

• If a router receives a source-route bridging (SRB) packet with bit 2 of the routing control field set, the router might send back a bridge path trace report frame to a group address, instead of to the source of the original frame. This can cause congestion. [CSCdi47561]

• A downstream physical unit (DSPU) sometimes retries connecting to the host too rapidly, with as many as sixty tries per second, flooding the host with XID packets. This problem causes the NetView log to get congested and run out of storage, which might bring down the host. [CSCdi47803]

• If DLSw with FST is configured, an LLC2 session should not be set up. [CSCdi47888]

• Using the no lnm disable command in conjunction with a CSNA internal Token Ring adapter can cause a bus error. [CSCdi47898]

• The DLSw SDLC ABM bit is not turned off in the first XID sent to an SCLC station. [CSCdi47942]

• The direct command is not supported in the bisync interface. It should not be configured. [CSCdi48520]

• Under the condition where two token ring interfaces are attached to the same physical token ring and where either:

A) an all routes explorer is generated on that ring

B) a packet with a rif that indicates that the packet should go back onto the token ring it originated on

will cause a bridge loop and cause router cpu to rise as well as increase ring utilization.

This bug fix makes the router check the rif in further detail. [CSCdi48577]

• When using appn on a c4500, c4700 or c7500, a spurious memory access message may occur. [CSCdi48608]

• During cross-domain file transfers via Data Link Switching Plus (DLSw+) on a Logical Link Control (LLC) connection, frames might be sent out of sequence. This problem can cause a receiving Physical Unit 4 (PU 4) or Physical Unit 5 (PU 5) to disconnect. [CSCdi48915]

• NETBIOS name recognized frames are now filtered by NETBIOS access-lists as a result of CSCdi36649. This can break some applications and needs to be optional. [CSCdi49101]

• When attempting to run APPN over Frame Relay, the router generates error and traceback messages: "APPN-6-APPNSENDMSG," "APPN-7-APPNETERROR," and "SYS-2-BADSHARE." [CSCdi49162]

• On Cisco 7000 series routers installed with a CIP, the commands csna, llc2, offload , and show extended channel tcp-stack fail after a router reload or reboot. To workaround, reboot the microcode. [CSCdi49312]

• The number of downstream PUs supported should be increased from 256 to 1024. [CSCdi49448]

• When using an APPN Connection Network over FDDI, sessions that utilize the router as a member of the FDDI connection network will fail to activate. [CSCdi49560]

• dlsw remote-peer 0 tcp ip @ tcp-queue-max incorrect. It cant be set to a value greater than 255. [CSCdi49687]

• DSPU error message, DSPU-3-LSXIDNegotiationError, incorrectly reports the bad byte and bad bit fields from the CV 0x22 error vector of an XID3.

The sense data from the CV 0x22 (when present) is also not provided in the DSPU error message. [CSCdi49863]

• Connections to a host cannot be established from a DSPU using virtual telecommunications access method (VTAM) through a Cisco 3172 Channel Interface Processor (CIP). [CSCdi49872]

• When doing large unidirectional files transfers that do not require application level acknowledgements, DLSw does not increment the circuit flow control window fast enough to allow more user I-frame data to flow. [CSCdi49900]

• Users can not control the tcp-queue-max on peer-on-demand peers (those learned about through a border peer). The "tcp-queue-max" keyword was ommitted from the "dlsw peer-on-demand-defaults" configuration command. This ddts adds this keyword.

Additionally, this ddts enhances the "show dlsw peers" output to show the current congestion level of a TCP peer's outbound tcp queue and also displays the amount of time a peer is connected. [CSCdi49949]

• If peer A and peer B are DLSw priority peers (the keyword priority is on the remote peer definition), and peer A is reloaded, peer B may crash. [CSCdi50155]

• IOS 10.2 may fail to forward explorers incoming from RSRB to the local token Ring of low-end platforms. [CSCdi50509]

Interfaces and Bridging

• On a Cisco 4500 router, if you issue the no shutdown command on a Fiber Distributed Data Interface (FDDI) interface, the router will reboot. [CSCdi42429]

• BRI commands not recognized by system with both MBRI NPM and CT1/CE1 NPM installed. Work around is to remove the CT1/CE1 NPM. [CSCdi43998]

• The FDDI interface becomes deaf to data traffic, but not SMT traffic. The command clear interface fddi {number} may provide a workaround. [CSCdi44246]

• When a Cisco 2500 runs X.25 over the B channel of a Basic Rate Interface (BRI), it sends the idle character 0xFF (mark) instead of the idle character 0x7E (flag). X.25 requires flags, not marks, for the idle character. [CSCdi44262]

• The MIP T1 and E1 interfaces do not support enhanced online insertion and removal (EOIR/OIR). There is no workaround. This bug is fixed in Release 11.0(8) and later, and requires a minimum of MIP hardware version 1.1 (73-0903-08 Rev A0).

In addition to the hardware requirement, the fix for this bug that is in Release 11.0(8) and later releases requires that you allow a minimum of 15 seconds to elapse between OIR events. Removal of one interface counts as one event, and insertion of one interface counts as one event.

If your MIP hardware is not at least hardware version 1.1, it will not EOIR or OIR correctly!

Failure to allow this time for the router to stabilize between OIR events can result in the reset performed for one event corrupting the reset performed for another event, which could require interfaces to be reconfigured or reinitialized manually. This reset requires even more time if additional channel-groups are defined within the router. The time between OIR events should be increased to as much as 30 seconds if three or more MIP cards are fully channelized in the router. While the corruption of this reset activity might occur only occasionally if OIR events are too closely timed, it is mandatory to allow the correct interval to guarantee the benefits of EOIR/OIR. [CSCdi46137]

• Fair queueing is not disabled on the interface when encap sdlc is issue. Circumvention is to do a no fair-queue prior to doing sdlc encap. [CSCdi46765]

• Frame relay packet-by-packet compression cannot be configured on point-to-point frame-relay subinterfaces.

Note: that this bug wasn't actually resolved in the 11.0 tree until 11.0(5.1). [CSCdi46908]

• If AAA authorization is used on an interface that is configured for local address pooling, an IP address may be allocated from the pool, authorized by AAA and then returned to the pool before IP traffic starts. However, the IP address will be still be used as the peer address. Since it is now considered 'free' in the local address pool, it may be handed out to another interface resulting in a duplicate peer address on another interface. One sympton of this would be two neightbor routes in the IP routing table pointing to different interfaces. [CSCdi47583]

• Transparent bridging and the HSRP protocol cannnot be simultaneously enabled on Fast Ethernet interfaces. Random crashes occur, which can result in image or memory corruption. [CSCdi48646]

• Bridging from a Token Ring through an ATM cloud via RFC 1483 AAL5-SNAP encapsulation back to a Token Ring does not function because of an incorrect CTL/OUI. There is no workaround. [CSCdi49151]

• CSCdi44835 broke rsp transparent bridging over ethernet.

no workaround

fixed in next release. [CSCdi49301]

• Serial interfaces that are down but not administratively disabled might periodically reset with the error "(8010) disable - fsip_reset()". [CSCdi49431]

• During topology changes and bridge table clearing, %SYS-3-TIMERNEG messages may be logged. As a side effect, bridge table entries may not expire early, but will remain in the bridge table for the full aging interval.

The complete message is of the form:

%SYS-3-TIMERNEG: Cannot start timer (0x...) with negative offset (-...). -Process= "Spanning Tree", ipl= ..., pid= ... -Traceback= ... [CSCdi50360]

IP Routing Protocols

• ARP throttling not working [CSCdi43596]

• Under some circumstances, when a DVMRP neighbor becomes active over a DVMRP tunnel, the tunnel will not be added to the outgoing interface list for existing multicast routing table entries.

Workaround is to do a "clear ip mroute *" after the neighbor becomes active. [CSCdi46003]

• If a router is incorrectly configured with an autonomous system (AS) placed in a confederation it is not part of, the confederation information within the AS path will be incorrectly propogated. The workaround is to configure the router correctly. [CSCdi46449]

• Fair queue size is limited to 512 elements. [CSCdi46763]

• OSPF is not able to do load balancing on multiple connected interface which is configured on the same subnet. This fix solves the problem for 11.0 and later release. [CSCdi47030]

• EIGRP packets are sent out on async interfaces which normally should not be routing unless configured with async default routing. [CSCdi47184]

• On a Cisco AGS+ router with FDDI interfaces and 181-1 cBus microcode on the interface, enhanced IGRP does not discover neighbors when bridge-group is configured on that interface. [CSCdi48057]

• If there is a gateway of last resort in the routing table, packets that should be forwarded to a helper address are instead send out the interface to the gateway of last resort. The destination ip address is filled in with 0.0.0.0 in the packet header. If there is no gateway of last resort, this problem should not occur.

There is no workaround for this problem. [CSCdi48312]

• On a router that borders a PIM/DVMRP multicast environment, DVMRP graft messages fail to be generated causing latency in joining an IP multicast group. [CSCdi49375]

• Packet corruption might occur when fast-switching IP packets from ATM interfaces to Token Ring interfaces configured with the multiring command. [CSCdi49734]

ISO CLNS

• ISO Interior Gateway Routing Protocol (IGRP) will not work when interoperating between Motorola processor-based Cisco routers (older routers such as MGS, AGS+, or Cisco 7000) and millions of instructions per second (mips) processor-based Cisco routers (later routers such as the Cisco 4500, 4700, or 7500). [CSCdi44688]

• ISIS fails to install more then one Level2 route in the CLNS routing table, when there are multiple equal-cost paths to the other area available. As a result there is no CLNS loadbalancing for destinations in another area. [CSCdi48162]

• When DECnet IV/V conversion is on, and the Phase V protocol is ISIS, ISIS adjacencies in the adjacency data base can end up with an adjacency format of "Phase IV".

This can happen if a DECnet IV hello was received first, in which case DECnet creates a Phase V adjacency in the adjacency data base, and marks it as "Phase IV". When the ISIS hello comes in a little later, ISIS fails to modify the adjacency format to be "Phase V".

A snippet of a display from the customer's router is attached below:

KCCR01# sh clns is

System Id Interface State Type Priority Circuit Id Format AA00.0400.2204 Ethernet0 Up IS 0 0000.0000.0000.00 Phase IV ...

Clearing the table and re-issuing the "show" command shows:

KCCR01# sh clns is

System Id Interface State Type Priority Circuit Id Format AA00.0400.2204 Ethernet0 Up IS 0 0000.0000.0000.00 Phase V

Basically, the problem will show up when the DECnet hello comes in first. [CSCdi48461]

• ISIS doesn't allow multiple NET's.

gray(config)#router isis gray(config-router)#net 39.840f.1135.6700.26.55.0020.0054.d900 gray(config-router)#net 39.840f.1135.6700.27.55.0020.0054.d900 % Ambiguous command: "net 39.840f.1135.6700.27.55.0020.0054.d900"

This is because the parser generates another command at the 'router isis' level which makes the 'net' command ambiguous. The other command ('network') actually applies to BGP and should not be generated by the parser at the 'router isis' level.

gray(config)#router isis gray(config-router)#net 39.840f.1135.6700.27.55.0020.0054.d900 gray(config-router)#? Router configuration commands: ... ... lsp-gen-interval Minimum interval between SPF calculations lsp-mtu Set maximum LSP size maximum-paths Forward packets over multiple paths net A Network Entity Title for this process (OSI only) network Specify a network to announce via BGP [CSCdi48790]

Novell IPX, XNS, and Apollo Domain

• Cisco 1003, Cisco 1004, and Cisco 1005 routers advertise all IPX services with a SAP hop count of zero. Both dynamically learned and static SAPs are sent out every interface with a zero hop count, which makes remote services invisible to Novell servers connected directly to the router (for example, on the LAN interface).

Clients on LANs with no server can connect correctly, because the router answers the GetNearestServer request. However, whenever a Novell server resides on the same LAN as the client, the client will not be able to connect to any remote services.

Use the show ipx servers command to determine whether any SAPs are being seen with zero hop count from the neighboring router. [CSCdi46488]

• Use of the command no ipx sap-uses-routing-info causes Services learned after sap-uses-routing-info was disabled to not be propagated out other interfaces, included responses to SAP queries and GNS queries.

Workaround is to enable ipx sap-uses-routing-info. [CSCdi46812]

• When an IPX static route is configured to be associated with an ipx interface which is presently down the static network defined in the static route is advertised as reachable until the interface state changes, it should not be advertised until the link comes up. [CSCdi47023]

• the configuration of ipx delay to set a ticks value for an interface allows too large a value, the current range is 0 thru 1000000, the maximum value should be 65535. [CSCdi47086]

• Parallel equal bandwidth IPXWAN links may calculate different NLSP metrics. [CSCdi47276]

• Services added to the Service Table which have no direct route to their network but do have a default route are not being re-advertised out other interfaces. [CSCdi47299]

• Network FFFFFFFE is ignored when the handling of FFFFFFFE as the 'The IPX Default Route" is disabled, when default route handling is disabled FFFFFFFE shouold just be another ipx network as is is in 10.2 and earlier releases. [CSCdi47314]

• When debugging ipx sap events debugging is displayed for failure to forward packets which are not sap packets. [CSCdi47413]

• NLSP and ISIS may report corrupted LSP checksums. There is no workaround to this problem. [CSCdi47916]

• The ipx accounting command does not get removed after no ipx routing is configured. The workaround is to issue no ipx accounting command before disabling routing. [CSCdi48651]

• On 4500 systems using token ring IPX SNAP encapsulation can produce alignment warning message. [CSCdi49352]

• When an Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) route is advertised back into Routing Information Protocol (RIP), the delay within the Enhanced IGRP cloud is not properly taken into account in the tics metric value of the route when it is redistributed into RIP. The RIP advertised route might then look closer than it really is. [CSCdi49360]

• When an interface goes down, services that are not learned over that interface are marked as down. This behavior might cause excessive SAP packet generation because packets are flooded first as down, are then learned, and are finally flooded again as new. [CSCdi49369]

• If IPX Enhanced IGRP is running, the following command sequence might cause the router to reload: interface serial no ipx network no ipx routing [CSCdi49577]

• IPX Services advertised by SAP with a missing Servicename are accepted by the Service table, they should be rejected. NetWare Servers when seeing this Service advertised in NLSP LSPs will complain about an "LSP L1 packet received ... has malformed option code 0xc3" [CSCdi50223]

TCP/IP Host-Mode Services

• Under unknown circumstances, random lines on an ASM will pause indefinitely in Carrier Dropped state. The only way to clear the line is to reload the ASM. [CSCdi44663]

• If an IP helper-address is configured on an interface, the router will fail to forward directed broadcasts sent to a MAC broadcast address. [CSCdi47639]

• When a DLSw remote peer brings down a TCP connection during the peer connection sequence, the partner DLSw router may crash. This ddts fixes this problem by adding better communication between DLSw and the tcp driver. [CSCdi47801]

• Opening hundreds of simultaneous telnet connections from a TTY or VTY can cause the software to reload with a watchdog timeout error. [CSCdi47841]

• Receiving malformed TCP options on a connection can cause the software to reload. [CSCdi49358]

• A router running DLSw may print the following error message when a peer reloads:

%SYS-6-STACKLOW: Stack for process TCP Driver running low, 36/1000 [CSCdi50306]

VINES

• VINES servers located downstream might unexpectedly lose routes that were learned via Sequenced Routing Update Protocol (SRTP). This behavior results from improper handling of network sequences numbers by the system. Issuing a clear vines neighbor or disabling SRTP are suggested workarounds. [CSCdi45774]

• A Cisco router reloads when it receives incorrectly formatted Interprocess Communications Protocol (IPC) packets from the VINES application software Streetprint. The VINES IPC length field should contain the number of bytes that follow the long IPC header in a data packet, but Streetprint incorrectly sets the IPC length in each IPC message to the total number of bytes of all IPC messages. [CSCdi47766]

• If a Vines-configured serial interface is down, then a small-buffer memory will occur. This leak will occur for as long as Vines is configured on the interface, or as long as the interface is down. [CSCdi48180]

• Vines clients using Bluemail get the message "time not available" on serverless segments connected to a 4500 or a 4700. The only workaround is putting a Vines file server on the segment. [CSCdi48247]

• Lost connectivity to Vines server co-incides with appearance of Align-3 message on console. Router is configured for Vines SRTP routing. SH ALIGN reports a number of spurious memory access errors pointing to the same SRTP procedures. [CSCdi48252]

• A simple vines access list (in the range 200-299) is used to filter time updates. This should be applied with the global configuration command vines time access-group 2xx.

The parser incorrectly accepts the interface configuration command vines access-group 2xx which can yield unexpected results.

The workaround is to use the correct configuration as specified in the "Router Products Configuration Guide". The example in the "Router Products Command Reference" under the vines access-list (simple) is incorrect up to and including the 11.0 documentation. [CSCdi49568]

Wide-Area Networking

• Each interface can be configured to authenticate using either CHAP or PAP.

There is currently no mechanism to switch to a different protocol if the default authentication protocol is not supported on the remote client. [CSCdi35908]

• When a LAN Emulation (LANE) client becomes nonoperational, the subinterface remains in the Up state. This causes routing tables to retain routes longer than normal. These routes remain until the configured routing protocol discovers (via neighbor discovery or holddown) that the subinterface has gone deaf. Static routes are discouraged on LANE interfaces, because the route will always be advertised. [CSCdi36121]

• When routing an X.25 call request packet containing a Calling/Called Address Extension facility, sometimes the Calling/Called Address Extension facility is inadvertently modified. [CSCdi41580]

• An X.25 interface might hang if the Link Access Procedure, Balanced (LAPB) layer gets stuck in the RNRsent state. This might occur if virtual circuits (VCs) receive encapsulated datagram fragments that are held for reassembly, and the number of these fragments approaches the interface input queue count. The LAPB protocol will not exit the RNRsent state until the number of held buffers decreases. This condition can be cleared if a shut /no shut is performed on the interface, or if the other end of the LAPB connection resets the protocol. [CSCdi41923]

• The subinterface shutdown command is ignored by ATM subinterfaces. Existing SVCs are not deleted and processing of traffic continues. [CSCdi43692]

• If a new permanent virtual circuit (PVC) is defined on an ATM Interface Processor (AIP) when existing switched virtual circuits (SVCs) and PVCs are already defined, an interface reset might occur with a subsequent restart of all SVCs. [CSCdi43779]

• When IP traffic is fast switched from an AIP onto an FDDI interface, an extra byte added to the end of the packets. [CSCdi44580]

• The traffic counters of the show atm traffic command for ATM interfaces may not reflect all of the traffic counted in show int atm command.

show atm traffic command output looks as follows now:

router#show atm traffic 279548 Input packets 15025 Output packets 17 Broadcast packets 0 Packets received on non-existent VC 0 Packets attempted to send on non-existent VC 129 OAM cells received 134 OAM cells sent

where Input packets include all input packets on the atm interfaces i.e. process , fast and autonomous switched as well as those received on non-existent VC.

Similarly Output packets include all process, fast and autonomous switched out- going packets including broadcast packets.

Packets attempting to be sent on non-existent VC are just displayed and not counted as Output packets since they are never sent. [CSCdi45189]

• On reload an X.25 interface can enter the 'protocol up' state before all of the interface's configuration commands have been processed. This can cause problems if the X.25 configuration includes commands that will not take effect while the protocol is up (i.e. modulo, default window and packet sizes and the VC range parameters).

The symptom of this problem is the printing of 'Parameter held until RESTART' messages while the router image has not completed its startup. In particular, the PVC configuration commands will be refused if commands to modify the default VC ranges are held off. [CSCdi45199]

• When a Cisco 4000 with a Basic Rate Interface (BRI) has the isdn tei powerup configuration flag set, the watchdog timeout will crash the router. A workaround is to configure the router with the isdn tei first-call command. [CSCdi45360]

• Running X.25 Defense Data Network (DDN) encapsulation on a Cisco 2500 serial port might cause the router to reload. This problem appears to be the result of mixing x.25 switching and X.25 DDN. A workaround is to shut down the serial interface. [CSCdi45673]

• When configuring 2 routers back-to-back via ATM using SMDS encapsulation, you may experience intermittent ping failures.

Cisco Systems expects to resolve this caveat in a future AIP microcode version. [CSCdi45807]

• Fix is as follows:

This is regarding an internet draft from S. Cobb of Microsoft [to update RFC 1332].

We currently implement the IP DNS [main, secondary] configuration ["tell me who your DNS server is"] portion of this draft but it was suggested that we give the server configured by the async-bootp command instead, if configured. This has been implemented.

A separate bug will be added for configuration of the WINS name server information. [CSCdi46322]

• The router can reload if two PAD connections were initiated if "debug x25" and "terminal monitor" are enabled on one of the PAD connections while the other connection is doing constant pings. [CSCdi46665]

• Routers with ISDN BRI interfaces which use the isdn switch-type basic-net3 command may experience BRI port failures dues to all network layer control blocks (NLCB's) being used and never released. Once all NCLB's and call control blocks (CCB's) are used and hung, a reload of the router is required to use the BRI interface. The problem does not apply to ISDN Primary Rate interfaces (PRI).

A possible workaround is to set the dialer idle-timeout value on the BRI routers connected to NET3 switches higher than the timeout value of the other router or routers connecting via ISDN. This assumes the other router or routers do not have BRI's connected to NET3 switches, as they would have the same problem. This also requires knowledge of the dialer idle-timeout value configured on the other router or routers.

The problem does not occur if the call hangup is initiated by the ISDN network rather than the BRI router connected to a NET3 switch.

11.0(2.1), 10.3(6.1) and 10.2(8.5) were the first available versions which exhibited the problem. [CSCdi46668]

• Async interface connections hung up in heavy load conditions. Async interfaces use standard keepalives suited to faster and high bandwidth interfaces. [CSCdi48054]

• Under some unknown conditions, an ISDN B Channel may fail to disconnect. The PPP keepalive feature detects the partially disconnected link and repeatedly reports "exceeded max retries taking LCP down" every few minutes. This defect was introduced in software version 11.0(3.2). [CSCdi48111]

• The IPXCP Configuration Complete option is not supported. This is an advisory option to indicate that the sender thinks that no more negotiation is necessary. The option will be supported in a future release of IOS. [CSCdi48135]

• Some PPP clients will not negotiate the IPCP IP address option, either because they have been pre-configured or because they captured the IP address from the login session. As a result, the IPCP code will not install a neighbor route or dialer map to the peer's address. In a future release, a neighbor route and dialer map will always be installed to the peer address which may have been pre-configured or entered at the command prompt. [CSCdi48136]

• The cisco will have problems running the primary-dms100 switchtype against a Meridian 1 configured running SL1 network mode. The channel-id, called party and call ref length are not compatible. [CSCdi48239]

• Changes required to pass ISDN BRI NET3 France Delta testing. [CSCdi48422]

• Incoming 64kb voice calls will not work. An incorrect assumption was made at implementation. [CSCdi48606]

• There are some errors in the prompts when configuring frame relay.

In some instances the user is given a help prompt that indicates RFC1294 encapsulation is about to be configured.

This is erroneous. RFC1294 is obsoleted by RFC1490.

As of IOS release 10.3 Cisco uses RFC1490 for bridged and routed protocols.

These errors are all cosmetic.

No work around is required. [CSCdi48715]

• If parallel connections are made to a dialer group or ISDN interface that use the same IP address and a neighbor route is necessary, then the neighbor route is added for the first connection only. Subsequent connections will detect that a route already exists and do not add another route. This situation works until the first connection closes and its neighbor route is removed. The other connections remain but no neighbor route is installed for them. This problem applies to parallel connections not to multilink bundles. [CSCdi49007]

• When booting a router on which all ATM interfaces are in a no shut state, you need to issue a shutdown and no shutdown command sequence on one of the ATM interfaces to make Service-Specific Connection-Oriented Protocol (SSCOP) fully initialized and to allow ATM signaling to function properly. [CSCdi49275]

• If Cisco's enhanced Terminal Access Controller Access Control System (TACACS+) is enabled, you cannot specify inbound authentication on the Point-to-Point Protocol (PPP) authentication configuration line. [CSCdi49280]

• Nondefault IPX encapsulation on an ATM subinterface using the ipx encaps xxx command does not work. To configure the nondefault encapsulation, use the ipx network network encapsulation encapsulation-type command. [CSCdi49729]

• Cisco IOS Release 11.0(6), Release 11.1(2), and Catalyst 5000 ATM software release 2.1 and later contain a fix for an Emulated LAN defect. If you deploy Release 11.0(6), Release 11.1(2), or Catalyst 5000 ATM software release 2.1 or later releases in your network, and you use Emulated LAN bridging features, you must upgrade the Cisco IOS software in all routers and Catalyst 5000 switches in your network to use a version of Cisco IOS software that contains the fix. Failure to upgrade all devices in a particular Emulated LAN will result in interoperability problems between Cisco devices.

If you choose to continue to use Cisco IOS Release 11.0(5), Release 11.1(1) or earlier releases, the Catalyst 5000 requires ATM software release 1.1. [CSCdi49790]

XRemote

• Xremote does not work if attempted from telnet connections. [CSCdi49862]

11.0(4) Caveats/11.0(5) Modifications

This section describes possibly unexpected behavior by Release 11.0(4). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(4). For additional caveats applicable to Release 11.0(4), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(5).

AppleTalk

• If you take a Macintosh that is already connected to a local appletalk network (e.g. it already has a zone) and use ARAP to dial into a remote network, the Mac will not answer an NBP lookup in the remote network zone. The Mac would only answer NBP lookups in one of the zones it is connected to. [CSCdi26866]

• AppleTalk Transaction Protocol (ATP) packets might be incorrectly sent to a multicast address instead of a unicast address. This can cause problems such as the inability to login to an AppleTalk server. [CSCdi44145]

• AT eigrp doesn't update fast cache entries when eigrp routes go away. Therefore, it is possible that the fast cache may contain invalid entries when running AT eigrp. This fix corrects this problem by invalidating the fast cache entries when eigrp routes go away. [CSCdi46975]

Basic System Services

• When fast-switching is enabled on an async interface, configured with PPP/CHAP and tacacs+ network authorization, a per-user access list applied by the tacacs+ server may stop working as soon as permitted traffic has passed through the interface. Configuring no ip route-cache on the interface will prevent the problem at the expense of slower performance. [CSCdi39791]

• When configuring a new protocol to be routed, the router will bring down existing ISDN connections. Examples are "ipx routing" or "no vines routing". This is an inconvenience when telnetted into the router over ISDN to configure another protocol. [CSCdi42391]

• If a packet being bridged either exceeds the maximum size or is too small a crash may occur on the 10.3 release. For the 11.0 release and later, the problem exhibits itself as an alignment error. [CSCdi43513]

• When doing Tacacs+ authorization, any server message returned by the Tacacs+ daemon in an authorization response is ignored i.e. not displayed to the user. [CSCdi44055]

• TACACS should be able to use a specific ip address for all outgoing TACACS packets. [CSCdi45224]

• Certain snmp manager (cabletron) machines look at the ipRouteType field of a query (rfc1213) to find out if the network reported is directly connected or not. When we report a static route to the snmp querier we always put the ipRouteType as "direct(3)" which stands to mean directly connected which is not true in all cases. [CSCdi45367]

• When authenticating using tacacs or extended tacacs with PAP on an interface which is not an asynchronous line, the system may reload if the principal's username and password also exist in the local database. [CSCdi45530]

• Polling the following Management Information Base (MIB) variable causes the Cisco 7000 router's CPU utilization to exceed 90 percent: .iso.org.dod.internet.private.enterprises.cisco.local.linterfaces. lifTable.lifEntry.locIfOutputQueueDrops [CSCdi45961]

• Tacacs+ does not send accounting stop requests. [CSCdi46519]

• use of HSRP in heavy traffic situations can cause RSP-3-ERROR reports and cbus resets. [CSCdi46654]

• When querying the variable dot1dBaseBridgeAddress from rfcs 1286 and 1493, the value ffffffffffff is returned rather than a unique identifier for the router.

This will cause the discovery mechanism of IBM bridge management software (Lan Network Manager for AIX) to fail against Cisco Routers. [CSCdi46677]

• If TACACS+ is configured to return a Mandatory peer IP address, this address will be ignored at PPP or SLIP startup from an exec command. If TACACS+ is configured to return an Optional peer IP address, this address will be used. This defect does not affect TACACS+ returning a peer address during IPCP negotiation. [CSCdi47170]

• Upon process completion the scheduler will leak a small amount of memory. On routers that have numerous processes, such as ipx, the memory leak can be significant. When the router runs out of memory a crash is possible. There is no workaround, you must upgrade to a revision of the code that contains this fix. Note that this bug only exists in 11.0(4.2) and 11.0(4.3). [CSCdi47177]

• The initial introduction of the following command : snmp-server enable traps envmon

introduced a problem wherein any use of the "snmp-server enable traps" command will automatically enable all envmon SNMP traps. This occurs when the user types in this command, as well as after a router reboot, if any other "snmp-server enable trap" exists in the configuration file. The only workaround is to manually type : no snmp-server enable traps envmon or to disable the envmon traps via SNMP.

Again, this will disable the envmon traps, but the traps will be enabled again on the next reboot. [CSCdi47252]

DECnet

• Switching of DECnet Phase IV packets may be slow when the packets need to traverse a Phase V cloud (i.e. when DECnet IV/V conversion is involved).

An illustration of this problem can be seen by issuing a 'SET HOST' command from one Phase IV host to another over a Phase V cloud, and noticing that the connect can take about a minute to complete. Normally this operation should take a few seconds. [CSCdi38569]

• The 'show dec static' command shows bogus SNPA's if the static route that is being displayed points to a non p2p interface, and the SNPA does not have an 'ethernet-like' format (an example is an X.121 address).

This is a cosmetic bug only. [CSCdi46327]

EXEC and Configuration Parser

• If you configure a nondefault Fiber Distributed Data Interface (FDDI) transmission time and save the fddi valid-transmission-time to nonvolatile random-access memory (NVRAM), the system will reload when the boot monitor reads the command from NVRAM at boot time. If a nondefault time is required, the workaround is to boot that portion of the configuration using the boot host command. [CSCdi37664]

IBM Connectivity

• When applying NetBIOS access lists with rsrb remote-peer access list statements on a system with active SRB traffic, the router may reload due to a bus error. The fix changes the system code so that it handles these conditions in a more graceful manner. [CSCdi18993]

• Commands are no longer tied to encapsulation type and are translated as follows:

sdlc hdx becomes half-duplex bsc fdx becomes full-duplex sdlc rts-timeout val becomes half-duplex timer rts-timeout newval sdlc cts-delay val becomes half-duplex timer cts-delay newval

Note that the units for newval are in milliseconds while the v alues for val were in microcode cycles. These values are translated by the code. [CSCdi30258]

• Optimize APPN ISR (intermediate session routing) data throughput performance. Users can expect a substancial increase in APPN data throughput. [CSCdi32469]

• Some token ring packets that are parsed can end up with the RIF field aligned on an odd byte boundary, causing this message %ALIGN-3-CORRECT. [CSCdi35413]

• Mis-aligned routing information field in SRB packets cause an error message to be displayed. This error message is only seen on routers with MIPS processors (4500, 4700, 7500). [CSCdi36169]

• The hold-queue num out command on the CIP interface is not retained after a microcode reload, and the output hold-queue depth of the CIP interface is returned to the original default value. The hold-queue num out for CIP interfaces must be reconfigured after a microcode reload command. [CSCdi40831]

• The counters for "Processor" and "Route cache" switched packets are incorrect in the "show interface interface-id stats" command output.

When a packet cannot be fast switched using the route cache, the packet must be switched by the processor.

The counters for "Route cache" switched packets are incremented even if the fast switch of a packet fails.

The counters for "Processor" switched packets are incremented correctly. [CSCdi41891]

• Currently the IOS will warn the user if a duplicate bridge is defined in the router. This condition should never be permitted. [CSCdi42740]

• The token ring interface fails to pass any traffic once the input queue becomes wedged. The wedged condition can be detected by issuing a show interface token x/y. When the input queue shows 76/75 the interface is wedged. The short term workaround is to increase the size of the hold queue. This can be done by going into config mode and enter the interface sub-command hold-queue 999 in. [CSCdi43561]

• On low-end systems for a DTE router interface, after a router reload, SDLC packets are identified as HDLC packets by the serial driver until a shut/no shut command is performed for the interface. This causes occassional packet drops without any trace, if the byte pattern happens to match that of other protocols. This can also cause serious performance problems. [CSCdi43686]

• Using the SRB proxy-explorer feature with SRB autonomous switching on FDDI can cause incoming packets to be dropped by the FDDI interface. The work around is to disable the SRB proxy-explorer feature or disable SRB autonomous switching on the FDDI interface. [CSCdi44095]

• Frame Relay autoinstall with dlsw bridge-group 1 in the router configuration can cause the router to reset with error message " Exception: Software forced crash at 0x" [CSCdi44169]

• When configuring "netbios name-cache timeout", the parser help incorrectly specifies the units as seconds. The actual parameter used and the documentation correctly specify the units as minutes. Any value greater than 35000 for this value is accepted but will give unexpected results. [CSCdi44259]

• When configuring proxy-explorers on an interface that is bridging IPX traffic, the router would detect invalid memory accesses and display the following message:

ALIGN-3-SPURIOUS: Spurious memory access made at 0xnnnnnnnn reading 0x1 [CSCdi45258]

• When running DLSw+ frame-relay encapsulation in a non pass-thru mode, Netbios stations may time out. This may happen especially on Netbios stations that have Netbios retries and timeout values lower than the default values. The default values are typically retry value of 8 and timeout value of 500 ms. Increasing Netbios retries and/or timeout value will eliminate this behavior. [CSCdi45362]

• When configuring more than 2 interfaces in a ring group, where the interfaces are bridged into the ring group using different bridge numbers, explorers would not be forwarded out all the interfaces in the ring group. [CSCdi45373]

• DLSw peers with direct encapsulation will not be connected. Use TCP encapsulation as a workaround. [CSCdi45411]

• Release-note: A router configured for QLLC support of a PU 2.0 to a host may ignore the null XID response from the host, and not send the XID T2 on behalf of the controller. [CSCdi45514]

• DSPU/SNA interface configuration commands are accepted by the parser even though this configuration is not supported. [CSCdi45529]

• When running aping traffic for long time the router will intermittently crash at CepPongRequest. This was seen on the 4500, but it could happen on any platform. [CSCdi45974]

• Outbound access lists were not always being applied to fast switched explorer frames. [CSCdi46182]

• -- Release Note --

When a locally attached SDLLC connection sends a TEST frame to a CIP connected host, the TEST frame is dropped and router reports a Bad VCN error. Frames are in turn received from the host and forwarded to the appropriate destination.

This problem only exists when there are access lists configured on the router interfaces. [CSCdi46474]

• The cost from capabilities exchange was being ignored by the peer. With this fix, When cost is not configured in the remote-peer statement, the cost received from the remote peer in the capabilities exchange message is used. [CSCdi46574]

• When using DLUR and attempting a logon at a USSMSG10 from a downstream dependent LU, the LU will get stuck in a wait state. [CSCdi46681]

• Router configured for DSPU crashes at _CLSCepCheck while making DSPU config changes. [CSCdi46820]

Interfaces and Bridging

• Low-end routers do not check collisions or keepalives to determine line protocol up/down. High end routers check both to determine line protocol up/down. [CSCdi32464]

• The serial interface on a Cisco 2500 series router enters a looped state if it is configured as a backup DTE interface and if the cable is disconnected and reconnected a few times. To fix the problem, enter a clear interface command. [CSCdi32528]

• Mis-alligned packets causing %ALIGN-3-CORRECT messages in a token ring environment. [CSCdi35920]

• On a 4000 with ISDN BRI interfaces, the link establishment uses too much memory to set up the call causing the link not to come up. [CSCdi37200]

• A Cisco 7000 series router configured with a Silicon Switch Processor (SSP) might sporadically reload when main memory is low. [CSCdi43446]

• Changing the encapsulation on a dialer interface after issuing the command no dialer in-band causes the router to reload. To prevent this problem from happening, do not remove the dialer type from the configuration. [CSCdi44101]

• for atm tbridging of 2 ethernets, snap packets of size 1492 bytes will not be bridged correctly.

no workaround.

fixed in next release. [CSCdi44993]

• When bridging is configured on interfaces not capable of silicon switching engine (SSE) bridging, then SSE bridging for all interfaces on the router is disabled. The workaround is to use cBus bridging. [CSCdi45124]

• Without this fix, compression statistics for compression on HDLC-encapsulated lines will not be updated. The result is a display of all zeros...

Even without the fix, compression continues to work, but evaluation of compression ratios is complicated. [CSCdi45308]

• The output of show controller cbus on an SSP will will be inconsistent when reporting the Altera version number. [CSCdi46074]

• On the 7000, sometimes you will see an error like the following when you remove an interface processor card. For example, the following error occured when I removed an interface processor from slot 1:

DBUS-3-DBUSINTERR: Slot 1, Internal Error %CONTROLLER-2-CRASHED: Interface Processor in slot 4 not responding (8004): shutting it down

This error occured because the software was trying to access the card after it had been removed. [CSCdi46228]

• The MIP board will continue to experience output drops in severely bursty traffic; this fix will allow more smaller packets to be locally queued on the mip. [CSCdi46383]

• Transparent bridging is broken when bridging from atm to atm. packets get corrupted and show up on the other side as bad SAP packets.

no work around.

fixed in next release. [CSCdi46803]

• If TACACS+ returned an IP address during SLIP or PPP Authorization (during command processing at the exec level), the peer address would be ignored unless 'async dynamic address' had been configured. [CSCdi47013]

IP Routing Protocols

• From one router customer is not able to trace to another router that is directely connected via ethernet. Noticed that the destination router is not responding with port unreachables. [CSCdi40929]

• Attempts to route Internetwork Packet Exchange (IPX) packets by Routing Information Protocol (RIP) or by Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) might fail on primary serial interfaces. Failure can occur when the subinterfaces were configured for IPX routing before their primary interface was. [CSCdi44144]

• OSPF tries to delete MAXAGE LSA when no delete bit is set. This results in a slower convergence. It can be seen under 'debug ip ospf events'. [CSCdi44588]

• If the area id of the network command for ospf is changed on network statment. The subnet in that network statment still remains with the old area ID in ospf database. Unless you do "no network" statment first with the old area id first, and then add the new network statment with the new area id. [CSCdi44966]

• No fair-queue command on async interface has no effect. [CSCdi45120]

• If there is non-OSPF recursive route (with higher adminstrative distance) installed in the routing table and that route is also advertised by OSPF, then spurious memory access could happen when OSPF does route calculation. [CSCdi45610]

• AURP tries to send a Open-Req to establish a connection, it fails because IP ARP fails to create incomplete entry for IP address.

Symptom:

#sh app int tun 0 Tunnel0 is up, line protocol is up AppleTalk port is an AURP Tunnel AURP Data Sender state is Unconnected AURP Data Receiver state is Waiting for Open Response AURP Tickle Time interval is 90 seconds AppleTalk address gleaning is not supported by hardware AppleTalk route cache is not initialized

Debug:

#sh deb ARP: ARP packet debugging is on UDP: UDP packet debugging is on ATIP: AURP packets debugging is on AURP connection debugging is on

AT: Tunnel0: Open-Req sent UDP: sent src=1.0.0.2(387), dst=1.0.0.1(387) IP ARP: failed to create incomplete entry for IP address: 1.0.0.1

Work-around: Ping the other side of the tunnel (IP address). This will create the ARP entry and AURP will be fine after that. [CSCdi46070]

• Enhanced IGRP might announce IP summary routes that have the metric value set too high. This can make the applicable networks unreachable. [CSCdi46290]

• If two OSPF processes exists and redistribution is configured, when a connected OSPF interface for the redistributed OSPF process go down, the router could crash. [CSCdi46409]

ISO CLNS

• When a router has a statically configured ES/IS neighbor, ISO-IGRP fails to advertise them after clear clns route . The workaround is to delete and readd the static neighbors. [CSCdi42468]

• When one has configured a static clns route, this route should be automatically redistibuted into ISIS. When the static clns route is pointing to a next-hop NSAP, the route gets redistributed OK. When the static clns route is pointing to an interface, the route does *not* get redistributed into ISIS. [CSCdi44622]

• If an IS-IS LSP is not regenerated for 24.8 days, it will become impossible to transmit it for another 24.8 days. This could only happen in extremely stable IS-IS networks. [CSCdi45179]

• Under rare conditions, show isis route can cause the router to reload. [CSCdi45496]

• Configuring an ISIS 'net' multiple times results in the creation of multiple ISIS Update and Adjacency processes. [CSCdi45586]

• The ISIS "level-2 attached" flag is set in some ISIS Link State Packets in which it should not be set. This problem has no known operational effects. There is no workaround to this problem. [CSCdi46860]

• When ISO-IGRP is running on a router, and a CLNS default route is configured, the ISO-IGRP routing table entry corresponding to the local entry shows "*Unknown SNPA*", instead of the usual "--".

This is purely cosmetic in nature, and has no impact on CLNS routing functionality. [CSCdi47322]

Novell IPX, XNS, and Apollo Domain

• When issuing the interface subcommand "ipx sap-incremental eigrp (AS) rsup-only" for a second EIGRP Autonomous System (AS), an additional "ipx sap-incremental eigrp (AS) rsup-only" command is added to the configuration for the first EIGRP AS automatically. [CSCdi37965]

• When using subinterfaces and multiple IPX encapsulations it is necessary to use either the "ipx network x encap y" form of the ipx network command or to put the ipx encapsulaiton novell-ether as the last subinterface.

If one uses the "ipx network x" and "ipx encapsulation y" form, that is two commands, and the first interface configured in for encapsulation novell-ether then the second interface will complain about encapsulation already in use.

This can be a problem if the subinterface was configured in the following manner in configuration editor:

interface ether 1.3 ipx encap sap ipx network 777

The system will accept this and this will function normally until the next system reload/power-off/on at which time the ipx network 777 will produce an error message and not be accepted. [CSCdi38803]

• XNS routing fails over AIP interface after a no mac-address command is given which changes the mac address. [CSCdi44602]

• IPX fastswitching fails over non-LANE AIP (ATM) interfaces, this problem was introduced in 11.0(3.1) in a fix for IPX LANE fastswitching. [CSCdi44647]

• When using NLSP and RIP in a network with parallel or multiple paths an NLSP external route may replaced by a RIP route, if the RIP route is the best (or tied for best) route known in the area. Under these circumstances, entries for this network which are already in the fastswitch cache will not be invalidated, causing a sub-optimal routing path to be taken. [CSCdi45600]

• Static SAP command should write to non-volatile memory the quoted string to allow embedded spaces.

example: ipx sap 4 "Silly ServerName" 1.0000.0000.0001 453 3 currently is written to NVM as ipx sap 4 Silly ServerName 1.0000.0000.0001 453 3

upon system reload an error is generated for the static sap. [CSCdi45662]

• If ipx sap-incremental is configured, a router might end up with fewer service access point (SAP) entries than actually exist if the interface goes down and then comes back up. This problem occurs more often when there are many SAP entries in the network environment. [CSCdi46224]

• The IPX ping command may accept illegal IPX addresses and convert illegal portions of the adress to zro. Example: ping DY.0000.0000.0001 becomes ping 0.0000.0000.0001, it should produce and illegal ipx address message and abort the ping. [CSCdi46268]

• The global configuration command ipx nlsp has no options having to do with RIP/SAP compatibility the help message is misleading and should be changed. [CSCdi46270]

Protocol Translation

• A TCP to LAT/X25 translation with an "access-class" option specifying an extended access list can cause the router to reload. Extended access lists are not allowed to be used with a translate command. [CSCdi44853]

• Using AppleTalk Remote Access over a V.120 connection causes the message "%SYS-3-HARIKARI: Process VTY-ARAP Helper top-level routine exited" to be displyed on systems running the Protocol Translator option. [CSCdi45538]

• If a PPP authentication mechanism has been set for a VTY interface, then an attempt to set an alternate mechanism will appear to succeed but the old mechanism will still be used and written out in the configuration. [CSCdi46568]

• When doing protocol translation, the IP address assigend to the Virtual Async line is missing from the extended tacacs XTA_SLIPOFF message sent by the system. [CSCdi46961]

TCP/IP Host-Mode Services

• On a Cisco AGS+ router or Cisco 7000 router, if ip tcp header-compression is turned on for Fiber Distributed Data Interface (FDDI) or serial interfaces, the following error message might display: %LINK-3-TOOBIG: Interface Serialxx, Output packet size of 1528 bytes too big [CSCdi38666]

TN3270

• If a null field is encountered in a TN3270 screen, the router may reload. [CSCdi43297]

• TN3270 does not assume the appropriate 132 x 27 dimensions when set up as a Model 5 (MOD5) terminal. [CSCdi44497]

Wide-Area Networking

• The AIP card of the Cisco 7000 series routers does not map the virtual path identifier/virtual channel identifier (VPI/VCI) pair used in an ATM connection unless the router is initiating the switched virtual circuit. There are two symptoms: The first occurs when a new VPI/VCI is opened to the router from an ATM switch. In this case, the AIP does not pass this information to the RP and a reply to the incoming traffic is not sent back on the VPI/VCI just opened. Rather, the AIP card opens a new VPI/VCI and sends it back to the switch, creating unidirectional switched virtual circuits, which is inefficient. The second more serious symptom occurs when cells carrying packets, which are responses to those in a VPI/VCI pair opened by a sending router, return on a new, unidirectional VPI/VCI for which the router has no mapping. In this case, the incoming cells are missed, requiring retransmissions to complete the intended communications. The correct behavior is for the router to map all VPI/VCI pairs. [CSCdi32192]

• Pings across a BRI ISDN channel when using X.25 encapsulation. [CSCdi33844]

• When using Cisco 2500 series terminal servers with PPP, packets might pass after IPCP has completed negotiation, but before the interface is declared up. This might cause problems with applications that send out immediate requests, since the reponse may be dropped by the terminal server due to the interface being down. The workaround is to place a slight pause after IPCP has been negotiated and before sending out requests. [CSCdi37400]

• Because the ARP table has a VC to reach the IP address, the system will never try to place a call to it. So all packets for that IP address disappear down a black hole.

Workaround: save off the new configuration and reboot. [CSCdi40580]

• ISDN interfaces on an MBRI card might stop functioning, if the following error message is reported: "%SYS-3-HARIKARI: Process ISDN top-level routine exited..." To restart ISDN, reload the router. [CSCdi42578]

• LEX interfaces connected to a Channelized T1 NIM on a 4000/4500/4700 will cause the router to crash with a SegV exception.

LEX interfaces should not be used with the CT1 card prior to this release. [CSCdi42843]

• With encap lapb or encap X25 configured, sometimes the command lapb N1 xxx disappears from the working configuration and N-1 falls back to the default. This problem is most likely to occur after an interface reset or a reload. [CSCdi44422]

• Once the DLCI is assigned to a mulit-point FR port. Thought the DLCI has been removed from the port, it will not be added to anohter subinterface. [CSCdi44657]

• IPC comms may malfunction in IPC-capable cards during OIR events. [CSCdi44696]

• When running an MBRI using a 5ESS switchtype and using spids on multiple interfaces on the BRI 0 interface will work correctly. When doing a clear int on all the other interfaces the spid for BRI 0 will be sent out. This can be verified by running debug isdn q921 and debug isdn q931. There is no workaround. [CSCdi44727]

• The command show frame pvc can cause the router to reload with a bus error. [CSCdi45206]

• Under unknown conditions, debug ppp packet may cause the router to stop processing packets. [CSCdi45322]

• If an ATM interface goes down and back up because of a disruption on the fibres connecting it, pvc's defined for the interface remain inactive. Because this includes the signaling (qsaal) and ilmi pvc's, no svc's can be established, either.

The workaround is to do a shut/no shut on the interface. [CSCdi45544]

• This is a bug which can cause the ATM code to crash (potentially at boot-time) if you do not declare any PVCs but do declare an ARP Server. The workaround is to always declare the signalling VC before attempting to configure an ARP Server.

Note that if a PVC was present at any point after boot, and then deleted, and the ARP server was declared, this will not crash. But if it is written to NVRAM, there will be a crash on boot. [CSCdi45733]

• The parse command for frame-relay payload compression was disabling the parse-tree for all commands after it in the frame-relay map statement (effectively anything after the DLCI number that wasn't a payload compress command.)

This patch re-enables those commands. [CSCdi45797]

• If a PPP connection negotiates a peer IP address and comes Open, a 'neighbor' route (a Connected route with a metric of zero) will be added to the routing table unless another route to this address points to this interface. If a 'neighbor' route is added to the routing table, it may not be cleared when the PPP connection is dropped. There is no mechanism to remove this route. A workaround is to always configure a static route or subnet route to cover the peer's address thus avoiding the 'neighbor route' in the first place. [CSCdi45830]

• Under certain conditions XOT data might be delayed by the router. [CSCdi45992]

• Serial interface running with x25 encapsulation under heavy load can under some circumstances stop sending lapb RR's. The x25 switch is sending I frames untill the window is full. After 3 seconds when the switch sends a frame with the poll bit set, we reject the frame and the traffic continues. [CSCdi46024]

• NFS call-by-call support will only work with an isdn switctype of primary-4ess. To place a voice call configure the "dialer voice-call" as well as configuring the desired dialing plan. In order for the called party type to be set to international the number must be prefaced by 011.

The matrix is as follows:

NFS Data Voice International

SDN Yes Yes GSDN (Global SDN) MEGACOMM No Yes Yes ACCUNET Yes Yes Yes

Sample config:

isdn switch-type primary-4ess !

controller T1 1/0 framing esf linecode b8zs pri-group timeslots 1-24

interface Serial1/0:23 description This is the DMS D-chan 415-390-9503 ip address 6.1.1.3 255.255.255.0 encapsulation ppp no keepalive dialer map ip 6.1.1.1 name tommyjohn class sdnplan 14085770715 dialer map ip 6.1.1.2 name angus class megaplan 14085773775 dialer map ip 6.1.1.4 name angus class accuplan 14085773778 dialer-group 1 ppp authentication chap

map-class dialer sdnplan dialer outgoing sdn ! map-class dialer megaplan dialer voice-call dialer outgoing mega ! map-class dialer accuplan dialer outgoing accu ! [CSCdi46101]

• Under some unusual circumstance, 7000 may reload with bus error. [CSCdi46318]

• ISDN PRI routers connected to a 5ESS switch may not accept incoming calls if the Called Party Number IE contains an unknown type. This can occur during interoperabilty of a 5ESS and a Teleos switch. [CSCdi46675]

• A "Spurious Access" message may be seen when an interface goes up or down. There is no impact to this message. [CSCdi46813]

• If PPP received a Protocol-Reject from the remote, it will not allow that protocol to be used on an interface until a clear interface has been issued. Allow for the remote side to tell us a protocol is now allowed by that remote. [CSCdi46888]

11.0(3) Caveats/11.0(4) Modifications

This section describes possibly unexpected behavior by Release 11.0(3). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(3). For additional caveats applicable to Release 11.0(3), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(4).

AppleTalk

• When Appletalk fast-switching is enabled on a serial interface, packets are not forwarded. The interfaces combination that failed the switching tests are aip-fsip, aip-mip, hip-aip, eip-fsip and hip-eip. When fast-switching is disabled on the Serial interface, ping returns 100%.

Workaround:

no appletalk route-cache on serial interfaces. [CSCdi40486]

• Issuing the command show appletalk route network, where network is an AppleTalk proxy network, causes the system to halt. [CSCdi44235]

Basic System Services

• When the filenames were prompted for after entering a 'copy tftp flash' command, the whitespace was not being stripped off the destination filename (the source filename was being correctly stripped). This resulted in flash filenames with embedded spaces.

The fix involved moving the whitespace stripping to a common function that is called by both the source and destination filename read functions. [CSCdi17352]

• link/interface UPDOWN messages are displayed when an image is being netbooted. This is harmless. There is no workaround. [CSCdi36372]

• IP multicast fast switching does not work on the Cisco 7500 series routers. However, process-level IP multicast switching does work. All multicast interfaces on Cisco 7500 series routers should be configured to process switch IP multicast traffic using the interface configuration command no ip mroute-cache. [CSCdi39140]

• When a CHAP or PAP authenticated session disconnects while "aaa new-model" is configured, 48 bytes of memory will be lost until the next reload. [CSCdi40008]

• Cisco 2511 running XTACACS does not send an end record (xlogoff) when logging in as a second user id on the same connection. [CSCdi41291]

• DHCP proxy pooling does not work at all. The error message

% No address for remote. Check 'Peer Default IP Address a.b.c.d' % or configure IP pooling support.

will appear. [CSCdi42183]

• [CSCdi42241]

• Router may reload when trying to parse attribute-value pairs returned by a TACACS+ daemon. [CSCdi42385]

• When doing protocol translation, the IP address and username assigned to a user on a VTY is missing from the extended tacacs XTA_SLIPOFF message sent by the system. [CSCdi42554]

• Summer time epochs are not updated at the end of summer time. If a system stays up from before the end of one summer time period until the beginning of the next one, the system will not shift into summer time.

A workaround is to reissue the "clock timezone" command. [CSCdi43033]

• NTP may not synchronize immediately after system startup. It will synchronize after approximiately fifteen minutes in any case. There is no workaround to this problem. [CSCdi43035]

• AAA Accounting connections does not generate any accounting data for incoming connections (ie "reverse telnet"). [CSCdi43781]

• TTY Lines are not marked as "available" immediately after the modem hangs up. This happnes when the line modem hangs up while TACACS+ is trying to authenticate the line. [CSCdi43911]

• There is a small chance of the scheduler accidentally stopping all process timers, instead of just stopping its shadow timer for the process. This problem was introduced in 11.0(3.1). [CSCdi44034]

• The router may hang if a single process failes to update its event timers. [CSCdi44073]

DECnet

• Decnet Conversion should make validity checks. [CSCdi44859]

EXEC and Configuration Parser

• The async-bootp time-offset command does not allow negative offsets. [CSCdi40595]

• "reload" will cause a spurious access if the config needs saving but overwriting the config from a previous version is not confirmed. [CSCdi42918]

• The command privilege exec level 0 help does not show up in the configuration. [CSCdi44243]

IBM Connectivity

• SNMP queries of the CIP CLAW configuration MIB table (cipCardClawConfigTable) would also return non-CLAW channel device type confgiiuration objects. [CSCdi30997]

• When STUN is used to support virtual multi-dropped devices to an AS/400, unless CD is tied low to the AS/400, the line is reset when one multi-dropped device goes down. A new feature will be added to handle this in Cisco IOS. [CSCdi33572]

• DSPU sends TEST (P) in response to a NULL XID (P) on connect-ins, causing problems with certain LLC2 implementations. [CSCdi40809]

• The Cisco 4500 might reload if a TEST (F) or NULL XID (F) is received while the X.25 SVC for the QLLC connection is down. [CSCdi40851]

• The router's serial interface driver software occasionally drops SDLC frames, if the bit patterns are identical to HDLC LEX frames. Dropping occurs on interfaces using STUN-basic encapsulation with non-IBM SNA data traffic (for example, COMM10 CNS protocol). Note that there is no indication in the router when this problem occurs. The router does not increment the interface "drop" counter or the STUN "drop" counters. Detection is only possible with a media tracing tool. [CSCdi41558]

• SNMP queries of the CIP daughter board MIB table (cipCardDaughterBoardTable) would not return the record if the corresponding CIP interface was not configured with a valid channel device statement.

The SNMP MIB object for the the CIP interface online/offline status (cipCardDtrBrdOnline) was indicating the opposite of the true CIP interface status. [CSCdi41938]

• The Find Name NetBIOS broadcast is sent from the Token Ring interfaces even though the proxy-explorer and NetBIOS name caches are configured on the interface. To workaround, run back-level software. [CSCdi41972]

• Although routers with sufficient memory and CPU horsepower should support more than 1000 LLC2 sessions, the actual number of sessions allowed is erroneously limited to significantly fewer. [CSCdi42181]

• DLSW backup peers broken [CSCdi42215]

• CIPs with hardware revisions 4.0 and 4.1 are not compatible with the 7500 line of routers. This was not properly reflected in the output of the "show diagbus" command, which marked every CIP as "7500 compatible" regardless of its hardware revision. [CSCdi42373]

• In a FRAS configuration: if IOS on the TokenRing sends an XID to the FEP or 3172, and there is no response, IOS puts about 4K of memory into the 'Per Minute Jobs' under 'show proc memory'. This memory is never released back into the Free pool (memory leak). [CSCdi42475]

• LLC2 connections cannot be established to CSNA internal LANs configured on the RSP/75xx platforms

Problem introduced in 11.0(2.3) work-around is to use 11.0(2) or 11.0(2.2) [CSCdi42839]

• When displaying a topology with over 200 records (TG and NN), the show command will overwrite some memory at the end of the display buffer. Memory validation checks will detect and flag the error. [CSCdi42940]

• 2 global commands were added to add keepalive support.

bstun remote-peer-keepalive where n is the time period between keepalives in seconds

bstun keepalive-count where count is the number of keepalive periods to expire before declaring the TCP session down.

The keepalives can be viewed with debug bstun event

eg. BSTUN: Received Version Reply opcode from (all[2])172.16.12.2/1976 at 1360 BSTUN: Received Version Request opcode from (all[2])172.16.12.2/1976 at 1379 BSTUN: Received Version Reply opcode from (all[2])172.16.12.2/1976 at 1390 [CSCdi42960]

• Running QLLC/LLC2 conversion in the router would somtimes result in a memory leak during connection establishment. [CSCdi43119]

• A DLUR race condition occurs when deactivating a DLUR-DLUS pipe and DLUR is pending a BIND (RSP) from the downstream dependent LU. [CSCdi43157]

• The following commands may disappear from the router configuration if the connection does not become active:

sna start dspu start sna rsrb start dspu rsrb start [CSCdi43278]

• When an SDLLC or QLLC virtual ring is configured, explorers may be incorrectly forwarded to the interface corresponding to the 3rd ring in the routing information field (RIF). [CSCdi43378]

• When activating many dependent LUs (typically greater than 4 per PU), it is possible that the data destined for the DLUS will get queued in DLUR. When this happens and the downstream PU is inactivated, the queued data is made invalid. However, DLUR attempts to send the data to DLUS and may corrupt memory. This can result in a software crash. [CSCdi43486]

• when more than one vc is configured per subinterface for atm rfc 1483 transparent bridging, every other packet originating from fddi would have the mac address swapped in canonical order.

work around is to configure one atm vc per sub interface.

fixed in next release. [CSCdi43833]

• Large delays might be seen in sdlc session startup for PU 2.0 sessions if you are using FRAS or DLSw.

A workaround is to configure the router for sdllc to start the timer. The sdllc configuration can then be removed and the timer will continue on the 5 second dispatch interval. [CSCdi43856]

• On the 7500 platform, all IP packets from the CIP are processed switched, even though the interface has been configured for fast switching. [CSCdi43990]

• Occasionally a traceback is generated when a link is coming down because of receiving a DISC.ind. This does not seem to result in any lost function. [CSCdi44391]

• If an end-station is continuously connecting/disconnecting to DSPU, the router may begin losing memory in 2K blocks.

The router will not recover this memory without reload. [CSCdi44393]

• SRB bridged packets may be dropped when the router is configured for RSRB direct, and priority/custom queueing is enabled on the output Serial interface. A work-around is to disable priority/custom queueing on the Serial interface. [CSCdi44430]

• A message warning of low or exhausted stack space for the LLC2 Timer process will appear if the router is experiencing this problem. [CSCdi44511]

• The 11.1(1) version may experience a problem

%SCHED-3-STUCKTMR: Sleep w/expired timer 5B9E98, time 0x8A38 (23:05:32 ago). -Process= "BSTUN Background", ipl= 6, pid= 25

when bstun keepalives are configured on.

Do not run with bstun keepalives with 11.1(1).

A problem with not using keepalives is that line outages across the tunnel will not be detected and reported.

This problem will be fixed in version after 11.1(1.0) . [CSCdi44604]

• Packets cannot be fast switched from the CIP virtual interface to a TRIP interface when TRIP10-3 microcode is loaded with 11.0(3.2)

Work-around problem by loading TRIP10-2 microcode with 11.0(3.2) [CSCdi44617]

• When using the SNANM feature in non-Enterprise images, the "[no] sna rsrb start" command will work properly but will not appear in the configuration output and will not be written into NVRAM.

Work-around is to use an Enterprise image. [CSCdi44719]

Interfaces and Bridging

• Vines routing updates do not get bridged across token ring token ring interfaces configured for transparent bridging. [CSCdi37413]

• Any protocols that make use of multicast addressed frames (e.g. OSPF, RTMP) may loose its information due to the fact that the FDDI interface may stop receiving multicast addressed frames, which is usually detected only after a couple of hours the system is up and running. [CSCdi38185]

• When LANE is configured along with rfc1483 bridging on the same major interface (but different sub-interface), then adding a bridge-group in another sub-interface will cause the AIP to reset. All the VCs associated with LANE (Client, Server/BUS/Config, as the case may be) will reset. After the AIP reset completes, LANE will go back to the operational state. [CSCdi38662]

• At startup, 4000 family routers with MBRI interfaces can overflow ISDN processing queues resulting in errors messages indicating "NO MEMORY for ISDN L1 Q elements". [CSCdi38915]

• Transparent bridging may fail to forward packets on MultiBus Token Ring interfaces or MCI serial interfaces on the AGS. [CSCdi39644]

• TN3270 and TELNET user sessions can be dropped unexpectedly from the Cisco 2509 and Cisco 2511 access server asynchronous ports, because of an inactivity timeout. [CSCdi41542]

• Copan class of routers (2509, 2510, 2511, 2512) don't output BREAK correctly out of the async tty lines. [CSCdi42050]

• For a given bridge table entry, bridging may fail to forward packets to one destination, although packets to other destinations will be properly forwarded. This can be seen by a show bridge nnnn.nnnn.nnnn command. The TX count increments, but the RX count stays constant. The workaround is to issue a clear bridge command. [CSCdi42445]

• On a Cisco 4500 router bridging DECnet, certain stations might be unable to establish connectivity over transparent bridging, because some DLC frames are not forwarded when they should be. [CSCdi42690]

• In very rare cases, it's possible for AGS style MCI ethernet interfaces to be classified incorrectly as fast ethernet interfaces. [CSCdi42751]

• When using SLIP or PPP on the AUX port, the CPU utilization of the router is higher than it should be. [CSCdi42894]

• Fast switching fails over mip. Pings fail when mip is configured for fast switching, they are succesfull when removed. [CSCdi43173]

• Hardware flow control may be inadvertently disabled on the Cisco 2509, 2510, 2511 and 2512 routers' asynchronous ports after issuing a configure network or a copy tftp running-config command. To restore flow control, issue the line configuration command flowcontrol hardware on all lines. [CSCdi43306]

• The Cisco 4000 series routers with FDDI network interface modules (NIMs) might reload under certain stressful conditions. [CSCdi43618]

• When configuring SLIP or PPP framing on the auxilliary port of a router, "Low memory modified by Input Helper" messages erroneously appear in the system error log. [CSCdi43970]

• Enabling SSE for IP might cause the system to crash. The workaround is to perform the no ip route-cache sse command. [CSCdi44414]

• tbridging where serial links are involved w/ the RSP is broken. mac addresses in the bridge table show up off by 4 bytes.

no workaround.

fixed in next release. [CSCdi44835]

IP Routing Protocols

• A router running OSPF may restart with a bus error under extremely rare conditions. [CSCdi25568]

• When a standby ip address for HSRP is changed, the new MAC address associated with the IP address will not enter the ARP table until a clear arp is done. In addition, if the standby address is removed from an interface, the arp entry will not be removed and the router may still respond to pings sent to the standby address. [CSCdi26336]

• When EIGRP split horoizon is disabled on the 7000 PRI interface, the routing updates are not properly sent to the remote routers causing routes to be removed. When split horizon is enabled, routing is OK. [CSCdi32436]

• RIP doesn't immediately flush routes with a higher metric value when better routes are available. [CSCdi37812]

• Routers running 10.2 or higher fail to add an entry to the ARP cache when they receive a valid HP probe VNA reply. Possible workarounds: configure static ARP entries. If not absolutely necessary, don't use HP probe but use ARPA or SNAP encapsulation. [CSCdi41952]

• Under some rare circumstances, the router may reload while fastswitching over a DDR interface. [CSCdi42068]

• The show ip bgp net mask subnets command may display BGP entries that do not match the selected criteria. This is purely a cosmetic problem. [CSCdi42970]

• There is no way for an administrator to specify the ip source address used in TFTP requestion from a router. A new command ip tftp source-interface interface should be added. [CSCdi43195]

• The count of IP packets which violated an access list but which were not kept because the "Account Threshold" was exceeded is never initialized or reset. As a result, spurious values may be displayed in this field in the output from "show ip accounting access-violations". [CSCdi43342]

• 7000 router restarts with IP multcasting [CSCdi43368]

• The distribute-list command should allow extended access lists for outbound filtering. [CSCdi43559]

• Policy-based routing cannot be enabled on subinterfaces. [CSCdi43739]

• MAC Burned-in-addresses (BIA) can sometimes replace the HSRP group MAC address for the HSRP IP address in the ARP table. [CSCdi43875]

• Under unknown conditions, 7000s with an SSP will incorrectly generate a spurious %SYS-2-GETBUF error message. [CSCdi44709]

• Eigrp Scheduler not working properly. Work around is to use managed timers. [CSCdi44810]

ISO CLNS

• IS-IS, and NLSP may generate CPU HOG messages. [CSCdi39906]

• When clns routing is enabled on an X.25 serial interface, and you try to statically configure a CLNS IS-NEIGHBOR or CLNS ES-NEIGHBOR before defining the X25 map command, the configurator discards the commands without generating error message. [CSCdi40640]

• Open System Interconnection (OSI) end system adjacencies sometimes do not appear in an IS-IS protocol Level-1 pseudonode LSP. This is especially likely to occur when there is only one router on the LAN containing the end systems. [CSCdi43236]

LAT

• The rating for LAT services is incorrect when more than 255 virtual terminals (vtys) are used. [CSCdi44088]

Novell IPX, XNS, and Apollo Domain

• The global configuration command

ipx broadcast-fastswitching

when enabled will permit IPX directed broadcast packets to be fastswitched. (A directed broadcast is one with a network layer destination address of the form, net.ffff.ffff.ffff) This may be useful in certain broadcast-based applications that rely on helpering.

The default setting for this command is off. The default behavior is to always process-switch these packets.

Note that eligible directed broadcast packets are never autonomous switched, even if autonomous switching is enabled on the output interface. Also note that routing and service updates are always exempted from this treatment. [CSCdi37234]

• In 10.3 maximum-paths was reduced to a maximum of 4 equal cost paths, due to NLSP overhead. This restriction should not be made if NLSP is not configured. [CSCdi42340]

• 'ipx router ?' erroneously displays 'isis' as one of the supported protocols in the help menu. [CSCdi42574]

• IPX fastswitching over ATM/LANE does not work properly. [CSCdi42852]

• The ipx routing command does not enable the IPX RIP protocol if no ipx routing is configured. The workaround is to not configure no ipx routing. [CSCdi42953]

• A spurious "ipx router rip" may show in the configuration file after disabling ipx on all interfaces and removing the configuration of other ipx features. This command will not show after a minute or two and has no adverse side effects.

The ipx internal-network command may appear in the configuration file for a short while after removing the ipx internal-network from the configuration. [CSCdi43211]

• When using IPXWAN unnumbered the PPP control protocol IPXCP my attempt to negotitate a link ipx network using a network number from an interface where ipx was recently disabled. This appears to happen the most if the ipx internal-network number is removed and then reconfigured, this may give the appearence of ipxcp using the internal-network number, and the internal network number may disappear from the routing table. [CSCdi43213]

Protocol Translation

• For incoming PAD connections, the Protocol Translator uses a default PAD profile to set the remote X.3 PAD paramaters unless a profile script is defined in the translate command. To override the default PAD profile the PT uses, create a PAD profile script named "default" by using the X29 profile global configuration command:

x29 profile default parameter:value [parameter:value]

Where "default" is the name of the default PAD profile script and the parameter:value is the X.3 PAD parameter number and value separated by a colon. [CSCdi14369]

• The global "translate" command keyword options are now shown in lower case. [CSCdi41300]

TCP/IP Host-Mode Services

• Fast retransmit scheme is incorporated into the TCP process. [CSCdi39128]

• BOOTP attempts may fail over an asynchronous VTY PPP connection when async-bootp commands are used. This is because of an incorrect User Datagram Protocol (UDP) checksum on the BOOTP reply. [CSCdi41168]

• IP helper address doesn't work over un-numbered interfaces. [CSCdi43791]

VINES

• When adding a new X.25 map to an existing interface and running VINES with SRTP enabled, the router will request full routing updates from all VCs on the interface, not just the new VC. This can cause high CPU and link utilitization on the affected interface. [CSCdi38892]

• Workstations on a Vines serverless segment connecting through a router running IOS 10.3 will experience delays in accessing StreetTalk services. The router does not respond to StreetTalk requests directed to itself. The workstation will direct the requests elsewhere after a time-out period. [CSCdi40757]

• The system may halt unexpectedly after issuing a clear vines neighbor command. [CSCdi42431]

• Cisco routers will reply to NetRPC Searches for the Server Service with a reliable IPC data packet instead of an unreliable IPC datagram. This can add a small amount of additional traffic to the networks where the responses are sent. [CSCdi42851]

• If, while in suppression, the metric for a route changes, the suppression interval should be restarted. [CSCdi43012]

• When a route with a better metric is learned via SRTP from a neighbor different from the current neighbor, the route will unnecessarily enter suppression. This can cause an instabilities in the network. [CSCdi43112]

• Under some circumstances, the router will send updates for Vines networks that are not reachable. [CSCdi44038]

• Configuring a X25 static map for Vines can cause the system to halt. [CSCdi44082]

• A SRTP update sent in response to a client request for specific networks will omit the last network specified in the request. [CSCdi44517]

• show vines access may unexpectedly halt the system when displaying very long access lists entries. [CSCdi44873]

Wide-Area Networking

• This ddts fixes two things:

1) show atm interface x/0 does not always display active VCCs correctly.

2) show atm vc and write term used to not show inactive PVCs. E.g. if a user configures a PVC that is in the inactive state, user will not see the PVC in either show atm vc, or write term This has caused confusions to some users.

We now change to let show atm vc and write term display any PVC, as long as long the PVC is still being configured and we add a field "Status" to the output of the show atm vc command to differentiate whether a PVC being displayed is an ACTIVE one or an INACTIVE one. [CSCdi31527]

• Changing the input or output hold-queues for a BRI interface does not change the individual channel queue depths. [CSCdi32869]

• Ping and telnet fail over an X.25 link configured for transparent bridging. [CSCdi36544]

• When a Called Line Address Modified (CLAM) facility is encoded in an X.25 Call Confirm packet, a subsequent Clear issued by the router for that VC will encode the VC addresses without encoding a CLAM facility. This is contrary to the specification for Clear packet encoding. [CSCdi39381]

• The output of show atm vc xx includes a line about "Destination NSAP." It is actually showing the Remote NSAP. This distinction is only meaningful on remotely originated calls. [CSCdi39637]

• Currently there is no way to see the idle time remaining on an ATM SVC before it is disconnected. [CSCdi39654]

• The frame relay map can become stuck in a state if it has been staticly configured and then taken out, so that we will not inverse-arp for the DLCI after removal. [CSCdi40866]

• Clearing X.25 virtual circuits on an interface using "clear x25" command can cause a spurious memory access on the c4500 platform. [CSCdi40878]

• show isdn status only allows dsl values up to 9. It should support values up to 15. [CSCdi42110]

• Routers with an ISDN BRI interface might have problems with B channels, or might run out of call control blocks, because B channels might be assigned that are already in use. The router rejects these calls with a "Channel Unacceptable" cause. If the router runs out of call control blocks, severe errors will likely occur. [CSCdi42123]

• ISDN routers with a PRI or BRI interface might crash when receiving a Layer 3 Status Enquiry message with a "Display IE" in the message. [CSCdi42382]

• "ATM failed to create VC" errors can occur because an ATM switch assigns VPI/VCI numbers outside the ranges that can be accepted by the router. The workaround is to manually set the VPI/VCI space on the switch. [CSCdi42518]

• ISDN routers may have trouble placing additional calls and may run out of ISDN Call Control Blocks (CCBs). [CSCdi42565]

• If you enter a dialer string dial-string command on an ISDN interface instead of a dialer map command, the router may crash. [CSCdi42764]

• Sometimes, when the hardware interface on which a lane server-bus is running is disabled with "shut" and then later enabled again with "no shut", the lane server-bus remains down, rather than restarting as it should.

The workaround is to do "no lane server-bus" followed by "lane server-bus ...." on the subinterface where the server-bus is running. [CSCdi42765]

• With sub-interfaces defined on ATM interfaces (AIP) and using the command atm pvc vcd vpi vci aal5mux ip under each sub-interface, the PVCs may not show up in the active configuration (write t) after reload, thus causing the PVCs not to come up. The only way to get the PVCs up is to issue a config mem commamd. [CSCdi43387]

• The 4500 will fail when the pri controller configuration is removed. This failure will be seen as a 'SegV Exception'. It will not occur if the interface has been shutdown since the router was last rebooted. A workaround, if the pri controller configuration must be removed, is to first shutdown the interface, reboot the router, and then remove the configuration. [CSCdi43511]

• If the remote end of the connection (the peer) attempts to authenticate with PAP, and no authentication of the peer is attempted, the authentication will appear to succeed, but none of the NCPs (such as IPCP or IPXCP) will begin negotiation. The peer will think the link is up. The local end will think the link is down. [CSCdi43514]

• Removing the connector from an ATM interface on a 7000 series router with IP configured on that atm interface may lead to a crash. [CSCdi43519]

• Once the ATM interface is up and has established the SVCs, then a clear interface atm x/y is issued . The router then tries to re-establish VCs. At this point the atm switch sens a status request to the router. The router ignores this status request. After 4 seconds the switch then times out the status request and issues call releases. The router responds to the call release with a code of zero. [CSCdi43528]

• Certain configurations of IP Address Pooling commands will cause IPCP to reject an IP Address suggested by the peer. Typically, no peer address will be negotiated and IP connectivity may be broken. This will occur and debug statements will corroborate that IP Address Pooling is involved even if no 'ip address-pool' or 'peer default ip address' statements have been entered.

This problem can be avoided if each PPP interface is configured correctly for a peer address, or for address pooling, or with pooling explicitly disabled.

The commands to configure pooling (local or dhcp) are site specific.

If a fixed peer address is acceptable, it can be set with:

name(config-if)#peer default ip address a.b.c.d

where a.b.c.d is the IP network address of the peer. Note that this command replaces the command:

name(config-if)#async default ip address a.b.c.d

for async interfaces, but applies to all PPP and SLIP interfaces including ISDN interfaces.

Pooling can be explicitly disabled on an interface with the command:

name(config-if)#no peer default ip address

This command will have no other effect and can be replaced later with an appropriate address pooling configuration. [CSCdi43677]

• Service provider images failed to include X.25. [CSCdi43711]

• Change for ISDN BRI approval of NET3 switchtype for Taiwain. [CSCdi43785]

• With Frame-Relay IP TCP Header-Compression enabled on the appropriate ports, tcp sessions across a frame-relay link produce unintended results. The problems have manifested themselves as spontaneous router reload, or hung sessions.

Workaround: Turn header compression off. [CSCdi43927]

• The router reloads if the interface subcommand asynch mode dedicated is configured for a Group-Async Interface. [CSCdi44030]

• When an ATM interface is changed from "shut" to "no shut", LANE servers configured on subinterfaces remain down, rather than becoming operational.

The workaround is to repeat the "lane server-bus" command on each subinterface after doing the "no shut" on the main interface. [CSCdi44330]

• ISDN BRI routers connected to a 5ESS switch can have calls fail. This can occur if the line is configured for voice and data. The show isdn memory will show that the number of NLCB blocks has reached it's maximum. [CSCdi44348]

• If the PPP peer attempts to negotiate VJ Header Compression with more than slots than are configured, the router should Nak the IPCP Configure Request and suggest an acceptable slot value. Instead, a malformed IPCP Configure Reject is generated that includes an IPCP Addresses option (Option #1) and a malformed option. The trace of the packet exchange (using 'debug ppp negotiate') also shows a 'bad CI length' message. [CSCdi44404]

• ISDN PRI changes for NET5 switchtype for Italian homologation. Includes changes to handle Restart messages for the various European switches. [CSCdi44526]

11.0(2) Caveats/11.0(3) Modifications

This section describes possibly unexpected behavior by Release 11.0(2). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(2). For additional caveats applicable to Release 11.0(2), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(3).

AppleTalk

• IPTalk clients running CAP cannot start up because a nonstandard NBP packet generated by the client is not forwarded by the system. There is no workaround. [CSCdi39096]

• Topology:

Net10 Net20 Creator ----- Router 1 ----- Member | | -- Router 2 --

Creator creates a group. Member joins group. There will be 2 forwarding paths since since Net10 is local to both routers.

Workaround is to avoid this topology if possible.

The correct behaviour is to only have one path even when the route is locally connected on the routers. [CSCdi39756]

• Acknowledge outgoing nbp packets as (un)interesting packets when nbp filters are used with dialer lists. This allows the dialer to determine when to place a call. [CSCdi40454]

• Using show appletalk route to display information about a connected route may result in a spurious access. There is no operational impact to the system. [CSCdi41913]

Basic System Services

• Undefining a tacacs-server host and then defining a new one when there are oustanding requests still pending from the first host may cause a system reload. [CSCdi36726]

• On AGS+, 7000, and 7500 platforms, the command buffers huge size [size] has no effect. [CSCdi38912]

• User information is now available for PPP users, even when no authentication is performed. We still don't know who the user is, but we can now pass other information (such as port name and remote_address ...) along with authorization and accounting messages. [CSCdi40013]

• When performing SNMP queries of a router using the RSP2 board, the router may reset with error message "System restarted by abort". [CSCdi40186]

• There are several possible situations that can cause a reload when using AAA (TACACS+) accounting. Also, when using IP address negotiation between IPCP and AAA, IPCP would not use addresses provided by AAA. [CSCdi40334]

• Fair queuing doesn't work on ISDN interfaces. [CSCdi40357]

• Failure to netboot found in version 10.3(5) IOS. [CSCdi40422]

• When using Protocol Translation for Virtual Async connections, The system may restart with : System was restarted by error - Illegal Instruction, PC 0x0. [CSCdi40681]

• AAA Accounting records for rlogin connections do not contain attribute/value pairs for protocol and remote address. [CSCdi40773]

• AAA Accounting for connections does not contain an attribute/value pair indicating the remote tcp port being connected to. (However, this information can be derived from the "cmd" attribute value.) [CSCdi40774]

• Newer boards, such as the SMIP and SSIP, may cause a SEGV exception on an RSP when using an image that does not include the proper support. [CSCdi40862]

• The reload command has been modified to allow for the scheduling of a reload in the future. [CSCdi40898]

• In some configurations including a Loopback interface, memory will be consumed by packets erroneously queued to that interface. As packets are queued to the Loopback interface, free memory dwindles until the router crashes because it has no free memory.

The only workaround is to delete the Loopback interface. [CSCdi41281]

• Removing enable secrets with the "no enable secret" config command would fail and print an error when specifying explicit privilege levels. [CSCdi41368]

• When DSPU or DLSw+ is configured to accept connections across QLLC/X.25, the router will reload when the second QLLC/X.25 connection becomes active. [CSCdi41826]

• The show buffers command will display some counters as if they were signed numbers when they are in fact unsigned. [CSCdi41857]

• If an Interface Processor fails and becomes "disabled" as seen in the "show diag" command's output, it may not restart automatically. In addition, if it is EOIR'd from the slot, the interface counts seen in the "show version" command's output may be incorrect and the configuration information may be lost for the reinsertion of the same Interface Processor type. [CSCdi41907]

• Not all OEM vendor names are printed correctly for the "show version" output. [CSCdi42122]

• With AAA (and TACACS+) a privilege level of zero could not be specified for a user, even though zero is a valid level. [CSCdi42490]

• An off by one error may cause a system reload when running BGP if thousands of withdrawn routes are sent out as a part a BGP update message. [CSCdi42495]

• [CSCdi42575]

EXEC and Configuration Parser

• Port numbers above 32767 are written as negative numbers to nvram when using the ip host configuration command. [CSCdi41005]

IBM Connectivity

• The SNA packet is lost during fragmentation if no buffer is available to store the fragmented packet. The SNA application will recover and resend the packet without disconnecting the session. [CSCdi27730]

• A router configured for IBM automatic spanning tree with the default BPDU interval of 2 seconds may instead send BPDU's at 1 second intervals. However, the correct spanning tree will still be formed. [CSCdi35149]

• Netbios access-list host doesnt look at name recognized frames. [CSCdi36649]

• With DLSW configured, changing the bridging protocol caused the router to be restarted by error due to an Illegal Instruction. [CSCdi37823]

• With source- route bridging configured (local only), the router occasionally appends random data to the end of LLC2 RR frames being bridged through the router. Some LLC2 devices will reject these padded frames, which causes sessions to be lost. [CSCdi38486]

• Release-note:

The bridge number on the DSPU RSRB statement was originally hard-coded to a 1. Under certain conditions, other vendors routers will modify the RIF based on whether it contains a bridge number 1. [CSCdi38628]

• For using RSRB direct over Frame Relay, MTU size of the frame-relay interface shoule be greater than 2104 (MAXDGRAM_RSRB). If its less than this value, the configuration is now allowed but packet is dropped if its size is greater than the MTU size of the interface.

Set the MTU size of the frame-relay interface to be greater than the largest-frame size of RSRB. [CSCdi38633]

• RSRB Does not work correctly over fair queued interfaces.

Fair Queuing should be disabled on serial interfaces used by RSRB. [CSCdi39023]

• The following message may be received when using the RSRB local-ack feature: %SYS-2-LINKED: Bad p_enqueue of 97E950 in queue 8EA038

The Bad p_enqueue message appears when RSRB local-ack discards packets during normal LLC2 protocol but does not discard the packet correctly.

The Bad p_enqueue message does not indicate a problem in the RSRB network but the side-effect of displaying this message multiple times may affect router performance. [CSCdi39706]

• dlsw sends test_cmds to sap 04 instead of of sap 00 if the cache is stale. [CSCdi39850]

• Output from "debug cls message" does not decode all error codes. [CSCdi40288]

• When FRAS enables and disables the rsrb virtual port for backup, errors are being reported in the "debug cls error" output. When the virtual ring is created, a "virtual ring already exists" error is sometimes reported. When the virtual ring is supposed to be deleted, an "unknown port" error is reported. When the backup activated again, an "already exists" error is reported.

This problem is relatively harmless. It can waste some memory when in the normal (backup disabled) state since the data structures for the virtual ring are not getting cleaned up. [CSCdi40289]

• In environments where there is a delay between the time the router is powered on, and the time that the frame relay LMI reports that the PVC is ACTIVE, the FRAS feature may switch over to it's backup link.

A delay mechanism is to be introduced that will retry the frame relay link a configured number of times before switching over to the backup interface. [CSCdi40292]

• CMNS will use an incorrect mac address when trying to open a LLC2 connection to a host running DECnet phase iV. The current workaround is to have the DECnet host opening the LLC2 connection to the router. [CSCdi40639]

• Local and Remote ring number can now be between 1 and 4095. Before they were limited between 1 and 255. [CSCdi41283]

• An unsolicited debug message may be received from DSPU even though no debugging is enabled.

The format of this unsolicited message is as follows: LS hostname RNR sent to host

This message does not indicate any problem and may occur during normal data transfer by DSPU. [CSCdi41646]

• When DSPU over QLLC is configured, the router may experience loss of memory due to the fragmentation of large frame into several smaller frames.

The work-around for this memory leak is to ensure the MAXDATA for both the upstream and downstream links are set at a maximum of 256 bytes.

If data lengths are 256 bytes or less, data frames will not require fragmentation by QLLC and memory leak should not occur. [CSCdi41663]

• After you configure a LAN Network Manager (LNM) PC with a bridge definition that contains the target interface MAC addresses on the router, watch for the following behavior. If a no source-bridge local-ring bridge-number target-ring command is entered for one of the interfaces previously configured on the LNM PC and a Link Bridge command is then entered on the LNM PC, the router halts with a bus error indication. The only workaround is to ensure that no source-bridge local-ring bridge-number target-ring commands are not executed on the router after you define the target LNM server bridge on the LNM PC. [CSCdi41997]

• SNANM and/or DSPU commands are not accepted for configuration of a Frame-Relay sub-interface.

The SNANM and/or DSPU commands are accepted for configuration of a Frame-Relay primary interface. [CSCdi42171]

• SRB packets are not bridged to/from the CSNA internal LANs when DLSw+ peers are configured with FST/direct encapsulation.

Work-around is to configure DLSw+ peers for TCP encapsulation. [CSCdi42462]

Interfaces and Bridging

• An asynchronous interface will not drop DTR when a dedicated asynchronous interface is configured in the shutdown state. The workaround is to configure modem dtr-active on the line. [CSCdi32952]

• When Current Routing and Bridging is enabled on a high-end box, Decnet packets received on a bridging fddi interface could be mistakenly routed if Decnet routing is enabled on other interfaces. [CSCdi37174]

• VINES ping fails over transparent bridging with the following configurations: Ethernet-FDDI Ethernet-FDDI-Ethernet FDDI-serial-FDDI with serial encapsulations HDLC, PPP, FR-EITF, Frame Relay FDDI-HSSI-FDDI with serial encapsulations HDLC, PPP, FR-EITF, Frame Relay DEC and IEEE with serial encapsulations HDLC, PPP, FR-EITF, Frame Relay There are no failures with SMDS or X25. [CSCdi37994]

• If the serial interface on the C1005 router is configured with "encapsulation atm-dxi", the following error message appears:

%QUICC-3-BADENCAP: Unit 0, bad encapsulation in idb->enctype = 0x22

This is because the C1005 does not support the atm-dxi encapsulation, and it should not be configured on the serial interface. [CSCdi39433]

• Weighted fair queueing is incompatible with transparent bridging on High-Level Data Link Control (HDLC), Frame Relay, and ATM serial interfaces. The default configuration of weighted fair queuing causes bridge flooding to fail and may produce the following error messages:

%SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=hex-value, count=number -Traceback= list-of-hex-values %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=hex-value, count=number -Traceback= list-of-hex-values

Weighted fair queueing cannot be "deconfigured" on serial lines in Release 11.0(1) software due to another problem, so transparent bridging should not be configured on HDLC, Frame Relay, or ATM serial interfaces. On non-serial interfaces, the same problem will occur if you explicitly configure weighted fair queueing. [CSCdi39516]

• In the Show line N command, the dispatch timeout is shown in the peculiar format: hours:minutes:seconds.milliseconds. The milliseconds value is not a proper decimal fraction (ie 0.80 instead of 0.080) [CSCdi39673]

• When the "clear couters Async X" command is executed, the overrun/overflow/ crc error counters are not zeroed. [CSCdi40167]

• the transparent bridging code can report giants coming off an atm interface. situations where this can occur are when routers are configured w/ non-hdlc encaps on the serial links, or when priority queuing is configured.

the work around is to configure the serial interfaces for hdlc or not forcing process level transparent bridging.

fixed in the next release. [CSCdi40560]

• While bridging on a router with an RSP2 processor from ethernet to ATM to ethernet, if a MAC address filter is enabled, IPX, IP, Appletalk, and XNS will fail to be forwarded. This happens with IEEE and DEC spanning tree. [CSCdi40658]

• if atm or frame relay is used in a tbridging environment, decnet and clns packets were not being flooded correctly. no work around. fixed in next release. [CSCdi40861]

• Cisco 2509 through Cisco 2512 devices' asynchronous lines stop accepting input under certain conditions. One of these conditions occurs when a user connected to a LAT host types a Control-C character. A clear line x or a change to the line parameters will cause the line to start accepting input again. [CSCdi40994]

• 2500 token ring interface will not try to reinsert into token ring hub after one failed attempt. [CSCdi41499]

• Under rare circumstances, the IP fast switching cache can contain overlapping prefixes. If the SSE manager detects this, it will disable SSE switching. This was introduced in CSCdi39840. [CSCdi41807]

• Ethernet loopback packets (type 0x9000) are not bridged but rather are discarded by type. This will cause applications that use end-to-end loopbacks to fail in a bridged network. [CSCdi41850]

IP Routing Protocols

• The system allows the assignment of the same IP address to multiple X.25 interfaces on the same system. [CSCdi15734]

• System reloads when OSPF LSA is sent in send_ls_update. [CSCdi20080]

• Variance and traffic share on eigrp not working. [CSCdi34629]

• Major network summary not sent in RIP/IGRP out unnumbered interface. [CSCdi35158]

• EIGRP neighbor tables do not reflect correct uptime. Entries show "never" in the uptime colume. Must manually clear ip-eigrp neighbor from table to start timer on uptime. [CSCdi36672]

• OSPF does not retransmit new LSAs when an ACK is received, rather than waiting the full retransmission interval. This slows down database syncronization. [CSCdi39931]

• EIGRP displays incorrect redistributed routes in topology table in version 10.2 IOS. [CSCdi40200]

• The command "ip mroute" will fail to do a recursive lookup of a route to determine the correct RPF interface. The use of the PIM neighbor will still work. [CSCdi40341]

• When ip ospf network broadcast is configured on wan interface like frame-relay, and ip ospf hello-interval command is used to set the interval to 30, then the hello-interval is not retained upon reload. Workaround is not to set hello-interval to 30 in this case. [CSCdi40729]

• If PIM sparse-mode is enabled on an ethernet interface, all incoming ISIS packets on that interface are lost (not received). Disabling PIM sparse-mode on the interface cures the problem. [CSCdi40951]

• Modify OSPF flooding algorithm by sending back its most recent copy of lsa when received old one. It speeds up recovery from route flapping. [CSCdi40976]

• Packets generated by the router which are forwarded based on local IP policy are not correctly forwarded. Debugging of policy routing is overly difficult. [CSCdi41042]

• If the active router supresses a proxy ARP response due to split-horizon reasoning, and the standby router has the best path (and would provide a proxy ARP response in a non-HSRP scenario), then we fail to provide the expected proxy ARP response with HSRP. [CSCdi41163]

• The show ip route command may display garbage characters if used with ISIS, for example:

* 144.228.10.1, from 144.228.10.1, via Hssi1/0^AxT

There is no workaround to this problem. It is purely cosmetic in nature. [CSCdi41383]

• On an SSE equipped 7000 routing IP with IP fast switching and SSE switching enabled, if a route is configured to use parallel paths, and one of the paths is removed due to a local interface flap, the SSE will suspend operation and the system will revert to fast switching. [CSCdi41527]

• If a loopback or tunnel interface is destroyed via the no tunnel or no loopback commands and that interface has an IP address present before destruction, the router does not properly pass through packets destined for that IP address. A workarround is to remove the IP address on the interface before destroying it. [CSCdi41543]

• We report the pps (packet/second) and kbps (Kbits/second) measured during the last sampling period of 1 full second. [CSCdi41573]

• OSPF is not able to flood huge router LSA (bigger than 1456 bytes) correctly. The huge router LSA is generated when there is more than hundred OSPF interfaces or there is more than hundred secondary addresses defined on the OSPF interfaces. The maximum number of interfaces before the problem hits varies, it depends on the type of interfaces. In the worst case, 60 point-to-point OSPF interfaces is sufficient to cause the problem. At the worst, this huge LSA can cause the router to restart. This fix enables the router to process huge LSA correctly. Note that all routers in the OSPF area that need to process huge LSA must be upgraded with version containing the fix; Routers running versions without this fix could restart upon receiving the huge LSA. [CSCdi41883]

• Helper addresses will not work on IP unnumbered interfaces. This is a problem for network protocols that require broadcast forwarding on dialup, such as Microsoft Networking over TCP/IP. Workaround is to configure an appropriate ip broadcast-address in addition to the ip helper-address on the async interface in order to facilitate forwarding. [CSCdi42154]

• When pinging a non-existant host, arp table entries for that host, with a mac address of 00:00:00:00:00:00, are reported via snmp in the atTable and the ipNetToMediaTable as defined in mib-2. [CSCdi42267]

• Under uncommon circumstances, the IP fast switching cache can become inconsistent. [CSCdi42366]

• Disabling SSE switching on an interface can leave cache entries in the SSE. Packets will continue to be switched based on these cache entries. A workaround is to first shutdown the interface, then disable the SSE. Another workaround is to clear the SSE after disabling it. [CSCdi42444]

• If a ppp session on an ISDN interface has installed a neighbor route in the routing table and then the routing table is cleared, the neighbor route will not be re-installed although the connection will remain undisturbed. [CSCdi42602]

• Remove the "ip cache-ager-interval" and "ip cache-invalidate-delay" commands. These esoteric tuning knobs are no longer necessary nor supported. [CSCdi42608]

ISO CLNS

• When running ISO-IGRP and a CLNS route goes in holddown and gets deleted, a memory leak of 128 bytes will occur. This can happen very frequently in a normal network. The final result will be that the ISO-IGRP process will use most RAM memory, and the router will become unreachable and stops functioning. A reboot is the only way to get the router going again. [CSCdi39191]

• CLNS packets which should be fast switched from an AIP to a FIP are switched incorrectly. [CSCdi40977]

• CLNS Error packets may contain invalid information in the data field, or they may not be sent at all. There is no workaround to this problem. [CSCdi41968]

Novell IPX, XNS, and Apollo Domain

• If NLSP is disabled, a host name entry for the system will be left in the name cache. There is no workaround to this problem. [CSCdi31507]

• NLSP will not generate a WAN pseudonode (thus advertising received RIP routes) if NLSP is configured on a WAN interface but the router at the other end is RIP-only.

The workaround is to disable NLSP on the interface. [CSCdi33185]

• If the interface is configured with an encapsulation that is not the same as default, there is no way to reverse it back to the default using the command no ipx encapsulation The workaround is to remove the ipx network number and then reconfigure the ipx network number on the interface. [CSCdi37380]

• Most NLSP options cannot be configured on subinterfaces.

There is no workaround to this problem. [CSCdi38152]

• If NLSP is configured on one end of a point-to-point link but not the other, the router configured for NLSP does not redistribute the RIP routes received when RIP compatibility mode is automatically started. A workaround is to disable NLSP on the link. [CSCdi39102]

• Under some circumstances, ISIS and NLSP link state packets may stop being transmitted on an interface. There is no workaround to this problem. [CSCdi39582]

• Issuing the "no ipx router rip" command causes the "IPX RIP" process to run continuously in background (about 6% CPU load). This condition appears to be corrected by issuing the "ipx router rip" command. [CSCdi40568]

• 'show ipx traffic' command ignores the terminal length setting using the command 'term len xx' and displays all information at once. [CSCdi40901]

• If NLSP is configured and deconfigured, 'ipx routing' should not resurrect the command 'ipx router nlsp' and spawn its processes. [CSCdi41016]

• When a floating static route is defined, the same route learned via NLSP do not override the user-defined floating static route. [CSCdi41138]

• When NLSP is turned off by either doing 'no ipx router nlsp' or 'no ipx routing', some memories are not released to the system. [CSCdi41213]

• When a learned route entry goes away on an interface which is also used as the IPX default route path and a routed packet to the previously learned network is sent over this interface while the learned network is in hold down a system restart may occur. [CSCdi41272]

• Doing 'no ipx network xx' and then 'shutdown' on the interface sometimes may leave the connected route as secondary connected. [CSCdi41319]

• XNS fastswitching is not enabled by default. An initialization routine is not properly initializing fastswitching. [CSCdi41365]

• If NLSP is configured, the router may create multiple path via the same interface to its neighbors internal network if its maximum path is set greater than 1. [CSCdi41778]

• 'clear ipx route number' wipes out the static route in the configuration if the route that is being cleared is a static route. [CSCdi41898]

• On interfaces using ipx secondaries the ipx triggered delay commands show up for each secondary as well as the primary, they should only appear once per primary interface. Triggered delays if not explicitly set should follow any explicit normal RIP/SAP delays set, they are not they are using the default values. [CSCdi42278]

• Configuring IPX on the the router when the router has low memory, might cause the command shell to crash. [CSCdi42363]

Protocol Translation

• The "host-name" Telnet/TCP outgoing option stores the hostname in the "translate" command rather than its IP address allowing a single IP address to map onto multiple IP destinations.

The following configuration translates incoming PAD connections to multiple Telnet/TCP destinations offered by the IP hostname shadow.

ip host shadow 172.21.9.7 172.21.9.55 172.21.9.60 translate x25 31315555501 tcp shadow host-name

The Protocol Translator attempts to open the next destination if the first one fails. [CSCdi18102]

• "telnet transparent" and "escape-char none" are now automatically set on incoming one-step Vty-async connections over TCP. The "stream" option must be used with the "telnet" exec command to accomplish total transparency to a vty-async connection over TCP. [CSCdi38359]

• When using permanent virtual circuits (PVCs) with the "swap" option on packet assembler/disassembler (PAD) to TCP translation, the PVC may terminate after the first connection. [CSCdi39626]

• Terminating a PAD-virtual asynchronous connection immediately after initiating it can cause the router to reload. [CSCdi39675]

• Protocol translation using Two-steps Virtual Async connection causes the router to reload. [CSCdi40229]

• You cannot use x25 regular expressions in a translate statement. [CSCdi40511]

• Any new Virtual Async connection that drops immediately (PAP/CHAP authentication mismatched) causes an incomplete clean up of the Virtual Async process. [CSCdi42137]

TCP/IP Host-Mode Services

• UDP checksum is being set to zero instead of recalculated when a BOOTP reply from a server (with a correct UDP checksum) is being forwarded to the client. This causes certain BOOTP client implementations to incorrectly ignore the BOOTP reply. [CSCdi38285]

• An access server can accept a new reverse tcp connection while being in the HANGUP state for the previous connection. This will cause the new connection to be closed shortly after being established. This happens with the modem cts-required command configured. [CSCdi39085]

VINES

• When running VINES on a Cisco 4500 router, the router may occasionally generate the message "VINES: Invalid string in data". [CSCdi39242]

• Issuing a show vines interface command can crash the system. [CSCdi40388]

• Under heavy loads, the VINES router system process may not run frequently enough for proper VINES operation. Symptoms include a high amount of route and neighbor flappage. Reducing the load on the router may help alleviate the problem. [CSCdi41922]

• The router is too restrictive on doing MAC/VIP frame size comparison on fddi. The result is, no vines server connected behind the fddi ring is seen by the router. This is particularly evident when an ethernet/fddi translational bridge is between the router and vines server. (ex. C1200 catalyst switch) [CSCdi42292]

Wide-Area Networking

• When running PRI there are spurious access at bringup time. This is from a shut/no shut or a RESTART and RESTART_ACK. There is no CCB allocated yet. [CSCdi35949]

• When encapsulating OSI packets for transmission on a frame relay PVC, two copies of the NLPID are put in the header. RFC1490 specifies that the redundant NLPID should be left out. [CSCdi36199]

• Added support for voice calls. Incoming and outgoing voice calls can now be configured seperately. For outgoing calls there is a new field in the dialer map statement called "class". For incoming calls, which are ignored for BRI, there is a new interface command "isdn incoming-voice data".

For outgoing calls to be placed as a voice call:

dialer map ip 6.1.1.1 name test class foo 15551212

map-class dialer foo dialer voice-call

For incoming voice calls to be accepted. Currently BRI ignores voice calls and PRI rejects them:

int bri 0 isdn incoming-voice data [CSCdi36915]

• If an interface configured for priority or custom queueing is modified to encapsulate LAPB, the configuration will still reflect the queuing feature but the interface will operate using the standard queuing method. [CSCdi38693]

• If a router has two ATM interfaces connected to different switches, and one of the switches is reset, or a new prefix is set on one switch, the clients associated with both interfaces will go down and back up. Only the clients associated with the switch that was reset should go down and up.

There is no workaround. [CSCdi38974]

• Routers with an ISDN BRI interface may not properly answer incoming calls. This may occur if a "clear interface bri x" command is entered while calls are established or if the isdn tei flag is configured for first-call. The incoming call will be accepted, but the Layer 3 CONNECT message will not get sent out to the network. [CSCdi39627]

• This results in SVC churning, but has no real impact on functionality. It means that the VCD numbers (and underlying VPI/VCI) going to the ARP server changes more than you would like, but there is virtually no impact on address resolution. Worst case it means that the client doesn't have a call in place when it wants to ARP, so it drops the packet and calls the server. The next packet (and all future ones to that destination) will then get switched. [CSCdi39635]

• The first CMNS connection directed to an Ethernet CMNS host fails if the LLC2 session between the Cisco router and the CMNS host has not been opened by a previous connection attempt. [CSCdi39783]

• In rare circumstances, an SDLLC connection failure can cause the router to reload. This is true for releases 10.2, 10.3 and 11.0. [CSCdi39832]

• When a serial ppp link from a 7000 to a lex box goes protocol down, the lex code should not continue to forward frames out the serial interface. [CSCdi39882]

• This causes alignment errors, but doesn't seem to have any other ill effects. [CSCdi39998]

• Frame-relay priority-dlci-group command disappears from the router configuration when PVC status changes from ACTIVE to INACTIVE or DELETED. [CSCdi40018]

• The crash in this bug is the result of CSCdi40023. The fix for CSCdi40023 resolved this bug CSCdi40106. We added an extra checking in this bugs fix, so frame-relay won't crash the router even there is a hashing function error. [CSCdi40106]

• Changing the NSAP of the ATM ARP Server leaves the old map lying around. This does not appear to interfere with the correct functioning of the ARP client. [CSCdi40212]

• The ATM ARP Server will crash the router after receiving a packet from a client reporting the IP address 0.0.0.0. This usually happens by forgetting to configure an IP address on the ATM interface.

Workaround: make sure you have IP Addresses on all members of the LIS. [CSCdi40277]

• Data transits the network correctly, but over more SVCs than it ought to use (9 instead of 2). [CSCdi40510]

• Changes implemented for basic-net3 switchtype for ISDN BRI interfaces. This is required for Italy homologation, as they test more cases within the specification. [CSCdi40646]

• X.25 and LAPB encapsulations do not operate correctly. [CSCdi40746]

• Routers with an ISDN PRI interface may have channels put into an "out-of-service" condition and will not accept or place calls. This seems to show up predominantly on the DMS-100 switches.

The routers will now change the channels back to "in-service" with a Layer 3 Restart message, a shutdown of the interface as well as with the Service (in-service) message. [CSCdi40762]

• You should not be able to specify the "inarp" keyword here. If you specify the MIDs then you can also use the "inarp" keyword. [CSCdi40829]

• A CMNS call directed to a downed x.25 destination interface causes a bus error. [CSCdi40830]

• When a multipoint subinterface is defined with no associated PVCs, the system marks the subinterface down. This condition is corrected as soon as a PVC is associated with the subinterface. [CSCdi40880]

• This causes some non-critical sections of the Classic IP over ATM code to run slower than they should on 4500 and 7500 routers. [CSCdi40913]

• Configuring X.25 on a serial interface may cause the router to reload unexpectedly with the message "Exception: Illegal Instruction". All router platforms that have X.25 functionality are susceptible to this problem. [CSCdi40956]

• On an ISDN interface configured as part of a Dialer group for PPP:

- IPCP will cause a host route to be pointed at the D channel (subinterface 23 in the case of a Primary Rate Interface) - IPCP will override a statically defined host route of the calling party - IPCP will only install a single host route even if multiple users are connected - Host routes installed by IPCP will never be cleared

On an asynchronous (incl VTY) interface:

- BOOTP will fail - An IP address entered with a PPP command will be lost during IPCP negotiation

On a Point-to-Point interface (async, VTY, sync, ISDN, etc):

- IP Address Pooling will lose addresses - IPCP will not negotiate the correct IP address

On a VTY interface:

- 'default' is not a valid parameter to 'ppp' or 'slip' on the first command [CSCdi40958]

• [CSCdi41170]

• An attempt to start up a new Virtual Async connection on a VTY line that has not been totally shut down from the previous connection can cause the router to reload. [CSCdi41378]

• Once X.25 has been configured on an interface, that interface will not work correctly with any other serial protocol. The router must be rebooted before another serial protocol may be used. [CSCdi41491]

• The system may reload if the virtual async line is reset at the same time as the PAD connection is closing. [CSCdi41961]

• If a multicast packet is sent to an ATM interface and it does not map onto a VC, unpredictable behavior may result affecting the entire router. [CSCdi42139]

• Forced reload of router when forwarding an X.25 call and the destination interface is down. [CSCdi42195]

• Support for two non-standard IPCP options has been added. These options were defined by Microsft and ship in the Windows 95 and Windows NT client. They support the negotiation, by the client, of up to two DNS addresses. Previous to this, these options were rejected by the Cisco access server. Two other non-standard options, used to negotiate up to two WINS addresses, are not supported and are still rejected.

The DNS address(es) returned in the negotiation are the first (and second) addresses in the 'ip name-server' configuration command. If a DNS address is not available to be given to the client, then the option(s) is rejected. [CSCdi42205]

• When making international ISDN PRI using a 4ESS switchtype calls will be marking as international calls if the number called starts with 011 or x011, where x may be any digit, and more than 4 digits are dialled. This will only be true when the switchtype is primary-4ESS. [CSCdi42248]

• When using a PAD connection, a false "buffer already setup" log message is sent to the monitoring terminals, or SYSLOG hosts. The PAD connection continues to function properly. [CSCdi42345]

• After a "micro reload" command, the router cannot send to a multicast or broadcast address associated with a LANE subinterface. This means IP route updates will not be sent out, causing other routers to loose IP routes through this router.

The workaround is to reboot the router after adding any necessary "micro" commands to the configuration. [CSCdi42371]

11.0(1) Caveats/11.0(2) Modifications

This section describes possibly unexpected behavior by Release 11.0(1). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(1). For additional caveats applicable to Release 11.0(1), see the caveats sections for newer 11.0 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(2).

AppleTalk

• The system may halt unexpectedly when show appletalk route detail is given. There is no workaround. [CSCdi36007]

• On a large AppleTalk network with redundunt links, CPU utilization may increase dramatically due to heavy recalculation for each neighbor's update as a result of an unbalanced (lopsided) routing table search tree. [CSCdi39372]

Basic System Services

• Using point-to-point LAPB compression seems to generate a memory leak. Workaround would be removing the command 'compress predictor' from the configuration. The problem with the predictor (RAND) compression algorithm was fixed. [CSCdi32109]

• If tacacs extended was configured prior to configuring AAA New-model and tacacs+, the system may continue to send some extended tacacs messages until it is reloaded with the new configuration. A workaround is to manually turn of extended tacacs before enabling AAA. [CSCdi35591]

• A new global command [no] downward-compatible-config version causes the router to attempt to generate configurations that are compatible with the specified version. Currently, only IP access lists back to version 10.2 are generated. [CSCdi36981]

• When using autoselect PPP in conjuction with TACACS+ authorization, the routing table will contain the host route for the default IP address assigned on the async interface even if TACACS+ and IPCP have assigned a different address to the client. [CSCdi37366]

• When netbooting a Cisco 7500 series router, the error message "CBUS-3-CCBPTIMEOUT" might be displayed. This message indicates that the router is failing to recognize the interfaces in the ciscoBus 1 slots. [CSCdi37853]

• The spinning star animation during file transfer is compelling visually but useless for showing problems with a TFTP connection. [CSCdi37940]

• On Routers running subset images which do not support all serial line encapsulation types (CFRAD, CiscoPro) setting the encapsulation on a serial interface to an unsupported type can cause a recursive encapsulation swapping loop. This caveat has been resolved in 10.2(8.1), 10.3(5.1) and 11.0(1.1) releases. [CSCdi38244]

• When frame-relay is configured, a 4500 with a 11.0(1) xboot image may exhibit cosmetic SYS-3-SUPNONE at reload. [CSCdi38328]

• IPX SAP process may consume more memory than required causing a memory leak and potential memory exhaustion. [CSCdi38381]

• the "output hang" time as seen in "show interface" is wrong for cbus interfaces. [CSCdi38496]

• cardIfIndexTable in the cisco Chassis MIB is not available. [CSCdi38945]

• Use of the fair-queue interface command with a non-default value for congestive discard threshold can cause the router to reload.

If accepted, the value is correctly interpreted, but will not be saved in the stored configuration. [CSCdi38970]

• The 'conversation' counters in the 'show queue' (for WFQ) display are inaacurate. [CSCdi39224]

• There is a problem with tn3270 emulation in which the 3270 datastream WSF command code X'll' isn't handled correctly. After receipt of this command by the router the keyboard becomes locked up. To get the IBM login screen the user must reset the keyboard, and enter an attention key (ENTER). [CSCdi39265]

• Support for the Network Time Protocol (NTP) was left out of the service provider (-p) images. [CSCdi39294]

• SNMP can report information about cards that have been removed, in cardIfIndexTable. [CSCdi39308]

• No start_time attribute is sent in AAA Accounting records via TACACS+, even if the router knows what time it is. [CSCdi39403]

• When using a router with an RSP, if the command no ip route-cache is executed for an X.25-configured serial interface, the message "%RSP-3-RESTART: cbus complex" is sometimes displayed. [CSCdi39476]

• [CSCdi39698]

• Router looses memory slowly when PPP async encapsulation is used in conjunction with AAA & Tacacs+. [CSCdi39879]

• Router looses memory slowly when Tacacs_plus is used in conjunction with AAA for authenticating User logins and Network connections. [CSCdi39880]

• [CSCdi39967]

• Telnet speed is retained even after the session is closed in version 10.3 IOS. [CSCdi40022]

• Privilege levels set by TACACS+ now are properly applied to the user at login. [CSCdi40150]

DECnet

• When DECnet connect initiate packets are sent over a DDR link, the router tries to open up a DDR link. In the meantime, however, DECnet thinks there is no route to the destination and returns the packet to the sender, thereby terminating the connection. A second connect initiate session is needed for the connect to get across.

The fix is for DECnet to recognize that this is a special situation which needs to be handled differently, and that the packet should be dropped instead of being returned to the sender of the connect initiate packet.

Once the circuit is established, one of the (numerous) retransmit connect initiate packets will establish the end-to-end session.

This fix is on the DECnet side; the relevant dialer fix appears in CSCdi37919. [CSCdi33368]

• The DECnet fast-switching code path cannot handle a static route that points to another DECnet address (i.e. the static route has no outgoing interface information). In this situation, we need to punt the packet to process switching, which can get the next-hop interface information. [CSCdi38977]

• Segv exception when running DECnet Phase IV to Phase V conversion. [CSCdi39208]

EXEC and Configuration Parser

• The rshd process on a Cisco router tries to append domain suffixes on a DNS lookup even though it should have been passed a FQDN. A possible workaround is to configure ip domain-list .. [CSCdi30543]

• You cannot assign a privilege exec level to the command terminal download [CSCdi38824]

IBM Connectivity

• If the CIP controller fails to execute a configuration command successfully, the system does not undo the command. A write term will erroneously show the presence of the command, when in fact, it is not configured. The user must manually undo the configuration by issuing the [no] form of the command.

This situation can be detected by the occurrence of a CIP-generated message following the configuration command, such as the following:

%CIP3-3-MSG: %CONFIG-3-NODEVSPC: Error allocating storage for device block [CSCdi25909]

• SDLLC traffic flow over RSRB/FST over X.25 can cause system to reload. Same symptoms (STACKLOW error) may be observed with X.25 over LLC2. [CSCdi30085]

• In configurations where there is a duplicate definition for a bridge on two interfaces, even with one of the interfaces shutdown, stange connectivity problems can occur. Duplicate bridge definitions should not be permitted within the router and should be avoided within a network. [CSCdi37283]

• Netbios connections occasionally fail to connect through remote source route bridging when local acknowledgement is enabled. The workaround is to disable local acknowledgement. [CSCdi37525]

• The SNA SDLC MIB implementation is based on draft-ietf-snadlc-sdlc-mib-06. This Internet Draft has been superceed by RFC 1747. [CSCdi37617]

• The router may be forced to reload when removing configuration statements for the Downstream Physical Unit feature - i. e. no dspu rsrb... This will only occur if there are active PUs while the configuration statements are being removed, so a workaround would be to shutdown interfaces or take other measures to ensure there are no PU transactions taking place before removing the DSPU configuration commands. [CSCdi38144]

• On the 4000, 4500, and 4700 series routers with FDDI interfaces, if SR/TLB (translational bridging) is set up between the FDDI and Token Ring, all frames destined to multicast or functional MAC addresses have their destination address translated to canonical format. While this is correct for Ethernet to T/R SR/TLB, it is not correct for FDDI to T/R SR/TLB. This problem is not seen on the 70x0 or AGS+ platforms. [CSCdi38322]

• LNM does not get the adapter profile for the local bridge and the remote bridge, once the bridge number of the local bridge is changed.

If the remote adapter is queried from the LNM station, the LNM adapter is closed, and no other operation can be performed. [CSCdi38368]

• When DLSw+ prioritization is enabled, the DLSw+ code classifies traffic as normal priority when it should be high priority. This problem is only seen on the 4500 platform - the problem does not occur on non-4500 platforms. [CSCdi38827]

• When using Cisco's APPN network node function, a APPN TG number is currently assigned for the partner node each time that node connects in. If the node disconnects and reconnects many times, the storage and overhead of maintaining the previous inactive TG is not optimal. Cisco plans to change to reuse TG numbers that were used during previous connections to the same partner node. [CSCdi38839]

• Configuring the nw sub-parameter of the llc2 dynwind command is not possible unless it is combined with the dwc sub-parameter. [CSCdi38916]

• A problem was introduced in the fix for CSCdi38322 which caused Source-Route Translational bridging (SR/TLB) to break. This problem affects Interim release 10.3(5.1) only - routers doing SR/TLB should not use this Interim IOS version. No other IOS versions will be affected by this problem. [CSCdi38988]

• The negotiation of window size between two DLSw+ peers may not end up with the same window size at both peers, causing problems with flow control, and ultimately, with any level of DLSw+ traffic, causing the DLSw+ session to hang. PLEASE NOTE: The fix for this problem cannot be made backwards- compatible. As such, versions of Cisco IOS without this fix (Interim release 10.3(5.2) or below) should not be used in the same DLSw+ network as versions of Cisco IOS with the fix (Interim release 10.3(5.3) or above, or any release of IOS 11.0). [CSCdi39082]

• An AGS+ may crash unexpectedly when configured to do RSRB direct encapsulation over a serial line with the message "Exception: Illegal Instruction at 0xC"

This feature is not supported and is being removed. [CSCdi39276]

• The following three problems have been observed when source route bridging from token ring to FDDI is enabled on a router:

1. A corrupt frame is generated on the FDDI when a explorer frame is bridged from the token ring. The resulting FDDI explorer frame has its 'MAC address length bit' set to indicate 2 byte addressing when, in fact, the frame has a 6 byte address. These frames are mis-read by other stations on the FDDI ring.

2. If source route bridging from token ring to FDDI is configured to use a ring group while remote source route bridging (RSRB) is also configured, the router will erroneously attempt to forward FDDI frames over RSRB links. Source route bridging from FDDI to token ring over RSRB is not supported.

3. If the router receives a FDDI frame with a duplicate ring number in the routing information field (i.e. a rif loop), it will erroneously forward the frame. The correct behavior is to drop frames that contain RIF loops. [CSCdi39293]

• If an APPN NN has a CP name that is lexicographically higher than the SSCP name of the VTAM, the system might experience XID negotiation failure with sense 08090040. [CSCdi39565]

• When using the Cisco APPN network node feature, when the Cisco NN has a CPSVRMGR (dlur to dlus lu6.2 session pair) pipe with a VTAM host and an IBM 3745 is used as the connection to the composite network node, the Cisco APPN node may pause indefinitely if the 3745 sends the Cisco node an adaptive session pacing window size of 7FFF. [CSCdi39568]

Interfaces and Bridging

• When you do a show controller MCI on a Hitachi based product with no cable attached, you see buffer size, HD unit, and No DCE cable. This may cause some confusion with the specific message of DCE cable. This is a known display message error. [CSCdi28337]

• The 5 minute input and output rate counters may reflect rates that are higher than the actual rate when fastswitching, autonomous switching, or SSE switching. [CSCdi30206]

• Very intermittently,The FSIP controller detected a spurious error on the transmit buffer size resulting in a controller fatal error.

fsip179-0 corrects the problem. [CSCdi30344]

• SDLC Multidrops need router to ignore data carrier detect for High-End Platform. This behavior has been observed in 10.0 code. This aspect of implementation will be in post 10.0 IOS. [CSCdi32813]

• The 4500 with an FDDI interface module may reload with an error. The interface should reset first instead of reload. A temporary workaround is to shutdown the fddi interface. [CSCdi35936]

• Under some circumstances, packets arriving via a MIP interface will not be silicon switched when they should be. A workaround is to insure that there is an appropriate network layer protocol address defined for the first channel group in the configuration for each controller. [CSCdi37030]

• On the BRUT partner product (2500 variant co-developed with DEC) when an Ethernet interface goes down the output of a show interface still shows the Interface as being up. The SNMP Replies are also incorrect. This problem has been resolved in 10.0(10.5), 10.2(8.1) and 10.3(5.1) releases of the code. [CSCdi37135]

• When routing packets to serial interfaces, the output packet and byte count values available via SNMP or displayed with the "show interfaces" command may be inflated. [CSCdi38269]

• Transparent bridging across HDLC serial links does not work with LAT compression enabled on low end platforms. The workaround is to disable LAT compression. [CSCdi38595]

• Intermittenly vty-async connection messages are not displayed after entring SLIP/PPP exec command. [CSCdi39088]

• When an access list is loaded via the config net command, large blocks of memory might be consumed by the silicon switching engine (SSE) manager process, requiring the router to be rebooted. [CSCdi39419]

IP Routing Protocols

• For EIGRP, there are a number of items missing from the show ip protocol command especially in regards to EIGRP metrics and default networks. [CSCdi23668]

• The bug exist in all releases. When secondary address is from interface which is OSPF enabled, OSPF will be turned off on that interface. Customers have to do a no network/network commands sequence to enable OSPF on that interface again. [CSCdi26731]

• When executing the "no router ospf" command, a system reload occurs. [CSCdi33077]

• Removing an ip name-server address that does not exit, will cause the system to return an incorrect error message. [CSCdi35100]

• Router responds to a rtquery with a TTL of 2. [CSCdi35234]

• When the eigrp process receives a hello packet from a neigbor, it tries to send an update packet, but this process of sending an update packet can be suspended by the eigrp process. When the eigrp process gets scheduled again to send the update packet the neighbor could be dead and all of the internal data structures for that peer (neighbor) could have been erased, which confuses the eigrp process and results in the generation of wrong bus address. [CSCdi35257]

• This bug exist in all releases. If OSPF are configured on unnumbered interfaces but the address of source interface is then modified so that OSPF is disabled on the source interface, OSPF is not disabled correctly on those unnumbered interfaces. The router will crash when OSPF routing process is latter deconfigured. [CSCdi35840]

• Clearing ip route causes memory corruption which in turn causes reload, when the memory is checked for validity. Problem reported in 10.2(6). The fix has been integrated into 10.2(8.1), 10.3(5.1) and 11.0(1.1) releases. [CSCdi36060]

• If a route's holddown timer expires and new information comes in before the route is finally aged out, the IP route cache may get out of sync. (Obviously, this can only happen with routes learned via RIP and IGRP.) [CSCdi36713]

• Packets that are locally generated by the router cannot be policy-routed. The new command ip local policy route-map name defines such a policy, and the show ip local policy command displays the policy. [CSCdi36983]

• When using the IP Local-area Mobility feature, the router may reload under some circumstances. As a workaround, Local-area mobility can be disabled. [CSCdi37313]

• The IGRP metric for routes coming from a BRI interface are incorrect. [CSCdi37686]

• EIGRP retains summary route with incorrect metric if learned by multiple paths. [CSCdi37985]

• router display following cpu hog messages and trace back:

Jul 27 15:09:54 harvard-gw 526: %SYS-3-CPUHOG: Task ran for 3520 msec (44/7), Process = OSPF Router, PC = 243182 Jul 27 15:09:54 harvard-gw 527: -Traceback= 3E206 24318A 22F204 Jul 27 15:09:54 bbn3-gw 325: %SYS-3-CPUHOG: Task ran for 5964 msec (99/40), Process = OSPF Router, PC = 243182 Jul 27 15:09:54 bbn3-gw 326: -Traceback= 3E206 24318A 22F204 [CSCdi38044]

• When an IP multicast address is used as the destination address in an ip helper-address command, the router fails to forward the broadcast. [CSCdi38134]

• In a misconfigured/malfunctioning token ring bridging environment, pinging of the HSRP virtual IP address can cause the ICMP echo request packets to be massively replicated. [CSCdi38170]

• Doing a redistribute connected will also redistribute interface static route into OSPF. In other words, OSPF will generate external link state advertisement for it. Doing clear ip route * will delete the external link state advertisement. [CSCdi38232]

• Standard IP access-lists (1-99) do not accept the host keyword like the extended IP access-list (100-199). [CSCdi38358]

• DVMRP can spew a lot of debug output, and CSCdi37082 (partially) took care of this by allowing the user to specify debugs for only incoming or only outgoing streams. However, this too was not enough, so we are enhancing the debug to accept an access list. [CSCdi38504]

• A problem exist in which static routes are not being redistributed into eigrp after a clear ip route * . A workaround is to kick start the redistribution process by either removing one static route and reinstalling it, or by removing and reinstalling the redistribute static command under router eigrp xx command. [CSCdi38766]

• In EIGRP, the hold-time and hello-interval do not properly default when the encapsulation on the line is changed to frame-relay. [CSCdi38859]

• AutoInstall sets up temporary static routes to access the TFTP server. These routes are torn down when AutoInstall is complete. When this happens, the chain of static routes may become corrupted. [CSCdi38875]

• Transparent Bridging of IP ARP from HDLC serial interfaces to token ring fails to forward unicast ARP replies. [CSCdi38884]

• On a router running OSPF, a clear ip route * could cause the router to reload. This caveat has been fixed in 10.2(8.1), 10.3(5.2) and 11.0(1.3) releases. [CSCdi38914]

• "ip ospf network point-to-multipoint" doesn't support 4 routers on the same subnet with version 10.3(4.6) [CSCdi38999]

• Extended IP access lists which use UDP destination ports can have an incorrect configuration generated for them. This bug was introduced in 10.3(5.1). [CSCdi39192]

• In some rare circumstances, the router may suddenly cease to respond to commands or forward packets. Power-cycling the router may be necessary in order to recover. [CSCdi39471]

• OSPF sometimes create intra-area host route which point to itself during route flapping. This fix resolves the problem. [CSCdi39623]

• When a router is configured with tunnel or loopback interfaces, output buffers are consumed and not returned. In addition, tunnel interfaces will not pass packets. There is no way to clear the output buffers other than to reload the router. The consumption rate is based on the frequency of sending packets down a tunnel or to a loopback interface. To reduce the impact, shutdown the tunnel or configure the router to not use the loopback interface.

Tunnel1 is up, line protocol is up Hardware is Tunnel Internet address is 10.0.0.1 255.0.0.0 MTU 1500 bytes, BW 4800 Kbit, DLY 500000 usec, rely 255/255, load 1/255 Encapsulation TUNNEL, loopback not set, keepalive set (10 sec) Tunnel source 171.69.232.7 (Ethernet0), destination 171.69.232.20 Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled Checksumming of packets disabled Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Output queue: 67/64/5 (size/threshold/drops) Conversations 2/2 (active/max active) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 67 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets, 0 restarts 0 output buffer failures, 0 output buffers swapped out [CSCdi39816]

ISO CLNS

• Getting system reloads while routing CLNS and errors on the console:

null db: null ibn in clns, xs_sending process = clns input, ipl=0, pid=30 traceback = 0x28376, 0x24608C, 0x24652A [CSCdi34841]

• If an ESH is received from a neighbor running ISIS, it will overwrite the ISIS adjacency and cause unnecessary LSP flooding and SPF calculation. The adjacency count also gets messed up.

This can happen in some unusual circumstances when running ISIS for IP only. [CSCdi37612]

• The ISIS protocol definition requires that a received LSP which is corrupted (according to its internal checksum) be purged by the receiver, causing the initiator of the LSP to regenerate it.

However, if a network has a link which causes data corruption with correct data link checksums, this can cause a continuous cycle of purging and regenerating large numbers of LSPs, rendering the network nonfunctional.

There is no workaround to this problem. [CSCdi37692]

• If a subnetted network is present in the network, the level 2 link state packets will be reflooded every time the shortest path first algorithm runs. [CSCdi37879]

• Under obscure circumstances, it is possible for a level-1/level-2 ISIS adjacency to be reflected in only one of the level-1 and level-2 adjacencies. The result is partial connectivity.

A possible workaround is to perform a "clear clns neighbors" command when this occurs. [CSCdi38310]

• If ISIS is configured on a serial line *after* the ISIS process is configured to be L2-only, hellos will not be sent, and the adjacency will not come up.

This problem does not happen after a reboot, because the interface is configured for ISIS before the ISIS process is set to be L2-only.

A workaround is to configure ISIS on the serial line, followed by the ISIS process. Another workaround is to perform all configuration, save the configuration to non-volatile memory, and restart the system. [CSCdi38585]

Novell IPX, XNS, and Apollo Domain

• Sometimes SPX spoofing may start on one side while the other side is not spoofing, this will cause spx sessions to timeout. [CSCdi38175]

• distribute-list command is missing under ipx router rip command. [CSCdi38216]

• When a SAP packet fails to be sent the SAP sent counters may still be incremented. [CSCdi38293]

• In highly redundant topologies containing backdoor paths a routing loop may occur when running IPX-EIGRP. [CSCdi38319]

• Adding an XNS static route that's also an interface route causes the routing table to have duplicate entries. [CSCdi38591]

• Show ipx server unsorted actually shows server listed sorted by name, it should show the unsorted table. [CSCdi39233]

Protocol Translation

• Virtual async interfaces, such as those used for slip or ppp over pad connections, may unexpectedly stop sending packets. [CSCdi36149]

• An access class specified on a translate command using X.25/pad as the inbound transport is not evaluated properly. [CSCdi37114]

• When using one-step translation without requiring a login, a per-user access lists cannot be assigned by Extended TACACS for a virtual async interface. [CSCdi37678]

• A Virtual Async connection was not notified of the line RESET condition and remained active. The "show translation" exec command continued to show active users that did not exist because the active user count was not decremented. This prevented the "no translate" configuration command from deleting the translate entry. [CSCdi39133]

TCP/IP Host-Mode Services

• The router can erroneously drop packets (generating ICMP ttl-expired messages) from serial interfaces when TCP header compression is configured on those interfaces. [CSCdi37637]

• TCP header compression debugging and detailed ip debugging can sometimes print TCP sequence and acknowledge numbers as negative numbers. [CSCdi39127]

TN3270

• A slow memory leak occurs in operations, causing the router to reload when it runs out of memory. This problem was introduced in IOS Release 10.3. Cisco Systems expects to address this caveat in release 10.3. [CSCdi37917]

• The cursor placement in TN3270 emulation does not behave as expected. When editting fields in a CICS application, the cursor moves to the side of the screen, instead of to the left-most position in the field. Cisco Systems expects to resolve this caveat in release 10.3 of the IOS. [CSCdi38677]

VINES

• A Vines BADTIMER error message may appear following system initialization. This is purely cosmetic. [CSCdi35167]

• Current behavior is to send Vines redirects to an all 'F's broadcast at both the data link and network layer addresses.

A redirect should to sent to a data link unicast address and a vines network broadcast address. [CSCdi38016]

• The Vines fastswitching cache may not be properly invalidated when either a better or alternative equal-cost route is learned. As a result, packets may not be optimally routed when they are fastswitched. [CSCdi38606]

• The system may halt unexpectedly when show vines interface is used. The behavior occurs only when SRTP is enabled. [CSCdi38846]

• When vines single-route is enabled, the metric for alternative routes is recorded incorrectly. Disabling vines single-route avoids the problem. [CSCdi39054]

Wide-Area Networking

• When a received Call is routed to a CMNS host, an LLC2 connection is attempted but fails, the configured CMNS map is deleted. [CSCdi30978]

• Values on dialer timers, such as the "dialer idle-timeout" command, do not work for values greater than 2147483, rather than the published maximum (4294967).

The workaround is to use the lower value as the maximum. [CSCdi33266]

• On link reset, the LAPB N1 value is not updated after the new modulo is configured. This causes the encapsulation failure on large packets when LAPB modulo is changed to 128. [CSCdi35191]

• Traceroute responses will not be sent out over an ATM link, so traceroutes always fail when attempting to transit ATM links. Normal data packets (such as ping) work just fine, though.

There is no workaround. [CSCdi35837]

• The following new show command will be added:

show isdn history

It will display the call type (outgoing/incoming), called or calling party number and the duration of the call in seconds. [CSCdi36875]

• When using X.25 encapsulation over BRI interface, LAPB fails to connect and no traffic is sent or received. [CSCdi37190]

• The router may crash when removing Cx1 controller commands. This is a small timing window and can only be recreated by executing a script. If the commands are removed by hand the router will not crash. [CSCdi37341]

• After changing an X.25 LTC from 1 to another number, the router configures the interface as a PVC following a reload or clearing of the X.25 interface. [CSCdi37627]

• When establishing semi-permanent ISDN connections, the SPC facility code is missing in the CONNECT message which may cause some problems with certain switches. [CSCdi37630]

• If the start-up configuration includes a LANE server-bus on a shutdown interface, server-bus's on other interfaces do not come up. The LANE server process will also be consuming large amounts of CPU time. The workaround is to remove the "lane server-bus" commands on shutdown interfaces from the start-up configuration. [CSCdi37789]

• ATM cells being generated (by AIP) are in incorrect format. Incoming OAM cells are also process incorrectly. [CSCdi37887]

• If a telnet connection is opened to the router through a frame-relay link with TCP header compression enabled and that the router is reloaded for some reason like a power outage, a second software-caused reload may occur when the router is being restarted. [CSCdi37923]

• Interfaces using Blacker Front End encapsulation do not correctly determine X.121 addresses from IP addresses. [CSCdi37951]

• When an AIP interface is declared down due to a CD state change while there are SVC's on the AIP, messages similiar to the following may show up.

%SYS-3-INVMEMINT: Invalid memory action (free) at interrupt level

%SYS-2-MALLOCFAIL: Memory allocation of 34 bytes failed from 0x748D8, pool Processor, alignment 0

No workaround. [CSCdi38087]

• Removing a dialer interface which has a PRI as a member from the configuration causes the router to reload. [CSCdi38220]

• ISDN BRI routers, 2500 and 3000 series, will not properly activate Layer 1 after a shut/no shut on the interface. This will cause incoming calls to fail because Layer 1 does not see the event. A work around is to force an outgoing call, this activates Layer 1 and will allow incoming calls to be recognized. This only affects the igs images. [CSCdi38254]

• X.25 doesn't accept configurations of the T1x series of timers when configured as a DCE. As a work-around, configure the analagous T2x timer. [CSCdi38404]

• After a reload, de-group commands disappear from working config. Need to do a config memory after a reload to restore the de-group statements from NVRAM. [CSCdi38475]

• CMNS connections cannot be established. [CSCdi38709]

• There is a bug and a misunderstanding here. The bug will occassionally keep IP traffic from transiting PVCs using static maps to resolve the IP address of the remote side.

The misunderstanding is that such IP addresses will never appear in the ARP table, by design. PVCs using RFC 1577 inverse ARP will populate the ARP table, static maps will not. [CSCdi38804]

• The router receives a lmi update from the switch saying that a dlci is "inactive" but it is reflected as "deleted" in the show frame-relay PVC and map statements. [CSCdi38822]

• On the high-end platforms such as the AGS+ and the 7000, autoinstall does not work for images 11.0(0.15) and later. [CSCdi38852]

• If IPX is configured before LANE, it comes up with the default box ethernet address. Workaround is to configure LANE first and then bring up IPX. [CSCdi38984]

• This could only happen when ILMI is enabled on an ATM interface and the NSAP is constructed using the interface atm esi command and an ILMI prefix from the ATM switch.

A problem could occur if the line goes down, the switch deletes the NSAP from the routing table, the switch sends the prefix. If the prefix is the same as before, then we did not attempt to reregister with the switch resulting in no calls sent to the router.

The workaround is to do remove then add the ESI address on the ATM interface. Or, remove then add the ilmi pvc on the interface. [CSCdi39215]

• In order for autoinstall to work over frame-relay, the DLCI over which the autoinstall is performed needs to be unique in the router. [CSCdi39401]

• In configurations where a static map is mapping an IP address to an ATM-VC and running an ARP server on that IP logical IP subnetwork (LIS), an ARP is performed for that address. When the NSAP is returned, the static map entry to point at the NSAP in changed instead of a PVC. The workaround is not to use RFC 1577 ARP Servers with static mapped PVCs. [CSCdi39485]

• If a Frame Relay permanent virtual circuit (PVC) is deleted and then restored, it cannot return to an active state. [CSCdi39496]

• Frame Relay DLCIs that are deleted via the no frame-relay interface dlci command are not actually deleted from the system. [CSCdi39555]

• The LANE Server running an a Cisco router will reject "join" messages from other vendors' LANE Clients if the message length is more than the exact size (108 bytes) defined in the LANE 1.0 specification. This prevents the other vendor's Client from becoming operational.

There is no workaround for this problem. [CSCdi39757]

• When multiple ATM subinterfaces are configured, spurious memory accesses or a crash could result when client applications are disabled. There is no workaround. [CSCdi39792]

• When using point-to-point subinterfaces on a frame relay interface, all packet traffic fails due to encapsulation failures--no map found. This is caused by a mismatch in the map entry routine and the lookup routine.

There is no work-around for the problem. [CSCdi40023]

• When we receive ARP Requests for addresses we do not know about, we send back an ARP NAK, but we do not credit our account for freeing up the buffer. So eventually we think we are holding on to more than our fair share of buffers and stop using any more.

There is no workaround. [CSCdi40108]

11.0(17)BT Caveats

This section describes possibly unexpected behavior by Release 11.0(17)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(17)BT.

Basic System Services

• Adding an RSRB peer with direct encapsulation on a Cisco 7000 router configured with CSNA causes a "%RSP-3-RESTART: cbus complex restart" message and takes down the CIP interface. [CSCdi82836]

IBM Connectivity

• CIP TN3270 Server command "show extended ch6/2 tn3270 pu puname" displays some information about the PU, followed by a listing of the LU's belonging to that PU.If the client's IP port number contains 5 decimal digits, the "show" command only displays the first 4 digits, and the fifth digit is missing. [CSCdj13444]

11.0(16)BT Caveats/11.0(17)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(16)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(16)BT. For additional caveats applicable to Release 11.0(16)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(17)BT.

TN3270 server lu idle timer wrapped around every 18.2 hours. [CSCdj41564]

• TN3270 server lu idle timer wrapped around every 18.2 hours. [CSCdj41564]

11.0(15)BT Caveats/11.0(16)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(15)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(15)BT. For additional caveats applicable to Release 11.0(15)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(16)BT.

11.0(14)BT Caveats/11.0(15)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(14)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(14)BT. For additional caveats applicable to Release 11.0(14)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(15)BT.

IBM Connectivity

• Running either CMPC or TN3270 and CSNA on the CIP can cause the Router Process (RP or RSP) to mistakenly think that the CIP virtual interface, /2, is stuck or hung. The result of this is that the RP/RSP will either reset the CIP virtual interface or reset the Cbus complex. Resetting the CIP virtual interface will cause all sessions using the virtual interface (CSNA/LLC2, TN3270) to fail. Resetting the Cbus complex will cause all sessions (CSNA/LLC2, TN3270 or OFFLOAD/TCPIP) on all every CIP in the router to fail. [CSCdi82710]

• When running TN3270 Server SHOW commands or accessing SNMP MIB variables related to CIP TN3270 Server, a Spurious Read message is displayed at the router console. This appears to have no impact on the operation of the router or the CIP. [CSCdi88047]

• When configuration changes are made in TN3270 server such that new PU is added which uses a new ip address, very rarely failure might happen with following message:

%CIP3-3-MSG: %MEMD-3-VCNREGISTER: Invalid VCN (65535)specified

Failing "Invalid VCN number" could be different than 65535 also.

Following message was also reported when SSP is being used:

%SYS-6-STACKLOW: Stack for process SSE Manager running low...

The failure continues until the route-processor is reloaded. There is no known workaround. [CSCdj07773]

• Telstra ITG have a requirement for an enhancement to the 'show extended channel x/y tn3270 client-ip-address' command. Due to the large number of tn3270 clients that access Telstra's network via the CIP-tn3270 server, they have the requirement for a more efficient means of displaying required output from the above command.

The tn3270 server remembers the client IP addresses of active sessions, as well as terminated sessions.What Telstra are concerned about is the amount of output that is displayed as a result of a 'sh ext channel x/y tn3270 client-ip-address' command. This output can sometimes contain data for hunderds of sessions, some active and some terminated.

The enhancement that Telstra ITG are requesting, is the ability to display the status of tn3270 sessions based on the state of a IP address's sessions.

They would like an optional operand to be available at the end of the command which would allow client IP addresses to be queried based on session status. The desired session state such as (ACT/SESS, ACT/NA etc) could be entered into this operand so that only the sessions that were reflecting the requested status be displayed.

Example Current command

show extended channel x/y tn3270 client-ip-address

Example of desired command modification.

show extended channel x/y tn3270 client-ip-address

Status will be available status such as ACT/SESS or ACT/NA [CSCdj07826]

11.0(13)BT Caveats/11.0(14)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(13)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(13)BT. For additional caveats applicable to Release 11.0(13)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(14)BT.

• If odd sap value is configured on a Tn3270-server PU on cip, PU might get stuck in Reset state. The odd sap values are illegal. To avoid this problem, odd sap values shouldn't be used. [CSCdi90299]

11.0(12)BT Caveats/11.0(13)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(12)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(12)BT. For additional caveats applicable to Release 11.0(12)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(13)BT.

IBM Connectivity

• In Tn3270 server config tcp-port of 0 and 65535 cannot be used. It can potentially cause a microcode reload. To avoid hitting this problem donot use port number 0 or 65535 under tn3270-server context or any PU statements underneath that.

This ddts ensures that tcp-port under tn3270 server won't accept the value of 0 or 65535 [CSCdi64150]

• When show on a PU is done which has been in shut state, it doesn't show correct values of siftdown values inherited from global context. The siftdown variables are tcp-port, idle-time, keepalive, unbind-act and generic-pool.

This only affects the show command and doesn't cause any other operational problem. [CSCdi65716]

• Running CIP features TN32700-Server and CSNA concurrently on the same CIP will produce incorrect interface counters. The statistics reflecting the TN3270-Server traffic on the CIP virtual interface si not included in the counters displayed. [CSCdi68510]

11.0(11)BT Caveats/11.0(12)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(11)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(11)BT. For additional caveats applicable to Release 11.0(11)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(12)BT.

SNA alerts generated by the CIP TN3270 Server get corrupted and dropped by the IOS. Such behavior can prevent the alerts from being forwarded to the host.

• SNA alerts generated by the CIP TN3270 Server get corrupted and dropped by the IOS. Such behavior can prevent the alerts from being forwarded to the host. [CSCdi70208]

11.0(10)BT Caveats/11.0(11)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(10)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(10)BT. For additional caveats applicable to Release 11.0(10)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(11)BT.

• When debugging channel events - by means of the "debug channel events" command - the timing-mark command is being misprinted as "UNKNOWN" command. [CSCdi59855]

• Change mib to add tn3270sRunningTime and make some names more meaningful. "Deprecate tn3270sLuLastEvent. Added ciscoTn3270ServerMIBGroupObsolete. Modified SYNTAX clause for tn3270sLuAppnLinkIndex. Introduced tn3270sRunningTime. Replaced tn3270sStatsInboundTransactions, tn3270sStatsOutboundTransactions, tn3270sStatsSampledInboundTransactions, tn3270sStatsNetSampledInboundTransactionRespTime, tn3270sStatsSampledOutboundTransactions, tn3270sStatsNetSampledOutboundTransactionRespTime, with tn3270sStatsInboundChains, tn3270sStatsOutboundChains, tn3270sStatsSampledHostResponses, tn3270sStatsNetSampledHostResponseTime, tn3270sStatsSampledClientResponses, tn3270sStatsNetSampledClientResponseTime respectively. " [CSCdi67808]

11.0(9)BT Caveats/11.0(10)BT Modifications

This section describes possibly unexpected behavior by Release 11.0(9)BT. Unless otherwise noted, these caveats apply to all 11.0 BT releases up to and including 11.0(9)BT. For additional caveats applicable to Release 11.0(9)BT, see the caveats sections for newer 11.0 BT releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.0(10)BT.

• Historically, both the default and maximum values for the TN3270 server maximum-lus parameter were set at 20000. Because of licensing issues, the default value will be set to 2100; the maximum value will become 32000. License reminders will be displayed when the default is exceeded, and warning messages would be displayed when the configured maximum is approached. [CSCdi62250]