
23
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-12
Caveats in Cisco IOS XE 3.9S Releases
Symptom:
VC Counters do not increment On IM OIR followed by SSO.
Conditions:
This is seen on HA system when IM OIR is followed by SSO switchover is performed.
Workaround:
There is no workaround.
•
CSCuf64704
Symptom:
“%MPLS-3-OUT_OF_LABEL3_SPACE: SIP0: nile_mgr: Out of resource to create”
labels errors are seen on the console.
Conditions:
This issue is seen with scaled configurations, when LDP peer goes down and recovers.
Workaround:
Reduce the scale.
•
CSCuf65040
Symptom:
The 1G or 10G IM may go in out of service state after a hard OIR of the IM.
Conditions:
This issue occurs after a hard OIR is performed.
Workaround:
Perform a another hard OIR or a SSO switchover followed by a soft OIR.
•
CSCuf66022
Symptom:
The 10 Gigabit Ethernet interface status goes down on one side.
Conditions:
This issue occurs after shutting down the Ten Gigabit Ethernet interface and SSO is
performed.
Workaround:
Perform a
shutdown
followed by a
no shutdown
10 Gigabit Ethernet interface
•
CSCuf74072
Symptom:
Seeing CRC errors on SFP IM with CU SFP.
Conditions:
This issue occurs when the CU SFP is configured with 100Mbps speed.
Workaround:
There is no workaround.
•
CSCuf83316
Symptom:
Traffic loss of more than 1sec was observed during router reload.
Conditions:
This issue occurs on issuing
reload
command in middle router with R-LFA in RING
topology.
Workaround:
There is no workaround.
•
CSCuf83453
Symptom:
The
show ethernet service instance
stats
command displays "0" at Egress stats
counters.
Conditions:
This issue is seen after using
show platform hardware pp active asic stats
command.
Workaround:
Reload the router.
•
CSCuf83886
Symptom:
Label exhaust message is seen even on valid case if policy is configured before xconnect
is configured on scaled configuration.
Conditions:
This issue occurs when a service-policy is configured before configuring xconnect on
the router that has consumed close to max labels.
Workaround:
First configure xconnect and then configure service-policy