Re: frame relay mqc

I think thats it you've been loooking for.

R1#sh run map
Building configuration...

Current configuration:
!
map-class frame-relay R2
 frame-relay cir 128000
 service-policy output R2
!
map-class frame-relay R3
 frame-relay cir 128000
 service-policy output R3
end

R1#sh frame-relay pvc 102

PVC Statistics for interface Serial1/0 (Frame Relay DTE)

DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.1

  input pkts 5 output pkts 5 in bytes 520
  out bytes 520 dropped pkts 0 in pkts dropped 0

  out pkts dropped 0 out bytes dropped 0
  in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
  out BECN pkts 0 in DE pkts 0 out DE pkts 0
  out bcast pkts 0 out bcast bytes 0
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:02:26, last time pvc status changed 00:00:57
  cir 128000 bc 128000 be 0 byte limit 2000 interval 125
  mincir 64000 byte increment 2000 Adaptive Shaping none
  pkts 5 bytes 520 pkts delayed 0 bytes delayed 0

  shaping inactive
  traffic shaping drops 0
  service policy R2
 Serial1/0.1: DLCI 102 -

  Service-policy output: R2

    Class-map: class-default (match-any)
      5 packets, 520 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      Queueing
        Flow Based Fair Queueing
        Maximum Number of Hashed Queues 16
        (total queued/total drops/no-buffer drops) 0/0/0
  Output queue size 0/max total 600/drops 0
R1#sh run int s1/0.1
Building configuration...

Current configuration : 275 bytes
!
interface Serial1/0.1 multipoint
 ip address 10.1.1.1 255.255.255.0
 frame-relay map ip 10.1.1.3 103 broadcast
 frame-relay map ip 10.1.1.2 102 broadcast
 frame-relay interface-dlci 102
  class R2
 frame-relay interface-dlci 103
  class R3
 no frame-relay inverse-arp
end

BR,

Alberto

On 29 January 2012 16:55, Aaron <aaron1_at_gvtc.com> wrote:

> Ok, thanks, so I can do it on the frame relay maps for multi point
> interfaces. Thanks Alberto****
>
> ** **
>
> *From:* Alberto Santos [mailto:albertofsantos_at_gmail.com]
> *Sent:* Sunday, January 29, 2012 4:46 AM
> *To:* Aaron
> *Cc:* ccielab_at_groupstudy.com
> *Subject:* Re: frame relay mqc****
>
> ** **
>
> Aaron,****
>
> ** **
>
> the applying phase do not mean that it can only be used under interface
> level, but it says it will be used for applying a policy-map. as you saw,
> it can be config under interface level, map FR level and also under a
> policy-map class level. as a nested policy for example.****
>
> ** **
>
> you are allowed to config per interface and per DLCI level under P2P or
> multipoint interface, that depends what are the requirements.****
>
> ** **
>
> BR,****
>
> ** **
>
> Alberto****
>
> On 26 January 2012 18:53, Aaron <aaron1_at_gvtc.com> wrote:****
>
> I've always understood that MQC QOS is made-up of .
>
>
>
> Class-map
>
> Policy-map - which calls previous class-map
>
> Service-policy - applied to an interface in/out which calls previous
> policy-map
>
>
>
> I've just learned/read that mqc qos on frame relay uses something
> additional. map-class.
>
>
>
>
>
> class-map my-class-map
>
>
>
> policy-map my-policy-map
>
> class my-class-map
>
>
>
> map-class frame-relay my-map-class
>
> service-policy output my-policy-map
>
>
>
> interface serial 0/0.1 point-to-point
>
> frame-relay interface-dlci 100
>
> class my-map-class
>
>
>
>
>
> .is that it?
>
>
>
> Also, can you do this on a multipoint fr interface? .on a phy serial
> interface?
>
>
>
> Aaron
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
> ****
>
>
>
> ****
>
> ** **
>
> -- ****
>

--
*
*
Blogs and organic groups at http://www.ccie.net