
552
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S9
–
SIP-600
Workaround: Reload the linecard with the affected interfaces.
• CSCsk72704
Symptoms: Tracebacks and spurious memory access occur when MR APS is unconfigured.
Conditions: The direction has to be changed from bidirection to unidirection before unconfiguration.
Workaround: There is no workaround.
• CSCsk75759
Symptoms: RP does not boot up if it is power cycled immediately on upgrading the ROMmon.
Conditions: Occurs only with Cisco IOS Release 12.0(33)S-based images.
Workaround: Avoid power cycle of the PRP immediately after the upgrade. Boot IOS after the
ROMmon upgrade.
• CSCsk76076
Symptoms: There are no netflow data for the traffic received on the port-channel 1. There is netflow
data for the traffic received on port-channel 2, but the data match with the traffic from first interface
of the bundle. Netflow data are still correct for the traffic sent to a port-channel interface (netflow
destination interface).
Conditions: Sampled netflow configured on GSR 12416 router, 2 port-channel configured Upgrade
of the IOS from version 12.0(32).S5 to version 12.0(32).S8.
Workaround: There is no workaround.
• CSCsk84729
Symptoms: PIM neighbor will not form over tunnel interface when a VRF is re-added. If the
neighbor does form, even then MCAST traffic will continue to drop on the E3 LC.
Conditions: Occurs after a VRF is removed and later on re-added. This was observed in Cisco IOS
Release 12.0(32)S.
Workaround: Remove and re-add the hw-module slot X ip multicast hw-accelerate source-table
size command. This is a traffic-impacting operation.
• CSCsk86526
Symptoms: After a long haul fiber cut is restored on DWDM equipment, the interface on E4+ is
stuck.
Conditions: Occurs on the following topology:
Test GSR (E4+) ---(local fiber)--- third-party DWDM ---- long hual fiber -------- third-party DWDM
---(local fiber)---- Customer GSR
LOF is seen on E4+ which is not getting cleared upon restoration of long haul fiber cut. This is
causing the interface not to come up.
Workaround: Framer is not sending an interrupt to clear the LOF in software. When LOS interrupt
comes to clear LOS, check the status of LOF also and clear it if it is not present.
• CSCsk92715
Symptoms: Some Frame-relay interfaces stop forwarding traffic after SPA reload.
Conditions: The issue happens with multilink frame-relay interfaces configured on a SPA using any
of the following SIP on a Cisco 12000 series router:
–
SIP-401
Comentarios a estos manuales