From: Chuck Church (cchurch@MAGNACOM.com)
Date: Wed Sep 18 2002 - 10:03:49 GMT-3
When you enable FRTS, I think there are defaults for all the traffic shaping
parameters, like CIR, etc. With pure custom queueing, there's no CIR
enforced.
Chuck Church
CCIE #8776, MCNE, MCSE
Sr. Network Engineer
Magnacom Technologies
140 N. Rt. 303
Valley Cottage, NY 10989
845-267-4000
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Nick Shah
Sent: Wednesday, September 18, 2002 12:54 AM
To: Omer Ansari; ccielab@groupstudy.com
Subject: Re: custom queuing under a frame interface
Omer
My thinking is that both should be the same. Ideally the packets are
submitted to the physical interface for delivery (and hence queuing applied
there should work).
Thoughts ??
Nick
----- Original Message -----
From: "Omer Ansari" <omer@ansari.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, September 18, 2002 9:44 AM
Subject: custom queuing under a frame interface
> All,
>
> in the following, is "A" different from "B" ?
> [assume queue list is same for both and only 2 subifs]
>
> A
> =====
> !
> interface Serial2/0
> no ip address
> encapsulation frame-relay
> frame-relay traffic-shaping
> !
> interface Serial2/0.1 multipoint
> ip address 165.10.1.4 255.255.255.0
> frame-relay class cq <---------------
> ...
> !
> interface Serial2/0.2 point-to-point
> ip address 165.10.5.4 255.255.255.0
> frame-relay class cq <-------------
> ...
> !
> map-class frame-relay cq
> no frame-relay adaptive-shaping
> frame-relay custom-queue-list 2
> !
>
>
>
> B
> =====
>
> !
> interface Serial2/0
> no ip address
> encapsulation frame-relay
> custom-queue-list 2 <-------------
> !
> interface Serial2/0.1 multipoint
> ip address 165.10.1.4 255.255.255.0
> ...
> !
> !
> interface Serial2/0.2 point-to-point
> ip address 165.10.5.4 255.255.255.0
> ...
>
>
>
>
> Assuming the answer to above would apply to priority queue list also.
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:55 GMT-3