Cisco Cisco IOS Software Release 12.0 S Release Notes
1955
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(23)S4
When the symptom occurs, the output of the show hardware pxf cpu subblocks privileged EXEC
command lists “noSB” for the affected subinterface, as is indicated in the following example:
command lists “noSB” for the affected subinterface, as is indicated in the following example:
Router# show hard pxf cpu sub | i GigabitEthernet4
GigabitEthernet4/0/0 up 12000 4 PXF 1 81C4A800 4
GigabitEthernet4/0/0.500 administ 12000 4 PXF 1 81C4A800 noSB
Workaround: Change the encapsulation of the subinterface to dot1q when the subinterface is not
shut down. The state of the main interface is irrelevant. After you change the encapsulation, you can
shut down the subinterface again.
shut down. The state of the main interface is irrelevant. After you change the encapsulation, you can
shut down the subinterface again.
When the subinterface is created while the main interface is shut down, the subinterface and the
VLAN do not function properly. Perform the following steps to recover the VLAN:
VLAN do not function properly. Perform the following steps to recover the VLAN:
1.
Ensure that the subinterface is not shut down.
2.
(Optional) Enter the no encapsulation dot1q native subinterface configuration command.
3.
Remove the subinterface.
4.
Recreate the subinterface.
5.
Change the encapsulation back to dot1q.
•
CSCeb78329
Symptoms: After a Route Processor Redundancy Plus (RPR+) switchover occurs, the deletion of an
existing permanent virtual circuit (PVC)/permanent virtual path (PVP) fails. This situation prevents
you from recreating the same PVC/PVP. You can create a new PVC/PVP, but once you delete it, you
cannot recreate it because the PVC remains in the active state.
existing permanent virtual circuit (PVC)/permanent virtual path (PVP) fails. This situation prevents
you from recreating the same PVC/PVP. You can create a new PVC/PVP, but once you delete it, you
cannot recreate it because the PVC remains in the active state.
Conditions: This symptom is observed on a Cisco 10000 series that runs Cisco IOS Release 12.0 S
or Release 12.0 SX.
or Release 12.0 SX.
Workaround: There is no workaround. To enable the router to return to normal operation, reload the
router.
router.
•
CSCeb78610
Symptoms: The interface protocol may not come up for a 1-port OC-12 Packet-over-SONET (POS)
line card when the encapsulation frame-relay interface configuration command is configured.
line card when the encapsulation frame-relay interface configuration command is configured.
Conditions: This symptom is observed on a Cisco 10000 series when the 1-port OC-12 POS line card
is connected back-to-back to another line card in another Cisco 10000 series.
is connected back-to-back to another line card in another Cisco 10000 series.
Workaround: There is no workaround.
•
CSCeb82737
Symptoms: When you shut down the last port of an 8-port Fast Ethernet half-height line card (port
7), all the other ports on the line card may stop transmitting traffic.
7), all the other ports on the line card may stop transmitting traffic.
Conditions: This symptom is observed on a Cisco 10000 series.
Workaround: Do not shut down port 7. If port 7 is shut down, enter the no shutdown interface
configuration command on the interface to enable traffic to resume on the other interfaces.
configuration command on the interface to enable traffic to resume on the other interfaces.
•
CSCeb83784
Symptoms: The following error message may appear for a 3-port Gigabit Ethernet Engine 2 line
card, and the line card may reset:
card, and the line card may reset:
%LCGE-3-SOP_BAD_PACKET: Found corrupt pkts in tx-sop-sram.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(23)S3.
Release 12.0(23)S3.
Workaround: There is no workaround.