Re: IE WB lab 7, ver 3, section 8.2

From: Oscar (oscar@kaos.es)
Date: Mon Sep 18 2006 - 07:34:34 ART


Hi

Another question is the propossed solution for R5 is sligthly wrong (in my
opinion)

they use :
!
map-class frame-relay DLCI_504
 frame-relay cir 768000
 frame-relay bc 7680
 frame-relay fragment 960
!
map-class frame-relay DLCI_503
 frame-relay cir 768000
!

but I think the shoud use this for the DLCI to R3
!
map-class frame-relay DLCI_503
 frame-relay cir 768000
 frame-relay bc 7680
!

The question says "the shaping intervals of R4 and R5 should be such as to
minimize delay due to serialization" and in the proposed solution they do
that just for the DLCI between R4 and R5. But the DLCI to R3 uses the same
phisical interface in R5 so you have an interval of 10ms for DLCI 504 and 63
ms for DLCI 503 wich is not correct (as they are both using the same fisical
interface). A voice packet is going to wait for 63ms in R5 if a big paquet
has been sent to R3 just before the voice paquet itself.

Rack1R5#sh traffic-shape s0.35

Interface Se0.35
       Access Target Byte Sustain Excess Interval Increment Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes)
Active
503 768000 6048 768000 0 63 6048 -
Rack1R5#
Rack1R5#
Rack1R5#sh traffic-shape s0.54

Interface Se0.54
       Access Target Byte Sustain Excess Interval Increment Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes)
Active
504 768000 960 7680 0 10 960 -
Rack1R5#

----- Original Message -----
From: "Roberto Fernandez" <rofernandez@us.telefonica.com>
To: "san" <san.study@gmail.com>; "Cisco certification"
<ccielab@groupstudy.com>
Sent: Wednesday, June 28, 2006 12:26 AM
Subject: RE: IE WB lab 7, ver 3, section 8.2

> Sam,
>
> As soon as you enter the "frame-relay traffic shaping" command you will
> be (by default) telling to your router to use 56Kbps as the CIR on each
> PVC. As you see, now you have to fix this, and you tell the router to
> use 768Kbps since this is your target rate and you are mandated to
> adhere to it. That is:
>
> frame-relay cir 768000
>
> Here the MINCIR makes no point. You need MINCIR on the following cases:
>
> 1-You are using adaptive-shaping, which implies you are willing to
> decrease your speed down to MINCIR value
>
> 2-You are reserving bandwidth (using a policy-map and the bandwidth
> command), then you need to specify MINCIR because the routers calculates
> its available bandwidth from this value and by default MINCIR is half of
> the CIR.
>
> An example can show you:
> !
> !
> Interface Serial0/0
> frame-relay traffic shaping
> frame-relay class SHAPED
> !
> map-class frame-relay SHAPED
> frame-relay cir 786000 !!!(here you are implying a MINCIR of 384000)
> service-policy out PRIORITY_BANDWITH
> !
> class-map match all VOICE
> match protocol rtp
> !
> policy-map PRIORITY_BANDWITH
> class VOICE
> priority 512
> !
> !
> If you try to use the configuration it will not work, the router will
> complain of not having enough bandwidth to reserve as priority for you.
> You are requesting 512000 and it has only available its default MINCIR
> of 384000) in this case if you ADD frame-relay mincir 768000 then you
> will be able to reserve some bandwidth. Your map class would be:
>
> map-class frame-relay SHAPED
> frame-relay cir 786000 !!!(here you are implying a MINCIR of 384000)
> frame-relay mincir 768000 !!!(you are making all your bandwidth
> available)
> service-policy out PRIORITY_BANDWITH
>
> Best Regards,
> Roberto
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> san
> Sent: Tuesday, June 27, 2006 12:56 PM
> To: Cisco certification
> Subject: IE WB lab 7, ver 3, section 8.2
>
> Hi all,
>
> Why or when do we use "frame-relay cir 768000" instead of "frame-relay
> mincir 768000".
> Based on the question i assume it would be mincir but wasnt. Could you
> clarify.
>
> Question Says:
> Frame Relay interfaces of R3, R4 and R5 are all clocked at T1 speed by
> the
> FR SP. However since R5 only has a single connection to the FR cloud,
> each
> VC on R5 has been equally provisioned a cir of 768k by the telco.
> Configure all endpoints of the FR network to adhere to the provisioned
> CIR.
>
> --
> Thanks & Rgds
> SAN
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART