
767
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Conditions: Policing is not working in the MPLS cloud. Even though packets are getting classified
correctly, policing is not working on those packets.
Workaround: There is no workaround.
Further Problem Description: Policing is not working in the MPLS cloud. Consider the following
three scenarios:
1) When a service policy and MPLS are configured on the subinterface, policing works fine. 2)
When a service policy and MPLS are configured on the main interface, policing works fine. 3) When
a service policy is attached on the main interface and MPLS on the subinterface, policing does not
work.
The first two cases work fine. It means if the MPLS feature and policy are on the main interface or
the MPLS feature and policy are on the subinterface, policing works correctly. The problem is with
the third case. Here, the MPLS feature is applied on the subinterface and policy on the main
interface. If we do not have MPLS configured and we are receiving just IP packets, then all cases
work fine. But MPLS packets are treated as IP packets.
• CSCsm66774
Symptoms: When a MIV policy-map is attached to the core facing interface in the output direction,
then classification is incorrect.
Conditions: Occurs when MIV policy-map is applied to core facing interface in output direction.
Workaround: There is no workaround.
• CSCsm68773
Symptoms: LFI bundles will not come up.
Conditions: The commit of CSCsl98665 disturbed the single member bundle creation.
Workaround: There is no workaround.
• CSCsm69368
Symptoms: Memory allocation failures and WATERMARK messages are seen on console.
Conditions: Occurs when Netflow Data Export (NDE) is enabled with Netflow TCAM overflown
with flows on a DFC. RP CPU utilization is high.
Workaround: The system is not supposed to scale for that many flows. Disable Netflow for
immediate fix.
• CSCsm69981
Symptoms: ISG is not allocating the next free port in the cyclic order as expected.
Conditions: The symptom is observed on PC clients using a web-portal. It is observed when the
browser is shutdown and a new one started within 60 seconds and when the web-server timeout is
set for 60 seconds.
Workaround: Adjust the web-server TCP port allocation timers to match that of the ISG and PC
clients.
Further Problem Description: ISG allocates a free port in a port-bundle when a subscriber sends a
TCP SYN packet. The port is freed after around 60 seconds. After this, if the same subscriber sends
a TCP SYN packet (in order to establish a new session), ISG allocates the freed port and not the next
free port in the cyclic order.
• CSCsm70668
Symptoms: A soft OIR over E3:POS impacts complete traffic with a biscuit tunnel.
Comentarios a estos manuales