Cisco ASR 903, Руководство пользователя, Страница: 237 / 280

51
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Caveats in Cisco IOS XE 3.9S Releases
Symptoms: classification not works properly with non-matching traffic when IP acl is used.
Conditions: This occurs only if we have classes based on acl match. only acl class will classify
properly and other classes based on dscp or class-default wont work
Workaround: No known workaround
• CSCue00332
Symptom: BFD connections flap, bringing down IGP.
Conditions: Occurs when you enable BFD on an interface that is flapping.
Workaround: There is no workaround.
• CSCue01419
Symptoms: EIGRP neighborship is lost on OC3IM / OC12 IM interfaces configured on port 0.
Conditions: Seen only for interfaces which are configured on port 0 of OC3IM or OC12 IM. Not
seen on ports 1,2 or 3.
Workaround: Perform a shut/no shut on interfaces configured on port 0. Alternatively remove
EIGRP and configure again.
• CSCue01919
Symptoms: Enhancement to L2 protocol tunnelling feature to forward/drop more protocols and
reserved mac addresses that are under IEEE wellknown mac address range (0180C2000002-0F) as
a part of CE2.0 certification.
Conditions: This the L2 protocol tunnelling enhancement for CE2.0 certification.
Workaround: There is no workaround.
• CSCue03418
Symptoms: The router displays OSPF protocol flaps causing a 20–30 second traffic loss.
Conditions: The issue occurs very intermittently on a HA system with a 6 second dead-interval
value when you issue the redundancy force-switchover command;
Workaround: Increase the dead-interval value.
• CSCue05962
Symptoms: Cos/Vlan Classification doesn’t work on port channel member links
Conditions: Apply a Cos based Qos policy on port-channel member links. All the packets will start
flowing through class default instead of getting classified on the interface. Look at the attached
console logs for configs details.
Workaround: None
• CSCue07849
Symptoms: Link failure in L3VPN core takes a long time (in 10s of seconds) to converge even with
BGP PIC enabled.
Conditions: 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 + Edge configuration. If these 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.