From: James Matrisciano (jmatrisciano@kenttech.com)
Date: Fri Sep 02 2005 - 10:29:29 GMT-3
All I would say is, watch where you put the frame-relay class statement.
With placing it on the serial interface, any DLCI is going to pick up
that class map, you want to put it under the DLCI you want, so when you
put in frame-relay interface-dlci 106, it should open you up into the
actual DLCI configuration, at that point, put in the frame-relay class
QOS command.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
nhqky888@ybb.ne.jp
Sent: Friday, September 02, 2005 3:51 AM
To: ccielab@groupstudy.com
Subject: Re: RE: Not to fragment for VoIP
Hi,
Thanks James.
My answer is,
R1:
interface Serial0
no ip address
encapsulation frame-relay
clockrate 148000
frame-relay class QOS
frame-relay traffic-shaping
frame-relay lmi-type cisco
frame-relay intf-type dce
!
interface Serial0.1 point-to-point
ip address 1.1.8.1 255.255.255.252
frame-relay interface-dlci 106
!
map-class frame-relay QOS
frame-relay cir 64000
frame-relay bc 640
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay fragment 80
!
* R1s Serial 0 has only one subint.
Correct me if I m wrong.
KY
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:13 GMT-3