Scott,
I think the packet dropping is unavoidable, no matter how you configure RED.
Most of the time, your TCP is in congestion avoidance state, it increases
its transmission window size by one every RTT (round trip time). In other
words, it will increase its transmission rate till congestion happ
cols bgp | display inheritance
> group MyGroup {
>neighbor 10.0.0.1 {
>##
>## 'policy-2' was inherited from group 'groupB'
>## 'policy-1' was inherited from group 'groupA'
>##
>import [ policy-3
All,
In configuration below, groupA and groupB import policy-statement 1 and 2,
respectively. So, what is the sequence of import policy neighbor 10.0.0.1
should go through? Should it be
1. policy-statement-3, then 2, then 1? or
2. policy-statement-3 only? or
3 something else?
group MyGroup {
a
ftware to do ACL, it may achieve that
> but I have no experience with that.
>
> On Fri, Jun 19, 2009 at 9:43 AM, Li Zhu wrote:
>
>> All,
>>
>> In the firewall filter, the counter can count number of packets match the
>> term. In the simple firewall filter below,
All,
In the firewall filter, the counter can count number of packets match the
term. In the simple firewall filter below, the counter AF11_NUM and EF_NUM
can count number packets with af11 and ef, respectively. My question is: can
Cisco achieve similar goal? I know this may be a Cisco question, bu
Masood, Nugroho
Thank you for the reply. I agree with both of you that rewrite takes effect
on both inner and outer mpls label. My next question is:
what if I want to mark inner and outer MPLS label differently? Say I want
mark the inner exp with 5 and outer exp with 6? Is it possible to achieve
t
All,
There is a network like CE --- PE --- P. The PE is M320. Traffic is from CE
to P. The traffic out of CE is native IP, after it reaches and gets out PE
(then to P), it is double-tagged with MPLS lable. There is a exp
rewrite-rule applied on PE link to P router. My questions is
will the rewrite
7 matches
Mail list logo
