Specifications

1038
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
Conditions: This symptom is observed when you reload a Cisco platform and when the interfaces
were in the up/up state before you reloaded the platform.
Workaround: Enter the shutdown command followed by the no shutdown command on the
controller of either the T3 line card or port adapter on the Cisco platform or on the T3 line card or
port adapter on the platform at the remote end.
Alternate Workaround: Enter the shutdown command followed by the no shutdown command on
the main interface on the Cisco platform.
• CSCin74070
Symptoms: Performance degrades when the number of VCs through which traffic is sent is scaled
for PCRoMPLS AToM VCs.
Conditions: This symptom is seen on a Cisco 7500 series with a PCRoMPLS configuration on VCs.
Workaround: There is no workaround.
• CSCin76595
Symptoms: A Cisco 7500 series may show a large number of tracebacks of the “64bit read” access
type on a VIP.
Conditions: This symptom is observed on a Cisco 7500 series that runs Cisco IOS Release 12.2 S or
Release 12.3 when the VIP contains a PA-POS-OC3, PA-POS-2OC3, or PA-SRP-OC12.
Workaround: There is no workaround.
IP Routing Protocols
• CSCea59206
Symptoms: When you configure the distribute-list router configuration command under the
address-family ipv4 vrf vrf name router configuration command, the distribute-list router
configuration command may appear under the main routing process as may be displayed in the
output of the show running-config EXEC command.
Conditions: This symptom is observed in either a Routing Information Protocol version 2 (RIPv2)
or a Border Gateway Protocol (BGP) configuration when you specify the interface-type and
interface-number arguments of the distribute-list {access-list-number | access-list-name} {in |
out} [interface-type interface-number] router configuration command.
The symptom does not occur when you do not define the interface-type and interface-number
arguments and only enter the distribute-list {access-list-number | access-list-name} {in | out}
router configuration command.
Workaround: There is no workaround.
• CSCed33044
Symptoms: ARP may not function properly on the remote side of point-to-point Fast Ethernet link
with a default static route until the remote side is pinged.
Conditions: This symptom is observed on a Cisco router when ARP and /31 mask are configured on
a point-to-point link Fast Ethernet link with a default static route. The symptom is
platform-independent.
Workaround: There are four different workarounds:
– Use a /30 netmask on the point-to-point Fast Ethernet connection.
– Configure a static ARP entry for the remote side of the Fast Ethernet link.