24
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Caveats in Cisco IOS XE 3.9S Releases
Conditions: This issue occurs when BGP PIC core and PIC edge is configured and there are more
than one ECMP core paths to reach backup BGP peer.
Workaround: Configure only one core path to reach both primary and repair BGP Peers in a BGP
PIC Core and Edge configuration. If there are more than one equal cost physical paths to reach BGP
peers, then adjust the configuration by increasing the distance for all paths except one.
• CSCug44908
Symptom: Traffic goes down after applying policy-map without ingress classification.
Conditions: This issue occurs when without classifying the traffic in the Ingress, this policy map is
applied in the egress port.
Workaround: Edit the policy map by changing the bandwidth percentage number.
• CSCug45557
Symptom: Ingress marking does not work when Egress marking has a match on qos-group.
Conditions: This issue occurs when ingress marking is not working when Egress marking matches
on qos-group.
Workaround: There is no workaround.
• CSCug45618
Symptom: OSPF does not come up with policy map having 2 different EFP classes and configured
on 2 different interfaces.
Conditions: This issue is observed only when same policy map is applied on 2 interfaces with one
EFP in the policy map.
Workaround: Remove the policy map from one of the interfaces to bring up the OSPF.
• CSCug46010
Symptom: The non IP packets get classified under the second class instead of class-default when
two class-maps one having match on L4 ACL and other having match on L3 ACL with permit ip any
any is configured.
Conditions: This issue occurs when two class-maps one matching on L3 ACL match and another
matching on TCP or UDP are configured.
Workaround: There is no workaround.
• CSCug46157
Symptom: When an existing policer is deleted and added back, the policer fails to take effect.
Conditions: This issue occurs when the policing was dynamically deleted and added.
Workaround: Remove the policy-map and re-apply on the interface or EFP.
• CSCug57503
Symptom: ESP crash observed on the router.
Conditions: This issue occurs after executing the show platform hardware qfp command on the
active feature packet-trace configuration.
Workaround: Do not execute unsupported command.
• CSCug61357
Symptom: The ISIS router fails to come up after issuing a shutdown followed by a no shutdown
command.
Conditions: This issue occurs when RLFA and BFD configutations exist on the router.
To Next Page
Loading...
Need help?
General
