
24
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Chapter
Caveats in Cisco IOS XE 3.7S Releases
•
CSCud07642
Symptom:
The ASR 903 router is unable to pass traffic to the ASR 9000.
Conditions:
Occurs with a clear-channel ATM over MPLS configuration using AAL0
encapsulation.
Workaround:
Enable MPLS control-word on the ASR 9000.
•
CSCud09632
Symptom:
The router does not correctly update the J0 byte on the OC-3 or OC-12 interface module.
Conditions:
Occurs in a back-to-back configuration with two ASR 903s passing SONET traffic.
Workaround:
There is no workaround.
•
CSCud15785
Symptom:
The router experiences flapping on REP connections.
Conditions:
Occurs under the following conditions:
–
MAC limiting is enabled and a MAC address is at the maximum value
–
REP is configured with a 200 millisecond LSL ageout timer
Workaround:
Increase the REP timer to above 500 milliseconds or disable the MAC limiting
feature.
•
CSCud15841
Symptom:
The
clear ip mroute
* command causes resource leakage.
Conditions:
Occurs when you issue the
clear ip mroute
* command while IP multicast is enabled.
Workaround:
Reload the router.
•
CSCud17457
Symptom:
The router drops IP multicast traffic.
Conditions:
Occurs when you perform the following actions:
–
Configure EFPs as members of a port channel containing a single interface.
–
Remove the configuration for the EFPs
–
Remove the interface from the port channel
–
Add the EFPs back onto the interface
Workaround:
Reload the router or issue a stateful switchover (SSO).
•
CSCud23698
Symptom:
The router stops applying classification and marking for a class.
Conditions:
Occurs when you remove a priority level while using dual priority for the
class-map.
Workaround:
Remove and reattach the policy-map on the interface.
•
CSCud28982
Symptom:
The router does not process egress CoS marking on an Ethernet service instance.
Conditions:
Occurs when you configure QoS on an Ethernet service instance that is a member of a
bridge-domain and uses dot1q encapsulation.
Workaround:
There is no workaround.