These release notes describe the features, modifications, and caveats for Software Release 9.14, up to and including Release 9.14(12). Refer to the Release 9.1 publications Router Products Configuration and Reference and Router Products Configuration and Reference Addendum for complete 9.14 product documentation.
Note Release 9.14 has reached its end of sales and end of maintenance milestones. Release 9.14(12) is the last maintenance release of Release 9.14. No more features or bug fixes will be applied to Release 9.14. Customer support is available for one year following the end of maintenance. Release 9.14(12) will be available to customers through the TAC and via CIO for one year. If you do not have access to CIO, you should order a diskette copy of the software and store it on a TFTP server at your site so that it can be accessed via netbooting. If you are considering upgrading your software, the preferred upgrade path for Release 9.14 users as of April 24, 1995 is Cisco Internetwork Operating System (Cisco IOS) Release 10.0(9) or Release 10.2(5).
Release 9.14 software is documented in an addendum that is designed to be used with the Release 9.1 software publication. These release notes highlight some of the differences between Release 9.1 and Release 9.14 features and functionality.
These release notes discuss the following topics:
Note All of the following caveats sections include only the most serious caveats. Use UniverCD or CIO to see all the caveats for these releases.
- 9.14(12) Caveats, page 13
- 9.14(11) Caveats/9.14(12) Modifications, page 13
- 9.14(9) and 9.14(10) Caveats/9.14(11) Modifications, page 14
- 9.14(8) Caveats/9.14(9) Modifications, page 15
- 9.14(7) Caveats/9.14(8) Modifications, page 18
- 9.14(6) Caveats/9.14(7) Modifications, page 23
- 9.14(5) Caveats/9.14(6) Modifications, page 28
- 9.14(4) Caveats/9.14(5) Modifications, page 29
- 9.14(3) Caveats/9.14(4) Modifications, page 34
- 9.14(2) Caveats/9.14(3) Modifications, page 36
- 9.14(1) Caveats/9.14(2) Modifications, page 39
- Cisco Information Online, page 41
- UniverCD, page 42
The 9.14 releases are close equivalents to the 9.1 releases. Table 1 shows the correspondence between the releases.
Release 9.14 and 9.1 Correspondence
Release ...
| Is a Close Equivalent of ...
|
|---|
| 9.14(1)
| 9.1(4)
|
| 9.14(2)
| 9.1(5)
|
| 9.14(3)
| 9.1(7)
|
| 9.14(4)
| 9.1(7)
|
| 9.14(5)
| 9.1(7)
|
| 9.14(6)
| 9.1(10)
|
| 9.14(7)
| 9.1(11)
|
| 9.14(8)
| 9.1(12)
|
| 9.14(9)
| 9.1(12.6)
|
| 9.14(10)
| 9.1(14)
|
| 9.14(11)
| 9.1(15)
|
| 9.14(12)
| 9.1(16)
|
This means that most caveats introduced in Release 9.1(16) were also introduced in Release 9.14(12). It also means that most caveats resolved in Release 9.1(16) were also resolved in Release 9.14(12).
Table 2 lists the minimum system software level required to support the specific network processor modules.
Minimum System Software Releases for Network Processor Module Types
Network Processor Module Type
| Minimum System Software Level
|
|---|
| Multimode FDDI
| 9.14(1)
|
| Dual Ethernet
| 9.14(2)
|
| Single-mode FDDI
| 9.14(3)
|
| Dual Token Ring
| 9.14(5)
|
| Four-Port Serial
| 9.14(6)
|
Release 9.14(9) allows customers to upgrade their Cisco 2500 series software remotely.
This section describes the new features in Release 9.14(8).
Flash load helper is a software option available to users who want to upgrade their system software on run-from-Flash systems. Flash load helper simplifies the upgrade procedure without requiring additional hardware; however, it does require some brief network downtime. A system image running from Flash memory can use Flash load helper only if the boot ROMs support Flash load helper. If the boot ROMs do not support Flash load helper, you must perform the Flash upgrade manually.
Flash load helper involves an automated procedure that reloads from the current running image to the ROM-based bootstrap image, downloads to Flash, and reboots to the system image in Flash. Flash load helper performs checks and validations to maximize the success of a Flash upgrade and minimize the chance of leaving Flash in either an erased state or with a nonbootable file.
Release 9.14(8) includes Flash enhancements that apply to the Cisco 4000 and the Cisco 3000 platforms that are not run-from-Flash systems. These enhancements cover Flash upgrades, automatic booting, and reloads. The improvements are as follows:
- The software provides checks and validations to maximize the success of a Flash upgrade and minimize the chances of leaving Flash either in an erased state or with a nonbootable file. File searching in Flash memory is improved. If a filename is not specified, the entire Flash directory is searched for a bootable file instead of checking just the first file.
- The softare attempts to recognize the file in Flash memory. If it is recognized, the softare decides whether it is bootable.When the software is set for autobooting, if a total boot failure occurs, the ROM image is started either from Flash or over the network.
- When the software is set for autobooting, it tries netbooting the commands in the system configuration up to five more times.
- When the software is set for autobooting, if all boot commands in the system configuration are for netbooting and all fail, the softare attempts to boot the first valid file in Flash memory.
- When the software is set for autobooting and the boot commands specified in the configuration fail, one of the following occurs:
- If the "boot default ROM software" bit in the configuration register is on , the system boots the ROM image without any retries.
- If the "boot default ROM software" bit in the configuration register is off, the system retries the netboot commands up to five more times. If these fail, it then boots the ROM image.
- User interface improvements include the following:
- Separate source and destination filenames
- Extensive confirmation prompts and warning messages
- The software does not allow a reload from a virtual terminal if the system is not set for automatic booting. This prevents the system from dropping to the ROM monitor prompt, thereby taking the system out of the remote user's control.
A new command is available when an ISDN BRI interface is configured for the Australian TS013 switch type. Use the isdn calling-number command to configure up to 16 digits. The command tells the network the number of the device making an outgoing call.
This section describes the new features in Release 9.14(6).
For Cisco 4000 routers, the software now supports the 4T NIM, an interface processor that provides four serial ports in full or half-duplex mode. The following new software features are supported for the 4T NIM:
- The invert txc command is allowed for both DTE and DCE.
- The show controller command is enhanced to display the clock rate and cable type (EIA/TIA-232, EIA/TIA-449, V.35, X.21, or EIA-530, DTE, or DCE) and modem signals (handshakes).
Note Prior to the acceptance of the EIA/TIA standard by the ANSI committee, EIA/TIA was referred to as a recommended standard called RS-
xxx.
For Cisco 4000 routers, the software now supports the 2R NIM, an interface processor that provides connections to two Token Ring networks.
The software now supports National ISDN 1. To configure it, use the following command:
isdn switch-type basic-ni1
Release 9.14 supports the Cisco 4000, Cisco 3000 series, and Cisco 2500 series.
The Cisco 4000 supports the following FDDI network processor modules:
- Dual-attachment FDDI network processor module, PHY-A multimode/PHY-B multimode
- Dual-attachment FDDI network processor module, single mode
- Single-attachment FDDI network processor module, PHY-S multimode
Release 9.14 supports the following software features:
- Full FDDI support on the Cisco 4000. The following Release 9.14 FDDI features differ from previous releases for other platforms:
- Ethernet-to-FDDI fast switching for IPX.
- FDDI station management (SMT).
- The FDDI module supports transparent bridging for FDDI-to-Ethernet and FDDI-to-serial configurations.
- The FDDI module supports translational bridging for FDDI-to-FDDI, FDDI-to-Ethernet, and FDDI-to-Token Ring configurations. Note that previous versions of this release note incorrectly stated that FDDI modules did not support translational bridging.
- The Release 9.14 implementation of SMT is based on XDI 6.2.3.
- A system image can be copied from a Maintenance Operation Protocol (MOP) server into Flash memory with the copy mop flash command.
- IPX fast switching over Token Ring to serial, Ethernet, and FDDI interfaces.
The Cisco 4000 supports the Fiber Distributed Data Interface (FDDI). FDDI is an ANSI-defined standard for timed, 100-Mbps token passing over fiber-optic cable. The Cisco implementation of FDDI complies with Version 6.2 of the X3T9.5 FDDI specification, offering single-attachment stations (SASs) and a Class A dual-attachment interface that supports the fault-recovery methods of dual-attachment stations (DASs).
The following commands allow you to configure and monitor FDDI interfaces.
To start and stop the processes that perform the connection management (CMT) function, which allows you to start and stop the ring on one fiber, use the following EXEC commands:
cmt connect [type unit [phy-a|phy-b]]
cmt disconnect [type unit [phy-a|phy-b]]
To specify an FDDI module, use the following global configuration command:
interface fddi unit
To specify the encapsulation method, use the following interface subcommand:
[no] fddi encapsulate
To display information about the FDDI interface, use the following EXEC command:
show interfaces [type unit] [accounting]
To log inbound and outbound SMT frames, use the following EXEC command:
debug fddi-smt-packets
To set the token rotation time, use the following interface subcommand:
fddi token-rotation-time microseconds
To set the TVX time, use the following interface subcommand:
fddi valid-transmission-time microseconds
To control the FDDI TL_MIN time, use the following interface subcommand:
fddi tl-min-time microseconds
To set the maximum number of unprocessed station management (SMT) frames that will be held for processing, use the following global configuration command:
[no] smt-queue-threshold number
To set the autoshutdown threshold of CMT events (in events per second), use the following interface subcommand:
fddi cmt-max-rate number
Release 9.14 supports many fast-switching capabilities. Refer to the fast-switching support table in the Router Products Configuration and Reference Addendum for a complete list of capabilities.
Digital Equipment Corporation's Maintenance Operation Protocol (MOP) is supported on serial and Ethernet interfaces. Release 9.14 supports the following MOP features:
- Loading system software
- Remote router management
- Periodic ID messages
- Loading Flash memory
The following commands allow you to configure and monitor MOP interfaces.
To boot a system image using MOP, use the following ROM monitor command:
b mop filename [MAC-address] [interface]
To configure the system to boot using MOP at power up or at system reload, use the following command:
[no] boot system mop filename [MAC-address] [interface]
To copy a system image that has been stored on a DEC MOP server into Flash, use the following EXEC command:
copy mop flash
To enable MOP debugging messages to be displayed, use the following EXEC command:
debug mop
To enable MOP on an interface, use the following interface subcommand:
[no] mop enabled
To configure an interface for periodic MOP system ID messages, use the following interface subcommand:
[no] mop sysid
To set the time the server will wait for a response before retransmitting a message, use the following command:
[no] mop retransmit-timer seconds
To set the number of times the MOP server will retransmit an unacknowledged message before declaring a failure, use the following command:
[no] mop retries count
The Release 9.14 software generates MOP error messages.
This section describes warnings and cautions about using the Release 9.14 software. The information in this section supplements that given in the following caveats sections.
If you are upgrading to Release 9.14 from an earlier Cisco software release, you should save your current configuration file before configuring your router with the Release 9.14 software.
Release 9.1 is no longer supported on the Cisco 4000. You must use Release 9.14.
In a Cisco 2500, Cisco 3000, and Cisco 4000, the system allocates default buffers based on the amount of I/O memory that is physically available. On the Cisco 4000, the default number of large permanent buffers is changed from 0 to 15. Also, the maximum number of large buffers is changed to 30 buffers. These changes require approximately 45 KB more I/O memory.
These changes were made to accommodate a system running remote source-route bridging (RSRB) applications in some configurations, particularly Token Ring over serial. In such configurations, large packets (greater than 1524 bytes) were dropped because there were no large buffers available to hold the packets for processing. (Initially, 0 large buffers were allocated.)
With a quad serial port configured as a DCE, modem synchronization problems might occur. This is due to a small deviation in the clock frequencies generated by the port (.16% too high at clock rates from 1200 through 38400). Reconfiguring the port as a DTE should correct this problem.
On a Cisco 2500 with 9.14(4) bootROMs running Release 10, you might be un able to Telnet into the router. The bootstrap image supports only five virtual terminal lines (vtys), not 64, and therefore rejects all the vty commands, including t he password. A workaround is to have two separate line commands, each with a different password.
In this example, the bootstrap rejects the second line command, but accepts the first one with the first password:
line vty 0 4
password foo1
line vty 5 63
password foo2
When booting the system software from a TFTP server, do not copy the software image from the router to the TFTP server, then copy it a second time. If you do, the second image will be appended to the first image rather than written over it, and the image will not function in your routers. If you want to copy the image a second time, first delete the image from the destination directory on the server, then recopy the image.
 | Caution If you type the name of a file that does not actually exist, and then tell the router to erase the existing image in Flash memory, you erase the only working system software image in Flash memory. At this point, do not reboot the router. Issue the copy tftp flash command again to load the appropriate image into Flash memory. |
Cisco 2500 series routers execute their images directly from Flash memory. Routers running a compressed image uncompress the image into RAM and then execute code from RAM. Running from RAM on the Cisco 2500 is not supported. Hence, do not load a compressed image as the first file in Flash memory.
Release 9.14(3) does not support local loopback for DCE on Cisco 3000 routers.
When setting the bandwidth, the bandwidth that is displayed with the show interfaces command might not match for some higher bandwidths because some roundoff is performed on the number you entered. The values shown match those seen in IGRP update packets and hence are more useful for debugging.
As of Software Release 9.1, the router automatically translates old default network commands into appropriate static routes. The translation is completely transparent.
On the Cisco 4000, when building the receive buffer rings for the serial and Ethernet interfaces, if a buffer request fails (that is, if there is not enough of a particular buffer size left in the pool), the interface is marked as down and the initialization is abandoned at that point. The interface will later initialize as more buffers are created to fill the demand. This problem is most noticeable in the 1E4T configuration. The serial 3 interface might take as long as five minutes before that interface becomes usable.
However, buffer pool allocation is a user-tunable parameter. The buffer pool to tune depends on the type of encapsulation used by the interfaces. Correspondingly, the ring size changes with the size of buffer required. Table 3 shows the mapping between buffer and ring size on the Cisco 4000. The examples following the table illustrate how to tune buffer pool allocation.
Mapping between Buffer and Ring Size
| Maximum Transmission Unit (MTU)
| Receive Ring Size
|
|---|
| MTU < 1524
| 32
|
| 1524 < MTU < 5024
| 32 (if I/O memory > 2 MB)
16 (if 1 MB< I/O memory <= 2 MB)
8 (if I/O memory <= 1 MB)
|
| 5024 < MTU < 18024
| 4
|
Examples
On a Cisco 4000 1E4T using HDLC encapsulation, there are five receive rings, each with 32 entries. The cache size is 32 buffers. The MTU for this encapsulation is less than 1524 bytes (the same as for Ethernet), so you must use buffers from the "big" pool. The basic number of "big" buffers required is (5 + 1) * 32 = 192. Adding a bit of "comfort" space, you can configure the buffer pool by entering the following command:
buffers big permanent 200
This increases the permanent buffer pool allocation for big buffers to 200.
As a second example, a Cisco 4000 6T router using X.25 encapsulation has six receive rings, each with eight entries, plus a cache ring of eight entries. The MTU for this encapsulation is less than 5024 bytes but greater than 1524, so you must use buffers from the "large" pool. The basic number of "large" buffers required is (6 + 1) * 32 = 224 if the I/O memory is larger than 2 MB. Adding a bit of "comfort" space, you can configure the buffer pool by entering the following command:
buffers large permanent 230
This increases the permanent buffer pool allocation for large buffers to 230.
In general, you should boot the box, check for whichever buffer pool is depleted, and increase that one. The figures used in the preceding examples are only estimates.
To change parameters on X.25 interfaces, you must first shut down the interface.
Access control lists assigned to an AppleTalk interface using the appletalk access-group interface subcommand deny access to packets that originate at the source router. This behavior is contrary to ACL behavior for other protocols, such as TCP/IP, in which access is denied only to packets that the local router is forwarding.
Page 25-2 of the Release 9.1 Router Products Configuration and Reference mistakenly represents that Cisco's SDLLC can support IBM 5494 devices. SDLLC supports only SDLC-attached PU type 2 devices; it does not support PU type 1, PU type 2.1, PU type 4, or PU type 5 devices. However, on the Token Ring side of the SDLLC interface, it is possible to connect a PU type 4 (front-end processor) or type 5 device (host), or an AS/400 computer, which operates in PU 2.1 and host emulation modes.
Note that these restrictions do not exist with STUN (SDLC to SDLC). STUN supports any PU type running over SDLC.
When applying a SAP update delay to a Novell interface, Novell indicates that the delay should not exceed 120 ms and recommends that it be much smaller than 120 ms. Delay values in the range of 2 to 8 ms are common. If you need to use a larger SAP update delay time, you should increase the size of the input hold queue using the hold-queue length in interface subcommand.
In the Cisco 4000 4T (four-port serial module), the show interface command might display an underrun field containing a nonzero number in about one of 250,000 packets. This is normal behavior due to a known component feature.
This section describes possibly unexpected behavior by Release 9.14(12). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(12). Release 9.14(12) is a close equivalent to Release 9.1(16). This means that, in general, most 9.1(16) caveats also apply to 9.14(12).
The caveats listed here describe only the serious problems. For a complete current list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- On a Cisco 4000, the serial line suffers an input queue jam. Issuing the show interfaces command reveals about 50 buffers accumulating per week. Eventually the input queue reaches the limit of 76/75, and access across the serial link stops. This problem seems to be related to the routing of DECnet or the bridging of LAT. [CSCdi13564]
- In an environment where OSPF is redistributed into RIP and RIP into OSPF, under certain circumstances, the RIP updates are no longer interpreted by the router. Instead, they are forwarded to the gateway of last resort. [CSCdi18372]
This section describes possibly unexpected behavior by Releases 9.14(11). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(11). For additional caveats applicable to Releases 9.14(1), see the caveats sections for newer 9.14 releases. The caveats for new releases precede this section.
Release 9.14(11) is a close equivalent to Release 9.1(15). This means that, in general, most 9.1(15) caveats also apply to 9.14(11). All the caveats listed in this section are resolved in Release 9.14(12).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- A router receiving a MOP connection request through its serial port for one of its LAN port addresses responds with the LAN port's burnt-in address instead of the actual hardware address. If the requesting host uses the DECnet-style MAC address of the router in the request packet, the host will not recognize the response packet sent by the router because it identifies a different address in the "source" field. This causes the requesting host to time out on the connection request. [CSCdi26991]
This section describes possibly unexpected behavior by Releases 9.14(9) and 9.14(10). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(10). For additional caveats applicable to Releases 9.14(9) and 9.14(10), see the caveats sections for newer 9.14 releases. The caveats for new releases precede this section.
Release 9.14(9) is a close equivalent to Release 9.1(12), and Release 9.14(10) is a close equivalent to Release 9.1(14). This means that, in general, most 9.1(14) caveats also apply to 9.14(10). All the caveats listed in this section are resolved in Release 9.14(11).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- Detection and initialization of the Flash load helper logging buffer is handled incorrectly, possibly causing a "booting loop." During power up, reloading, or exception handling, the system detects the presence of the Flash load helper logging buffer by validating a magic value in the buffer header. If the magic value is present, the buffer is assumed to be present. During power cycling, the magic value can be retained in DRAM even though the contents of the buffer are invalid and parity has been lost. Logging messages to the buffer during booting results in a parity error. The system then tries to log a message to the Flash load helper logging buffer, which leads to a double bus fault. The system watchdog timer resets the system and the process repeats. The following output is displayed on the console port:
System Bootstrap, Version 4.0(8), RELEASE SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
System Bootstrap, Version 4.0(8), RELEASE SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
System Bootstrap, Version 4.0(8), RELEASE SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
System Bootstrap, Version 4.0(8), RELEASE SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
...
- The OK LED may also flash at the rate at which the system reboots. If the system showing this symptom is powered off for a minute and then powered on, it should boot correctly. [CSCdi24663]
- Setting the llc2 ack-max parameter to the value n causes the router to acknowledge every n + 1 packets. Because this value cannot be set to zero, you cannot instruct the router to acknowledge every packet. [CSCdi27034]
- If an R16M Token Ring card is administratively down and the router is reloaded or powered off and back on, the card tries to initialize its interface and is no longer administratively down. [CSCdi17976]
- When TCP/IP routing and transparent bridging are enabled on the same interface, some SNAP-encapsulated TCP/IP packets with destinations on the same network segment may be bridged to other networks. [CSCdi23944]
- In order for the routers to work with true SDLC Multidrops using IBM or IBM compatible modems and telco lines, you need to tie DCD to DSR on the remote modem connections to the PU device. This is a workaround. [CSCdi24194]
- When multiple FDDI cards are present in the router, the interfaces in the lower slot positions may lose their downstream neighbors. [CSCdi25764]
- The VINES RIF cache becomes corrupted when an end station does an all routes broadcast/nonbroadcast return. The problem is that the router returns a corrupt RIF to the end station. [CSCdi23239]
This section describes possibly unexpected behavior by Release 9.14(8). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(8). For additional caveats applicable to Release 9.14(8), see the caveats sections for newer 9.14 releases. The caveats for new releases precede this section.
Release 9.14(8) is a close equivalent to Release 9.1(12). This means that, in general, most 9.1(12) caveats also apply to 9.14(8). All the caveats listed in this section are resolved in Release 9.14(9).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- When system uptime exceeds approximately 24.45 days, AppleTalk interfaces can unexpectedly hang during restarts and never become operational. The only workaround is to reload the system. [CSCdi20052]
- A router configured as a Level 1 router sends Level 2 routing updates. [CSCdi20884]
- The netbios enable-name-cache command is not working in a topology that has two or more paths to access the workstations. The show rif command shows both paths, but the show netbios-cache command shows only one path. [CSCdi18524]
- Translational bridging of Novell IPX packets from Ethernet to FDDI and back to Ethernet fails if the source MAC address ends with 0xff. All other protocols bridge correctly with this MAC address, and all other MAC addresses bridge correctly with all protocols. [CSCdi21873]
- A bus error might occur on a Cisco 4000 router when it is connecting to a 3Com Netbuilder II, version 7.1 via a serial line configured for PPP encapsulation. The following error messages might be displayed when you enter the debug ppp command: [CSCdi22454]
LINK-2-NOSOURCE: source IDB not set, SYS-2-INLIST:Buffer in list, SYS-2-LINKED: Bad p_enqueue, and SYS-2-BADSHARE: Bad refcount in pak_duplicate.
- In OSPF, when a neighbor goes down, a host route for that neighbor is incorrectly added. A possible workaround is to trigger the rebuild of OSPF router link state advertisement by changing the interface metric or by rebooting. [CSCdi21103]
- The system might crash and reload while the route described in (c) is removed from the routing table. A combination of the following conditions causes this to happen: (a) There is a variably subnetted route; (b) Multiple routes hash into the same subnet table hash bucket; (c) There is a subnet with netnumber == major_net and mask == major_net_mask; and (d) Another subnet follows. The root cause is the same as CSCdi20345. [CSCdi18659]
- Removing a translate command from the configuration can cause other translations using the same inbound IP address to stop working. A workaround is to configure the remaining translations again by doing write memory and config memory. [CSCdi23621]
- When forwarding a StreetTalk broadcast from a server, if no routing table entry exists for the source network, the broadcast is flooded out all interfaces including the source interface. This flooding can cause broadcast storms because the packet are propogated forever. A likely cause of this problem is a bug in Banyan's SRTP implementation whereby the server stops sending compatibility updates. This condition can be fixed by applying the 5.52(5) "LJ" patch, or the 5.53(6) "LF" patch. [CSCdi22844]
- The fast-switching code does not move the entire SMDS header to the buffer for outbound SMDS traffic. The last 2 bytes are 0x0800 for IP, but the 4 bytes before that should have been an OUI of 0x00 0x00 0x00. [CSCdi21250]
- When X.25-over-TCP (XOT) sends a Call Confirm that modifies one of the two proposed flow control facilities (window sizes or maximum packet sizes), the values might be set to 0, which is illegal. [CSCdi21602]
- The original default of the ipx gns-response-delay command was 500 ms. This value fixes an issue in NetWare 2.x with dual-connected servers in parallel with a router. NetWare 2.x was the most common release. NetWare 3.x and later do not have the same issue, and a nonzero GNS response delay may cause problems in certain situations. The default of the ipx gns-response-delay command has been changed to 0. [CSCdi22285]
- Fast switching large IPX packets from a high MTU interface (like Token Ring or FDDI) to an MCI serial card might corrupt MCI memory, resulting in an "%MCI-3-SETUPERR" message. This condition can occur only for versions of IPX that use packets larger than the default 576 bytes (using LIPX or BIGPAK). [CSCdi22888]
This section describes possibly unexpected behavior by Release 9.14(7). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(7). For additional caveats applicable to Release 9.14(7), see the caveats sections for newer 9.14 releases. The caveats for new releases precede this section.
Release 9.14(7) is a close equivalent to Release 9.1(11). This means that, in general, most 9.1(11) caveats also apply to 9.14(7). All the caveats listed in this section are resolved in Release 9.14(8).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- Executing the show appletalk interface command may cause the system to restart itself. This happened on interfaces configured with many zones. [CSCdi18875]
- Under rare circumstances, the clear line command fails to clear the process running on that line. A show process command shows that the process on that line has an inappropriate and rapidly increasing number in the "invoked" column. [CSCdi16063]
- If a SAP update packet is received with an invalid length, much larger than the data actually contained in the packet, the system may reload. It is also possible, but unlikely, that invalid server entries may appear in the show ipx server table. When these packets are received, they should be counted as SAP format errors and the counter displayed by the show ipx traffic command should increment. [CSCdi19010]
- While converting from DECnet Phase IV to Phase V (and vice versa), the router holds back a converted packet once in a while and sends it out when some other event happens (for example, routing update and keepalives). This sporadic delay in packet transmission results in degradation of end-to-end DECnet performance. [CSCdi20151]
- Incorrect interface MTU negotiation occurs on any interface whose default MTU is larger than the Ethernet MTU (for example, FDDI). When a VAX comes up, the router negotiates a block size that is larger than the maximum value it can process (1524). Consequently, all adjacent routers send larger-sized updates, which the router rejects. This situation makes all destinations behind the router unreachable. [CSCdi20225]
- FEP-to-FEP local acknowledgment sessions are blocked when an SDLC-TG packet SQN=1 was delivered before a packet SQN=0. [CSCdi17904]
- If an RSRB remote peer is defined but not currently in use, the router may reload due to a software forced crash. [CSCdi17934]
- After running for an extended period of time with remote source-route bridging configured, the console may display "%SYS-2-LINKED: Bad enqueue of nnnnnn in queue nnnnn" messages. These are followed by a traceback message containing several hex numbers. RSRB continues to function normally. [CSCdi18003]
- In low-end routers such as the Cisco 4000 and Cisco 3000, the Token Ring interface ignores IP packets with single-route or an all-route broadcast RIF. [CSCdi18131]
- When source-route translational bridging is used in a dual TIC (Token Ring interface) environment, the RIF is cached for the first return explorer from the destination.If another return explorer from the same destination is later seen with a shorter RIF, the RIF cache on the router is updated. This causes the end-stations to reinitiate their sessions. The correct behavior for source-route translational bridging in a dual TIC environment is to cache the shortest RIF based on the fastest return and lock it. A timer is then started. If there is no packet from the destination and timer expires, the RIF cache for the destination is removed. Subsequently, new returns from an alternate route may be cached. If there are packets from the destination station, the RIF from the cache is applied and the timer is reset. [CSCdi18169]
- In a local acknowledgment environment, incoming disconnect packets were not handled properly and remained on the input queue. The Token Ring input queue would fill up completely and cause continuous Token Ring resetting. [CSCdi18222]
- For SDLLC, there are certain situations in which LLC2 congestion across the RSRB connection can cause the LLC transmit queue to be overrun. If this is the case, a packet that has been acknowledged on the SDLC interface can get dropped on the LLC queue and cause a session interruption. One of the symptoms of this occurring is the SNA LU-LU session ending with an UNBIND due to a skipped sequence number in the TH header. Changes have been made in the SDLLC code to allow the system to sense congestion on the LLC2 side and apply back pressure on the SDLC side by sending RNRs. The current/maximum values of the LLC transmit queue can now be displayed with the show llc2 command. The default value is 200, with a maximum of 2000 allowed. The value can be changed with the llc2 txq interface configuration command. [CSCdi18898]
- SDLLC configurations with System 88 machines may fail due to a known limitation in their ability to handle the direction bit in the RIF field. The fix modifies the router behavior to allow for this contingency. [CSCdi18921]
- 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]
- A reverse Ethernet SDLLC configuration with local acknowledgment enabled may cause a reload due to a software forced crash (jump to zero). [CSCdi19067]
- Use of the rsrb remote-peer 100 tcp n.n.n.n lsap-output-list number causes a slow memory leak under heavy RSRB load. The show process memory command will show an increasing amount of memory taken by the SRB background process. The workaround is to remove the access list and achieve the same desired behavior through the use of access lists applied on the Token Ring interfaces. [CSCdi19106]
- A configuration in which SDLLC and Reverse SDLLC are configured back to back does not work properly. A sample of this configuration would be an SDLC attached FEP going to a Token Ring through the router (Reverse SDLLC) to another router to an SDLC attached PU. This configuration is common where a TIC for a FEP is not available and the customer requires both remote SDLC and Token Ring connectivity through the router network to a single SDLC line on the host side. The fix will ensure this configuration works. The workaround is to configure STUN for SDLC attached physical units (PUs) and Reverse SDLLC for Token Ring attached PUs going to separate SDLC FEP lines on the host side. [CSCdi19148]
- Access lists of the form rsrb remote-peer nnn tcp ip address netbios-output-list host access-list-name do not function properly. The workaround is to use the same access list applied on the Token Ring interface to achieve the desired result. [CSCdi19198]
- The stun cos-enable causes unnecessary FID4 frame resequencing. The network gains no benefit and the routers are performing unnecessary work, so the feature is being removed. In addition, the feature was causing packets to be delivered out of transmission group sequence, which in rare occasions causes blocking transmission groups. [CSCdi19357]
- When the T1 timer on a multidrop SDLC line is too short, SDLC messages of the form "nn data from wrong address! got address" (where nn are SDLC poll addresses in hex) appear on the console. In a large multidrop configuration, the number of these messages is excessive. This behavior has been changed so that the messages appear only when debug sdlc is enabled. These messages are informational only, and polling of the downstream SDLC devices continues. [CSCdi19376]
- This fix allows a FEP operating as a secondary SDLC station to load a remote FEP operating as a primary SDLC station. The opposite has been possible since 9.1(9). Before a FEP is loaded with an NCP Gen, it does not have an SDLC role. The SDLC role is negotiated via XID exchange when the remote FEP is activated. [CSCdi20463]
- In systems configured to support the spanning-tree bridging protocol, the root bridge BPDUs reappear at the root bridge in a HSSI environment. [CSCdi18812]
- When transparently bridging from Token Ring to serial on a Cisco 4000, a 2-byte length field is inserted without correcting the frame size. During the copy, the last two bytes of the packet get lost. This only happens when flooding packets. [CSCdi18814]
- On Cisco 3000 series routers, when using dial-on-demand routing, a transition of CTS or DSR can appear as a transition of DCD when spoofing. [CSCdi19053]
- The router continually reports "%SYS-2-NOBLOCK: event dismiss with blocking disabled" errors preventing the router from processing other information. Reloading the router temporarily resolves the issue. [CSCdi18565]
- The default network does not work properly depending on the subnet used. [CSCdi18743]
- If an FDDI interface on a router reset via the no shut command, IP routes would be deleted from that interface. But since the FDDI ring is still in operational mode, there is no event generated to let OSPF know that routes have gone and recalculate SPF. [CSCdi19255]
- The source address-sensitive form of the distance command now works for OSPF. It formerly was silently ignored. Note that for OSPF, this command has slightly different semantics, since the source address is matched based on the router ID of the router that originated the route within the OSPF area, rather than the next-hop router. [CSCdi19369]
- The router and communication servers allow remote users to Telnet into virtual terminal line ports by connecting to ports 20xx/40xx/60xx/80xx. All the standard VTY/TTY security features, such as passwords, TACACS, and the ability to block access with the access-class in command have always been supported, even when connecting to a high port. However, since many users are unaware of this functionality, they do not take it into account when constructing packet filtering firewalls. Since this functionality can be explicitly enabled and configured by use of the virtual terminal line rotary feature, the default behavior is not necessary. This is not a security bug, but rather a behavior that should be avoided. [CSCdi20050]
- OSPF can choose and install nonoptimal interarea and external routes when there are multiple link state advertisements for the same destination advertised by multiple area border routers (or Autonomous System Boundary Routers for external routes). This can cause a routing loop if other neighboring routers still install the shortest path to the destination. This problem will happen only after the system has been up for a period of time. The length of this period depends on how much connectivity changes have occurred. In a fairly busy network, the estimated length of this period is five to six weeks. [CSCdi20071]
- After an OSPF router installed a default route to network 0.0.0.0 that is advertised in an external link state advertisement (LSA) by an autonomous system boundary router (ASBR) and a connectivity change happens in the network that triggers SPF calculation, the router will not reinstall the default route. This problem is introduced in the following software versions: 9.1(11.4), 9.17(9.2), and 9.21(3.1). There is no workaround. [CSCdi20401]
- Every time an OSPF router notices its neighbor state change on an interface (either by seeing new Hello packets or the lack of Hello packets for a RouterDeadInterval) and attempts to reoriginate its own router link state advertisement (LSA) but there is no change that needs to be reflected in the router LSA, a piece of memory of the size of the router LSA would be permanently consumed. This problem manifests itself by a slowly declining amount of free memory shown in the show memory command. There is no workaround to this problem. This problem is introduced in software version 9.1(11.5). [CSCdi20849]
- The IS does not put dynamically learned ESs over point-to-point links in the L1 LSP, so the other ISs do not have a route to that ES. [CSCdi18856]
- Beginning with 9.1(6.4), the router does not correctly honor the vines propagate command. Broadcast packets are dropped when they should be forwarded. This is most noticeable when performing a newrev command on a serverless client when a serial line separates the client and server. [CSCdi20428]
- When DDR is configured with priority queuing, a packet may get stuck in the output queue on MCI/ciscoBus serial cards and get released only when the next packet replaces it in the queue. This one-packet delay can delay packets, increasing response time or causing packet drops in case of timeout. [CSCdi17666]
- With X.25, the message "System restarted by error - Jump to zero" appears. If you issue a show stack command, you see a two-line stack trace. The cause is related to failed PAD calls; an area of memory is modified after it has been returned as no longer in use. When the load is heavy or X.25 performance is slow, this invalid reference may modify critical data, causing unpredictable results. [CSCdi17688]
- Bridged IP packets for router management are sent with the wrong size. If you are bridging IP and using IP for router management, packets sourced by the router for the second frame-relay bridge entry are truncated. [CSCdi18862]
- On outers with an ISDN BRI interface running the basic-dms100 or basic-ni1 switchtype, B-channels become unavailable if there are long dialing delays for outgoing calls through an ISDN network. Also, when a call is connected on channel B2 and the dialer idle timer attempts to hang up the call, the B-channels may become stranded and unavailable for usage. [CSCdi19671]
- When using a BRI interface as a backup interface and the backup is being done based on load, the BRI interface may be taken down prematurely even though the load is still high. [CSCdi20472]
- There is a problem with type 4 NetBIOS broadcast traffic looping in redundant topologies. The workaround is to eliminate redundancy. [CSCdi18824]
- When an output SAP delay is configured , an update is in progress, service entries are timing out (older than 4 times the SAP update interval), and a GNS request is received, the router may restart. [CSCdi20370]
This section describes possibly unexpected behavior by Release 9.14(6). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(6). For additional caveats applicable to Release 9.14(6), see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(6) is a close equivalent to Release 9.1(10). This means that, in general, most 9.1(10) caveats also apply to 9.14(6). All the caveats listed in this section are resolved in Release 9.14(7).
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, or use UniverCD as described at the end of this document.
- If source-route bridging is used, the LAN Network Manager functions such as CRS, REM, and RPS are automatically turned on. An error in the system code causes rapid accumulation of small buffers. The workaround is to put the configuration statement no lnm crs. [CSCdi16384]
- The router goes into a state where it stops sending out DECnet Level 1 routing updates. The number of Level 1 adjacencies will show 0 though the router does have adjacent Level 1 nodes. In some instances the Level 1 adjacency count will go to 65,363. The impact of this behavior is DECnet Level 1 routing breaks down. The workaround is to reinitalize the DECnet routing process in the router by removing and reentering the DECnet routing commands. [CSCdi15732]
- Due to the incorrect frame translation when SR/TLB is enabled, bridging access lists fail to stop the frame correctly. [CSCdi17037]
- During SDLLC startup, the system does not respond to the XID POLL frame sent by some upstream devices that require a response to properly bring up the LLC2 session. [CSCdi17093]
- When removing the global source-bridge ring-group configuration command, the router may crash due to an invalid memory pointer. [CSCdi17134]
- When remote source-bridging is enabled between multiple peers, one or more of the peers may be stuck in REMOPEN state. This is observable via the show source-bridging command. The correct behavior is to transit from REMWAIT to OPEN state. [CSCdi17149]
- The netbios access-list feature does not function properly for permit/deny decisions against NetBIOS names that contain special nonalphanumeric characters. The workaround is to change the NetBIOS names of the end stations to use only alphanumeric characters. [CSCdi17163]
- For an interface with SDLC encapsulation, many fields in output from the show interface command do not have units associated with them. The code fix adds units and other cosmetic changes to make the display easier to interpret. [CSCdi17210]
- A system reload may occur when attempting to remove STUN process by entering no stun peer-name ip-address. This behavior seems to occur only after the stun sessions are up and running for a while. The router won't reload if the above command is entered right after a session is established. [CSCdi17657]
- A system reload may happen while configuring source-route bridging, and a no vines routing is entered. [CSCdi17862]
- After running for an extended period of time with remote source-route bridging configured, the console may display "%SYS-2-LINKED: Bad enqueue of nnnnnn in queue nnnnn" messages. This message will be followed by a traceback message containing several hex numbers. RSRB will continue to function normally. The error message is printed under the wrong condition and can be ignored. Future versions of software will only print this message when appropriate. [CSCdi18003]
- When trying to open more than one FST remote peer version 3 connection, only one peer can open successfully. The remaining FST remote peers stay in a closed state. The workaround is to use TCP or direct encapsulation. The problem was due to an internal data structure not being initialized properly and has been fixed. [CSCdi18117]
- The old default SDLC hold queue depth of 50 is too low in some configurations and does not allow sufficient time to apply back pressure on the LLC connection before packets are dropped. The default SDLC hold queue value has been changed to 200. The value is still user configurable via the sdlc holdq interface configuration subcommand. This problem is most likely to be an issue in configurations with high-speed RSRB connectivity feeding a slow-speed SDLC line. [CSCdi18461]
- The local acknowledgment feature of remote source-route bridging sends a SABME to the end station with the incorrect direction bit set in the RIF portion of the MAC frame. The fix corrects this behavior, which existed only in interim releases between 9.1(10.1) and 9.1(10.4) inclusive. [CSCdi18617]
- Fully loaded CSC/4 terminal servers with 96 lines get wedged occasionally. [CSCdi15849]
- The FDDI trace counter can increment when there are no beacons on the ring. [CSCdi16744]
- The Cisco 4000 FDDI interface goes into administratively down status and stays there. A show interface for the FDDI includes the message "Forced FDDI shutdown when CMT rate exceeded 10358 events/sec ." A show controller FDDI displays the message "last non zero cmt rate 10358/sec, peak rate 23/sec ." This is a bug in how we determine the rate of connection management (CMT) events. In this example the actual rate never exceeded 23 per second. In early testing of the FDDI interface on the Cisco 4000, an excessive CMT rate could use up 100% of the processor and lock it up, so we checked for excessive rates and if the rate exceeded 1000/second would shut down the interface to protect the rest of the router. [CSCdi17010]
- The commands for manipulating the manual forward and discard functions of transparent bridging require fields that the manual has marked as optional. The correct behavior is to infer a "reasonable default" in the absence of an explicit optional parameter. [CSCdi17121]
- When setting queue-limits on any interface, the ciscoBus complex will reset itself. This will cause Token Rings to reinitialize. [CSCdi17646]
- In modular systems configured with CSC-1R or CSC-2R Token Ring interface cards running STRMON microcode version 1.2 or older, NetBIOS multicast traffic is not propagated when bridging from Ethernet to Token Ring to Ethernet. [CSCdi17697]
- On the Cisco 4000 platform, when routing Novell/IPX out Token Ring interfaces through source-route bridges, RIF fields may be corrupted with fast switching enabled. The workaround is to disable the Novell route-cache on the Token Ring interface. [CSCdi18492]
- When using remote source route bridging with FST encapsulation, the number of frames both in and out of a Token Ring interface are displayed incorrectly. Frames input and output through the Token Ring interface are counted twice. [CSCdi18797]
- On the 3000 series routers, when using dial-on-demand routing, a transition of CTS or DSR can appear as a transition of DCD when spoofing. [CSCdi19053]
- In a Cisco 4000, configured with three 4T NIM's, port 9 is nonfunctional. The transmit and receive ring buffer descriptors crossed page boundaries. [CSCdi19303]
- At system boot time, TACACS code dies because it fails to establish a UDP socket with which to talk to the TACACS server. [CSCdi17830]
- If the router hears ES hellos, this may cause the ISO-IGRP process to get called, though the router is not configured for ISO-IGRP. [CSCdi17079]
- IS-IS stops sending IS-IS Hellos after 49 days. This leads to loose adjacencies. [CSCdi18757]
- When using the printer option for a TCP-LAT translation, one packet erroneously remains in the input queue on the receiving interface for each translation attempt which fails. [CSCdi17681]
- Disabling vines split-horizon does not allow VINES StreetTalk broadcasts to be forwarded out an interface that they were received on. This breaks "hub-and-spoke" Frame Relay networks, because spoke StreetTalk broadcasts are not forwarded from the hub router to other spoke sites. [CSCdi17488]
- Configuring SMDS on serial lines that are shut down and subsequently reenabling them can in some circumstances cause a reload. A Token Ring interface appears to be required to trigger this problem. [CSCdi15880]
- X.25 calls received on a serial interface cannot be routed to a CMNS host. [CSCdi17212]
- After an ISDN DDR connection is already established, the line sometimes gets a DISCONNECT message from the remote end and the line drops. The only way to get the line back to where you can redial the distant end is to issue a clear int bri 0 command.[CSCdi17908]
- For incoming ISDN BRI calls, you can verify a called party number and subaddress number in the incoming setup message if it is delivered by the switch. The verification is always done if a number is configured in either an isdn answer1 or isdn answer2 command:
interface bri 0
isdn answer1 5552222:1234
- or
isdn answer2 9991111:9876
- The 5552222 and 9991111 are the called party numbers and the 1234 and the 9876 are the subaddresses. Note that the colon (:) is the separator.
- If nothing is configured, all calls will be accepted. In case one or both the answer numbers are configured, then the incoming called party number and the subaddress will be verified before accepting the call. It is possible to configure just the called party number or just the Subaddress. In such a case, only that part will be verified. The verification will proceed from right to left, for both called party number and the subaddress. It is possible to declare a digit a "don't care" digit by configuring it as an "x" or "X". In such a case, any incoming digit will be allowed. [CSCdi18425]
- A router with an ISDN BRI configured for the basic-1tr6 switch type may have problems connecting on Channel B2. An incoming SETUP message using Channel B2 can be incorrectly answered using Channel B1. This may cause the PPP protocol to keep the BRI channel interface in a Protocol-Up and Line-Down situation. It will also prevent the B2 channel from receiving any more calls. [CSCdi18562]
- Routers with an ISDN BRI interface using basic-dms100 or basic-ni1 switch types may have problems connecting to the correct B-channel if a call is made to another country and the switch responds to an outgoing SETUP message with a SETUP_ACK message. The router now uses the correct B-channel. It is also possible to append a # character to the end of the called number. This character tells the switch that no more digits follow; all the digits are in this SETUP message. The basic-net3 switch type will no longer include a Diagnostic field in an outgoing Disconnect message. This caused problems for Sweden when running basic-net3 switch type. [CSCdi18832]
- Bridged IP packets for router management are sent with the wrong size. If you are bridging IP and using IP for router management, packets sourced by the router for the second Frame-Relay bridge entry are truncated. [CSCdi18862]
- Decoding errors may occur when useing the debug isdn-event and debug isdn-q931 command on routers with an ISDN BRI interface. This occurs when new information elements are added. This case involves basic-net3 switch type and includes a "Connected Number" IE in the Connect message. This is a cosmetic error only, but the ERROR message makes it misleading. [CSCdi19054]
- Routers with an ISDN BRI interface running the basic-dms100 or basic-ni1 switch type may have B-channels become unavailable for usage if there are long dialing delays for outgoing calls through an ISDN network. Also, when a call is connected on Channel B2 and the dialer idle timer attempts to hangup the call. The B-channels may become stranded and unavailable for usage. [CSCdi19671]
This section describes possibly unexpected behavior by Release 9.14(5). Unless otherwise noted, these caveats apply to all 9.14 releases up to and including 9.14(5). For additional caveats applicable to Release 9.14(6), see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(5) is a close equivalent to Release 9.1(7). This means that, in general, most 9.1(7) caveats also apply to 9.14(5). All the caveats listed in this section are resolved in Release 9.14(6).
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, or use UniverCD as described at the end of this document.
- Multipacket responses to requests, such as RTMP Route Data Requests and ZIP GetZoneLists, can be partially lost if no AARP entry exists for the requesting node. A workaround is to populate the AARP cache before the request. Sending a ping packet from the requestor suffices. Alternatively, send the request twice. [CSCdi13758]
- Gleaning of MAC addresses from AppleTalk Phase 2 packets does not work properly on Token Ring and FDDI interfaces. A low impact workaround is to disable gleaning by issuing the command no apple gleaning on the affected interfaces. It may also be necessary to clear the AARP cache to flush out any corrupt entries. This may be done by issuing the EXEC command, clear arp. [CSCdi14227]
- When NBP BrRq and NBP FwdReq packets are converted to NBP LkUps, the source address is not preserved. This can cause access-groups to inadvertently filter out the LkUps. The workaround is to disable access-groups. [CSCdi14245]
- Devices that perform gleaning of MAC addresses from AppleTalk Phase 2 packets may experience connectivity problems. This problem can manifest itself as services on the local network appearing and disappearing in Mac Choosers. There is no workaround. An upgrade is necessary. [CSCdi14732]
- The zone list presented to an Appletalk Remote Access client may omit valid zones names. [CSCdi16652]
- Ethernet frames containing an invalid LLC header length and a DSAP equal to 0xF4 or 0x7E cause memory corruption and cause the system to reload. [CSCdi15699]
- The system fails to reply to a DO TIMEMARK when translating from Telnet to X.25. This may result in a Telnet session hang between the router and the machine sending the DO TIMEMARK. [CSCdi16405]
- The router apparently ignores the command decnet routing-timer xxx, and sends Level 2 routing updates at a higher interval. [CSCdi12802]
- There is a known memory leak when running DECnet routing. Obvious symptoms include being unable to Telnet into the router until rebooting the system, and encountering "%% Low on memory; try again later" messages when attempting to issue commands from the console port. If you look at the first page of a show memory command output over time, you will notice the amount of free memory decrease continuously. [CSCdi17083]
- When changing the bridge number of an SRB interface using LAN Network Manager platform, the router crashed. [CSCdi16403]
- OSPF does not sufficiently validate received data, which in some cases can cause system failure. [CSCdi16521]
- When an interface goes down, the system fails to poison the corresponding subnet route in RIP or HELLO routing advertisements sent out other interfaces that are part of the same major network number. The system also fails to poison a network summary route advertised by RIP or HELLO to other networks. The result is that adjacent routers must time out the corresponding route in their tables, instead of being notified of the routing change immediately. [CSCdi16698]
- The system fails to reply to a DO TIMEMARK when translating from Telnet to X.25. This may result in a Telnet session hang between the router and the machine sending the DO TIMEMARK. [CSCdi16405]
This section describes unexpected behavior and problems in Release 9.14(4) that were resolved in Release 9.14(5). For additional caveats applicable to Release 9.14(5), please see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(4) is a close equivalent to Release 9.1(7). This means that, in general, most 9.1(7) caveats also apply to 9.14(4). All the caveats listed in this section are resolved in Release 9.14(5).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- When converting NBP BrRq packets into NBP FwdReq, the system does not preserve the original DDP source address. It, instead, uses the address of the outgoing interface. This can short-circuit access-group filtering. [CSCdi13287]
- Possibly due to a condition where all valid interfaces are in a down state, TACACS (or SYSLOG, or other datagram-oriented protocols running above IP) may begin sourcing packets from a downed interface. This situation can be verified with the show ip sockets command. It can be remedied by shutting down an interface (which may already be shut down). A workaround is to assign an IP address to the loopback interface. [CSCdi12845]
- Password Authentication Protocol (PAP) is now supported. [CSCdi16253]
- A router running with IV/V conversion enabled converts any Phase IV hellos it receives and adds it to the Phase V adjacency data base. The format of this entry in the Phase V data base is recorded as "Phase IV". If a corresponding Phase V hello comes in (i.e. the other router is also running Phase V), it should overwrite the entry in the Phase V adjacency data base that was always forwarding to the final destination instead of the next hop. A IV adjacency is stored in the V adjacency data base as noted above. This info is ALSO entered into the V routing table, so that it is propagated through the OSI cloud. The caveat results in the router not updating this route, so the route would go into holddown and ultimately go away. Therefore Phase IV ES information never stays long enough in the V routing table. [CSCdi11174]
- DECnet does not accept hellos from nodes with node-address greater than the max-address configuration parameter if the hello contains an area address that is different from the router's area address. [CSCdi13136]
- The problem was simply that the system did not learn the burned-in address of the token ring adapter card until after the interface inserted onto the ring. If the interface was shutdown when the router was booted and the router was configured for bridging, the virtual ring address would be configured with the address 4000.0000.0000, which is clearly invalid. This happened because the virtual ring uses the burned-in address of the adapter, logically ORed with the 4 to obtain its unique address, which is a problem in the above scenario. [CSCdi07105]
- The LLC2 and SDLC sessions of the downstream router hang when the upstream router of a SNA link configured with SRB/SDLLC and local-ack is power cycled. The show llc2 and show interface commands on the downstream router will provide erroneous display of the LLC2 and SCLC sessions. The workaround is to reload the downstream router. [CSCdi10477]
- The router would reload with the error message of "restarted by bus error at PC 0x1ADF00. This points to the local acknowledgment routine. Turning off Local Ack functions as a workaround. [CSCdi10718]
- If a server was rebooted, it would complain about duplicate server names on the net. When the RIF times out, it would be able enter the ring. In a RSRB environment with duplicate routers on a single ring, within the same ring group packets can be placed on the ring from which they came. The routers need to have remote peer statements to each other and also have proxy explorer enabled to cause this problem. The workaround is to turn off proxy explorer, and the solution is to upgrade to 9.1(6) or above.[CSCdi11016]
- After power-cycling, RSRB peers may not renegotiate properly. The state will be OPEN, but no traffic will pass. [CSCdi12749]
- The ethernet-transit-oui standard command does not function as described in the manual for 8209 compatibility. When going from Token Ring to ethernet, with ethernet-transit-oui on the token ring interface, the router should convert all frames to Ethernet II frames, regardless of the SNAP OUI field. Instead, frames with an OUI of 000000 (all frames from an 8209) are translated to an 802.3 frame with the SNAP header intact. [CSCdi12844]
- Under heavy traffic situations, if a ring group or a remote peer is removed, the router running source-route bridging could crash when presented with explorer frames. [CSCdi13122]
- The router may fail to bridge certain protocols upon initial startup. Reloading the router will correct this condition. [CSCdi11480]
- The bridge is not forwarding broadcast packets over a bridge circuit group. The packets propagate on both serial links but are blocked at the second serial interface on the other end. The show span command will display that the second interface is in the blocking state. [CSCdi11811]
- In certain environments, the use of source-bridge proxy-explorer may cause a router to reload, reporting a "Jump to Zero" error. [CSCdi12328]
- Sending the state machine to the PCM Maintenance state using the PC_Disable signal will cause the PCM state to be "Maint" while disabled, instead of "Off" as it was before. Even tough the Cisco high-end routers also show the "Off" state while disabled, this is not consistent with the FDDI SMT standard. All Cisco routers will be consistent showing the state as "Maint" when the SMT release 7.2 code is ported to all platforms supporting FDDI interfaces. [CSCdi13653]
- The Cisco 4000 now supports the 2R NIM, a two Token Ring interface module. [CSCdi13715]
- The Cisco 3104 and Cisco 3204 incorrectly use an idle pattern of 0xFF rather than 0x7E. [CSCdi14126]
- Under extreme circumstances if autonomous switching is enabled (i.e., ip route-cache cbus is configured), the router will reload. [CSCdi12415]
- When an interface is shut down on a router running OSPF, the OSPF process will try to learn the routes through a different interface. This results in a very high CPU utilization on the router (above 95%) for a few minutes until the SPF algorithm has recalculated all the routes. [CSCdi10108]
- After a reload, an OSPF area border router fails to advertise some networks over an X.25 network. The workaround to do a shut/no shut of the X25 interface. [CSCdi13027]
- The formula for metric calculation was not correct; in particular, setting K4 to zero and K5 to 1 would make the denominator of the expression to be zero, causing a "zero error divide." [CSCdi11705]
- LAT compression fails when flooding frames, in other words when the destination mac address is not known. Issue fixed by not compressing LAT frames when destination unknown (or broadcast). Only LAT frames that do not need to be flooded (duplicated) will be compressed. [CSCdi11199]
- A protocol translator used for LAT to TCP host-initiated connections (such as printing) may run out of memory over time. [CSCdi12683]
- A Cisco router does not forward a subnet only broadcast in the same manner that a Banyan Server does. The Cisco router will forward it as a MAC layer broadcast onto the LAN segment containing the server, whereas a Banyan server will forward it directly to the server as a MAC unicast and let the server rebroadcast it. [CSCdi12555]
- When a network containing servers is configured as a serverless network, packets received on this interface that are passed through the helper code may not be returned to the free buffer pool, eventually causing the interface to stop receiving because it has exceeded the input queue count. [CSCdi12842]
- The M bit is set improperly in the last packet when the packet is full but no additional data to be sent. [CSCdi12080]
- AppleTalk fails over BRI interfaces on the Cisco 3000. The port on the far-end router never completes initialization. [CSCdi12456]
- IP over Frame Relay fast switching works only for Frame Relay ietf encapsulation. For cisco encapsulation, only process switching works. Packets from any media to Frame Relay are fast switched, but packets from Frame Relay to any media are process switched. This seems to have been introduced in 9.14(2.3) when CSCdi12764 was fixed. The workaround is to use FR-IETF encapsulation, or use 9.14(2) with either cisco or Frame Relay ietf encapsulation. [CSCdi13283]
- Issuing the dialer rotary-group command should not be allowed to be entered for BRI interfaces. [CSCdi13901]
- Added National ISDN 1 support for the 3000 line of routers that support BRI interfaces. This is configured by the isdn switch-type basic-ni1 command. [CSCdi14573]
- Due to a parsing error, the interface subcommand frame-relay lmi-type ANNEX D is not accepted. This occurs even when the system is reading a configuration file written by the software, as from nonvolatile memory. A workaround is to load a configuration file at boot time containing the alternative form, frame-relay lmi-type ansi, which is accepted. [CSCdi15175]
- The Cisco 2500 series with ISDN BRI interfaces has been homologated for NET3 and 1TR6 switch types. The NET3 information elements were expanded to include other countries that use the NET3 standard, such as New Zealand. [CSCdi15356]
- When applying an extended access list, packets using IPX packet type 4 (PEP) are forwarded only when there is already an entry in the IPX route cache for this IPX destination. If there is no entry or if IPX route caching has been turned off, no frames are forwarded. The access list itself works fine but devices trying to communicate using PEP-packets seem to get filtered. [CSCdi11730]
- The system may reload if a Novell or XNS route is being removed from the routing table at the same moment the show novell route or show xns route is accessing that information from the routing table. [CSCdi12101]
- If a Novell SAP update is received which has more than the normal seven services per frame advertised and all those services are new, there is a strong possibility that memory will be corrupted. [CSCdi12108]
- The optional behavior of the rip-check command as of CSCdi09056 is now the default. To disable RIP-check handling of RIP requests, use the no novell rip-check. Two new counters have been added to the show novell traffic display: SAP format errors and RIP format errors.If these counters are incrementing on a router, you should investigate which client is sending malformed RIP requests by enabling debug novell-rip-event. This command displays information about the next packet that arrives; it also displays information about other RIP events that may be interesting. Enabling debugging may cause unwanted overhead on the router. You may also want to use an analyzer. [CSCdi12244]
- If the Novell routing information is displayed while in the process of being updated, then the system may reload. [CSCdi12736]
- When responding to a RIP request from a NetWare 3.1x/4.x server/router, the response is sent to an incorrect MAC address (0000.0000.0001) and therefor is never received. This will only happen on NetWare devices which use an internal network number, a response to normal NetWare Client is sent to the correct MAC address. [CSCdi13400]
- With Novell fast switching, when multiring is enabled, the DSAP SSAP values get corrupted. The workaround is to disable Novell route-cache on the Token Ring interface. [CSCdi15182]
This section describes unexpected behavior and problems in Release 9.14(3) that were resolved in Release 9.14(4). For additional caveats applicable to Release 9.14(4), please see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(3) is a close equivalent to Release 9.1(7). This means that, in general, most 9.1(7) caveats also apply to 9.14(3). All the caveats listed in this section are resolved in Release 9.14(4).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- When converting NBP BrRq packets into NBP FwdReq, the system does not preserve the original DDP source address. It, instead, uses the address of the outgoing interface. This can short-circuit access-group filtering. [CSCdi13287]
- Possibly due to a condition where all valid interfaces are down , TACACS, SYSLOG, or other datagram-oriented protocols running above IP may begin sourcing packets from a downed interface. To verify this situation, use the show ip sockets command. To remedy it, shut down an interface (if it is not already down). A workaround is to assign an IP address to the loopback interface. [CSCdi12845]
- DECnet does not accept hellos from nodes with node address greater than the max-address configuration parameter if the hello contains an area address that is different from the router's area address. [CSCdi13136]
- The system did not learn the burned-in address of the Token Ring adapter card until after the interface inserted onto the ring. If the interface was shut down when the router was booted and the router was configured for bridging, the virtual ring address would be configured with the address 4000.0000.0000, which is clearly invalid. This happened because the virtual ring uses the burned-in address of the adapter, logically ORed with the 4 to obtain its unique address, which is a problem in the above scenario. [CSCdi07105]
- The LLC2 and SDLC sessions of the downstream router hang when the upstream router of a SNA link configured with SRB/SDLLC and local acknowledgment is power-cycled. The show llc2 and show interface commands on the downstream router will provide erroneous display of the LLC2 and SDLC sessions. The workaround is to reload the downstream router. [CSCdi10477]
- The router reloads with the error message of "restarted by bus error at PC 0x1ADF00." This points to the local acknowledgment routine. Turn off local acknowledgment functions as a workaround. [CSCdi10718]
- After power-cycling, RSRB peers may not renegotiate properly. The state will be OPEN, but no traffic will pass. [CSCdi12749]
- The ethernet-transit-oui standard command does not function as described in the manual for 8209 compatibility. When going from Token Ring to Ethernet with ethernet-transit-oui on the Token Ring interface, the router should convert all frames to Ethernet II frames, regardless of the SNAP OUI field. Instead, frames with an OUI of 000000 (all frames from an 8209) are translated to an 802.3 frame with the SNAP header intact. [CSCdi12844]
- The router may fail to bridge certain protocols upon initial startup. Reloading the router will correct this condition. [CSCdi11480]
- The bridge is not forwarding broadcast packets over a bridge circuit group. The packets propagate on both serial links but are blocked at the second serial interface on the other end. The show span command will display that the second interface is in the blocking state. [CSCdi11811]
- In certain environments, the use of source-bridge proxy-explorer may cause a router to reload, reporting a "Jump to Zero" error. [CSCdi12328]
- When an interface is shut down on a router running OSPF, the OSPF process will try to learn the routes through a different interface. This results in a very high CPU utilization on the router (above 95%) for a few minutes until the SPF algorithm has recalculated all the routes. [CSCdi10108]
- The formula for metric calculation was not correct; in particular, setting K4 to zero and K5 to 1 would make the denominator of the expression to be zero, causing a "zero error divide." [CSCdi11705]
- After a reload, an OSPF area border router fails to advertise some networks over an X.25 network. The workaround to do a shut/no shut of the X25 interface. [CSCdi13027]
- If a network is set up such that two or more routers are connected to a LAN segment containing a server, and the router interfaces connected to that LAN segment have been configured as serverless, then it is likely that there will be a broadcast storm. The workaround is to correctly configure the routers by removing the serverless specification on the interfaces that have servers connected to them. [CSCdi11991]
- Under certain rare conditions, heavily congested lines may lose PPP keepalive packets. [CSCdi10691]
- The M bit is set improperly in the last packet when the packet is full but no additional data to be sent. [CSCdi12080]
- The fix submitted for CSCdi12849 is incomplete; X.25 INTERRUPT packets are still mishandled in switched VCs. [CSCdi13369]
- The dialer rotary-group command should not be allowed to be entered for BRI interfaces. [CSCdi13901]
This section describes unexpected behavior and problems in Release 9.14(2) that were resolved in Release 9.14(3). For additional caveats applicable to Release 9.14(3), please see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(2) is a close equivalent to Release 9.1(6). This means that, in general, most caveats fixed in 9.1(6) were also fixed in 9.14(2). All the caveats listed in this section are resolved in Release 9.14(3).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- This correction prevents 32808 bytes from being lost each time a write memory command is executed on systems which utilize the MC or MC+ NVRAM board for its NVRAM configuration. [CSCdi11659]
- Changes made to support the AutoInstall feature may result in the router displaying console messages such as "Booting network-confg..." These messages are cosmetic only. [CSCdi12394]
- A router running with IV/V conversion enabled converts Phase IV hellos and adds them to the Phase V adjacency database. In the Phase V database, these entries are recorded as "Phase IV." If a corresponding Phase V hello arrives, it should overwrite the entry in the Phase V adjacency database. A IV adjacency is stored in the V adjacency database. This information is also entered in the V routing table so that it is propagated through the OSI cloud. The result is that the router does not update this route, so the route goes into holddown and is ultimately removed. [CSCdi11174]
- The system did not learn the burned-in address of the Token Ring adapter card until after the interface inserted onto the ring. If the interface was shut down when the router was booted and the router was configured for bridging, the virtual ring address would be configured with the address 4000.0000.0000, which is invalid. This happened because the virtual ring uses the burned-in address of the adapter, logically ORed with the 4 to obtain its unique address. [CSCdi07105]
- The LLC2 and SDLC sessions of the downstream router hang when the upstream router of a SNA link configured with SRB/SDLLC and local-ack is power cycled. The show llc2 and show interface commands on the downstream router will provide erroneous display of the LLC2 and SDLLC sessions. The workaround is to reload the downstream router. [CSCdi10477]
- The router reloads with the error message "restarted by bus error at PC 0x1ADF00." As a workaround, disable Local Ack functions. [CSCdi10718]
- The router may fail to bridge certain protocols upon initial startup. Reloading the router corrects this condition. [CSCdi11480]
- The bridge is not forwarding broadcast packets over a bridge circuit group. The packets propagate on both serial links but are blocked at the second serial interface on the other end. The show span command will display that the second interface is in the blocking state. [CSCdi11811]
- Using the source-bridge proxy-explorer command may cause a router to reload, reporting a "Jump to Zero" error. [CSCdi12328]
- Under extreme circumstances if autonomous switching is enabled with ip route-cache cbus, the router reloads. This is most likely to occur when the tables used to maintain the autonomous switching cache becomes large. This might happen if a large numbers of hosts are on a single interface. [CSCdi12415]
- When an interface shuts down on a router running OSPF, OSPF tries to learn the routes through other interfaces. This results in a high CPU utilization (above 95%) for a few minutes until the SPF algorithm can recalculate the routes. [CSCdi10108]
- The formula for metric calculation was not correct; in particular, setting K4 to zero and K5 to 1 would make the denominator of the expression to be zero, causing a "zero error divide." [CSCdi11705]
- A Cisco router does not forward a subnet only broadcast in the same manner that a Banyan server does. The router forwards it as a MAC layer broadcast onto the LAN segment containing the server, whereas a Banyan server forwards it directly to the server as a MAC unicast and lets the server rebroadcast it. [CSCdi12555]
- The M bit is set improperly in the last packet when the packet is full but no additional data to be sent. [CSCdi12080]
- A Cisco 3104 or 3204 can be configured with a VN3 switch type. This is necessary to operate properly in a France ISDN network. [CSCdi12527]
- A Cisco 3000 with an ISDN BRI interface with the switch type set for NET3 may lose call control blocks. Calls will not be made and if the ISDN debugs are enabled, a HOST_DISCONNECT_ACK message may be displayed. [CSCdi12529]
This section describes unexpected behavior and problems in Release 9.14(1) that were resolved in Release 9.14(2). For additional caveats applicable to Release 9.14(3), please see the caveats sections for newer 9.14 releases. The caveats for newer releases precede this section.
Release 9.14(1) is a close equivalent to Release 9.1(5). This means that, in general, most caveats fixed in 9.1(5) were also fixed in 9.14(1). All the caveats listed in this section are resolved in Release 9.14(2).
The caveats listed here describe only the serious problems. For a complete list of caveats against this release, access CIO as described in the section "Cisco Information Online" later in this document, or use UniverCD as described at the end of this document.
- The no exec-banner command is documented in the router software manual, but is implemented only on communication servers. [CSCdi11290]
- Under heavy traffic loads, the SDLC T1 timer may expire prematurely. This can be seen in multidrop circuits where the T1 timer is set to 1. The cause is the delay between when the T1 timer is set in the software and when the packet is sent on the line. As packets are queued at the interface, the delay becomes significant. The sdlc line-speed rate interface subcommand has been added to compensate for this delay. The argument rate is in bits per second. For DCE, rate should be the same as theclock rate on the interface. For DTE, rate should be the clock rate on theDCEdevice to which DTE is connected. [CSCdi09719]
- The Token Ring interface was sending ring status messages to the LAN manager when it was in the DOWN state. The status messages are valid only after the interface has begun the insertion process. [CSCdi10364]
- If the IP MTU is set to less than the interface MTU, packets will be process-switched rather than fast-switched. [CSCdi09453]
- On the Cisco 4000, if one of the FDDI neighbors has a duplicate MAC address, the FDDI interface transitions endlessly. [CSCdi09807]
- When bridging between more than two locations on X.25 (that is, multiple x25 map commands), multicasts on some logical channels have the Ethernet header (addresses and type) truncated. Unicasts are not effected by this problem. There is no workaround. Users encountering this problem are advised to contact the Cisco TAC for upgrade information. [CSCdi10063]
- FDDI SIF and SRF station management frames can contain an incorrect value for tvx, the FDDI valid transmission time. [CSCdi10191]
- There is a window in which commands to the interface get dropped. The fix is to protect against interrupts when issuing commands. In this case, the system drops the command to throttle the interface. When the system later tries to unthrottle the interface, it can get passed random pointer values to the interfaces shared memory. Also, store the throttle count in idb and display in show controller. [CSCdi11046]
- When IP directed broadcast packetsare received, the system erroneously attempts to resolve the directed broadcast address via HP Probe address resolution broadcasts. This occurs if the directed broadcast is destined for a directly connected interface, and that interface is configured for arp probe. The system then also correctly forwards the directed broadcast as a data link layer broadcast (if not disabled via the no ip directed-broadcast command). The system should send the directed broadcast as a data link layer broadcast out the directly connected interface, but should not attempt to perform address resolution on the IP-directed broadcast address. [CSCdi09627]
- When the system attempts to add connected routes for an interface's primary and secondary IP addresses, it may fail to add some of the routes for the secondary addresses. This failure occurs if the interface state changes from up to down while the system is in the process of establishing the connected routes for the interface. This problem is most readily seen for connected routes on an FDDI interface, and OSPF is being used. You may need to defer the specification of the interface's secondary IP addresses until the interface's state has stabilized. [CSCdi09744]
- On routers with Token Ring interfaces, enabling OSPF using the following commands may cause the router to execute an immediate system reload:
- router ospf ospf-process-id
network address wildcard-mask area area-id
- There is no workaround. Users wishing to use OSPF under these circumstances are advised to call the Cisco TAC for more information. [CSCdi10488]
- If many hundreds of subnets are being transmitted via IGRP, the router's performance router may be impaired. The general symptom is extremely long delays through the router when routing updates occur. [CSCdi11284]
- The router rejects IS-IS packets when more than one SNPA with the same address is present in the CLNS neighbor table. This can be determined with the debug clns-routing command. [CSCdi10931]
- When clns route-cache is enabled (default) and a DECnet Phase IV adjacency has been established, for the Phase IV-Phase V conversion routine can forward Phase V packets (CLNS) to the Phase IV end system. This results in a loss of connectivity when the Phase IV end system attempts to connect to a Phase V host. A workaround is to disable CLNS route caching via the no clns route-cache command. However, this may slow performance. [CSCdi10980]
- For "encapsulation DDNX25," DDN Precedence facility is allowed in X25 CALL CONNECTED frames. The DDN Precedence must agree with that of the X25 CALL REQUEST frame. [CSCdi11405]
- When adding static SAP entries, the SAP Flash updates indicate the wrong hop count. When the correct hop count is sent in the periodic updates, neighbor routers think the topology has changed and place the service into hold down, timeout, and flash an advertisement of hops equal 16 before advertising the correct hop count. [CSCdi10834]
- When bringing up an interface that has been down since system startup on a router running with xns ub-emulation configured for over four weeks, the newly installed XNS interface does not send UB XNS RIP packets after the initial update at interface startup. A workaround is to briefly turn off xns ub-emulation and then turn xns ub-emulation back on. This may cause a couple minutes of UB route disruption on routes using this router. [CSCdi11543]
Cisco Information Online (CIO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CIO to obtain additional content and services.
Available 24 hours a day, 7 days a week, CIO provides a wealth of standard and value-added services to Cisco's customers and business partners. CIO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CIO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously--a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CIO (called "CIO Classic") supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CIO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CIO in the following ways:
- WWW:
http://www.cisco.com.
- Telnet:
cio.cisco.com (198.92.32.130).
- Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100, N81, up to 14.4 kbps.
For a copy of CIO's Frequently Asked Questions (FAQ), contact ciohelp@cisco.com. For additional information, contact cioteam@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or
tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or
csrep@cisco.com.
The complete caveats against this release are available on UniverCD, which is Cisco Systems' library of product information on CD-ROM. On UniverCD, access the System Software Release 9.14 Caveats in the System Software Release 9.1 database.
