That wording is kinda fuzzy but I would interpret it the same way you did.
In other words, the RETURN traffic would be silently dropped and no error
messages generated. But I have not labbed this and most of my CoPPs practice
is with ingress only.


 -Hammer-

"I was a normal American nerd."
-Jack Herer





On Sun, Mar 6, 2011 at 3:26 AM, Kingsley Charles <[email protected]
> wrote:

> Hi all
>
> When you apply CoPP for output traffic, it applies to all traffic coming
> out from the CP. The highlighted statement is not clear to me. Does it mean
> that the error messages are not sent for the return CP traffic for those two
> mentioned ingress CP traffic.
>
> Snippet from
> http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/ctrl_plane_policng_external_docbase_0900e4b1805eee4d_4container_external_docbase_0900e4b180dd87e0.html
>
> Output Rate-Limiting and Silent Mode Operation
>
> A router is automatically enabled to silently discard packets when you
> configure output policing on control plane traffic using the *service-policy
> output **policy-map-name* command.
>
> Rate-limiting (policing) of output traffic from the CP is performed in
> silent mode. In silent mode, a router that is running Cisco IOS software
> operates without sending any system messages. If a packet that is exiting
> the control plane is discarded for output policing, you do not receive an
> error message.
>
> When control plane policing is configured for output traffic, error
> messages are not generated in the following cases:
>
> •Traffic that is being transmitted to a port to which the router is not
> listening
>
> •A connection to a legitimate address and port that is rejected because of
> a malformed request
>
>
>
> With regards
>
> Kings
>
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to