26
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-12
Chapter
Caveats in Cisco IOS XE 3.10S Releases
• CSCue36239
Symptom: Match EFP policy on a port channel stops working after one of the policies on the
member links is removed.
Conditions: This issue is observed when you attach a policy to all the member links on the port
channel, remove it from one of the member links from which traffic flows.
Workaround: Remove policies from all the member links and reattach the policies.
• CSCue39978
Symptom: Traffic stops in ATM PVP after performing an IM OIR followed by SSO.
Conditions: This issue is observed after performing an IM OIR followed by SSO when ATM PVP
is configured.
Workaround: Reload the router.
• CSCue43250
Symptom: IMA configuration is not parsed correctly after a router reload when the A903-IM40S
module is inserted in Bay4 or Bay5 of the Cisco ASR 903 router.
Conditions: This issue is observed when the IMA and ATM interfaces are adjacent. It happens only
if the IM is inserted on Bay 4 or above.
Workaround: Insert the IM in bay 0 or bay 3 if you want the IMA and ATM parsing to work.
Alternatively, reconfigure the ATM and IMA interfaces.
• CSCue45274
Symptom: Traffic drop is seen on a port for more than 8 minutes when a BDI, which is not part of
this new port is shut down.
Conditions: This issue is observed when a BDI is shut down and another port which is not a part of
the shut down BDI port join the multicast group.
Workaround: There is no workaround.
• CSCue45306
Symptom: The CEM circuits that are configured over TDM IM go down after performing an SSO.
Conditions: This issue is observed when you perform an SSO, the CEM circuits that are configured
over TDM IM go down.
Workaround: Reload the router.
• CSCue47834
Symptom: IOMd crashes and IM goes out of service during SSO.
Conditions: This issue is observed when you have ATM and IMA configured and perform an SSO.
IOMd crashes and the IM goes out of service.
Workaround: There is no workaround.
• CSCue54997
Symptom: The system accepts two input clock sources from the same OC3 IM although the system
supports only one input clock source per OC3 IM. This results in clock failures.
Conditions: This issue is observed when two input clock sources are accepted from the same OC3
IM although the framer on the IM can support only one clock source.
Workaround: Do not configure the second input clock source from the same OC3 IM.
Alternatively, remove both OC3 clock sources and configure the desired OC3 controller.