Cisco Cisco IOS Software Release 12.2

Page de 292
29
Caveats for Cisco IOS Release 12.2
OL-3513-16 Rev. G0
  Resolved Caveats—Cisco IOS Release 12.2(31)
Resolved Caveats—Cisco IOS Release 12.2(31)
This section describes possibly unexpected behavior by Cisco IOS Release 12.2(31). All the caveats 
listed in this section are resolved in Cisco IOS Release 12.2(31). This section describes severity 1 and 2 
caveats and select severity 3 caveats.
The following information is provided for each caveat:
Symptoms: A description of what is observed when the caveat occurs. 
Conditions: The conditions under which the caveat has been known to occur. 
Workaround: Solutions, if available, to counteract the caveat.
IBM Connectivity
CSCeh18295
Symptoms: DLSw circuits do not connect.
Conditions: This symptom is observed when DLSw Ethernet redundancy is configured via the dlsw 
transparent switch-support
 command.
Workaround: Recycle DLSw on the master router.
Further Problem Description: The output of the show dlsw transparent cache command shows the 
NEGATIVE state for the circuits on the master router although no actual circuits exist on either the 
master router or the slave router. 
CSCeh90809
Symptoms: Removing BSTUN peer attribute causes a Cisco router to crash.
Conditions: This symptom occurs when changing the bstun protocol- group protocol name global 
configuration command and subsequently changing the bsc char-set value (from ascii to ebcdic or 
vice versa) on the BTSUN encapsulated interface. The router will crash.
Workaround: There is no workaround. 
Miscellaneous
CSCea84387
Symptoms: A user session may pause indefinitely, causing a Cisco router to become unresponsive.
Conditions: This symptom is observed when multiple simultaneous users enter modular QoS CLI 
(MQC) commands on the same router via separate vty sessions.
Workaround: Allow only one user at a time to enter MQC commands. 
CSCeb47225
Symptoms: If a key is configured on a tunnel interface, the inbound access-list on that interface is 
ignored. 
Conditions: This problem is seen with a configuration that is similar to the following:
interface Tunnel0
 ip address 192.168.1.1 255.255.255.0
 ip access-group 100 in
 tunnel source FastEthernet0/0