
6
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Chapter
Caveats in Cisco IOS XE 3.10S Releases
•
CSCug70182
Symptom:
The ASR903-IMA8S port remains up without the fiber.
Conditions:
This issue occurs when the GLC-FE-100FX optic is used.
Workaround:
There is no workaround.
•
CSCug96284
Symptom:
Memory leaks seen on boot up of the router.
Conditions:
This issue occurs on booting the system.
Workaround:
There is no workaround.
•
CSCuh00108
Symptom:
CMAND crash seen on the router.
Conditions:
This issue occurs during midplane idprom read at bootup.
Workaround:
Reload the router.
•
CSCuh03023
Symptom:
IP connectivity over BDI fails after a link flap network event.
Conditions:
This issue occurs intermittently with BDI enabled for IP/MPLS forwarding and
running VPN services over it. Adjacency failures are seen after couple of link flap events, which
impacts Layer3 forwarding over BDI.
Workaround:
There is no workaround.
•
CSCuh13883
Symptom:
Standby IOMD crashes continuously at system bootup.
Conditions:
This issue occurs at system bootup and when the system waits for a user input at the
initial dialog box during configuration.
Workaround:
There is no workaround.
•
CSCuh16707
Symptom:
The interface module (IM) status LED glows green before the PHY Init state is complete.
Conditions:
This issue occurs after an IM OIR is performed.
Workaround:
Use the
show platform
command output to check if the IM reaches the OK state.
•
CSCuh42926
Symptom:
High CPU utilization is seen when Trunk EFP is configured on port channel and MAC
address table limit is configured on the bridge domain.
Conditions:
This issue occurs when Trunk EFP is configured on port channel and MAC address
table limit is configured on the bridge domain.
Workaround:
Do not use port channel.
•
CSCuh46103
Symptom:
BDI statistics not getting incremented on the router.
Conditions:
This issue occurs when the ingress and egress statistics displayed using
show interface
bdi
or the
show int bdi statistics
command does not get incremented even if the traffic is flowing
through the BDI interface.
Workaround:
Use
show platform hardware pp active interface statistics bdi
command to view
the statistics.