Release 10.1(3) Caveats
This section describes possibly unexpected behavior by Release 10.1(3). The caveats listed here describe only the serious problems. For a most current list of caveats against this release, access CIO as described in the section "Cisco Information Online" at the end of this document.
- When IPX routing is enabled on a Token Ring interface and there is a source-route bridge network behind the ring, a multiring ipx all command is used to cache the RIF in the router. During normal operation all is well. But when a station is moved from one ring to another ring (for example, from 0B8 to 0B1), the station cannot reach the server. Looking at the RIF cache on the AGS+, it is fine. However, analyzing the frames with a Sniffer, we can see the "create connection request" from the station with a good RIF field but the answer from the AGS+ shows the previous RIF (the RIF before the station was moved). The workaround is to disable the IPX route cache or to clear the IPX cache when a station is moved. This is a general problem with all routed protocols. The RIF code does not inform the routing protocols when an entry in the table changes. Therefore, the cache entries become invalid. [CSCdi17099]
- Under heavy load, remote source-route bridging sessions using local acknowledgment might unexpectly close. The warning message "LOCACK: invalid IFRAME frame dropped" appears on the console, and any associated LLC sessions are dropped. There is no workaround for this behavior. [CSCdi24374
- When a configuration change occurs that causes the Token Ring interface to initialize, there is a delay between the time the command is entered and the initialization process begins. The Token Ring initialization also impedes other process-level functions. [CSCdi16454]
- The Enhanced IGRP interface command ip summary-address is not written to configuration memory, and thus disappears after the router reboots. The command must be reissued after each reboot. [CSCdi23171]
- In some instances, when a Frame Relay subinterface with an inactive DLCI has been administratively shut down by a user, it may exit the shutdown state and return to the active state even though the DLCI is still in an inactive state. [CSCdi25156]
Release 10.1(2) Caveats/Release 10.1(3) Modifications
This section describes possibly unexpected behavior by Release 10.1(2). All the caveats listed in this section are resolved in Release 10.1(3). For additional caveats applicable to Release 10.1(3), see the caveats sections for newer 10.1 releases. The caveats for newer releases precede this section.
The caveats listed here describe only the serious problems. For a most current list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document.
- Issuing the no appletalk glean command on Phase I AppleTalk interfaces causes AppleTalk ARP to fail. To avoid this problem, do not issue this command. [CSCdi24698]
- AppleTalk ports can get stuck in the restart state when system uptime is greater than 24.85 days. There is no workaround; you must reload the system. [CSCdi25482]
- Global Appletalk ARP commands have a side effect of changing the router ID number for AppleTalk Enhanced IGRP. There is no workaround. [CSCdi25786]
- A STUN multipoint link with 4700 ALA controllers drops connection. When an IBM 4700 ALA polls for the first station, it polls for the second station as soon as it gets a reply. While the IBM waits for a reply from the second station, the first station loses the session. [CSCdi20511]
- An FDDI SMT related crash can happen when the FDDI ring experiences one of the following conditions:
- Configuration changes (cables being connected or disconnected)
- Undesirable configuration reached (for example, wrapped main dual ring)
- Excessive frame errors
- Buffer starvation due to excessive incoming traffic
- Duplicate station MAC address
- Stations (MAC entities) insertion or deinsertion next to this station
- Excessive link errors
- All these conditions cause this station to send out FDDI SMT Status Report frames, which, depending on timing, mightinterfere with normal data frames being transmitted on the same interface and cause a crash to occur. The crash is much more likely to happen when the FDDI interface is heavily fast switching. [CSCdi21508]
- When TCP/IP routing is enabled along with transparent bridging on the same interface, some SNAP encapsulated TCP/IP packets with destinations on the same network segment may be bridged to other networks. [CSCdi23944]
- When receiving DECnet control packets of an unidentifiable type (usually illegal), the interface can saturate its input buffer space resulting in the interface's being unable to receive additional packets. The input queue (displayed with the show interface command) will show n+1/n packets, where n is the size of the input hold queue.[CSCdi24993]
- When load-balancing IP traffic over multiple equal-cost paths, the system's routing table might reach an inconsistent state, leading to a system reload. Before the inconsistent state is reached, the system must have three or four equal-cost paths for a particular route. A routing update must then be received that causes the system to replace those paths with fewer (but still more than one), better metric paths. This route must then become used for further locally generated traffic. This problem is most likely to be seen after an interface flap (that is, after an interface's line state goes from up to down to up again) in an environment where there are redundant, but not symmetric, interconnections between routers. The problem also seems more likely in FDDI environments, where interfaces flap before fully coming up. These flaps can result in multiple back-to-back routing table changes. [CSCdi20674]
- UDP broadcasts can be flooded even if TTL checks fail. [CSCdi22568]
- OSPF may repeatedly retransmit a link-state advertisement with an incorrect checksum. [CSCdi25269]
- The Cisco 4500 router does not properly pass OSI CLNS packets to serial interfaces configured to use Frame Relay. This results in no CLNS connectivity over Frame Relay interfaces. [CSCdi24363]
- The rsup-only keyword of the ipx sap-incremental command cannot be used on subinterfaces. [CSCdi24492]
- Routing VINES over X.25 links might cause the router to unexpectedly reload. [CSCdi24728]
- The router loses packets if an SRTP update is received while there are packets on the SRTP reassembly queue from a different SRTP update. [CSCdi25280]
- Redundant routers can get into a deadlock state where they continuously exchange unicast RTP messages. This state can last up to three minutes or until broken by information from a third router. This problem has only been seen with the RTP protocol, not with the SRTP protocol. [CSCdi25580]
- When the vines serverless broadcast command is configured in a redundant topology and all other router interfaces are configured with the vines serverless command, a broadcast storm results. [CSCdi25597]
- When fast switching VINES over a source-route bridged Token Ring network, the router does not build its fast-switching cache entries properly. This prevents communication with stations that are across a bridge from the router. The workaround is to disable fast switching on the Token Ring interface. [CSCdi26288]
- Excessive interface transitions can cause the router to stop sending VINES routing updates on that interface. [CSCdi26300]
- A router might reload itself after you issue the show frame-relay map command if the Frame Relay interface has a static map configured and is running Inverse ARP for the same DLCI. [CSCdi25585]
- The Frame Relay broadcast queue might exhibit drops under high broadcast volume. There will be an increase in "buffer element" misses at the same time the drops happen. [CSCdi25707]
Release 10.1(1) Caveats/Release 10.1(2) Modifications
This section describes possibly unexpected behavior by Release 10.1(1). All the caveats listed in this section are resolved in Release 10.1(2). For additional caveats applicable to Release 10.1(2), see the caveats sections for newer 10.1 releases. The caveats for newer releases precede this section.
The caveats listed here describe only the serious problems. For a most current list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document.
- Issuing the no appletalk glean command on Phase I AppleTalk interfaces causes AppleTalk ARP to fail. To avoid this problem, do not issue this command. [CSCdi24698]
- The interface configuration command access-expression [in | out] expression is written to configuration memory as a filter for both inbound and outbound packets. [CSCdi24000]
- When an explorer packet is received by the router and the requested hardware address in the explorer packet cannot be verified, the router retransmits the explorer packet out all interfaces at a high rate for several seconds. This behavior manifests itself as a sudden increase in Token Ring traffic for several seconds. [CSCdi22541]
- On half-duplex SDLC serial interfaces, the show interfaces serial unit command returns incorrect information regarding the RTS and CTS signal timing information. This has no operational impact on the SDLC link. [CSCdi23781]
- A STUN multipoint link with 4700 ALA controllers drops the connection. When an IBM 4700 ALA polls for the first station, it polls for the second station as soon as it gets a reply. While the IBM waits for a reply from the second station, the first station loses the connection. [CSCdi20511]
- In some situations, the OSPF router does not form an adjacency with a neighboring router on a local FDDI ring. This is indicated by OSPF showing "State DOWN" in the output of show ip ospf interface while the interface and line protocol are up. On the FDDI interface in question, issuing the shutdown command followed by no shutdown corrects the situation. [CSCdi18460]
- Under rare circumstances, an opening TCP connection can get stuck in CLOSEWAIT state. This can also result in a STUN peer session getting stuck in an OPENING state at the same time. [CSCdi23455]
- Enabling the Hewlett-Packard IP Probe protocol via the ip probe proxy command does not correctly enable the protocol. There is no workaround for this behavior. [CSCdi23909]
- When changing the encapsulation on a serial link from a point-to-point mode (such as HDLC or PPP) to a "cloud" mode (such as SMDS or Frame Relay), IS-IS routing fails to consider the interface as broadcast media. Because of this, the CSNP will not be exchanged and hence the database will not be synchronized. To work around this problem, unconfigure and configure IS-IS after changing the encapsulation type. [CSCdi23691]
- When you issue the clns is-neighbors command on a router subinterface, the command takes effect, but the neighbor address is not saved when written to configuration memory. When you reboot the router, it reads the configuration file and displays a syntax error, and the clns is-neighbors command is ignored. [CSCdi23750]
- The Cisco 4500 router does not properly pass OSI CLNS packets to serial interfaces configured to use Frame Relay. This results in no CLNS connectivity over Frame Relay interfaces. [CSCdi24363]
- The interface configuration command ipx watchdog-spoof fails to properly enable Novell watchdog timer spoofing. There is no workaround for this behavior. [CSCdi23324]
- The rsup-only option of the ipx sap-incremental command cannot be used on subinterfaces. [CSCdi24492]
- The router might be restarted due to an address error when PAP authentication has been configured on an async line. A PPP client sending an invalid PPP frame may cause this to occur. [CSCdi24013]
- When sending traffic to an interface configured for DTR dialing on a Cisco 4500 series router, the router may reload. The workaround is to configure in-band dialing first, then change the configuration to DTR dialing. [CSCdi24766]
