19
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Caveats in Cisco IOS XE 3.9S Releases
• CSCue51682
Symptom: The REP protocol flaps, as indicated by the following error messages:
*Feb 8 06:51:38.857: %REP-4-LINKSTATUS: GigabitEthernet0/0/1 (segment 10) is
non-operational due to neighbor not responding
*Feb 8 06:51:39.096: %REP-4-LINKSTATUS: GigabitEthernet0/0/1 (segment 10) is
operational.
Conditions: Occurs under the following conditions:
–
The router is sending traffic using the incremental MAC address table
–
Fast LSL is configured using a 200ms timer.
–
The router is configured with more than 2000 MAC addresses.
Workaround: Remove fast LSL from the REP configuration.
• CSCue54649
Symptom: Traceback is seen on new active RSP console after performing a SSO.
Conditions: This issue is seen when OC-3 IM is configured on OC-12 mode. The POS and serial
interfaces mayor may not be configured.
Workaround: There is no workaround.
• CSCue61803
Symptom: IMs do not get powered off when router is reloaded.
Conditions: This issue is seen occasionally on reload.
Workaround: There is no workaround.
• CSCue65149
Symptom: OBJ messages are observed when changing the interval in EVC BD offload cases (scale).
Conditions: This issue occurs when 3.3ms session interval and MEPS is configured on the router
and then the MEPS and domain configuration is removed and a session interval of 10ms interval is
configured.
Workaround: Configure a low session interval.
• CSCue66137
Symptom: The IOMD crashes with CPU hog messages.
Conditions: This issue occurs with OC-3 interface module and traffic is sent over a multilink bundle
with packet size greater than 600 byte.
Workaround: There is no workaround.
• CSCue73478
Symptom: Standby RSP Sync LED become holdover after switchover.
Conditions: This issue occurs after a switchover.
Workaround: There is no workaround.
• CSCue77596
Symptom: Cos value gets wrongly marked for a QinQ packet
Conditions: This issue occurs on a service instance with dot1q encapsulation and no rewrite is
configured on the interface.The policy map attached in the ingress has marking in it.
Workaround: There is no workaround.