Cisco Cisco IOS Software Release 12.0 S Release Notes
2367
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(12)S
•
CSCdr73473
Removing and attaching a service policy under a traffic load might cause spurious memory access
errors and high CPU utilization on the Versatile Interface Processor (VIP). This spurious access
occurs at hqf_get_policymap().
errors and high CPU utilization on the Versatile Interface Processor (VIP). This spurious access
occurs at hqf_get_policymap().
Workaround: Stop background traffic before making configuration changes.
•
CSCdr74025
The spatial reuse protocol (SRP) line card on a Cisco 12000 series Internet router that is running
Cisco IOS Release 12.0(11.5)S might reload unexpectedly upon start-up. There is no workaround.
Cisco IOS Release 12.0(11.5)S might reload unexpectedly upon start-up. There is no workaround.
•
CSCdr75209
When Frame Relay fragmentation is configured after attaching a traffic-shaping service policy to a
large number of permanent virtual connections (PVCs), the service policy might not function
properly. Since Frame Relay fragmentation appears after “service-policy” in the configuration order,
there is a chance that this situation will occur after a system reload. The specific policy that fails is:
large number of permanent virtual connections (PVCs), the service policy might not function
properly. Since Frame Relay fragmentation appears after “service-policy” in the configuration order,
there is a chance that this situation will occur after a system reload. The specific policy that fails is:
policy-map fr-pvc
class class-default
shape average <cir>
service-policy llq-policy
Workaround: Configure service-policy after FR fragmentation, or add queue-limit to the traffic
shaping policy as follows:
shaping policy as follows:
policy-map fr-pvc
class class-default
shape average <cir>
queue-limit <n>
service-policy llq-policy
•
CSCdr75997
CSCdm94333, which was integrated in Cisco IOS Release 12.0(9.6)S, introduced a new version of
the Automatic Protection Switching (APS) protect group protocol that required both working and
protect routers to be upgraded simultaneously. The fix for CSCdr75997 relaxes this restriction by
supporting interoperability between systems that are running different versions of the APS protocol
so that working and protect can be upgraded independently.
the Automatic Protection Switching (APS) protect group protocol that required both working and
protect routers to be upgraded simultaneously. The fix for CSCdr75997 relaxes this restriction by
supporting interoperability between systems that are running different versions of the APS protocol
so that working and protect can be upgraded independently.
•
CSCdr80820
A Cisco 12000 series Internet router that is configured for distributed IP multicast might exhibit the
following error messages:
following error messages:
SLOT 8:03:43:10: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x402EB90C reading
0x0
SLOT 8:03:43:10: %ALIGN-3-TRACE: -Traceback= 402EB90C 402E779C 402E9AC4 402E9BA8
402E9388 4009B02C 4009B018 00000000
SLOT 8:03:43:10: %ALIGN-3-TRACE: -Traceback= 402EB910 402E779C 402E9AC4 402E9BA8
402E9388 4009B02C 4009B018 00000000
There is no workaround.
•
CSCdr80686
When a rate-limiting feature (for example, committed access rate (CAR)) or a QoS feature (for
example, access-control list (ACL)) is enabled on an interface of an Engine 0 or Engine 1 line card
on a Cisco 12000 series Internet router, the receive (RX) byte and packet counters for that interface
shows the net number of byte and packets that have been admitted to the interface. In this situation,
packets that are dropped at the interface because of CAR or ACL are excluded from the RX byte and
packet counters. There is no workaround.
example, access-control list (ACL)) is enabled on an interface of an Engine 0 or Engine 1 line card
on a Cisco 12000 series Internet router, the receive (RX) byte and packet counters for that interface
shows the net number of byte and packets that have been admitted to the interface. In this situation,
packets that are dropped at the interface because of CAR or ACL are excluded from the RX byte and
packet counters. There is no workaround.