
25
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Chapter
Caveats in Cisco IOS XE 3.7S Releases
•
CSCud30806
Symptoms:
The router accepts a QoS WRED configuration containing
match-all
configurations for
two different
prec
values, which is not supported.
Conditions:
Occurs when you configure a policy with a class-map containing
match-all
configurations for two different
prec
values.
Workaround:
There is no workaround.
•
CSCud33298
Symptom:
The router crashes.
Conditions:
Occurs when the peer device shuts down.
Workaround:
There is no workaround.
•
CSCud34346
Symptom:
The router crashes.
Conditions:
The issue can occur when:
–
The router is configured with multiple ECMP paths
–
MPLS IP is not enabled on one of the ECMP paths
Workaround:
There is no workaround.
•
CSCud35689
Symptoms:
The router accepts a queue-limit configuration at the parent level of a policy or at the
Vlan class/ port level. This configuration is not supported.
Conditions:
Occurs when you add a queue-limit configuration on a policy at the parent level or at
the vlan class/ port level.
Workaround:
There is no workaround.
•
CSCud37927
Symptoms:
The router does not learn remote Connectivity Fault Management (CFM) Maintenance
Endpoint (MEPs).
Conditions:
Occurs when the router is passing REP or STP traffic and one port is in an ALT or BLK
state.
Workaround:
There is no workaround.
•
CSCud38164
Symptom:
The router displays an object download failure message on the console.
Conditions:
Occurs when the number of ip routes reaches its maximum configurable limit.
Workaround:
There is no workaround.
•
CSCud38433
Symptom:
The router is unable to establish MPLS neighborship or ping the destination loopback
interface.
Conditions:
Occurs when you configure two Equal Cost Multipath (ECMP) paths on a bridge
domain interface (BDI) using static routes.
Workaround:
The following workarounds exist:
–
Use Interior Gateway Protocol (IGP) instead of static IP routes.
–
Shut down one of the ECMP paths.