
24
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-12
Chapter
Caveats in Cisco IOS XE 3.8S Releases
•
CSCua95873
Symptoms:
The router continues passing traffic on the OC-3 interface after you shut down the
controller.
Conditions:
Occurs when you shut down the OC-3 controller; the router momentarily continues to
increment interface counters.
Workaround:
There is no workaround.
•
CSCub73405
Symptom:
Cisco ASR903 router can experience latency for process-switched traffic and display
high CPU utilization at nile_mgr.
Conditions:
Occurs on an ASR 903 with redundant RSPs after you reload the standby RSP.
Workaround:
Reboot the router.
•
CSCub78861
Symptom:
Following a reload, the router handles CFM only on 128 VLANs or bridge-domains.
Conditions:
Occurs when the router configuration contains CFM and more than 128 VLANs or
bridge-domains.
Workaround:
There is no workaround.
•
CSCub79869
Symptom:
BGP PIC edge convergence time is high.
Conditions:
Occurs in a 3-label stack setup using LDP, BGP, and VPN labels.
Workaround:
There is no workaround for a stack using 3 labels. However, the issue does not occur
when you use 2 labels.
•
CSCub98691
Symptom:
The router displays an I2C write fail error message.
Conditions:
The issue can occur when the router is idle or when the router is loaded and passing
traffic.
Workaround:
There is no workaround. However, the issue does not have any functional impact.
•
CSCuc01154
Symptom:
The router does not report B1, B2, and B3 alarms at normal thresholds.
Conditions:
Occurs on the OC-3 interface module when the router sends errored frames.
Workaround:
There is no workaround.
•
CSCuc41763
Symptom:
The router displays a RUNHOG traceback error message.
Conditions:
Occurs when you reload the router or an interface module.
Workaround:
There is no workaround.
•
CSCuc51051
Symptom:
Remote LFA FRR convergence takes more than 50 milliseconds.
Conditions:
Occurs after you reload the router.
Workaround:
Reset the interface on the primary path.