Guest

Cisco IOS Software Releases 12.2 SR

Cross-Platform Release Notes for Cisco IOS Release 12.2SR: Caveats for 12.2(33)SRD through 12.2(33)SRD8

  • Viewing Options

  • PDF (3.2 MB)
  • Feedback
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8

Table Of Contents

Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8

Resolved Caveats—Cisco IOS Release 12.2(33)SRD8

Resolved Caveats—Cisco IOS Release 12.2(33)SRD7

Resolved Caveats—Cisco IOS Release 12.2(33)SRD6

Resolved Caveats—Cisco IOS Release 12.2(33)SRD5

Resolved Caveats—Cisco IOS Release 12.2(33)SRD4

Resolved Caveats—Cisco IOS Release 12.2(33)SRD3

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2a

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2

Open Caveats—Cisco IOS Release 12.2(33)SRD1

Resolved Caveats—Cisco IOS Release 12.2(33)SRD1

Open Caveats—Cisco IOS Release 12.2(33)SRD

Resolved Caveats—Cisco IOS Release 12.2(33)SRD


Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8


Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in this section.

Because Cisco IOS Release 12.2SR is based on Cisco IOS Release 12.2, many caveats that apply to Cisco IOS Release 12.2 also apply to Cisco IOS Release 12.2SR. For information on severity 1 and 2 caveats in Cisco IOS Release 12.2, see the Caveats for Cisco IOS Release 12.2 document located on Cisco.com.

In this section, 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.


Note If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Support: Tools & Resources: Bug Toolkit (which is listed under Troubleshooting). Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.)


This section consists of the following subsections:

Resolved Caveats—Cisco IOS Release 12.2(33)SRD8

Resolved Caveats—Cisco IOS Release 12.2(33)SRD7

Resolved Caveats—Cisco IOS Release 12.2(33)SRD6

Resolved Caveats—Cisco IOS Release 12.2(33)SRD5

Resolved Caveats—Cisco IOS Release 12.2(33)SRD4

Resolved Caveats—Cisco IOS Release 12.2(33)SRD3

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2a

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2

Open Caveats—Cisco IOS Release 12.2(33)SRD1

Resolved Caveats—Cisco IOS Release 12.2(33)SRD1

Open Caveats—Cisco IOS Release 12.2(33)SRD

Resolved Caveats—Cisco IOS Release 12.2(33)SRD

Resolved Caveats—Cisco IOS Release 12.2(33)SRD8

Cisco IOS Release 12.2(33)SRD8 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD8 but may be open in previous Cisco IOS releases.

CSCtf71673

Symptoms: A Cisco router shows a PRE crash.

Conditions: This issue is seen when the system is configured for PTA and L2TP access and is running Cisco IOS Release 12.2(34)SB4 during a pilot phase.

Workaround: There is no workaround.

CSCtg48785

Symptoms: The following error may appear in the log:

%DATACORRUPTION-1-DATAINCONSISTENCY: copy error,

Conditions: This issue occurs while issuing show x25 hunt-group command when a large amount of x25 traffic needs to traverse the device.

Workaround: Do not use the show x25 hunt-group command.

CSCtr28857

A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.

Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp

CSCtr91106

A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.

Products that are not running Cisco IOS Software are not vulnerable.

Cisco has released free software updates that address these vulnerabilities.

The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.

This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai

CSCts38429

The Cisco IOS Software Internet Key Exchange (IKE) feature contains a denial of service (DoS) vulnerability.

Cisco has released free software updates that address this vulnerability. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-ike

Resolved Caveats—Cisco IOS Release 12.2(33)SRD7

Cisco IOS Release 12.2(33)SRD7 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD7 but may be open in previous Cisco IOS releases.

CSCsw77313

Symptoms: After a successful login to a router, issuing the login command with a different username may result in the session appearing to execute with the new username even if the login attempt is unsuccessful. The new username will be reported by commands such as show users, and it will be used in AAA processing and reporting. The privilege level of the new user is not changed. It stays at the privilege level of the original user.

Conditions: The symptom is observed with authorization enabled with the aaa authorization configuration command.

Workaround: Use "aaa authorization" to disable the login exec command.

CSCtg26538

Symptoms: After applying a CoPP policy any traffic that would arrive at the CPU with an MPLS label is not classified and is classified in the class-default.

Conditions: This symptom will be seen for any traffic arriving at the CPU with a MPLS label. The easiest manifestation of this would be to use a loopback in a VRF for management. Any traffic destined to or sourced from that loopback interface will not match the expected CoPP policy classification. For example:

interface loopback0

ip vrf forwarding red

ip address 192.168.1.1 255.255.255.255

!

access-list 101 permit ip any host 192.168.1.1

!

class-map loopback-traffic

match access-group 101

!

policy-map loopback-copp

class loopback-traffic

police 8000

!

control-plane

service-policy in loopback-copp

Any traffic destined to the loopback0 interface will be classified in class-default class.

Workaround: There is no workaround.

CSCti45732

Symptoms: Upon a reload, a Cisco 7600 series router configured as VTP server may lose some VLANs from its VLAN database.

Conditions: The VLANs lost do not have any access ports in the device. All other switches in the network should be in VTP transparent mode. This issue is seen on a Cisco 7600 series router that is running Cisco IOS 12.2(33)SRE1 and SRE2 Releases.

Workaround: Configure the Cisco 7600 as VTP transparent instead of VTP server.

CSCto43154

Symptoms: A Cisco device running Cisco IOS may reload unexpectedly with the following message:

%SYS-2-CHUNKBADREFCOUNT: Bad chunk reference count, chunk <address> data <address> refcount FFFFFFFF alloc pc <address>

Conditions: This symptom is observed on Cisco device running Cisco IOS.

Workaround: There is no workaround.

CSCtq81391

Symptoms: Standby supervisor (on a router in SSO mode) crashes upon bootup in Cisco IOS Release 12.2(33)SRD5.

Conditions: This symptom happens when the router has multicast scale configurations, with 50+ OIFs, and 30k+ IGP routes. When active supervisor performs bulk sync, due to memory corruption issue, standby supervisor crashes.

Workaround: Boot the router in RPR+ mode.

CSCtr37182

Symptoms: XAUI coding errors are seen on the console.

Conditions: This symptom is observed on a Cisco 7600 series router.

Workaround: There is no workaround.

CSCtr70073

Symptoms: Multicast traffic is affected, and the PIM neighborship goes down.

Conditions: This symptom is seen when the IPv6 address family is configured in the IPv4 MVRF.

Workaround: Remove the IPv6 address family from the MVRF. Save the configurations and reload the router.

CSCtr74529

Symptoms: The following error messages are displayed:

%ENVM-DFC3-4-LONGBUSYREAD: C2W Interface busy for long time reading temperature

sensor 1

%ENVM-DFC2-4-LONGBUSYREAD: C2W Interface busy for long time reading temperature

sensor 2

Conditions: This symptom is not caused by any specific conditions.

Workaround: There is no workaround.

CSCts51980

Symptoms: STM1-SMI PAs of version 3.0 do not come up.

Conditions: This symptom is observed when the new version of PAs do not come up with enhanced flexwan.

Workaround: There is no workaround. Without the PA, flexwan will come up.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD6

Cisco IOS Release 12.2(33)SRD6 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD6 but may be open in previous Cisco IOS releases.

CSCta77064

Symptoms: Crashinfo file is not generated.

Conditions: This symptom occurs when SIP600/ES20 line cards crash.

Workaround: There is no workaround.

CSCtc84960

Symptoms: Traffic is not forwarded in LSM P2MP setup. This problem is seen after the router is booted up.

Conditions: The problem is seen in LSM P2MP on a HA setup.

Workaround:

1. The problem can be prevented by configuring tunnel mpls traffic-eng fast-reroute on the P2MP tunnel interface.

2. Use non HA setup.

3. Reset the ingress line card.

4. Program the fpoe table by using "test fpoe index index value value" or "test fpoe index index restore".

Further Problem Description: P2MP tunnels do not forward the traffic on head end after the reload because the FPOE is programmed incorrectly. Here we see the traffic hitting the tunnel interface but not the outgoing physical interface. FPOE is not getting populated due to empty port lists.

CSCtd10712

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCth25634

Symptoms: The password is prompted for twice for authentication that is falling over to the line password.

Conditions: This symptom is observed when login authentication has the line password as fallback and RADIUS as primary. For example:

aaa authentication login default group radius line

Workaround: Change the login authentication to fall back to the enable password that is configured on the UUT. For example:

enable password keyword 
aaa authentication login default group radius enable

Further Information: The fix for this bug also fixes an unrelated problem that may allow unauthorized users access to EXEC mode if the "line" authentication method is configured with fallback to the "none" authentication method. In other words, if the following is configured:

aaa new-model 
aaa authentication login MYMETHOD line none
 
   
line con 0
  login authentication MYMETHOD
  password some password
 
   

then users providing the wrong password at the password prompt will be granted access.

This issue was originally introduced by Cisco Bug ID CSCee85053, and fixed in some Cisco IOS releases via Cisco Bug IDs CSCsb26389 ("Failover for aaa authentication method LINE is broken") and CSCsv06823 ("Authentication request does not failover to any method after enable"). However, the fix for this problem was not integrated into some Cisco IOS releases and this bug (CSCth25634) takes care of that.

Note that Cisco Bug ID CSCti82605 ("AAA line password failed and access to switch still passed") is a recent bug that was filed once it was determined that the fix for CSCee85053 was still missing from some Cisco IOS releases. CSCti82605 was then made a duplicate of this bug (CSCth25634) since the fix for this bug also fixes CSCti82605.

CSCth69364

Cisco IOS Software contains a memory leak vulnerability in the Data-Link Switching (DLSw) feature that could result in a device reload when processing crafted IP Protocol 91 packets.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-dlsw.shtml.

CSCtj22457

Symptoms: ISSU fails with config sync failure mcl.

Conditions: This symptom is seen during the commitversion of ISSU.

Workaround: There is no workaround.

CSCtj38606

Symptoms: The following error message is seen:

%SYSTEM_CONTROLLER-3-MISTRAL_RESET: System Controller is reset:Normal Operation 
continues

The show ibc exec command reports increments of the following counter:

Hazard Illegal packet length = 7580

Conditions: The symptom is observed on a Cisco 7600 series router.

Workaround: There is no workaround.

CSCtj53299

Symptoms: Met corruption issue is observed.

Conditions: This symptom occurs during OIF churn.

Workaround: Use the clear ip mroute command for the problematic entry.

CSCtj70282

Symptoms: VRF ping does not work.

Conditions: This symptom is seen with one or more VRFs with MDT tunnels existing on the router. In that case any application like unicast VRF, SwEoMPLS, and VPLS may be affected if they use the same VLAN.

Workaround: There is no workaround.

CSCtj94358

Symptoms: SIP400 will pass the traffic through a previously configured VLAN on reconfiguring the bridge-domain command.

Conditions: This symptom is seen with the egress interface that is a SIP400 with MPB configured.

Workaround: Remove the "bridge-domain" configuration and then add the new "bridge-domain".

CSCtj95032

Symptoms: PIM packets are dropped at SIP400. As a result PIM neighborship is not formed between the CEs.

Conditions: This symptom is seen when the egress interface is on SIP400 with bridging configured on it.

Workaround: There is no workaround.

CSCtj96489

Symptoms: In a CISCO 7600 router, a freshly provisioned interface, or an interface which has been administratively no shut, belonging to non-default VRF, may fail to forward traffic.

Conditions: This is a race condition and hence timing sensitive.

Workaround: Another interface shut/no shut may help restore service.

CSCtk02155

Symptom: Attachment to the CHOC3 SPA console fails after seeing VC configuration command failures.

Conditions: This symptom is seen with CHOC3 SPA on SIP200 or SIP400.

Workaround: Reset the line card.

Further Problem Description: The periodic process resyncs the IPC between the host and CHOC3 SPA. As this is not happening, we are not able to attach to the SPA console.

CSCtk07369

Symptoms: The buginf statement "draco2_fastsend: PAK_BUF_ON_OBL processing vlan" appears on the console.

Conditions: This statement is displayed in certain cases, such as multicast replication.

Workaround: There is no workaround.

CSCtk34380

Symptoms: Router may crash during many additions/deletions of MVRFs and/or during SSO switchover.

Conditions: This symptom is observed on a Cisco 7600 series router with MVRFs added/deleted in MVPN scenario.

Workaround: There is no workaround.

CSCtk36377

Symptoms: VRF ping fails for some of the VRFs after deleting and adding MVRFs.

Conditions: This symptom is seen when adding and deleting MVRFs using a script.

Workaround: Delete VRF and add it back.

CSCtk36897

Symptoms: Crash is observed.

Conditions: This symptom occurs while unconfiguring "no ipv6 mld snooping".

Workaround: There is no workaround.

CSCtk47960

Symptoms: Large CLNP packets may be dropped when forwarded over SIP- 200/Flexwan2 module. Header Syntax errors may be recorded on receiving host.

Remote side will generate the following:

%CLNS-3-BADPACKET: ISIS: L1 LSP, packet (902) or wire (896) length invalid

Conditions: This symptom is seen on Cisco 7600 switch with SIP-200 line card that is running Cisco IOS 12.2(33)SRD3 and later releases.

Issue is seen when packets larger than 911 bytes are sent (Payload and Header).

Workaround: If CLNS is only used for ISIS neighborships "no isis hello padding" can be configured to establish ISIS neighborship. For the LSP packets, configure lns-mtu 903 under router isis on the Cisco 7600 to make this work.

CSCtk83760

Symptoms: Met updates from SUP are reaching Cisco 67xx DFC cards.

Conditions: This symptom is observed during OIF churn. This is not reproduced locally, and the fix is put in as a sort of preventive mechanism.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD5

Cisco IOS Release 12.2(33)SRD5 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD5 but may be open in previous Cisco IOS releases.

CSCed11719

Symptoms: A switch is learning MAC addresses from the wrong port.

Conditions: This symptom occurs on a dot1q trunk that is connected to that switch port with one of the subinterfaces configured for bridging.

Workaround: There is no workaround.

CSCsg99677

Symptoms: Crashinfo collection to a disk filesystem will fail and generate the following error message:

File disk#:crashinfo_20070418-172833-UTC open failed (-1): Directory entries are 
corrupted, please format the disk

Or the crashinfo file will be stored as CRASHI~1.

Conditions: This symptom is observed with normal crashinfo collection to a disk filesystem.

Workaround: Configure the crashinfo collection either to a network filesystem (such as tftp or ftp) or to a local filesystem of type "flash". Configuring to a local filesystem is a preferable option.

CSCsk48102

Symptoms: Supervisor crashes due to an address error on the switch processor:

Address Error (load or instruction fetch) exception, CPU signal 10

Conditions: This appears to be a very rare random occurrence that only occurs in devices that have uptime over one year. In some cases, the devices were up for over two years before encountering this.

Workaround: There is no workaround.

CSCsm97014

Symptoms: MLPoFR with the member group interface as crackerjack PA (PA-MC-2T3-EC) is configured. On applying a simple policy along with RTP header compression virtual template, the connectivity breaks.

Conditions: This is seen across PA (PA-MC-2T3-EC) and on applying both header compression and QoS policy.

Workaround: There is no workaround.

CSCso50205

Symptoms: If a SSM static mapping command is used and router processes SSM groups outside the configured static SSM mapping range, routers fall to DNS-based look to find SSM mapping. If DNS servers are not reachable or DNS servers are not configured to provide mapping, input interface Q builds up leading to control plane instabilities affecting other protocols.

Conditions: This symptom occurs when DNS-based SSM mapping and DNS servers are not reachable.

Workaround: If SSM mapping information is never fetched from a DNS server, configure no ip igmp ssm-map query dns.

If DNS is used, ensure that DNS servers are always reachable and also have low DNS query timeout value.

CSCso60442

Symptoms: A crash occurs.

Conditions: This symptom is observed when the show buffers interface dump command is entered.

Workaround: There is no workaround.

CSCsr39340

Symptoms: Packets may be dropped.

Conditions: This symptom is observed if the core interface for AToM is a GRE tunnel.

Workaround: There is no workaround.

CSCsv70157

Symptoms: On a Cisco 7609 router that is running Cisco IOS Release 12.2(33)SRD, after configuring any interface with any carrier-delay value other than 0 (the default), upon entering wr mem you get an unexpected warning message:

"Warning: Overriding existing carrier delay value to 0"

Conditions: There appears to be no special conditions to reproduce this defect. Simply configure any interface with a carrier delay and execute wr mem:

Router#conf t
      Enter configuration commands, one per line.  End with CNTL/Z.
      Router(config)#int f2/12
      Router(config-if)#carr
      Router(config-if)#carrier-delay 2
      Router(config-if)#end
      Router#wr
      Building configuration...
      Warning: Overriding existing carrier delay value to 0
  
  %SYS-5-CONFIG_I: Configured from console by console[OK]
      Router#

Workaround: There is no workaround.

Further Problem Description: This warning should come when Asymmetric Carrier Delay (ACD) is configured on an interface and you then attempt to configure Standard Carrier Delay via the carrier-delay delay interface command. However, the message is coming when ACD is not configured.

CSCsv73506

Symptoms: If a port member of a Port-channel interface comes up after a service instance with bridge-domain is created, it may not join spanning tree for the VLAN corresponding to the bridge-domain.

Conditions: Unknown at this time.

Workaround: Perform a shut and no shut under the service instance.

CSCsx56362

Symptoms: BGP selects paths which are not the oldest paths for multipath. This causes BGP to unnecessarily flap from multipath to non-multipath as a result of route flaps.

Conditions: The symptom is observed when:

1. BGP is configured.

2. More than one equally-good route is available.

3. BGP is configured to use less than the maximum available number of multipaths.

Workaround: There is no workaround.

CSCsx78789

Symptoms: A router crashes in the presence of MQC samplers.

Conditions: The symptom is observed only when MQC samplers are applied to the interface, when the configurations are applied in a particular order.

Workaround: Use NetFlow random samplers.

CSCsy47987

Symptoms: After an RP switchover occurs, some PPP interfaces remain up/down until the router is reloaded or the encapsulation is changed to HDLC.

Conditions: The symptom is observed on a Cisco 10000 series router with dual PREs when some PPP interfaces are up and some are down after a PRE switchover. In addition, the "interface resets" counter on the problematic interface will increment.

Workaround: Change the encapsulation to HDLC or try issuing the command clear ppp interface.

CSCsy56433

Symptoms: The sh rommon rp command for the standby intermittently fails to display the correct information for the ROMMON regions. This issue occurs intermittently and is not easily reproducible.

Conditions: This issue was also hit during the ROMMON upgrade with Cisco IOS on standby, although this is not easily reproducible. After selecting F1 as the preferred region on the standby and resetting it, although ROMMON upgrade was successful as observed on the standby console, the sh rommon command on the active displays that both regions were invalid.

The following steps provide the details that cause the reported behavior:

1. Upgrade the standby ROMMON F1 region.

2. Upgrade the standby F2 region.

3. The sh rommon command displays that both F1 and F2 are approved, with F2 region as the preferred region. To choose the F1 as the preferred region, issue upgrade rom slot 8 rp preference region1.

4. Then issue a HW reset to ensure that F1 region is the preferred region.

5. As expected, the RP boots up with the upgraded ROMMON. Displays that the ROMMON is running from the F1 region.

6. When the sh rommon slot 8 rp command is issued, instead of displaying F1 and F2 as approved regions, with F1 also as preferred region, the command displays that both regions are invalid, but indicates that the ROMMON is running from the F1 region.

Workaround: There is no workaround.

CSCsy61321

Symptoms: Accounting requests sent to the TAC server do not fail over to the second server.

Conditions: This symptom is observed when two TACACS servers are configured, the first without TACACS, the second with TACACS, and authentication is configured as "none".

Workaround: Use a single working server, or ensure that the first group uses a valid server.

CSCsy83266

Symptoms: A router experiences CPU hog or crashes when doing snmpwalk.

Conditions: This symptom is observed when interfaces are attached with a large-scale police configuration (for example, a two-level policy map, 200 (parent classes) x 15 (child classes) = 3000 policers).

Workaround: There is no workaround for walking the table. To get a specific entry, use snmpget.

CSCsy88764

SymptomS: ISG PPPoE sessions may lose their authenticated state if they receive Change of Authorization (CoA) for service swapping.

Conditions: After sending CoA pushes to deactivate an existing service and active new one to ISG PPPOE sessions, the sessions may change state from authenticated to connect. It means the sessions are already in logoff state. As a result, all Subscriber Service Switch (SSS) showings are empty.

Workaround: There is no workaround.

CSCsz23099

Symptoms: A memory leak is experienced and a higher number of loadinfo is allocated, which can be seen by using the show ip cef loadinfo command.

Conditions: The symptom is observed with a router that is running Cisco IOS Release 12.2(33)SRD1 and that is configured with PBR with next-hop with reachablity that is moving between one path and two paths.

Workaround: There is no workaround.

CSCsz87710

Symptoms: The RPF is enabled by default on a newly created SVI/loopback interface, which is causing ping failure. See the following example:

switch(config)#int vlan 1103
  switch(config-if)#mtu 9216
  switch(config-if)#ip add
  switch(config-if)#ip address 172.16.2.1 255.255.255.0
  switch(config-if)# logging event link-status
  switch(config-if)# mpls ip
  switch(config-if)#no sh
  
  switc#sh ip interface vlan 1103
  Vlan1103 is up, line protocol is up
    Internet address is 172.16.2.1/24
    ::: ::::::::       :::::::::::::::::::::::
    BGP Policy Mapping is disabled
    Input features: uRPF, MCI Check   <<<<<<<<<< RPF is enabled by default
    Output features: IP Post Routing Processing, HW Shortcut Installation
    Post encapsulation features: MTU Processing, IP Protocol Output Counter, 
IP 
  Sendself Check, HW Shortcut Installation
   
  Router#ping 172.16.2.1
  
  Type escape sequence to abort.
  Sending 5, 100-byte ICMP Echos to 172.16.2.1, timeout is 2 seconds:
  .....
  Success rate is 0 percent (0/5)

Conditions: This symptom occurs when RPF is enabled on the interface for the first time. Delete the interface. Create the interface again with the same name.

Workaround: There is no workaround.

CSCta18596

Symptoms: The following tracebacks and messages appear on the console logs:

%ALIGN-3-SPURIOUS: Spurious memory access made at 0x61AB0C78 reading 0x22 
%ALIGN-3-TRACE: -Traceback= 61AB0C78 623849E8 62384A58  
607CCD8C 61372428 613769FC 61376E68 613773C4

In addition, you may see instability of the serial interfaces (i.e.: when an interface is configured, it stays up for a while and then goes down).

Conditions: The symptoms are observed when upgrading to Cisco IOS Release 12.2(31)SB14 on a Cisco 7200 series router only on the interfaces configured with frame-relay fragmentation configured on the main interface.

Workaround 1: Use fragmentation in the map-class with FRTS (i.e.: configure "frame-relay traffic-shaping" under the main interface and configure fragmentation under the map-class and apply the map-class to PVC). For example:

interface Serial1/0.1/1/4/2:0
  no ip address
  encapsulation frame-relay IETF
          ...
  frame-relay traffic-shaping
  frame-relay lmi-type ansi
  frame-relay intf-type dce
  no clns route-cache
  max-reserved-bandwidth 100
 !
 interface Serial1/0.1/1/4/2:0.101 point-to-point
          ...
  frame-relay interface-dlci 101   
   class BANKOFIRE-S1/0.1/1/4/2:0.101-SR611638725
  
 map-class frame-relay BANKOFIRE-S1/0.1/1/4/2:0.101-SR611638725
  frame-relay cir 768000
  frame-relay mincir 768000
  no frame-relay adaptive-shaping
  service-policy input BANKOFIRE-IN-S1/0.1/1/4/2:0
  service-policy output BANKOFIRE-OUT-S1/0.1/1/4/2:0
  frame-relay fragment 600
 !

Workaround 2: Make sure that the fragmentation size is different in different interfaces (with interface fragmentation).

CSCta22221

Symptoms: Frame relay client triggers reload of standby router.

Conditions: This symptom occurs if many frame relay related configurations are present.

Workaround: There is no workaround.

CSCta58068

Symptoms: During BGP convergence, a CPU spike may be seen on the local PE in an MVPN configuration.

Conditions: The symptom may be observed with the following conditions:

Remote PE neighbor switchover.

On local PE, do a clear ip bgp bgp nbr.

On bring up of local PE.

Large configurations, such as one with 300 MDT default tunnels.

The following is an example of an MVPN configuration where this problem can be seen:

1. OSPF routing protocol is enabled on all the networks in the topology.

2. Each PE router has 100 MVRFs defined (between vpn_0 to vpn_99).

3. MDT default is configured on all the mVRFs on the PE routers.

4. PE routers have an iBGP session, ONLY with the RR (route-reflector).

5. eBGP session exists between the Routem and PE1, with Routem sending 200,010 VPNv4 routes.

6. OSPF session also exists between Routem and PE1, with Routem sending 100 OSPF routes.

In effect, the following states are present in the network:

On PE and RR routers:

1. IGP states = 100 OSPF routes.

2. BGP states = 200,010 VPNv4 routes.

On PE routers ONLY:

1. VRF sessions = 100 VRFs (vpn0 to vpn_99).

2. MDT sessions = 100 SSM sessions.

Workaround: There is no workaround.

CSCta59022

Symptoms: On configuring auto-tunnel primary onehop and auto-tunnel backup together, the router crashes because of a stack overflow.

Conditions: This symptom occurs when configuring mpls traffic-eng auto-tunnel and backup together

Workaround: Configure auto-tunnel primary and wait for 10 seconds for primary to come up and then configure auto-tunnel backup.

CSCta69118

Symptoms: The ping from CE1 to CE2 fails when VLAN xconnect is provisioned, even though the session is up.

Conditions: The symptom is observed with Cisco IOS Release 12.4(20)T4.

Workaround: There is no workaround.

CSCtb17507

Symptoms: A crash will be seen at cfib_prefix_create_rews ().

Conditions: This symptom occurs with high scaled configuration with multiple show and no show while installing the routes into hardware.

Workaround: There is no workaround.

CSCtb23840

Symptoms: CPU HOG traceback messages may be seen when using a time-based ACL for QoS matching. The CPU hog will be printed when the time-range becomes active, or goes inactive. During the time-range active or inactive transitions, a CPU spike will be seen.

Conditions: This symptom is seen when using a time-based ACL for QoS matching.

Workaround: There is no workaround.

CSCtb47647

Symptoms: Active RP crashes at pim_send_join_prune.

Conditions: The symptom is observed when performing some PIM-related testing with specific configurations and after carrying out an SSO. When you attempt to debug memory leak issue using a memory traceback recording command, the router crashes while executing the command show memory traceback exclusive.

Workaround: There is no workaround.

CSCtb50757

Symptoms: The router may crash.

Conditions: This symptom is observed when interfaces used by ISIS routers as nexthop are deleted.

Workaround: Disable interfaces used by ISIS routes as nexthop before deleting them.

CSCtb73450

Symptoms: Start-Control-Connection-Request (SCCRQ) packets may cause tunnel to reset after digest failure.

Conditions: This symptom is observed when the SCCRQ packets are sent with an incorrect hash.

Workaround: There is no workaround.

CSCtb86439

Symptoms: Slow memory leak occurs on Cisco Intelligent Services Gateway (ISG) during normal operations.

Conditions: Leak is observed if there is some error condition such as a mis-configuration in the user or service profile.

Workaround: There is no workaround.

This ddts needs to double commit to mcp_dev first, then commit to rls6. Now mcp_dev is doing some regression and scaling testing.

CSCtb92791

Symptoms: The command ip ospf message-digest-key in interface mode may have an invalid key.

Conditions: The symptom is observed when "parser config cache interface" is configured.

Workaround: Use the command no parser config cache interface.

CSCtc27221

Symptoms: Complete traffic that is switched through TE tunnels will be punted to RP causing high CPU and will see traffic loss.

Conditions: This symptom is seen while testing TE-FRR.

Workaround: There is no workaround.

CSCtc35103

Symptoms: ES+ switchport stops forwarding after initial configuration.

Conditions: This symptom is seen with switchport configuration on ES+ and only sometimes.

Workaround: Remove and reapply the configuration.

CSCtc51539

Symptoms: A Cisco router crashes with a "Watch Dog Timeout NMI" error message.

Conditions: This symptom is observed only on devices configured with Bidirectional Forwarding Detection (BFD). For further information on BFD, consult the following link:

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html

Workaround: Disable BFD.

CSCtc69991

Symptoms: A Cisco ASR 1000 Series Aggregation Services router configured as a DMVPN spoke may throw tracebacks.

Conditions: The symptom is observed when "odr" is configured as the overlay routing protocol and a shut and no shut is done on the tunnel interface.

Workaround: Use EIGRP as the overlay routing protocol.

CSCtd08797

Symptoms: MPLS packets are software switched when port-channel interfaces are the MPLS interfaces. Affects tag-to-tag traffic.

Conditions: Issue is seen after the router is upgraded to Cisco IOS Release 12.2(33)SRD3. The MTU for the MLS CEF adjacency for the MPLS label is misprogrammed and shows up as 0. Should see "MTU failures" incrementing in show mls stat.

Workaround: Flap the interface.

CSCtd24840

Symptoms: There might be collisions during switchover leading to a critical "SCP find master quiesce" message getting dropped.

Conditions: The symptom is observed with the presence of SIP400 and 67xx cards.

Workaround: There is no workaround.

CSCtd38225

Symptoms: When ISG is enabled and DHCP sessions re-start just around the time their leases expire, some sessions may get stuck dangling indefinitely. Sending DHCPDISCOVER message (i.e.: re-starting the CPE) will not restore the session. The affected subscriber(s) will not be able to establish a session.

Conditions: The issue seems to be a corner-case situation. It is observed when ISG is enabled and DHCP sessions re-start just around the time their leases expire.

Workaround: The only known workaround is to manually clear the dangling session(s) using the clear ip subscriber dangling time command although this may not be a suitable workaround in a live production network.

CSCtd67010

Symptoms: A Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD3 may crash in process "Ethernet OAM".

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD3. It is not necessary to have Ethernet OAM configured.

Workaround: There is no workaround.

CSCtd73256

Symptoms: A Cisco Catalyst switch may reload while issuing the show ip ospf int command.

Conditions: The symptom is observed when the show ip ospf int command is paused while the backup designated router neighbor goes down, for example:

c3560sw2#show ip ospf int
 Vlan804 is up, line protocol is up 
   Internet Address 10.0.0.2/24, Area 0 
   Process ID 1, Router ID 10.0.0.2, Network Type BROADCAST, Cost: 1
   Transmit Delay is 1 sec, State DR, Priority 1
   Designated Router (ID) 10.0.0.2, Interface address 10.0.0.2
  --More-- 
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8,
 changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan804, changed
 state to down
%OSPF-5-ADJCHG: Process 1, Nbr 10.0.0.1 on Vlan804 from FULL to DOWN,
 Neighbor Down: Interface down or detached
%LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to down

The next line that will be displayed in the "show ip ospf int" output will be the following:

Backup Designated router (ID) 10.0.0.1, Interface address 10.0.0.1

If at this point you press enter or spacebar to advance the output, the device will reload and the following error message will be shown:

Unexpected exception to CPUvector 2000, PC = 261FC60

Workaround: There is no workaround.

CSCtd74135

Symptoms: Microsoft Point-to-Point Encryption (MPPE) enforcement may not work on a Cisco router. The router may allow Point-to-Point Tunneling Protocol (PPTP) users to connect without negotiating the MPPE.

Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 15.0(1)M even if it is configured with the ppp encrypt mppe 128 required command.

Workaround: Using the authentication type of MS-CHAP in place of MS-CHAP-V2 can prevent this issue. The MPPE works fine with the required option as well, when used with the authentication type "MS-CHAP".

CSCtd93508

Symptoms: SIP-200 goes into crashing loop with the following messages in the log:

%R4K_MP-3-CRASHED: CPU 1 has now crashed a total of 11 times. SYS-3-INTPRINT: Illegal 
printing attempt from interrupt level.  
-Process= "CPU Monitor", ipl= 5, pid= 54

This secondary crash happens because of primary crash in the QoS code, which happens when high priority traffic is flowing through QoS enabled interfaces of a particular SPA.

Conditions: From the crashed system the SPA used was "SPA-1XCHSTM1/OC3 (0x463)". Other SPAs may be affected.

The trigger is just the flow of priority traffic through this interface with the following policy attached to that serial interface:

policy-map child
    class pri
       priority percent 4%
    class bw
      bandwidth percent 25%
    class class-default
     bandwidth percent 71%
  
  policy-map parent
     classs class-default
     shape average < > kbps
     service-policy child.
 
   
policy-map parent classs class-default shape average < > kbps service-policy child.

Note: Any flavor of priority like priority, priority percent, priority kbps can trigger this error condition.

Workaround: Replacing the priority percent with bandwidth percent will solve the crash, but traffic is not properly prioritized:

policy-map child
    class pri
       bandwidth percent 4%      <<<< priority to bandwidth
    class bw
      bandwidth percent 25%
    class class-default
     bandwidth percent 71%

CSCtd94144

Symptoms: Ethernet OAM packets are not terminated locally.

Conditions: This is seen only when xconnect is configured under main interface for l2tpv3 tunneling. This is not applicable for VLAN mode l2tpv3.

Workaround: There is no workaround.

CSCte00934

Symptoms: If configuration loss occurs after bootup due to ROMmon bug CSCsq77835, copying startup-config running-config followed by the write memory command does not always fix the problem.

Conditions: This symptom is seen with corruption of SLOTCACHE ROMmon variable reenter cwan configuration-card type, controller and interface configuration write mem.

Workaround: OIR the CWAN card, reenter cwan configuration and write memory.

CSCte02089

Symptoms: IP DSCP is rewritten to 0 after disposition on PE.

Conditions: This symptom occurs when unconfiguring and adding a VRF back for packets exiting out of an interface having ip vrf receive configured.

Workaround: There is no workaround.

CSCte03083

Symptoms: With queuing policy attached on MFR, removing "encapsulation frame- relay" on the physical interface puts the interface in inconsistent state. "Encapsulation frame-relay" cannot be reconfigured on the physical interface.

Conditions: This symptom is see when QoS is in place.

Workaround: There is no workaround.

CSCte10706

Symptoms: When you configure FRF.12 "frame-relay fragment 512 end-to-end" on the serial interface, the router crashes.

Conditions: The symptom is observed when you configure FRF.12 "frame-relay fragment 512 end-to-end" on a CJ-PA.

Workaround: There is no workaround.

CSCte10790

Symptoms: A Cisco Catalyst 6500 series switch may unexpectedly reload due to bus error on the switching processor when making access list entry config changes or when removing an entire access-list.

Conditions: This bug fixes two related crashes. One in which the crash occurs when making ace configuration changes and another when removing an entire ACL.

Details on the conditions to trigger the crash when making the ace configuration changes:

This can be reproduced in all the branches and the basic criteria reproducing this is we should have ACE is greater than 13, and we should have the extended ACE that has destination IPADDR.

The issue is seen when we have more that three ACE which have the same source and destination address and mask and we delete the ACE in sequence like:

no 110
no 120
no 130

Then try to add ACE which has the same source address and mask but no destination. The infinite loop will result in crash.

120 ACE
130 ACE
CRASH will happen

Follow the same order:

ip access-list extended vlan959-out
 permit ip 10.227.128.52 0.0.0.3 any
 remark - Standard out ACL -
 permit tcp any any established
 deny   tcp any any eq 707
 deny   tcp any eq 707 any
 deny   tcp any any eq 4444
 deny   tcp any eq 4444 any
 deny   udp any any eq 31337
 deny   tcp any any eq 12345
 deny   tcp any any eq 12346
 deny   tcp any any eq 20034
 deny   tcp any any eq 7597
 deny   ip host 0.0.0.0 any
 remark - allow cns & UFAD networks
 permit ip 10.227.212.0 0.0.0.255 any
 permit ip 10.227.212.0 0.0.0.255 any
 permit ip 10.228.212.0 0.0.0.255 any
 permit ip 10.249.10.0 0.0.0.255 any
 permit ip 10.227.128.52 any
 permit ip 10.5.187.240 0.0.0.15 any
 permit ip 10.241.28.240 0.0.0.15 any
 permit ip 10.227.128.112 0.0.0.3 any
 permit udp 10.227.128.0 0.0.0.255 eq ntp 10.241.33.0 0.0.0.255
 permit udp 10.227.128.0 0.0.0.255 eq domain 10.241.33.0 0.0.0.255
 permit tcp 10.227.128.0 0.0.0.255 eq domain 10.241.33.0 0.0.0.255
 permit tcp 10.227.156.0 0.0.0.255 host 10.241.33.11 eq www
 permit tcp 10.227.128.0 0.0.0.255 host 10.241.33.29 eq cmd

Then follow the order:

no 110
no 120
no 130
120 permit udp 10.227.128.0 0.0.0.255 eq domain any
130 permit tcp 10.227.128.0 0.0.0.255 eq domain any

Workaround: The ACE configuration change crash can be worked around by deleting the entire ACL and then add the resequenced ACE.

The crash when removing the access-list itself has no workaround.

CSCte38945

Symptoms: Unable to get ping reply from the multicast group configured on loopback interface.

Conditions: The symptom can occur when there are multiple routes populated in an interface and the interface goes down. All the routers associated with the interface should be removed, but only one is deleted. This results in the ping failure.

Workaround: Shut down the other interfaces associated with the router and enable it again.

CSCte48877

Symptoms: On configuring a PVC on main interface or subinterfaces and then configuring xconnect under it, causes the standby sup to have a negative circuit id that is retained even after the switchover.

The PVC gets a negative circuit id.

VCs do not come up and all the xconnects are down with Cisco 7600 image. Cisco IOS Release 12.2(33)SRE has the same issue.

Conditions: See the following sample show output when this happens:

PE1#sh atm pvc 11/900
 ATM3/0/0: VCD: 4095, VPI: 11, VCI: 900
 UBR, PeakRate: 149760 (353208 cps)
 AAL5 L2transport, etype:0x1B, Flags: 0x1861, VCmode: 0x0, Encapsize: 4
 OAM Cell Emulation: not configured
 Interworking Method: like to like
 AC Type: ATM AAL5,  Circuit Id: -2146761852<<,  AC State: UP,  Prov: YES
 Switch Hdl: 0x1FF7FFB,  Segment hdl: 0x3FEDFF6
 AC Hdl: 0xC7010FE0,  AC Peer Hdl: 0xF4010FE1,  Flg:0,  Platform Idx:4093
 Remote Circuit Status = No Alarm, Alarm Type = None
 Local Circuit Status = No Alarm, Alarm Type = None
 InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
 InPRoc: 0, OutPRoc: 0, Broadcasts: 0
 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
 InPktDrops: 0, OutPktDrops: 0
 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, 
 CPIErrors: 0
 Out CLP=1 Pkts: 0
 OAM cells received: 0
 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
 OAM cells sent: 0
 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutAIS: 0, F5 OutRDI: 0
 OAM cell drops: 0
 Status: UP

Workaround: There is no workaround.

CSCte49283

Symptoms: Sometimes the LNS router sends an incorrect NAS-Port value.

Conditions: The symptom is observed when the LNS router sends a stop accounting-request to the RADIUS server.

Workaround: There is no workaround.

CSCte49641

Symptoms: On ES+, policy map is attached to subinterface on main or port- channel. Traffic is not being marked with CoS value specified in the policy map, and it is always propagated from dscp/precedence of the packet.

Conditions: This symptom is seen when attaching CoS marking policy map to subinterface on main or port-channel of ES+ LC, Cisco 7600 router, enable the mls qos command. Traffic is not being marked with CoS value specified in the policy map, and it is always propagated from DSCP/precedence of the packet.

Workaround: There is no workaround.

Further Problem Description: On routed interfaces, ES+ mark the packet as "trust dscp" even when ingress marking of CoS is configured ("set cos 0-7") in the policy map. Because of this, CoS value is always propagated from dscp/prec.

CSCte74705

Symptoms: A Cisco 7600 router that is running Cisco IOS Release 12.2(33)SRD may generate L2 Queue Error (%L2-SP-4-QUEER) messages when a link down/up event occurs across multiple interfaces in a short period of time.

Conditions: This symptom may occur when a large number of attachment circuits are configured with EVC style configuration, and a large number of MAC addresses are known to the system.

Workaround: There is no workaround.

CSCte78165

Symptoms: Device may reload when the show ip protocol command is issued.

Conditions: The symptom is observed when routing protocol is configured and the ISIS routes are being redistributed.

Workaround: Do not use the show ip protocol command.

CSCte79777

Symptoms: There is a CPU hog and the router crashes.

Conditions: The symptom is observed when the syslog is configured with a "logging discriminator", for example:

logging discriminator TB msg-body includes Trace 
 logging trap debugging
 logging host 1.1.1.1 discriminator TB

Workaround: Remove "discriminator" from syslog (e.g.: replacing "logging host 1.1.1.1 discriminator TB" with "logging host 1.1.1.1").

CSCte91656

Symptoms: Flooding of traffic for known unicast MAC on the VPLS VCs seen after FRR cutover, reopt, or SSO switchover.

Conditions: The symptom is observed with ES-20 as the access interfaces and having port-channel member interfaces. It is seen when you configure "ve EVC under port-channel" with bridge domain and VPLS configuration.

Workaround: Flap the pseudowire.

CSCtf00132

Symptoms: A Cisco 7200 series router crashes when there are unauthenticated sessions in a multichassis SGBP environment.

Conditions: The symptom is observed when multiple unauthenticated sessions in a multichassis multilink PPP SGBP environment are dialed from the same client on multiple home gateways as part of the same session.

Workaround: There is no workaround.

CSCtf06442

Symptoms: The newly active supervisor on a Cisco 7600 router with SSC-400 may crash shortly after SSO failover due to a large amount of traffic causing system instabilities.

Conditions: This behavior is seen on a Cisco 7600 router that is running Cisco IOS Release 12.2(33)SRC5.

Workaround: Configure MLS rate limiters to prevent RP from being overwhelmed, which may prevent the router from crashing.

CSCtf06486

Symptoms: SSO failover may be delayed by approximately 10 seconds when SSC- 400 is present in chassis.

SSC-400 is not SSO aware. However other line cards may be affected by this.

Conditions: The following error message can be seen:

oir_enable_switching_for_modules_replied: Slot: 7 (nonEMS20g) took > 10000 ms extra to 
reply

Workaround: There is no workaround.

CSCtf07513

Symptoms: A Cisco 10000 series router crashes when removing loopback interface while sessions are up and TCP traffic is flowing.

Conditions:

1. Reproducible under scalable scenario.

2. Sessions should have PBHK feature.

3. TCP traffic should be flowing.

4. Loopback interface sourcing address to PBHK is removed.

Workaround: Do not remove loopback interface before stopping traffic.

CSCtf09260

Symptoms: On a Cisco 7600 that is running Cisco IOS Release 12.2(33)SRD3 that has a Multilink PPP group configured on interfaces residing on an OSM- 1CHOC12/DS0, performing a shut followed by a no shut on the parent Multilink interface may result in the removal of a service-policy output command if the policy-map contains shape average with a rate greater than the rate of a single Multilink PPP member link. The condition may also be triggered by the following:

1. When you shut and no shut on the remote Multilink interface, an event that could be replayed during a telco event if all members fail.

2. When you remove all member links either locally or on remote peer, which results in local Multilink down.

Conditions: This issue occurs on Cisco 7600/OSM-1CHOC12/DS0 that is running Cisco IOS Release 12.2(33)SRD3.

1. Problem does not happen if shape average rate is less than single_member_link_rate.

2. Problem does not happen with a flat queueing policy attached to Multilink interface.

3. Problem does not happen with SIP-200 and SIP-400 with various SPA modules.

Workaround: Manually re-apply the service-policy output command.

CSCtf12803

Symptoms: The command to configure overhead accounting on an ES+ module is not available.

Conditions: The symptom is observed with an ES+ module.

Workaround: There is no workaround.

CSCtf15927

Symptoms: L2TPv3 session traffic stops flowing following an SSO failover.

Conditions: The symptom is observed only when the local and remote end have different cookie configurations for the L2TPv3 session, followed by an SSO failover.

Workaround: Clear the tunnel manually.

CSCtf16623

Symptoms: On a Cisco 7600 ES+, the internal VLAN tag is incorrectly inserted into VC-type 4 frames.

Conditions: The symptom is observed with basic functioning.

Workaround: There is no workaround.

CSCtf20154

Symptoms: Max VTemplate limit on RSP720 is 200 and cannot go beyond this number.

Conditions: This symptom is specific to RSP720.

Workaround: There is no workaround.

Further Description: This limit is seen on RSP720. The limit for SUP720 is 1000.

CSCtf22243

Symptoms: High adjacency usage is seen in stats/non-stats region.

Conditions: This symptom is observed when VPNV4 prefixes are getting load balanced across even number of TE Tunnels that are FRR protected.

Workaround: Change the load-balancing mode to simple and use the clear ip bgp neighbor * command.

CSCtf22968

Symptoms: IP multicast cannot be L3-switched between two routed pseudowires.

Conditions: The symptom occurs when routed pseudowire is the ingress and egress interface for multicast traffic, and an ES20+ is the exit line card. IP unicast traffic is not affected.

Workaround: There is no workaround.

CSCtf27303

Symptoms: On a Cisco router, a BGP session for a 6PE (peer-enabled in AF IPv6 and end-label configured) with a third-party router, which does not advertise capability IPv6 unicast (not AFI 2 SAFI 1, only AFI 2 SAFI 4) may be torn down right after it establishes, as the Cisco router sends out an update in the non-negotiated AF IPv6 unicast (AFI/SAFI 2/1).

Conditions: The symptom is observed under the following conditions:

Cisco side: session enabled for IPv6 + send-label. Cisco router is running Cisco IOS Release 12.2(33)XNE1 and Release 12.2(33)SRE.

Third-party: only capability IPv6 labeled unicast advertised.

Workaround: There is no workaround.

CSCtf29654

Symptoms: Ingress plus egress traffic on ES-20 line card traffic is spanned. The total output traffic span destination interface is much less than aggregate traffic at ingress.

Conditions: This symptom is seen in Cisco 7600 router having ES-20 as ingress line card and trying to monitor huge amount of traffic of more than 5 Gbps.

Workaround: There is no workaround.

CSCtf33203

Symptoms: Supervisor crashes due to RPC communication failure SP-RP.

Conditions: This symptom is observed when high temperature is seen on entire device. One module crosses alarm threshold which generates minor error RPC message.

Workaround: There is no workaround.

CSCtf35224

Symptoms: When using Cisco IOS Release 12.2(33)SRD3, UDP broadcast traffic cannot be forwarded correctly through flexwan line card of the Cisco 7600. There are some count values that are increasing on serial interface of brand router, but there was no output from the debug ip packet command on brand router.

Conditions: When using Cisco IOS Release 12.2(33)SRD3 based on below topology, UDP broadcast traffic cannot be forwarded correctly using the ip helper-address x.x.x.x command.

2800-4(Pagent)[F0/0] <---------> [Gi6/2] 7600-2 [S4/0/0:1] <----Serial back-
to-back-----> [S0/3/0:1] 2800-5
 Traffic Pattern from Pagent is below.
- tgn L3-src-addr 10.1.1.2
- tgn L3-dest-addr 192.168.234.255
- tgn L4-src-port 1234
- tgn L4-dest-port 1234

Workaround: When using Cisco IOS Release 12.2(33)SRC1, UDP broadcast traffic can be forwarded correctly using the ip helper-address x.x.x.x command.

CSCtf39455

Symptoms: Router can hang when xconnect configuration is modified on a VLAN subinterface while data packets are being switched. The following error traceback is printed:

%SYS-2-NOTQ: unqueue didn't find 0 in queue

Conditions: The symptom is observed when the VLAN subinterface is still seeing data traffic and the main interface is not shut down, and when the xconnect configuration on the VLAN subinterface is being modified.

Workaround: Shut down the main ethernet interface when doing xconnect configuration changes on the subinterface.

CSCtf44529

Symptoms: PPPATM session does not come up on its own after switchover.

Conditions: This symptom occurs when DLFIoATM is configured along with RPR+.

Workaround: Use the shutdown command followed by the no shutdown command on the ATM interface.

CSCtf48413

Symptoms: MLS CEF entries for default route are not getting reprogrammed for default routes after a LC reload. This issue is there when default route is getting resolved through MPLS TE tunnels with FR objects, and one of the LC through which MPLS TE tunnel passes through crashes.

Conditions: This symptom occurs when default route is reachable through more than one mpls te tunnels with FR objects. When one of the LC resets (through which MPLS TE tunnel is passing through), FR object backwalk is not fixing the adjacency properly.

Workaround: This issue happens only in LC reset cases. This will usually not happen in customer networks. Fix by flapping the MPLS TE FRR back up tunnel.

CSCtf50862

Symptoms: Upon the router bootup in steady state, MAC addresses (both core and access side) are flushed out periodically resulting in traffic flooding across all ports.

Conditions: The symptom is observed when MAC OOB is enabled by the following command: mac-address-table synchronize.

If you have EVC-PC on access, VPLS in the core, and traffic flow is asymmetric, this can result in flooding of the traffic from access to core and core to access.

Workaround: Use the clear mac-address-table dynamic command on the RP.

CSCtf50894

Symptoms: During the collection process an interrupt is raised by a higher priority event (topology change, i.e.: a tunnel shutdown). If the tunnel shutdown occurs at a very precise time before the collection is complete, data structures used by FRR collection end up being deleted/altered by the higher priority event. When the suspended FRR statistics collection process resumes, it ends up working with data that has become stale/trashed. This results in a crash.

Conditions: The symptom is observed on an MPLS TE FRR enabled router that will trigger periodic collection of accounting information for all prefixes using a given TE tunnel as its next-hop. This process is invoked in 10 second intervals and it can be suspended by other higher priority processes before its runtime completion.

Workaround: Disable FRR protection.

CSCtf51332

Symptoms: An interface with PBR/VRF select configuration punts all traffic to the RP and causes high CPU usage. When MLS rate-limiter is configured, there might be packet losses at higher rate of traffic.

Conditions: When a PBR/VRF-select route-map is removed from the first interface on which the PBR/VRF select was configured, the internal RSVD VLAN is removed. This causes the packets from all interfaces with this route-map to be punted to the RP.

Workaround 1: Disable VPN-CAM lookup.

Workaround 2: Configure identical route-maps with different names, for example:

route-map sak-vrfs-in1 permit 10
       match ip address SAK-PAM-SOURCES
       set vrf sak-pam
      !
       route-map sak-vrfs-in1 permit 20
       match ip address SAK-VOIP-SOURCES
       set vrf sak-voip
      !
      
  
       route-map sak-vrfs-in2 permit 10
        match ip address SAK-PAM-SOURCES
        set vrf sak-pam
       !
       route-map sak-vrfs-in2 permit 20
        match ip address SAK-VOIP-SOURCES
        set vrf sak-voip
       !

Apply these route-maps on to the interfaces which will carry identical VRF select configurations.

interface GigabitEthernet2/3.104
      description SAK/PAM Turku C-FI-20709-8416
      encapsulation dot1Q 104
      ip vrf receive sak-pam
      ip vrf receive sak-voip
      ip address 10.100.220.177 255.255.255.252
      no ip redirects
      no ip proxy-arp
      ip policy route-map sak-vrfs-in1
      arp timeout 300
    !
     interface GigabitEthernet2/3.505
      description SAK/PAM Turku C-FI-20709-8416
      encapsulation dot1Q 505
      ip vrf receive sak-pam
      ip vrf receive sak-voip
      ip address 10.100.220.26 255.255.255.254
      no ip redirects
      no ip proxy-arp
      ip mtu 1500
      ip policy route-map sak-vrfs-in2
      arp timeout 300
     !

Workaround 3: Create a dummy interface and apply this route-map first on the dummy interface (but do not delete the sub-interface).

CSCtf51541

Symptoms: After a parity error is detected in the system controller and a soft-reset is performed, inband traffic may be interrupted in one direction.

The following log message indicates that the error occurred and a soft-reset was performed:

%SYSTEM_CONTROLLER-SP-3-ERROR: Error condition detected: TM_DATA_PARITY_ERROR

Conditions: No particular hardware or software configuration has been identified to contribute to this. The issue is due to transient hardware errors.

Workaround: Configure EEM policy to look for the error and trigger an immediate switchover.

CSCtf53672

Symptoms: A router crashes when any CWAN module is not responding to the RP keepalives.

Conditions: The symptom is observed with a Supervisor 32.

Workaround: There is no workaround.

CSCtf54561

Symptoms: A MPLS TE FRR enabled router can encounter a crash if the show ip cef vrf vrf-name command is issued.

Conditions: This symptom occurs when the VRF contains many entries (17k) in which the outgoing interface changes due to a topology change.

Workaround: Command should not be issued when many topology changes occur on interface flaps.

CSCtf64235

Symptoms: Distributed LFI over ATM (dLFIoATM) session does not ping after switchover when router is configured in SSO mode.

Conditions: The symptom is observed when the global redundancy mode is SSO.

Workaround: Perform a shut and no shut on the ATM physical interface.

CSCtf74073

Symptoms: Enhanced FlexWAN resets upon copying a scaled configuration.

Conditions: The symptom is observed upon directly copying a scaled configuration into the running configuration.

Workaround: Copy configuration into start up from the disk or any other source file.

CSCtf75053

Symptoms: DHCP Relay will send a malformed DHCP-NAK packet. The malformed packet will be missing the END option (255) and the packet's length will be truncated to 300. In effect, all the options after 300 bytes, if any, will be missing.

Conditions: When a Cisco 10000 series router is configured as a relay and a DHCP request is sent from the CPE, the router will send a DHCP-NAK when client moves into a new subnet.

Workaround: There is no workaround.

CSCtf75587

Symptoms: Active RP crashes when ISSU upgrade is initiated (SSO mode) from Cisco IOS Release 12.2(33)SRD3 to Release 12.2(33)SRD4.

Conditions: The symptom is observed when "mls qos" is configured on the router and then an SSO mode ISSU switchover is initiated.

Workaround 1: Disable QoS with the no mls qos command.

Workaround 2: Upgrade in RPR mode. First, verify that following command is not in the running-configuration:

no service image-version efsu

If this command is in the running configuration, remove it using service image-version efsu.

CSCtf77037

Symptoms: After an OIR of Enhanced FlexWAN, some of the DLFIoATM bundles do not come up.

Conditions: The symptom is observed after an OIR of Enhanced FlexWAN.

Workaround: Do a shut/no shut on the ATM interface.

CSCtf77047

Symptoms: Ping ATM subinterface peer IP address has packet loss from Cisco 7206.

Conditions: This symptom occurs with the following:

1. NPE-G2+PA-MC-STM-1SMI+PA-A6-OC3SML

2. Enable EIGRP on ATM subinterface

Workaround: There is no workaround.

CSCtf78662

Symptoms: On a Cisco 7600 series router that is configured with REP, the IGMP query is not forwarded through the secondary REP port leaving part of the ring incapable of receiving multicast traffic. The other switches in the REP ring located after the secondary port are unable to receive the IGMP queries from the Cisco 7600 and thus may not elect any mrouter port.

Conditions: The symptom is observed only when the REP has a converged topology and the alternate port is not located in the Cisco 7600 but anywhere else in the REP ring.

Workaround 1: One of the two REP ports on the Cisco 7600 must be elected/configured as an alternate port.

Workaround 2: One of the two REP ports on the Cisco 7600 must be in shutdown.

CSCtf79154

Symptoms: After an SSO switchover, some of the virtual-access interfaces do not ping.

Conditions: The symptom is observed after an SSO switchover.

Workaround: Do a shut/no shut on the corresponding subinterface.

CSCtf80408

Symptoms: Enhanced FlexWAN crashes.

Conditions: The symptom is observed with following steps:

1. Have scaled DLFIoATM (256 bundles) on a single PA.

2. Have traffic flowing through all the bundles.

3. Do a switchover.

4. When standby comes up, do a shut/no shut on ATM interface.

Workaround: There is no workaround.

CSCtf82671

Symptoms: On a 1xOC3 CEoP SPA, changing SF/SD thresholds using the threshold sf-ber or threshold sd-ber commands does not cause an APS switchover to happen at the new SF threshold.

Conditions: The symptom is observed only if APS is enabled on a 1xOC3 CEoP SPA.

Workaround: There is no workaround.

CSCtf82883

Symptoms: When clearing a VRF route, there is a traffic drop on other VRF routes.

Conditions: The symptom is observed with an L3 VPN configuration.

Workaround: There is no workaround.

Further Problem Description: Some LTE broker distribution is leaked to other VRFs.

CSCtf83737

Symptoms: Switch Processor crashes, which can be either on the active RP or the standby.

Conditions: This symptom occurs when IPv4 multicast routing is configured.

Workaround: Remove multicast configuration completely.

CSCtf84237

Symptoms: A router may reload with the following crash decode (traceback summary):

0x123d7e24 is in vpdn_apply_vpdn_template_pptp 
0x1239c100 is in l2x_vpdn_template_find 
0x123d81dc is in vpdn_apply_l2x_group_config 
0x123cfedc is in vpdn_mgr_call_initiate_connection 
0x123cce68 is in vpdn_mgr_event 
0x123ce974 is in vpdn_mgr_process_client_connect 
0x123cf248 is in vpdn_mgr_process_message 
0x123cf368 is in vpdn_call_manager 

Conditions: The symptom is observed when an invalid tunnel-type VSA is configured, for example:

vsa cisco generic 1 string "vpdn:tunnel-type=l2tp_bad"

Workaround: Configure a correct tunnel-type VSA in Radius.

CSCtf85661

Symptoms: Ethernet OAM packets are not punted to RP and instead are tunneled to the remote PE.

Conditions: The symptom is observed with EoMPLS and an L2TPv3 network when "ethernet oam" is configured under the interface.

Workaround: Configure "ethernet cfm global" in global configuration mode.

CSCtf86240

Symptoms: Enhanced FlexWAN with scaled DLFI setup crashes.

Conditions: The symptom is observed with the following steps:

1. 256 dLFIoATM interfaces on a single PA.

2. Traffic is flowing through all the bundles.

3. Remove IPHC configuration from all the bundles.

4. Do a shut/no shut after removing the IPHC configuration.

5. Add IPHC configuration again and do a shut/no shut.

Workaround: There is no workaround.

CSCtf86865

Symptoms: Enhanced FlexWAN with scaled DLFI setup crashes on doing shut/no shut on ATM interface.

Conditions: The symptom is observed with the following steps:

1. 256 dLFIoATM interfaces on a single PA.

2. 50 Mbps traffic includes 10 Mbps of 64 byte + 20 Mbps of TCP + 20 Mbps of UDP.

3. Perform a shut/no shut on ATM interface.

Workaround: There is no workaround.

CSCtf90692

Symptoms: There is an ipservices build failure due to the fix for CSCtf51332.

Conditions: The build fails with the below compilation error:

const/common-rp/fm-earl7/fm_pbr_earl7.c@@ ((,),) obj-4k-draco2-mp-earl7 obj-7k-
sup3-rp-earl7 obj-m8500-sup3-rp-earl7
const/common-rp/fm-earl7/fm_pbr_earl7.c:593: relocation truncated to fit:
R_PPC_REL24 cmfi_feature_alloc_vlan_rcv_vrf
const/common-rp/fm-earl7/fm_pbr_earl7.c:593: undefined reference to
`cmfi_feature_alloc_vlan_rcv_vrf'

Workaround: There is no workaround.

CSCtf90970

Symptoms: TX CPU might crash on a Cisco 7600 SIP-200 due to a particle chain corruption.

Conditions: The symptom is observed when "ppp multilink interleave" is configured on a multilink PPP bundle.

Workaround: Disable the "ppp multilink interleave" feature on the multilink PPP bundle.

CSCtf92354

Symptoms: Traceback is seen when doing a shut and no shut under heavy traffic (100Mbps).

Conditions: The following steps cause this issue:

1. 256 dLFIoATM interfaces on a single PA.

2. Traffic is flowing through all the bundles which is above NDR (100 Mbps) but less than interface bandwidth (155Mbps). This 100 Mbps traffic includes 20 Mbps of 64 byte + 40 Mbps of TCP + 40 Mbps of UDP.

3. Do a shut/no shut.

4. Tracebacks will be seen.

Workaround: There is no workaround.

CSCtf96118

Symptoms: A standby RSP that is supposed to start with SSO mode starts with RPR mode due to the following error.

Config Sync: Bulk-sync failure due to Servicing Incompatibility. Please check 
full list of mismatched commands via:
  show redundancy config-sync failures mcl
 
   
Config Sync: Starting lines from MCL file:
-no mls flow ipv6

The running Cisco IOS image uses IPSERVICE, which is unable to configure no mls flow ipv6. But this command can be detected as mismatch command, and it fails to start with SSO mode.

Conditions: This issue can occur after conducting "write memory" and reloading the part.

This issue is confirmed by using Cisco IOS Release 12.2(33)SRC4. A similar issue has been seen on Cisco IOS Release 12.2(33)SRC5 and Cisco IOS Release 12.2(33)SRD4, but not on Cisco IOS Release 12.2(33)SRE.

Workaround: Conduct reload when startup-config is saved in NVRAM.

CSCtf96659

Symptoms: Broadcast/multicast storm across L2 switchport trunked etherchannel on ES+ links.

Conditions: The symptom is observed with an L2 trunked port-channel interface with ES+ member links. There is "ip pim" configured on VLAN SVI where that VLAN is allowed across the trunked port-channel.

Workaround: Use a single link configured as switchport trunk.

CSCtg01296

Symptoms: Enhanced FlexWAN with scaled DLFI setup resets on doing a shut/no shut on the ATM interface.

Conditions: The symptom is observed with the following steps:

1. 256 dLFIoATM interface on a single PA. 2. Traffic of around 44 Mbps Imix types is flowing through the all bundles. This is equally divided between all the bundles. 3. Do a continuous shut/no shut. 4. Enhanced FlexWAN might reset. It does not generate a crashinfo.

Workaround: There is no workaround.

CSCtg11217

Symptoms: Standby crashes when doing an SSO.

Conditions: The symptom is observed when one of the slots in the chassis has a fabric connection issue.

Workaround: Power down the module in the slot that is having the fabric connection issue.

CSCtg11421

Symptoms: The following issues are observed:

All egress traffic by SIP-400 is dropped.

Consecutive BusConnectivityTest failure for SIP-400.

When SIP-400 is hosting intelligent SPAs such as SPA-8XCHT1/E1, then this SPA gets into OutSrvc state.

Conditions: The symptom is observed with a SIP-400 with egress LLQ shaping and with a high volume of traffic to low speed stream.

Workaround 1: SIP-400 reload using the hw-module module X reset command (where X is the module/SIP-400 number).

Workaround 2: Remove LLQ configuration.

Workaround 3: SIP-400 microcode reload (where X is the module/SIP-400 number):

attach X  
enable  
microcode reload np 

CSCtg13413

Symptoms: ESP tunnel establishment with VPNLB is unsuccessful.

Conditions: The symptom is observed with ESP VServer and UDP VServer with ISAKMP configured in a basic hub-spoke VPN setup.

Workaround: There is no workaround.

CSCtg14446

Symptoms: Packets are dropped in excess of the configured rate for hierarchical policies, with shaper in the parent policy.

Conditions: The symptom is observed only with HQoS policies (flat policies are not affected).

Workaround: There is no workaround.

CSCtg14755

Symptoms: In a 6PE environment, on a Cisco 7600 PE injecting a directly connected v6 prefix, the hardware programming for the BGP local label for that prefix might be incorrect when an IPv6 address is deleted and re-added.

Conditions: The symptom is observed when multiple BGP paths exist for this prefix (remote PEs advertise the same prefix).

Workaround: Perform a shut/no shut on the local interface.

CSCtg16191

Symptoms: A SIP-400 line card may crash due to a memory leak in the code for bringing down PPPoE sessions. A few hours before the crash, the line card starts to generate the following logs:

%SYS-2-MALLOCFAIL: Memory allocation of
100352 bytes failed from 0x407F181C, alignment 0
Pool: Processor  Free: 2242304  Cause: Memory fragmentation Alternate Pool:
None  Free: 0  Cause: No Alternate pool 

You can also verify this memory leak using the show memory allocating-process totals command on the SIP-400 line card and searching for VA_LOCK. More memory is allocated to VA_LOCK when you bring up PPPoE sessions, but the usage will not go down even after the PPPoE sessions are torn down.

Conditions: The symptom is observed only with PPPoE sessions.

Workaround: There is no workaround.

CSCtg22774

Symptoms: The input queue on which the packets are being received for RLB is getting wedged and all the packets are being dropped.

Conditions: The symptom is observed on an RSP720 platform only and when the packet size is more than 512 bytes.

Workaround: You can use SUP720, if the hardware is available.

Further Problem Description: RSP platform supports particle-based packet buffers. When the packet is punted to the SLB process, the particles are collated and converted to contiguous buffers. If there is an error in the RLB packet processing, then the packet is being freed assuming that it is a particle. This freeing is not succeeding and the packet is getting queued to the input interface queue permanently.

CSCtg35298

Symptoms: Traffic drops are seen between two PEs after re-optimization.

Conditions: The symptom is observed with 16k VPLS VC, 4k scalable EoMPLS, 1K software EoMPLS, 600 primary tunnels to nPE1 and one tunnel to nPE2 from nPE3.

Workaround: There is no workaround.

CSCtg44996

Symptoms: Flows get dropped when the packet size is greater than 1514.

Conditions: The symptom is observed after L2TPv3 reassembly on an ES+ card with default MTU on access facing. The packets get dropped because of MTU validation. This is seen in VLAN mode configuration only.

Workaround: Increase the access facing MTU.

CSCtg49331

Symptoms: Multicast streams may not be forwarded to some interfaces, even though they are forwarded to other interfaces on the device without issues.

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD4 with egress multicast replication mode.

Workaround: Use ingress replication mode. If egress replication mode is used and the issue is present, service can be restored by using the clear ip mroute A.B.C.D command:

Or perform a shut and no shut on the affected interface.

CSCtg52130

Symptoms: When running "show mmls met" on SP or DFC, the line card crashes

Conditions: This symptom will happen when the met set has a fixed set.

Workaround: There is no workaround.

CSCtg62555

Symptoms: System may be out of service after removing the IP address from the "ip portbundle source loopback" interface. The following error may be shown:

%SYS-2-CHUNKFREE: Attempted to free nonchunk memory, chunk 2BA721819088, 
 data 2BA760900868. -Process= "SSM connection manager", ipl= 0, pid= 137
 -Traceback= 1#cdb5a75db2833d1c207cda33ef68fc00  :400000+6D755D :400000+1AF0949
 :400000+49D5A2B 
 :400000+49D98FF :400000+49DB212 :400000+1919497 :400000+19044BF :400000+190434B
 :400000+18FA668 
 :400000+18F9378
 
 %Software-forced reload

Conditions: This symptom is observed on a Cisco ASR1000 series router functioning as an ISG, when Port Bundle Host Key (PBHK) is enabled on the sessions, when thousands of sessions are established, and a high rate of traffic is running in both the upstream and downstream directions.

Workaround: There is no workaround.

CSCtg73456

Symptoms: Bulk sync fails due to applying the tx-ring- limit command on the main interface, which is not supported.

Conditions: This symptom occurs when appling the tx-ring- limit command on the main interface and doing an SSO.

Workaround: There is no workaround.

CSCtg83578

Symptoms: When you disable and enable the mls qos rewrite ip dscp command, the set functionality is not working.

Conditions: The symptom is observed with a policy-map with set operation, and when you execute the no mls qos rewrite ip dscp and mls qos rewrite ip dscp in the global mode.

Workaround: Execute no mls qos and mls qos in the global config mode.

CSCtg91201

Symptoms: DHCP-added static routes get removed sometimes and the traffic towards the host gets dropped.

Conditions: The symptom is observed with IP unnumbered relay and with a third party external DHCP server. (This issue can also occur with an IOS DHCP server, but the probability is quite low.)

Workaround: There is no workaround.

CSCtg92587

None High CPU in the SNMP Engine process is observed every five minutes.

CSCtg94250

Symptoms: Removing address-family ipv4 vrf vrf (in router BGP) followed by no ip vrf vrf (where "vrf" is the same) could result in a crash.

Conditions: The symptom is observed in a large VPNv4 scale setup, when applying the following commands to the same VRF back-to-back:

1. no address-family ipv4 vrf vrf

2. no ip vrf vrf

3. ip vrf vrf

The trigger of the BGP crash is a result of a racing condition between event 1 and event 2.

Workaround: Since this is a racing condition, the workarounds are:

1. Not applying (1) before (2).

2. Give sufficient time for (1) to complete before applying (2).

CSCth01394

Symptoms: On a Cisco 7606 router that is running Cisco IOS Release 12.2(33) SRD3 with SIP200/SPA-4XCT3/DS0, when you have ppp multilink interface(s) configured with member links from same SPA (software based multilink) and you physically remove SPA, you will see that upon executing the show ppp multilink command, the multilink interface still has reference for member links. If you do the sh run int serialx/y command, you will get message interface not found.

Conditions: This issue is consistently reproducible.

Workaround: There is no workaround.

CSCth02479

Symptoms: Router crashes.

Conditions: The symptom is observed when the show upgrade fpd file tftp: command is performed.

Workaround: Copy the fpd file to "disk:" and then perform the show upgrade fpd file disk: command.

CSCth02725

Symptoms: There is an interoperability issue between a third-party vendor's routers and Cisco routers with severe IPTV service failure in Prune-Overriding environment.

Conditions: The symptom is observed in the following scenario:

1. Router A is Cisco 7609 router (IP address 10.1.1.1) and connects to Router B (third-party vendor's router; IP address 10.1.1.3) and Router C (IP address 10.1.1.2).

2. If subscriber under Router C disappears, Router A receives "Prune" message from Router C.

3. Router A does not change "source IP of PruneEcho message (10.1.1.2)" and sends it to Router B.

4. At this time, Router B should send overriding-join to Router A because Router B still has subscribers. But Router B drops the PruneEcho message because source IP (10.1.1.2) is not from PIM neighbor. Router B cannot send overriding-join to Router A.

5. As a result, multicast traffic (IPTV stream) to Router B stops.

Workaround: Connect C and B to become PIM neighbors. However, this cannot always be considered a recommended workaround because of potential high cost and/or other (sometimes third-party) limitations.

CSCth15790

Symptoms: ES+ low-queue line card crashes with HQoS policy applied.

Conditions: The symptom is observed with an HQoS policy and with three-level HQoS and classes containing "priority" statements for either priority level1 or level2. When traffic passed through either of the PQ classes the line card may crash after some random period of time.

Workaround: There is no workaround.

CSCth18571

Symptoms: An ES+ module may reload when a SPAN session is configured for a source VLAN.

Conditions: The symptom is observed with a Cisco 7600 ES+ and with Cisco IOS Release 12.2(33)SRD4. VFI configuration needs to be present.

Workaround: There is no workaround.

CSCth33500

Symptoms: NAS port is reported as zero on LNS.

Conditions: This symptom occurs when "vpdn aaa attribute nas-port vpdn-nas" is configured.

Workaround: There is no workaround.

CSCth46888

Symptoms: When ARP entry is refreshed due to timeout or execute clear arp command, router sends ARP request for cached MAC address. However, request message does not use virtual MAC for Source (Sender) MAC.

Conditions: This symptom occurs when the router is VRRP master, and VRRP IP is configured the same as the interface IP.

Workaround: There is no workaround.

CSCth55383

Symptoms: When entering the show tech command on RP, the line card with DFC may display SWITCH_BUS_IDLE message.

Conditions: This symptom occurs when entering the show tech command on RP.

Workaround: There is no workaround.

CSCth64439

Symptoms: With different image versions and with "issu image-version comp disable" configured, the standby comes up in SSO mode instead of RPR.

Conditions: The symptom is observed when "issu image-version comp disable" is configured.

Workaround: Enable image-version compatibility check (using issu image-version comp enable).

CSCth66700

Symptoms: (S,G) expiry timer is updated again about two minutes after stopping the (S,G) stream.

Conditions: The symptom is observed with the (S,G) expiry timer.

Workaround: There is no workaround.

Further Problem Description: The behavior of the expiry timer is not changed even if you change the value of mls ip muticast flow-stat-timer.

CSCth69504

Symptoms: A Cisco 7600 series router may experience a small buffer leak in the small buffer pool on SP.

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD configured with IGMP snooping.

Workaround: Disable IGMP snooping either globally or per VLAN.

CSCth71899

Symptoms: An SSO causes a met3 VLAN to become 0.

Conditions: The symptom is observed with 600 S,G distributed with OIFs over SVIs and L3 interfaces and after an SSO. It happens only on triggering joins and leaves for the groups, on the CFC card.

Workaround: There is no workaround.

CSCth72565

Symptoms: The reachability of the PE2 router's loopback is lost from PE1 after an interface flap in the core. The LSP toward PE2 "breaks" due to data plane programing error (wrong labels).

Conditions: The symptom is observed with MPLS with the presence of ECMP. The PE1 has two uplinks to core routers. In a steady state there is no ECMP between PE1 and PE2. When a link is lost in the P-core (link flap or shut and no shut) there is ECMP between PE1 and PE2. After the link flap between the two P routers in the core, PE1 is losing connectivity to PE2.

Workaround 1: Use the clear ip route on the affected IP address.

Workaround 2: Avoid ECMP by altering link cost.

CSCth72765

Symptoms: Configuring "mls qos protocol hsrp police rate" does not enable policing of HSRPv2 packets.

Conditions: The symptom is observed on a Cisco 7600 series router when "mls qos protocol hsrp police rate" is configured.

Workaround: There is no workaround.

CSCth84995

Symptoms: Router may reload when performing an ISSU upgrade or downgrade.

Conditions: This symptom occurs when performing an ISSU upgrade or downgrade.

Workaround: There is no workaround.

CSCth87195

Symptoms: Flexwan ATM interface goes down.

Conditions: This symptom is observed while configuring "mac-address" or "atm bridge-enable".

Workaround: Perform a shut and no shut on the interface.

CSCth90001

Symptoms: Packets egressing interfaces of ES+ line cards are not received on the other side of L2 link when SVI plus switchport configuration is used. It is random and does not occur on every ES+ line card.

Conditions: This symptom is observed when ES+ line card is egress line card and SVI plus L2 switchport configuration is used. When this issue is seen the CFI bit in vlan tag header for such packets is set by X40g egress-intf causing the peer router to drop such packets.

Workaround: Use L3 802.1q subinterface configuration.

CSCti00020

Symptoms: Standby takes more time to come up on SSO.

Conditions: This symptom depends on the SIP based cards that are on the chassis. Every single SIP based card increases the time by one more minute.

Workaround: There is no workaround.

CSCti14290

Symptoms: A Cisco 7600 series router acting as the PE router in an MPLS network may stop forwarding traffic for certain IP prefixes within a VRF. This symptom may occur after a router reload, upgrade or crash due to corrupted hardware-forwarding information on the ingress module for the VPN label of the affected IP prefix.

The problem can be identified by comparing the output of the following commands:

1. Determine the BGP VPN Label for the prefix

show ip bgp vpnv4 all vrf vrf name prefix
 
 router# sh ip cef vrf test 10.1.1.1 detail 
 10.1.1.0/24, epoch 13
   local label info: other/4828 <=== label is 4828
   recursive via 10.100.1.2
     attached to GigabitEthernet1/1
 

2. Determine the hardware forwarding for the prefix on the Supervisor

show mls cef mpls label label detail
 
 RCORL02#sh mls cef mpls label 4828 detail 
 
 Codes: M - mask entry, V - value entry, A - adjacency index, P - FIB Priority
        D - FIB Don't short-cut, m - mod-num, E - ELSP?
 Format: MPLS - (b | xtag vpn pi cr mcast label1 exp1 eos1 valid2 label2 exp2 
 eos2)
 V(2570   ): B | 1 0    0 0 0 4828    0 1 0 0       0 0 
 (A:213683 ,P:0,D:0,m:0 :E:1)
 M(2570   ): F | 1 FFF  0 0 1 FFFFF   0 1 0 0       0 0
 
show mls cef adjacency entry entry id
 
 DRCORL02#sh mls cef adjacency entry 213683 detail
 
 Index: 213683  smac: 0000.0000.0000, dmac: 00d0.2b12.5500
                mtu: 65535, vlan: 1024, dindex: 0x7FFA, l3rw_vld: 1
                format: MPLS, flags: 0x1000008600 
                label0: 0, exp: 0, ovr: 0
                label1: 0, exp: 0, ovr: 0
                label2: 0, exp: 0, ovr: 0
                op: POP
                packets: 0, bytes: 0

3. attach to the ingress module and use the same commands as step 2 and compare the values, if the destination mac address is not the same there is hardware forwarding corruption. Note: The adjacency index will be a different number on the module dfc.

remote login module module number
 
 Router# remote login module 1
 Trying Switch ...
 Entering CONSOLE for Switch
 Type "^C^C^C" to end this session
 
 
 Router-dfc1#sh mls cef mpls label 4828 detail
 Codes: M - mask entry, V - value entry, A - adjacency index, P - FIB Priority
        D - FIB Don't short-cut, m - mod-num, E - ELSP?
 Format: MPLS - (b | xtag vpn pi cr mcast label1 exp1 eos1 valid2 label2 exp2 
 eos2)
 V(1301   ): B | 1 0    0 0 0 4828    0 1 0 0       0 0 
 (A:147570 ,P:0,D:0,m:0 :E:1)
 M(1301   ): F | 1 FFF  0 0 1 FFFFF   0 1 0 0 
 
       0 0
 Router-dfc1#sh mls cef adjacency entry 147570 detail
 Index: 147570  smac: 0000.0000.0000, dmac: 0000.138b.0000
                mtu: 65535, vlan: 1024, dindex: 0x7FFA, l3rw_vld: 1
                format: MPLS, flags: 0x1000008600 
                label0: 0, exp: 0, ovr: 0
                label1: 0, exp: 0, ovr: 0
                label2: 0, exp: 0, ovr: 0
                op: POP
                packets: 59, bytes: 24025

Conditions: The Cisco 7600 must have a distributed forwarding card installed on the ingress module and be configured as an MPLS PE router. The problem is only observed after a router reload, upgrade, or crash.

Workaround: Reloading the ingress module will resolve the hardware forwarding corruption on the module:

hw-module module module number reset

CSCti24657

Symptoms: New settings for fabric channel preemphasis are for sip600/esm20 card for Cisco 7609, Cisco 7609S, and Cisco 7613 chassis.

Conditions: There are no conditions.

Workaround: There is no workaround.

CSCti37167

Symptoms: A router crashes.

Conditions: This symptom occurs after router compares the snmp value of mplsTunnelLastPathChange.

Workaround: There is no workaround.

CSCti37503

Symptoms: RP is dropping IPv6 mcast packet.

Conditions: This symptom happens while sending to SSM group.

Workaround: There is no workaround.

CSCti68153

Symptoms: QinQ packet header is modified breaking QinQ.

Conditions: This symptom occurs when you use ES+ card on the Cisco 7600 where the pseudowire encapsulation begins.

Workaround: One possible workaround is to use double vlan tagging before the packet gets to the ES+ card so that when it pops the first Vlan tag, it will modify the second dummy tag and not the actual Payload. This issue is also not seen on ES20 card.

CSCti80956

Symptoms: Traffic outage and duplication is seen during fibre cut in customer deployment.

Conditions: This symptom is seen with traffic reroute, L2/L3 co-existence.

Workaround: There is no workaround.

CSCtj08597

Symptoms: With the following simple topology, the router crashes when sending IGMP joins from IXIA:

UUT-----Peer-----Ixia

The peer is a Cisco 7600 router acting as a layer2 (only switchport config towards UUT and IXIA) box. There are 10 OIF interfaces on UUT.

Conditions: This symptom is observed when doing a SSO switchover.

Workaround: There is no workaround.

CSCtj15265

Symptoms: The event trace buffer gets wrapped around resulting in met cc log not being available.

Conditions: This symptom is seen when there is a lot of OIF churn.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD4

Cisco IOS Release 12.2(33)SRD4 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD4 but may be open in previous Cisco IOS releases.

CSCee36959

Symptoms: A Cisco 6500 and Cisco 7600 may rarely and unexpectedly reload with the following error message on the SUP:

%RPC-SP-2-FAILED: Failed to send RPC request

online_diag_sp_request:get_rp_cpu_info.

Conditions: This occurs very rarely when the MSFC or RP is too busy processing an event and can not respond to the RPC from the SUP. This is seen only on systems that run native Cisco IOS.

Workaround: There is no workaround.

CSCek48205

Symptoms: The output counters for a Multilink Frame Relay (MFR) bundle interface may not be updated correctly.

Conditions: Occurs after the same interface is deleted and recreated.

Workaround: There is no workaround.

CSCsc13670

Symptoms: The backup configurations that are generated by the Archive feature may be truncated.

Conditions: This symptom is observed when you reload the router with the Archive feature enabled.

Workaround: Enter the privileged mode.

CSCsc85962

Symptoms: When retransmitted packet of Main Mode is received at Cisco IOS router after established SA, it deletes its IKE SA.

Conditions: Replayed packet of Phase 1 is resent.

Workaround: There is no workaround.

CSCsh79241

Symptoms:

1. Tracebacks are occasionally seen when the action "Limit+flood" is triggered.

2. Tracebacks are seen when the "Limit+flood" action is triggered and the MAC limit for the VLAN is removed.

Conditions: The symptom is observed when DFCs are present in the chassis.

Workaround: There is no workaround.

CSCsi51649

Symptoms: A device may reload with NAT traffic under certain conditions.

Conditions: The symptom may be seen in rare cases if a number of successive packets of the same flow are received at a high rate and the pool memory is exhausted in the software.

Workaround: There is no workaround.

CSCsi97428

Symptoms: SSM (S,G) entries periodically created and deleted if OIL is Null and if source is not directly connected.

Conditions: Issue observed on Cisco 7600 platform running Cisco IOS Release 12.2(33)SRC4.

Workaround: There is no workaround.

CSCsk83505

Symptoms: Under various circumstances, UDP input queues can grow to much larger than their intended size. This can result in memory allocation errors if the application that services a UDP input queue is unable to do so quick enough to keep up with incoming traffic. UDP needs to drop received packets, once a given input queue has reached its limit.

Conditions: This symptom is observed with RIPv6 with a large number of neighbors in both Cisco IOS and ION images.

Workaround: There is no workaround.

Further Problem Description: The root cause is that several pieces of code are enqueuing packets to ipsocktype InQ without checking its size, and without updating statistics.

CSCso86544

Symptoms: After an SSO the new active SP crashes at pm_vlan_get_portlist.

Conditions: The symptom is observed after an SSO and is triggered by an OIR offline.

Workaround: There is no workaround.

CSCsq11897

Symptoms: A crash is seen when the interface board is removed.

Conditions: The symptom is observed in a very rare scenario when a BGP session is established and the corresponding interface board is removed.

Workaround: There is no workaround.

CSCsq68156

Symptoms: FRF12 packets are dropped by a PE router.

Conditions: This symptom is observed on a Cisco 12000 series Internet router that has a SPA-1XCHSTM1/OC3, SPA-2XCT3/DS0, or SPA-8XCHT1/E1.

Workaround: There is no workaround.

CSCsq82663

Symptoms: Very high CPU utilization observed under a ~400 MB traffic load on a Cisco Catalyst 6503-E or 6504-E switch with the Cisco IOS Server Load Balancing (SLB) feature.

Conditions: The symptom is observed when the SLB feature is deployed on a Cisco Catalyst 6503-E or 6504-E switch, for DMVPN hubs load balancing for branches (spokes) using OC12 POS SPA as the WAN interface. When traffic is sent from the branch to the networks behind hubs, SLB is not able to install the shortcuts for hardware switching for ingress POS WAN port. The packets are process switched, which increases CPU usage dramatically.

Workaround: There is no workaround.

CSCsq83789

Symptoms: Some L3 interfaces have the wrong LTL programmed for Unknown Unicast.

Conditions: The symptom is observed in a chassis with a SPA-IPSEC-2G card.

Workaround: There is no workaround.

CSCsr47527

Symptoms: The following errors will prevent a standby processor from reaching Hot Standby (full SSO).

Config Sync: Bulk-sync failure due to Servicing Incompatibility. Please check full 
list of mismatched commands via: show redundancy config-sync failures mcl 
Config Sync: Starting lines from MCL file: -
 
   

Conditions: This symptom is most often seen during an ISSU upgrade.

Workaround:

1. Let the Standby come up in RPR mode after MCL mismatch.

2. Then apply the redundancy config-sync ignore mismatched-commands command in exec mode on Active.

3. Now change the redundancy mode to SSO on Active. The setup will come up in SSO mode.

CSCsr64777

Symptoms: A router crashes because of a block overrun (overwriting the memory block).

Conditions: This symptom is observed only when NetFlow version 5 is used.

Workaround: NetFlow version 9 could be used for exporting.

CSCsr72674

Symptoms: There is a possibility the RP could encounter a software exception, resulting in a crash.

Conditions: The symptom is observed with MPLS VPN enabled over a tunnel (GRE, for example) and when the tunnel is configured to be associated with a user-configured VRF.

Workaround: There is no workaround.

CSCsu04049

Symptoms: Following an SSO, pruning recalculations are not done on the new active supervisor and all the VLANs that are available on the switch are put into a not-pruned list.

Conditions: The symptom is observed following an SSO on the new active supervisor.

Workaround: There is no workaround.

Further Problem Description: The join messages from the peer are not handled because flag clearing after the VLAN addition is not occurring on the standby. Thus, after the standby becomes active, the pruning recalculations do not occur.

CSCsu45210

Symptoms: After upgrading from Cisco IOS Release 12.2(18)SXF8 to 12.2(33)SXH2, the standby supervisor constantly reloads with no error messages.

Conditions: The symptom is observed after a software upgrade using the standby. The standby is reloaded with the new software, there is a switchover, then the standby is reloaded again.

Workaround: Remove the port security configuration on all ports.

CSCsu46644

Symptoms: After the router reboots, the username/password prompt does not appear after three minutes. The following message is shown instead of the router login prompt:

% Authentication failed

Conditions: The symptom is observed on a router that is running Cisco IOS interim Release 12.2(33.1.18)SB1.

Workaround: Add the "no no aaa account system guarantee-first" configuration.

CSCsu59900

Symptoms: Standby RP crashes.

Conditions: Occurs when a shut/no shut is performed on the subinterface with a anything over MPLS (AToM) VP configured.

Workaround: There is no workaround.

CSCsu76993

Symptoms: EIGRP routes are not tagged with matching distribute-list source of route-map.

Conditions: Problem is observed where the route-map is applied to a specific interface. When the route-map is applied globally without the specific interface things appear to work fine.

Workaround: There is no workaround.

CSCsu89656

Symptoms: A router may reload when a user reconfigures ATM AToM VP.

Conditions: There is slim timing window that the router may reload when a user issues the commands to reconfigure the ATM VP.

Workaround: There is no workaround.

CSCsu92300

Symptoms: After the IP address of the loopback interface at the PE router is changed, some Mroute entries are in a pruned state.

Conditions: The symptom is observed after changing the IP address of the loopback interface which is configured as the source interface for an MDT tunnel.

Workaround: Use the clear ip bgp * command.

CSCsu96698

Symptoms: More specific routes are advertised and withdrawn later even if config aggregate-address net mask summary-only is configured. The BGP table shows the specific prefixes as suppressed with s>

Conditions: This occurs only with very large configurations.

Workaround: Configure a distribute-list in BGP process that denies all of the aggregation child routes.

CSCsu99270

Symptoms: A Cisco Catalyst 6500 system running with VPNSPA in crypto-connect mode may see high CPU utilization on the RP. Generally, high CPU will be associated with the ARP input process.

Conditions: The symptom will be seen when the VPNSPA is configured to be in crypto-connect mode.

Workaround: There is no workaround.

Further Problem Description: The problem can be verified by running the command show crypto vlan, noting down the port-VLAN (for example: Vlan 710, hex 2C6), logging into the switch remote log switch and running the command test mcast ltl index Cxxx, where xxx is the hex-value of the port-VLAN (in this case, C2C6).

If the command shows the RP as part of this LTL index and there is high CPU utilization then it is possible that you are hitting this issue. If this issue is suspected then you should also determine what packets are hitting the route-processor.

CSCsv09467

Symptoms: Router crashes when interface is defaulted with port-security sticky MAC address configured.

Conditions: The symptom is observed under the following conditions:

1. On a router that is running Cisco IOS Release 12.2(33)SRD.

2. . "Switchport" is configured with port-security and sticky MAC address:

interface <>

switchport

switchport mode access

switchport access vlan <>

switchport port-security

switchport port-security mac-address sticky

3. With traffic on, interface mode is changed as follows:

a. access mode to trunk mode

b. trunk mode to access mode

4. Default the interface with "default int <>" from configuration mode.

5. Router crashes.

Workaround: There is no workaround.

Further Problem Description: Mode changes on switchport with port-security configured from access mode to trunk mode and then to L3 port by defaulting the interface configuration (with the default interface interface-number command) in configuration mode can cause the router to crash.

CSCsv18579

Symptoms: The logging buffer fills with this message:

UTC: FC1: recognized & transferred a satvcl packet, total 604369 UTC: DFC1: recognized & transferred a satvcl packet, total 604370 UTC: DFC1: recognized & transferred a satvcl packet, total 604371 UTC: DFC1: recognized & transferred a satvcl packet, total 604372 UTC: DFC1: recognized & transferred a satvcl packet, total 604373

Note: The counter always increments by one.

Conditions: The symptom is observed with Cisco IOS Release 12.2(18)SXF5 and when reflexive ACL is configured.

Workaround: There is no workaround.

CSCsv49924

Symptoms: The wrong binding and route are created on the DHCP Relay Agent.

Conditions: The symptom is observed when multiple DHCP Relay Agents are present in between clients and the DHCP server.

Workaround: There is no workaround.

CSCsv66694

Symptoms: If the router has a static route and that route is redistributed into EIGRP with a route-map, the EIGRP topology table shows that the router is setting the tag on the redistributed route. However, both the routing table and the EIGRP topology table do not show the tag as being set.

Conditions: The symptom is observed when a Cisco ASR 1006 router that is running Cisco IOS Release 12.2(33)XNB1 is EIGRP neighbors with a Cisco 7300 series router (running Cisco IOS Release 12.2(31)SB10).

Workaround: There is no workaround.

CSCsv81952

Symptoms: Standby supervisor reloads due to parser return code error.

Conditions: The symptom is observed when the redundant supervisor is running Cisco IOS Release 12.2(33)SRD3.

Workaround: There is no workaround.

Further Problem Description: The issue can be seen, for example, by creating parser view (it was also reported when removing service policy from ATM subinterface):

Router#conf t

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#parser view CDandA

%PARSER-6-VIEW_CREATED: view 'CDandA' successfully created.

Router(config-view)#

%RF-SP-5-RF_RELOAD: Peer reload. Reason: Proxy request to reload peer

%OIR-SP-3-PWRCYCLE: Card in module 8, is being power-cycled (RF request)

%PFREDUN-SP-6-ACTIVE: Standby processor removed or reloaded, changing to

Simplex mode

Router(config-view)#

CSCsw81427

Symptoms: Label entries in the TCAM are leaking when there is label deallocation, due to routing or LDP events.

Conditions: The symptom is observed when LDP or BGP withdraw labels due to network events like a route flap or link flap.

Workaround: There is no workaround.

Further Problem Description: Labels in the hardware are not deleted when the labels are withdrawn by LDP or BGP. This can cause traffic loss or traffic misforwarding if those labels are again installed by LDP or BGP.

CSCsx10028

Symptoms: A core dump may fail to write or write very slowly (less than 10KB per second).

Conditions: The symptom is observed when the cause of the crash is processor memory corruption. When this occurs, the corrupted memory pool cannot be used to write the core dump so it will likely fail. (IO memory corruption crashes should not have this problem.)

Workaround: There is no workaround.

CSCsx16206

Symptoms: Incoming traffic destined for Etherchannel is lost due to a configuration error on the ASIC of certain line cards.

Conditions: Occurs only if Etherchannel is configured across multiple line cards. Chassis contains 6516A and 6548-ge-tx line cards. Etherchannel members do not need to be on the these cards.

Workaround: Force switching mode to truncated threshold such that it stays in bus mode. Resetting the workaround will fix the line card experiencing the problem, but if the reset causes a switching-mode change from truncated to flow through and back to truncated, then any other line cards with the same ASIC will now experience the problem.

CSCsx20177

Symptoms: "no int loopback" with "advertise passive-only" causes a stuck prefix.

Conditions: This symptom is observed on a Cisco 7600 series router that is using an RSP720 with Cisco IOS Release 12.2(33)SRD.

Workaround:

Do not use "advertise passive-only". Unconfiguring and reconfiguring this command clears the stuck prefix.

Or with "advertise passive-only":

First remove "passive-interface loopback" from router isis.

Then remove the interface via "no int loopback".

CSCsx20659

Symptoms: There is a ping failure on an ES-20 line card.

Conditions: The symptom is observed when booting while the ICC mechanism is busy.

Workaround: Perform a shut/no shut on the interface, after booting up.

CSCsx27496

Symptoms: Router may crash with an address error in the BGP function.

Conditions: The symptom is observed when the router is configured for BGP and traffic is passing.

Workaround: There is no workaround.

CSCsx39263

Symptoms: After an SSO, TCP Intercept entries in TCAM are not programmed correctly. As a result, TCP packets are not punted to software and thus Netflow entries are not installed.

Conditions: The symptom is observed when TCP Intercept is already configured when the standby comes up. Also, at least two switchport interfaces are present in the router.

Workaround: Remove the TCP Intercept configuration and then reconfigure it.

CSCsx46854

Symptoms: Tracebacks are seen from the interrupt scheduler due to a process suspension.

Conditions: The symptom is observed when changing the IMA group and trying to remove the ATM/IMA interface.

Workaround: There is no workaround.

CSCsx55672

Symptoms: Client fails to get an IP address when it sends a subscription request to the UUT on which a DHCP-initiated IP subscriber session is configured.

Conditions: The symptom is observed when the server is configured with a "Subscriber IP Address Assignment Using DHCP" based ISG session. When the client requests an IP address by sending the subscription request, it fails to negotiate a valid address from the DHCP pool configured on the server.

Workaround: There is no workaround.

CSCsx57711

Symptoms: On a router configured with BGP VPNs, VRF removal may not work properly. VRF can remain in delete-pending state or BGP may crash at a later time.

Conditions: The symptom is observed when the router is configured with one or more VRFs and has the BGP VPN address family enabled. The problem may be triggered by the deletion of a VRF from the router configuration through the no ip vrf or the no vrf definition commands. The issue is a race condition in the BGP code that deals with VRF net deletion and cleanup. Hitting the issue becomes more likely in large scale setups in terms of the number of configured VRFs and the number of nets in the BGP VPN table.

Workaround: Make sure that all the nets in the BGP VPN table belonging to the VRF are deleted before issuing the VRF deletion command. To delete all the nets belonging to the VRF:

1. All BGP CE neighbor configuration for that VRF must be removed.

2. Any redistribution of routes into BGP for that VRF must be deconfigured.

3. The import route-targets for the VRF must be removed.

Following the removal of the configuration, at least two minutes must elapse so that BGP can complete its cleanup. When no nets belonging to the VRF remain in the BGP table it should be safe to delete the VRF without the possibility of hitting this issue.

CSCsx65705

Symptoms: The router crashes upon executing the no route-map command with a match statement referencing an already-removed access-list.

Conditions: The symptom is observed when the access-list is not present while executing the no route-map command.

Workaround: Remove the match statements which are pointing to the access-list before the access-list is removed.

CSCsx69555

Symptoms: Unknown prefixes show up in the BGP table when "route-map" is configured on a neighbor and labels are sent from the other side.

Conditions: The symptom is observed when the command set mpls-label is not given inside the route-map.

Workaround: Give the command set mpls-label under all the route-maps configured on the neighbors.

CSCsx70085

Symptoms: Router watch failed.

Conditions: Issue occurs randomly with a very low probability if you are running an HA system.

Workaround: There is no workaround.

CSCsx87562

Symptoms: The following error is seen following interface range configuration change:

%SYS-3-TIMERNEG: Cannot start timer (0xXXXXXXXX) with negative offset (- YYYYYYYYYY).

-Process= "<interrupt level>", ipl= 2

Conditions: This symptom is seen with dual supervisors installed and affects these Cisco Catalyst 4000 releases: 12.2(52)SG/XO, 12.2(50)SG4/5/6, 12.2(53)SG/SG1.

Workaround:

1. Configure the interfaces one by one.

2. Force a switchover "redundancy force-switchover".

3. Use Cisco IOS Release 12.2(50)SG3 until the fix code is released.

CSCsy08048

Symptoms: Memory usage increases by about 10MB in processor memory following the creation of new checkpointing buffer pools. The result is less free memory available for other purposes.

Conditions: This increase is of a fixed size, is seen immediately after boot, and is not configuration-dependent.

Workaround: This issue should not impact most customers unless they are reaching the very limits of free memory with their configuration, in which case a reduction in the scale of configuration would work around the problem but may result in diminished features or scalability.

CSCsy09743

Symptoms: Multilinks flap after being added to an MLP bundle with a service policy attached to the interface.

Conditions: The symptom is observed when an existing service policy is on a interface. The interface is added to an MLP bundle without manually removing the service policy.

Workaround 1: Before adding the interface to the MLP bundle, remove the existing service policy configuration with the no service-policy command.

Workaround 2: If the link is already flapping, remove the MLP configuration with the no ppp multilink command then reapply the same service policy and remove it:

service-policy XXXXXXXXX

no service policy XXXXXXXX

Check that the queuing has been removed with show hqf interface XXXX. The command should return no output if the queuing has been removed. Add back the MLP configuration:

ppp multilink

ppp multilink group YYY etc

Workaround 3: Remove the channel-group and re-add it, if the interface was created as part of a channel-group.

Workaround 4: Use the wr mem command and reload the router.

CSCsy24691

Symptoms: For 6KW DC PS, some or all of the four power-input sensors are missing from SNMP entries in entPhyiscalTable "power-supply [1-2] power-input [1-4] Sensor".

Conditions: The symptom is observed with a 6KW DC Power Supply 2.

Workaround: There is no workaround.

CSCsy31601

Symptoms: After switchover on UUT, BGP sessions will not be re-established and the RTRA will not accept a connection from the UUT.

Conditions: The symptom is observed only if "timer 0 0" (hold-down timer never expires) is configured on DUT (where switchover is done) and there are no route changes on the RTRA. If any route is advertised or withdrawn by RTRA, the peer will send a TCP reset.

Workaround: Do not use "timer 0 0" (hold-down timer never expires).

Further Problem Description: This is observed in internal testing and is a rare case scenario.

CSCsy34533

Symptoms: Fast switching does not work when "dot1q native vlan" is configured on the interface.

Conditions: The issue is seen with a Cisco 7600 series router.

Workaround: Remove CLNS fast switching from the interface where the VLAN is configured.

CSCsy34805

Symptoms: Police rate configuration is lost after reload.

Conditions: The following configuration:

police rate 40000000 burst 1250000 peak-rate 60000000 peak-burst 1875000

is saved in the router configuration as:

police rate 40000000 bps burst 1250000 peak-rate 60000000 peak-burst 1875000

This configuration is invalid and is rejected.

Workaround: Configure using bytes per second and bytes as qualifiers:

police rate 40000000 bps burst 1250000 bytes peak-rate 60000000 bps peak-burst 1875000 bytes

CSCsz11384

Symptoms: The following error is logged:

%IDMGR-3-INVALID_ID: bad id in id_get (Out of IDs!)

Conditions: Symptom observed in Cisco IOS Release 12.2(33)SRC in Cisco Intelligent Services Gateway (ISG) solution and with a very high rate of DHCP discoveries.

Workaround: There is no workaround.

CSCsz16961

Symptoms: The system crashes when one of the 6PE multipath interfaces is shut down. All cards crash with the same decodes.

Conditions: The symptom is observed with IPv6 Provider Edge (Cisco 6PE) router over MPLS with multiple paths.

Workaround: There is no workaround.

CSCsz24554

Symptoms: The standby router reloads continuously.

Conditions: The symptom is observed in highly scaled environments when the checkpointing facility may get permanently stuck to FLOW_OFF if the standby unit reloads when FLOW_OFF is asserted.

Workaround: Reload the standby unit after executing the test checkpoint flow on command.

Further Problem Description: Execute the show checkpoint stat command at the active router console CLI to determine if the flow control state is set to OFF.

CSCsz25451

Symptoms: The TX CPU crashes when there is a setup of 1K DMLP interfaces and when the SPAs are reloaded.

Conditions: The symptom is observed in a highly-scaled configuration when the SPAs are reloaded.

Workaround: There is no workaround.

CSCsz40677

Symptoms: PRE crash caused by DHCP internal function.

Conditions: The symptom is observed when the router is running as a DHCP server.

Workaround: There is no workaround.

CSCsz66064

Symptoms: VPLS FRR cutover takes much longer than expected (5-6 seconds), when the primary is on ES40 and backup on ES20.

Conditions: The symptom is observed when VPLS VCs are going on the TE FRR tunnel, and cutover happens with the backup interface on ES20. The issue is seen with scaled VCs.

Workaround: There is no workaround.

CSCsz68709

Symptoms: A console may lock when using the scripting tcl init init-url command.

Conditions: This symptom is observed when using the scripting tcl init init-url command where the init- url is invalid or inaccessible, then entering the tclsh command and appending a file name.

Workaround: Ensure that the init-url argument used in the scripting tcl init command is valid and accessible.

Alternate workaround: Enter the tclquit command to end the Tcl shell and return to privileged EXEC mode, then enter the tclsh command to enable the Tcl shell again.

CSCsz71787

Symptoms: A router crashes when it is configured with DLSw.

Conditions: A vulnerability exists in Cisco IOS software when processing UDP and IP protocol 91 packets. This vulnerability does not affect TCP packet processing. A successful exploitation may result in a reload of the system, leading to a denial of service (DoS) condition.

Cisco IOS devices that are configured for DLSw with the dlsw local- peer automatically listen for IP protocol 91 packets. A Cisco IOS device that is configured for DLSw with the dlsw local-peer peer-id IP- address command listen for IP protocol 91 packets and UDP port 2067.

Cisco IOS devices listen to IP protocol 91 packets when DLSw is configured. However, it is only used if DLSw is configured for Fast Sequenced Transport (FST). A DLSw FST peer configuration will contain the following line:

dlsw remote-peer 0 fst ip-address

It is possible to disable UDP processing in DLSw with the dlsw udp-disable command. However, disabling UDP only prevents the sending of UDP packets; it does not prevent the device from receiving and processing incoming UDP packets.

Workaround: The workaround consists of filtering UDP packets to port 2067 and IP protocol 91 packets. Filters can be applied at network boundaries to filter all IP protocol 91 packets and UDP packets to port 2067, or filters can be applied on individual affected devices to permit such traffic only from trusted peer IP addresses. However, since both of the protocols are connectionless, it is possible for an attacker to spoof malformed packets from legitimate peer IP addresses.

As soon as DLSw is configured, the Cisco IOS device begins listening on IP protocol 91. However, this protocol is used only if DLSw is configured for Fast Sequenced Transport (FST). A DLSw FST peer configuration will contain the following line:

dlsw remote-peer 0 fst ip-address

If FST is used, filtering IP protocol 91 will break the operation, so filters need to permit protocol 91 traffic from legitimate peer IP addresses.

It is possible to disable UDP processing in DLSw with the dlsw udp-disable command. However, disabling UDP only prevents the sending of UDP packets; it does not prevent the receiving and processing of incoming UDP packets. To protect a vulnerable device from malicious packets via UDP port 2067, both of the following actions must be taken:

1. Disable UDP outgoing packets with the dlsw udp-disable command.

2. Filter UDP 2067 in the vulnerable device using infrastructure ACL.

* Using Control Plane Policing on Affected Devices

Control Plane Policing (CoPP) can be used to block untrusted DLSw traffic to the device. Cisco IOS software Releases 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T support the CoPP feature. CoPP may be configured on a device to protect the management and control planes to minimize the risk and effectiveness of direct infrastructure attacks by explicitly permitting only authorized traffic sent to infrastructure devices in accordance with existing security policies and configurations. The following example, which uses 192.168.100.1 to represent a trusted host, can be adapted to your network. If FST is not used, protocol 91 may be completely filtered. Additionally, if UDP is disabled with the dlsw udp-disable command, UDP port 2067 may also be completely filtered.

!--- Deny DLSw traffic from trusted hosts to all IP addresses

!--- configured on all interfaces of the affected device so that

!--- it will be allowed by the CoPP feature.

access-list 111 deny udp host 192.168.100.1 any eq 2067

access-list 111 deny 91 host 192.168.100.1 any

!--- Permit all other DLSw traffic sent to all IP addresses

!--- configured on all interfaces of the affected device so that it

!--- will be policed and dropped by the CoPP feature.

access-list 111 permit udp any any eq 2067

access-list 111 permit 91 any any

!--- Permit (Police or Drop)/Deny (Allow) all other Layer 3 and Layer 4

!--- traffic in accordance with existing security policies and

!--- configurations for traffic that is authorized to be sent

!--- to infrastructure devices.

!--- Create a Class-Map for traffic to be policed by

!--- the CoPP feature.

class-map match-all drop-DLSw-class

match access-group 111

!--- Create a Policy-Map that will be applied to the

!--- Control-Plane of the device.

policy-map drop-DLSw-traffic

class drop-DLSw-class

drop

!--- Apply the Policy-Map to the Control-Plane of the

!--- device.

control-plane

service-policy input drop-DLSw-traffic

In the above CoPP example, the access control entries (ACEs) that match the potential exploit packets with the "permit" action result in these packets being discarded by the policy-map "drop" function, while packets that match the "deny" action (not shown) are not affected by the policy-map drop function. Please note that in the Cisco IOS 12.2S and 12.0S trains, the policy-map syntax is different:

policy-map drop-DLSw-traffic

class drop-DLSw-class

police 32000 1500 1500 conform-action drop exceed-action drop

Additional information on the configuration and use of the CoPP feature is available at:

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6642/prod_ white_paper0900aecd804fa16a.html

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html

* Using Infrastructure ACLs at Network Boundary

Although it is often difficult to block traffic transiting your network, it is possible to identify traffic that should never be allowed to target your infrastructure devices and block that traffic at the border of your network. iACLs are a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The iACL example shown below should be included as part of the deployed infrastructure access-list that will protect all devices with IP addresses in the infrastructure IP address range. If FST is not used, protocol 91 may be completely filtered. Additionally, if UDP is disabled with the dlsw udp-disable command, UDP port 2067 may also be completely filtered.

!--- Permit DLSw (UDP port 2067 and IP protocol 91) packets

!--- from trusted hosts destined to infrastructure addresses.

access-list 150 permit udp TRUSTED_HOSTS MASK INFRASTRUCTURE_ADDRESSES

MASK eq 2067

access-list 150 permit 91 TRUSTED_HOSTS MASK INFRASTRUCTURE_ADDRESSES

MASK

!--- Deny DLSw (UDP port 2067 and IP protocol 91) packets from

!--- all other sources destined to infrastructure addresses.

access-list 150 deny udp any INFRASTRUCTURE_ADDRESSES MASK eq 2067

access-list 150 deny 91 any INFRASTRUCTURE_ADDRESSES MASK

!--- Permit/deny all other Layer 3 and Layer 4 traffic in accordance

!--- with existing security policies and configurations.

!--- Permit all other traffic to transit the device.

access-list 150 permit ip any any

interface serial 2/0

ip access-group 150 in

The white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection access lists. This white paper can be obtained at the following link:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a0080 1a1a55.shtml

Further Problem Description: This vulnerability occurs on multiple events to be exploited. It is medium complexity in order to exploit and has never been seen in customers environment.

CSCsz72138

Symptoms: A POS interface on a PA-POS-2OC3 may experience a stuck issue. All packets will be dropped after hitting the stuck scenario:

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:

72048413<<<<<<<<<<<<<<<<<<<<all packets are getting dropped

Queueing strategy: Class-based queueing

Output queue: 197/1000/0 (size/max total/drops)<<<<<<<<<<<output queue

remains stuck at 197

Conditions: This issue is common to different platforms such as the Cisco 7300, Cisco 7304, and Cisco 7200. Stuck can happen with and without service policy also.

Workaround:

1. Do a "shut"/"no shut" of affected interface.

2. Do a soft OIR of affected slot.

CSCsz81158

Symptoms: Stale prefixes are seen in BGP tables because of missing withdrawals.

Conditions: The symptom is seen in a scale setup where the UUT has hundreds of peers. After several hundred thousand prefixes have been exchanged, the removal of some prefixes at a neighbor will not cause the UUT to send withdrawals of those prefixes to the neighbors it has already advertised those prefixes to.

Workaround: Do a hard reset.

CSCsz83570

Symptoms: SSH sessions disconnect during large data exchanges, such as large logs with pagers.

Conditions: The symptom is observed when large amounts of data are exchanged between both ends: client and server (i.e.: the client provides a large input to the server and the server has a large output to send to the client). The session gets hung momentarily and disconnects after the timeout period of 120 seconds.

Workaround: Use 3DES for encryption.

CSCta06451

Symptoms: Memory leak is observed in export packets when both OER and Netflow are enabled.

Conditions: The symptom is observed only when both Netflow and OER export is enabled. OER export is enabled by default to a 3949 port.

Workaround: There is no workaround.

CSCta07104

Symptoms: The mpls bgp forwarding command is not synced to the standby router.

Conditions: When the mpls bgp forwarding command is not configured manually on the ASBR router, when eBGP Inter-AS session comes up, the command is auto-generated on the interface. The command is not synced to the standby router.

Workaround: The issue will not be seen:

1. When the mpls bgp forwarding command is configured manually.

2. When the command is not configured manually, after a switchover, both the active router and the standby router will get that command.

CSCta08194

Symptoms: A router may crash.

Conditions: This symptom is observed when reprovisioning an AToM tunnel with AAL5 encapsulation.

Workaround: There is no workaround.

Further Problem Description: A complex sequence of events with specific timing characteristics is required to hit this crash.

CSCta08772

Symptoms: EzVPN clients are failing negotiation. This may cause the router to use the less-specific route.

Conditions: The problem can occur when 0/0 is configured as a destination and EXACT_MATCH is specified.

Workaround: There is no workaround.

CSCta20946

Symptoms: ES+ line card crashes.

Conditions: The symptom is observed with a port-channel with ethernet service instances. QoS is applied on both EVC and service group. Repeated rapid configuration and unconfiguration, involving removal of policy-maps and service groups.

Workaround: There is no workaround.

Further Problem Description: There are few conditions where improper clean up happens in platform QoS data structures leading to out of bound memory accesses. Memory corruption occurs, resulting in a crash with various signatures.

CSCta31247

Symptoms: On scaled SVI QoS (with a minimum of 100 SVIs), modifying the policy-map causes the ES+ line card to crash. The policy-map contains seven class-maps and actions.

Conditions: The symptom is observed on a Cisco 7600 series router with an ES+ line card. A policy-map with multiple class-maps is configured and attached to 100 SVI (minimum) interfaces. The policy-map is modified dynamically. Additionally, overwriting the running configuration without any changes causes the line card crash.

Workaround: There is no workaround.

CSCta41186

Symptom: QoS classification in SIP-400 LC does not work as expected when there are "deny" or "match not" entries.

Conditions: There should be more than one deny entry ("match not" in class map or "deny" in ACL).

Workaround: There is no workaround.

CSCta43577

Symptoms: ES20/6704/SIP400 line cards crash during bootup.

Conditions: The symptom is observed when there are many line cards in the setup.

Workaround: There is no workaround.

CSCta45976

Symptoms: A BFD session cannot be established to the peer if the same IP address is configured on the device in a different VRF.

Conditions: The symptom is observed when BFD sessions stay in a down state.

Workaround: Remove the locally-configured IP address.

CSCta46107

Symptoms: FTP transfers from FTP servers on internet to router fail, with "Connection timed out" or protocol errors.

Conditions: The symptom is observed with the following conditions:

Cisco 877, Cisco 1801, Cisco 1841 routers.

Cisco IOS Release 12.4(24)T and 12.4(24)T1.

Workaround: There is no workaround.

Further Problem Description: Using TFTP or SCP works fine.

CSCta46483

Symptoms: The standby crashes upon deleting the "ip subscriber routed" configuration from the port-channel interface.

Conditions: The symptom is observed upon the creation of a port-channel subinterface for a non-existing main interface. It is seen on deleting the configuration "ip subscriber routed" from the main interface. The standby crashes due to parser sync error (due to the configuration mismatch).

Workaround: There is no workaround.

CSCta49840

Symptoms: GGSN may encounter a fatal error in VPDN/L2TP configurations.

Conditions: The symptom is observed in rare race conditions when physical connectivity on the interface to LNS is lost while there are active sessions and traffic.

Workaround: There is no workaround.

CSCta56431

Symptoms: L3VPN/6VPE traffic stops following an SSO when label mode is "per-vrf".

Conditions: The symptom is seen only when the label mode is changed from per-prefix configured initially. (If it is from the startup configuration, the issue is not seen.)

Workaround: Perform a shut/no shut of the VRF interface.

CSCta57455

Symptoms: Cisco 7600 router processor may crash.

Conditions: Occurs when a large packet to be multicast is replicated in the router in software switching path, and there are multiple such packets being processed in quick succession.

Workaround: There is no workaround.

CSCta61293

Symptoms: When a port-channel with an EVC bridge-domain is undergoing a state transition, the Mroute table on the RP does not populate the SVI interface in the outgoing list. This SVI corresponds to the bridge-domain number specified in the EVC.

Conditions: The symptom is observed with a port-channel EVC bridge-domain. When you perform a shut/no shut this issue is seen.

Workaround: Remove then add "ip igmp join-group <>" under the SVI interface on the receiver router.

CSCta71873

Symptoms: Multicast traffic may not forward correctly to OIFs (which are port-channel/SVI) if there is a continuous link flap.

Conditions: The symptom is observed when the OIF is a port-channel/SVI.

Workaround: There is no workaround.

CSCta73054

Symptoms: When using passive FTP with NAT VRF, the connection is broken after NAT in the Cisco 7300. The port numbers are not consistent.

The source port is translated from "X_PORT" to "Y_PORT", but after NAT to the outside, the port still remains the same. This breaks the passive FTP session.

Conditions: This issue is observed when using Cisco IOS Releases 12.2(31)SB11, 12.2(31)SB14, 12.2(33)SB3a and 12.2(33)SB5 when using VRF NAT and trying to establish passive FTP connections across the Cisco 7300.

Workaround: No issues are observed when Cisco IOS Release 12.2(25)S11 is used. The passive FTP session and NAT behave as expected.

CSCta75687

Symptoms: BGP sends the withdrawn message to a peer as if a prefix was labeled (even though the prefix is not labeled). This can cause interoperability problems if the peer does not understand the message and may lead to routing loops in the network.

Conditions: The symptom is observed on a router configured with BGP peering with another vendor's router.

Workaround: Unconfigure the send-label knob. (The existing session will flap since capability will have to be renegotiated.)

CSCta77678

Symptoms: RTP timestamp on the RFC 2833 event is modified. IP Phones are using RFC2833 to transport the DTMF signals, which causes problems with the Voicemail systems.

Conditions: This symptom occurs when RTP header compression is enabled.

Workaround: There is no workaround.

Further Problem Description: The problem disappears if cRTP is disabled. The issue is seen with Class-Based cRTP configured and also with other cRTP configuration types.

CSCta79313

Symptoms: When the router is running EIGRP, there are a lot (hundreds) of routes in the routing table and when changes to the prefix-list are applied (it does not matter if it is currently used by EIGRP or not) high CPU is observed. The process that is causing high CPU is EIGRP-IPv4. Sometimes there can be observed a %SYS-3-CPUHOG for EIGRP-IPv4 process.

Conditions: The issue is hardware independent so can be observed on any router with EIGRP prefix lists, and lots of routes in the RIB (routing table). Additionally there must be at least one redistribute command on EIGRP as well.

Please note that problem could also occur without the BGP routing process, but the necessary condition is for the device to have many routes in the RIB table (BGP has been the logical source for introducing large numbers of routes to the routing table).

Workaround: There is no workaround.

Further Problem Description: To mitigate the impact of this issue, minimize changes to prefix lists or do during a scheduled maintenance window where brief periods of high CPU may not cause customer impact.

CSCta85026

Symptoms: CLI does not accept white spaces in the DHCP option 60 Vendor Class Identifier (VCI) ASCII string, and shows the following error message:

Router(dhcp-config)#option 60 ascii Cisco AP c1240

% Invalid input detected at '^' marker.

Router(dhcp-config)#

Conditions: The symptom is observed with Cisco IOS Release 12.4(24)T1 and later.

Workaround: There is no workaround.

CSCta91556

Symptoms: Packets are getting SSS switched on the LAC towards LNS.

Conditions: The symptom is observed when bringing up any PPPoE or PPPoA session.

Workaround: There is no workaround.

CSCtb04035

Symptoms: Core dump capture is only allowed on bootflash/bootdisk of SP and not external disks, such as disk0: and disk1.

Conditions: The symptom is observed when capturing core dump for debugging when there is not enough space left in SP bootflash.

Workaround: There is no workaround.

Further Problem Description: SP core dump can be written to bootflash/disk0:/disk1 using the command exception and the new argument switch.

CSCtb13546

Symptoms: A Cisco IOS router crashes with a bus error.

Conditions: This symptom occurs when a Cisco IOS router is performing multihop VPDN (a.k.a. tunnel switching). The router may infrequently crash due to a bus error.

This crash is limited to cases where at least one of the following VPDN group commands are configured:

ip pmtu

ip tos reflect

Workaround: Disable the above mentioned commands. However the consequences of this on user traffic must be evaluated first.

CSCtb13846

Symptoms: Standby resets upon changing the bandwidth of the policy attached to the MFR interface when in shut state.

Conditions: The symptom is observed when you configure a policy-map to have a small bandwidth. Attach this service-policy onto the MFR interface which is in UP state. Next, shut down the MFR interface and modify the policy to take more bandwidth in the service-policy. The standby then resets.

Workaround: Configure less bandwidth in the service-policy.

CSCtb15699

Symptoms: When accounting is enabled in both a TC prepaid service profile and the prepaid configuration, the prepaid accounting records are not sent.

Conditions: The symptom is observed when a TC service is applied to a PPP or IP session. Service profile has prepaid and accounting enabled. Prepaid configuration also has accounting enabled.

Workaround: There is no workaround.

CSCtb17388

Symptoms: Following a router reload, the following error message is seen:

cmfi_vpnid_is_valid Invalid Vpn Id

Conditions: The symptom is observed while reloading the router which has a large number of VRFs with IPv6 address-family, but no "ipv6 unicast-routing" enabled.

Workaround: If not in "Host mode", there is no need to have VRF IPv6 address-family without "ipv6 unicast-routing". So simply remove VRF IPv6 address family or add "ipv6 unicast-routing", save the configuration, and reload.

CSCtb20650

Symptoms: Occasionally, you may not be able to copy an image to the standby when the standby is in RPR mode. The following error is seen:

TF I/O failed in data-in phase

Conditions: The symptom is seen in RPR mode only.

Workaround: Copy in SSO mode.

CSCtb25549

Symptoms: Router crashes.

Conditions: The symptom is observed with the following sequence:

1. Use the command debug condition username.

2. Bring up a VPDN session.

3. Clear the VPDN tunnel on LAC.

4. Remove the conditional debug.

Workaround: There is no workaround.

CSCtb33899

Symptoms: When CS5 packets are classified with DSCP-based WRED ES+ line cards, the packets should curve CS5 random drop counters, not the default. The random detect default drop counter is updated instead of CS5.

Conditions: The symptom is observed with a DSCP-based WRED service policy applied in egress direction on an EVC local connect circuit on ES40 line card.

Workaround: There is no workaround.

CSCtb39430

Symptoms: A malfunctioning line card or standby RP inserted into a running Cisco 7600 chassis can cause 99% packet loss for traffic entering CFC-based line cards.

Conditions: The symptom is observed on any Cisco 7600 system with a malfunctioning line card/standby RP in a live system (logging SWITCH_BUS_IDLE error messages).

Workaround: Power down line card by line card to identify the culprit line card/standby RP. Once the SWITCH_BUS_IDLE error messages stop it is likely the culprit has been identified.

Further Problem Description: Flows between DFC cards are not affected.

CSCtb41458

Symptoms: IPv6 multicast traffic is process-switched on IPv6 RBE.

Conditions: IPv6 Cisco Express Forwarding (CEF) is enabled, however IPv6 multicast traffic is process-switched on IPv6 RBE interface.

Workaround: There is no workaround.

CSCtb44299

Symptoms: In certain situations, the standby reloads.

Conditions: The problem occurs when the first CR is typed on the standby console at exactly the same time as a configuration command is executed on the active. The next command on the standby will cause the standby to reload.

Workaround: Do not enable the standby console, or ensure that you are not configuring the active when the standby console is first used.

CSCtb60261

Symptoms: After defaulting the port-channel interface that has EVCs (with QoS) on them which are in turn members of service group with QoS on it, QoS resources in the line card are not deleted. Because of this, when EVCs with QoS are reconfigured on the port-channel interface the following error is seen:

%X40G_QOS-DFC2-3-ACTN: Traffic Manager programming error. creation failed

Conditions: This is more pronounced in a scale scenario. It only occurs with PC EVC. But can be observed with single EVC on a port-channel also. This is observed with an ES+ card.

Workaround: Do not default/delete the port-channel interface when it has EVCs with QoS. Remove QoS on the EVC before deleting the EVC itself or before deleting the interface. That is, do not use the following commands before EVCs are removed on port-channel:

default interface port-channel <>

no interface port-channel <>

CSCtb70344

Symptoms: SCP messages are dropped by line cards. No response is sent to the NMP.

Conditions: The symptom is observed when large numbers of continuous SCP messages are sent to a single line card.

Workaround: Possibly pause SCP transmission to the line card and then retry.

Further Problem Description: This mostly affects offline diagnostics as offline tests can send continuous SCP messages to the line card.

CSCtb70578

Symptoms: With L2PT and SPAN configurations in the same router, the following error message might be displayed on a Cisco 7609 router:

%SPANTREE-SP-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 1 on

GigabitEthernet1/2 VLAN5.

%SPANTREE-SP-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/2 on MST0.

Inconsistent local vlan.

Conditions: The symptom is observed under the following conditions:

1. RSPAN is configured on the Cisco 7609 router.

2. STP BPDUs are being tunneled up to the Cisco 7609 router via L2PT.

3. L2PT is configured locally on the Cisco 7609 router.

Workaround: Apply a VACL where the RSPAN session is sourced:

mac access-list extended block_l2tp_dmac

deny any host 0100.0ccd.cdd0 L2PT destination mac

permit any any

vlan access-map block_l2tp 10

match mac address block_l2tp_dmac

action forward

vlan filter block_l2tp vlan-list 5 insert rspan vlan. (In this case, it is 5)

CSCtb70584

Symptoms: With MSToEVC and N-PE redundancy enabled between two Cisco 7600 series routers in a ring topology, the assigned root Cisco 7600 series router blocks its connection to the other router due to a dispute state.

Conditions: This issue is seen in a ring topology with MSToEVC and N-PE redundancy between two nodes. It occurs when there are valid active and backup MPLS-TE tunnels between the nodes. BPDUs travel across both tunnels (even though they should only traverse the primary) and cause the dispute state.

Workaround: Disable the backup tunnel between the nodes, although this removes the redundancy in case the link between the nodes fails.

CSCtb78266

Symptoms: An incorrect NAS port ID is given when testing IDBless VLAN for PPPoE.

Conditions: The symptom occurs on a Cisco 7200 router that is running Cisco IOS Release 12.4(15)T10.

Workaround: There is no workaround.

CSCtb79113

Symptoms: If there is a PWE between two Cisco 7600 series routers and if one of the routers reloads, the PWE3 comes up once the device has booted after the reload but it does not pass any traffic.

Conditions: The symptom is observed if there is a PWE between two Cisco 7600 series routers and if one of the routers is booted after a reload.

Workaround: Take the xconnect statements off and apply them back on (sometimes on one side and sometimes both sides).

CSCtb80410

Symptoms: SP crash due to delay in the Standby Supervisor powering down during CBUS recovery.

Conditions: The symptom is observed when the Standby Supervisor has a faulty backplane connector to jam the constellation bus.

Workaround: There is no workaround.

CSCtb81445

Symptoms: A policy-map with "trust dscp" configured under a class-map is not accepted on a port-channel interface in ingress for LAN card member-links.

Conditions: The symptom is observed on a Cisco 7600 series router. It is seen when a policy-map is configured with "trust dscp" under a class map and when this is attached to the port-channel interface in an ingress direction for the LAN card member-links on it.

Workaround: There is no workaround.

CSCtb86520

Symptoms: Serial interfaces configured as Multilink Frame Relay (MRF) member links on SONET APS Protect line card may erroneously be in UP/UP state (they should be UP/DOWN) thereby resulting in the parent MFR interface being UP/UP, further resulting in dual connected routing entries in RIB. This causes a service outage as IP flows are forwarded to an APS PROTECT link and lost.

Conditions: The symptom is observed under the following conditions:

1. A Cisco 7600 series router with two WS-SUP720-3B cards and two OSM-1CHOC12/T1-SI.

2. The router is running Cisco IOS Release 12.2(33)SRB5.

3. Issue may occur during hard reset (removing the power) of the Cisco 7600 series router.

4. Issue is reproducible by enabling member links on Protect MLFR line card first, then enabling member links on the active MLFR line card like this:

A. Make sure all serial interface are in "shutdown" state.

B. Configure two MFR bundles (say MFR1 and MFR2) and subinterfaces MFR1.1 and MFR2.1

C. Configure four serial interfaces as a member of MFR1 under the OSM-1CHOC12/T1-SI which is in an inactive state.

D. Configure another four serial interfaces as a member of MFR2 under the OSM-1CHOC12/T1-SI which is in SONET APS active state.

E. Give "no shut" on the MFR serial member interfaces belonging to SONET APS inactive OSM-1CHOC12/T1-SI F. Give "no shut" on the MFR serial member interfaces belonging to SONET APS active OSM-1CHOC12/T1-SI

Observe that all the MFR serial member interfaces configured are in "UP/UP" state and both (inactive and active OSM-1CHOC12/T1-SIs) MFR interfaces are also UP.

5. Issue does NOT happen under same conditions when using MLPPP or straight serial links. 6. Issue also reproducible after simple reload in ~40% of reloads.

Workaround 1: Perform a shut, no shut on APS Protect MFR interface.

Workaround 2: Perform a shut on the member links configured under the inactive controller.

CSCtb88060

Symptoms: When unidirectional Ethernet (UDE) is configured, UDLD configurations are nullified. On taking out UDE configs, the port should re-participate in UDLD. But is not happening here.

Conditions: The problem is seen if we configure udld port aggressive command.

Workaround: To use the global command udld enable.

CSCtb89424

Symptoms: In rare instances, a Cisco router may crash while using IP SLA udp probes configured using SNMP and display an error message similar to the following:

hh:mm:ss Date: Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x424ECCE4

Conditions: This symptom is observed while using IP SLA.

Workaround: There is no workaround.

CSCtb90653

Symptoms: TCP ports 4509, 4510, and 2222 are opened without any configuration.

Conditions: The following releases are affected: Cisco IOS Release 12.2(33)SRD, 12.2(33)SRD1, 12.2(33)SRD2, 12.2(33)SRD2a, and 12.2(33)ZZ.

Workaround: Disable the listening of the ports with the privileged CLI command: test platform ezdriver deactivate.

CSCtb99472

Symptoms: Doing an OIR of a PA-2CT3 Port Adapter in subrate mode causes some of the interface configurations to get lost and the subrate channels to go down.

Conditions: The symptom is observed with Cisco 7200 series routers that is running with Cisco IOS Release 12.2(33)SRD2.

Workaround: To reapply the serial configuration, perform a "shut/no shut".

CSCtc01196

Symptoms: ISIS topology is broken after two or three consecutive SSOs with "isis nsf ietf" enabled. This causes routes to be missing in the routing table and permanent traffic loss.

Conditions: The symptom is observed when "isis nsf ietf" is enabled and the restarting router comes up too slowly, causing neighboring routers on LAN interfaces to time out.

Workaround: Perform a shut/no shut on the interface and ISIS will re-establish adjacency with the neighbors on the LAN interface.

CSCtc04459

Symptoms: High CPU is observed when sequential IMSI values are sent in a PDP request and, as a result, low NDR is observed.

Conditions: The symptom is observed under the following conditions:

1. GTP-SLB is configured.

2. Sequential IMSI values are sent in a GTP PDP request.

Workaround: Use random IMSI values.

CSCtc15394

Symptoms: The parity errors are seen on a 4XOC3-ATM 1XOC3-ATM 1XOC12-ATM SPA while it is operational and plugged into SIP200 or SIP400 chassis with or without traffic running.

Conditions: No known conditions. Soft errors can happen any time due to environmental effects.

Workaround: There is no workaround.

CSCtc17058

Symptoms: VC stops sending traffic due to duplicate VPN ID in port-based EoMPLS.

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD.

Workaround: Do a shut/no shut on the interface (either on the same interface on which the VC has stopped sending traffic or an interface which has the port-based EoMPLS configured on the router).

CSCtc17311

Symptoms: TCAM device has corrupted data for valid entries seen in an X40G line card.

Conditions: The symptom occurs during a background TCAM consistency checker.

Workaround: There is no workaround.

Further Problem Description: Ignore these messages as the entries are already corrected.

CSCtc17429

Symptoms: Multicast packets for some IP multicast groups get duplicated.

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD2a and having an SRP ring as the OIF interface for IP multicast. The duplicate packets for those groups can be seen using the command show ip mroute count on the other nodes in the SRP ring.

Workaround: There is no workaround.

CSCtc22745

Symptoms: Without PMTU configured and the interface MTU is 1500 on the L2TPv3 uplinks, packets are not fragmented.

Conditions: Occurs with packets that require fragmentation between the L2TPv3 endpoints.

Workaround: There is no workaround.

CSCtc24864

Symptoms: CDP is disabled and its neighbors are not seen on a CDP-enabled QnQ port after a shut/no shut operation.

Conditions: The symptom is observed on an L2 QnQ tunnel port. By default, on L2 QnQ tunnel port CDP is disabled. CDP can, however, be enabled on a QnQ port through the command cdp enable. After enabling the CDP on a QnQ port, a subsequent link down and link up (shut and no shut) of this QnQ port results in disabling the CDP which is the default behavior.

Workaround: Configure CDP (using the cdp enable command) again after link up.

CSCtc24959

Symptoms: Occasionally you may experience a multicast traffic loss in dual path line cards.

Conditions: The symptom is observed in dual path line cards. Occasionally, met2 programming will go out of sync between two data paths.

Workaround: Any change that triggers reprogramming that entry will help. Changing replication mode to ingress is a workaround.

CSCtc32238

Symptoms: mVPN traffic is not getting forwarded after SUP failover.

Conditions: The symptom is observed under the following conditions:

The multicast traffic is flowing from ingress PE towards egress PE.

Used redundancy force-switchover or primary SUP OIR for the SUP failover on ingress PE.

Some of the mVPN traffic flows stopped forwarding the traffic.

Workaround: There is no workaround.

CSCtc33158

Symptoms: A router may experience packet drops for the following packet byte size ranges, only when L2TPv3 cookies are enabled:

238-241

494-497

750-753

1006-1009

1262-1265

The following error will be reported when the packets are dropped:

%DEV_SELENE-DFC3-3-XAUI_LEN: Selene 0 XAUI 0 Packet Length Error

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD2, using an interface on a 7600-ES+40G3CXL module for a core-facing L2TPv3 tunnel.

Workaround: Disable L2TPv3 cookies.

CSCtc36588

Symptoms: After reload in Cisco IOS Release 12.2(33)SRD3, the MAC address of a port-channel, including member links on the supervisor, is set to 0000.0000.0000.

Conditions: This issue is seen after a reload in Cisco IOS Release 12.2(33)SRD3 and when a port-channel has member links on the supervisor.

Workaround: Configure the MAC address as follows:

7600(config)#interface port-channel XY

7600(config-if)#mac-address XXXX.YYYY.ZZZZ

CSCtc37147

Symptoms: RPF check fails when default route originates from IS-IS and the egress interface is a TE tunnel.

Conditions: This symptom is observed when IS-IS is configured as the routing protocol and the default route originates from IS-IS.

Workaround: Use the ip mroute command or route-leaking to set a specific route in the table. Enter show ip route 0.0.0.0 to determine if the next hop for the default route is an MPLS tunnel interface. If it is, enter ip mroute to configure the real interface that the MPLS TE tunnel uses for the default route multicast nexthop.

Alternate workaround: Use the OSPF routing protocol rather than IS-IS.

CSCtc38796

Symptoms: In some instances, when the Cisco 7600/RSP720/RP crashed and the core dump is configured to be created. But this coredump is corrupted and recognized by gdb.

Conditions: This symptom is seen only with RSP720.

Workaround: There is no workaround.

CSCtc40677

Symptoms: The distribute-list applied to the virtual-template interface is not effective for the virtual-access interfaces spawned by that template. For example, configured on the ASR (hub) is:

router eigrp 1

redistribute static metric 10000 100 255 1 1500

network 10.0.0.0

no auto-summary

distribute-list prefix TEST out Virtual-Template1 !

ip route 0.0.0.0 0.0.0.0 Null0

!

ip prefix-list TEST seq 10 permit 0.0.0.0/0 ip prefix-list TEST seq 20 permit

10.0.0.0/8

and on the branch site connected via a virtual-access interface:

Branch#sh ip route eigrp

Load for five secs: 0%/0%; one minute: 0%; five minutes: 0%

10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks

D 10.0.0.0/8 [90/46251776] via 10.12.0.2, 00:00:06, Dialer1

D 10.1.1.0/24 [90/46228736] via 10.12.0.2, 00:00:06, Dialer1

D 10.2.2.0/24 [90/46354176] via 10.12.0.2, 00:00:06, Dialer1

D*EX 0.0.0.0/0 [170/46251776] via 10.12.0.2, 00:00:06, Dialer1

This shows that no filtering was applied, since the 10.1.1.0/24 and 10.2.2.0/24 should have been dropped off the updates.

Conditions: The symptom is observed on a Cisco ASR 1000 series router that is running Cisco IOS Release 12.2(33)XND1.

Workaround: Configure the distribute-list for the specific virtual-access interface used for the connections on the hub.

CSCtc41760

Symptoms: A Cisco 6500 may experience redzone crash at UDLD process. The following message may appear:

%SYS-SP-3-OVERRUN: Block overrun at 44456570 (red zone 6D000700)

-Traceback= 40291448 402938DC 40D74570 40D763A0

Traceback will vary from code to code.

Conditions: UDLD is configured

Workaround: Disable UDLD.

CSCtc46171

Symptoms: LTLs leak for VPLS VC after an SSO.

Conditions: The symptom is observed with "Auto Discovery" VPLS VCs after an SSO.

Workaround: There is no workaround.

CSCtc46174

Symptoms: A Cisco 10000 series router that is configured for ISG has no limit for number of redirected sessions which could result in high CPU.

Conditions: This symptom is observed on a Cisco 10000 series router that is running ISG and Cisco IOS Release 12.2(33)SB or 12.2(31)SB.

Workaround: There is no workaround.

CSCtc46512

Symptoms: There is a crash in SSR regression.

Conditions: The symptom is observed when a service policy is applied on a session and traffic is flowing through the session. This applies to IOU (simulator) images only.

Workaround: There is no workaround.

CSCtc52149

Symptoms: SIP200 CPU 1 crashes as indicated below.

SLOT 4: Aug 16 14:42:52.115 KSA: %R4K_MP-3-CRASHED: CPU 1 has now crashed a total of 1 times

Conditions: There is no specific trigger to this problem. It happens randomly and recovers on its own.

Workaround: There is no workaround.

CSCtc52236

Symptoms: SIP module crash.

Conditions: There is no specific trigger to this problem. It happens randomly and recovers on its own.

Workaround: There is no workaround.

Further Problem Description: This happens when an IP packet removes padding calculated from ATM control.

CSCtc52740

Symptoms: Cisco 7600 ES+ interface will not accept policy map with "random-detect cos-based" statement.

Conditions: CLI configuration is rejected on main interface of an ES+ line card.

Workaround: There is no workaround.

CSCtc57044

Symptoms: The mpls propagate-cos command may not function correctly on a Cisco 7600 router.

Conditions: This was observed on several Cisco 7600s running Cisco IOS Release 12.2(33)SRC.

Workaround: Remove and reapply the mpls propagate-cos command.

CSCtc58898

Symptoms: In MPLS VPN scenario, if it happens that default route known via RIP in VRF is looping, route might stay in RIB.

Conditions: Issue observed in Cisco IOS Release 12.2(33)SRC4 and 12.2(33)SRC5.

Workaround: Clear VRF routing table of with the clear ip route vrf name * command.

CSCtc60458

Symptoms: On a Cisco 7600 router with a large number of VCs and VLANs, traffic stops forwarding traffic for several seconds while standby supervisor is booting.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRC4.

Workaround: There is no workaround.

CSCtc60463

Symptoms: The traceroute mac src_mac dst_mac command can cause a software crash on a Cisco 7600 router when configured with a large number of VLANs.

Conditions: This occurs on a Cisco 7600 router running Cisco IOS Release 12.2(33)SRC4.

Workaround: Do not use the traceroute mac src_mac dst_mac command. Use a specific VLAN ID when using this command.

CSCtc60958

Symptoms: After the line card reset or router reload, the CLI (committed as part of CSCtb88169) does not get applied.

Conditions: The issue is seen with a router reload or line card reset.

Workaround: Reconfigure the command manually once the line card is up.

CSCtc61025

Symptoms: For VPLS autodiscovered pseudowires using FEC129, the label release message is not understood by the peer in Inter-op tests.

Conditions: The symptom is observed when you delete the VFI or shut the attachment circuit to cause the label withdraw message to be sent. The peer will correspondingly send the label release message.

Workaround: There is no workaround.

CSCtc75774

Symptoms: Protect channel shows signal failure with working channel even though working channel is up and working correctly.

Conditions: The symptom is observed when the protect channel acts as an active controller and when you do a shut/no shut on the working channel which acts as an inactive controller.

Workaround: There is no workaround.

CSCtc77028

Symptoms: A Cisco 10000 series router with a mix of passthrough, TAL, prepaid and postpaid sessions may experience a memory leak at sss_pm_post_authorization_cleanup.

Conditions: The symptom is observed on a Cisco 10000 series router running a PRE-3 and Cisco IOS Release 12.2(33)SB7.

Workaround: Reload the router.

CSCtc81653

Symptoms: The system crashes if the port-channel is removed while it is serving data traffic.

Conditions: Port-channel is configured with the member links in it. The traffic is sent through the port-channel. If the port-channel is removed, the system sometimes crashes.

Workaround: There is no workaround.

CSCtc84758

Symptoms: On a router configured for ISG that is running postpaid Web-Logon users with SESM as the external portal, a memory leak may occur in RADIUS LOCAL SERVER.

Conditions: The symptom is observed on a Cisco 10000 series router with a PRE-3 and running Cisco IOS Release 12.2(33)SB7 using SESM as a captive portal. The issue can be triggered with this sequence of events:

1. Postpaid user is redirected to SESM.

2. SESM sends Access-Request to router after captivating user/pass from postpaid user.

3. RADIUS LOCAL SERVER creates AAA request and sends it to ISG.

4. ISG creates another AAA request to send an Access-Request to authenticate the postpaid user.

5. AAA receives a response from external AAA.

6. AAA passes the response to RADIUS LOCAL SERVER which transmits an Access-Accept or Access-Reject to SESM.

If the processing delay of sum (C,D,E,F) is greater than the SESM timeout, SESM will send another Access-Request with the same credentials for the Account logon postpaid user in B.

If this occurs, policy/AAA will now use this second Account-Logon request from SESM for this user's Account Login and the policy will not free the AAA request from the former Account Logon request, hence the memory leak will present as RADIUS LOCAL SERVER.

Workaround:

1. Make sure SESM Account Logon Timeout > RADIUS timeout.

2. Decrease load on external AAA (RADIUS) machines.

CSCtc87700

Symptoms: A Cisco 7600 router may fail to process ingress Link Integrity Protocol messages on MFR serial link members, which will disallow Multilink Frame Relay interfaces from enabling.

Conditions: This symptom occurs on a Cisco 7600 router with SUP-720-3BXL and OSM CHOC12, and running Cisco IOS Release 12.2(33)SRC and 12.2(33)SRD. This issue happens when MFR serial members are configured on CHOC12 OSM but may also occur on other line cards.

Workaround: There is no workaround.

CSCtc87822

Symptoms: On a PE router, eBGP-learned VRF routes might not be advertised to eBGP neighbors in the same VRF.

Conditions: The symptom is observed if DUT first learns the route from IBGP-VPNv4 (same RD) and then learns the route from the CE.

Workaround: Soft clear towards the CEs missing the routes.

CSCtc90579

Symptoms: Router crashes due to memory corruption during MPLS TE auto backup tunnel deletion.

Conditions: Caused by topology changes triggering backup tunnel deletion and RSVP hello mechanism.

Workaround: Gloablly, disable RSVP hello and enable BFD hello:

Router(config)#no ip rsvp signalling hello

Router(config)#ip rsvp signalling hello bfd

Per MPLS TE enabled interface:

Router(config-if)#no ip rsvp signalling hello

Router(config-if)#ip rsvp signalling hello bfd

CSCtc94339

Symptoms: Multicast traffic is not forwarded in an egress direction via GRE over MPLS after a switchover.

Conditions: The symptom is observed with GRE over MPLS with PIM enabled on the tunnel interface, from a Cisco 7600 series router in SSO redundancy mode.

Workaround: Reload the router.

Further Problem Description: Identification of this issue can be seen when "dindex" shows as 0x0. In working state it is 0x7FFA:

show mls cef adjacency encap-tunnel detail

Index: 30 mtu: 1522, vlan: 1016, dindex: 0x0, l3rw_vld: 1 <<<<

format: ENCAP-TUNNEL, flags: 0x11103500008600

ip_sa: 10.10.10.10 ip_da: 10.20.20.20, tos: 0 ttl: 255

wccp_hdr: 0, gre_hdr: 800

packets: 415, bytes: 48970

CSCtc94873

Symptoms: After few show memory commands the telnet session to a Cisco 7600 series router is suspended and the router crashes. Traceback shows:

-Traceback= 406AAEA0 406AB400 418164AC 418050B8 4067460C 406787E4 4067B7D8 4063076C 423BB0F4 4065D058 417CB1C8 417CB1B4 Decode

Conditions: The symptom is observed with a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD3 and with "show memory" commands.

Workaround: Do not use show memory fragment commands.

Further Problem Description: When BFD is enabled and when the command show memory [fast] fragment detail is invoked, the crash/hang is observed at times. This is partially fixed with this DDTS to overcome SCHED-SEMNOTLOCKED error. Another part of it is fixed with CSCtd94438.

CSCtd00054

Symptoms: Link flap/down on PA-MC-T3E3-EC interface.

Conditions: This symptom is observed when changing encapsulation after reload.

Workaround: Perform an online insertion and removal (OIR) of the PA.

CSCtd00479

Symptoms: When ISIS is configured for NSF IETF, if the restarting router is a DIS on the LAN, after a switchover the ISIS database and topology could be incorrect. This results in an incorrect routing table.

Conditions: The symptom is observed when ISIS is configured for NSF IETF and a switchover occurs.

Workaround: Use NSF CISCO, or disable NSF.

CSCtd15853

Symptoms: When removing VRF configuration on remote PE, local PE receives withdraw message from remote PE to purge its MDT entry. However, local PE does not delete the MDT entry.

/// Topology ///

iBGP

<------------------->

12.2(33)SB7 12.0(27)S4a

1.1.1.1/32 2.2.2.2/32

PE1(UUT) ------------ PE2

PE1 receives MDT entry from PE1 and PE2.

Please focus a entry of "2.2.2.2/32" from PE2.

PE-1

---

PE1-PRE2#

PE1-PRE2#sh ip bgp ipv4 mdt all

BGP table version is 13, local router ID is 1.1.1.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

Route Distinguisher: 1:1 (default for vrf V1)

*> 1.1.1.1/32 0.0.0.0 0 ?

*>i2.2.2.2/32 2.2.2.2 0 100 0 ? <<<---- HERE

*>i3.3.3.3/32 3.3.3.3 0 100 0 ?

---

To trigger the issue, vrf configuration is remove on PE2.

You can see that PE2 sends withdraw message to PE1(1.1.1.1).

PE-2

---

PE2-PRE1#

PE2-PRE1#

PE2-PRE1#conf term

Enter configuration commands, one per line. End with CNTL/Z.

PE2-PRE1(config)#

PE2-PRE1(config)#no ip vrf V1

Tunnel interface was deleted. Partial configuration may reappear on reuse.

% IP addresses from all interfaces in VRF V1 have been removed

PE2-PRE1(config)#

PE2-PRE1(config)#

*Nov 9 12:29:35.447: %LINK-5-CHANGED: Interface Tunnel3, changed state to

administratively down

*Nov 9 12:29:36.467: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel3,

changed state to down

PE2-PRE1(config)#

PE2-PRE1(config)#end

PE2-PRE1#

PE2-PRE1#

*Nov 9 12:30:05.435: BGP(2): nettable_walker 2:1:1:2.2.2.2/32 no best path

*Nov 9 12:30:05.435: BGP(2): 1.1.1.1 send unreachable 2:1:1:2.2.2.2/32

*Nov 9 12:30:05.435: BGP(2): 1.1.1.1 send UPDATE 2:1:1:2.2.2.2/32 --

unreachable <<--- HERE

*Nov 9 12:30:05.435: BGP(2): updgrp 1 - 1.1.1.1 enqueued 1 updates,

average/maximum size (bytes) 45/45

PE2-PRE1#

PE2-PRE1#

PE2-PRE1#sh ip vrf

PE2-PRE1#

---

The MDT entry(2.2.2.2/32) is not deleted even if PE1 indeed receives withdraw message from PE2. "clear ip bgp *" would be needed to purge the MDT entry.

PE-1

---

PE1-PRE2#

*Nov 9 12:29:34.323: BGP:from:3 to:4 update format 1:1:3.3.3.3/0 MDT grp

239.0.0.1 pfxptr->masklen 96

*Nov 9 12:29:34.323: BGP:from:3 to:4 update format 1:1:1.1.1.1/0 MDT grp

239.0.0.1 pfxptr->masklen 96

*Nov 9 12:29:34.323: BGP(4): 2.2.2.2 send UPDATE (format) 2:1:1:1.1.1.1/32,

next 1.1.1.1, label 0, metric 0, path Local

*Nov 9 12:29:34.323: BGP:from:3 to:4 update format 1:1:2.2.2.2/0 MDT grp

239.0.0.1 pfxptr->masklen 96

*Nov 9 12:29:34.323: BGP(4): updgrp 1 - 2.2.2.2 updates replicated for neighbors:

*Nov 9 12:30:05.799: BGP(4): 2.2.2.2 rcv UPDATE about 1:1:2.2.2.2/64 --

withdrawn, label 3 <<--- HERE

*Nov 9 12:30:05.799: BGP: 2.2.2.2 Modifying prefix 1:1:2.2.2.2/64 from 4 -> 3

address

PE1-PRE2#

PE1-PRE2#sh ip bgp ipv4 mdt all

BGP table version is 13, local router ID is 1.1.1.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

Route Distinguisher: 1:1 (default for vrf V1)

*> 1.1.1.1/32 0.0.0.0 0 ?

*>i2.2.2.2/32 2.2.2.2 0 100 0 ? <<---- HERE

*>i3.3.3.3/32 3.3.3.3 0 100 0 ?

PE1-PRE2#

PE1-PRE2#

PE1-PRE2#clear ip bgp *

PE1-PRE2#

*Nov 9 12:31:22.043: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Down User reset

*Nov 9 12:31:22.043: %BGP_SESSION-5-ADJCHANGE: neighbor 2.2.2.2 VPNv4 Unicast

topology base removed from session User reset

*Nov 9 12:31:22.043: %BGP_SESSION-5-ADJCHANGE: neighbor 2.2.2.2 IPv4 MDT

topology base removed from session User reset

*Nov 9 12:31:22.043: %BGP-5-ADJCHANGE: neighbor 3.3.3.3 Down User reset

*Nov 9 12:31:22.043: %BGP_SESSION-5-ADJCHANGE: neighbor 3.3.3.3 VPNv4 Unicast

topology base removed from session User reset

*Nov 9 12:31:22.043: %BGP_SESSION-5-ADJCHANGE: neighbor 3.3.3.3 IPv4 MDT

topology base removed from session User reset

*Nov 9 12:31:22.555: %BGP-5-ADJCHANGE: neighbor 3.3.3.3 Up

*Nov 9 12:31:22.563: BGP(3): 3.3.3.3 rcvd UPDATE w/ attr: nexthop 3.3.3.3,

origin ?, localpref 100, metric 0

*Nov 9 12:31:22.563: BGP(3): 3.3.3.3 rcvd 1:1:3.3.3.3/32

PE1-PRE2#

PE1-PRE2#

PE1-PRE2#sh ip bgp ipv4 mdt all

BGP table version is 1, local router ID is 1.1.1.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

Route Distinguisher: 1:1 (default for vrf V1)

* i3.3.3.3/32 3.3.3.3 0 100 0 ?

---

Conditions:

mVPN is configured on PE router.

Both Pre-MDT SAFI and MDT-SAFI IOS are running in a Multicast Domain.

CCO : MDT SAFI

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6557/ps6604/ps6651/prod_white_paper0900aecd80581f3d.html

Workaround: There is no workaround.

CSCtd21590

Symptoms: RP crashed after executing no import ipv4 unicast map filter.

Conditions: BGP import events debugging is on with debug ip bgp import updates or debug ip bgp import event.

Workaround: Do not enable debug ip bgp import event or debug ip bgp import update.

CSCtd25133

Symptoms: Router gets into APS channel mismatch state.

Conditions: Observed with MGX connected as APS peer, when both MGX cards (active and standby) are reloaded simultaneously.

Workaround: Force APS switchover.

CSCtd25933

Symptoms: Active or standby RP crashes on executing the shut then no shut commands on the interface.

Conditions: The symptom is observed with the following conditions:

1. Encapsulation QnQ (or dot1q) is configured and removed on the sub-interface, on a WAN interface (SIP400).

2. Same VLAN configured as Encapsulation QnQ (or dot1q) on a LAN interface (ES+).

3. Perform shut/no shut on the ES+ interface.

Workaround: There is no workaround.

CSCtd27247

Symptoms: The router crashes when doing concurrent VRF add and deletion configurations.

Conditions: The symptom is observed when a multiple configuration terminal is doing concurrent VRF add and deletion configurations.

Workaround: Do not do concurrent VRF addition and deletion.

CSCtd33145

Symptoms: On a Cisco 10000 series router/PRE-3 that is running Cisco IOS Release 12.2(33)SB7 and ISG, the memory on the standby RP may become severely fragmented due to some SSS functions.

After an SSO switchover, the new-active RP initially takes over with fragmented memory causing frequent malloc errors and eventually requiring a reload to recover.

Conditions: The symptom is observed on a Cisco 10000 series router/PRE-3 that is running Cisco IOS Release 12.2(33)SB7 with 10K ISG sessions in a mix of web-login, TAL, prepaid, and passthrough.

Workaround: A reload will recover memory.

CSCtd35091

Symptoms: The input queue on ISG access interface gets filled up causing the interface to wedge.

Conditions: The symptom is observed when an L2-connected IP session for a client exists on the ISG and traffic from that client comes in with a different IP address to the one used to identify the session. This traffic is dropped and interface wedging is observed.

Workaround: There is no workaround other than a router reload.

CSCtd40804

Symptoms: The EVC configuration does not exist on the ES20 line card. The first "show" command (below) shows that the EVC was known to the Route Processor (RP) on the Supervisor Engine, while the second command shows that the EVC did not exist on the ES20 line card in slot 4:

#sh ethernet service instance id 3555 interface gi4/0/1

Identifier Interface State CE-Vlans

3555 GigabitEthernet4/0/1 UP

#remote command mod 4 sh ethernet service instan id 3555 int gi4/0/1

EFP ID 3555 on interface GigabitEthernet4/0/1 does not exist

Conditions: The symptom is observed after a Supervisor switchover.

Workaround: There are two workarounds for this issue. Both require that every port on the ES20 be configured prior to a switchover. If this is done, then the problem will not exist after a switchover and new EVCs can be successfully added following the switchover.

1. Configure at least one service instance under each interface on the ES20. An example is shown below:

interface GigabitEthernet1/0/3

service instance 1 ethernet

encapsulation dot1q 3

2. Configure "ethernet uni id name under each interface on the ES20. An example is shown below:

interface GigabitEthernet1/0/5

ethernet uni id gi_1_0_5

CSCtd54338

Symptoms: The following output from the command show ip rtp header-compression, shows that one channelized serial interface has a large accumulated number of "seconds since line card sent last stats update" compared with another channelized serial interfaces in device with the same platform:

GR_SA_CORE_7613R_1#show ip rtp header-compression Serial1/2/0.1/3/1:0

RTP/UDP/IP header compression statistics:

Interface Serial1/2/0.1/3/1:0 (compression on, Cisco)

Distributed fast switched:

10364 seconds since line card sent last stats update

Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs

0 dropped, 0 buffer copies, 0 buffer failures

Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted

0 bytes saved, 0 bytes sent

Connect: 16 rx slots, 16 tx slots,

0 misses, 0 collisions, 0 negative cache hits, 0 free contexts

Conditions: The symptom is observed with the following conditions:

Cisco IOS Release 12.2(33)SRD3.

Platform: Cisco 7613 router.

RP: RSP720-3CXL-GE.

SIP: Cisco 7600 SIP-200.

SPA: SPA-1XCHSTM1/OC3.

This issue normally begins to show when the count of the channelized subinterface (number of cRTP sessions) is 200 or over.

Workaround: Disable then enable RTP header-compression on the interface.

Further Problem Description: The issue can be resolved by using disable cRTP and enable cRTP on each subinterface (see DDTS CSCso48621). However, sometimes the problem can reoccur in a few days after recovery on the same subinterface.

CSCtd62220

Symptoms: The following error is seen:

%DATACORRUPTION-1-DATAINCONSISTENCY: copy error

Conditions: The symptom is observed under normal use. The issue is not consistently reproducible and is a corner case.

Workaround: There is no workaround.

CSCtd66014

Symptoms: ES+ line card crashes at powerup of a Cisco 7600 router that is running Cisco IOS 12.2SRE image if either the Traffic Manager or Frame memories in the ES+ Network processors report a double bit ECC error. The ES+ line card crashinfo will have the following string:

%NP_DEV-DFC2-3-ECC_DOUBLE: Double-bit ECC error detected on NP 0, Mem 19, SubMem 0x1,SingleErr 1, DoubleErr 1 Count 1 Total 1

Conditions: Router reloads, OIR of ES+ cards, system environment temperatures that slowly vary around an ambient temperature of about 30 degreesC. This happens at system powerup. We have seen double bit ECC problems reported after a few hours of traffic if the ambient temperatures vary around 30 degreesC.

Workaround: No configuration workaround is available. The line card will reset itself and will be operational in the second reload.

CSCtd66918

Symptoms: Standby Supervisor continually resets during detection of bad hardware in the system.

Conditions: The symptom is observed when the bad line card is inserted in the slot following the Standby Supervisor slot (e.g.: Standby Supervisor in slot 6 and bad line card in slot 7).

Workaround: There is no workaround.

CSCtd72426

Symptoms: Checkpointing facility on the standby SP is leaking memory buffers. This can lead to a WATERMARK error message.

Conditions: The symptom is observed with the checkpointing facility on the standby SP.

Workaround: There is no workaround.

Further Problem Description: This issue can be checked with the command show ipc session all verbose from the standby SP. This output will show more messages requested then messages returned for the client "CHKPT:STANDBY SP" and this difference will grow every day. The show check client command from the standby SP will show the buffers held for "REP CHKPT CLIENT" and that this value is increasing over time.

CSCtd72462

Symptoms: A Cisco 7600 series router with an RSP720-3C processor may unexpectedly reboot after the show policy-map interface command is executed.

Conditions: The issue is seen when there is a policy map on an interface with the following:

No set action.

No shared aggregate policer action.

No aggregate policer action.

uflow policer with "conform action" configured.

Workaround: There is no workaround.

CSCtd75033

Symptoms: Cisco IOS Software is affected by NTP mode 7 denial-of-service vulnerability.

Conditions: Cisco IOS Software with support for Network Time Protocol (NTP) contains a vulnerability processing specific NTP Control Mode 7 packets. This results in increased CPU on the device and increased traffic on the network segments.

This is the same as the vulnerability which is described in http://www.kb.cert.org/vuls/id/568372.

Cisco has release a public facing vulnerability alert at the following link:

http://tools.cisco.com/security/center/viewAlert.x?alertId=19540

Cisco IOS Software that has support for NTPv4 is NOT affected. NTPv4 was introduced into Cisco IOS Software: 12.4(15)XZ, 12.4(20)MR, 12.4(20)T, 12.4(20)YA, 12.4(22)GC1, 12.4(22)MD, 12.4(22)YB, 12.4(22)YD, 12.4(22)YE and 15.0(1)M.

All other versions of Cisco IOS and Cisco IOS XE Software are affected.

To see if a device is configured with NTP, log into the device and issue the CLI command show running-config | include ntp. If the output returns either of the following commands listed then the device is vulnerable:

ntp master <any following commands>

ntp peer <any following commands>

ntp server <any following commands>

ntp broadcast client

ntp multicast client

The following example identifies a Cisco device that is configured with NTP:

router#show running-config | include ntp

ntp peer 192.168.0.12

The following example identifies a Cisco device that is not configured with NTP:

router#show running-config | include ntp

router#

To determine the Cisco IOS Software release that is running on a Cisco product, administrators can log in to the device and issue the show version command to display the system banner. The system banner confirms that the device is running Cisco IOS Software by displaying text similar to "Cisco Internetwork Operating System Software" or "Cisco IOS Software." The image name displays in parentheses, followed by "Version" and the Cisco IOS Software release name. Other Cisco devices do not have the show version command or may provide different output.

The following example identifies a Cisco product that is running Cisco IOS Software Release 12.3(26) with an installed image name of C2500-IS-L:

Router#show version

Cisco Internetwork Operating System Software

IOS (tm) 2500 Software (C2500-IS-L), Version 12.3(26), RELEASE SOFTWARE

(fc2)

Technical Support: http://www.cisco.com/techsupport

Copyright ) 1986-2008 by cisco Systems, Inc.

Compiled Mon 17-Mar-08 14:39 by dchih

<output truncated>

The following example shows a product that is running Cisco IOS Software Release 12.4(20)T with an image name of C1841-ADVENTERPRISEK9-M:

Router#show version

Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version

12.4(20)T, RELEASE SOFTWARE (fc3)

Technical Support: http://www.cisco.com/techsupport

Copyright ) 1986-2008 by Cisco Systems, Inc.

Compiled Thu 10-Jul-08 20:25 by prod_rel_team

<output truncated>

Additional information about Cisco IOS Software release naming conventions is available in "White Paper: Cisco IOS Reference Guide" at the following link:

http://www.cisco.com/warp/public/620/1.html

Workaround: There are no workarounds other than disabling NTP on the device. The following mitigations have been identified for this vulnerability; only packets destined for any configured IP address on the device can exploit this vulnerability. Transit traffic will not exploit this vulnerability.

Note: NTP peer authentication is not a workaround and is still a vulnerable configuration.

* NTP Access Group

Warning: Because the feature in this vulnerability utilizes UDP as a transport, it is possible to spoof the sender's IP address, which may defeat access control lists (ACLs) that permit communication to these ports from trusted IP addresses. Unicast Reverse Path Forwarding (Unicast RPF) should be considered to be used in conjunction to offer a better mitigation solution.

!--- Configure trusted peers for allowed access

access-list 1 permit 171.70.173.55

!--- Apply ACE to the NTP configuration

ntp access-group peer 1

For additional information on NTP access control groups, consult the document titled "Performing Basic System Management" at the following link:

http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_basic_sys_manage.html#wp1034942

* Infrastructure Access Control Lists

Warning: Because the feature in this vulnerability utilizes UDP as a transport, it is possible to spoof the sender's IP address, which may defeat ACLs that permit communication to these ports from trusted IP addresses. Unicast RPF should be considered to be used in conjunction to offer a better mitigation solution.

Although it is often difficult to block traffic that transits a network, it is possible to identify traffic that should never be allowed to target infrastructure devices and block that traffic at the border of networks.

Infrastructure ACLs (iACLs) are a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The iACL example below should be included as part of the deployed infrastructure access-list, which will help protect all devices with IP addresses in the infrastructure IP address range:

!---

!--- Feature: Network Time Protocol (NTP)

!---

access-list 150 permit udp TRUSTED_SOURCE_ADDRESSES WILDCARD

INFRASTRUCTURE_ADDRESSES WILDCARD eq 123

!--- Note: If the router is acting as a NTP broadcast client

!--- via the interface command "ntp broadcast client"

!--- then broadcast and directed broadcasts must be

!--- filtered as well. The following example covers

!--- an infrastructure address space of 192.168.0.X

access-list 150 permit udp TRUSTED_SOURCE_ADDRESSES WILDCARD

host 192.168.0.255 eq ntp

access-list 150 permit udp TRUSTED_SOURCE_ADDRESSES WILDCARD

host 255.255.255.255 eq ntp

!--- Note: If the router is acting as a NTP multicast client

!--- via the interface command "ntp multicast client"

!--- then multicast IP packets to the mutlicast group must

!--- be filtered as well. The following example covers

!--- a NTP multicast group of 239.0.0.1 (Default is

!--- 224.0.1.1)

access-list 150 permit udp TRUSTED_SOURCE_ADDRESSES WILDCARD

host 239.0.0.1 eq ntp

!--- Deny NTP traffic from all other sources destined

!--- to infrastructure addresses.

access-list 150 deny udp any

INFRASTRUCTURE_ADDRESSES WILDCARD eq 123

!--- Permit/deny all other Layer 3 and Layer 4 traffic in

!--- accordance with existing security policies and

!--- configurations. Permit all other traffic to transit the

!--- device.

access-list 150 permit ip any any

!--- Apply access-list to all interfaces (only one example

!--- shown)

interface fastEthernet 2/0

ip access-group 150 in

The white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection access lists and is available at the following link:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml

* Control Plane Policing

Provided under Control Plane Policing there are two examples. The first aims at preventing the injection of malicious traffic from untrusted sources, whilst the second looks at rate limiting NTP traffic to the box.

- Filtering untrusted sources to the device.

Warning: Because the feature in this vulnerability utilizes UDP as a transport, it is possible to spoof the sender's IP address, which may defeat ACLs that permit communication to these ports from trusted IP addresses. Unicast RPF should be considered to be used in conjunction to offer a better mitigation solution.

Control Plane Policing (CoPP) can be used to block untrusted UDP traffic to the device. Cisco IOS Software Releases 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T support the CoPP feature. CoPP can be configured on a device to help protect the management and control planes and minimize the risk and effectiveness of direct infrastructure attacks by explicitly permitting only authorized traffic that is sent to infrastructure devices in accordance with existing security policies and configurations. The CoPP example below should be included as part of the deployed CoPP, which will help protect all devices with IP addresses in the infrastructure IP address range.

!--- Feature: Network Time Protocol (NTP)

access-list 150 deny udp TRUSTED_SOURCE_ADDRESSES WILDCARD

any eq 123

!--- Deny NTP traffic from all other sources destined

!--- to the device control plane.

access-list 150 permit udp any any eq 123

!--- Permit (Police or Drop)/Deny (Allow) all other Layer3 and

!--- Layer4 traffic in accordance with existing security policies

!--- and configurations for traffic that is authorized to be sent

!--- to infrastructure devices

!--- Create a Class-Map for traffic to be policed by

!--- the CoPP feature

class-map match-all drop-udp-class

match access-group 150

!--- Create a Policy-Map that will be applied to the

!--- Control-Plane of the device.

policy-map drop-udp-traffic

class drop-udp-class

drop

!--- Apply the Policy-Map to the

!--- Control-Plane of the device

control-plane

service-policy input drop-udp-traffic

In the above CoPP example, the access control list entries (ACEs) that match the potential exploit packets with the "permit" action result in these packets being discarded by the policy-map "drop" function, while packets that match the "deny" action (not shown) are not affected by the policy-map drop function.

- Rate Limiting the traffic to the device The CoPP example below could be included as part of the deployed CoPP, which will help protect targeted devices from processing large amounts of NTP traffic.

Warning: If the rate-limits are exceeded valid NTP traffic may also be dropped.

!--- Feature: Network Time Protocol (NTP)

access-list 150 permit udp any any eq 123

!--- Create a Class-Map for traffic to be policed by

!--- the CoPP feature

class-map match-all rate-udp-class

match access-group 150

!--- Create a Policy-Map that will be applied to the

!--- Control-Plane of the device.

!--- NOTE: See section "4. Tuning the CoPP Policy" of

!--- http://www.cisco.com/web/about/security/intelligence/coppwp_gs.html#5

!--- for more information on choosing the most

!--- appropriate traffic rates

policy-map rate-udp-traffic

class rate-udp-class

police 10000 1500 1500 conform-action transmit

exceed-action drop violate-action drop

!--- Apply the Policy-Map to the

!--- Control-Plane of the device

control-plane

service-policy input drop-udp-traffic

Additional information on the configuration and use of the CoPP feature can be found in the documents, "Control Plane Policing Implementation Best Practices" and "Cisco IOS Software Releases 12.2 S—Control Plane Policing" at the following links:

http://www.cisco.com/web/about/security/intelligence/coppwp_gs.html and http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtrtlimt.html

CSCtd75248

Symptoms: With QoS is disabled globally and when the ES20 interface is configured as a trunk, if traffic is sent with a valid COS value, the ES20 re-marks all COS values to "0".

Conditions: The symptom is observed when QoS is globally disabled.

Workaround: Enable QoS globally using mls qos and trust the ES20 trunk interface to retain CoS values using mls qos trust cos.

Further Problem Description: This issue is not seen in Cisco IOS Release 12.2(33)SRB. It is present in Cisco IOS Release 12.2(33)SRC onwards

CSCtd77905

Symptoms: Traffic will not flow properly for the first VRF, if there is a switchover from active to standby. This issue occurs because of a race condition.

Conditions: The symptom is observed only in the HA setup.

Workaround: Delete and reconfigure the problematic VRF.

Further Problem Description: The problem is a timing issue. In the standby Supervisor, the aggregate labels are not getting programmed properly for the first VRF configured in the system.

CSCtd83819

Symptoms: Traffic drops on SIP400 upon unconfiguring and reconfiguring "bre-connect vlan-id".

Conditions: The symptom is observed when you unconfigure and reconfigure "bre-connect vlan-id".

Workaround: Remove and reconfigure the PVC, or reload the SPA, or do an APS switchover.

CSCtd87264

Symptoms: DHCP unicast BootP offers can not be propagated back in the incoming interface as the ARP entry is missing. This happens only when the relay function is combined in a VRF and the incoming interface is unnumbered.

Conditions: The symptom is observed when SRD/SRE Cisco 7600 series router is a DHCP relay/snooping agent. The request must come in a VRF.

Workaround: Move the relay agent function to the global routing table.

CSCtd90429

Symptoms: VPLS traffic occasionally gets blackholed after multiple iterations of mid-point failure or reoptimization.

Conditions: The symptom is observed when the core-facing interfaces are SIP400.

Workaround: Perform a shut/no shut on the TE tunnel interface.

CSCtd91012

Symptoms: If BRE configurations are present on the HWIDB, when you configure an APS group an error message will be thrown to remove the BRE configurations.

Conditions: The symptom is observed when there are BRE configurations on the HWIDB and you try to configure an APS group.

Workaround: Remove the BRE configurations and then configure the APS group.

CSCtd94128

Symptoms: On ES+ cards, packets in the egress direction do not have the outer tag preserved.

Conditions: This is seen on a port-mode configuration for an L2TPv3 tunnel where tagged packets are sent from the subscriber. The outer tag is always rewritten to null while the COS bits are preserved.

Workaround: There is no workaround.

CSCtd94438

Symptoms: When the show memory fast fragment detail command is given, it leads to a crash of the Cisco 7600 series router. The console logs show some semaphore lock-related messages, IPC/XDR messages, and RP crash-related messages.

Conditions: The symptom is observed when BFD is enabled and the show memory fast fragment detail command is given.

Workaround: Avoid using the show memory fast fragment detail command, or disable BFD from the startup configuration and reload the router.

Further Problem Description: If BFD is disabled in the startup configuration (i.e.: BFD is not configured when bringing up the router) the crash is not seen.

CSCtd99244

Symptoms: ES+ line card crashes reporting double bit ECC error.

Conditions: This symptom occurs usually in the initial phases of line card bootup, but this has also been reported after a few hours of traffic through the ES+ line card ports.

Workaround: There is no workaround. The ES+ may not report this error in the second reload. If errors persist, powercycle the chassis, or OIR the ES+.

CSCtd99248

Symptoms: There could be occasional double bit ECC errors for the traffic manager and other metadata memories that are reported on the Network processor on the ES+ line card.

Conditions: This symptom is observed when the router reloads, OIR of ES+ cards, system environment temperatures that slowly vary around an ambient temperature of about 30 degreesC. This happens at system powerup. We have seen double bit ECC problems reported after a few hours of traffic if the ambient temperatures vary around 30 degreesC.

Workaround: No configuration workaround is available. The line card will reset itself and will be operational in the second reload.

CSCte14504

Symptoms: Router crash with TLB (load or instruction fetch) exception.

Conditions: The symptom is observed with a reload of the router that is running a Cisco IOS SRD Release.

Workaround: There is no workaround.

Further Problem Description: This is memory issue and so it might not be seen at every reload. In the local testbed, the crash is seen after a reload with a few VRF configurations under VLAN.

CSCte21958

Symptoms: A Cisco router may reload when an L2TP xconnect pseudowire is configured using a pseudowire class that has not yet been defined.

Conditions: This symptom is observed when the following sequence of commands is entered:

configure terminal

interface Ethernet0/0.1

encapsulation dot1Q 400

xconnect 10.0.0.1 555 encapsulation l2tpv3 pw-class test

pseudowire-class test

encapsulation l2tpv3

protocol l2tpv3 test

ip local interface Loopback0

vpdn enable

This symptom affects all platforms.

Workaround: Define the pseudowire class using the pseudowire- class configuration command before referencing that pseudowire class in an xconnect configuration.

CSCte28933

Symptoms: L2TPv3 VLAN-mode reassembled packets get dropped on ES+.

Conditions: The symptom is observed when "L2TPv3 cookie" is configured and L2TPv3 packets get fragmented in the core or at source.

Workaround: Configure L2TPv3 without cookies.

CSCte37192

Symptoms: Traffic is dropped in the egress by SIP400.

Conditions: The symptom is observed when BRE is configured, then removed, then reconfigured. Then perform a shut/no shut on the interface where the PVC is present.

Workaround 1: Perform a shut/no shut on the interface.

Workaround 2: Perform a SPA OIR.

CSCte38652

Symptoms: The standby reloads due to one of the line cards getting powered down with the reason given as: "Failed to configure the line card".

Conditions: The symptom is observed with a fully-loaded setup with all ESM20G cards and a large amount of configuration.

Workaround: There is no workaround.

CSCte38681

Symptoms: Configuration sync error is seen upon enabling/disabling AAL5 encapsulation along with two reloads.

Conditions: The symptom is observed only with a reload and upon disabling/enabling the AAL5 encapsulation.

Workaround: Reload the router.

CSCte46834

Symptoms: The router crashes.

Conditions: The symptom is observed with the following steps on the PE:

config t

ip vrf vpna

import map IMPORT99 (this is the trigger).

Workaround: There is no workaround.

CSCte48935

Symptoms: Following a reload, the ES20 port is unbundled from the port-channel and the following error message is shown:

Port-channel10 and TenGigabitEthernet9/0/0 have different trust states

Conditions: The symptom is observed with "mls qos" disabled globally and "mls qos trust" disabled on the ES20 interface.

Workaround: Enable "mls qos" on the router. If "mls qos" is not desired, there is no workaround.

CSCte50573

Symptoms: Degraded performance with RLB and T-RLB.

Conditions: The symptom is observed with the following conditions:

1. SLB is configured with service radius.

2. High CPU even at lower rates of 300 TPS.

3. Cisco IOS Release 12.2(33)SRE.

Workaround: There is no workaround.

CSCte56594

Symptoms: Seeing two dips of traffic drop after SSO, the first dip is about 80 milliseconds, the second traffic dip up to about 30 seconds.

Conditions: This symptom is observed on the PE (Cisco 7609-S) that is configured with OSPF NSF and both MPLS and RSVP GR. Also 4K vlans, 20K virtual circuit is configured peering with another 5 PEs on the VPLS domain. Generate 60M unidirectional traffic across this VPLS domain, then execute redundancy switchover via CLI.

Workaround: There is no workaround.

CSCte58686

Symptoms: Link flaps after an upgrade to Cisco IOS Release 12.2(33)SRD3.

Conditions: The symptom is observed following an upgrade from Cisco IOS Release 12.2(33)SRB5 to SRD3.

Workaround: There is no workaround.

CSCte58749

Symptoms: Some interfaces start flapping upon upgrading to Cisco IOS Release 12.2(33)SRD3.

Conditions: This is a corner case condition. The interface flaps occur under following conditions:

1. The peer connected on the other side of the interface sends a CODEREJ for a valid ECHOREP sent by a Cisco router.

2. On receiving CODEREJ for ECHOREP, the router terminates the PPP session. The PPP sessions restart, and the interface flaps.

Workaround: Disable keep-alive on the misbehaving peer router.

CSCte67196

Symptoms: On a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD3 equipped with an OSM-CHOC12 line card, if a member link is removed and re-added to a multilink group during periods of congestion, the multilink interface may not recover its full transmit bandwidth.

This issue only occurs when "service-policy output" is configured on the multilink interface and when this service policy contains queuing actions.

This condition may be accompanied by the "show policy-map" interface failing to update packet counters and offered rate.

Conditions: The symptom is observed on a Cisco 7600 series router that is running Cisco IOS Release 12.2(33)SRD3 equipped with an OSM-CHOC12 line card aggregating multilink interfaces using queuing policy-maps.

Workaround: Remove and reapply "service-policy output" from the degraded multilink interface.

CSCte68259

Symptoms: Random end-to-end traffic failure with an ES+ line card with L2TPv3 termination on one port which is interfacing with EVC BD remotely.

Conditions: This issue occurs when the ES+ line card is configured with the L2TPv3 feature.

Workaround: There is no workaround.

CSCte95228

Symptoms: The line card 7600-ES+ on a Cisco 7600 series router may reload due to memory corruption.

Conditions: One of the conditions is cable pull with scaled configurations. This is seen with VPLS configuration only so far. This is a rare situation and seen only once.

Workaround: Shut the port on which OIR is done.

CSCte99481

Symptoms: After SSO if you get drop for around 30 secs having VPLS and 4k HWIBDS.

Further Problem Description: After switchover the process which clears the counters for HWIDBS take the whole of CPU and not allowing OSPF to work properly. Resulting in the drop of traffic.

CSCti78408

Symptoms: %SYS-DFC4-3-CPUHOG: Task is running for (128000)msecs, more than (2000)msecs (4/3),process = console_rpc_server_action.

%SYS-DFC4-2-WATCHDOG: Process aborted on watchdog timeout, process = console_rpc_server_action.

Conditions: This issue can be seen with the following conditions:

1. Issuing show tech command on ES+

2. Issuing show platform hardware config-pld command on ES+

Workaround: Do not use show tech and show platform hardware config-pld commands on ES+.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD3

Cisco IOS Release 12.2(33)SRD3 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD3 but may be open in previous Cisco IOS releases.

CSCee63182

Symptoms: A Cisco router may crash or may stop responding.

Conditions: This has been always seen with an atm interface only when a rate-limit command is enabled on the interface. The crash occurs when an interface that is configured with a rate-limit command is deleted by entering the no interface command and then reenabled by entering the interface command.

Workaround: Remove the rate-limit configuration from the interface before deleting the interface.

Further Problem Description: Happens under very specific circumstances and the crash is seen randomly.

CSCse15495

Symptoms: The following CLASS-BASED-QOS-MIB counters are incorrect in output direction:

- cbQosCMPrePolicyByte64

- cbQosCMPostPolicyByte64

In input direction cbQosCMDropByte64 is incremented and is always equal to cbQosCMPrePolicyByte64.

Conditions: Hardware specific setup: SIP-600 and 10GE SPA.

Workaround: There is no workaround.

CSCse29527

Symptoms: A Cisco 7600 Series router or Cisco Catalyst 6500 Switch may unexpectedly reload due to bus error when running remote command switch show mmls met.

Conditions: Occurs when the device is doing multicast.

Workaround: Do not run the command.

CSCse97873

Symptoms: Resilient Ethernet Protocol (REP) flaps due to excessive CPU utilization occurs.

Conditions: Occurs in a Resilient Ethernet Protocol (REP) segment if 4000 VLANs are configured on the router and if VLANs are allowed on a switchport.

Workaround: There is no workaround.

CSCse99958

Symptoms: A Cisco router may fail to access a flash card after formatting it, and the following error message is generated:

*** Emulating mis-aligned load at 0x80000190 PC = 0x8001179c ... succeeded

Conditions: The symptom is observed on a Cisco 7200 series, Cisco 7301, and Cisco 7500 series that run Cisco IOS Release 12.4(10) or Release 12.4(12) and occurs only when a flash card is accessed from the ROMmon prompt.

Workaround: There is no workaround. Note that the symptom does not occur in Release 12.4(8a) or an earlier release.

CSCsh54161

Symptoms: Under certain unusual circumstances, routes can go SIA in an EIGRP network and create transient routing loops.

Conditions: When the metric on an interface increases rapidly, the symptom can occur. This can happen with MANET interfaces as well as bundled interfaces (such as port-channels).

Workaround: There is no workaround.

CSCsl01427

Symptoms: The following symptoms all relate to the same root cause:

1. In syntax check mode, if there is a standby in SSO mode, the cts dot1x command does not work and the following error messages are displayed:

RouterRP(syntax-if)#cts dot1x %ERROR: Standby doesn't support this command ^ % Invalid input detected at '^' marker.

RouterRP(syntax-archive)#path disk0: %ERROR: Standby doesn't support this command ^ % Invalid input detected at '^' marker.

2. After a redundancy force-switchover, the applet configuration is lost and retains only the applet name. (This is done by configuring an applet on the main RP and switchover to the Standby by issuing a redundancy force-switchover. Issue the sh run command on the Standby which is now the main RP.) All the action statements are lost.

3. The Standby switch reloads by itself after going into the event manager applet configuration mode:

Config Sync: Line-by-Line sync verifying failure on command: event manager applet cli-test-01 due to parser return error

4. The Standby switch may also reload upon removing the command event manager applet:

RouterRP(config)#event manager applet 1 EEM: Applet 1 is currently being modified

OR

RouterRP(config)#no event manager applet 1 EEM: Applet 1 is currently being modified

Conditions: The symptoms are observed in syntax check mode, if there is a standby in SSO mode.

Workaround: There is no workaround.

CSCsl33908

Symptoms: The image name displayed in show version will be truncated to 64 characters if the image name is more than that.

Conditions: It occurs in High Availability (HA) setup.

Workaround: There is no workaround.

CSCsl66427

Symptoms: Shortly after replacing FlexWAN, SNMP queue starts to fill and SNMP queue full error message is printed:

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full

Conditions: Occurs on a Cisco 7600 router running Cisco IOS Release 12.2(33)SRD1.

Workaround: Apply following view:

snmp-server view Flash iso included

snmp-server view Flash ciscoFlashMIB exclude

snmp-server view Flash ciscoFlashDevice exclude

snmp-server view Flash ciscoFlashPartitions exclude

snmp-server view Flash ciscoFlashPartitionTable exclude

snmp-server view Flash ciscoFlashPartitionEntry exclude

snmp-server community <name> view Flash RW

If this is not enough to get rid of SNMP queue full, reload the router so that the view applies at the router bootup.

CSCsm26063

Symptoms: Router crashes following a shut/no shut on the main interface.

Conditions: Occurs on a router running Cisco IOS Release 12.2SXH2a. IPv6 traffic must be flowing over the WAN interface for multiple IPv6 prefixes. The crash occurs when a shut/no shut is done on the main interface on which multiple subinterfaces have been configured and IPv6 routing is enabled.

Workaround: There is no workaround.

CSCsm85890

Symptoms: When there are two PA-2T3 cards on a VIP6-80 and hard loop one port on one PA-2t3, it causes the port on the second PA-2T3 card to flap. The impact of the issue is that the interface flaps once and it results in dropping of 6-7 packets.

Conditions: When we do a shut/no shut on a serial port, the other serial port on the same VIP might flap once.

Workaround: Put each PA-2T3 card on different VIP modules.

Further Problem Description: Any Cisco IOS release that incorporates CSCsj96781 will definitely see this bug. The other affected serial port can belong to the same PA (in case of two-port T3+ PA) or it can belong to a different PA on a different bay but on same VIP.

CSCso29141

Symptoms: A Catalyst 6500 switch with an etherchannel spanning multiple DFC modules may drop packets for a certain MAC on egress. This happens when one of the DFCs carrying the etherchannel has an incorrectly programmed MAC address entry, pointing at the internal drop index.

Conditions: This only occurs in an asymmetric routing scenario, where frames are constantly egressing the etherchannel destined for certain MAC addresses, but frames are not consistently seen from those MAC addresses. This is often the case when Hot Standby Routing Protocol (HSRP) is running, and this particular switch is the HSRP standby.

Workaround: Through tweaking ARP and MAC address aging timers, this situation can be avoided. We recommend that the MAC address aging timer be set at least 3 times higher than the ARP timer for the VLAN interface.

The configuration for this is:

Switch(config)#mac-address synchronize

Switch(config)#mac-address aging-time 900

Switch(config)#interface Vlan360

Switch(config-if)#arp timeout 300

Further Problem Description: While a MAC address is in this condition, the following outputs will look like this:

Switch#show mac-address-table address 0000.0000.0001 all det

MAC Table shown in details ========================================

PI_E RM RMA Type Alw-Lrn Trap Modified Notify Capture Flood Mac Address Age Pvlan SWbits Index XTag ----+---+---+----+-------+----+--------+------+-------+------+--------------+----+------+------+------+---- Module 1: No No No DY No No Yes No No No 0000.0000.0001 0x3A 360 0 0x7FFF 0 Active Supervisor: No No No DY No No Yes No No No 0000.0000.0001 0x69 360 0 0x342 0

Here, we see that the MAC address is not present on Module 2, which it should be. On Module 1, we see that the index pointed to is 0x7FFF, which represents the internal drop index in the 6500. Also, we see the "Flood" bit is set to 'No'. In this condition, all frames egressing Module 1 for this MAC will be dropped. Had "Flood=Yes", the frames would be flooded instead of dropped, which is normal behavior.

CSCso42210

Symptoms: Following reload, controllers come up, but interfaces stay down.

Conditions: A router with HA Sup720 and non-HA Sup32 is connected with 8xCHT1/E1 SPA, 1xCHSTM1 SPA and 4xCT3 SPA in a SIP-200. Upon reloading 8xCHT1/E1 SPA alone on both sides simultaneously, 6-7 interfaces go down and never come up. They show as up/up in line card but up/down in RP.

Workaround: There is no workaround.

CSCso84507

Symptoms: When a downgrade is done from Cisco IOS Release 12.2(33)SB to Release 12.2(31)SB, the Standby that is loaded with Cisco IOS Release 12.2(31)SB fails to do config sync and keeps crashing.

Conditions: This symptom occurs when both Active and Standby are loaded with Cisco IOS Release 12.2(33)SB image with PPPOX (PPPoA or PPPoE) configurations. Standby is downgraded to Cisco IOS Release 12.2(31)SB. The standby loaded with Cisco IOS Release 12.2(31)SB fails to do configuration sync and keeps crashing after configuring issu loadversion command.

This is also seen in the case of an upgrade from Cisco IOS Release 12.2(31)SB* to Cisco IOS Release 12.2(33)SB image, after issu runversion command, when Active has Cisco IOS Release 12.2(33)SB and Standby has Cisco IOS Release 12.2(31)SB* image.

Workaround: For upgrade from Cisco IOS Release 12.2(31)SB* to Cisco IOS Release 12.2(33)SB image:

After issu runversion command, when Active has Cisco IOS Release 12.2(33)SB:

1. Configure the following:

router#configure terminal router(config)#redundancy router(config-red)#force-rpr 1

2. Cisco IOS Release 12.2(31)SB* becomes Standby and will crash once and then come up in RPR mode.

3. Do issu commitversion and Standby will come up with Cisco IOS Release 12.2(33)SB image.

For downgrade from Cisco IOS Release 12.2(33)SB to Cisco IOS Release 12.2(31) SB* image:

1. Configure the following on Active PRE Cisco IOS Release 12.2(33)SB:

router#configure terminal router(config)#redundancy router(config-red)#force-rpr 1

2. Do issu loadversion command, which causes Standby to go down and come up as Standby (Cisco IOS Release 12.2(31)SB*). The new Standby will crash once and then come up in RPR mode.

3. Do issu runversion command to make Standby as Active (Cisco IOS Release 12.2(31)SB*).

4. Do issu commitversion command and Standby will come up in Cisco IOS Release 12.2(31)SB*.

The force-rpr 1 command is removed from the configuration by now, since Cisco IOS Release 12.2(31)SB* image does not support this command.

CSCsq71492

Symptoms: A Cisco IOS device may reload with an address error or have alignment errors and tracebacks such as %ALIGN-3-SPURIOUS or %ALIGN-3-TRACE

Conditions: The symptoms are most likely to occur when the TACACS+ server (ACS) sends an "authentication error" when ACS is configured, or when a request timeout occurs. There may be other AAA or TACACS related conditions that cause the symptom.

Workaround: There is no workaround.

CSCsq82041

Symptom: Memory leak when remote PEs have more xconnects configured than UUT

Conditions: set session limit under vpdn-group and over subscribe sessions. Workaround: NA

CSCsq84624

Symptoms: A Cisco router might crash when debug condition portbundle ip 10.1.1.1 bundle 0 is configured.

Conditions: Occurs when this command is executed prior to configuring ip portbundle.

Workaround: There is no workaround.

CSCsr06094

Symptoms: A Cisco router may ungracefully reload.

Conditions: The symptom is observed when the router is processing CoA RADIUS messages and when certain debugs are turned on.

Workaround: Disable all debugs.

CSCsr17660

Symptoms: PE-CE performance degradation of 80% on initial convergence.

Conditions: Occurs when BGP and VPNv4 are configured.

Workaround: There is no workaround.

Further Problem Description: Performance is not affected after initial convergence.

CSCsr75700

Symptoms: In very rare cases, a Cisco 10000 series router crashes with a log similar to:

%Software-forced reload Breakpoint exception, CPU signal 23, PC = 0x408FAFC0

Possible software fault. Upon recurrence, please collect crashinfo, "show tech" and contact Cisco Technical Support.

-Traceback= 408FAFC0 408F8B78 41990010 419910E0 41992DB8 42158AF4 41992EC0 41953F8C 41956C1C

(Note that the hex values of the traceback may be different.)

Conditions: The symptom is observed on a Cisco 10000 series router that is running Cisco IOS Release 12.2(33)SB1.

Workaround: There is no workaround.

Further Problem Description: The occurrence of the problem so far has been rare. The decode of the traceback points to a BGP issue. The confirmation of whether a crash is due to this bug in BGP or not can only be made after the traceback from the crash has been decoded by Cisco support engineers.

CSCsr88705

Symptoms: Redistributed routes are not being advertised after a neighbor flap.

Conditions: This symptom is observed if BGP is redistributing local routes and if there are multiple neighbors in the same update-group and then a neighbor flaps. For the flapped neighbor, some redistributed routes are not being advertised.

Workaround: Undo and redo the redistribution.

CSCsr90248

Symptoms: Changing any of the parameters of a route-map does not take effect.

Conditions: Occurs when using a BGP aggregate-address with an advertise map.

Workaround: Delete the aggregate-address statement and then put it back for the change to take effect.

CSCsu11668

Symptoms: A router configured with BGP import from the global IPv4 table into a VRF using the VRF configuration command import ipv4 unicast map ... may exhibit a brief traffic outage to destinations reached through the imported routes following a switchover.

Conditions: Global to VRF import must be configured under the VRF. Issue only affects Cisco IOS Release 12.29(33)SR releases.

Workaround: There is no workaround.

CSCsu26526

Symptoms: Memory leak can be seen on the LNS.

Conditions: The symptom is observed on the L2TP Network Server (LNS) when the PPP client does a renegotiation.

Workaround: There is no workaround.

CSCsu49189

Symptoms: Frame-Relay fragment output not seen when modifying the attached map-class.

Conditions: Occurs on a Cisco 7200 router.

Workaround: Detach and attach Frame-Relay fragment.

CSCsu72059

Symptoms: After multiple OIRs, memory gets fragmented in line card and at one stage the mallocs start failing.

Conditions: There is a higher chance of fragmentation when we have ATM OC3 SPAs in both the bays and huge configurations which eat up lot of memory.

Workaround: Reload the line card.

CSCsu74400

Symptoms: A device running FTP to transmit the DHCP database may experience a file descriptor leak that results in errors such as:

ROUTER#show run

OR

ROUTER#show start Using XXXX out of XXXX bytes %Error opening nvram:/startup-config (Bad file number)

OR

ROUTER#dir nvram: Directory of nvram:/ %Error opening nvram:/ (File table overflow) XXXX bytes total (XXXX bytes free)

Conditions: Occurs when the router is configured to use FTP to transmit the DHCP database:

ip dhcp database ftp://XXXX:XXXX@X.X.X.X/XXXX

And the FTP server becomes unreachable. The file descriptor leak can be viewed in the output of show file descriptors:

ROUTER-B#show file descriptors File Descriptors:

FD Position Open PID Path 0 0 0302 145 ftp://X.X.X.X/DHCP 1 0 0302 145 ftp://X.X.X.X/DHCP 2 0 0302 145 ftp://X.X.X.X/DHCP 3 0 0302 145 ftp://X.X.X.X/DHCP 4 0 0302 145 ftp://X.X.X.X/DHCP 5 0 0302 145 ftp://X.X.X.X/DHCP 6 0 0302 145 ftp://X.X.X.X/DHCP 7 0 0302 145 ftp://X.X.X.X/DHCP 8 0 0302 145 ftp://X.X.X.X/DHCP 9 0 0302 145 ftp://X.X.X.X/DHCP <snip>

Workaround: Ensure that the FTP server does not become unreachable for more than 128 total minutes, as there are only 128 file descriptors. In the event that all 128 file descriptors are leaked, a reboot is required to recover.

CSCsu79754

Symptoms: PIM packets may be processed on interfaces which PIM is not explicitly configured.

Conditions: Unknown at this time.

Workarounds: Create an ACL to drop PIM packets to such interfaces.

CSCsv07467

Symptoms: When doing IP session on Layer 4 Redirect with VPN routing/forwarding (VRF) web logon scale test, subscriber tries to authenticate with 20 characters per second from test tool. MCP crashed into ROMMon

Conditions: Occurs only when test tool sends authentication at 20 characters per second

Workaround: There is no workaround.

CSCsv21612

Symptoms: High CPU on PM callback process on SP. Depending on the number of trunk links configured, the high CPU time increases exponentially with the number of trunk links.

Conditions: This occurs when VTP pruning is enabled and there are too many trunk links. High CPU on PM callback process is normal as the switch is pruning the VLANs. Problem only occur when there are too many trunk links and the high CPU last for too long and affects other layer 2 operations.

Workaround: Disable VTP pruning or reduce the number of trunk links. For phones, use mode access with voice VLAN configured if this configuration is supported by phone.

CSCsv27372

Symptoms: GRE tunnel terminates on switch where Server Load Balancing (SLB) is configured. Traffic to SLB VIP and real server fails and causes crash.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRC2. Router crashes and creates core dump while doing a telnet to a real server under NAT-configured server farm using GRE Tunnel.

Workaround: There is no workaround.

CSCsv38225

Symptoms: Router may reload when you unconfigure and then configure the ipv multicast-routing commands in quick succession.

Conditions: Occurs when these commands are entered in quick succession, such as with copy and paste.

Workaround: Allow for a delay when entering the commands ipv multicast-routing and no ipv multicast-routing.

CSCsv43802

Symptoms: System crashes while running online diags.

Conditions: The system may crash when there is a spike in CPU utilization or traffic in the system.

Workaround: There is no workaround.

CSCsv61073

Symptoms: BGP neighbors may experience increased flapping.

Conditions: Occurs when large number of BGP neighbors are configured with aggressive BGP hold-timer values.

Workaround: Increase the BGP hold-timer values beyond 10/30.

CSCsv62777

Symptoms: VTY session may get stuck after some extended pings are done and the CPU process may go high.

Conditions: The symptom is observed when an extended ping with CLNS is done and the command is left incomplete until the vty session times out.

Workaround: Issue can be prevented by not leaving the extended 'ping clns' command incomplete for long time in the vty session.

CSCsv90106

Symptoms: A router may write a crashinfo that lacks the normal command logs, crash traceback, crash context, or memory dumps.

Conditions: This might be seen in a memory corruption crash depending on precisely how the memory was corrupted.

Workaround: There is no workaround.

CSCsw16157

Symptoms: Routers using OSPF and MPLS Traffic Engineering may crash or operate incorrectly following changes to the configuration of MPLS-TE tunnel interfaces or OSPF. In some cases a configuration change will cause an immediate crash, while in others memory may be corrupted resulting in problems later.

Routers using MPLS-TE primary auto-tunnels are particularly vulnerable because those tunnel interfaces may be removed as the result of network topology changes as well as by modifying the running configuration.

Conditions: In order to be exposed to this problem, a router must have MPLS TE tunnel interfaces that are announced to OSPF. Systems that do not run OSPF, or which do not use MPLS-TE are not affected.

Systems that operate without "service alignment detection" enabled may crash when the following configuration commands are issued:

Global configuration mode:

* no interface tunnel <n> * no router ospf * no mpls traffic-eng auto-tunnel

Interface configuration mode:

* no ip unnumbered * no ip address

Exec mode:

* clear mpls traffic-eng auto-tunnel

Note that routers running modular IOS (ION) and IOS-XE do not have alignment detection enabled.

Regardless of the state of alignment detection, removing the last MPLS-TE tunnel interface to a destination can cause problems, as can removing auto-tunnel configuration. Removal of dynamically created auto-tunnel interfaces as a result of changes in the network topology has the same effect.

Note that routers using auto backup tunnels to provide fast reroute for static MPLS-TE tunnels do not have any extra exposure to this bug because while these backup tunnels may be removed due to topology changes, the static tunnel to the same destination will not be.

Normal UP/DOWN state changes of tunnel interfaces do not cause problems.

Workaround: To remove a MPLS-TE tunnel interface, first configure it down with the "shutdown" command in interface submode.

To remove an OSPF instance, first disable MPLS-TE for the instance by configuring "no mpls traffic-eng area <n>" in router ospf submode.

No workaround is available for MPLS-TE auto-tunnels.

CSCsw25200

Symptoms: When flapping a fiber, the link protocol comes up, but the line protocol does not.

Conditions: Occurs on links between SIP modules.

Workaround: Perform a shut/no shut on the interface.

CSCsw39190

Symptoms: Both active and standby supervisors crash.

Conditions: Occurs when Control Plane Policing (COPP) is configured and there are multiple session churns happening with PPPoE subscribers.

Workaround: There is no workaround.

CSCsw48359

Symptoms: With traffic flowing normally over a GRE tunnel terminating on the ES20 line card the module will crash when IPSec tunnel protection is enabled.<BR><BR>

Conditions: Occurs when tunnel endpoint is an interface on the ES20 line card.<BR><BR>

Workaround: This crash is seen only when GRE is accelerated by spa-ipsec-2g. If GRE is accelerated by the SUP, the crash does not happen. This is done by default in VRF mode without any other directives like "crypto engine mode gre vpnblade". To ensure the tunnel is adding "crypto engine gre supervisor" in the global configuration mode and on all the tunnels that are handled by ES20 for mpls recirculations.

As an alternative workaround, If the customer wants the GRE acceleration to be taken over by the spa-ipsec-2g. An ACL needs configured to drop all the plain unencrypted GRE traffic between a tunnel's source and destination ip addresses may also be effective if applied prior to configuring the "tunnel protection ..." command. However, this workaround may not scale in certain configurations.<BR><BR>

As a preventive precautionary measure. A safer practice would be to configure the Customer Edge device prior to configuring the Provider Edge. This configuration order should prevent this issue from occuring when adding IPSec Tunnel protection to GRE Tunnels.

CSCsw50069

Symptoms: Microflow policing fails to be removed or modified on port-channel subinterface.

Conditions: Occurs on a Cisco 7600 series router with port-channel subinterface configured for microflow policing, and the same policy configured on subinterface with encap VLAN as well as another subinterface without encap VLAN.

Workaround: There is no workaround.

CSCsw73196

Symptoms: BGP MDT session flaps when a router running Cisco IOS is interoperating with a router running Cisco IOS-XR and when withdrawal messages are sent by IOS to XR of previously advertised MDT prefixes.

Conditions: MDT prefixes need to be exchanged by IOS and XR routers. If a withdrawal message is exchanged subsequently for any reason then this problem is seen.

Workaround: There is no workaround.

CSCsw76817

Symptoms: Whenever MTU is configured under a port-channel with EVC (Ethernet Virtual Circuit), the MTU functionality does not work as expected.

Conditions: This happens only with Layer 3 port-channels.

Workaround: There is no workaround.

Further Problem Description: Whenever a member link is added to a port-channel, the member link's MTU is programmed to the jumbo MTU value (default 9216). Even when a custom MTU value is configured under port-channel, all the member links' MTUs are programmed with 9216.

CSCsw93867

Symptoms: The following messages appear in the log after a reload:

Suspending service policy (policyname) on Multilink(#)bandwidth of 24.00% is not available (1.00%)

bandwidth of 24.00% is not available (1.00%)

bandwidth of 24.00% is not available (1.00%)

bandwidth of 24.00% is not available (1.00%)

Conditions: A Cisco 7600 running Cisco IOS Release 12.2(33)SRB2 and 12.2(33)SRB3 with Multilink interface configured for CBWFQ QOS policy will suspend policy and display error message similar to the above if service-policy is applied to Multilink interface at time of route loading.

Workaround: Load router with no service-policies applied and apply them after router is up.

CSCsx03301

Symptoms: Crash in TCP.

Conditions: Happens when clearing a BGP neighbor. The trigger is uncertain and hard to reproduce.

Workaround: There is no workaround.

CSCsx07159

Symptoms: A policy-map is applied to an interface on ESM20G card and has a random-detect aggregate action configured in a class. If another class is added to the policy-map which has match statement as "match cos <cos-value>", this class gets added. Now if random-detect aggregate is removed from the previous class, an error message is dumped on screen :

'match cos' combined with other match statements at the same class level is not supported for this interface.

If random-detect action is added to this class, router crashes.

Conditions: Occurs with the following configuration:

policy-map PMAP_UPLINKS

class CMAP-RT-COS (match cos <vaue>)

class CMAP-BC-EXP

no random-detect aggregate

random-detect -----> (CRASH)

Workaround: Do not add a class-map with "match cos" filter to a policy-map which conflicts with other class-map filters.

CSCsx07537

Symptoms: Delay in bootup time of the line cards occurs during reload with diags enabled. Issue not seen when diags are disabled.

Conditions: There is no specific configuration or traffic combination that will trigger this issue. Issue seen with or without any Ethernet Virtual Circuit (EVC) configs or traffic conditions.

Workaround: Disable bootup diags or power down the 6748-GE-TX card

CSCsx08861

Symptoms: ATOM VC status is seen as down in standby RP and traffic loss is seen after switchover for 44 seconds.

Conditions:

1. Bring 6RU up (SSO) with 1 AToM VC, 1 AToM VP (Initial VC state: active:UP; standby:HOTSTANDBY)

2. Delete the AToM VC sub-int ('no int a2/2/0.122') and delete the AToM VP sub-int ('no int a2/2/0.1001')

3. Re-configure back the same AToM VC and VP configuration (VC state: Active:UP; Standby:DOWN for AToM VC)

4. If I do a force switchover ('redundancy force-switchover'). It will experience ~44 seconds of traffic lost for this VC.

Workaround: There are two work around for this issue:

1. Do not reconfigure the ATOM VC immediately after deleting a subinterface.

2. Do not copy and paste the ATOM VC configuration. Either do it manually step by step or copy the configuration from a file.

CSCsx09343

Symptoms: PKI daemon is stuck in DNS resolution attempt for the hostname used in the CDP.

Conditions: The when symptom is observed using name resolution for automatic actions taken by the router during non-interactive sessions (CRL download using name in CDP URI). Only applicable if 'ip domain-lookup' is enabled within the config

Workaround: There is no workaround.

CSCsx10086

Symptoms: When trying to configure a peer template using the command template peer-session S1_1 under router bgp 1 , it enters into UNKNOWN-MODE. Once there, we cannot get out of that mode and the router has to be rebooted.

Conditions: The bug is seen only in Cisco ION images. Cisco IOS images are fine. Following is an example:

ip39-1(config)#router bgp 1

ip39-1(config-router)#template peer-session S1_1

ip39-1(UNKNOWN-MODE)#?

% Unrecognized command

ip39-1(UNKNOWN-MODE)#end ^ % Invalid input detected at '^' marker.

Workaround: There is no workaround.

CSCsx15138

Symptoms: Device crashes upon entering command sh policy-map interface.

Conditions: Unknown at this time.

Workaround: There is no workaround.

CSCsx34584

Symptoms: Crash is seen when 1000 IP sessions identified by same MAC address are setup and torn down using Cisco Intelligent Services Gateway (ISG).

Conditions:

1. Setup 1000 IP sessions on ISG on one port. 2. Setup another 1000 sessions on second port with same MAC address range as in first port. 3. Ensure 1000 sessions are up. The other 1000 sessions setup request would be rejected as they are using the same MAC address as in step 1. 4. Clear the 1000 sessions using clear sss session all. 5. Repeat steps 2, 3, and 4 until crash is seen.

Note: This scenario is not supported and has been documented. Please refer to the Restrictions section on the following URL: http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/isg_sub_aware_enet.html#wp1074579

Workaround: This is a negative test case and will never happen in practical setups as the MAC addresses will not overlap. Also the network topology should ensure that the same subscriber MAC address does not appear on more than one physical interface.

CSCsx46415

Symptoms: Virtual Private LAN Services (VPLS) unicast traffic not flowing over the VC when core-facing port is ESM20 line card.

Conditions: Core-facing port must be on the 9th slot or higher in a Cisco 7609 or Cisco 7613 chassis. Also the VC neighbor scale should be very high on that VPLS VLAN.

Workaround: Use slots lower than 9.

CSCsx49573

Symptoms: Three separate Cisco IOS Hypertext Transfer Protocol (HTTP) cross-site scripting (XSS) vulnerabilities and a cross-site request forgery (CSRF) vulnerability have been reported to Cisco by three independent researchers.

The Cisco Security Response is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sr-20090114-http.shtml

Conditions: See "Additional Information" section in the posted response for further details.

Workarounds: See "Workaround" section in the posted response for further details.

CSCsx55152

Symptoms: Switch does not send TC trap if it is not a root bridge

Conditions: If switch is a root bridge, it generates TC trap when link goes both up and down. But if switch is not a root bridge, it generates TC trap only when link goes up.

Workaround: There is no workaround.

CSCsx58335

Symptoms: When relaying to multiple servers from an unnumbered interface, the DHCP relay sends packets to all servers, even for packets where the client is in a RENEWING state unicasting to attempt to reach a single server. ARP entries are retained for all offered addresses, even if the client is ultimately using a different address. These extra ARP entries persist for several hours.

Conditions: The symptom is observed under the following conditions:

1. When relaying a DHCP packet on an unnumbered interface and the DHCP client is in a renewing state (as determined by the fact that the packets are sent to the DHCP server which allocated the address so that we do not end up giving the client a new address, which would then interrupt the user sessions).

2. When the client is in any other state, or if we do not get a response from the DHCP server, the packets are sent to all helper-addresses.

Workaround: Use Cisco IOS 12.4T images.

Further Problem Description: Only retain an ARP entry for the address that the DHCP client ACKs. Do not retain addresses offered by DHCP servers which the client did not use in the ARP table.

CSCsx67931

Symptoms: The no l2tp tunnel authentication command does not work at LNS.

Conditions: This symptom happens when the VPDN group that is used has a virtual-template x.

Workaround: Configure the no l2tp tunnel authentication command under virtual template.

CSCsx81707

Symptoms: Following error message are seen when the frame-relay fragment <fragment size> command is configured under map-class attached to PVC:

% Fragment size 110 not supported. Supported fragment size are 128, 256 and 512. Rounding current fragment config to 128.

Conditions: This seen in distributed platforms (Cisco 7600) when fragment size configured is not 128, 256, or 512.

Workaround: Configure the fragment size as 128, 256 or 512

CSCsx93845

Symptoms: Memory leak is seen on configuring and unconfiguring "cem-group".

Conditions: Occurs when configuring and unconfiguring 4 "cem-groups" per controller.

Workaround: There is no workaround.

CSCsx95338

Symptoms: Crash occurs when BGP configuration is removed.

Conditions: BGP is checkpointing routes to the redundant RRP when the configuration change occurs. More likely to occur in a scaled setup.

Workaround: Do not enter the no router bgp command.

CSCsy03758

Symptoms: VPN routing/forwarding (VRF) transfer fails.

Conditions: Occurs when ISG is configured on the device.

Workaround: There is no workaround.

CSCsy07555

Cisco IOS devices that are configured for Internet Key Exchange (IKE) protocol and certificate based authentication are vulnerable to a resource exhaustion attack. Successful exploitation of this vulnerability may result in the allocation of all available Phase 1 security associations (SA) and prevent the establishment of new IPsec sessions.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml

CSCsy07953

Symptoms: Any attempt to copy a file from a router to an FTP server will fail. The FTP error is "No such file or directory".

Conditions: This is only a problem with FTP and only when transferring to an FTP server. Transfers from an FTP server work as expected.

Workaround: Use a different file transfer protocol, such as TFTP.

CSCsy15227

Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent webpage.

There are no workarounds that mitigate this vulnerability.

This advisory is posted at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml

CSCsy19659

Symptoms: When using Point-to-Point Tunnelling Protocol (PPTP) with RADIUS Accounting, there may be several "nas-error" and "lost-carrier" listed in accounting as the Acct-Terminate-Cause.

Conditions: The symptom is observed when using Cisco IOS Release 12.4T (Releases 12.4(15)T-12.4(22)T confirmed) and using PPTP with RADIUS Accounting in place.

Workaround: There is no workaround.

CSCsy21885

Symptoms: After SPA reload, the CHOC12-DS0 SPA may be transmitting B1/B2/B3 errors out. Remote side will detect SF BER, B1 TCA, B2 TCA, or B3 TCA alarms, or DS3 or DS1 alarms. The CHOC12-DS0 SPA will have SONET line REI, Path REI or DS3/DS1 RAI alarm.

Conditions: When the SPA boots up during temperature transition, the SPA transmit side could trigger B1/B2/B3 error detected by remote end. In a stable temperature environment, this problem is hard to reproduce. After SPA is booted up, the problem can not be reproduced even if temperature transits.

Workaround: A software workaround was released in Cisco IOS Release 12.2(33)SRD1 to reduce the issue. But in some SPAs, the problem may still happen. When the problem happens, reload the SPA.

CSCsy24878

Symptoms: Bulk sync fails.

Conditions: Occurs when the relay destination command is configured on the device.

Workaround: There is no workaround.

CSCsy26883

Symptoms: VPN routing/forwarding (VRF) traffic may experience packet loss after a supervisor switchover.

Conditions: Occurs on a Cisco 7600 running Cisco IOS Release 12.2(33)SRB2 or Cisco IOS Release 12.2(33)SRC2.

Workaround: Apply an access-list with "permit ip any any" in one of the VRF interfaces, or force another switchover.

CSCsy29534

Symptoms: In rare conditions, when removing address-familly in router RIP configuration just after importing large amount of routes in it, the router may crash on bus error.

Conditions: It was observed in the following context:

1) Supervisor 720 running Cisco IOS Release 12.2(18)SXF7. 2) 66K of routes were imported at that moment from BGP into RIP. 3) The address-family is removed.

Workaround: Wait a few minutes between the moment you create and import the routes in the address-family and the moment you remove it. Typically 3-5 minutes (depending on the number of routes, more delay may be needed).

CSCsy32000

Symptoms: Router crashes when BGP-IPv6 directly connected IBGP neighbors receives route with Link-local Nexthop.

Conditions: BGP sends IPv6 link-local address in following cases:

1) Directly connected eBGP neighbors

2) BGP Ipv6 neighbors connected using Link-local address

In case of this defect, testing device is advertising link-local nexthop for directly connected neighbor using global IPv6 address. Cisco router will never advertise link-Local nexthop.

Workaround: There is no workaround.

CSCsy39667

Symptoms: On a PPP aggregator using dhcp-proxy-client functionality, in a situation where a PPP client session is torn down and then renegotiated within 5 seconds, the DHCP proxy client may send a DHCP RELEASE for the previous DHCP handle after the new DHCP handle (created as a result of new IPCP CONFREQ Address 0.0.0.0) has accepted the same IP address allocation from the offnet DHCP Server. This results in the offnet DHCP server having no record of the lease as it exists on the PPP aggregator which causes future addressing conflicts.

Conditions: The symptom is observed on a Cisco 7200 (NPE-400) and 7200 (NPE-G2) that is running Cisco IOS Release 12.4 T, or 12.2 SB.

Workaround:

1. Automated: Write a script to compare active leases on the PPP aggregator to active leases on DHCP server. If a lease is found to only exist on the PPP aggregator, use clear interface virtual-access to recover.

2. Manual: use the command clear interface virtual-access.

Further Problem Description: This issue occurs because the DHCP client holdtime is static at 5 seconds and there are no IOS hooks to tie PPP LCP session removal and IPAM to suppress stale DHCPRELEASES waiting in queue for HOLDTIME to expire.

CSCsy53076

Symptoms: Copy to "slavedisk:" is failing with the following error:

Error writing slavedisk0:/rsp72043-adventerprisek9_dbg-mz.122-33.0.5.SRD (TF I/O failed in data-in phase)

Conditions: The issue is seen in RPR mode with Cisco IOS Release 12.2SR rsp720 image.

Workaround: Copy the file in SSO mode.

CSCsy54365

Symptoms: In extremely rare conditions, traffic loss might be observed through ws-x6704 modules equipped with DFC (DFC3b & 3bxl, DFC3a)

Conditions: To confirm that traffic loss might be related to this issue use the following command:

remote command module mod# show platform soft earl reset history

where <mod#> is slot number of the module experiencing traffic drops (ingress module)

cat6500#remote command mod 11 sh platform soft earl reset history

Num. of times patch applied : 156

Num. of times patch requested : 156

Time Reason InProgress Data

--------------+------------------------+------------+----------

5d20h Non-Earl Fatal error 0000 1701FFFFFFFFFFFF

5d20h Non-Earl Fatal error 0000 1701FFFFFFFFFFFF

5d20h Non-Earl Fatal error 0000 1700FFFFFFFFFFFF

5d20h Non-Earl Fatal error 0000 1700FFFFFFFFFFFF

For traffic loss to be related to this issue in above output one should see lines similar to above (most important is the last part i.e. 1701FFFFFFFFFFFF and 1700FFFFFFFFFFFF). There should be multiple lines like this and new lines might appear from time to time. Traffic loss would coincide with the appearance of new lines.

Workaround: There is no workaround other than upgrading to a release that has been fixed.

CSCsy58115

Symptoms: In a router running BGP, the BGP process may hold increased amounts of memory over time without freeing any memory. This may also be seen from the output of show proc mem sort and in the output of show ip bgp sum or show ip bgp vpnv4 all sum and looking at the number of BGP attributes which may be increasing over time in relation to the BGP prefixes and paths which may remain roughly the same.

Conditions: Some BGP neighbors are not in established state and exchanging prefixes. The issue is observed on all platforms running the following releases of Cisco IOS:

-12.2(31)SB14

-12.2(33)SB1b

-12.2(33)SB2

-12.2(33.05.14)SRB

-12.2(33.02.09)SRC

-12.2(33)SRC3

-12.4(20)T2

-12.4(22)T1

-12.2(33)SXI or later releases.

Workaround: Remove the configuration lines related to the inactive neighbors (neighbors in Idle or Active states).

CSCsy60498

Symptoms: On RSP720-10GE, VPNSPA always remains in INIT state.

Conditions: Unknown at this time.

Workaround: There is no workaround.

CSCsy60668

Symptoms: On a router in which MPLS Traffic Engineering (TE) is configured, toggling the router-id in the router configuration can cause the router to reload. For example, configuring "router ospf 100 mpls traffic-eng router-id loopback 0" quickly followed by "mpls traffic-eng router-id loopback 1" may trigger this symptom.

Conditions: It is necessary that "mpls traffic-eng tunnel automesh" is running in the OSPF area of the router, although automesh need not be configured on the affected router.

Workaround: There is no workaround.

CSCsy60846

Symptoms: With 2X1GE-V2 SPA on SIP400, when the interface connector changes from SFP to RJ45, the port failed to be up and it could no longer ping its partner.

Conditions: When the media-type of the 2X1GE-V2 interface is chanaged to RJ45 using the media-type rj45 command, the interface goes to down state. This issue is found in Cisco IOS Release 12.2(33)SRB, SRC, and SRD.

Workaround: Reload the router to bring up RJ45 ports.

CSCsy61006

Symptoms: Lawful intercept users are appearing in output from show run.

Conditions: Occurs in Cisco IOS Release 12.2(33)SRC.

Workaround: There is no workaround.

CSCsy62160

Symptoms: VLAN state unable to recover after shutdown by "mac-limit."

Conditions: Applicable for extended VLAN after MAC limit exceeded and action configured to shutdown.

Workaround: There is no workaround.

CSCsy70184

Symptoms: Traceback occur on SPA inside SIP-400.

Conditions: Occurs during online insertion and removal (OIR) of SPA.

Workaround: There is no workaround.

CSCsy73123

Symptoms: Connected route on port-channel sub-interface is not removed when port-channel is down.

Conditions: Happens when using /22 subnet. Does not happen when using /24 subnet.

Workaround: There is no workaround.

CSCsy74334

Symptoms: Sticky-ARP entries are refreshed forever even after the client is removed from the network.

Conditions: This issue is seen after an upgrade from Cisco IOS Release 12.2(33)SRB5 to Release 12.2(33)SRD1.

Workaround: There is no workaround.

CSCsy77191

Symptoms: Native GigE interfaces of a Cisco 7200 NPE-G2 router will not acknowledge reception of pause frames and will not stop its transmission in case of media-type RJ45.

Conditions: The symptom is observed with media-type RJ45 and with SFP with "no neg auto" configured.

Workaround: There is no workaround.

Further Problem Description: There are no issues with SFP with a "neg auto" configuration.

CSCsy77298

Symptoms: Option 82 is not appended in DHCP NAK packet by DHCP server.

Conditions: Not any specific condition.

Workaround: There is no workaround.

CSCsy81519

Symptoms: ISG subnet session feature if used in an environment where subscribers are connected to ISG interface on Layer 2 cloud, that is, ISG is the default gateway for the subscribers yet ISG subscribers interface is in routed mode, then adjacency to these connected subscribers is removed as soon as a subnet session is created and next hop is installed for these subscribers as the logical network id computed using the framed subnet mask received from AAA server as access accept radius attribute.

Conditions: This condition will occur for subnet session feature in scenario where ISG interface is defined under routed mode; however subscribers are connected over layer-2 cloud to this ISG interface, that is, ISG is the default gateway for these subscribers.

Workaround: There is no workaround if the subnet session feature has to be deliberately used in scenario as defined under conditions above. However this problem will not occur if the subscribers are one hop or more away from ISG.

Further Problem Description: ISG subnet session feature is used to group a number of sessions together using IP framed netmask attribute. The ISG subnet session feature can be used if ISG interface is defined under routed mode.

For example IP addresses belonging to a client say 192.168.0.68/24, 192.168.0.69/24, 192.168.0.70/24 and 192.168.0.70/24 can be grouped together under one ISG session if at the time of session creation a IP framed netmask 255.255.255.252 is returned in the access accept message from AAA server. The subscribers are one or more hop away from ISG interface (10.10.10.1/24)

The IP Framed Netmask attribute is used to compute the range of IP addresses to be grouped together under one ISG session. In example above, if a session is initiated firstly by IP address 192.168.0.69/24; then using IP Framed Netmask the computed range of IP addresses to be grouped together will be 192.168.0.68 to 192.168.0.71.

Now in a scenario where ISG interface is defined under routed mode though the subscribers are connected directly over Layer 2 cloud to ISG interface and Subnet Session is required to be used as a feature; then the stated problem under section Symptom above will occur.

Using example above and applying to this problematic scenario - the IP addresses of client 192.168.0.68/24, 192.168.0.69/24, 192.168.0.70/24 and 192.168.0.70/24 have to be grouped together under one ISG session using Subnet Session feature by returning a IP Framed Netmask 255.255.255.252 under Access Accept from AAA server, however the ISG interface (192.168.0.1/24) in this scenario is the default gateway to these Client IP end points.

Now as soon as the session is created and authenticated and Subnet Session feature is installed the next hop for these IP range 192.168.0.68 to 192.168.0.71 computed using IP Framed Netmask value 255.255.255.252 would be 192.168.0.68/30 resulting in traffic destined to all the range of IP addresses grouped under Subnet Session forwarded to 192.168.0.68/30 instead of using ARP to reach the IP end points directly.

CSCsy84862

Symptoms: In a rare event, router may crash in EIGRP code after a peer bounce and route removal.

Conditions: Crash seen during EIGRP route updates.

Workaround: There is no workaround.

CSCsy85171

Symptoms: Switch reports following messages:

CDL2 Read Error: Time out

CDL2 Write Error: Time out

Conditions: Occurs on a Catalyst 6500 switch running Cisco IOS Release 12.2(18)SXF.

Workaround: Re-seat the X2 modules. It is highly recommended to do a complete diagnostic test on all modules.

CSCsy86078

Symptoms: Router crashes with memory corruption.

Conditions: Occurs when BFD is configured on 10GigE interfaces and constant link flaps.

Workaround: There is no workaround.

CSCsy88134

Symptoms: When using an ES-40 10GE linecard, if the MAC layer of the WAN connection goes down, but the optical PCS layer remains up, the ES-40 port will never realize the link is down and will instead always keep the interface Up/Up. 10G ports in the ES+ family of line cards do not take advantage of link fault signalling by peer.

Protocols relying on fast reconvergence, will not be able to take advantage of the 10G link fault signalling.

Conditions: This problem can occur on any 10GE interface on an ES-40 line card when the remote transceiver or repeater keeps the PCS layer up but takes the MAC layer down.

The Link layer detection algorithm for 10G ports in the ES+ does not consider a Remote Fault signalled by the peer end. Thus link will continue to show as Link-Up, even though the remote end MAC has experienced a RX FAULT and did not happen to switch off the laser

Workaround: There is no workaround except to rely on higher layer protocols that send hellos or keepalives to determine when the link goes down and reroute around the failure with those protocols. Line protocol will never go down when the PCS layer is up on an ES-40 line card.

CSCsy88640

Symptoms: A core dump may fail to write, with the following errors seen on the console:

current memory block, bp = 0x4B5400A0,

memorypool type is Exception

data check, ptr = 0x4B5400D0

bp->next(0x00000000) not in any mempool

bp_prev(0x00000000) not in any mempool

writing compressed ftp://10.0.0.1/testuncached_iomem_region.Z

[Failed]

writing compressed ftp://10.0.0.1/testiomem.Z

[Failed]

writing compressed ftp://10.0.0.1/test.Z

[Failed]

%No memory available

Conditions: This is only seen for memory corruption crashes when "exception region-size" is configured to a value that is not divisible by 4.

Workaround: The recommended setting for exception region-size is 262144 in newer images. In older images, where the maximum configurable value is 65536, use the maximum.

CSCsy96407

Symptoms: Downstream traffic stopped after delete/recover of sub-interface configuration while sessions are up.

Conditions: Occurred with the following configuration:

* L2access IP aggregation session

* ISG as DHCP relay

* No VPN routing/forwarding (VRF)

* TAL authentication

Workaround: There is no workaround.

CSCsz00959

Symptoms: Standby router reboots continuously and comes to the prompt only after second or third attempt.

Conditions: When the standby is booting up, during the startup bulk sync, Cat6k QoS Manager client will time out after 30 seconds (depends on load on the box). Due to stress QoS config, during bulk sync, the standby is taking more time, and this triggers active to reset the standby.

Workaround: There is no workaround.

CSCsz01695

Symptoms: STP network will not converge if the vlan dot1q tag native global command is enabled. BPDUs will not get transmitted over Virtual Private LAN Services (VPLS) pseudowire (PW).

Conditions: Occurs in a network with nPE redundancy, where the redundant PEs are connected through VPLS PW.

Workaround: Disable the vlan dot1q tag native command.

CSCsz05181

Symptoms: A router may reload unexpectedly.

Conditions: The symptom is observed when the router has Bidirectional Forwarding Detection (BFD) configured and is actively sending keepalives. The crash has multiple possible triggers:

It can be triggered by certain show commands (show bootvar and show c7200 are known to cause the problem). The issue will not be seen on every invocation of the commands. It is a rare timing condition, so the probability of the crash increases as the commands are run more frequently.

It can also be triggered by large scale BFD deployments (hundreds of sessions on a single router).

Workaround: Unconfigure BFD.

CSCsz07569

Symptoms: The session ID changes between "interim" and "stop" accounting records.

Conditions: The symptom has been observed on Cisco IOS Release 12.2(31)SB12 with "radius-server attribute 44 extend-with-addr" in the configuration.

Workaround: Do not configure "radius-server attribute 44 extend-with-addr".

CSCsz10073

Symptoms: SPA-4XOC3-ATM can stop forwarding ingress traffic after cell packing timer is changed.

Conditions: Occurs when MPLS is configured over a tunnel interface and the cell packing timer is changed.

Workaround: There is no preventive workaround to this issue. Once the card is in the problem state, the FPGA is hung and to recover from this state, the SPA has to be reloaded.

CSCsz11784

Symptoms: DS3 interface on choc3/STM1 stops passing traffic.

Conditions: Occurs when a DS3 is oversubscribed.

Workaround: There is no workaround.

CSCsz14273

Symptoms: A Cisco IOS device may produce CPUHOG error messages and a watchdog timeout unexpected restart when running a Tool Command Language (Tcl) Embedded Event Manager (EEM) policy.

Conditions: This occurs when the EEM policy uses the Tcl puts command to print a very large amount of text.

Workaround: Do not use this command to print out a large amount of text.

CSCsz15931

Symptoms: The entPhysicalVendorType for Transceivers lists the vendortype of Port.

Conditions: Occurs during normal operation.

Workaround: There is no workaround.

CSCsz16723

Symptoms: A Cisco router running Cisco IOS Release 12.2(33)SRC1 may crash when removing the TE tunnel mode on a SIP600 or ES20 card.

Conditions: A tunnel bot uses the following script to remove tunnels:

interface Tunnel37025

no mpls ip

no tunnel mode mpls traffic-eng

exit

no interface Tunnel37025

In the transient time between removal of tunnel mode and removing the tunnel interface, packets are still moving through EARL.

Workaround: Shutdown the tunnel first, then complete the script:

interface Tunnel37025

shutdown

no mpls ip

no tunnel mode mpls traffic-eng

exit

no interface Tunnel37025

CSCsz18711

Symptoms: NAS-port-ID format reported by AAA accounting VS reply to a CoA account-query are different. Affects back-end server for billing functions.

Format send by AAA accounting records:

Apr 16 09:59:16.358: RADIUS: NAS-Port-Id [87] 25 "GigabitEthernet0/1.118:"

Format sent in reply to CoA Query:

Apr 16 10:03:49.149: RADIUS: NAS-Port-Id [87] 33 "nas-port:10.10.10.101:4/0/0/118"

Conditions: This behavior was observed in Cisco IOS Release 12.2(33)SB3.

Workaround: There is no workaround.

CSCsz20271

Symptoms: HQF is not getting cleaned after a policy with priority child class is removed from the "serial-vaccess" MLP interface. Also when removing the policy, an error message is seen:

qos-reg15-r5#config term

Enter configuration commands, one per line. End with CNTL/Z.

qos-reg15-r5(config)# no policy-map customer

please remove queuing feature from child policy first

qos-reg15-r5(config)#end

Conditions: The priority feature cleanup fails and prevents further service policy removal.

Workaround: There is no workaround.

CSCsz21640

Symptoms: A router may crash with BusError when sending an AccountingStop record.

Conditions: Just before the crash, the following error messages are seen:

%IDMNGR-7-ALLOCFAIL: Warning: Failed to allocate memory for keylist in event_init %IDMNGR-7-ALLOCFAIL: Warning: Failed to allocate memory for client request data in request_init

The system is configured for ISG-services.

Workaround: There is no workaround.

Further Problem Description: This was seen in a customer specific special based on Cisco IOS Release 12.2(31)SB13.

CSCsz21857

Symptoms: IPV6 traffic dropped over Virtual Private LAN Services (VPLS) cloud.

Conditions: VPLS core is configured. IPV6 end devices are PCs.

Workaround: When routers are used as end devices instead of PCs, then the issue is not seen

CSCsz27104

Symptoms: Acct-Session-Id attribute received in CoA message is decoded incorrectly.

Conditions: When session ID is less than 8 hex characters, the decoded value is incorrect.

Workaround: There is no workaround.

CSCsz30192

Symptoms: Following error message is seen:

%SIP200_MP-4-PAUSE: Non-master CPU is suspended for too long

Conditions: This is seen when fragmentation is configured under PVC and either that configuration is changed or PVC state changes.

Workaround: There is no workaround.

CSCsz30221

Symptoms: Router crashes.

Conditions: Occurs while unconfiguring class-default.

Workaround: There is no workaround.

CSCsz30839

Symptoms: Switch virtual interface (SVI)-to-SVI Layer 3 ping is failing.

Conditions: Occurs when SVI (VLAN) is configured with IP address on both ends.

Workaround: There is no workaround.

CSCsz37530

Symptoms: Port is shut down, and following error message is displayed:

%SYS-DFC3-2-LINKED: Bad enqueue of 191C92B4 in queue FD9EAD0 -Process= "SCP Hybrid process"

Conditions: Problem is seen with Cisco 7600 running Cisco IOS Release 12.2SRD image with Port-channel configured and the member-link used is a ES+ Linecard interface.

Workaround: There is no workaround.

CSCsz39086

Symptoms: With a subinterface or software Ethernet Over MPLS (EoMPLS) configured for a single tag, QinQ traffic with outer VLAN tag matching the configuration, but with full-range of inner tag is dropped.

Conditions: All QinQ traffic with the outer tag matching the configured tag on subinterface is dropped.

Workaround: Use scalable EoMPLS, which provides a versatile range of VLAN matching and has the required properties as expressed in this defect.

CSCsz40772

Symptoms: Traffic is lost for local forwarding between two EVCs in a VRF.

Conditions: Occurs when VRF includes attachment circuits which are defined as EVCs. Each EVC is configured on separate bridge-domain and separate IP subnet. Forwarding between remote PEs works properly but local traffic between the EVCs breaks.

Workaround: Keep the EVC on different NPs on the ES40 or replace EVC and bridge domain configuration by sub-interfaces.

CSCsz42143

Symptoms: 6148A-GE-TX module resets due to keep-alive failures.

Conditions: Excessive errors and micro link flaps on a port.

Workaround: There is no workaround.

Further Problem Description: This is a rare problem triggered by misbehavior of a 10Base-T hub when a FastEthernet host is connected to it.

CSCsz43691

Symptoms: If TAL subscribers attempt to logon when the Cisco ASR 1000 series router RADIUS service download requests a time-out, some sessions will get stuck in "Attempting" state during user/service authorizations. Once 200 sessions are stuck in this state, no subscriber will be able to login until all the sessions (those that are active and those that are stuck in "Attempting" state) are manually cleared using the clear subscriber session all command.

Conditions: The symptom is observed when TAL subscribers attempt to logon while the Cisco ASR 1000 series router RADIUS service download requests a time-out.

Workaround: Use the clear subscriber session all command to manually clear all sessions. This may be, however, service disruptive and impractical in a production network.

CSCsz45226

Symptoms: Multicast Open Shortest Path First (OSPF) Bidirectional Forwarding Detection (BFD) packets are corrupted when going out of ESM20 interface on an Ethernet Over MPLS (EoMPLS) setup.

Conditions: When sending a multicast OSPF database descriptor (DBD) packets or multicast ping packets to the 224.0.0.5 address and the packet size grows above a certain size (108B) in the payload, a specific byte of multicast packet traversing the EoMPLS link is corrupted.

Workaround: There is no workaround.

CSCsz45509

Symptoms: Dead Peer Detection (DPD) packets are not sent following loss of ISAKMP SA and IPSec in UP-NO-IKE state.

Conditions: Occurs when DPD is configured and ISAKMP SA is deleted independently of IPSec SAs

Workaround: Manually clear the crypto session to create a new ISAKMP SA.

CSCsz45567

A device running Cisco IOS Software, Cisco IOS XE Software, or Cisco IOS XR Software is vulnerable to a remote denial of service condition if it is configured for Multiprotocol Label Switching (MPLS) and has support for Label Distribution Protocol (LDP).

A crafted LDP UDP packet can cause an affected device running Cisco IOS Software or Cisco IOS XE Software to reload. On devices running affected versions of Cisco IOS XR Software, such packets can cause the device to restart the mpls_ldp process.

A system is vulnerable if configured with either LDP or Tag Distribution Protocol (TDP).

Cisco has released free software updates that address this vulnerability.

Workarounds that mitigate this vulnerability are available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20100324-ldp.shtml

CSCsz47517

Symptoms: Policy-map counters are not updated after online insertion and removal (OIR), and shaping is not happening.

Conditions: Occurs after OIR under bi-directional traffic.

Workaround: Remove the service-policy in both affected device and peer and then re-attach to update counters.

CSCsz47619

Symptoms: ES-20 line card repeatedly resets.

Conditions: Occurs when fabric sync failure occurs on ES-20.

Workaround: Enter the following command: test scp linecard keepalive disable.

CSCsz47926

Symptoms: An Error message that includes "IXP-MAP-QOS" is displayed on the supervisor. Occurs when an Ethernet flow point (EFP) interface is recreated or deleted and when online insertion and removal (OIR) is performed on a SPA with an EFP interface on SIP-400.

Conditions: Occurs only when there is a EFP policy on a Gig V2 SPA on SIP-400.

Workaround: There is no workaround. The issue does not impact functionality.

CSCsz50620

Symptoms: Bus error crash at an invalid address.

Conditions: The symptom is observed when running Cisco IOS Release 12.2(31)SB with SSS configured.

Workaround: There is no workaround.

CSCsz52815

Symptoms: If number of hours for statistics is increased to 10 or more after the probe is initially run and then restarted, system crashes with memory corruption

Conditions: Occurs when the probe is started with the hours of statistics less than 10 and then re-started with the hours of statistics greater than 9.

Workaround: There is no workaround.

CSCsz53177

Symptoms: When running Network Load-balancing (IGMP-mode) in VLANs with PIM enabled and static ARP entries for unicast IP to layer-2 multicast address, packet duplication will occur.

Conditions: This symptom occurs when sending unicast (non-multicast) IP packets with multicast layer-2 destinations.

Workaround: Use non-IGMP NLB modes (unicast or multicast with static macs) or use IGMP snooping querier instead of PIM on NLB SVIs.

CSCsz54749

Symptoms: Router crashes.

Conditions: Occurs when configured with BGP damping and default IPv4 unicast address-family is deleted.

Workaround: Do not delete the default IPv4 unicast address-family.

CSCsz56805

Symptoms: Different IPs are seen on the same session between Active and Standby PRE cards and the number of in-use IP addresses on Standby is more than that on the Active.

Conditions: The symptom is observed with the frequent connect/disconnect of sessions and when IP addresses are allocated from the local pool.

Workaround: Reload the Standby card frequently.

CSCsz58461

Symptoms: Configuring no negotiation auto on Gigabit interface of 2xGEv2 SPA reduces duplex on interface to half. This causes traffic drop if traffic is bi-directional.

Conditions: Occurs when "media-type" configured on Giginterface as "SFP".

Workaround: There is no workaround.

CSCsz59914

Symptoms: When the SAMI module is booted up, CEF is disabled by default in the PPCs. If a PPC is configured for ISG, no static IP sessions (L2-connected or L3-routed) can come up. Even after enabling CEF, static IP sessions still do not come up. If the PPC(s) or SAMI gets reloaded after enabling CEF and writing the configurations into memory, sessions will come up.

Conditions: When installing/configuring a new SAMI card for ISG, static IP sessions will not come up if CEF was disabled on bootup.

Workaround: Since the issue happens only when CEF was disabled on bootup, enabling CEF, doing a write memory, and then reloading the PPC will avoid this issue.

CSCsz61156

Symptoms: Routes do not appear in Routing Information Base (RIB) of a VRF.

Conditions: Occurs with the following configuration:

- Customer has IPv6 static route in VRF X.

- Customer has configured BGP to import routes from VRF X into VRF Y.

- BGP is apparently importing the VRF X route into VRF Y as requested

- the routes are not showing up in VRF Y RIB

Workaround: There is no workaround.

CSCsz62046

Symptoms: CPUHOG occurs in SNMP ENGINE, immediately followed by a crash.

%SYS-3-CPUHOG: Task is running for (4000)msecs, more than (2000)msecs (91/87),process = SNMP ENGINE.

Conditions: Querying cc6kxbarModuleChannelTable and cc6kxbarStatisticsTable in CISCO-CAT6K-CROSSBAR-MIB with invalid channel index may trigger this problem. The valid channel index range for the cc6kxbarModuleChannelTable and cc6kxbarStatisticsTable are (0..1)

Regular snmp mibwalk on those 2 tables will not cause this problem.

Workaround: Avoid MIB querying on cc6kxbarModuleChannelTable and cc6kxbarStatisticsTable with any specific invalid channel index. Instead just do regular SNMP MIBwalk on cc6kxbarModuleChannelTable and cc6kxbarStatisticsTable should be safe and work fine.

CSCsz62528

Symptoms: When configuring ATM or ima-group under controller T1/E1, the SNMP MIB does not populate the corresponding ATM interface. Because of this defect, ANA application is unable to model it correctly.

Conditions: Problem exists on Cisco 7600 running Cisco IOS Release 12.2(33)SRC.

Workaround: There is no workaround.

CSCsz62974

Symptoms: Router crashes while querying for cvpdnTemplateActiveSessions.

Conditions: Occurs if the vpdn-template name is long.

Workaround: There is no workaround.

CSCsz63870

Symptoms: On configuring HDLCoMPLS on SPA-8XCHT1/E1 SPA with 7600-SIP-400. traffic stops flowing from that interface.

Conditions: Occurs when Xconnect is configured.

Workaround: There is no workaround.

CSCsz69988

Symptoms: Connectivity Fault Management (CFM) packets are not transparently passed through scalable EoMPLS setup with SIP400 on the access side.

Conditions: This happens when CFM is disabled after enabling it

Workaround: Perform an online insertion and removal (OIR) on the line card.

CSCsz71782

Symptoms: ASR crashes and reboots when RSIM sends VSA 1 command with wrong format.

Conditions: VSA 1 format string has a colon which should not be there.

vsa cisco generic 1 string "qos-policy-out:=remove-class(sub, (class-default, voip))"

Workaround: There is no workaround.

CSCsz72581

Symptoms: Dead Peer Detection (DPD) does not trigger a new IKE session if the previous IKE session fails.

Conditions: Occurs when using on-demand DPD.

Workaround: Manually clear the IKE session to trigger a new IKE.

CSCsz73470

Symptoms: When there are more than 8000 DHCP sessions on a Cisco 7600 ISG, a few dangling sessions are sometimes observed.

Conditions: This symptom occurs when there are more than 8000 DHCP sessions on a Cisco 7600 ISG. ISG is configured as a DHCP relay.

Workaround: Clear the sessions using the clear ip subscriber dangling command.

CSCsz75715

Symptoms: Policy-maps configured with random detect can cause unnecessary packet drops.

Conditions: When an output policy-map is applied on SIP400 on Cisco IOS Release 12.2(33)SRD, and if class-maps are configured with "random detect", drops may occur even if the traffic is lower than the configured bandwidth percentage. If "random detect" is removed, drops is no longer seen. Also, this issue is seen only with low-speed interfaces. In this particular customer case, Gigabit Ethernet interface was configured in FastEthernet mode (speed 100mbps)

Workaround: There is no workaround.

CSCsz76701

Symptoms: Sup720 crashes during ISIS adjacency flapping.

Conditions: When an ISIS adjacency is flapping, issuing the command show isis topology triggered the crash. However, this observed only once in customer network

Workaround: There is no workaround.

CSCsz79094

Symptoms: Router fails on a forced switchover to the standby supervisor card. The standby supervisor card tries to come online but encounters a crash and goes into ROMMon. To recover from this state the router requires a power cycle.

Conditions: Occurs on Cisco 7600s running Cisco IOS Release 12.2(33)SRD2 and SRD2a and using non-Cisco SFPs.

Workaround: Avoid non-Cisco SFPs or use a different release of Cisco IOS.

CSCsz81473

Symptoms: Subscriber upstream traffic stops flowing after an online insertion and removal (OIR) is performed on a line card, or when a pair of shut/no shut commands is entered when IP sessions are brought up on main interface. For ES+ line cards, the problem can be seen even for Port-Channel main interface and all non-access sub-interfaces.

Conditions: This defect is seen only when the main interface fails to get the same hidden VLAN allocated to it prior to line card OIR (or while entering shut/no shut commands).

Workaround: There is no workaround.

CSCsz82587

Symptoms: MPLS-TE configuration leads to router crash due to online insertion and removal (OIR).

Conditions: MPLS-TE sessions coming up/down during OIR may lead to router crash.

Workaround: There is no workaround.

CSCsz82825

Symptoms: When relaying to multiple servers, from an unnumbered interface, the Cisco IOS DHCP relay sends packets to all servers, even for packets where the client in a RENEWING state unicasting to attempt to reach a single server.

ARP entries are retained for all OFFERed addresses, even if the client ultimately is using a different address. These extra ARP entries persist for several hours.

Conditions:

1. When relaying a DHCP packet on an unnumbered interface, and the DHCP client is in a renewing state (as determined by the fact), send it to the DHCP server that allocated the address so that we do not end up giving the client a new address, which would then interrupt the user sessions.

2. When the client is in any other state, or if we do not get a response from the DHCP server, send to all helper-addresses.

Workaround: There is no workaround.

Further Problem Description: Only retain an ARP entry for the address that the DHCP client acknowledges. Do not retain addresses offered by DHCP servers that the client did not use in the ARP table.

CSCsz89319

Symptoms: Free memory is going down because SSS Manager is growing.

Conditions: This symptom is observed on a Cisco 7600 that is used for ISG and that is running Cisco IOS Release 12.2(33)SRC3 under high network activity.

Workaround: There is no workaround. Reload the router to free memory.

Further Problem Description: The speed of the memory leak depends on the network activity. The more stress on the router, the faster the leak.

CSCsz92345

Symptoms: Unit under test crashes under heavy traffic when online insertion and removal (OIR) is performed on a SIP400.

Condition: Occurs with huge Layer 2 and Layer 3 protocol configuration and SIP400.

Workaround: There is no workaround.

CSCsz96323

Symptoms: A Cisco 7301 router crashes with "protocol pptp" configured.

Conditions: The symptom is observed with a Cisco 7301 router when "protocol pptp" is configured.

Workaround: There is no workaround.

CSCsz97011

Symptoms: No Layer 4 Redirect (L4R) traffic is reaching the portal.

Conditions: Occurs if there is a sub-interface on the port facing the portal.

Workaround: There is no workaround.

CSCsz97091

Symptoms: Packet drop occurs when show version, show run, and write memory commands are issued.

Conditions: Packet drop will be observed as input errors accounted as overruns. The rate of packets being dropped will be proportional to the rate of traffic.

Workaround: There is no workaround.

CSCsz99027

Symptoms: Router crashes on applying/removing priority from service map.

Conditions:

1. Configure priority in class default. Apply it on EVC on ES20 line card.

2. Remove priority from class default.

3. Now, either removing or applying priority causes the router to crash.

Workaround: There is no workaround.

CSCta00720

Symptoms: Attempting an auto proxy logon causes a crash.

Conditions: This crash is seen only with auto proxy service download.

Workaround: If services are activated by CoA service logon, this issue will not be seen.

Further Problem Description: Attempting authentication of the proxy service causes a crash with traceback in description when the user profile is similar to:

simulator radius subscriber 1 framed protocol ppp service framed authentication rouble-auto password cisco vsa cisco 250 Aproxy_service;proxy_user;welcome vsa cisco generic 1 string "accounting-list=default" !

CSCta04550

Symptoms: Active supervisor may crash if standby supervisor resets for any reason.

Conditions: This can happen if a interface level event happens around the same time of standby supervisor reload. The timing window is extremely small for the bug to happen.

Workaround: There is no workaround.

CSCta08632

Symptoms: After supervisor forces switchover several times, a router two hops away has wrong ISIS topology and ISIS routing table.

Conditions:

1. Incremental shortest path first (ISPF) enabled in ISIS.

2. set-overload-bit on-startup in ISIS.

3. Supervisor force switchover several times

Workaround: Disable ISPF in ISIS.

CSCta10442

Symptoms: Policy-map not applied at SIP400 in dLFI over ATM case after performing shut/no shut of the interface.

Conditions: Occurs after performing shut/no shut on the interface.

Workaround: Perform an online insertion and removal (OIR) on the SIP400.

CSCta10908

Symptoms: We will see the traffic loss when there is a cut-over in the Spatial Reuse Protocol (SRP) ring.

Conditions: There should be HWEoMPLS configured in the system. Ingress card should be DFC card (not a supervisor card), and core-facing card should be SRP card.

Workaround: Either we use the supervisor card as ingress card, or we need to write to EARL adjacency on the line card using the test mls cef adjacency command.

CSCta15786

Symptoms: Polcy-based routing (PBR) stops working after stateful switchover (SSO). All traffic that should be policy-routed is dropped instead.

Conditions: This usually happen after several switchovers between supervisors. Usually problem occurs after about 10 switchovers, however, it could happen after first one.

Workaround: Remove and add policy on the interface.

CSCta20257

Symptoms: BGP modifies next-hop of the route owned by other protocol in Routing Information Base (RIB).

Conditions: Occurs when other protocol route is best in RIB due to lower admin distance, and BGP trys to add the route to RIB.

Workaround: Enter the clear ip routex.x.x.x command.

CSCta25363

Symptoms: The show mls qos module command is not relevant for ES+ line cards and produces invalid output.

Conditions: Occurs during normal operation.

Workaround: Do not use the show mls qos module for ES+ line cards.

CSCta26029

Symptoms: Path attribute memory leak is found when there is some path attribute churn in the network.

Conditions: The symptom is seen only when there are idle peers on the router.

Workaround: Unconfigure the idle peers.

CSCta26071

Symptoms: A Cisco IOS platform can crash when authorizing Radius profiles. The issue is due to an invalid terminal sync change that updated the incorrect enumeration structure, leading to one enumeration having 1 too many entries and another one too few.

When parsing the "protocol" or "service" field, the AAA code may walk beyond the boundaries of a string array associated with the above mentioned enumerations. This will cause platforms such as the Cisco ASR to crash.

Conditions: This crash has been observed on a Cisco ASR1004 (RP2) that is running the Cisco IOS-XE version Cisco IOS Release 12.2(33)XNC1t.

Workaround: This crash will occur if an invalid protocol or service field is provisioned in a Cisco VSA. However, even when valid protocols or services are used, it is possible that certain enumeration walking code may also trigger a crash. However, Cisco has not been able to validate that situation. As a consequence, when using branches such as Cisco IOS Release 12.2(33)SB or Release 12.2XNC, without this fix, it is critical that no invalid Cisco VSA be used.

CSCta30344

Symptoms: Relay information option is not verified in the downstream DHCP packets.

Conditions: This happens only when option 82 insertion is configured at the interface configuration mode.

Workaround: Configure option 82 in global configuration mode.

CSCta34908

Symptoms: Following error message is displayed:

SPA_EEPROM-3-RPC_FAILED: Failed to send RPC message to read EEPROM of SPA in subslot 7/0 - rpc timeout error after fpd upgrade.

Conditions: This error usually seen following reload of the SPA after FPD upgade of SPA.

Workaround: Perform an online insertion and removal (OIR) of SPA. If that does not work, then reload line card.

CSCta42753

Symptoms: Following reload or reseat of Protect LC in ADM TRuepointR 6400, SPA-2OC3-POS/SIP400/SRD2 reports "Received Alarm: L-AIS" on the PROTECT port of a 1+1 APS group when an inline SONET analyzer attached to same wire reports no L-AIS is present on the wire.

Conditions: L-AIS is recovered by an STE via looking for K2 = 0x07 for 5 consecutive frames.

A Cisco POS interface with "pos ais-shut" will transmit L-AIS when interface is shutdown. Without "pos ais-shut" the interface continues to send valid SONET frames toward the STE/LTE.

Workaround: Remove/reinsert the cable on CPE to clear the alarm.

CSCta43713

Symptoms: Port-channel on interface of ES+, a line card reload causes memory leak on "RPC pagp_switch_sp2mp" and "QM_VLOU_MAP". It loses about 748 bytes per policy-map attached on interface.

Conditions: Occurs on a Cisco 7600 series router with policy-map configured on port channel interface.

Workaround: There is no workaround.

CSCta46650

Symptoms: The console gets stuck when the show arp command is executed and "esc" is pressed to stop viewing the whole output.

Conditions: The symptom is observed with 512 ARP sessions on the system and set term len equal to 20.

Workaround: There is no workaround.

CSCta46653

Symptoms: In ES+ line cards with link daughter card versions less than .200, there is a possibility of the line card crash when an SFP module is removed and inserted.

Conditions: Occurs under normal operating conditions.

Workaround: There is no workaround.

CSCta58194

Symptoms: Router crashes with max-entries of NAT translations limit imposed.

Conditions: With ip nat max-entries limit <> configured and greater than limit number of flows passed through the NAT router, crash is seen when the above limit configuration is removed and a large amount of translations are created.

Workaround: There is no workaround.

CSCta61663

Symptoms: Cisco 7600 SPA-1XCHSTM1/OC3 SPA does not use the configuredn etwork-clock source as the reference for the T1/E1.

Conditions: The SPA-1XCHSTM1/OC3 SPA is configured to use the internal clock for timing of the T1/E1. The network-clock is configured on the Cisco 7600 to use the reference from an ATM OC3 interface.

Workaround: There is no workaround.

CSCta65610

Symptoms: When configuring an OSPF sham-link between two PEs also used for multicast VPN, RPF check for the source of a multicast stream points to the physical interface used by the sham-link instead of the tunnel.

Conditions: Configure two PEs to run MVPN and create a sham-link between them. Remote routes that are learned through the sham link will not have an MDT tunnel.

Workaround: There is no workaround. Prefixes must be learned through i-BGP.

CSCta68856

Symptoms: Policy map with multiple MAC ACL filters matches only the traffic with the first MAC ACE in the ACL.

Conditions: Occurs on a Cisco 7600 series router with ES+ linecard, and with policy map with MAC ACL configured on ES+ linecard interface.

Workaround: There is no workaround.

CSCta69232

Symptoms: Resilient Ethernet Protocol (REP) will not converge if REP is configured over switchport and vlan dot1q tag native is enabled.

Conditions: In this case, the REP PDUs will be sent as tagged packets.

Workaround: There is no workaround.

CSCta77105

Symptoms: Hierarchical service policy is not attached to multilink on SIP-200

Conditions: When the hierarchical service-policy is applied on the interface on sip1 or sip2, it is rejected.

Workaround: There is no workaround.

CSCta77747

Symptoms: If a ES+ port is configured as switchport trunk and the Cisco 7600 is supposed to route the traffic between the vlans carried in the trunk, routing is not happening.

Conditions: Occurs when ES+ ports are configured as switchports, such as follows:

interface GigabitEthernet2/2

switchport

switchport trunk allowed vlan 666,777

switchport mode trunk

Workaround: Use EVC instead of switchport, such as follows:

interface GigabitEthernet2/2

no switch

service instance 10 ethernet

encapsulation dot1q 666

rewrite ingress tag pop 1 symmetric

bridge-domain 666

!

service instance 20 ethernet

encapsulation dot1q 777

rewrite ingress tag pop 1 symmetric

bridge-domain 777

CSCta78252

Symptoms: If the link flaps on a multilink bundle, or if the CE router is hard reset, when the bundle comes back up, it will not pass traffic until all but one of the interfaces of the bundle are removed.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRD2.

Workaround: There is no workaround.

CSCta79634

Symptoms: System crash in L2TP. Following this, most of the L2TP setups fail.

Conditions: The symptom occurs at an L2TP control-plane event.

Workaround: Clear VPDN again or reload the router.

CSCta89002

Symptoms: Following error message is displayed:

EARL_L2_ASIC-SP-4-L2L3_SEQ_ERR, EARL L2 ASIC #0: L2L3 Mismatch seq #0x507 and %CPU_INTF_FPGA-5-PAUSE_FAIL

After this message, router crashes.

Conditions: Occurs when sending large a amount of IPv4 packets towards FlexWAN2 with bad version in short span, such as >1000pkts at line rate.

Workaround: There is no workaround.

CSCta91367

Symptoms: Bus error crash on SIP-600 SPA-10X1GE-V2.

Conditions: Crash is specific to SIP-600 when a applying QinQ configuration to the sub-interface of a GE.

Example:

interface GigabitEthernet1/0/0.1

encapsulation dot1Q XXX second-dot1Q XXX

Thus far, this has been seen on Cisco IOS versions based on 12.2(33)SRB and 12.2(33)SRD.

Workaround: Have verified that the SIP-400 with SPA-2X1GE and 7600-ES20-GE3CXL support QinQ with Cisco IOS Release 12.2(33)SRB3.

CSCta99162

Symptoms: When the command passive-interface default is entered under router ISIS, the router reloads.

Conditions: Enter router ISIS configuration mode and enter the passive-interface default command. Router reloads.

Workaround: Configure a passive interface under router ISIS.

CSCtb05885

Symptoms: CEM circuit on Cisco 7600 CEoP SPA does not forward AIS alarm towards attachment circuit even though it is in "TDM Fault" condition as indicated by the output of show cem circuit detail. It also incorrectly shows the CEM circuit as being in "Packet loss" state.

Conditions: This happens only when CEM circuit is in "TDM Fault" condition.

Workaround: There is no workaround.

CSCtb08593

Symptoms: ES40 crashes continuously and powers down.

Conditions: Occurs when configuring default native VLAN on a subinterface with dot1q encapsulation.

Workaround: Remove the dot1q encapsulation configuration.

CSCtb22873

Symptoms: If show mpls forwarding with ownerowner command is issued in cases where none of the entries in a very large forwarding table match the specified owner, a CPUHOG error and traceback may occur.

Conditions: This problem would only occur in cases where a configuration generating a very large MPLS forwarding table existed.

Workaround: Do not issue this command for an owner that did not create any labels.

CSCtb33667

Symptoms: Serial interface in CH0C3 SPA in mode CT3 does not come up. SONET controller and the T3 controller are up, but T1 controller that is configured under T3 is down with LOF alarm.

Conditions: Occurs when configuring STS-1 in CT3 or CT3-E1 mode.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2a

Cisco IOS Release 12.2(33)SRD2a is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD2a but may be open in previous Cisco IOS releases.

CSCsv79583

Symptoms: When coarse wavelength division multiplexing (CWDM) small form-factor pluggable (SFP) module of any wave length is inserted in the GE port or OC48 port, the SFP module is disabled and the following message is displayed:

%TRANSCEIVER-3-NOT_COMPATIBLE: SIP0/0: Detected for transceiver module in 
GigabitEthernet0/0/0, module disabled 

The output of the show status command shows the following:

CE1#show hw-module subslot 3/3 transceiver 1 status 
The transceiver in slot 3 subslot 3 port 1 has been disabled because: the transceiver 
type is not compatible with the SPA.

Conditions: This issue is seen with a new version of CWDM SFP in which the EEPROM programming has been changed. All releases prior to Cisco IOS Release 12.2(33)SRE and 12.2(33)SRD3 are incompatible with the new SFP version. For the Cisco ASR 1000, all software releases prior to 12.2(33)XNC release 3 and release 4 are affected.

Workaround: Issue is not seen with the older version of SFP.

CSCta46653

Symptoms: In ES+ line cards with link daughter card versions less than .200, there is a possibility of the line card crash when an SFP module is removed and inserted.

Conditions: Occurs under normal operating conditions.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD2

Cisco IOS Release 12.2(33)SRD2 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD2 but may be open in previous Cisco IOS releases.

CSCdy26008

Symptoms: The negotiated IP address is not cleared from an asynchronous interface when a call ends, even though the IP address is returned properly to the IP peer pool.

Conditions: This symptom is observed when the peer is configured to dial in to the network access server (NAS) and to obtain an IP address through IP Control Protocol (IPCP) negotiations with the NAS. The NAS is configured with pools of IP addresses to be allocated to the peer when the peers generate a PPP call to the NAS. The NAS is also configured to authenticate the peer through RADIUS.

Workaround: There is no workaround.

CSCec72958

Symptoms: A Cisco router that is configured for Network Address Translation (NAT) may reload unexpectedly because of a software condition.

Conditions: This symptom can occur when the router translates a Lightweight Directory Access Protocol (LDAP) packet. NAT translates the embedded address inside the LDAP packet. This problem is strictly tied to NAT and LDAP only.

Workaround: There is no workaround.

CSCec85585

Symptoms: Some virtual circuit (VC) information is missing in the Simple Network Management Protocol (SNMP) MIB object cAal5VccEntry from the output of the snmpwalk router configuration command. The ATM VCs 0/100, 0/200 and 0/500 exist on the router but are missing in the MIB.

Conditions: This symptom is observed on a Cisco 7513 router that is running a special image of Cisco IOS Release 12.2(15)T5. The symptom may also occur in other releases.

Workaround: Enter the show atm vc privileged EXEC command on the same device to obtain a complete list of all the VCs.

CSCeg80842

Symptoms: The output of serial interfaces on a PA-MC-8TE1 may become stuck after several days of proper operation.

Conditions: This symptom is observed on a Cisco 7206VXR that runs Cisco IOS Release 12.3(10a) and that has MLP configured on the serial interfaces of the PA-MC-8TE1.

Temporary Workaround: Perform an OIR of the PA-MC-8TE1 or reload the router until the symptom occurs again.

Further Problem Description: The symptom occurs during normal operation of the router. If many errors occur on the link, the symptom is more likely to occur.

CSCeh75136

Symptoms: If a user fails to successfully establish a SSH connection on the first attempt, subsequent attempts may also fail.

Conditions: Occurs when a Cisco router is configured to authenticate SSH connections using TACACS+. The rem_addr field in the TACACS+ header may be empty if the user does not successfully authenticate on the first attempt. This may cause authentication or authorization failures if rem_addr information is required by the TACACS+ server.

Workaround: Configure ipssh authentication-retries 0.

CSCek75694

Symptoms: A router running Cisco IOS 12.4T may reload unexpectedly

Conditions: Occurs when BFD is configured and active.

Workaround: Disable the BFD feature.

CSCin01217

Symptoms: A router may not allow the peak cell rate value on an interface that is bundled with more than one ATM T1 interface or more than one ATM E1 interface to be set to a value that is more than the bandwidth of one T1 ATM interface or one E1 ATM interface.

Conditions: Occurs on Cisco 3600 routers Cisco IOS Release 12.2(6.8)T2

Workaround: There is no workaround.

CSCin91677

Symptoms: The Unavailable Seconds (UAS) that are displayed in the output of the show controllers serial slot/port command are incorrect. The display of the UAS starts only after 20 contiguous severely errored seconds (SES) instead of after 10 contiguous SES.

Conditions: This symptom is observed on a Cisco 7200 series that is configured with a PA-T3+ port adapter.

Workaround: There is no workaround.

CSCsb61514

Symptoms: Packets larger than 1526 bytes get dropped between supervisor and Cisco Multi-Processor WAN Application Module (MWAM) on a Cisco 7600.

Conditions: Drops were seen even after increasing MTU size.

Workaround: Reduce MTU on tunnel end systems, which increases fragmentation.

Further Problem Description: The problem is reproducible with extended pings of size 1527 bytes, which get dropped in direction SUP->MWAM as diagnosed with deb ip icmp.

CSCsb98906

Symptoms: A memory leak may occur in the "BGP Router" process.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0(26)S6, that is configured for BGP, and that has the bgp regexp deterministic command enabled.

Workaround: Disable the bgp regexp deterministic command.

CSCsc78999

Symptoms: An Address Error exception occurs after Uninitialized timer in TPLUS process.

Conditions: This is a platform independent (AAA) issue. It may be seen with a large number of sessions while accounting is configured with a T+ server.

Workaround: Disable accounting, or use RADIUS accounting instead of a T+ server.

CSCse29570

Symptoms: Router might unexpectedly reload during CNS configuration download.

Conditions: The downloaded configuration must disable the CNS configuration initial or partial for this crash to occur.

Workaround: Use static configuration and prevent configuration download from CNS server.

CSCse87210

Symptoms: On Catalyst 6500 Series and Cisco 7600 Series, when certain service modules transmit packets to VLANs also used with Distributed EtherChannel (DEC), those packets may be dropped and lost. For further description, please review "Field Notice: FN-61935 - Catalyst 6500 Series and 7600 Series Service Module Incompatibility With Distributed EtherChannel and Packet Re-Circulation."

Conditions: The problem only happens when service cards are operating in crossbar-enabled mode.

Workaround: See the above referenced Field Note for several workarounds.

CSCse97209

Symptoms: Standard communities are not set correctly by an outbound route-map.

Conditions: Occurs when route-map uses continue option.

Workaround: There is no workaround.

CSCsf25157

Symptoms: An IPv6 ping may fail when the atm route-bridged ipv6 command is enabled.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS interim Release 12.3(22.13), interim Release 12.4(13.9), or Release 12.4(13b) and that is configured for QoS.

Workaround: There is no workaround.

CSCsg11616

Symptoms: While restarting the iprouting process, the system crashed at redzone corruption.

Conditions: Occurs following a switchover. The iprouting process should restart once the standby becomes active.

Workaround: There is no workaround.

CSCsg39754

Symptoms: When DHCP snooping is configured on a VLAN, the redirect access list programmed in TCAM permits a wide range of UDP ports from bootps/bootpc to 65xxx.

Conditions: UDP traffic to these destination ports (0x143, 0x243, 0xFF43) is being redirected to Route Processor (RP). If "ip dhcp snooping limit" is not configured, then RP CPU goes to 100%.

Workaround: There is no workaround.

CSCsh48947

Symptoms: Some of the 48 power over Ethernet ports of a line card cannot be configured as "power inline static" with the maximum power capacity, 15.4 watts, that a port can support.

Conditions: The number of supported ports depends on the power rating of the voice daughter board. One or more ports may not operate at maximum capacity.

Workaround: There is no workaround.

CSCsi88974

Symptoms: While configuring a mediation device (MD), if the MediationSrcInterface is set to loopback interface, traffic will cause MALLOC failures.

Conditions: Problem is seen when traffic rate is equal to or greater than 8000 packets per second.

Workaround: Do not use loopback0 as MD source interface.

CSCsj34557

Symptoms: Router displays following error message and reloads:

Jun 18 06:12:23.008: event flooding: code 10 arg0 0 arg1 0 arg2 0

%SYS-3-OVERRUN: Block overrun at E5D8310 (red zone 00000000) -Traceback= 0x6080CEB0 
0x60982108 0x60982EC0 0x6098511C 0x609853BC %SYS-6-MTRACE: mallocfree: addr, pc 
662B5B1C,608A6F3C 0,608A6D9C 662B5B1C,608A6D4C 662B5B1C,300001A6 662B5B1C,608A6F3C 
0,608A6D9C 662B5B1C,608A6D4C 662B5B1C,300001A6 %SYS-6-MTRACE: mallocfree: addr, pc 
662B5B1C,608A6F3C 0,608A6D9C 662B5B1C,608A6D4C 662B5B1C,300001A6 662B5B1C,608A6F3C 
0,608A6D9C 662B5B1C,608A6D4C 662B5B1C,300001A6 %SYS-6-BLKINFO: Corrupted redzone blk 
E5D8310, words 6088, alloc 61FE2638, InUse, dealloc 80000000, rfcnt 1 -Traceback= 
0x6080CEB0 0x609681D4 0x6098211C 0x60982EC0 0x6098511C 0x609853BC %SYS-6-MEMDUMP: 
0xE5D8310: 0xAB1234CD 0xFFFE0000 0x0 0x63894208 %SYS-6-MEMDUMP: 0xE5D8320: 0x61FE2638 
0xE5DB2D0 0xE5D8144 0x800017C8 %SYS-6-MEMDUMP: 0xE5D8330: 0x1 0x0 0x1 0x64B53478

%Software-forced reload

Conditions: Occurred on a Cisco 7200 running the c7200-ik9s-mz.124-7a.bin image.

Workaround: There is no workaround.

CSCsj78403

Symptoms: A router may crash when the clear ip bgp command is entered.

Conditions: Occurs on devices running BGP and configured as a route reflector client with conditional route injection configured.

Workaround: Unconfigure conditional route injection.

CSCsk04318

Symptoms: Under the BGP router configuration mode, removing an address-family configuration and then immediately reapplying the same configuration may cause the standby RP of a dual-RP router to reload unexpectedly. Typically, the following configuration sync error will be reported:

Config Sync: Line-by-Line sync verifying failure on command: address-family ipv4 vrf NAME due to parser return error

Removing and replacing the RD configuration under a VRF may also trigger the same type of sync error behavior, although the command listed as failing line-by-line sync will be different.

Conditions: Removal of a BGP address-family configuration triggers background cleanup processing that occurs asynchronously after the command is entered by the user. The background cleanup runs on both the active RP and the standby RP, although the cleanup may happen at different times on the active and standby. Because such background processing does not usually run in lockstep on the two RPs, a window exists after entering an address-family deconfiguration command where the active RP and standby RP are not in the same state. If the user tries to reconfigure the address-family command before both RPs have completed processing and are again in the same state, line-by-line sync may fail and cause the standby RP to reload.

Workaround: The line-by-line sync error can be avoided by allowing adequate time for the standby RP to complete background processing and arrive in an identical state as the active RP. If configuration commands are applied when both RPs are in a consistent state, the configuration sync error will not occur and the standby RP will not reload. The background processing normally happens at 60-second intervals, so waiting 2 minutes between deconfig/reconfig attempts for the same command should prevent the issue in all cases.

The line-by-line sync error and standby RP reload should not cause any service impact, as only the standby RP is affected. The active RP remains fully functional and continues traffic forwarding as usual while the standby RP reloads.

CSCsk49705

Symptoms: The ip nat inside source static network command does not have the <cr> option.

Conditions: This symptom is observed on a Cisco 7200 router that is loaded with Cisco IOS Release 12.4 or 12.4T.

Workaround: There is no workaround.

CSCsk94179

Symptom: Connectivity problems are observed for IPv6 client, which obtained IPv6 prefix via DHCP for Virtual Access interface, due to incorrect static routes in the routing table for the assigned IPv6 prefix.

Conditions: Occurs with IPv6 prefix delegation via DHCP, when client moves from one interface to another.

Workaround: None

Further problem description: When IPv6 prefix delegation assigns a prefix for Virtual Access interface, it creates a static route for the prefix in the routing table. When a client moves to a new interface, old binding and the old routes are retained, which causes the problem.

CSCsl00472

Symptoms: A Cisco router unexpectedly reloads with memory corruption after showing multiple "%SYS-2-INPUT_GETBUF: Bad getbuffer" messages

Conditions: Occurs during normal operation.

Workaround: There is no workaround.

CSCsl04687

Symptoms: "Total packets L3 Switched" counter does not include multicast packet count.

Conditions: Occurs always. "Total packets L3 Switched", includes packet switched by FIB, NetFlow and ACL only.

Workaround: There is no workaround.

CSCsl32142

Symptoms: A router may reload after reporting SYS-3-OVERRUN or SYS-3-BADBLOCK error messages. SYS-2-GETBUF with "Bad getbuffer" error may also be reported.

Condition: Occurs when PIM auto-RP is configured and IP multicast boundary is enabled with the filter-autorp option.

Workaround: Configure IP multicast boundary without the filter-autorp option.

CSCsl68327

Symptoms: Packets may be lost during rekey.

Conditions: Occurs because IPSec transit packets may trigger invalid SPI.

Workaround: There is no workaround.

CSCsl71704

Symptoms: A receive access control list (rACL) with large ACL is not applied on interface if is QoS configured.

Conditions: Occurs when rACL with large ACL is applied on an interface. It consumes over 60% of ternary content addressable memory (TCAM) space. If the rACL is applied a second interface with QoS, the configuration fails without displaying an error message.

Workaround: There is no workaround.

CSCsm28287

Symptoms: After shutting down a GRE tunnel interface, the active RP crashed and switchover took place. The following error message was displayed:

%ALIGN-1-FATAL: Illegal access to a low address 13:02:45 UTC Fri Jan 18 2008 addr=0xD, 
pc=0x7144A5A0, ra=0x7209FFF8, sp=0x5ABEE90 SLOT0:01:40:03: %DUMPER-3-PROCINFO: pid = 
16409: (sbin/ios-base), terminated due to signal SIGBUS, Bus error (Invalid address 
alignment) SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: zero at v0 v1 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: R0 00000000 7A5FD854 EF4321F9 
7A6452D0 SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: a0 a1 a2 a3 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R4 EF4321CD 0000000B 0000000B 00000000 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: t0 t1 t2 t3 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R8 7CB96E10 00FDDBE0 00000000 EFFFFFFF 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: t4 t5 t6 t7 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R12 00000000 F7E8E12F 00000000 00000000 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: s0

Conditions: Occurred on a Cisco 7200 running an internal build of Cisco IOS Release 12.2SX.

Workaround: There is no workaround.

CSCsm47417

Symptoms: W2:setting ceExtSysBootImageList cause write memory to work incorrectly.

Conditions: Occurs after setting ceExtSysBootImageList to a new boot image from SNMP. The new boot image in running-config is not copied to startup-config. Instead, a variable "d" will be copied to startup-config after the write memory. The show bootvar command will show BOOT variable = d.

Example: bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:3> 
bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:3>getmany -v2c 
10.64.68.138 public ceExtSysBootImageList ceExtSysBootImageList.2001 = 
disk1:s72033-adventerprisek9_dbg-vzsm47417test ceExtSysBootImageList.2017 = 
disk1:s72033-adventerprisek9_dbg-vzsm47417test 
bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:4>setany -v2c 
10.64.68.138 public ceExtSysBootImageList.2001 -o "disk1:" ceExtSysBootImageList.2001 
= disk1: ------------------------------------------------ 7600-11-1# 00:02:56: 
%SYS-5-CONFIG_I: Configured from 10.64.71.240 by snmp

Workaround: There is no workaround.

CSCsm53196

Symptoms: Crash occurs at "ip_route_delete_common".

Conditions: Occurs under the following scenario:

1)A multicast BGP route exists.

2)A unicast BGP route exists for the same prefix.

3)Another route covered by the same majornet as the BGP route exists.

4)There are both iBGP and eBGP sources for the BGP prefix.

5)Redistribution of BGP routes into an IGP must be configured.

Topology change in network causes mBGP to switch from using the iBGP sourced route to the eBGP sourced route will cause the crash.

Workaround: If there are not both iBGP and eBGP sources for the same route the problem will not occur. If redistribution of BGP Into an IGP is not configured the problem will not occur.

CSCsm55817

Symptoms: When configuring ATM PVCs, under the PVC syntax you can provide a handle to describe the PVC. If this handle starts with "00" (zero zero) then the command will fail.

Conditions: The symptom is observed when configuring ATM PVCs and where the PVC handle starts with "00".

Workaround: Do not use handles that start with "00".

CSCsm64307

Symptoms: When PPP sessions are terminated, the standby NPE may crash. This is true for both PPP sessions that are terminated naturally (from the customer end), and those that are terminated prematurely (at the provider end due to a command such as clear pppoe sessions all).

Conditions: At present the conditions are unknown. It only appears to impact 12.2(31)SB10 and related releases.

Workaround: There is no workaround.

CSCsm71537

Symptoms: The router crashes when Independent Optimized Edge Routing (OER) is configured.

Conditions: Occurs when OER is configured.

Workaround: There is no workaround.

CSCsm86832

Symptoms: The line protocol of the serial interface keeps flapping.

Conditions: This symptom is observed after the Atlas BERT pattern is run on a fractional T1 (1 or 2 timeslots).

Workaround: Add/Remove the T1.

CSCso00864

Symptoms: System running in crypto engine mode vrf with SVI interfaces that have crypto map attached and is in SSO redundancy mode may experience crash of the standby supervisor when the interface referenced by crypto map local address is modified.

Conditions: The system is in SSO redundancy mode, has SVI interfaces with crypto map configuration and running in "VRF mode".

Workaround: There is no workaround.

CSCso29361

Symptoms: The commands given in the interface range command may not be synced to all interfaces configured in the range in the standby supervisor.

Conditions: Occurs when configuration commands are entered under interface vlan range command. They get attached to only the first VLAN in the range in the redundant supervisor. After switchover, traffic does not flow due to the missing VLAN configuration.

Workaround: There is no workaround.

CSCso42170

Symptoms: CPUHOG and traceback messages seen for IP NAT ager process.

Conditions: Occurs when NAT is configured with dynamic translations greater than 27,000, and the NAT pool is exhausted. The following messages are seen:

05:13:43: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs 
(19/13),process = IP NAT Ager. -Traceback= 40BA0994 40BA0F00 40B983A8 40B9852C 
413C2B08 413C2AF4

Workaround: There is no workaround.

CSCso56038

Symptoms: The following error message may be seen:

%DUAL-3-INTERNAL: eigrp 4: Internal Error

Conditions: This symptom is seen when a PE-CE setup using site-of-origin (SoO) tags, in which an PE router that is running EIGRP can learn the same route both by EIGRP (from a CE neighbor) and also by redistribution.

The above error may be seen when EIGRP on the PE prepares to send information to a neighbor about a route learned from another neighbor (with no SoO tag), but before the information can be sent, the route is replaced by a redistributed route (with an SoO tag). The above error can be seen. This behavior is very dependent on the timing of this series of events.

Workaround: There is no workaround.

Further Problem Description: It is not clear what functional impact this may have, or whether the error message is purely a warning.

CSCso57020

Symptoms: Etherchannel states for Link Aggregate Control Protocol (LACP) port-channels are inconsistent between active and standby, which could possibly affect traffic forwarding.

Conditions: Occurs while configuring several LACP port channels. This could be seen if LACP port channels are configured and the device is brought up in SSO mode.

Workaround: Once the standby is completely up in HOT state, perform a shut/no shut on the interfaces that are inconsistent.

CSCso65266

Symptoms: A customer upgraded to Cisco IOS Release 12.0(32)Sy4, and now the customer is seeing a memory leak in the BGP process. The memory leak is happening with the BGP router process at the rcach chunk memory when the route map has a "continue" clause in the configuration.

Conditions: The leak is seen when a "continue" statement is configured in a inbound/outbound route map.

Workaround: There is no workaround.

CSCso74922

Symptoms: Resilient Ethernet Protocol (REP) state flaps after line card reset

Conditions: Occurs on routers running Cisco IOS Release 12.2(33)SRD with SIP600 ports configured as REP edge ports.

Workaround: There is no workaround.

CSCso84567

Symptoms: Non-TCP traffic passing through the device is punted to the control plane policer. When Control Plane Policing (CoPP) is configured, the bridge result is changing to policy route because WCCP is being applied to all IP packets of a WCCP service.

Conditions: Both WCCP and CoPP must be enabled for this issue to occur.

Workaround: There is no workaround.

CSCso88138

Symptoms: When there is a link flap or a reload, RSVP shows that the interface is down while actually the interface is up. Because of this, the tunnel may take a backup path even when the interface is up.

Conditions: Unknown at this time.

Workaround: Perform a shut/no shut on the interface.

CSCso90058

Symptoms: MSFC crashes with Red Zone memory corruption.

Conditions: This problem is seen when processing an Auto-RP packet and NAT is enabled.

Workaround: There is no workaround.

CSCso90970

Symptoms: The no ip proxy-arp command that is configured under ISG enabled interface is not working.

Conditions: This symptom is observed on the ethernet interface, where an ip subscriber command is configured. Same interface allows disabling IP Proxy ARP with the no ip proxy-arp command, but the command is ignored.

Workaround: There is no workaround.

CSCsq04355

Symptoms: Customer mistakenly modified the service module SPAN session which caused high CPU on the switch. This caused the interface to flap, bringing down Hot Standby Routing Protocol (HSRP), Open Shortest Path First (OSPF) and other protocols resulting in an outage.

Conditions: Occurs when manipulating the service module SPAN session

LAB1(config)#monitor sess 1 source vl 2028
% Session 1 used by service module
LAB1(config)#no monitor sess servicemodule
LAB1(config)#do sh mon

Session 2

---------

Type : Local Session
Source Ports :
Both : Gi2/2
Destination Ports : Gi3/2
LAB1(config)#monitor sess 1 source vl 2028
LAB1(config)#do sh mon

Session 1

---------
Type : Local Session
Source VLANs :
Both : 2028
Session 2
---------
Type : Local Session
Source Ports :
Both : Gi2/2
Destination Ports : Gi3/2

Workaround: Do not modify or change the SPAN session related to the service module using the session number. Instead use no mon session servicemodule in order to remove the session.

CSCsq06208

Symptoms: When health monitoring (HM) diagnostic failure happens, call-home diagnostic messages are not out before platform action is taken.

Conditions: Call-home is subscribed to diagnostic alert group minor or major error and the gold policy is active. It only happens when the HM diagnostic test interval is small enough.

Workaround: Set the HM diagnostic test interval to be large enough, but there is no guarantee it will work in all test cases.

Further Problem Description: Because gold policy is last policy in EEM queue, it waits for call-home messages to send out before it executes. If gold policy continues to trigger on the next test failure after reaching the threshold when action notify flag is already false, it does not need to wait for call-home message to execute. It could crash the system before the call-home message for the last gold policy finishes.

Adding ACTION_NOTIFY TRUE condition to the gold policy will prevent the gold policy to continuously execute and consistent with call-home message triggering condition.

CSCsq14261

Symptoms: Downstream traffic will drop when we send IPv6 traffic over PPPoE sessions.

Conditions: Bring up a PPPoE session over L2TP tunnel for address negotiated by IPv6, then send downstream IPv6 traffic.

Workaround: There is no workaround.

CSCsq14311

Symptoms: Router crashed while clearing NAT translations.

Conditions: Occurred on a Cisco 7200.

Workaround: There is no workaround.

CSCsq37953

Symptoms: Junk value is seen in stand-by router.

Conditions: Junk value is observed in stand-by router when normal ATM PVC is created. After switch-over, junk value is seen in both active and stand-by routers.

Workaround: There is no workaround.

CSCsq39079

Symptoms: During periods of high IKE initial session establishment the, SPA may crash.

Conditions: Occurs with high number of simultaneous IKE sessions being established.

Workaround: There is no workaround.

CSCsq42885

Symptoms: Line card crashes recurrently with the "Address exception error".

Conditions: The issue is seen when entering the no shutdown command on the spatial reuse protocol (SRP) interface.

Workaround: There is no workaround.

CSCsq51378

Symptoms: ATM PA Interface with no cables connected shows up/up after forced redundancy.

Conditions: Occurred under the following scenario:

- No cables attached to Fast Ethernet or ATM interface.

- Issue no shut on interface.

- The show ip int brief command shows interface status up/protocol down.

- After redundancy force command is entered, interface shows up/up (no cables connected).

This affects Fast Ethernet interfaces and ATM interfaces on WS-x6582-2PA/PA-2FE-TX and PA-A3-OC3-MM. It does not affect Supervisor ports or Serial Interfaces.

Workaround: There is no workaround.

CSCsq53542

Symptoms: After stateful switchover (SSO) there may be loss of multicast packet delivery for 10 or more seconds.

Conditions: Occurs when multicast routing is enabled in the default mode.

Workaround: If there are no mStatic or mBGP routes, the following configuration will avoid the problem:

Router(config)#ip multicast rpf multitopology Router(config)#global-address-family 
ipv4 multicast Router(config-af)#topology base Router(config-af-topology)#use unicast 
base Router(config-af-topology)# 

CSCsq55691

Symptoms: QoS with Link Fragmentation and Interleaving (LFI) over ATM does not work.

Conditions: Occurs after a shut/no-shut on the ATM interface

Workaround: Reload the line card on both ends.

CSCsq60016

Symptoms: A router crashes after a long RSA key string is entered.

Conditions: This symptom is observed when a very long hex string is entered.

Workaround: Break the entry into shorter strings.

CSCsq77282

Symptoms: Creating a sub-interface may occasionally cause a traceback

Conditions: This may happen when configuring an ATM or SONET sub-interface.

Workaround: There is no workaround.

CSCsq77571

Symptoms: Router (SP) crash may happen upon deleting multiple VRFs or unconfiguring multiple MDTs.

Conditions: The crash is seen when trying to delete multiple MDTs at one time.

Workaround: Allow at least seconds after each MDT delete command or VRF delete command before issuing the next command.

CSCsr05746

Symptoms: ESM20 line card may crash while booting up.

Conditions: Occurs intermittently with a scaled topology.

Workaround: There is no workaround.

CSCsr09062

Symptoms: Cisco 7200 crashes due to memory corruption.

Conditions: Occurs when MLP+QoS is configured on a Cisco 7200 router. QoS policy is having bandwidth, change the BW parameter and flap the multilink using clear int multilink1 to see the crash.

Workaround: There is no workaround.

CSCsr18589

Symptoms: A Virtual Router Redundancy Protocol (VRRP) group configured on a VLAN interface flaps from the backup to the master state after stateful switchover (SSO) when the existing master is still available on the network. The group will flap back to backup a short period later.

Conditions: The problem only occurs when there are a large number of VLAN interfaces with a VRRP group configured on each interface and SSO is performed.

Workaround: Each of the VRRP groups can be configured with a larger VRRP advert timer value. Values should be varied depending on the setup, but a larger than default value is usually required.

CSCsr18942

Symptoms: Traceback occurs when VPN routing/forwarding (VRF) is deleted and then recreated.

Conditions: Occurs when multicast RP is configured under VPN routing/forwarding (VRF) first. When the VRF is deleted, some multicast data may still be locked and not deleted, causing the traceback when a new VRF is created and multicast RP is configured there.

Workaround: There is no workaround.

CSCsr26025

Symptoms: When "0.0.0.0/8 static route to null 0" is configured, the default gateway failover does not work. RIB is not updated.

Conditions: Occurs under the following scenario:

- Border Gateway Protocol (BGP) with two neighbors sending a default gateway. - Static route "0.0.0.0/8 to null 0" is configured. - Failover takes place and RIB is not updated.

Workaround: There is no workaround.

CSCsr27727

Symptoms: A Cisco Catalyst 6000 reports the following message and unexpectedly reloads:

%SYS-2-ASSERTION_FAILED: Assertion failed: "wccp_acl_item_valid(item,NULL)"

Conditions: This symptom is observed on a WS-C6509 that is running Cisco IOS Release 12.2(33)SXH2a.

A WCCP service is configured with a redirect-list referring to a simple ACL.

Workaround: Use an extended ACL as the WCCP redirect-list.

CSCsr29468

Cisco IOS Software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.

Cisco has released free software updates that address this vulnerability.

Several mitigation strategies are outlined in the workarounds section of this advisory.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml

CSCsr41079

Symptoms: Error message seen after stateful switchover (SSO):

%CHKPT-4-NOMESSAGE: Message is NULL, (Cannot get data ptr)

Conditions: Occurs when Intermediate System-to-Intermediate System (IS-IS) NSF is configured.

Workaround: There is no workaround.

CSCsr43461

Symptoms: Some configurations are missing after a reload.

Conditions: This symptom is seen when a router reloads that results in missing configurations of "vrf selection source" under show run.

Workaround: There is no workaround.

CSCsr45502

Symptoms: A router intermittently runs into crashes in a large scale network with active PPPoEoA sessions.

Conditions: This symptom occurs when many active PPPoEoA sessions exist.

Workaround: There is no workaround.

CSCsr49316

Symptoms: A crash happens when the show ipv6 rpf x:x:x::x command is given.

Conditions: This symptom is observed only when there are more than 16 adjacencies for a single static route. The crash happens when the show ipv6 rpf command is given for this particular static route.

Workaround: There is no workaround. This problem occurs as long as there are more than 16 adjacencies for single static route even if some of them are not active.

CSCsr51801

Symptoms: Some of the route-maps configured for BGP sessions (eBGP) are not permitting the prefixes upon a router reload.

Conditions: The symptom is observed when a large number of route-maps for a BGP session are configured and the router is reloaded.

Workaround: Issue the command clear ip bgp * soft.

CSCsr53264

Symptoms: A software-forced crash occurs on the RP of a Cisco 7600 running Cisco IOS Release 12.2(33)SRB2.

Conditions: Occurs when the clear route-map counters <name> command is entered.

Workaround: Upgrade to Cisco IOS Release 12.2(33)SRC3 or later.

CSCsr54959

Symptoms: Router crashed when removing a policy attached to a VLAN interface with a route map and access lists attached.

Conditions: Occurred on a Catalyst 4500 running Cisco IOS Release 12.2(46)SG. The device may reload unexpectedly due to a software-forced crash. Defect also affects other platforms and releases of Cisco IOS.

Workaround: There is no workaround.

CSCsr55713

Symptoms: A crash occurs.

Conditions: The crash is caused by a ping across an ISATAP tunnel. The symptom is observed only in Cisco IOS Release 12.4(15)T7 on the Cisco 7200 (it is not known to affect other platforms), since the crash is dependent on the Cisco IOS memory map (which varies with each image).

Workaround: There is no workaround.

CSCsr55922

Symptoms: The EIGRP IPv6 process may incorrectly select a router-ID from the 127.0.0.0 address range.

Symptoms: The same router-ID may be selected on two separate Cisco routers configured for EIGRP IPv6. External prefixes advertised by one of the EIGRPv6 routers will be ignored by the receiving EIGRPv6 router due to the fact the routerID contained in the external data portion of the prefix matches the receiving routerID; a loop prevention method.

Workaround: Manually configure a router-ID under the EIGRP IPv6 process with router-id<address> command.

CSCsr56465

Symptoms: Line card MAC notification test fails when redundancy mode is changed from RPR to SSO or SSO to RPR. SIP-400 Bus Connectivity Test failed when the following commands are issued:

Conf t redundancy mode rpr

Conditions: The issue observed in the Fabric Hot Sync-enabled Sup720 and RSP720 routers Cisco IOS Release 12.2(33)SRC. In the problem state, Super Santa Ana (SSA) channels are out of sync. For example, show platform hard ssa status will display SSA channel status from the SSA based CWAN module console.

Workaround: There is no workaround.

CSCsr60252

Symptoms: MPLS Layer 3 VPN with HQOS on PA-A6-OC3 with 500 ATM PVCs crashes at PEs wth online insertion and removal (OIR).

Conditions: Perform a soft OIR of PE while entering the hw-module slot 5 start command to observe the crash.

Workaround: Configure with HQoS for 500 PVCs.

CSCsr60789

Symptoms: Occasionally a crash occurs after preemptive switchover with no traffic.

Conditions: Unknown. Issue is not reproducible on a consistent basis.

Workaround: There is no workaround.

CSCsr68497

Symptoms: The router crash when the default pppoe enable command is entered.

Conditions: Occurs with 4094 PPPoE sessions active. When the above command is used to disable PPPoE under Ethernet subinterface, the router crashes.

Workaround: There is no workaround.

CSCsr68528

Symptoms: When there is heavy traffic on the 10-GE SPA (that is, 80 percent or more of line rate), and the interface is shut/no shut, there is a low probability that the interface may become stuck and incorrectly send pause frames on the connected link, interrupting traffic flow. This is also seen on ES20 line cards with 10-GE ports. (CSCsx82439)

Conditions: This symptom is observed when the link is shut/no shut while there is a high level of traffic on the link. In case of ES20, it is also seen in case of line card reload.

Workaround: Add and remove auto-negotiation on the interface configuration to recover the link. In case of ES20, toggling flow-control recovers the interface.

CSCsr70963

Symptoms: A Cisco 10000 PRE will reload unexpectedly when a radius server which is marked as dead is removed from the configuration during authentication of sessions.

Conditions: The issue is seen when a RADIUS server is marked as dead. There are attempts to retry and access the server during its removal from the configuration.

Workaround: There is no workaround.

CSCsr72352

Symptoms: EBGP-6PE learned IPv6 labeled routes are advertised to IBGP-6PE neighbor by setting NH as local IP address.

Conditions: This symptom is observed on 6PE Inter-AS Option C with RR case.

Workaround: There is no workaround.

CSCsr76818

Symptoms: Queue wedges on one of the SP input queues. When the peer switch was sending VTP packets to the switch trunk interface where no vtp was configured, the interface input-buffer was filled up by the VTP packets. When the buffer is full, the interface is not be able to process any incoming control packets.

Conditions: Occurs when the trunk interface is configured no vtp and its peer interface is a has VTP enabled.

Workaround: Configure the peer with no vtp to prevent VTP packets being received on the other interface.

CSCsr79367

Symptoms: Slow synchronization of IP subscriber sessions from Active to Standby RP.

Conditions: This issue is observed only for a large number of IP subscriber sessions. While the traffic is flowing, if user manually requests to clear all the sessions and while that is processing the line card reboots, then standby RP can get into a state there are dangling sessions. This does not render the router useless, but increases the sync time from active to standby.

Workaround: There is no workaround.

CSCsr80601

Symptoms: An ISAKMP SA is not deleted as expected after removing the RSA key.

Conditions: The issue is seen when the user tries to clear the ISAKMP SAs by issuing the clear crypto session command on an IKE SA that has multiple IPSEC SAs.

Workaround: Use the clear crypto sa and clear crypto is commands.

CSCsr81271

Symptoms: A Cisco 7600 router with PA-A3-T3 port adapter in flexwan module WS-X6582-2PA could generate following error messages with tracebacks upon a mass ATM PVCs flap:

SLOT 2/0: %CWAN_ATM-3-VC_OR_PORT_ERR: Invalid VCD FF03 or Port: 0 -Traceback= 403E2200 
403A8C1C 40344F88 40347FD0 403481B4 403C374C 401CD170

Slot 2/0 is the slot the port adapter is installed.

Conditions: This seems to only occur when a large number of ATM PVCs flap, most likely from the service provider side.

Workaround: There is no workaround.

CSCsr82785

Symptoms: If APS is configured on a large number of channelized sub-interfaces associated with a single controller such that a single failure can cause all of these interfaces to failover at the same time, and RIP is configured to run over these interfaces, high sustained CPU usage will be seen following the failover and reconvergence time will be lengthy.

Conditions: Large number of APS protected interfaces fail over at the same time. RIP is the protocol running on those interfaces. IP addresses on all interfaces are covered by the same network statement.

Workaround: There is no workaround.

Further Problem Description: The length of the high CPU and reconvergence period will increase as the number of impacted interfaces increases.

The length of the high CPU and reconvergence period will also increase as the number of network statements which cover the IP addresses on the affected interfaces decreases i.e. it will be worst when a single classful network (e.g. 10.0.0.0) covers all interfaces, somewhat better when multiple classful networks are impacted.

CSCsr82895

Symptoms: When a router has many PPPoE sessions and the router is configured as an RP-mapping agent, the router crashes following a switchover.

Conditions: The symptom is observed when the router has 8000 PPPoE sessions and it is configured as an RP-mapping agent. Following a switchover, the issue is seen.

Workaround: Another router that does not have as many interfaces in the network should be configured as the RP-mapping agent.

CSCsr84639

Symptoms: After 30 minutes, MIB synchronization failure messages appear on primary RP. Secondary RP crashes.

Occurs under the following scenario:

1) Bringup 1 pppox session on the L2TP network server (LNS)

2) Pass bidirectional traffic through the LNS

3) After 30 minutes, MIB sync failures message appear on primary RP and secondary RP crashes.

Workaround: Enter the no snmp mib notification-log default command.

CSCsr86515

Symptoms: Router crashed due to watchdog timeout in the virtual exec process:-

%SYS-3-CPUHOG: Task is running for (128000)msecs, more than (2000)msecs 
(129/17),process = Virtual Exec. -Traceback= 40B5D8A8 40B5D984 40B5DA4C 40B5DB78 
40B5DC6C 40C0E1BC 4125D3A8 4209FAEC 420AA5A0 4054C05C 420570D8 40575510 41257298 
41257284 %SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = Virtual Exec. 
-Traceback= 40B5D8C8 40B5D984 40B5DA4C 40B5DB78 40B5DC6C 40C0E1BC 4125D3A8 4209FAEC 
420AA5A0 4054C05C 420570D8 40575510 41257298 41257284

Conditions: This was observed on a Cisco 7600 with Supervisor 720 running Cisco IOS Release 12.2(33)SRB3 after a ATM sub-interface was removed.

Workaround: There is no workaround.

CSCsr86826

Symptoms: A standby SP may experience a memory leak in the mls-hal-agent process.

Conditions: This has been experienced on a Cisco 7600 router with dual SUP720s running either Cisco IOS Release 12.2(33)SRC or Cisco IOS Release 12.2(33) SRC1. The router is configured for multicast.

Workaround: There is no workaround.

CSCsr96042

Symptoms: ASR1000 Router crashes.

Conditions: Occurs if "ip vrf" is deleted from the configuration.

Workaround: There is no workaround.

CSCsr97343

Symptoms: An MSDP peer may flap randomly.

Conditions: The symptom is observed when the device is configured with logging host ip-address... or logging host ip-address.

Workaround: It has been observed that removing the "logging host" configuration helps in preventing the peer-flap: no logging host ip-address no logging ip-address

CSCsr97753

Symptoms: Pinging an interface fails.

Conditions: Occurs when unconfiguring xconnect on the interface.

Workaround: Perform a shut/no shut on the interface.

CSCsr98731

Symptoms: If running OSPF, stale routes may be installed in the RIB. Also wrong paths (inter-area vs. intra-area) are preferred.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRC1.

Workaround: There is no workaround.

CSCsu02975

Symptom: Router crashes due to memory corruption

Conditions: WAN router crashes when feature combination includes Frame Relay, EIGRP, GRE, QoS, and multicast are configured on WAN aggregation and branches.

The issue is seen only on PA-MC-2T3/E3-EC The issue is seen only when frame-relay fragment and service-policy is part of map-class frame-relay configs

Workaround: Have either frame-relay fragment or service-policy as part of map-class frame-relay configs

CSCsu03229

Symptoms: On the standby provider edge (PE) aggregation device, when label allocation fails, the box can crash upon retry.

Conditions: Occurs in redundancy mode in PE aggregation device configured for tunnel stitching.

Workaround: There is no workaround.

CSCsu04088

Symptoms: With unidirectional Ethernet (UDE) enabled on ES20 port, UniDirectional Link Detection (UDLD) gets disabled. But on converting the port from L3 to L2 (or vice versa) or on shut/no shut of interface, UDLD is enabled again on the interface. Once UDLD gets enabled, due to the UDE feature, the port is detected as unidirectional and put to err-disabled state.

Conditions: Occurs on ES20 ports configured for both UDE and UDLD.

Workaround: Disable UDLD on the port.

CSCsu04360

Symptoms: Acct-Time-Delay and Tunnel-Link-Stop records are missing from L2TP network server (LNS).

Conditions: Occurs when using radius server for authentication.

Workaround: There is no workaround.

CSCsu04473

Symptoms: Upon the first SSO switchover triggered with the redundancy force-switchover command, the traffic stops on the ATM N-to-1 VCC pseudowires configured with cell-packing in the direction from the MWR towards the 7600 SPA-4XOC3-ATM interface. Traffic recovers normally in the other direction.

Conditions: Occurs on a Cisco 7600 S-series equipped with dual SUP720-3BXL. The problem is seen only when cell-packing is enabled on the N-to-1 VCC pseudowires and when APS (MR-APS) is configured on the ATM OC3 interface of the Cisco 7600 SPA-4XOC3-ATM.

Workaround: Disable cell-packing on the ATM N-to-1 VCC pseudowires or alternatively disable APS on the SPA-4XOC3-ATM interface.

CSCsu05525

Symptoms: After removing the "default-originate" configuration, the default-route is not withdrawn.

Conditions: Occurred on a router running Cisco IOS Release 12.2SR.

Workaround: Clear the session to remove the configuration.

CSCsu08935

Symptoms: BGP as-override does not work properly on a PE to overwrite the AS in the AS4_PATH.

Conditions: When a 4 byte CE is peered to a 2 byte capable PE using AS 23456 and the command as-override is configured on the neighbor, the PE router does not override the AS in the AS4_PATH with its own AS number, mapped to 4 bytes.

Workaround: Use "allowas-in" on the CE.

CSCsu09663

Symptoms: Router crashes when scaling DHCP sessions on Cisco Intelligent Services Gateway (ISG).

Conditions: When the MCP-ISG is acting as DHCP Relay Agent or DHCP server, it crashes while large number of Layer 2-connected sessions are coming up.

Workaround: There is no workaround.

CSCsu10229

Symptoms: cdpCacheAddress(OID:1.3.6.1.4.1.9.9.23.1.2.1.1.4) MIB is not showing GLOBAL_UNICAST address.

Conditions: Occurs on a Cisco 7200 router running Cisco IOS Release 12.4(15)T7.

Workaround: There is no workaround.

CSCsu12040

Symptoms: BGP neighbors that are configured with as-override and send-label (CsC) together may not work after an interface flap or service reset.

Conditions:

neighbor xxx as-override neighbor xxx send-label

Workaround: Enter the "clear ip bgp * soft in" command.

Further Problem Description: Peers (neighbors) with a CsC (IPv4+label) BGP configuration with the as-override option should be separated into different dynamic update groups during the BGP update generation process. After the CSCef70161 fix in Cisco IOS Release 12.0(32)SY4, this is no longer the case; this CSCsu12040 fix enhances the CSCef70161 fix to handle the CsC (IPv4+label) case separately.

CSCsu24087

Symptoms: A router hangs for a couple of minutes, then crashes anytime the clear ip bgp neighbor x.x.x in command is issued.

Conditions: This symptom occurs when a router crashes when the clear ip bgp neighbor x.x.x.x soft in command is issued when the following commands are configured for that neighbor (without route-map): 1) neighbor x.x.x.x soft-reconfiguration inbound 2) neighbor x.x.x.x weight 3) neighbor x.x.x.x filter-list in

If any one of the commands is not configured, then the router will not crash.

Workaround: Configure route-map instead of filter-list for inbound direction. For example: "neighbor x.x.x.x filter-list 1 in" replace with "neighbor x.x.x.x route-map name in"

where, route-map name permit 10 match as-path 1

CSCsu26315

Symptoms: Traffic may not resume on ATM over MPLS (ATMoMPLS) connections.

Conditions: The symptom is observed when both ATMoMPLS and ATM over LS (ATMoLS) connections are on same card and a card reset is done.

Workaround: Reload the PXF.

CSCsu27109

Symptoms: When stateful switchover (SSO) is performed on a Cisco 7600, MPLS label allocation fails.

Conditions: Issues are seen on Cisco 7600 router. Occurs after performing the SSO. Also seeing CPU usage above 95% for 10-15 minutes.

Workaround: There is no workaround.

CSCsu27843

Symptoms: Router crashes when DHCPv6 is configured on the router.

Conditions: Router crashes when we remove the subinterface on which DHCPv6 PD request was configured.

Workaround: There is no workaround.

CSCsu27888

Symptoms: IGMP v3 reports are discarded.

Conditions: Occurs on Cisco 7200 router running Cisco IOS Release 12.4(20)T2.

Workaround: There is no workaround.

CSCsu27894

Symptoms: Flurry of DUP_IFINDEX messages are seen on standby.

Conditions: Occurs during bulk sync phase when standby is coming up.

Workaround: There is no workaround.

CSCsu31088

Symptoms: Not able to execute any commands under interface after running BERT tests.

Conditions: This issue is seen only after running SPA FPGA BERT tests and also when there is dual RP in chassis. With other BERT options, no issue is seen.

Workaround: There is no workaround.

CSCsu31935

Symptoms: Bootup diag test failures observed on 6816 card when multirouters are reloaded. Some ports were put in error disabled state.

Conditions: Failure triggered with random multirouters reloads (reload of CE1, PE1, Core1). Brief router info and config: IOS - 8/25 a76 Dual sup720 7606 6724 connected to remote 6724 (servicing vlans 2-2000) 6816 connected to remote 6816 (servicing vlans 2001-4000) sip600 (servicing vlans 1-4000 switchport)

Topology:

CE1----PE1----Core-1-----Core-2----PE2----CE2 Affected router is CE1.

Configuration: 4k VLANs, 6816 servicing VLANs 2001-4000 (switchports).

Workaround: Run the failing diag tests on demand.

Further Problem Description: Few bootup tests fail when on 6816 card when the multirouters are reloaded. On failure, the ports are put in error disabled state. Failure cause has been root caused to usage of reserved diag vlans in the configs. Please refer the link mentioned below.

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.1E/native/command/reference/S1.html

switchport dot1q: Do not enable the reserved VLAN range (1006 to 1024) on trunks when connecting a Catalyst 6500 series switch running Cisco IOS software on both the supervisor engine and the MSFC to a Catalyst 6500 series switch running Catalyst software. These VLANs are reserved in systems running Catalyst software. If enabled, systems running Catalyst software may error disable the ports if there is a trunking channel between these systems

When the diag vlans (1006 to 1011, 4094 to 4089) are used, there could be diag failures at some random cases. Please do not enable the reserved vlans.

CSCsu31954

Symptoms: A router reloads.

Conditions: Under certain crypto configurations with NetFlow also configured, the router will reload when required to fragment CEF-switched traffic on a Cisco 7200 router.

Workaround: There is no workaround.

CSCsu32104

Symptoms: A PRE-3 that is running Cisco IOS Release 12.2(31)SB code may encounter a Redzone overrun memory corruption crash.

Conditions: Unknown at this time.

Workaround: Turn off Auto IP SLA MPLS by entering the auto ip sla mpls reset command.

CSCsu35597

Symptoms: Renaming a directory gives error message.

Conditions: This happens on a Cisco router running Cisco IOS Release 12.4(20)T1.fc2 image

Workaround: There is no workaround.

CSCsu35624

Symptoms: When a private VLAN is configured on a VTPv3 server and then deleted, the update message on a peer VTPv3 client can cause a stack overflow for VLAN manager process and crash.

Conditions: Occurs in a Cisco 7600 running Cisco IOS Release 12.2(33)SRD.

Workaround: There is no workaround.

CSCsu36697

Symptoms: The line card reloads when a line card online insertion and removal (OIR) is performed. It does not happen consistently.

Conditions: This occurs when an empty policy is present.

Workaround: There is no workaround.

CSCsu36709

Symptoms: A router may unexpectedly reload.

Conditions: The symptom is observed specifically with a configuration of Enhanced Interior Gateway Routing Protocol (EIGRP) that is used to redistribute BGP routes. Plain EIGRP is not affected.

Workaround: Do not use EIGRP to redistribute BGP.

CSCsu36836

Symptoms: TCL scripts and policies attempting to work with open files and sockets simultaneously may not operate properly. One symptom is the vwait command may fail by reporting "would wait forever".

Conditions: Occurs when a TCL script opens both a file and a client or server socket simultaneously.

Workaround: Open and close files and sockets separately. Avoid having them open simultaneously.

CSCsu37205

Symptoms: BGP dampening under VPNv4 may cause router crash.

Conditions: Occurs when BGP dampening is enabled on VPNv4 address family, but not on individual IPv4 VRF<VRF-name>address-family.

Workaround: Enable the same set of BGP dampening on both the VPNv4 address family as well as all entries for IPv4 VRF address-family.

CSCsu39152

Symptoms: IF-MIB registration fails as there are no free ifIndex available.

Conditions: Occurs after an upgrade. Seen only in HA systems.

Workaround: There is no workaround.

CSCsu39704

Symptoms: Unable to configure pseudowire on virtual-PPP interface. Command is rejected with the following error:

Incompatible with ip address command on Vp1 - command rejected

Conditions: Occurs when IPv4 address or IP VPN routing/forwarding (VRF) has already been configured on the main interface.

Workaround: There is no workaround.

CSCsu40667

Symptoms: A Cisco 7600 series router may fail to install some NetFlow entries even if NetFlow table utilization is low.

Conditions: Occurs while flows are ingressing on ES20 module.

Workaround: There is no workaround.

Further Problem Description: The show mls netflow table-contention detail command will show a heavy ICAM table utilization, while TCAM utilization is small.

Router#sh mls net table-contention det
Earl in Module 1
Detailed Netflow CAM (TCAM and ICAM) Utilization
================================================
TCAM Utilization : 0%
ICAM Utilization : 98%
Netflow TCAM count : 152
Netflow ICAM count : 126
Netflow Creation Failures : 388663
Netflow CAM aliases : 0 

CSCsu42078

Symptoms: A router may crash due to bus error caused by an illegal access to a low memory address.

Conditions: This happens when a service-policy is applied to an interface, and then service-policy is removed under certain conditions.

One such condition is that "ip cef distributed" was configured on the router and the multi-link member flap triggered the service policy removal.

The problem is that, after the policy was removed, the packet path vector was not reset correctly and still trying to access the already-removed policy internally. When traffic flows, it will cause crash.

Workaround: For the above example, remove "ip cef distributed" from the configuration.

CSCsu42315

Symptoms: When the L3VPN prefix uses a tunnel with fast reroute (FRR) protection, there is traffic loss during reoptimization.

Conditions: Not all prefix in the VRF will observe this issue. This is seen only when there are more than 250,000 prefixes.

Workaround: There is no workaround.

Further Problem Description: Traffic loss during re-optimization can be due to faster tunnel cleanup also. It is advisable to configure mpls traffic-eng reoptimize timers delay cleanup <seconds> to fine tune the cleanup according to the topology.

CSCsu44992

Symptoms: VPDN redirect functionality does not work.

Conditions: Basic functionality is broken. No special condition is required.

Workaround: There is no workaround.

CSCsu46822

Symptoms: When account logon is done for a DHCP user, QoS policies defined in the user profile are not applied to the ISG session.

Conditions: A DHCP session is created. User performs account logon via SESM (not CoA). User profile has QoS polices defined. Session is authenticated but policies are not applied to the session.

Workaround: Perform account logon using CoA.

CSCsu46871

Symptoms: Unable to attach service policy to VT when bandwidth is configured in class default.

Conditions: Occurs when DLFI over ATM is configured while trying to attach service policy to VT when bandwidth is configured in class default.

Workaround: Configure bandwidth in user defined class and attach to VT.

CSCsu47037

Symptoms: Router crashes when an attempt is made to forward a packet out of an Auto-Template interface.

Conditions: This occurs when the interface's MTU is set to 0: Use the show interface Auto-Template X command to show the MTU.

Workaround: Configure a protocol MTU directly on the Auto-Template interface.

CSCsu48898

Symptoms: A Cisco 10000 series router may crash every several minutes.

Conditions: The symptom is observed with a Cisco 10000 series router that is running Cisco IOS Release 12.2(31)SB13.

Workaround: Use Cisco IOS Release 12.2(31)SB11.

CSCsu50118

Symptoms: More convergence time seen even with the carrier-delay msec 0 command configured.

Conditions: Occurs when carrier-delay msec 0 is configured on a gigabit interface.

Workaround: If excessive convergence time is observed even with the carrier-delay msec 0 command configured, enter the command again on the interface.

CSCsu51095

Symptoms: If connected routes are optimized using PfR, there will be a routing loop.

Conditions: This symptom can occur if, for some reason, PfR is learning connected routes or if the user has configured them.

Workaround: Create an oer-map with a prefix-list that contains the prefixes with the IP addresses of the connected routes (the next hops). Set the set observe mode in the oer-map.

CSCsu51245

Symptoms: Port-channel QinQ subinterface on ESM20 and SIP600 line cards do not pass traffic after router reload and line card reset.

Conditions: This condition is seen after router reload or member link line card reset. This is not seen when configuration is newly applied.

Workaround: To recover from the condition, perform a shut/no shut on the port channel main interface.

CSCsu53497

Symptoms: Traffic loss occurs in routed-PW interfaces.

Conditions: Occurs following router bootup with highly scaled VPN, PW, and SVI configuration.

Workaround: Perform a shut/no shut on SVI or on the failing interfaces.

CSCsu54801

Symptoms: IPv6/IPv6 Tunnel adjacency information is incomplete on the line card. This prevents IPv6/IPv6 multicast traffic on the tunnel.

Conditions: The symptoms are observed under normal operation.

Workaround: There is no workaround.

CSCsu55145

Symptoms: Router crashes due to critical software exception.

Conditions: Occurs on a Cisco ASR 1000 running Cisco IOS Release 12.2.

Workaround: There is no workaround.

CSCsu55883

Symptoms: With MLPPP configured on OSM, the following symptoms may be observed:

1. Line card might crash.

2. Links might flap.

3. Following error message from line card might be seen: "SLOT 9: Sep 14 13:48:48.479 CDT: %COMMON_FIB-3-FIBIDBINCONS2: An internal software error occurred. Multilink1 linked to wrong idb R11_Mu1"

Conditions: Occurs on routers running various Cisco IOS Release 12.2SR releases. Performing a shut/no shut on the OSM (especially on the card containing MLPPP) interfaces might trigger this issue.

Workaround: There is no workaround.

CSCsu56806

Symptoms: Hot Standby Routing Protocol (HSRP) IPv6 configuration can be re-added to a VLAN by software after the configuration has been deleted.

Conditions: If Hot Standby Routing Protocol (HSRP) IPv6 is configured on a VLAN interface, and the VLAN interface is deleted, then the HSRP IPv6 configuration will reappear on the VLAN if the VLAN is later recreated. Once this occurs then there is no way to remove the HSRP configuration.

Workaround: Remove the HSRP configuration before deleting the VLAN.

CSCsu57182

SYMPTOM:

The Cisco IOS may experience high CPU utilization.

CONDITIONS:

ISAKMP is enabled.

WORKAROUND:

None.

FURTHER INFORMATION:

This issue can occur if the Cisco IOS device processes a malformed IKE message.

CSCsu57331

Symptoms: In a Virtual Private LAN Services (VPLS) scenario with ESM20 as core facing interface, imposition traffic might fail.

Conditions: Occurs only when ports from Bay 1 are used as core facing interface.

Workaround: Reset the line card.

CSCsu57958

Symptoms: In a scenario where a Catalyst 6500 or Cisco 7600 performs DHCP snooping + DAI functionality and a second device acts as DHCP relay, it was observed that DHCP snooping database was not populated. DHCP snooping is configured in this case on the ingress VLAN (traffic from the DHCP clients) and the DHCP server can be reached on a different egress VLAN (DHCP requests are routed).

DHCP Replies from the server (DHCPOFFER and DHCPACK) are not snooped by the Catalyst 6500 or Cisco 7600 and so bindings are not established. Consequence is that clients will get their own IP Address but ARP Inspection will fail because bindings were not learned on the device.

Conditions: Occurs with DHCP Snoooping + DAI configured on a Catalyst 6500 or Cisco 7600 in a routed scenario (Ingress VLAN and Egress VLAN are different) and DHCP Relay performed by a different device.

Workaround: Configure DHCP Snooping on both client and server side VLANs. Problem is applicable to both Cisco IOS Release 12.2(18)SXF and Cisco IOS Release 12.2(33)SRB.

CSCsu62667

Symptoms: LSP ID change after stateful switchover (SSO) due to failure in signaling recovered label switched path (LSP).

Conditions: Occurs following a SSO switchover.

Workaround: There is no workaround.

CSCsu63994

Symptoms: With L2TPv3 sessions configured on the active RP, the CPU on standby RP is being used to setup L2TPv3 sessions to peer. The standby keeps attempting to establish all L2TPv3 sessions, which obviously fail to establish, and hence it keeps on retrying forever. This is a waste of standby RP CPU, since there is no point in attempting to establish sessions with peer on standby.

Conditions: Occurs when L2TPv3 pseudowires are configured on a router with active and standby RPs.

Workaround: There is no workaround.

CSCsu63996

Symptoms: NSF restart may be terminated and OSPF NBR may flap during RP switchover. The debug ip ospf adj command shows the following message: OSPF: Bad request received.

Conditions: The symptoms are observed when the links are broadcast networks and the restarting router is DR. It is seen when "nsf cisco" is configured and when some neighbors finish OOB resync much sooner than others.

Workaround: Use the nsf ietf command.

Alternate workaround: Configure routers so that the restarting router is not DR (use ospf network type point-to-point or priority 0).

CSCsu64215

Symptoms: Router may incorrectly drop non TCP traffic. TFTP and EIGRP traffic can be impacted as seen in CSCsv89579.

Conditions: Occurs when the ip tcp adjust-mss command is configured on the device.

Workaround: Disable ip tcp adjust-mss on all interfaces. Note that this may cause higher CPU due to fragmentation and reassembly in certain tunnel environments where the command is intended to be used.

CSCsu64323

Symptoms: The show vpdn history failure command should show the history of session failures due to entering incorrect password, but it does not show any history.

Router#show vp hi fa % VPDN user failure table is empty

Conditions: The problem was seen with Cisco 7201 running Cisco IOS Release 12.2(33)SRC1. No problem with Cisco IOS Release 12.4(4)XD9.

Workaround: There is no workaround.

CSCsu65189

Symptoms: If router is configured as follows:

router ospf 1 ...
passive-interface Loopback0

And later is enabled LDP/IGP synchronization using command

Router(config)#router ospf 1 Router(config-router)# mpls ldp sync 
Router(config-router)#^Z

MPLS LDP/IGP synchronization will be allowed on interface loopback too.

Router#sh ip ospf mpls ldp in Loopback0 Process ID 1, Area 0 LDP is not configured 
through LDP autoconfig LDP-IGP Synchronization : Required < ---- NOK Holddown timer is 
not configured Interface is up

If the clear ip ospf proc command is entered, LDP will keep the interface down. Down interface is not included in the router LSA, therefore IP address configured on loopback is not propagated. If some application like BGP or LDP use the loopback IP address for the communication, application will go down too.

Conditions: Occurs when interface configured as passive. Note: all interface types configured as passive are affected, not only loopbacks.

Workaround: Do not configure passive loopback under OSPF. Problem only occurs during reconfiguration.

The problem will not occur if LDP/IGP sync is already in place and: - router is reloaded with image with fix for CSCsk48227 - passive-interface command is removed/added

CSCsu65225

Symptoms: TFTP from supervisor to ACE modules fail.

Conditions: Results in the inability to copy/upgrade images to standby ACE. This is due to moving all 127.x.x.x addresses in an internal VPN routing/forwarding (VRF), which causes TFTP to fail.

Workaround: ACE modules could fail-over to make standby as active and then FTP from the server directly.

CSCsu67461

Symptoms: Router may crash when "show tracking brief" is entered if one or more tracking object have been created using the Hot Standby Routing Protocol (HSRP) cli, such as standby 1 track Ethernet1/0.

Conditions: This does not occur if all tracking objects use the new track command as follows:

track 1 interface Ethernet1/0 line-protocol interface Ethernet 0/0 standby 1 track 1

Workaround: Use show tracking instead, or configure tracking with the new command.

CSCsu67637

Symptoms: IPv6 address of loopback interface set as passive under Intermediate System-to-Intermediate System (IS-IS) router process is not present in IS-IS database.

Conditions: Issue is seen when loopback interface is set as passive under router IS-IS configuration and the IPv6 address of the interface is only added afterwards. If the passive-interface command is used when the loopback interface already has its IPv6 address configured, issue is not seen.

Workaround: After the IPv6 address is configured under the affected interface, remove and add the passive-interface configuration under the router IS-IS process.

CSCsu69590

Symptoms: After Flex Link failover, connectivity may be lost. Configured VLANs might be pruned on active link, causing VLAN interface to go down.

Conditions: This usually happens after the second Flex Link failover.

Workaround: Remove the Flex Link configuration from the interface, then reconfigure it.

CSCsu71004

Symptoms: Cisco 7600 RP crashes while executing the copy tftp sup-bootdisk: command. A similar crash seen upon switchover

Conditions: Occurs when issuing a copy command from SP console on an RSP720.

Workaround: There is no workaround.

CSCsu71728

Symptoms: A crash may occur while applying QOS under an MFR interface.

Conditions: The symptoms are observed while applying QOS under an MFR interface on a PA-MC-2T3-EC in L2VPN.

Workaround: There is no workaround.

CSCsu72025

Symptoms: SIP400 may crash during Change of Authorization (CoA) push.

Conditions: Occurs on a SIP400 with ACL configurations on iEdge sessions and CoA push enabled.

Workaround: There is no workaround.

CSCsu73128

Symptoms: Router crashes.

Conditions: Occurs when large number of remote end points try to connect to the gateway at the same time. The router may crash if "rsa-sig" is used as authentication method.

Workaround: There is no workaround.

CSCsu74397

Symptoms: When removing PA-MC-8TE1+ from the chassis, the router has an unexpected system reload. This reload happens when you remove the port adapter and the router is running the Cisco IOS bootloader image. Also happens when the port adapter is removed after the router finishes loading the Cisco IOS bootloader image and before it loads the complete Cisco IOS Software image.

Conditions: This occurs on a Cisco 7200 VXR NPE-G2 Series Routers on the Cisco IOS bootloader image from the Cisco IOS Release 12.4(4)XD.

Workaround: Remove PA-MC-8TE1+ when the complete Cisco IOS Software Image finishes loading.

CSCsu76800

Symptoms: "Acct-Input-Giga-word" and "Acct-Output-Giga-wor" attributes are missing in the Accounting request packets.

Conditions: The symptoms are observed when you send traffic that requires the giga word counters to be incremented.

Workaround: There is no workaround.

CSCsu77549

Symptoms: Protocol Independent Multicast (PIM) VPN routing/forwarding (VRF) neighbors not formed.

Conditions: Occurs after line card reload.

Workaround: Delete and add back the MVPN configuration.

CSCsu78559

Symptoms: In scaled conditions (8000 IP sessions) with SACL applied, line card memory leaks over a period of 4-5 hours. Sometimes this even results in a line card crash. The "Sacl Np Client" task occupies most of the CPU, and a large number of IP sessions (around 10% of 8k) will be in feature pending status, with ACL pending flag set.

Conditions: Occurs under scaled conditions with approximately 8000 IP sessions, with the same SACL applied to all IP sessions.

Workaround: There is no workaround.

CSCsu79340

Symptoms: Cisco router crashed while Intermediate System-to-Intermediate System (IS-IS) is coming up.

Conditions: Occurred only on a Cisco router running Cisco IOS Release 12.2(33)SRC2 with "mpls traffic-eng multicast-intact" configured under "router isis".

Workaround: Disable "mpls traffic-eng multicast-intact" configuration.

CSCsu81406

Symptoms: Following a processor switchover in route processor redundancy (RPR) plus mode, the SM-1CHOC12/T1-SI card on the channelized serial interfaces goes down.

Conditions: Occurs after the processor switchover in RPR plus mode.

Workaround: Use hw-module reset to solve the issue.

CSCsu81838

Symptoms: Memory leak occurs.

Conditions: Occurs during normal operations.

Workaround: There is no workaround.

CSCsu82893

Symptoms: Features requiring nas-port as a username determined by AAA (such as pre-auth) will not work on the standby device, causing standby sessions to be poisoned.

Conditions: AAA calculates the IP address of the best port, which is up and active. However, on the standby device, no interface is visibly active, resulting in a best IP address defining the router to be 0.0.0.0.

Workaround: There is no workaround.

CSCsu83563

Symptoms: Multicast rate-limiters stop working after a HA switchover.

Conditions: To see this issue you have to have a HA setup with multicast rate-limiters set. In order to see this issue the rate-limiters must have been set before the standby is booted. If the rate-limiters are set after standby is up in HOT state, the issue is not seen after switchover.

Workaround: Remove and reconfigure the rate-limiters.

CSCsu83588

Symptoms: After a router reload, the Flex Link configuration (switchport backup interface Po#) is lost.

Conditions: Occurs when a backup interface is a port-channel interface.

Workaround: There is no workaround.

CSCsu87248

Symptoms: Router crashes while adding flexible NetFlow.

Conditions: Occurred on a router running Cisco IOS Release 12.2(33)SRC1.

Workaround: There is no workaround.

CSCsu88256

Symptoms: Imposition traffic on a Ethernet Over MPLS (EoMPLS) VC is dropped.

Conditions: Occurs if xconnect is configured on a EVC with switchport on another interface.

Workaround: There is no workaround.

Further Problem Description: When this problem happens the DMAC used by the imposition line card is that of the switchport interface instead of the router MAC address, causing the packet to be dropped.

CSCsu89550

Symptoms: All tagged packets on a hardware Ethernet Over MPLS (EoMPLS) VC is subjected to CoPP when the VC is down.

Conditions: Occurs if VC is brought down by flapping core facing interface.

Workaround: Remove the control-plane policy.

Further Problem Description: It is applicable to only port-mode hardware EoMPLS.

CSCsu90280

Symptoms: IPv6 DMVPN tunnel does not work. IPv6 NHRP registration between Hub and Spoke fails.

Conditions: The symptoms are observed under normal operation.

Workaround: There is no workaround.

CSCsu92966

Symptoms: Send statistics from the show mpls l2 vc command are not displayed.

Conditions: Occurs on a PE when the other PE's core-facing link is flapped.

Workaround: Perform a shut/no shut on the SVI interface.

CSCsu93374

Symptoms: The group state of a slave group may unexpectedly change to Active after an RP switchover.

Conditions: The symptom is observed when HSRP multigroup is configured such that a slave group follows the state of a master group. If the HSRP group state is Standby, then the group state of the slave group may change to Active after an RP switchover.

Workaround: There is no workaround.

CSCsu94030

Symptoms: Internal VRF gets disabled at when the router boots up.

Conditions: Occurs after any failover or router start-up scenario

Workaround: Use the no platform ivrf disable to avoid the issue.

CSCsu94720

Symptoms: Router crashes when the shutdown command is used on an interface.

Conditions: Occurs when there are DHCPv6 bindings.

Workaround: There is no workaround.

CSCsu94864

Symptoms: The MLS shortcut for a user-traffic flow based on RADIUS Framed-IP (FIP) is not purged when the FIP sticky times out. RADIUS Load Balancing (RLB) sends out a purge request before deleting sticky and has no effect in deleting the MLS shortcut entry.

Conditions: Occurs on a device configured with RLB and FIP sticky idle timer and with MLS aging timer configured higher than the RLB FIP sticky idle timer.

Workaround: There is no workaround.

CSCsu95080

Symptoms: A router remains in the init_process state when parsing the configuration.

Conditions: The symptom is observed when an IPv6 multicast group joins without MLD configured. When the groups unjoin, the system suspends.

Workaround: Configure MLD.

CSCsu95171

Symptoms: In switches running Cisco IOS Release 12.2(33)SRC, high CPU may be seen on the SP/DFC due to NDE-IPv4 process. This may result in following unrelated problems:

- Corrupted file system(s)

- show running command may show "read error" etc.

- Continuous CPUHOGs automatically disabling Cisco Express Forwarding (CEF).

Log Messages reported:

%SYS-SP-3-CPUHOG: Task is running for (4000) msecs, more than (2000)msecs 
(2/0),process = NDE - IPV4.

Conditions:

- Affects 12.2(33)SRC or later, but not earlier versions.

- Slow response to console commands.

- Netflow enabled on point-to-point interfaces

- High number of IPv4 routes learned via BGP.

Workaround: Downgrade to the latest release of 12.2(33)SRB. During high CPU condition, do the following:

1. Remove ALL interface level and global netflow configurations.

2. Configure global command: cef table output-chain build favor convergence-speed.

3. Re-apply global and interface level netflow configurations.

The cef table ... command mentioned above will stay in the configuration. This command should stop this issue from re-occurring.

CSCsu95319

Symptoms: Igmp-proxy reports for some of the groups are not forwarded to the helper. This causes members not to receive the multicast traffic for those groups.

Conditions: The problem is seen when the igmp-proxy router is receiving UDP control traffic. That is, the router is receiving any UDP control-plane traffic on any interface.

Workaround: There is no workaround.

CSCsu96649

Symptoms: On Cisco 7600 with RSP720-3C-10GE processor, if the SIP-400 is configured as Lawful Intercept (LI) service module after a line card online insertion and removal (OIR), the SIP-400 may not get selected as Lawful Intercept service module.

Conditions: Occurs when the SIP-400 is configured as Lawful Intercept service module on the Cisco 7600.

Workaround: After line card OIR, select the SIP-400 again as the LI service module using the command li-slot list <sip400 slot number>.

CSCsu96730

Symptoms: Intelligent Services Gateway (ISG) traffic from one user to another may fail if the packet needs to be processed by the RP in a Cisco 7600.

Conditions: Occurs when ISG is configured and packets are switched from one subscriber to a second subscriber.

Other symptoms : - Counters of packet transfer might show difference between user transferring between each other - Access-list might fail to block the packet

The 2 above symptoms will be seen when user are sending receiving on the same interface via the ISG

Workaround: There is no workaround.

CSCsu97934

Symptoms: NPE-G1 is crashing with "pppoe_sss_holdq_enqueue" as one of the last functions.

Conditions: Unknown.

Workaround: Entering the deb pppoe error command will stop the crashing.

CSCsu99573

Symptoms: Cisco router crashes when Open Shortest Path First (OSPF) neighbor is being configured in non-base topology and IP address of the neighbor does not fall into range of any existing interface.

Conditions: This crash will only occur when OSPF is configured to support multi-topology routing, and neighbor statements are used in the submode for a non-base topology.

Workaround: Configure the neighbor with this IP address in the base topology first.

CSCsv00168

Symptoms: Junk values are being displayed on the router when characters/commands are inputted. For example, enter "enable", it shows "na^@^@"; enter "show version", it shows "h ^v^@e^@^r^@^@^@^@^@".

Conditions: The symptoms are observed with Cisco IOS Release 12.4(23.2)T.

Workaround: There is no workaround.

Further Problem Description: The CLI function is not affected by the junk values.

CSCsv01474

Symptoms: The ip rip advertise command might be lost from the interface.

Conditions: This symptom occurs in any of the following three cases:

1. The interface flaps. 2. The clear ip route command is issued. 3. The no network <prefix> command and then the network <prefix> command are issued for the network corresponding to the interface.

Workaround: Configure the timers basic command under the address-family under rip.

CSCsv02117

Symptoms: The following system error message with "Out of IDs!" warning is seen with traceback:

%IDMGR-3-INVALID_ID: bad id in id_get (Out of IDs!) (id: 0x0)

Conditions: This symptom is observed when flapping 24K sessions over 12K tunnel once, recreating this issue.

Workaround: There is no workaround.

CSCsv03300

Symptoms: Cisco 7200 NPEG2 router crashes while displaying the interface output for onboard gigabit ethernet using the show interface gig0/x command.

Conditions: Occurs when a CBWFQ QoS policy is attached to the onboard gigabitethernet interface.

Workaround: There is no workaround.

CSCsv04674

Symptoms: The M(andatory)-Bit is not set in Random Vector AVP, which is a must according to RFC2661.

Conditions: This symptom is observed with Egress ICCN packet with Random Vector AVP during session establishment.

Workaround: There is no workaround.

CSCsv04733

Symptoms: A LAC might terminate a tunnel unexpectedly.

Conditions: This symptom is seen when the tunnel password exceeds 31 characters.

Workaround: Use a shorter password if policy allows.

Further Problem Description: This is seen with Cisco IOS interim Release 12.2 (34.1.3)SB1. With a customer specific special based on Cisco IOS Release 12.2 (31)SB11, it allowed 64 characters.

CSCsv05934

Summary: Cisco's VTP protocol implementation in some versions of Cisco IOS and CatOS may be vulnerable to a DoS attack via a specially crafted VTP packet sent from the local network segment when operating in either server or client VTP mode. When the device receives the specially crafted VTP packet, the switch may crash (and reload/hang). The crafted packet must be received on a switch interface configured to operate as a trunk port.

Workarounds:There are no workarounds available for this vulnerability.

This response is posted at http://www.cisco.com/warp/public/707/cisco-sr-20081105- vtp.shtml

CSCsv06309

Symptoms: Link debounce down feature not working on RSP720-3C-10GE ports due to fast link feature.

Conditions: Occurs when link debounce is configured on RSP720-3C-10GE.

Workaround: Use "carrier-delay" instead.

Further Problem Description: On configuring link debounce, fast link, which is enabled by default and has no CLI, needs to go off but does not.

CSCsv06608

Symptoms: SXP is set up between two devices but fails to initialize.

Conditions: This symptom is observed when SXP is set up between two devices.

Workaround: There is no workaround.

CSCsv07188

Symptoms: Unable to configure PVC when connect command is configured.

Conditions: Occurs Cisco 7200 routers.

Workaround: There is no workaround.

CSCsv08352

Symptoms: Some static routes are not in the IP routing table state after a stateful switchover (SSO).

Conditions: This only occurs following a SSO event.

Workaround: Perform a shut/no shut of interface if the route does not come up automatically.

CSCsv08528

Symptoms: After the Resilient Ethernet Protocol (REP) topology is returned by the rep preempt command, MAC address table is not cleared.

Conditions: During internal testing, this occurred approximately 3 times out of 20.

Workaround: Use the clear mac-address-table dynamic command to clear the table.

CSCsv13243

Symptoms: Configuring Bidirectional Forwarding Detection (BFD) for a Border Gateway Protocol (BGP) neighbor that is established on a subinterface will cause the BGP session to go down.

Conditions: Occurs on a Cisco 7600 router with BGP session established on a subinterface and the subinterface is configured in "native vlan" mode while the configured BFD session is in ECHO Mode.

Workaround: Configure subinterface in "non-native" mode.

CSCsv13738

Symptoms: There are two ways to define VRFs when supporting the 6VPE feature: 1) ip vrf 2) vrf definition. The "vrf definition" configuration may take a much longer time to allow convergence between the PE and the CE than the "ip vrf" configuration.

Conditions: The symptoms are observed under the following conditions: - when the router boots up; and - when the issue has been seen using the "vrf definition" configuration; and - when the router has over 100,000 VPNv4 BGP routes; and - when a large number of VRFs are configured.

Workaround: Use the "ip vrf" configuration, if you have only IPv4 VRFs configured.

CSCsv13914

Symptoms: Traceback observed when the PPPoEoA session is brought up.

Condition: Occurs when the interface is not up.

Workaround: There is no workaround.

CSCsv14963

Symptoms: A provider-edge (PE) router configured to run Multicast VPN (MVPN) will not install an alternate MDT next-hop on a route that is learned through an OSPF sham-link.

Conditions: The symptom is observed when two PEs are configured to run MVPN and create a sham-link between them. Remote routes that are learned through the sham-link will not have an MDT tunnel.

Workaround: There is no workaround.

CSCsv15040

Symptoms: Infinite Loop occurs when doing MIB walk on cdot1agStackTable objects.

Conditions: Occurs on a Cisco 7600 running Cisco IOS Release 12.2(33)SRD and configured with 10GE-XFP-SPA and SIP-600 configured for Distributed Forward. This problem is seen when "MIP/MEP" configured on Te1/0/0 interface and MIB walk is performed on cdotagStackTable objects.

Workaround: Do not configure "MIP/MEP" on Te1/0/0 interface.

CSCsv16869

Symptoms: BGP updates may not be sent out.

Conditions: The symptom is observed when neighbors are flapped in a large- scale scenario.

Workaround: There is no workaround.

CSCsv20125

Symptoms: PPPoE sessions over VLAN over ATM with process switch stuck at LCP stage.

Conditions: Occurs when the protocol pppovlan command is configured on ATM subinterface along with no ip cef. PPPoE sessions are not created.

Workaround: Use the ip cef command.

CSCsv21295

Symptoms: Due to TestLoopback diagnostic failure on RSP supervisor, the interface is placed to err-disable state.

Conditions: This is seen when the interface is configured as RJ45 and with speed between 10 to 100mbps.

Workaround: Configure the speed on RJ45 interface "auto" negotiation and execute the diagnostic test TestLoopback to get the port out of err-disable.

CSCsv21403

Symptoms: Traffic is not passed through an Ethernet Virtual Circuit (EVC) service instance.

Conditions: Occurs after configuring EVC (Ethernet Virtual Circuit) service instance. The show platform efp-client command shows no output.

Workaround: There is no workaround.

CSCsv22930

Symptoms: When traffic engineering (TE) and fast reroute (FRR) is configured between the stitching router and provider edge (PE), traffic fails.

Conditions: Occurs when pseudowire stitching is configured.

Workaround: Do not enable FRR between these routers.

CSCsv23252

Symptoms: A Cisco 7600 running Virtual Private LAN Services (VPLS) with QinQ tunnels is forwarding CDP/VTP packets from the tunnel interfaces across remote sites, even when L2TP is not enabled.

Conditions: Occurs with a VPLS setup with QinQ tunnel interfaces facing the customer edge.

Workaround: Use different domain names to avoid changes to VTP database.

CSCsv24179

Symptoms: Protocol Independent Multicast (PIM) neighborship is not established with SIP600 over R-VPLS.

Conditions: Occurs when more than one VC on different VLANs exists with SIP600 links as core-facing and one of the VLANs configured with PIM.

Workaround: There is no workaround.

CSCsv24908

Symptoms: Layer 2 forwarding on other modules breaks when SIP-400 interface running eBGP and GRE flaps

Conditions: Occurs on a SIP-400 with SPA-2X1GE running BGP and GRE tunnels. Interface flaps on other modules are unable to resolve ARP or maintain routing neighbors. Issue seen on Supervisor 720 and Cisco 6748 CFC ports.

Workaround: Reload the chassis.

CSCsv25306

Symptoms: OSPF between two customer sites over H-VPLS network with SIP600 as core facing card in the hub router fails to come up.

Conditions: This is seen with traffic engineering (TE) and fast reroute (FRR) TE/FRR setup in the hub, and when TE tunnels have dynamic path option set.

Workaround: Perform a shut/no shut on the core-facing SIP600 interface.

CSCsv27428

Symptoms: TCP sessions passing through a NAT router freeze.

Conditions: The NAT router is a Cisco 7600 with RSP720. NAT translation entries keep using syn-timeout (default = 60 sec) even after TCP three-way handshake is done. Use show ip nat translation verbose to check timer

Workaround: Use the ip nat translation syn-timeout command, which mitigates the problem to some extent.

CSCsv27617

Symptoms: After reloading, NetFlow stops working and the output of show ip interface shows "IP Routed Flow creation is disabled in netflow table"

Conditions: This condition is seen on WAN main interfaces of a Cisco 7600 running Cisco IOS Release 12.2(33)SRB3 and can also be seen on Cisco IOS Release 12.2(33)SRC2.

Workaround: Remove and reconfigure NetFlow on the affected interfaces.

CSCsv28451

Symptoms: A Cisco 7600 PE router fails to redistribute a VRF prefix into BGP after the prefix or path to it flaps. The PE router will indicate the prefix being redistributed into BGP but the prefix will not get installed into the BGP table until the prefix is cleared:

E2#sh ip route vrf foo 10.5.5.5
Routing Table: foo Routing entry for 10.5.5.5/32 Known via "ospf 1", distance 110, 
metric 20, type extern 2, forward metric 10 Redistributing via bgp 666 Advertised by 
bgp 666 metric 10 match internal external 1 & 2 Last update from 10.45.45.2 on 
Ethernet1/0, 00:00:56 ago Routing Descriptor Blocks: * 10.45.45.2, from 10.5.5.5, 
00:00:56 ago, via Ethernet1/0 Route metric is 20, traffic share count is 1 PE2# PE2#sh 
ip bgp vpnv4 vrf foo 10.5.5.5 % Network not in table PE2#

Conditions: The PE router redistributing the given prefix must have a sham-link configured for the given VRF and an alternate path to the prefix must exist once the primary (sham-link) is down.

Workaround: Use the following command: clear ip route vrf vrfname <prefix>.

Further Problem Description: This problem is seen only in Cisco IOS Release 12.2(33)SRB. Cisco IOS Releases 12.2(33)SRC/SRD, etc. are not affected.

CSCsv29659

Symptoms: RP configured inside a NAT not shown on test device outside the NAT.

Conditions: Entering the show ip pim rp mapping command fails to display the RP.

Workaround: There is no workaround.

CSCsv30307

Symptoms: ISSU does not work from Cisco IOS Release 12.2(33)SRD to Cisco IOS Release 12.2(33)SRB5.

Conditions: When ISSU is performed from Cisco IOS Release 12.2(33)SRD image to 12.2(33)SRB5 image, ISSU is not working because of a default command introduced in 12.2(33)SRD.

Workaround: There is no workaround.

CSCsv30540

Symptoms: The error message %SYS-2-CHUNKBOUNDSIB and traceback are seen.

Conditions: The symptoms are observed when the show running- config/write memory command is issued.

Workaround: There is no workaround.

CSCsv33977

Symptoms: BGP peer fails to exchange the OPEN Message for negotiating capability when the neighbor router does not support any BGP capabilities.

Conditions: The symptom is observed when the neighbor router does not support any BGP capabilities and when the capability negotiation fails due to an SSO switchover.

Workaround: Configure "neighbor x.x.x.x dont-capability-negotiate". Issue the clear ip bgp * command when the issue occurs.

CSCsv35120

Symptoms: The ES20-GE3C/GE3CXL line card may crash if the explicit-path of an MPLS Traffic Engineering (TE) tunnel is changed so that it no longer goes out a core-facing port-channel interface.

Conditions: Seen only when the following conditions are met:

- Virtual Private LAN Services (VPLS) traffic passes over the MPLS Traffic Engineering tunnel.

- Traffic going out the tunnel initially goes over a port-channel interface.

- Five or more ports on the ES20 line card are used in the port-channel interface.

- The explicit-path specified avoids the port-channel interface

Workaround: Shut down the port-channel interface first before changing the tunnel's explicit-path.

CSCsv36266

Symptoms: E1 and SonetVT layers are down even though serial (Upper Layer) ifOperStatus is UP

Serial1/0/0.1/2/1/1:1 ifOperStatus.156 = up(1)

E1 1/0/0.1/2/1/1 ifOperStatus.157 = lowerLayerDown(7

TU 1/0/0.1/2/1/1 ifOperStatus.158 = down(2)

tug 3-2 tug 2-1 e1-1:chgrp1

AU-4 1, TUG-3 2, TUG-2 1, E1 1 (C-12 1/2/1/1) is up

156 Se1/0/0.1/2/1/1:11500512KUP UP

157 E1 1/0/0.1/2/1/102.05MUP <blank>

158 TU 1/0/0.1/2/1/102.05MUP down

Conditions: Occurs on serial interfaces of SPA-1XCHSTM1/OC3.

Workaround: There is no workaround.

CSCsv36892

Symptoms: TCLsh mode is not exited when the session is disconnected or times out. The next user to connect and authenticate is put in TCLsh mode.

Conditions: Occurs on high availability systems with an active and standby RP.

Workaround: Explicitly exit TCLsh mode rather than disconnecting or allowing the session to time out.

CSCsv38166

The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.

The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.

This vulnerability does not apply to the Cisco IOS SCP client feature.

Cisco has released free software updates that address this vulnerability.

There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.

This advisory is posted at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.

CSCsv41886

Symptoms: Entering the no ip routing or no router bgp xx command yields the following error message:

%IPRT-3-IPDB_DEL_ERROR: i_pdb delete error bgp, 4, 210074C8, 20E322E0, 0, 0 -Process= 
"IP RIB Update", ipl= 0, pid= 117, -Traceback= 0x61FD7F58 0x62005498 0x62006D24

Conditions: Occurs when a large number of VRFs must be configured and BGP is also configured to support these VRFs, then a show command, such as show run, is issued shortly after the no ip routing or no router bgp command.

Workaround: There is no workaround.

CSCsv42176

Symptoms: Router reloads, and the following error is displayed:

SP: MACSEC: Assert failure: mat_rc >= BD_MAT_RET_SUCCESS

Conditions: Occurs when, for a given service instance, a secure entry is removed with mac security aging inactivity configured and mac security configured.

This can occur through the CLI via a command like clear ethernet service instance id id interface interface id mac table, or it can occur due to EFP shutdown.

If this occurs at the same time that the entry's aging timer expires, the reload may occur.

Workaround: There is no workaround if "aging inactivity" is required. This problem will not occur if mac security aging inactivity is not configured.

CSCsv48296

Symptoms: The router reloads with the following error:

SYS-6-BLKINFO: Corrupted redzone blk

Conditions: Occurs when the cns image is active, and a CNS image operation is in progress.

Workaround: There is no workaround.

CSCsv50159

Symptoms: Spurious access or crash seen on a router with a CEoP SPA, when bulk sync happens between RP and RPR.

Conditions: Occurs during regular bootup.

Workaround: There is no workaround.

CSCsv50606

Symptoms: Subsequent software releases are not backward compatible with Cisco IOS Release 12.2(33)SXI when performing an ISSU upgrade.

Conditions: Occurs with versions of Cisco IOS that are released after Cisco IOS Release 12.2(33)SXI.

Workaround: Instead of ISSU upgrade or downgrade, perform a regular image upgrade or downgrade.

CSCsv57587

Symptoms: After online insertion and removal (OIR) of the SPA or line card holding the active Automatic Protection Switching (APS) interface, there are two active interfaces for the same APS group. During OIR, the old inactive interface becomes active and the OIRed interface also comes back up as active. The OIR interface should come up as inactive.

Conditions: The problem is seen only on ATM SPAs and is seen with both SR-APS and MR-APS configurations.

Workaround: In the case of a manual OIR, this can be prevented by entering the force APS switchover command before performing an OIR on the active.

When OIR happens due to other reasons and the problem is seen, perform a shut/no shut on one of the interface.

CSCsv59031

Symptoms: SIP-400 crashes on RADIUS CoA push with Cisco Intelligent Services Gateway (ISG).

Conditions: Occurs on a SIP-400 configured for IP/PPPoE sessions and ACL configuration push from other router.

Workaround: There is no workaround.

CSCsv62150

Symptoms: When cbgpPeerCapsTable is queried, it does not return the results of VPNv4 neighbors.

Conditions: Configuration should have VPNv4 neighbors.

Workaround: There is no workaround.

CSCsv63799

Symptoms: A router may reload if PfR is enabled and the number of flows exceeds the size of the NetFlow cache. This is a stress condition.

Conditions: This symptom is observed when PfR is enabled (which also enables NetFlow).

Workaround: A possible workaround is to configure the following:

ip flow-cache timeout active 1

CSCsv66827

Symptoms: Clearing the SSH sessions from a VTY session may cause the router to crash.

Conditions: The symptom is observed when a Cisco 7300 series router is configured for SSH and then an SSH session is connected. If the SSH session is cleared every two seconds using a script, the symptom is observed.

Workaround: There is no workaround.

CSCsv73388

Symptoms: "Circuit-id-tag" and "remote-id-tag" attributes may be duplicated in packets sent to the RADIUS server.

Conditions: The symptom is observed with Cisco IOS Release 12.2(31)SB13.

Workaround: Use Cisco IOS Release 12.2(31)SB14.

CSCsv73509

Symptoms: When "no aaa new-model" is configured, authentication happens through the local even when tacacs is configured. This happens for the exec users under vty configuration.

Conditions: Configure "no aaa new-model", configure login local under line vty 0 4 and configure login tacacs under line vty 0 4.

Workaround: There is no workaround.

CSCsv73735

Symptoms: After performing a redundancy switchover (RPR+ mode), the ARP table is not correctly populated. Entering the clear ip arp or the clear arp-cache commands, then pinging the connected CE or PE causes an incomplete entry to be added to the ARP table.

Conditions: This is seen on Gigabit Ethernet, FastEthernet and POS interfaces. ATM and serial interfaces seem do not appear to be affected. This behavior is not seen with stateful switchover (SSO).

Workaround: There is no workaround.

CSCsv73754

Symptoms: A Cisco 10000 series router crashes. Traceback decode points to a function of bgp_vpn_impq_add_vrfs_cfg_changes.

Conditions: The symptom is observed while unconfiguring VRFs. It is most likely to be seen when 100 VRFs or more are unconfigured.

Workaround: There is no workaround.

CSCsv79584

Symptoms: An 0.0.0.0 binding with a 0 minute lease gets created and subsequently removed on the DHCP unnumbered relay.

Conditions: The DHCP client sends a DHCPINFORM with ciaddr set to its address, but giaddr is empty. The relay fills in giaddr with its IP address and the server replies to giaddr. Since the DHCPACK is in response to DHCPINFOM, the lease-time option is absent. Relay receives the DHCPACK and tries to process it normally leading to the route addition.

Workaround: There is no workaround.

Further Problem Description: This behavior can indirectly have a negative impact on the system by triggering other applications to be called because the routing table change is triggered by such DHCP requests. Examining "debug ip routing" for 0.0.0.0/32 reveals 0.0.0.0/32 route flapping.

CSCsv79673

Symptoms: Unicast flooding occurs for all traffic destined to VLAN SVI. MAC address for the VLAN SVI is being learned dynamically.

Conditions: Changing the VLAN SVI configuration from IP to XCONNECT and back without shutting down the interface will result in the router MAC being learned dynamically instead of being installed as static. Normal aging occurs on the dynamic MAC, resulting in unicast flooding if the MAC is removed from the MAC address table.

Workaround: Perform a shut/no shut on the affected VLAN SVI.

CSCsv79993

Symptoms: A Cisco 7600 may crash when a distribute-list is deleted.

Conditions: Crash occurs when removing a distribute-list from EIGRP. The distribute-list was one of many that was sharing the same route-map and access-list. The crash only happens when multiple protocols have the same direction distribute-list configured on the same interface, as in the following example:

router eigrp 10

network 10.0.0.0

distribute-list 49 out Ethernet1/2.10

router rip

network 10.0.0.0

default-metric 2

distribute-list 49 out Ethernet1/2.10

Workaround: There is no workaround.

CSCsv80014

Symptoms: When doing an SNMP walk on OLD-CISCO-IP-MIB when the routing table has several thousand prefixes, excessive CPU utilization occurs.

Conditions: The symptoms are seen only when there are several thousand prefixes in the routing table.

Workaround: Exclude the OLD-CISCO-IP-MIB from the SNMP walk. This MIB has been deprecated.

CSCsv81009

Symptoms: Intermittent traffic loss occurs on switch virtual interface (SVI) enabled with Virtual Router Redundancy Protocol (VRRP). Cannot ping VRRP IP address.

Conditions: Occurs with VRRP configured on SVI. Traffic loss/ping VRRP IP address failure seen sometimes on bootup.

Workaround: If VRRP mac-address is present as dynamic entry on bootup, this issue can be seen. Reconfigure VRRP as a workaround.

CSCsv81751

Symptoms: Cisco 7200 G2 router crashes when changing configuration of serial interfaces from PPP to SDLC and back to PPP, while running traffic.

Conditions: This is observed on a T3 link with 56 channel groups configured on a WAN aggregation device. All the serial interfaces have service-policy configured.

Workaround: Remove the service-policy before changing the encapsulation to SDLC.

CSCsv85530

Symptoms: When accounting is enabled for virtual private dial-up network (VPDN), there might be messages with termination cause "nas-error" and displaying impossible values in Acct-Input-Octets, Acct-Output-Octets, Acct-Input-Packets and Acct-Output-Packets.

This causes accounting to be unreliable.

Conditions: Occurs with Cisco IOS Release 12.4T and configured for PPTP/L2TP with accounting.

Workaround: There is no workaround.

CSCsv85990

Symptoms: If there are multiple EFPs with, for example encapsulation 100, same encapsulation on different interfaces and with different bridge-domains configured for Virtual Private LAN Services (VPLS), then if there is a topology change notification (TCN) received on one of the Ethernet Flow Points (EFPs) on one interface, then Label Distribution Protocol (LDP) MAC address withdrawals are sent for all the bridge domains on all the interfaces.

Conditions: Occurs when the network has EVCs on the L2-Access forwarding to VPLS core. Multiple Spanning Tree (MST) is running on the access VLANs.

Workaround: There is no workaround.

CSCsv86256

Symptoms: In the pseudowire stitching configuration, if fast reroute (FRR) is enabled for link or node protection at the tunnel stitching router, then end-to-end connectivity is broken.

Conditions: Problem happens only if a Cisco 7600 is the stitching-point router and has MPLS Fast Reroute enabled.

Workaround: Disable FRR at the stitching point.

CSCsv86288

Symptoms: Sending a NETCONF hello reply which contains a "session-id" element triggers an instant crash. The device will report a reload due to a bus error.

Conditions: This occurs when sending a hello reply which contains a session-id element. A hello without this element, one which only contains NETCONF capabilities, does not cause a crash.

Workaround: Send a NETCONF hello without a session-id element.

CSCsv89643

Symptoms: If Ethernet interface configured as Open Shortest Path First (OSPF) point-to-point network then adjacency is being established using only multicast packets. As a result routes calculated over the link do not have MAC address of next-hop's IP resolved prior to routes being installed into the routing table. This leads to delay for routes to become usable as lower-level protocols have to trigger MAC resolution. During short period of time traffic sent over the interface is lost when routes are just installed for the first time.

Conditions: Occurs when Ethernet interface is configured for OSPF point-to-point.

Workaround: Problem will self-correct because passing traffic triggers MAC address resolution.

CSCsv90323

Symptoms: ISSU upgrade to Cisco IOS Release 12.2(33)SRD did not put router into route processor redundancy (RPR) mode.

Conditions: Occurs when no service image-version efsu is enabled. During ISSU upgrade from Cisco IOS Release 12.2(33)SRB or SRC to Cisco IOS Release 12.2(33)SRD, the router incorrectly goes into stateful switchover (SSO). The correct mode is RPR because SSO ISSU from these releases to Cisco IOS Release 12.2(33)SRD is not supported.

Workaround: Remove the no service image-version efsu configuration by the default service image-version efsu and continue the upgrade process.

Further Problem Description: If any of the following Config, Exec or ROMMON variables are set, the SSO-based ISSU will not be blocked:

Config:

"no service image-version efsu",

"no service image-version compatibility",

Exec:

"issu image-version compatibility disable",

ROMMON variable:

RED_MODE = "RPR_PLUS'

RED_MODE_SSO

RF_REDUN_COMP = 1

When performing any ISSU upgrade from SRB/SRC to SRD, make sure none of the above overrides is set on the router. The service image-version efsu command detects the incompatibility and puts the router in RPR mode.

CSCsv91602

Symptoms: Cisco 7201 with Gi0/3 experienced communication failure.

Conditions: This problem does not occur with Gi0/0 or Gi0/2.

Workaround: Perform a shut/no shut on the Gi0/3. The problem will occur again.

CSCsv92088

Symptoms: BACKPLANE_BUS_ASIC-4-DEV_RESET error interrupts generated by SIP-400 module, causing traffic interruption.

Conditions: Occurs when PPPoE traffic ingresses a SIP-400 line card on a Cisco 7600 Series router running Cisco IOS Release 12.2SR.

Workaround: There is no workaround.

CSCsv94471

Conditions: On an ES-20, sometimes the interface configured as a promiscuous port does not forward the traffic to other community and isolated ports on the same private VLAN. The traffic on the promiscuous port is forwarded to all other community and isolated ports belonging to the same private VLAN. This is the expected behavior.

Condition: Sometimes using the CLI on the interface configured in the promiscuous mode switchport mode private-vlan promiscuous after switchport private-vlan mapping <primary vlan> <secondary vlans> can cause traffic to be dropped. The order of these CLIs should not matter.

Workaround: There is no workaround.

CSCsv97273

Symptoms: The SP crashes when the device receives an IP address from the DHCP server. The following error message is displayed:

Signal = 11 Vector = 0x1400

Conditions: Occurs on a Cisco Catalyst 6500 with RSP720-3C-GE when the ip verify source vlan dhcp-snooping is enabled.

Workaround: There is no workaround.

CSCsv99716

Symptoms: A Cisco 10000 series router may crash at issu_print_memory while doing a loadversion.

Conditions: The symptom is observed on a Cisco platform, when enabling the debug command debug issu all in the router and doing a loadversion.

Workaround: Do not turn on ISSU debug.

CSCsw14845

Symptoms: An access-list with multiple ports in a single entry only programs the first port into TCAM. All subsequent ports are not processed according to the access-list entry.

For example, the following access-list should block both SSH (TCP port 22) and Telnet (TCP port 23), but Telnet is permitted.

ip access-list extended deny_ssh_and_telnet deny tcp any any eq 22 telnet permit ip 
any any

Conditions: Occurs when there is an extended named access-list with multiple ports in a single access-list entry. This only applies to transit traffic since traffic destined to the router is process-switched and processed in software.

Workaround: There is no workaround.

CSCsw16698

Symptoms: New DHCP clients are not able to get IP address from DHCP server via DHCP relay on the router. Existing clients are unable to renew their IP addresses

Other Symptoms:

1.1 When we're trying to display DHCP bindings with "show ip dhcp binding" command the following message is observed:

% The DHCP database could not be locked. Please retry the command later.

1.2 Command "ip dhcp database" disappeared from the running configuration.

1.3 Output of "show run" is delayed.

1.4 Output of "debug ip dhcp events" show the following when a new DHCP packet is received:

DHCPD: dhcpd_receive_packet: unable to lock semaphore to check for pre-existing bindings could not lock se. DHCPD: dhcpd_timer_process could not lock semaphore. DHCPD: dhcp_server_receive could not lock semaphore.

2.1. This bug may also cause DHCP Snooping failure. In this case, the output of the show ip dhcp snooping database command constantly shows these lines:

Agent Running : Yes Delay Timer Expiry : 0 (00:00:00) Abort Timer Expiry : Not Running

Conditions: Occurs when DHCP and/or DHCP Snooping database agent is configured to store bindings on a TFTP server, and then the database files are not present or are read-only for some time on TFTP server while the router tries to write to them.

Workaround: Before the issue occurs, there are three known alternatives to avoid this problem:

1. Either configure "length 0" for line console 0;

2. Or - log in via console at least once since router startup;

3. Or - use Cisco IOS Release 12.2(33)SRD but do not enable "debug tftp packet".

To fix the issue after it has occurred, connect to the router via console, press space bar to get rid of "--More--" prompt, then press enter to log in

CSCsw24542

Symptoms: A router may crash due to a bus error after displaying the following error messages:

%DATACORRUPTION-1-DATAINCONSISTENCY: copy error, %ALIGN-1-FATAL: Illegal access to a 
low address < isdn function decoded>

Conditions: The symptom is observed on a Cisco 3825 router that is running Cisco IOS Release 12.4(22)T with ISDN connections.

Workaround: There is no workaround.

Further Problem Description: When copying the ISDN incoming call number for an incoming call from Layer2, the length of the call number was somehow exceeding the maximum allocated buffer size (80). PBX has pumped a Layer2 information frame with call number exceeding the maximum number length limit. It leads to memory corruption and a crash.

CSCsw24611

Symptoms: A router configured with BGP and VPN import may crash.

Conditions: This is a hard to hit race condition. BGP imports a path from VRF-A to VRF-B. The following steps have to take place in exactly this order for the crash to occur: 1. The next-hop for the path has to become unreachable. 2. BGP has to re-evaluate the bestpath on the net in VRF-A and result in no-bestpath on the net (because there is no alternative path available). 3. RIB installation has to process the importing BGP net under VRF-B.

Step 3 will result in the crash. If, before step 3, the next-hop re-evaluation manages to process the net in VRF-B then it will clear the bestpath and there will be no crash. If, before step 3, the import code gets a chance to process the net it will clean-up the imported path from VRF-B and then there will be no crash.

Workaround: There is no workaround.

CSCsw24826

Symptoms: Cisco router may crash pointing to OSPF code because of low memory access.

Conditions: Crash is specific to the following scenario:

1. Neighbor router performs IETF NSF restart.

2. Software interface between routers is removed from configuration when NSF restart is undergoing, when grace LSA is present in the database of the helper router.

3. Helper router will crash 1 hour later during max-age procedure for grace LSA. Reason is that grace LSA is associated with interface, but that interface does not exist any more.

Workaround: If configuration changes need to be done during network changes, the following applies:

1) Shutdown OSPF interface

2) Check show ip ospf da. Can you see type-9?

- NO => good, remove interface

- YES => 'no shutdown' interface, wait for neighbor going FULL (type-9 will be flushed during sync)

3) Repeat Step 1.

CSCsw25255

Symptoms: A Catalyst 6500 or Cisco 7600 router may not send back a BPDU with agreement flag in response to a proposal on its root port, causing slow convergence on the designated bridge.

Conditions: This is seen on Catalyst 6500 switches running any version of Cisco IOS Release 12.2(33)SXH. This is seen on Cisco 7600 routers running any version of Cisco IOS Release 12.2SR.

Workaround: The problem does not occur if debug spanning-tree event is enabled. This can be a suitable workaround in an environment with a small number of VLANs if the debug does not impact CPU usage.

CSCsw28082

Symptoms: SNMP messages are not seen.

Conditions: When the BRI interface is down on a remote router, and no ppp link reset is configured on device, SNMP trap message shows "down" instead of "keepalive failed".

Workaround: There is no workaround.

CSCsw28139

Symptoms: PBR stops working after stateful switchover (SSO). All traffic that should be policy routed is dropped instead.

Conditions: This usually happens after several switchovers between supervisors. Usually problem occur after about 10 switchovers, however, it could happen after first one.

Workaround: Remove and add policy on the interface.

CSCsw31019

Symptoms: A Cisco router crashes.

Conditions: This symptom is observed if the frame-relay be 1 command is issued under "map-class frame-relay <name>" configuration.

Workaround: There is no workaround.

CSCsw35155

Symptoms: When using denies in ACLs in crypto maps, the VPN SPA or VPN SM crashes.

Conditions: Occurs when configuration uses denies in ACLs with crypto maps that causes too many entries in the Ternary Content Addressable Memory (TCAM).

Workaround: Enter the crypto ipsec ipv4 deny clear command.

CSCsw35638

Symptoms: When a Cisco router is the Merge Point (MP) for a protected TE tunnel, and FRR is triggered, two things happen:

- The primary LSP goes down, and traffic is lost on the protected tunnel. - Any PLR that is downstream of the failure will lose its backup.

Conditions: When a competitor's router is a point of local repair (PLR) and a Cisco router is a merge point, then when FRR is triggered, the Cisco router drops the backup tunnel (in some cases immediately and in other cases after 3 minutes). This causes the primary tunnel that is protected by this backup to go down. The issue has been identified as related to the fact that session attribute flags (link/node protection desired) are being cleared by the competitor PLR when the Path is sent over the backup tunnel.

Workaround: There is no workaround.

CSCsw36285

Symptoms: The show policy-map interface command yields incorrect policer information.

Conditions: This problem affects only the reporting of policing statistics. It does not affect policer functionality. When police action is configured in a service-policy, the conformed rate displayed in show policy-map interface does not match with the class-map offered rate.

Workaround: There is no workaround.

CSCsw36872

Symptoms: VPN-NUM in VLAN-RAM TCAM wrongly provisioned after reconfiguration of Layer 3 port-channel. This changes member link mapping, and VRF membership changes on Layer 3 port-channel. Also discrepancy in L3MGR info between RP and SP for affected port-channel/internal vlan representation observed.

Conditions: When the command channel-group <number> mode active is configured on the member link before the respective Port-channel is configured, this causes the member link interface to go admin down. When the port-channel is configured, the port-channel first comes up and then the member link. This may cause the port-channel to take up the same VLAN which was previously assigned to the member link. If this happens, the symptom is seen.

Workaround: One workaround is to configure the port-channel first and then activate the channel-group on the member link interface. Another workaround is to create a dummy interface so that it takes up the member link's previous VLAN and the port-channel will be assigned a new one, in which case this problem is not seen.

CSCsw37053

Symptoms: Traffic with aggregate label was forwarded in wrong VPN, causing the mis-forwarding, as the IP prefix was not present in the VPN routing/forwarding (VRF) table.

Conditions: Occurs under the following scenario:

1. Aggregate label should not be using the VPN CAM.

2. The recirculation VLAN has the wrong VPN number.

Workaround: Manually correct the wrong mls vlan-ram entry.

Further Problem Description: If there are multiple aggregate labels on a given VRF, there might be a chance of seeing this issue.

CSCsw37635

Symptoms: A Cisco 10000 series router may crash at issu_print_memory while doing a loadversion.

Conditions: The active router crashes when doing load version with "debug issu all" turned on.

Workaround: Do not turn on ISSU debug.

CSCsw43211

Symptoms: Following errors are seen:

%IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: 0xFFFFFFFF) -Traceback= 
60476EBC 60477400 60491664 616C5834 616C7EEC 61AB72CC 61AC2E64 61AC2EBC 60FE4274 
60FDEFA4 60FD4180 60FD4874 60FD4BBC 60FD275C 60FD27A0 60FC8F74

Conditions: This has been seen on a Cisco 7200 after upgrading to Cisco IOS Release 12.2(33)SRC2.

Workaround: There is no workaround.

CSCsw43272

Symptoms: The VPDN user does not take LNS-assigned IP addresses when using the DHCP pool.

Conditions: The symptom is observed whenever the DHCP server is unavailable or when the DHCP pool is exhausted.

Workaround: Use IP pool instead of DHCP pool.

CSCsw43499

Symptoms: Accounting start sent on DHCP OFFER rather than ACK.

Conditions: This issue can cause accounting irregularities if the DHCP process does not complete. For example, with active-active Cisco Intelligent Services Gateway (ISG) redundancy, two DHCP OFFERs will be sent, but only one will be accepted. Since accounting records are generated for both OFFERs, they will be duplicates of each other.

Workaround: There is no workaround.

CSCsw43948

Symptoms: A Cisco 3845 router that is running Cisco IOS Release 12.4(13) may bounce the frames (which are not destined for itself) on the same interface that receives them.

Conditions: The symptom is observed if there is bridging configured on an ethernet subinterface in the following way:

ip cef ! bridge irb ! interface GigabitEthernet0/1 no ip address no sh ! ! interface 
GigabitEthernet0/1.100 encapsulation dot1Q 100 ip address x.x.x.x x.x.x.x no ip 
redirects no ip unreachables no ip proxy-arp ip rip advertise 10 ! interface 
GigabitEthernet0/1.509 encapsulation dot1Q 101 bridge-group 1

Workaround: If the command bridge-group 1 is removed from the sub-interface, it will behave as expected.

CSCsw47475

Symptoms: Cisco 7600 router has multiple E1s that randomly flap.

Conditions: Occurs on a router with RSP720, SIP-200 and 8xCHT1/E1 SPA installed.

Workaround: There is no workaround.

CSCsw50608

Symptoms: With the traffic flowing between a promiscuous port and a port belonging to a community VLAN of the same primary VLAN, if the user adds or removes any other secondary VLAN under the same private VLAN using the following configuration under "int gi" for the promiscuous port.

Conditions: The issue was seen upon using the following CLI on the interface configured in the promiscuous mode.

switchport private-vlan mappingprimary-vlan add/removesecondary-vlan.

Workaround: There is no workaround.

CSCsw52698

Symptoms: The following error message is displayed:

%BACKPLANE_BUS_ASIC-4-DEV_RESET: Backplane Bus Asic reset, interrupt [0x062D]=0x0008

Conditions: Symptom reported by 7600-SIP-400 cards on 7600 Series Routers when PPPoE connections are terminated via the 7600-SIP-400 cards.

Workaround: There is no workaround.

CSCsw53404

Symptoms: FR-FR and FR-Ethernet connections configured for anything over MPLS (AToM) interworking do not work with the combination of SIP400 and channelized SPAs.

Conditions: Occurs with Frame Relay AToM configurations with SIP400 and channelized SPAs.

Workaround: There is no workaround.

CSCsw62346

Symptoms: When unsupported filter is added to global policy-map with only match-any as the filter, the router or line card might crash.

Conditions: Occurs when global policy map is attached to an interface.

Workaround: Detach service policy from interface before making changes.

CSCsw63003

Symptoms: Memory leak occurs in "BGP Router" process. Memory used by this process increase every day while the number of routes is not increasing.

Conditions: This occurs on a provider edge (PE) router running Cisco IOS Release 12.2(31)SB or 12.2(33)SB. Problem is seen when VPN routing/forwarding (VRF) is showing important BGP activity.

Workaround: Reload the router to avoid reaching low memory conditions.

CSCsw64270

Symptoms: Traffic may stop flowing on a T1 interface configured with Frame-relay encapsulation on online insertion and removal (OIR) of the SIP-400.

Conditions: The problem was observed on a Cisco 7600 router with Sup720 and SPA-1XCHOC12/DS0 installed in a SIP-400. The traffic may not recover on a T1 interface configured for Frame-relay encapsulation after an OIR of the SIP-400.

Workaround: Perform a software reset of the SIP-400 or reload of the router.

CSCsw69366

Symptoms: When sending packets that exceed specified MTU, packets are received as giants in PA-T1/E1 IMA card instead of being fragmented.

Conditions: It happens only after changing sub-interface MTU and after stateful switchover (SSO).

Workaround: Perform a shut/no shut on the main interface.

CSCsw70125

Symptoms: A Cisco 7600 SIP-400 with POS interfaces encapsulated with IETF frame-relay may incorrectly set 0x800 as Network Layer Protocol Identifier (NLPID) for hardware assisted multicast IP packets. The correct value is 0xCC.

Conditions:

A. IP unicast packets in hardware path do not have this problem.

B. IP multicast or unicast packets in software path do not have this problem.

C. Problem reproducible in Cisco IOS Release 12.2(33)SRA2, 12.2(33)SRA7, and 12.2(33)SRC2.

Workaround: There is no workaround.

CSCsw71208

Symptoms: Cisco 7600 does not respond properly to Link Control Protocol (LCP) echo requests, causing PPP sessions to renegotiate between the router and non-Cisco devices.

Conditions: Occurs on a Cisco 7600 running Cisco IOS Release 12.2(33)SRC2.

Workaround: Disable keep-alives on the non-Cisco device.

CSCsw72677

Symptoms: Router crashes with "no bba-group pppoe".

Condition: Happens after unconfiguring "bba-group".

Workaround: There is no workaround.

CSCsw73863

Symptoms: IDs allocated from DHCP are leaked, causing the device to reload.

Conditions: Device is configured as Cisco Intelligent Services Gateway (ISG) DHCP with 24000 sessions flapping every 10-12 minutes.

Workaround: There is no workaround.

CSCsw73956

Symptoms: During health monitor failure, platform action was taken immediately but platform action should be taken from gold TCL policy.

Conditions: Occurs when health monitor test failure crosses failure threshold.

Workaround: There is no workaround.

CSCsw75589

Symptoms: If you have configured Netflow and also have "ip flow-cache mpls label-positions", you are very likely to run in a bus error crash with info similar to what is seen here:

%ALIGN-1-FATAL: Illegal access to a low address 10:28:28 UTC Sat Dec 20 2008 
addr=0x1E, pc=0x61CB7180, ra=0x61CBA5C0, sp=0x65BCAF20
%ALIGN-1-FATAL: Illegal access to a low address 10:28:28 UTC Sat Dec 20 2008 
addr=0x1E, pc=0x61CB7180, ra=0x61CBA5C0, sp=0x65BCAF20
10:28:28 UTC Sat Dec 20 2008: TLB (store) exception, CPU signal 10, PC = 0x61CB7180

Conditions: Problem is platform independent but specific to IOS release. This problem is seen in 12.2(33)SRC1 and possibly affects 12.4T releases as well.

Workaround: Consider removing MPLS netflow configuration by removing the ip flow-cache mpls label-postion 1 command.

CSCsw76113

Symptoms: Unable to reuse a sub-interface as main-interface.

Conditions: Occurs when we configure no virtual-template subinterface when all of the Interface Descriptor Blocks (IDB) that platform supports are used as "subif-vaccess". No more "vaccess" can be created.

Workaround: Do not configure no virtual-template subinterface at run time. Check show vtemplate output. If there are more IDBs used by subinterface, then do not configure no virtual-template subinterface.

CSCsw76910

Symptoms: Supervisor reloads on configuring or verifying firewall farm commands.

Conditions: Occurs before and after compliance testing on the firewall farm commands.

Workaround: There is no workaround.

CSCsw77205

Symptoms: ES20 line cards crashing in a loop while using a anything over MPLS (AToM) VC with Cisco Intelligent Services Gateway (ISG).

Conditions: The issue is seen on all the ES20 cards installed in a Cisco 7609 router running Cisco IOS Release 12.2(33)SRC2.

Workaround: Manually shutdown the AToM interfaces and ISG interfaces to stop the crashes.

CSCsw78413

Symptoms: The BFD configuration may be lost from the interface/sub-interface upon a router reload or physical module of OIR.

Conditions: The symptom is seen when BFD is configured on an interface in certain multi-slot chassis.

Workaround: Ethernet interfaces seem immune to this problem. Certain platforms, such as the Cisco 10000 series router, are also immune.

CSCsw78939

Symptoms: No new sessions can come up using VPDN after a few days.

Conditions: The root cause is that we leak and run out of SSM switch IDs.

Workaround: There is no workaround.

CSCsw81485

Symptoms: Issuing no form of IPX configuration commands on an interface crashes the switch.

Conditions: Occurs when IPX routing is enabled on the device but not on the interface.

Workaround: Do not issue no form of IPX configuration commands on an interface where IPX is not enabled.

CSCsw82462

Symptoms: A connected prefix from the global routing table has a VPN routing/forwarding (VRF) interface as outgoing interface.

Conditions: This condition occurs after a clear ip route x.x.x.x for the prefix x.x.x.x.

Workaround: Shut the VRF interface, clear the prefix from the routing table, then no shut the VRF interface.

CSCsw82507

Symptoms: DPM on secondary Cisco Intelligent Services Gateway (ISG) does not clear its session despite the fact that a DHCP termination message is sent. Even though the binding is cleared, the session persists until the idle timeout expires or the session is manually cleared.

Conditions: Occurs when multiple DHCP relay agents are present between clients and DHCP server.

Workaround: The session may expire due to idle timeout or be manually cleared.

CSCsw85986

Symptoms: Traffic through multilinks drop in one direction as some bundles show lost fragments, causing input errors to increment. The SPA receives the required sequence after long time from the line card, and time out is less in SPA.

Conditions: Problem is seen when there are more member links in a bundle on SPA-1xCHOC12/DS0 bidirectional traffic is sent. Some bundles drop packets at ingress as lost fragments in one direction.

Workaround: There is no workaround.

CSCsw88324

Symptoms: The ESM20G, 7600-ES20-GE3CXL, indicates Major error on show module.

Conditions: No special configuration conditions are needed to reproduce. The online diagnostics status indicates "Major Error". The major error can be observed following a forced switchover using the redundancy force-switchover command.

Workaround: No workaround known. Only reloading the router may cause the ESM20G to recover and pass online diagnostics.

CSCsw89574

Symptoms: Under certain circumstances when a route entry containing a repair path is updated or deleted, the repair path may not be properly removed. This may result in the repair path being orphaned in memory consuming a 60 byte memory block.

Conditions: Occurs with mVPN/TE and multicast enabled on a BGP speaking router. All images based on Cisco IOS Release 12.2(33)SR may be impacted by this problem.

Workaround: There is no workaround.

CSCsw89720

Symptoms: When we perform SNMP query (getmany) on cbQosPoliceStatsTable and cbQosREDClassStatsTable, CPU utilization reaches 99% with a single SSH session. If we query cbQosPoliceStatsTable and cbQosREDClassStatsTable from 18 SSH sessions, CPU-HOG error message are seen

Conditions: Occurs with a large number of policies defined on a GigE subinterface (~4k).

Workaround: No workaround, other than stopping the query.

CSCsw89962

Symptoms: Ping across CE routers fails.

Conditions: Occurs when "bidir" is configured.

Workaround: There is no workaround.

CSCsw90340

Symptoms: Traffic flows with loopback on a Cisco 7200 router.

Conditions: Occurs when you shut the controller, configure loopback, then no shut the controller.

Workaround: There is no workaround.

CSCsw90798

Symptoms: A Cisco switch may reload after a VLAN is renamed.

Conditions: Occurred on a Catalyst 6500 running Cisco IOS Release 12.2(33)SXH3a and Cisco IOS Release 12.2(33)SXH4.

Workaround: There is no workaround.

CSCsw91320

Symptoms: A crash occurs with the following footprint:

10:08:22 EST Mon Jan 26 2009: Address Error (store) exception, CPU signal 10, PC = 
0x4330E8E0
0x432DF9F0 ---> dlink_rmqueue+30 0x432DFAEC ---> dlink_dequeue+2C 0x40DF73BC ---> 
nrp_service_notification_queue+26C 0x40DF7D8C ---> network_redist_process+210

Conditions: Occurs when a multicast protocol is configured on at least one interface. Intermediate System-to-Intermediate System (IS-IS) is configured to run on one of the interfaces on which the multicast protocol is enabled. For example:

interface TenGigabitEthernet1/1 ip address 10.10.1.21 255.255.255.252 ip router isis ip pim sparse-mode

IS-IS interface configuration is removed from the interface on which the multicast protocol is configured. If a unicast route owned by IS-IS changes shortly after the multicast interface configuration is removed, the crash may occur.

Workaround: The following multicast configuration can be used to avoid the risk of a crash:

Router(config)#ip multicast rpf multitopology
Router(config)#global-address-family ipv4 multicast
Router(config-af)#topology base
Router(config-af-topology)#use unicast base 

CSCsw91422

Symptoms: Crash occurs on Cisco 7206VXR/NPE-G1 running Cisco IOS Release 12.2(31)SB12.

Conditions: Occurs under general use. No error messages appear in logs.

Workaround: There is no workaround.

CSCsw92379

Symptoms: Many "IP ARP: Sticky ARP entry invalidated" syslog messages appear, and the RP reloads unexpectedly.

Conditions: This symptom is observed when a linecard is swapped while thousands of DHCP snooping bindings are present and the ip sticky-arp command is configured.

Workaround: Configure the no ip sticky-arp command.

CSCsw96484

Symptoms: An interface that has been error disabled by an OAM remote link failure will not be recovered even if OAM link failure error disable recovery has been configured.

Conditions: Occurs when Ethernet OAM is configured on the interface and a remote failure is detected.

Workaround: Perform a shut/no shut on the interface.

CSCsw99846

Symptoms: With mLDP over a P2P tunnel, traffic drops in multiple cases.

Conditions: The traffic drops when there is a change in path set entries, which can happen when you perform a shut and no shut the TE tunnel or toggle MPLS traffic-tunnel or use the clear mpls traffic-eng auto-tunne command.

Workaround: There is no workaround.

CSCsx05672

Symptoms: High CPU utilization occurs on the new active supervisor after a stateful switchover (SSO).

Conditions: Occurs when large numbers of logical interfaces (such as port-channel sub-interfaces or interface VLANs) are configured and earl policing policies applied (uflow policing or aggregate policing) on all the logical interfaces. The CPU utilization on the active supervisor aggravates on each switchover.

Workaround: There is no workaround.

CSCsx06457

Symptoms: A router configured with BGP may generate IPRT-3-NDB_STATE_ERROR log messages. An additional symptom when bgp suppress-inactive is configured is that the router CPU usage may get close to 100%.

Conditions: When both BGP and an IGP are advertising the same prefix, the error condition may occur. When in addition bgp suppress-inactive is configured high CPU usage by BGP may be seen.

Workaround: Removing the bgp suppress-inactive configuration should eliminate the high CPU problem. Removing either the BGP or IGP conflicting routes from the system should clear both symptoms.

CSCsx07181

Symptoms: Router crashes on trying to ping packet over SONET (POS) interface on CHOC12 SPA.

Conditions: The issue was seen on an internal build based on Cisco IOS Release 12.2(33)SRD. The problem does not occur in the released version of Cisco IOS Release 12.2(33)SRD, but this fix is required to correct an underlying programming error.

Workaround: There is no workaround.

CSCsx07317

Symptoms: Static NAT translations can fail after a reload or crash.

Conditions: The trigger seems to be a high number of static translations (~100 translations). Once the router is rebooted for any reason, the translations will fail.

Workaround: Remove and reapply static translations in the configuration.

CSCsx08294

Symptoms: A Cisco 6500 running Cisco IOS Release 12.2(33)SXH may encounter a bus error due to OSPF processes.

Conditions: Occurs when the device is configured for Open Shortest Path First (OSPF).

Workaround: There is no workaround.

CSCsx09353

Symptoms: Switched Port Analyzer (SPAN) is not capturing traffic in both directions. It only captures traffic in one direction.

Conditions: Occurs when running Cisco IOS Release 12.2(33)SRC or later and with a ES-20 card.

Workaround: Use another method of packet capture if possible. See VACL capture for details. Removing the SPAN configuration and reapplying it also helps in getting the feature working.

CSCsx09736

Symptoms: DHCP failed to get binding under IP as aggregation model with L2 access.

Conditions: Occurs with IP session with L2 access on a device configured for DHCP relay and VRF transfer.

Workaround: There is no workaround.

CSCsx11776

Symptoms: Executing the commands show ip bgp version recent 1 or show ip bgp version 1 from EXEC mode may cause the device to crash.

Conditions: The symptom is observed in affected images that have support for BGP.

Workaround: Use AAA command authorization to prevent the use of these commands.

Further Problem Description: A note regarding BGP Looking Glasses for IPv4/IPv6, Traceroute & BGP Route Servers:

Per http://www.bgp4.as/looking-glasses, BGP Looking Glass servers are computers on the Internet running one of a variety of publicly available Looking Glass software implementations. A Looking Glass server (or LG server) is accessed remotely for the purpose of viewing routing info. Essentially, the server acts as a limited, read-only portal to routers of whatever organization is running the lg server. Typically, publicly accessible looking glass servers are run by ISPs or NOCs.

Public Looking Glass servers running an affected version of Cisco IOS are specially susceptible to this bug because they provide unauthenticated public access to Cisco IOS devices. Because of this, operators of BGP Looking Glass servers are encouraged to use AAA to prevent execution of the commands mentioned above that are known to crash Cisco IOS.

CSCsx15841

Symptoms: The BGP aggregate-address command configured on active RP does not auto-sync to the running configuration of the standby RP.

Conditions: Occurs when BGP is configured on active/standby redundant RP system.

Workaround: Configure BGP aggregate-address and reboot the system, forcing both active and standby to load from startup configuration.

CSCsx17619

Symptoms: Connectivity between the multilink bundles is lost.

Conditions: Occurs upon configuration of DLFI over ATM and trying to clear the virtual-access created for multilink using the clear ppp interface virtual-access<no> command.

Workaround: There is no workaround.

CSCsx18270

Symptoms: Admin tag is being advertised by the neighbor router. This tag is not showing up in the local router. This causes route filtering based on admin tag to fail.

Condition: Occurred on a Cisco ASR1000 running Cisco IOS Release 12.2(33)XNB. Other devices and releases of Cisco IOS are affected.

Workaround: There is no workaround.

CSCsx20147

Symptoms: The delay value to destination computed is different between IPv4 and IPv6.

Conditions: Occurs when EIGRP for IPv6 is configured.

Workaround: There is no workaround.

CSCsx20523

Symptoms: Service-policy is not removed from gigabit interface.

Conditions: Occurs after you configure a gigabit interface as a switchport and then attach/detach a service-policy.

Workaround: In order to remove the service policy configuration, go into the mode where the policy was first configured and then unconfigure it.

CSCsx20566

Symptoms: Traffic through SIP400 stops or SIP400 displays minor error in show mod output.

Conditions: Seen sometimes on doing RPR+ switchover in a chassis that supports hot fabric synchronization.

Workaround: Reset the line card.

CSCsx21231

Symptoms: SPA-24CHT1-CE-ATM will remain out of service on a SIP-400 because of a missing API.

Conditions: This issue will be seen during boot up on a Cisco 7600 router with SPA-24CHT1-CE-ATM and SIP-400.

Workaround: There is no workaround.

CSCsx21482

Symptoms: The following commands executed from the console result in a device reload: write, copy running-config startup-config or show run.

Conditions: The symptom is observed when a large number of interfaces (200+) have been configured for RIPv6 and are active. Interfaces which are down will not contribute to the problem.

Workaround: There is no workaround.

CSCsx21606

Symptoms: On a Cisco 10000 series router that is running Cisco IOS Release 12.2(28)SB11, the serial interface becomes stuck in an up/down state and the multilink interface in a down/down state. The debugs indicate:

Se7/0/0.10/17:1 PPP: Missed a Link-Up transition, starting PPP Se7/0/0.10/17:1 PPP: Updating buffered PPP packet Se7/0/0.10/17:1 PPP: Starting timer for fast-start Se7/0/0.10/17:1 PPP: Handle allocation failure

Conditions: The symptom is observed when new T1s are added to the router. The triggers are an SSO configuration and when the router runs for a long time. The new T1s cause a lot of flapping of links.

Workaround: Reload the router or perform a PRE failover on the Cisco 10000 series router.

CSCsx22512

Symptoms: After clearing the DHCP snooping bindings, renewing from the database and reloading the line card, snooping bindings are lost.

Conditions: Occurs when DHCP snooping is configured to store bindings in the database on the flash disk.

Workaround: There is no workaround.

CSCsx23566

Symptoms: All Layer 3 traffic is silently dropped on the ES40 line card after the module is reset.

Conditions: Occurs when Layer 2- and Layer 3-based Ethernet Virtual Circuits are configured on the ES40. This happens after an RSP fail over or when the module is reset using the hw-module module # reset command.

Workaround: Reload the router.

CSCsx25316

Symptoms: A device may reload because of a crash after the command clear ip route * is executed.

Conditions: The trigger for this issue is executing the clear ip route* command in the presence of a default route. If an RIP update is received by the router while the routing information base is being cleared, the update will be processed causing RIP to check the state of the default route in the routing information base. This combination has the potential to cause a crash.

The probability of the crash occurring is proportionate to the size of the routing table. The larger the routing table, the greater the chance of encountering the problem.

Workaround: It is recommended to avoid using the clear ip route * command. If the prefix in question is known, then use clear ip route <prefix> instead.

Further Problem Description: This problem was observed in Cisco IOS Release 12.2(33)SRC3. All Cisco IOS SR33-based images (SRB, SRC, SRD and SB33) are vulnerable to this problem. The problem will be seen only when using the clear ip route * command and is platform independent. Other commands like clear ip ospf, clear ip bgp, clear ip isis or clear ip route <prefix> are not vulnerable.

CSCsx27659

Symptoms: L3 traffic is blackholed after online insertion and removal (OIR) of Distributed Forwarding Cards (DFCs).

Conditions: After an OIR, some of the adjacencies (recirculation) may not be correctly programmed when they go online.

Workaround: Use the clear adjacency command to reprogram the adjacencies correctly. This will impact traffic on the router.

Further Problem Description: Use the show mls cef adjacency entry <x> detail command to diagnose. A display of "vlan=0" on recirculation adjacencies indicates this problem.

CSCsx28948

Symptoms: Packet leak is observed on Cisco 7200 router running Cisco IOS Release 12.2(33)SRC.

Conditions: Multicast packet is forwarded to the tunnel interface, causing memory leak. Even packet is dropped, memory leak is observed. Multicast data having less then 64 byte size is dropped at the driver. Leak is not happening with interface other then tunnel interface.

Workaround: There is no workaround.

CSCsx33622

Symptoms: Flapping BGP sessions are seen in the network when a Cisco IOS application sends full-length segments along with TCP options.

Conditions: This issue is seen only in topologies where a Cisco IOS device is communicating with a non-Cisco-IOS peer or with a Cisco IOS device on which this defect has been fixed. The router with the fixed Cisco IOS software must advertise a lower maximum segment size (MSS) than the non-fixed Cisco IOS device. ICMP unreachables toward the non-fixed Cisco IOS router must be turned off, and TCP options (for example, MD5 authentication) and the ip tcp path-mtu-discovery command must be turned on.

Workaround: Any value lower than the advertised MSS from the peer should always work.

Setting the MSS to a slightly lower value (-20 to -40) is sufficient to avoid the issue. This number actually accounts for the length of TCP options present in each segment. The maximum length of TCP option bytes is 40.

If the customer is using MD5, Timestamp, and SACK, the current MSS should be decreased by 40 bytes. However, if the customer is using only MD5, the current MSS should be decreased by 20 bytes. This should be enough to avoid the problem. For example:

1. If the current MSS of the session is 1460, New MSS = 1460 - 40 = 1420 (accounts for maximum TCP option bytes; recommended).

2. If the current MSS of the session is 1460, New MSS = 1460 - 20 = 1440 (accounts for only the MD5 option).

CSCsx33961

Symptoms: SNMP engine consumes 100% CPU and device does not respond to SNMP polls.

Conditions: Occurs when ATM SPA subinterface counters, such as ifInOctets and ifOutOctets are being polled with multiple Varbinds in single SNMP PDU.

Workaround: There is no workaround.

CSCsx34297

Symptoms: Watchdog reset seen with combination of NPEG1+PA-POS-1OC3/PA-POS-2OC3.

Conditions: The symptom is observed on a Cisco 7200 series router and Cisco 7301 router with an NPEG1 processor.

Workaround: Change the MDL of operation to PULL using the command dma enable pull model.

CSCsx35306

Symptoms: Router crashes at "t3e3_ec_safe_start_push".

Conditions: The crash is seen immediately after removing the channel-group of the PA-MC-2T3/E3-EC card.

Workaround: There is no workaround.

CSCsx37313

Symptoms: When using encapsulation PPP on a POS SPA OC192POS-XFP in a SIP-600, the protocol comes up on both sides and IP Control Protocol (IPCP) is open for PPP. Pinging the remote side fails due to corruption of the PPP frame.

Conditions: Occurs when using encapsulation PPP on a POS SPA OC192POS-XFP

Workaround: Use High-Level Data Link Control (HDLC) encapsulation.

CSCsx37431

Symptoms: CE-to-CE ping for packet size less than 48 bytes fails or applications like telnet fail.

Conditions: Occurs with ATM SPA on SIP200. ATM PA on FW2 should be one of the CEs facing, while other PEe should be 7200

Workaround: There is no workaround.

CSCsx39405

Symptoms: When unconfiguring multicast distribution tree (MDT) and VPN routing/forwarding (VRF), SP crashes.

Conditions: The problem occurs on scale setup. When number of entries is large on PI multicast side, the PI process can get suspended during delete operation

Workaround: There is no workaround.

CSCsx40675

Symptoms: Router crashes

Conditions: Occurs during xconnect L2TP session configuration.

Workaround: There is no workaround.

CSCsx40747

Symptoms: A specific configuration of "ip casa" followed by a subsequent use of the command show running-config can cause the router to go into an infinite loop and hang.

Conditions: The symptom is observed when "ip casa" is configured and you enter into config-casa mode. The command show running-config will cause the router to hang.

Workaround: There is no workaround.

Further Problem Description: This issue is specific to the usage of ip casa. If you do not use casa, you are not vulnerable to the issue described here.

CSCsx41877

Symptoms: ATM PVP CLI become inaccessible to the command-line interface.

Conditions: The commands disappear after configuring l2transport VCs on ATM interface.

Workaround: Execute default on ATM interface before configuring any L2VC or L2VP.

CSCsx43897

Symptoms: CPU utilization goes high when a third session is allowed to be created through SNMP. Also occurs with applications that use SNMP to create sessions, such as NAM GUI.

Conditions: Perform the SNMPSet on the service module session (this will fail). Now try to create another local session via SNMPSets sequence.

Workaround: Use CLI to create the sessions.

CSCsx46858

Symptoms: Router crashes while configuring MAC addresses.

Conditions: Occurs when configuring MAC addresses under VT interface in "config-rite" mode.

Workaround: There is no workaround.

CSCsx47554

Symptoms: With a topology like this:

CE | type 4 xconnect type 4 xconnect |-------------------- 7600 --------------- GSR 
-------------- CE SIP400 Sup720 Giga subif Giga subif

the packets above 1496 are not passing through end-to-end.

The MTU on the edge-facing interfaces is 1500, the one on the core-facing interfaces is 1600.

Conditions: The GSR on the other side seems not to have a similar behavior. The bug has been reproduced in Cisco IOS Release 12.2(33)SRB3 and SRC3.

Workaround: Increase the MTU on the edge-facing interface end-to-end

CSCsx56369

Symptoms: Connectivity breaks on SPA based multilink bundles with ACFC/PFC configured when one of the member links go down.

Conditions: Occurs on a Cisco 7600. Multilink must be SPA based with ACFC/PFC configured. The output of show ppp multilink on the RP would show multilink in hardware.

Workaround: Adding back the link or bringing the link back up makes it work.

CSCsx57465

Symptoms: On a Cisco 7600-SIP-200 / SPA-2XOC3-ATM running the c7600s72033-adventerprisek9-mz.122-33.SRB4 image, an ATM interface may suddenly cease processing ingress packets resulting in all VC sharing the physical interface being shut down.

Conditions: Occurs when the ATM SPA interface is configured for LFI.

Workaround: There is no workaround.

CSCsx58268

Symptoms: The route-map functionality is broken with respect to BGP.

Conditions: Configure route-map and apply to BGP neighbor as an inbound/outbound policy and then reload the router. The route-map functionality will not work.

Workaround: There is no workaround.

CSCsx58369

Symptoms: DHCP snooping bindings are lost on a Cisco 6724 when online insertion and removal (OIR) is performed on the line card just after renewing the snooping bindings from database.

Conditions:

1) Bring up a snooping binding on a Cisco 6724 LC.

2) Make sure the binding has been written to the snooping database.

3) Clear the snooping binding by entering the clear ip dhcp snooping command.

4) Write the bindings from the database back to the snooping table by entering the renew ip dhcp snooping database command.

5) Ensure that the binding has been repopulated into the snooping table by entering the show ip dhcp snooping binding command.

6) Perform OIR on the line card.

7) When the line card comes up, it is seen that the snooping binding is not repopulated. It is lost.

Workaround: Send a fresh DHCP request from the client.

CSCsx58889

Symptoms: Calls fail intermittently with cause "47: no resource available" error.

Conditions: Occurs when router is under load test.

Workaround: There is no workaround.

CSCsx59309

Symptoms: Cisco IOS routers crash when filter style is changed from fixed filter (FF) to wild card filter (WF).

Conditions: Occurs when FF style reservation is installed on an interface and is then modified to WF style without first removing the FF style reservation.

Workaround: Remove FF style reservation before configuring for WF style reservation.

CSCsx60939

Symptoms: Standby crashes on deletion of a port-channel.

Conditions: The problem is seen only when lacp fast-switchover is configured on the port-channel.

Workaround: Shut the port-channel before deleting it.

CSCsx62080

Symptoms: Cisco ASR crashes into ROMmon when doing DHCP renew from client PC when Cisco Intelligent Services Gateway (ISG) is configured as DHCP relay.

Conditions: Occurs when ISG is acting as DHCP relay and without port-bundle host key (PBHK) enabled.

Workaround: Disable ping using the ip dhcp ping packets 0 command.

CSCsx63667

Symptoms: ES40 line card crashes.

Conditions:

1) Have Port-channel with a service instance without encapsulation.

2) Have members across NPs.

3) Remove all the members related to 1 NP.

4) Add a member to the NP, which already has a member.

5) Line Card crashes.

Workaround: There is no workaround.

CSCsx64122

Symptoms: Service policy disappears from Multilink Frame Relay (MFR) interface.

Conditions: This is observed after MFR interface flaps.

Workaround: There is no workaround.

CSCsx65525

Symptoms: SIP reloads with the following error messages:

%C7600_PWR-SP-4-DISABLED: power to module in slot 2 set off (Module Failed SCP dnld)

%CWAN_RP-6-CARDRELOAD: Module reloaded on slot 2/0

Conditions: Occurs during switchover from slot6 to slot5 with RSP720.

Workaround: There is no workaround.

CSCsx70889

Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.

CSCsx76308

Symptoms: Cisco 6500 crashes with Breakpoint exception, CPU signal 23.

Conditions: An attempt to free unassigned memory is seen before the crash:

00:01:25: %SYS-2-FREEFREE: Attempted to free unassigned memory at 50D9D260, alloc 
40CC9960, dealloc 40CC9A90
-Traceback= 41044F88 40CC9A98 40CC88C0 40CC20E4 40CCF5B0 406AF1AC 4069A834 4101848C 
41018478

Workaround: There is no workaround.

CSCsx78074

Symptoms: Unable to remove ACLs.

Conditions: Occurs on the ES20. The no form of the command does not work.

Workaround: Reload to recover.

CSCsx78826

Symptoms: ES20 cards crash due to an address error after a remote Label Distribution Protocol (LDP) session is shut. This is also seen when the remote router is reloaded.

Conditions: Occurs on a Cisco 7600 running Cisco IOS Release 12.2(33)SRD.

Workaround: There is no workaround.

CSCsx79111

Symptoms: MPLS packets that need a swap label may get punted to CPU because the outgoing interface/label has wrong MTU value in hardware (MLS). Once the packet is punted to CPU, it is forwarded correctly, as Cisco Express Forwarding (CEF) in software has correct info. If the traffic rate is high, this causes high CPU.

-show mls status can confirm the MTU failure increasing.

-remote command switch show mpls platform vlan shows wrong MTU for outgoing interface.

-show mls cef mpls label X detail will show the MTU as 0.

-show mpls forwarding-table interface X detail shows good MRU value.

Conditions: Occurs on a Cisco 7600 running Cisco IOS Release 12.2(33)SRB5.

Workaround: Re-stating the mtu command or mpls ldp mtu ... does not make any difference. You need to either bounce the affected interface or reload the switch.

CSCsx82880

Symptoms: MAC security on ESM20 ports stop working after unrelated configuration changes are done to any other ports on the same ESM20.

Conditions: On ESM20 ports having service instances configured with MAC security on them, traffic stops flowing on those EVCs when unrelated configuration changes are done on other ports on that ESM20.

Workaround: Perform a shut/no shut on the affected port.

CSCsx94132

Symptoms: Router displays the following message:

SCP-SP-5-ASYNC_WATERMARK: 36152 messages pending in SCP async: LCP#4

If the number of pending messages keeps increasing, router may eventually crash.

Conditions: Occurs under the following scenario.

- With a switchport on ES20 - With more than few hundred allowed VLANs on ES20 trunk - If STP state on the switchports flaps.

The last condition is critical for the bug to occur.

Workaround: Prevent conditions leading to STP flaps.

CSCsx94400

Symptoms: All traffic through ES line cards stops after a RSP failover. The line cards are powered down and never recover.

Conditions: Occurs occasionally when a redundancy force-switchover is executed on a router containing ES line cards with an N-PE redundancy configuration that looks like the following under a VPLS VFI:

l2 vfi vfi101 manual

vpn id xxx

forward permit l2protocol all

Workaround: Reload the router. If this does not help, reduce the number of possible core-facing MPLS interfaces that the VPLS pseudowire could possibly take.

CSCsy01763

Symptoms: Packets leak from source to destination when PACL is configured and switchover is not complete.

Conditions: During switchover, and until TCAM is programmed, packets are L3 switched even if the PACL will drop them further. Also, when the PACL is changed, such as addition or removal of ACEs, some packets which are supposed to be dropped will leak to the destination.

Workaround: There is no workaround.

CSCsy04594

Symptoms: When a Cisco 7600 is connected to a different MST region and has a port with root guard configured on the MST boundary port, all VLAN interfaces flap each time a superior BPDU is received on this port. This behavior was observed with Cisco IOS Release 12.2(33)SRB4 and Cisco IOS Release 12.2(18)SXF14.

Conditions: It was observed in the following context:

1) The switch is connected to a different MST region 2) It has a port configured as root guard on MST region boundary

Workaround: Shut down blocked port or remove root guard configuration from the port and the VLAN interfaces stop flapping.

CSCsy07555

Cisco IOS devices that are configured for Internet Key Exchange (IKE) protocol and certificate based authentication are vulnerable to a resource exhaustion attack. Successful exploitation of this vulnerability may result in the allocation of all available Phase 1 security associations (SA) and prevent the establishment of new IPsec sessions.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml

CSCsy07830

Symptoms: All traffic through ES line cards stops after a RSP failover. The line cards fail diagnostics and never recover.

Conditions: Occurs periodically when a redundancy force-switchover is executed on a router containing multiple RSPs and ES line cards.

Workaround: Reload the router.

CSCsy08264

Symptoms: MQC policy applied on ES+ interface may not work as expected. Occurs if too many unique bandwidth rates are configured and applied on same line card and on the interfaces belonging to same Network Processor.

Conditions: If more than 32 unique bandwidth rates are (defined in policy maps applied on same NP) configured, the policy map is accepted without error but may not work as intended.

Workaround: If multiple unique bandwidth rates are required, space the policy maps across interfaces based on different network processors.

CSCsy10610

Symptoms: LACP L3 POCH members flap, getting unbundled and bundled back again.

Conditions: Global native VLAN tagging has to be enabled, and L3 POCH interface should have a sub-interface configured under it.

Workaround: Disable global VLAN tagging.

CSCsy17724

Symptoms: After a reload, CPU on the router remains high and does not recover on its own.

Conditions: This issue was observed on a reload of a Cisco 7600 router with Supervisor 720. The system had a scaled configuration with a large number of VRF', sub-interfaces and some Virtual Private LAN Services (VPLS) PW. BGP and ISIS routing protocols were also in use. The high CPU is seen in the CEF background process.

Workaround: An SSO switchover or a system reload can clear the problem.

CSCsy22193

Symptoms: After stateful switchover (SSO), adjacency mismatch and traffic failure occur on ES20 sub-interfaces.

Conditions: This happens when egress QOS/ACL policy is configured on ES20 sub-interface.

Workaround: Perform a shut/no shut on the ES20 interface.

CSCsy24369

Symptoms: After removing "priority 30" from policy-map queuing_child, an attempt to add it back fails with the following message:

Configured Percent results in out of range kbps. Allowed range is 8-622000. The present CIR value is 6.

Conditions: Occurs with the following configuration:

Configure the following policy-map:
Policy Map queuing_child
Class ip_prec_1
priority 30 (%)
Class ip_prec_2
bandwidth remaining 20 (%)
Class ip_prec_3
bandwidth remaining 30 (%)
Class ip_prec_4
bandwidth remaining 49 (%)
Policy Map Dest
Class Dest
Policy Map queuing
Class class-default
Average Rate Traffic Shaping
cir 5000000 (bps)
service-policy queuing_child

Workaround: There is no workaround.

CSCsy24676

Symptoms: On occasion, a false positive is returned on a file system failure. File operation is deemed successful when, in fact, it has failed.

Conditions: This problem occurs when the file system device returns an error and the code follows the path in the file system buffer cache where the error is masked and converted to a success code. This problem is likely to show up if there is a device error during the write. The device error may be due to bad media or an OIR (although it is very unlikely during an OIR).

Workaround: There is no workaround.

Further Problem Description: This is possible during any file system operation where a file system device is unable to complete the operation and an error is returned. This error is not passed down to the file system stack but is converted to a success code. Other clients which are dependent on previous file system operations fail on successive file system calls and possibly result in a crash.

CSCsy26370

Symptoms: Router crashes at af_policer_get_class_drops.

Conditions: Router crashes while attaching policy under another policy.

Workaround: There is no workaround.

CSCsy26526

Symptoms: Router may reload under excessive netconf configuration.

Conditions: The following configuration commands, when configured repeatedly within a short period of time may cause the device to reload.

* netconf ssh

* netconf beep listener

Workaround: There is no workaround.

CSCsy27394

Symptoms: Users who can execute a show ip interface command can see that an LI tap is in progress.

Conditions: No specific conditions are necessary to trigger this problem.

Workaround: There is no workaround.

CSCsy28296

Symptoms: A PPP aggregator may erroneously remove a per-user static route downloaded from RADIUS when the first member link of a multilink group goes down.

Conditions: Issue observed on Cisco 7200/NPE-G1 running Cisco IOS Release 12.2(33)SRC3 and earlier SRC releases. Also occurs in Cisco IOS Release 12.2(33)SRD.

Workaround: Clear interface virtual-access (for the MLP bundle). You can also downgrade to Cisco IOS Release 12.2SB.

CSCsy33145

Symptoms: Interface default queue traffic is favored instead of the QoS applied to subinterface or EVC traffic.

Conditions: If there is a mix of QoS policy applied and not applied subinterfaces/EVCs on the main interface, the traffic on the subinterface/EVC without QoS can take the entire physical interface bandwidth, starving the QoS applied subinterface/EVC.

Workaround: Apply QoS policy on all the subinterface/EVCs on the main interface.

CSCsy42615

Symptoms: Entries for ABRs and ASBRs are missing from the OSPF route table. This results in inter-area and external routes being omitted from the Routing Information Base (RIB).

Conditions: The bug will only be seen when MPLS-TE tunnels are being used. Also, specifying non-default SPF timer values with timers throttle spf will increase the risk of hitting this bug.

Workaround: There is no workaround.

CSCsy43042

Symptoms: MPLS frames that need to be encapsulated into VRF GRE tunnel are punted to RP if the GRE tunnel requires MPLS imposition.

Conditions: This has been observed on Cisco 7600 provider edge (PE) routers in L3VPN environment.

Workaround: There is no workaround.

CSCsy45838

Symptoms: The show ip ospf border-router may cause a router to crash.

Conditions: Occurs if the border table is recalculated in a significant way while the output is being printed on the console. The risk of a crash is reduced if you avoid using the auto-more feature and allow the entire output to display at once.

Workaround: There is no workaround.

CSCsy55362

Symptoms: Console may hang.

Conditions: Occurs when the TACACS+ server is being used as AAA server and the single-connection option is configured.

Workaround: Remove the single connection option.

CSCsy55455

Symptoms: Device running Cisco IOS Release 12.2(33)SRD1 with SAA/SNMP crashes due to bus error.

Conditions: Occurs when an SNMP poll for IPSLA/SAA values is performed.

Workaround: There is no workaround.

CSCsy57786

Symptoms: The following TOS settings tests fail on ES+ card:

* TOS mapping from inner to outer IP header via ip tos reflect on PW class.

* TOS setting on outer IP header via ip tos value value.

* TOS setting via ingress MQC policy on IP subinterface with xconnect.

Conditions: Occurs on a ES+ card configured for L2TPv3.

Workaround: There is no workaround.

CSCsy58886

Symptoms: Router crash is seen during ISSU with mls qos enabled.

Conditions: Occurs when user does ISSU from Cisco IOS Release 12.2(33)SRC2 to SRC3 or from 12.2(33)SRD1 to later SRD release.

Workaround: Disable QoS globally using the no mls qos command.

CSCsy75784

Symptoms: Missing Intermediate System-to-Intermediate System (IS-IS) routes or routing loop occurs after the edge router reloads several times.

Conditions: Occurs when MT-IPv6 is running and fast convergence parameters are configured.

Workaround: Enter the clear isis * command on the affected router.

CSCsy81341

Symptoms: When FastEthernet SPA on SIP400 is used as the core-facing side, switch virtual interface (SVI)-based EoMPLS/VPLS traffic does not flow out of the pseudowires. Receiving Traffic on the pseudowire is fine.

Conditions: Occurs when FE spa on SIP400 is used as the core facing side for SVI-based EoMPLS/VPLS. All the imposition traffic is dropped.

Workaround: There is no workaround.

CSCsy83830

Symptoms: Router crashes when we send multiple access packets for same username when configured for RADIUS Load Balancing (RLB).

Conditions: Occurs with the following topology

CLIENT----->RLB----->SERVER

Client sends multiple access retry packets to server and router crashes after a period of time. This issue will be seen in cases where multiple access requests are seen for the same username, and 60 seconds expire since the arrival of the first of such access requests, before an accounting start for the same username is seen.

Workaround: If RLB do not see multiple access packets we wouldn't see any crash.

CSCsy87385

Symptoms: For IPv6 adjacencies, MTU is incorrectly programmed.

Conditions: Occurs with simple IPv6/6PE setup.

Workaround: There is no workaround.

CSCsy92895

Symptoms: When SIP-400 is configured as Lawful Intercept service module, after a line card online insertion and removal (OIR), the SIP-400 may not get selected as Lawful Intercept service module.

Conditions: Occurs when SIP-400 is configured as Lawful Intercept service module on a Cisco 7600.

Workaround: After line card OIR, select the SIP400 again as the LI service module using the command li-slot list <sip400 slot number>.

CSCsy95540

Symptoms: L2TP tunnel not coming up for ATM attachment circuit.

Conditions: The problem is seen on Cisco 7200 router running Cisco IOS Release 12.2(33)SRC.

Workaround: There is no workaround.

CSCsz08876

Symptoms: Packets are not getting in output policy.

Conditions: Occurs on ES+ card configured for L2TPv3.

Workaround: There is no workaround.

CSCsz11877

Symptoms: MPLS-TE tunnel label reallocation on midpoint router occurs while RSVP is gracefully restarting due to CPU switchover.

Conditions: Occurs on a Cisco 7600 that is configured as the midpoint router when the upstream node is a Cisco IOS-XR router. This does not happen if the upstream node is also a Cisco IOS router. Because of this label re-allocation, traffic downtime is ~100 msec

Workaround: There is no workaround.

CSCsz28707

Symptoms: DHCP binding in DHCP client may not work.

Conditions: Occurs after online insertion and removal (OIR) operation on a Cisco 7600 with SIP400 line card.

Workaround: There is no workaround.

CSCsz29991

Symptoms: The following error message is displayed:

%OSPF-4-NULL_PREV_LINKAGE with a traceback of:

errmsg(0x40636c28)+0x50

ospf_dlink_delink(0x40eda914)+0x3c

ospf_service_redist(0x40f2d03c)+0x428

ospf_router(0x40ee2f20)+0xa24

This error causes excessive CPU utilization, which causes the Supervisor or RSP to crash.

Conditions: Occurs after entering the clear ip ospf process command, especially in an environment that has multiple OSPF processes. Learning the same prefix with different processes can also cause this condition to occur.

In this case it was due to the fact that one process was configured with default-information originate always, causing an implicit redistribution. The other process was also learning a default route as E2.

Workaround: To avoid the issue:

- Clear ip ospf process on a process by process basis few min. apart.

- Shut/no-shut of the OSPF Process instead of the hard reset/clear

Reload is the only way to recover if the system has run into the issue already.

CSCsz42928

Symptoms: Multicast replicated packets get dropped at "SELENE".

Conditions: Occurs when ES+ card is in slot 1 and the port is 1/12.

Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(33)SRD1

This section describes possibly unexpected behavior by Cisco IOS Release 12.2(33)SRD1. All the caveats listed in this section are open in Cisco IOS Release 12.2(33)SRD. This section describes only select open caveats.

CSCsx37608

Symptoms: Tracebacks observed when shut/no shut is performed multiple times on ATM-OC3 interface.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRD.

Workaround: There is no workaround.

CSCsx95984

Symptoms: For C7600 ES+XT Serial line cards, the TenGigaEthernet interface could report erroneous link up status while the link is actually down.

Conditions: This problem is observed with Cisco IOS Release 12.2(33)SRD1. The problem happens when the remote side changes to different transport mode under interface configuration.

Workaround: Every time the remote side changes its transport mode configuration, do a shutdown and no shutdown for the corresponding interface in the local side.

CSCsy98323

Symptoms: Supervisor does not return to SP Prompt after Service line card (SVCLC) tunneling.

Conditions: After doing a remote login switch from supervisor, we go into SUP SP prompt. Then Tunnel into LCP ROMMon through svclc console <slot> from SUP-sp to boot LCP. Once LCP starts booting, we should come back to SP prompt. This is not happening now.

Workaround: Type a ^C to get back to the SP prompt.

Resolved Caveats—Cisco IOS Release 12.2(33)SRD1

Cisco IOS Release 12.2(33)SRD1 is a rebuild release for Cisco IOS Release 12.2(33)SRD. The caveats in this section are resolved in Cisco IOS Release 12.2(33)SRD1 but may be open in previous Cisco IOS releases.

Miscellaneous

CSCec72958

Symptoms: A Cisco router that is configured for Network Address Translation (NAT) may reload unexpectedly because of a software condition.

Conditions: This symptom can occur when the router translates a Lightweight Directory Access Protocol (LDAP) packet. NAT translates the embedded address inside the LDAP packet. This problem is strictly tied to NAT and LDAP only.

Workaround: There is no workaround.

CSCec85585

Symptoms: Some virtual circuit (VC) information is missing in the Simple Network Management Protocol (SNMP) MIB object cAal5VccEntry from the output of the snmpwalk router configuration command. The ATM VCs 0/100, 0/200 and 0/500 exist on the router but are missing in the MIB.

Conditions: This symptom is observed on a Cisco 7513 router that is running a special image of Cisco IOS Release 12.2(15)T5. The symptom may also occur in other releases.

Workaround: Enter the show atm vc privileged EXEC command on the same device to obtain a complete list of all the VCs.

CSCeg80842

Symptoms: The output of serial interfaces on a PA-MC-8TE1 may become stuck after several days of proper operation.

Conditions: This symptom is observed on a Cisco 7206VXR that runs Cisco IOS Release 12.3(10a) and that has MLP configured on the serial interfaces of the PA-MC-8TE1.

Temporary Workaround: Perform an OIR of the PA-MC-8TE1 or reload the router until the symptom occurs again.

Further Problem Description: The symptom occurs during normal operation of the router. If many errors occur on the link, the symptom is more likely to occur.

CSCeh75136

Symptoms: If a user fails to successfully establish a SSH connection on the first attempt, subsequent attempts may also fail.

Conditions: Occurs when a Cisco router is configured to authenticate SSH connections using TACACS+. The rem_addr field in the TACACS+ header may be empty if the user does not successfully authenticate on the first attempt. This may cause authentication or authorization failures if rem_addr information is required by the TACACS+ server.

Workaround: Configure ipssh authentication-retries 0.

CSCek75694

Symptoms: A router running Cisco IOS 12.4T may reload unexpectedly

Conditions: Occurs when BFD is configured and active.

Workaround: Disable the BFD feature.

CSCsb98906

Symptoms: A memory leak may occur in the "BGP Router" process.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0(26)S6, that is configured for BGP, and that has the bgp regexp deterministic command enabled.

Workaround: Disable the bgp regexp deterministic command.

CSCse29570

Symptoms: Router might unexpectedly reload during CNS configuration download.

Conditions: The downloaded configuration must disable the CNS configuration initial or partial for this crash to occur.

Workaround: Use static configuration and prevent configuration download from CNS server.

CSCsg11616

Symptoms: While restarting the iprouting process, the system crashed at redzone corruption.

Conditions: Occurs following a switchover. The iprouting process should restart once the standby becomes active.

Workaround: There is no workaround.

CSCsg39754

Symptoms: When DHCP snooping is configured on a VLAN, the redirect access list programmed in TCAM permits a wide range of UDP ports from bootps/bootpc to 65xxx.

Conditions: UDP traffic to these destination ports (0x143, 0x243, 0xFF43) is being redirected to Route Processor (RP). If "ip dhcp snooping limit" is not configured, then RP CPU goes to 100%.

Workaround: There is no workaround.

CSCsh48947

Symptoms: Some of the 48 power over Ethernet ports of a line card cannot be configured as "power inline static" with the maximum power capacity, 15.4 watts, that a port can support.

Conditions: The number of supported ports depends on the power rating of the voice daughter board. One or more ports may not operate at maximum capacity.

Workaround: There is no workaround.

CSCsi07687

Symptoms: Self ping to SVI fails when VLAN configurations are removed and reapplied.

Conditions: Occurs when an interface is deleted and added again.

Workaround: There is no workaround.

CSCsi88974

Symptoms: While configuring a mediation device (MD), if the MediationSrcInterface is set to loopback interface, traffic will cause MALLOC failures.

Conditions: Problem is seen when traffic rate is equal to or greater than 8000 packets per second.

Workaround: Do not use loopback0 as MD source interface.

CSCsj78403

Symptoms: A router may crash when the clear ip bgp command is entered.

Conditions: Occurs on devices running BGP and configured as a route reflector client with conditional route injection configured.

Workaround: Unconfigure conditional route injection.

CSCsk49705

Symptoms: The ip nat inside source static network command does not have the <cr> option.

Conditions: This symptom is observed on a Cisco 7200 router that is loaded with Cisco IOS Release 12.4 or 12.4T.

Workaround: There is no workaround.

CSCsk94179

Symptom: Connectivity problems are observed for IPv6 client, which obtained IPv6 prefix via DHCP for Virtual Access interface, due to incorrect static routes in the routing table for the assigned IPv6 prefix.

Conditions: Occurs with IPv6 prefix delegation via DHCP, when client moves from one interface to another.

Workaround: None

Further problem description: When IPv6 prefix delegation assigns a prefix for Virtual Access interface, it creates a static route for the prefix in the routing table. When a client moves to a new interface, old binding and the old routes are retained, which causes the problem.

CSCsl68327

Symptoms: Packets may be lost during rekey.

Conditions: Occurs because IPSec transit packets may trigger invalid SPI.

Workaround: There is no workaround.

CSCsl71704

Symptoms: A receive access control list (rACL) with large ACL is not applied on interface if is QoS configured.

Conditions: Occurs when rACL with large ACL is applied on an interface. It consumes over 60% of ternary content addressable memory (TCAM) space. If the rACL is applied a second interface with QoS, the configuration fails without displaying an error message.

Workaround: There is no workaround.

CSCsm28287

Symptoms: After shutting down a GRE tunnel interface, the active RP crashed and switchover took place. The following error message was displayed:

%ALIGN-1-FATAL: Illegal access to a low address 13:02:45 UTC Fri Jan 18 2008 addr=0xD, 
pc=0x7144A5A0, ra=0x7209FFF8, sp=0x5ABEE90 SLOT0:01:40:03: %DUMPER-3-PROCINFO: pid = 
16409: (sbin/ios-base), terminated due to signal SIGBUS, Bus error (Invalid address 
alignment) SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: zero at v0 v1 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: R0 00000000 7A5FD854 EF4321F9 
7A6452D0 SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: a0 a1 a2 a3 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R4 EF4321CD 0000000B 0000000B 00000000 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: t0 t1 t2 t3 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R8 7CB96E10 00FDDBE0 00000000 EFFFFFFF 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: t4 t5 t6 t7 SLOT0:01:40:03: 
%DUMPER-3-REGISTERS_INFO: 16409: R12 00000000 F7E8E12F 00000000 00000000 
SLOT0:01:40:03: %DUMPER-3-REGISTERS_INFO: 16409: s0

Conditions: Occurred on a Cisco 7200 running an internal build of Cisco IOS Release 12.2SX.

Workaround: There is no workaround.

CSCsm47417

Symptoms: W2:setting ceExtSysBootImageList cause write memory to work incorrectly.

Conditions: Occurs after setting ceExtSysBootImageList to a new boot image from SNMP. The new boot image in running-config is not copied to startup-config. Instead, a variable "d" will be copied to startup-config after the write memory. The show bootvar command will show BOOT variable = d.

Example:

bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:3> 
bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:3>getmany -v2c 
10.64.68.138 public ceExtSysBootImageList ceExtSysBootImageList.2001 = 
disk1:s72033-adventerprisek9_dbg-vzsm47417test ceExtSysBootImageList.2017 = 
disk1:s72033-adventerprisek9_dbg-vzsm47417test 
bgl11-lab1-tftp1:/auto/sw/packages/snmpr/15.1.0.3/solaris2bin:4>setany -v2c 
10.64.68.138 public ceExtSysBootImageList.2001 -o "disk1:" ceExtSysBootImageList.2001 
= disk1: ------------------------------------------------ 
7600-11-1# 00:02:56: %SYS-5-CONFIG_I: Configured from 10.64.71.240 by snmp

Workaround: There is no workaround.

CSCsm53196

Symptoms: Crash occurs at "ip_route_delete_common".

Conditions: Occurs under the following scenario:

1) A multicast BGP route exists.

2) A unicast BGP route exists for the same prefix.

3) Another route covered by the same majornet as the BGP route exists.

4) There are both iBGP and eBGP sources for the BGP prefix.

5) Redistribution of BGP routes into an IGP must be configured.

Topology change in network causes mBGP to switch from using the iBGP sourced route to the eBGP sourced route will cause the crash.

Workaround: If there are not both iBGP and eBGP sources for the same route the problem will not occur. If redistribution of BGP Into an IGP is not configured the problem will not occur.

CSCsm71537

Symptoms: The router crashes when Independent Optimized Edge Routing (OER) is configured.

Conditions: Occurs when OER is configured.

Workaround: There is no workaround.

CSCsm86832

Symptoms: The line protocol of the serial interface keeps flapping.

Conditions: This symptom is observed after BERT is run simultaneously on more than one fractional T1 with a Frame Relay sub-interfaces.

Workaround: Add and then remove the T1.

CSCso29361

Symptoms: The commands given in the interface range command may not be synced to all interfaces configured in the range in the standby supervisor.

Conditions: Occurs when configuration commands are entered under interface vlan range command. They get attached to only the first VLAN in the range in the redundant supervisor. After switchover, traffic does not flow due to the missing VLAN configuration.

Workaround: There is no workaround.

CSCso40612

Symptoms: Router is crashing due to random memory corruption in parser code.

Conditions: The crash happens on only particular sequence and timing of configuration.

Workaround: There is no workaround.

CSCso56038

Symptoms: The following error message may be seen:

%DUAL-3-INTERNAL: eigrp 4: Internal Error

Conditions: This symptom is seen when a PE-CE setup using site-of-origin (SoO) tags, in which an PE router that is running EIGRP can learn the same route both by EIGRP (from a CE neighbor) and also by redistribution.

The above error may be seen when EIGRP on the PE prepares to send information to a neighbor about a route learned from another neighbor (with no SoO tag), but before the information can be sent, the route is replaced by a redistributed route (with an SoO tag). The above error can be seen. This behavior is very dependent on the timing of this series of events.

Workaround: There is no workaround.

Further Problem Description: It is not clear what functional impact this may have, or whether the error message is purely a warning.

CSCso57020

Symptoms: Etherchannel states for Link Aggregate Control Protocol (LACP) port-channels are inconsistent between active and standby, which could possibly affect traffic forwarding.

Conditions: Occurs while configuring several LACP port channels. This could be seen if LACP port channels are configured and the device is brought up in SSO mode.

Workaround: Once the standby is completely up in HOT state, perform a shut/no shut on the interfaces that are inconsistent.

CSCso74922

Symptoms: Resilient Ethernet Protocol (REP) state flaps after line card reset

Conditions: Occurs on routers running Cisco IOS Release 12.2(33)SRD with SIP600 ports configured as REP edge ports.

Workaround: There is no workaround.

CSCso90970

Symptoms: The no ip proxy-arp command that is configured under ISG enabled interface is not working.

Conditions: This symptom is observed on the ethernet interface, where an ip subscriber command is configured. Same interface allows disabling IP Proxy ARP with the no ip proxy-arp command, but the command is ignored.

Workaround: There is no workaround.

CSCsq06208

Symptoms: When health monitoring (HM) diagnostic failure happens, call-home diagnostic messages are not out before platform action is taken.

Conditions: Call-home is subscribed to diagnostic alert group minor or major error and the gold policy is active. It only happens when the HM diagnostic test interval is small enough.

Workaround: Set the HM diagnostic test interval to be large enough, but there is no guarantee it will work in all test cases.

Further Problem Description: Because gold policy is last policy in EEM queue, it waits for call-home messages to send out before it executes. If gold policy continues to trigger on the next test failure after reaching the threshold when action notify flag is already false, it does not need to wait for call-home message to execute. It could crash the system before the call-home message for the last gold policy finishes.

Adding ACTION_NOTIFY TRUE condition to the gold policy will prevent the gold policy to continuously execute and consistent with call-home message triggering condition.

CSCsq14261

Symptoms: Downstream traffic will drop when we send IPv6 traffic over PPPoE sessions.

Conditions: Bring up a PPPoE session over L2TP tunnel for address negotiated by IPv6, then send downstream IPv6 traffic.

Workaround: There is no workaround.

CSCsq42885

Symptoms: Line card crashes recurrently with the "Address exception error".

Conditions: The issue is seen when entering the no shutdown command on the spatial reuse protocol (SRP) interface.

Workaround: There is no workaround.

CSCsq53542

Symptoms: After stateful switchover (SSO) there may be loss of multicast packet delivery for 10 or more seconds.

Conditions: Occurs when multicast routing is enabled in the default mode.

Workaround: If there are no mStatic or mBGP routes, the following configuration will avoid the problem:

Router(config)#ip multicast rpf multitopology 
Router(config)#global-address-family ipv4 multicast 
Router(config-af)#topology base 
Router(config-af-topology)#use unicast base
Router(config-af-topology)# 

CSCsq55691

Symptoms: QoS with Link Fragmentation and Interleaving (LFI) over ATM does not work.

Conditions: Occurs after a shut/no-shut on the ATM interface

Workaround: Reload the line card on both ends.

CSCsq60016

Symptoms: A router crashes after a long RSA key string is entered.

Conditions: This symptom is observed when a very long hex string is entered.

Workaround: Break the entry into shorter strings.

CSCsq77282

Symptoms: Creating a sub-interface may occasionally cause a traceback

Conditions: This may happen when configuring an ATM or SONET sub-interface.

Workaround: There is no workaround.

CSCsq77571

Symptoms: Router (SP) crash may happen upon deleting multiple VRFs or unconfiguring multiple MDTs.

Conditions: The crash is seen when trying to delete multiple MDTs at one time.

Workaround: Allow at least seconds after each MDT delete command or VRF delete command before issuing the next command.

CSCsr05746

Symptoms: ESM20 line card may crash while booting up.

Conditions: Occurs intermittently with a scaled topology.

Workaround: There is no workaround.

CSCsr09062

Symptoms: Cisco 7200 crashes due to memory corruption.

Conditions: Occurs when MLP+QoS is configured on a Cisco 7200 router. QoS policy is having bandwidth, change the BW parameter and flap the multilink using clear int multilink1 to see the crash.

Workaround: There is no workaround.

CSCsr18589

Symptoms: A Virtual Router Redundancy Protocol (VRRP) group configured on a VLAN interface flaps from the backup to the master state after stateful switchover (SSO) when the existing master is still available on the network. The group will flap back to backup a short period later.

Conditions: The problem only occurs when there are a large number of VLAN interfaces with a VRRP group configured on each interface and SSO is performed.

Workaround: Each of the VRRP groups can be configured with a larger VRRP advert timer value. Values should be varied depending on the setup, but a larger than default value is usually required.

CSCsr18942

Symptoms: Traceback occurs when VPN routing/forwarding (VRF) is deleted and then recreated.

Conditions: Occurs when multicast RP is configured under VPN routing/forwarding (VRF) first. When the VRF is deleted, some multicast data may still be locked and not deleted, causing the traceback when a new VRF is created and multicast RP is configured there.

Workaround: There is no workaround.

CSCsr26025

Symptoms: When "0.0.0.0/8 static route to null 0" is configured, the default gateway failover does not work. RIB is not updated.

Conditions: Occurs under the following scenario:

- Border Gateway Protocol (BGP) with two neighbors sending a default gateway.

- Static route "0.0.0.0/8 to null 0" is configured.

- Failover takes place and RIB is not updated.

Workaround: There is no workaround.

CSCsr29468

Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.

Cisco has released free software updates that address this vulnerability.

Several mitigation strategies are outlined in the workarounds section of this advisory.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml

CSCsr41079

Symptoms: Error message seen after stateful switchover (SSO):

%CHKPT-4-NOMESSAGE: Message is NULL, (Cannot get data ptr)

Conditions: Occurs when Intermediate System-to-Intermediate System (IS-IS) NSF is configured.

Workaround: There is no workaround.

CSCsr43461

Symptoms: Some configurations are missing after a reload.

Conditions: This symptom is seen when a router reloads that results in missing configurations of "vrf selection source" under show run.

Workaround: There is no workaround.

CSCsr49316

Symptoms: A crash happens when the show ipv6 rpf x:x:x::x command is given.

Conditions: This symptom is observed only when there are more than 16 adjacencies for a single static route. The crash happens when the show ipv6 rpf command is given for this particular static route.

Workaround: There is no workaround. This problem occurs as long as there are more than 16 adjacencies for single static route even if some of them are not active.

CSCsr53264

Symptoms: A software-forced crash occurs on the RP of a Cisco 7600 running Cisco IOS Release 12.2(33)SRB2.

Conditions: Occurs when the clear ip route-mapname command is entered.

Workaround: Upgrade to Cisco IOS Release 12.2(33)SRC3 or later.

CSCsr55713

Symptoms: A crash occurs.

Conditions: The crash is caused by a ping across an ISATAP tunnel. The symptom is observed only in Cisco IOS Release 12.4(15)T7 on the Cisco 7200 (it is not known to affect other platforms), since the crash is dependent on the Cisco IOS memory map (which varies with each image).

Workaround: There is no workaround.

CSCsr55922

Symptoms: The EIGRP IPv6 process may incorrectly select a router-ID from the 127.0.0.0 address range.

Symptoms: The same router-ID may be selected on two separate Cisco routers configured for EIGRP IPv6. External prefixes advertised by one of the EIGRPv6 routers will be ignored by the receiving EIGRPv6 router due to the fact the routerID contained in the external data portion of the prefix matches the receiving routerID; a loop prevention method.

Workaround:Manually configure a router-ID under the EIGRP IPv6 process with router-id<address> command.

CSCsr56465

Symptoms: Line card MAC notification test fails when redundancy mode is changed from RPR to SSO or SSO to RPR. SIP-400 Bus Connectivity Test failed when the following commands are issued:

Conf t redundancy mode rpr

Conditions: The issue observed in the Fabric Hot Sync-enabled Sup720 and RSP720 routers Cisco IOS Release 12.2(33)SRC. In the problem state, Super Santa Ana (SSA) channels are out of sync. For example,show platform hard ssa status will display SSA channel status from the SSA based CWAN module console.

Workaround: There is no workaround.

CSCsr68497

Symptoms: The router crash when the default pppoe enable command is entered.

Conditions: Occurs with 4094 PPPoE sessions active. When the above command is used to disable PPPoE under Ethernet subinterface, the router crashes.

Workaround: There is no workaround.

CSCsr70963

Symptoms: A Cisco 10000 PRE will reload unexpectedly when a radius server which is marked as dead is removed from the configuration during authentication of sessions.

Conditions: The issue is seen when a RADIUS server is marked as dead. There are attempts to retry and access the server during its removal from the configuration.

Workaround: There is no workaround.

CSCsr72352

Symptoms: EBGP-6PE learned IPv6 labeled routes are advertised to IBGP-6PE neighbor by setting NH as local IP address.

Conditions: This symptom is observed on 6PE Inter-AS Option C with RR case.

Workaround: There is no workaround.

CSCsr79367

Symptoms: Slow synchronization of IP subscriber sessions from Active to Standby RP.

Conditions: This issue is observed only for a large number of IP subscriber sessions. While the traffic is flowing, if user manually requests to clear all the sessions and while that is processing the line card reboots, then standby RP can get into a state there are dangling sessions. This does not render the router useless, but increases the sync time from active to standby.

Workaround: There is no workaround.

CSCsr80601

Symptoms: An ISAKMP SA is not deleted as expected after removing the RSA key.

Conditions: The issue is seen when the user tries to clear the ISAKMP SAs by issuing the clear crypto session command on an IKE SA that has multiple IPSEC SAs.

Workaround: Use the clear crypto sa and clear crypto is commands.

CSCsr81271

Symptoms: A Cisco 7600 router with PA-A3-T3 port adapter in flexwan module WS-X6582-2PA could generate following error messages with tracebacks upon a mass ATM PVCs flap:

SLOT 2/0: %CWAN_ATM-3-VC_OR_PORT_ERR: Invalid VCD FF03 or Port: 0 -Traceback= 403E2200 403A8C1C 40344F88 40347FD0 403481B4 403C374C 401CD170

Slot 2/0 is the slot the port adapter is installed.

Conditions: This seems to only occur when a large number of ATM PVCs flap, most likely from the service provider side.

Workaround: There is no workaround.

CSCsr82785

Symptoms: If APS is configured on a large number of channelized sub-interfaces associated with a single controller such that a single failure can cause all of these interfaces to failover at the same time, and RIP is configured to run over these interfaces, high sustained CPU usage will be seen following the failover and reconvergence time will be lengthy.

Conditions: Large number of APS protected interfaces fail over at the same time. RIP is the protocol running on those interfaces. IP addresses on all interfaces are covered by the same network statement.

Workaround: There is no workaround.

Further Problem Description: The length of the high CPU and reconvergence period will increase as the number of impacted interfaces increases.

The length of the high CPU and reconvergence period will also increase as the number of network statements which cover the IP addresses on the affected interfaces decreases i.e. it will be worst when a single classful network (e.g. 10.0.0.0) covers all interfaces, somewhat better when multiple classful networks are impacted.

CSCsr84639

Symptoms: After 30 minutes, MIB synchronization failure messages appear on primary RP. Secondary RP crashes.

Occurs under the following scenario:

1) Bringup 1 pppox session on the L2TP network server (LNS)

2) Pass bidirectional traffic through the LNS

3) After 30 minutes, MIB sync failures message appear on primary RP and secondary RP crashes.

Workaround: Enter the no snmp mib notification-log default command.

CSCsr86515

Symptoms: Router crashed due to watchdog timeout in the virtual exec process:-

%SYS-3-CPUHOG: Task is running for (128000)msecs, more than (2000)msecs (129/17),process = Virtual Exec. -Traceback= 40B5D8A8 40B5D984 40B5DA4C 40B5DB78 40B5DC6C 40C0E1BC 4125D3A8 4209FAEC 420AA5A0 4054C05C 420570D8 40575510 41257298 41257284 %SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = Virtual Exec. -Traceback= 40B5D8C8 40B5D984 40B5DA4C 40B5DB78 40B5DC6C 40C0E1BC 4125D3A8 4209FAEC 420AA5A0 4054C05C 420570D8 40575510 41257298 41257284

Conditions: This was observered on a Cisco 7600 with Supervisor 720 running Cisco IOS Release 12.2(33)SRB3 after a ATM sub-interface was removed.

Workaround: There is no workaround.

CSCsr86826

Symptoms: A standby SP may experience a memory leak in the mls-hal-agent process.

Conditions: This has been experienced on a Cisco 7600 router with dual SUP720s running either Cisco IOS Release 12.2(33)SRC or Cisco IOS Release 12.2(33) SRC1. The router is configured for multicast.

Workaround: There is no workaround.

CSCsr96042

Symptoms: ASR1000 Router crashes.

Conditions: Occurs if "ip vrf" is deleted from the configuration.

Workaround: There is no workaround.

CSCsr97343

Symptoms: An MSDP peer may flap randomly.

Conditions: The symptom is observed when the device is configured with logging host ip-address ... or logging host ip-address.

Workaround: It has been observed that removing the "logging host" configuration helps in preventing the peer-flap: no logging host ip-address no logging ip-address

CSCsr97753

Symptoms: Pinging an interface fails.

Conditions: Occurs when unconfiguring xconnect on the interface.

Workaround: Perform a shut/no shut on the the interface.

CSCsr98731

Symptoms: If running OSPF, stale routes may be installed in the RIB. Also wrong paths (inter-area vs intra-area) are preferred.

Conditions: Occurs on a router running Cisco IOS Release 12.2(33)SRC1.

Workaround: There is no workaround.

CSCsu04088

Symptoms: With unidirectional Ethernet (UDE) enabled on ES20 port, UniDirectional Link Detection (UDLD) gets disabled. But on converting the port from L3 to L2 (or vice versa) or on shut/no shut of interface, UDLD is enabled again on the interface. Once UDLD gets enabled, due to the UDE feature, the port is detected as unidirectional and put to err-disabled state.

Conditions: Occurs on ES20 ports configured for both UDE and UDLD.

Workaround: Disable UDLD on the port.

CSCsu04360

Symptoms: Acct-Time-Delay and Tunnel-Link-Stop records are missing from L2TP network server (LNS).

Conditions: Occurs when using radius server for authentication.

Workaround: There is no workaround.

CSCsu04473

Symptoms: Upon the first SSO switchover triggered with the redundancy force-switchover command, the traffic stops on the ATM N-to-1 VCC pseudowires configured with cell-packing in the direction from the MWR towards the 7600 SPA-4XOC3-ATM interface. Traffic recovers normally in the other direction.

Conditions: Occurs on a Cisco 7600 S-series equipped with dual SUP720-3BXL. The problem is seen only when cell-packing is enabled on the N-to-1 VCC pseudowires and when APS (MR-APS) is configured on the ATM OC3 interface of the Cisco 7600 SPA-4XOC3-ATM.

Workaround: Disable cell-packing on the ATM N-to-1 VCC pseudowires or alternatively disable APS on the SPA-4XOC3-ATM interface.

CSCsu05525

Symptoms: After removing the "default-originate" configuration, the default-route is not withdrawn.

Conditions: Occurred on a router running Cisco IOS Release 12.2SR.

Workaround: Clear the session to remove the configuration.

CSCsu08935

Symptoms: BGP as-override does not work properly on a PE to overwrite the AS in the AS4_PATH.

Conditions: When a 4 byte CE is peered to a 2 byte capable PE using AS 23456 and the command as-override is configured on the neighbor, the PE router does not override the AS in the AS4_PATH with its own AS number, mapped to 4 bytes.

Workaround: Use "allowas-in" on the CE.

CSCsu10229

Symptoms: cdpCacheAddress(OID:1.3.6.1.4.1.9.9.23.1.2.1.1.4) MIB is not showing GLOBAL_UNICAST address.

Conditions: Occurs on a Cisco 7200 router running Cisco IOS Release 12.4(15)T7.

Workaround: There is no workaround.

CSCsu12040

Symptoms: BGP neighbors that are configured with as-override and send-label (CsC) together may not work after an interface flap or service reset.

Conditions:

neighbor xxx as-override neighbor xxx send-label

Workaround: Enter the "clear ip bgp * soft in" command.

Further Problem Description: Peers (neighbors) with a CsC (IPv4+label) BGP configuration with the as-override option should be separated into different dynamic update groups during the BGP update generation process. After the CSCef70161 fix in Cisco IOS Release 12.0(32)SY4, this is no longer the case; this CSCsu12040 fix enhances the CSCef70161 fix to handle the CsC (IPv4+label) case separately.

CSCsu24087

Symptoms: A router hangs for a couple of minutes, then crashes anytime the clear ip bgp neighbor x.x.x in command is issued.

Conditions: This symptom occurs when a router crashes when the clear ip bgp neighbor x.x.x.x soft in command is issued when the following commands are configured for that neighbor (without route-map): 1) neighbor x.x.x.x soft-reconfiguration inbound 2) neighbor x.x.x.x weight 3) neighbor x.x.x.x filter-list in

If any one of the commands is not configured, then the router will not crash.

Workaround: Configure route-map instead of filter-list for inbound direction. For example: "neighbor x.x.x.x filter-list 1 in" replace with "neighbor x.x.x.x route-map name in"

where, route-map name permit 10 match as-path 1

CSCsu27109

Symptoms: When stateful switchover (SSO) is performed on a Cisco 7600, MPLS label allocation fails.

Conditions: Issues are seen on Cisco 7600 router. Occurs after performing the SSO. Also seeing CPU usage above 95% for 10-15 minutes.

Workaround: There is no workaround.

CSCsu27888

Symptoms: IGMP v3 reports are discarded.

Conditions: Occurs on Cisco 7200 router running Cisco IOS Release 12.4(20)T2.

Workaround: There is no workaround.

CSCsu27894

Symptoms: Flurry of DUP_IFINDEX messages are seen on standby.

Conditions: Occurs during bulk sync phase when standby is coming up.

Workaround: There is no workaround.

CSCsu31088

Symptoms: Not able to execute any commands under interface after running BERT tests.

Conditions: This issue is seen only after running SPA FPGA BERT tests and also when there is dual RP in chassis. With other BERT options, no issue is seen.

Workaround: There is no workaround.

CSCsu31935

Symptoms: Bootup diag test failures observed on 6816 card when multirouters are reloaded. Some ports were put in error disabled state.

Conditions: Failure trigerred with random multirouters reloads (reload of CE1, PE1, Core1). Brief router info and config: IOS - 8/25 a76 Dual sup720 7606 6724 connected to remote 6724 (servicing vlans 2-2000) 6816 connected to remote 6816 (servicing vlans 2001-4000) sip600 (servicing vlans 1-4000 switchport)

Topology:

CE1----PE1----Core-1-----Core-2----PE2----CE2 Affected router is CE1.

Configuration: 4k VLANs, 6816 servicing VLANs 2001-4000 (switchports).

Workaround: Run the failing diag tests on demand.

Further Problem Description: Few bootup tests fail when on 6816 card when the multirouters are reloaded. On failure, the ports are put in error disabled state. Failure cause has been root caused to usage of reserved diag vlans in the configs. Please refer the link mentioned below.

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.1E/native/command/reference/S1.html

switchport dot1q: Do not enable the reserved VLAN range (1006 to 1024) on trunks when connecting a Catalyst 6500 series switch running Cisco IOS software on both the supervisor engine and the MSFC to a Catalyst 6500 series switch running Catalyst software. These VLANs are reserved in systems running Catalyst software. If enabled, systems running Catalyst software may error disable the ports if there is a trunking channel between these systems

When the diag vlans (1006 to 1011, 4094 to 4089) are used, there could be diag failures at some random cases. Please do not enable the reserved vlans.

CSCsu31954

Symptoms: A router reloads.

Conditions: Under certain crypto configurations with NetFlow also configured, the router will reload when required to fragment CEF-switched traffic on a Cisco 7200 router.

Workaround: There is no workaround.

CSCsu35597

Symptoms: Renaming a directory gives error message.

Conditions: This happens on a Cisco router running Cisco IOS Release 12.4(20)T1.fc2 image

Workaround: There is no workaround.

CSCsu35624

Symptoms: When a private VLAN is configured on a VTPv3 server and then deleted, the update message on a peer VTPv3 client can cause a stack overflow for VLAN manager process and crash.

Conditions: Occurs in a Cisco 7600 running Cisco IOS Release 12.2(33)SRD.

Workaround: There is no workaround.

CSCsu36697

Symptoms: The line card reloads when a line card online insertion and removal (OIR) is performed. It does not happen consistently.

Conditions: This occurs when an empty policy is present.

Workaround: There is no workaround.

CSCsu36709

Symptoms: A router may unexpectedly reload.

Conditions: The symptom is observed specifically with a configuration of Enhanced Interior Gateway Routing Protocol (EIGRP) that is used to redistribute BGP routes. Plain EIGRP is not affected.

Workaround: Do not use EIGRP to redistribute BGP.

CSCsu37205

Symptoms: BGP dampening under VPNv4 may cause router crash.

Conditions: Occurs when BGP dampening is enabled on VPNv4 address family, but not on individual IPv4 VRF<VRF-name>address-family.

Workaround: Enable the same set of BGP dampening on both the VPNv4 address family as well as all entries for IPv4 VRF address-family.

CSCsu39152

Symptoms: IF-MIB registration fails as there are no free ifIndex available.

Conditions: Occurs after an upgrade. Seen only in HA systems.

Workaround: There is no workaround.

CSCsu39704

Symptoms: Unable to configure pseudowire on virtual-PPP interface. Command is rejected with the following error:

Incompatible with ip address command on Vp1 - command rejected

Conditions: Occurs when IPv4 address or IP VPN routing/forwarding (VRF) has already been configured on the main interface.

Workaround: There is no workaround.

CSCsu40667

Symptoms: A Cisco 7600 series router may fail to install some NetFlow entries even if NetFlow table utilization is low.

Conditions: Occurs while flows are ingressing on ES20 module.

Workaround: There is no workaround.

Further Problem Description: The show mls netflow table-contention detail command will show a heavy ICAM table utilization, while TCAM utilization is small.

Router#sh mls net table-contention det

Earl in Module 1

Detailed Netflow CAM (TCAM and ICAM) Utilization

================================================

TCAM Utilization : 0%

ICAM Utilization : 98%

Netflow TCAM count : 152

Netflow ICAM count : 126

Netflow Creation Failures : 388663

Netflow CAM aliases : 0

CSCsu42315

Symptoms: When the L3VPN prefix uses a tunnel with fast reroute (FRR) protection, there is traffic loss during reoptimization.

Conditions: Not all prefix in the VRF will observe this issue. This is seen only when there are more than 250,000 prefixes.

Workaround: There is no workaround.

Further Problem Description: Traffic loss during re-optimization can be due to faster tunnel cleanup also. It is advisable to configure mpls traffic-eng reoptimize timers delay cleanup <seconds> to fine tune the cleanup according to the topology.

CSCsu44992

Symptoms: VPDN redirect functionality does not work.

Conditions: Basic functionality is broken. No special condition is required.

Workaround: There is no workaround.

CSCsu46822

Symptoms: When account logon is done for a DHCP user, QoS policies defined in the user profile are not applied to the ISG session.

Conditions: A DHCP session is created. User performs account logon via SESM (not CoA). User profile has QoS polices defined. Session is authenticated but policies are not applied to the session.

Workaround: Perform account logon using CoA.

CSCsu46871

Symptoms: Unable to attach service policy to VT when bandwidth is configured in class default.

Conditions: Occurs when DLFI over ATM is configured while trying to attach service policy to VT when bandwidth is configured in class default.

Workaround: Configure bandwidth in user defined class and attach to VT.

CSCsu47037

Symptoms: Router crashes when an attempt is made to forward a packet out of an Auto-Template interface.

Conditions: This occurs when the interface's MTU is set to 0: Use the show interface Auto-Template X command to show the MTU.

Workaround: Configure a protocol MTU directly on the Auto-Template interface.

CSCsu48898

Symptoms: A Cisco 10000 series router may crash every several minutes.

Conditions: The symptom is observed with a Cisco 10000 series router that is running Cisco IOS Release 12.2(31)SB13.

Workaround: Use Cisco IOS Release 12.2(31)SB11.

CSCsu50118

Symptoms: More convergence time seen even with the carrier-delay msec 0 command configured.

Conditions: Occurs when carrier-delay msec 0 is configured on a gigabit interface.

Workaround: If excessive convergence time is observed even with the carrier-delay msec 0 command configured, enter the command again on the interface.

CSCsu51095

Symptoms: If connected routes are optimized using PfR, there will be a routing loop.

Conditions: This symptom can occur if, for some reason, PfR is learning connected routes or if the user has configured them.

Workaround: Create an oer-map with a prefix-list that contains the prefixes with the IP addresses of the connected routes (the next hops). Set the set observe mode in the oer-map.

CSCsu51245

Symptoms: Port-channel QinQ subinterface on ESM20 and SIP600 line cards do not pass traffic after router reload and line card reset.

Conditions: This condition is seen after router reload or member link line card reset. This is not seen when configuration is newly applied.

Workaround: To recover from the condition, perform a shut/no shut on the port channel main interface.

CSCsu54801

Symptoms: IPv6/IPv6 Tunnel adjacency information is incomplete on the line card. This prevents IPv6/IPv6 multicast traffic on the tunnel.

Conditions: The symptoms are observed under normal operation.

Workaround: There is no workaround.

CSCsu55145

Symptoms: Router crashes due to critical software exception.

Conditions: Occurs on a Cisco ASR 1000 running Cisco IOS Release 12.2.

Workaround: There is no workaround.

CSCsu55883

Symptoms: With MLPPP configured on OSM, the following symptoms may be observed:

1. Line card might crash.

2. Links might flap.

3. Following error message from line card might be seen: "SLOT 9: Sep 14 13:48:48.479 CDT: %COMMON_FIB-3-FIBIDBINCONS2: An internal software error occurred. Multilink1 linked to wrong idb R11_Mu1"

Conditions: Occurs on routers running various Cisco IOS Release 12.2SR releases. Performing a shut/no shut on the OSM (especially on the card containing MLPPP) interfaces might trigger this issue.

Workaround: There is no workaround.

CSCsu57331

Symptoms: In a Virtual Private LAN Services (VPLS) scenario with ESM20 as core facing interface, imposition traffic might fail.

Conditions: Occurs only when ports from Bay 1 are used as core facing interface.

Workaround: Reset the line card.

CSCsu57958

Symptoms: In a scenario where a Catalyst 6500 or Cisco 7600 performs DHCP snooping + DAI functionality and a second device acts as DHCP relay, it was observed that DHCP snooping database was not populated. DHCP snooping is configured in this case on the ingress VLAN (traffic from the DHCP clients) and the DHCP server can be reached on a different egress VLAN (DHCP requests are routed ).

DHCP Replies from the server (DHCPOFFER and DHCPACK) are not snooped by the Catalyst 6500 or Cisco 7600 and so bindings are not established. Consequence is that clients will get their own IP Address but ARP Inspection will fail because bindings were not learned on the device.

Conditions: Occurs with DHCP Snoooping + DAI configured on a Catalyst 6500 or Cisco 7600 in a routed scenario (Ingress VLAN and Egress VLAN are different) and DHCP Relay performed by a different device.

Workaround: Configure DHCP Snooping on both client and server side VLANs. Problem is applicable to both Cisco IOS Release 12.2(18)SXF and Cisco IOS Release 12.2(33)SRB.

CSCsu62667

Symptoms: LSP ID change after stateful switchover (SSO) due to failure in signaling recovered label switched path (LSP).

Conditions: Occurs following a SSO switchover.

Workaround: There is no workaround.

CSCsu63996

Symptoms: NSF restart may be terminated and OSPF NBR may flap during RP switchover. The debug ip ospf adj command shows the following message: OSPF: Bad request received.

Conditions: The symptoms are observed when the links are broadcast networks and the restarting router is DR. It is seen when "nsf cisco" is configured and when some neighbors finish OOB resync much sooner than others.

Workaround: Use the nsf ietf command.

Alternate workaround: Configure routers so that the restarting router is not DR (use ospf network type point-to-point or priority 0).

CSCsu64215

Symptoms: Router may incorrectly drop non TCP traffic. TFTP and EIGRP traffic can be impacted as seen in CSCsv89579.

Conditions: Occurs when the ip tcp adjust-mss command is configured on the device.

Workaround: Disable ip tcp adjust-mss on all interfaces. Note that this may cause higher CPU due to fragmentation and reassembly in certain tunnel environments where the command is intended to be used.

CSCsu65189

Symptoms: If router is configured as follows:

router ospf 1 ... passive-interface Loopback0