10
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-12
Caveats in Cisco IOS XE 3.9S Releases
•
CSCug05239
Symptom:
Traffic drops on the router.
Conditions:
This issue occurs when configuring multichassis Link Aggregation Control Protocol
(MLACP) switchover with Ethernet over Multiprotocol Label Switching (EOMPLS).
Workaround:
Configure port channel with EOMPLS.
•
CSCug10116
Symptom:
Traffic and ping do not flow through ATM interfaces on multiple controllers.
Conditions:
Series of
shutdown
and
no shutdown
commands on the controller or interface lead to
the failure.
Workaround:
There is no workaround. To recover from failure, perform an IM OIR.
•
CSCug18185
Symptom:
When the interfaces comes up after bootup, traffic received on the Cisco ASR 903 Router
serial interfaces are not switched to the BDI connected to Ixia.
Conditions:
This issue occurs when ARP resolution of the Ixia connected interface IP address fails.
Workaround:
Ping the Ixia port connected to the Cisco ASR 903 Router from another router
connected to the Cisco ASR 903 Router using Gigabit Ethernet interface.
•
CSCug18630
Symptom:
When you perform an OIR on the standby and active RSPs, CMAND crashes.
Conditions:
This issue is observed after performing multiple standby OIRs and bringing the
standby machine up.
Workaround:
There is no workaround.
•
CSCug21145
Symptom:
When system crashes, sometimes core files are generated with CRC errors.
Conditions:
This issue occurs when the system crashes under stress conditions.
Workaround:
There is no workaround.
•
CSCug27073
Symptom:
Multicast replication is improper when 255 outgoing interfaces (OIF’s) are configured.
Conditions:
This issue occurs when:
–
Perfuming IM OIR (soft/hard)
–
Clearing MRoutes (sometimes)
–
Enabling/disabling IGMP Snooping
Workaround:
There is no workaround.
•
CSCug31414
Symptom:
Multicast traffic drops on changing interface configuration from TEFP to VPLS over
port channel (PoCH).
Conditions:
This issue occurs when converting a layer 2 interface to layer 3; and then configuring
IP PIM and IP address in quick succession.
Workaround:
Use
shutdown
and
no shutdown
command on the interface.
More Info:
The problem occurs only when the adjacency create notification is received earlier than
the convert to layer 3 notification.