47
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-12
Chapter
Caveats in Cisco IOS XE 3.7S Releases
–
The IPv6 ACLs and IPv4 ACLs have the same names
Workaround: Create IPv4 ACLs with different names from the IPv6 ACLs.
• 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.
• CSCud40930
Symptom: Some interfaces within a bridge-domain are unable to send outbound L3 multicast
traffic.
Conditions: Occurs when the bridge-domain contains EFP interfaces, some of which are on a
port-channel. The issue can also occur after a router reload.
Workaround: Issue a shutdown/no shutdown on the BDI interface.
• CSCud44768
Symptom: Multilink bundles and member links flap when passing traffic.
Conditions: Occurs under the following conditions:
–
You configure more than 210 MLPPP bundles with one member link per bundle or 16 bundles
with 16 member links each.
–
The line is operating at a 64 or 128 byte line rate
Workaround: There is no workaround.
• CSCud44942
Symptom: The router does not learn remote Connectivity Fault Management (CFM) Maintenance
Endpoint (MEPs).
Conditions: Occurs when you configure a MEP on an interface.
Workaround: There is no workaround.
• CSCud45336
Symptom: The router displays CPU hog error messages and crashes.
Conditions: Occurs when you reload the router a high number of Structure-agnostic TDM over
Packet (SAToP) pseudowires.
Workaround: There is no workaround.
• CSCud49749
Symptom: Copper Ethernet interface module (IM) ports remain in a suspended state after stateful
switchover (SSO).
Conditions: Occurs when you create a port-channel with
–
Two links from a copper Ethernet interface to another copper Ethernet interface
–
One link from a copper Ethernet interface to an SFP Ethernet interface
Workaround: Issue a shutdown/no shutdown on copper-to-copper connection interfaces.