40
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Caveats in Cisco IOS XE 3.9S Releases
Further Problem Description:
ASR903 when locked to internal free-running clock, then ASR903
PTP master function transmits clockclass value 14 which corresponds to holdover state instead of
58 which corresponds to free-running clock.
•
CSCuc64899
Symptom:
The router does not learn remote Connectivity Fault Management (CFM) Maintenance
Endpoint (MEPs).
Conditions:
Occurs on interfaces with an xconnect statement after a reload on a peer device.
Workaround:
Remove and re-apply the CFM configuration.
•
CSCuc66393
Symptom:
The router loses OC-3 interface configurations after an ISSU upgrade.
Conditions:
Occurs on OC-3 serial and POS interfaces after an ISSU software upgrade.
Workaround:
There is no workaround.
•
CSCuc66895
Symptom:
Layer 2 traffic loop seen in REP topology for a transient time, when the Cisco ASR 903
which is a part of the REP ring is reloaded.
Conditions:
This symptom is observed when the Cisco ASR 903 is part of an REP ring, and the box
is reloaded with saved REP configurations.
Workaround:
Traffic loop is transient, once REP convergence looping is stopped.
•
CSCuc68246
Symptom:
The standby IOMD crashes on booting up the standby RSP.
Conditions:
This symptom occurs when booting up the standby RSP with a configuration that is
already present.
Workaround:
Boot up the standby without any configurations and start configuration once the
standby has reached STANDBY_HOT state.
•
CSCuc68462
Symptom:
The router drops PTP traffic.
Conditions:
The issue occurs occasionally when you configure PTP slave clock to receive
VLAN-tagged traffic.
Workaround:
There is no workaround.
•
CSCuc70509
Symptom:
Packet rate counters i.e. packets per second is not cleared to 0 when interface goes down.
Conditions:
Applies to all TDM interfaces like serial , mlppp , POS , etc. Issue seen on controller
shut etc, not seen on interface shut.
Workaround:
None. Should be fixed now.
•
CSCuc71410
Symptoms:
Config sync failure but it doesn’t have much of an impact on the service
Conditions:
We have a mac limit configured with action as limit and when the configured limit is
exceeded, the standby comes up after the limit is hit
Workaround:
none