From: Howard C. Berkowitz (hcb@xxxxxxxxxxxx)
Date: Wed Apr 24 2002 - 16:25:44 GMT-3
At 2:38 PM -0400 4/24/02, Peter van Oene wrote:
>control traffic generally flows with 111. Hence, if you set your
>data traffic to 111, your routers with no longer be able to
>prioritize control packets which can have rather negative effects
>when the dropping begins. Many times 111 and 110 are also handled
>with equal priority which may be the reason why cisco advises
>against both.
>
>Pete
>
>
>At 08:07 PM 4/24/2002 +0500, Ahmed Mamoor Amimi wrote:
>>Can some expert tell me why it is not recommended precedence value
>>of 6 and 7.
>>I have seen at CCO that it will produce potential problem with the core data
>>traffic like routing and other signalling.... if this is so then why these
>>value are given to be configured.
>>
>>
>>-Mamoor
First, there are quite a number of Cisco commands, some documented,
some not, that aren't really intended for customer use other than
perhaps with the TAC. Others were put in for developers and there
was no strong reason to take them out.
Routing protocols do set these values. I could conceive (as a fairly
unlikely possibility) that some bad implementation might not do so,
and you might want to reset them properly in the interest of
interoperability.
There is a saying internal to Cisco that there are two reasons to
have "knobs", or ways to adjust unusual protocol parameters.
1. For extremely knowledgeable people, usually TAC, to circumvent
bugs
2. To anchor one end of a rope that a user puts around his neck to
hang himself.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:18 GMT-3