Re: Frame-relay DLCI priority levels

From: Petr Lapukhov (petr@internetworkexpert.com)
Date: Sat Sep 30 2006 - 12:27:49 ART

Hi Alexei :)

It has some difference (interface FIFO or PQ)... Though it works in both
cases :))

#debug frame packet
#debug priority

With FIFO it just classifies and assigns packets to respective PVC:

R4#ping 45.45.45.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 45.45.45.5, timeout is 2 seconds:

*Sep 25 05:27:04.169: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high
*Sep 25 05:27:04.169: Serial0/1(o): dlci 100(0x1841), pkt type 0x800(IP),
datagramsize 104.
*Sep 25 05:27:06.169: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high
*Sep 25 05:27:06.169: Serial0/1(o): dlci 100(0x1841), pkt type 0x800(IP),
datagramsize 104.
*Sep 25 05:27:08.169: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high
*Sep 25 05:27:08.169: Serial0/1(o): dlci 100(0x1841), pkt type 0x800(IP),
datagramsize 104.
*Sep 25 05:27:10.169: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high

With PQ it also does PQ processing at _interface_ level:

R4#ping 45.45.45.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 45.45.45.5, timeout is 2 seconds:

*Sep 25 05:30:17.533: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high
*Sep 25 05:30:17.533: Serial0/1(o): dlci 100(0x1841), pkt type 0x800(IP),
datagramsize 104
*Sep 25 05:30:17.533: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high

*Sep 25 05:30:17.533: PQ: Serial0/1 output (Pk size/Q 104/0). <======= THIS
ONE

*Sep 25 05:30:19.533: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high
*Sep 25 05:30:19.533: Serial0/1(o): dlci 100(0x1841), pkt type 0x800(IP),
datagramsize 104
*Sep 25 05:30:19.533: PQ: Serial0/1: ip (s=45.45.45.4, d=45.45.45.5) -> high

It probably makes sense to use interface PQ in this situation :) It's QoS,
after all :)

30.09.06, Alexei Monastyrnyi <alexeim@orcsoftware.com> NAPISAL(A):
>
> Works fine without one :-)
> It picks priority group via "frame-relay priority-dlci-group"
>
> But it should be FIFO on both interfaces to have it working.
>
> A.
>
> on 9/30/2006 3:52 PM Petr Lapukhov wrote:
> > It's seems like that you forgot to put "priority-group 1" command on
> > interfaces.
> >
> > I remember I tried that "esoteric" topic back in days :) It doesn't
> seems
> > it'll
> > become a popular technology :)
> >
> > HTH
> >
> > PS
> > Actually, this is not called PIPQ - it's "DLCI prioritization" :) PIPQ
> is
> > when you
> > schedule different DLCIs into different priority queues.
> >
> > DLCI prioritization is the "reverse" case, where you put traffic with
> > different
> > priorities into different DLCIs.
> >
> > 2006/9/30, Radoslav Vasilev <deckland@gmail.com>:
> >
> >> Hi Group,
> >>
> >> I'm trying to separate two classes of traffic over two separate PVC
> >> over a single link (back to back between two routers). The idea is to
> >> later use PIPQ and test connectivity while checking the queueing with
> >> PIPQ.
> >>
> >> R4 and R5 connected back-to-back over interfaces serial 0/1 on each:
> >>
> >> R4:
> >>
> >> frame-relay switching
> >>
> >> interface Serial0/1
> >> ip address 192.168.100.4 255.255.255.0
> >> encapsulation frame-relay
> >> clock rate 128000
> >> frame-relay priority-dlci-group 1 100 101 101 101
> >> frame-relay intf-type dce
> >> end
> >>
> >> access-list 100 permit icmp any any
> >> access-list 101 permit tcp any any eq telnet
> >> access-list 101 permit tcp any eq telnet any
> >> priority-list 1 protocol ip high list 101
> >> priority-list 1 protocol ip low list 100
> >>
> >> R5:
> >>
> >> frame-relay switching
> >>
> >> interface Serial0/1
> >> ip address 192.168.100.5 255.255.255.0
> >> encapsulation frame-relay
> >> load-interval 30
> >> frame-relay priority-dlci-group 1 100 101 101 101
> >> end
> >>
> >> access-list 100 permit icmp any any
> >> access-list 101 permit tcp any any eq telnet
> >> access-list 101 permit tcp any eq telnet any
> >> priority-list 1 protocol ip high list 101
> >> priority-list 1 protocol ip low list 100
> >>
> >> As seen above, i want to use DLCI 100 for telnet traffic (two-way) and
> >> DLCI 101 for icmp traffic.
> >>
> >> I'm testing with pinging/telneting to R4 from R5,here's the debug on
> R4:
> >>
> >> while telneting from R5:
> >> Rack1R4# 1 00:59:45.659: Serial0/1(i): dlci 101(0x1851), pkt type
> >> 0x800, datagramsize 45
> >> *Mar 1 00:59:45.763: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 44
> >> *Mar 1 00:59:45.767: Serial0/1(i): dlci 101(0x1851), pkt type 0x800,
> >> datagramsize 45
> >> *Mar 1 00:59:45.975: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 44
> >> *Mar 1 00:59:45.983: Serial0/1(i): dlci 101(0x1851), pkt type 0x800,
> >> datagramsize 46
> >> *Mar 1 00:59:45.983: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 54
> >>
> >>
> >> whilte pinging from R5:
> >> *Mar 1 01:00:18.099: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 104
> >> *Mar 1 01:00:18.115: Serial0/1(i): dlci 101(0x1851), pkt type 0x800,
> >> datagramsize 104
> >> *Mar 1 01:00:18.115: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 104
> >> *Mar 1 01:00:18.131: Serial0/1(i): dlci 101(0x1851), pkt type 0x800,
> >> datagramsize 104
> >> *Mar 1 01:00:18.131: Serial0/1(o): dlci 101(0x1851), pkt type
> >> 0x800(IP), datagramsize 104
> >> *Mar 1 01:00:18.151: Serial0/1(i): dlci 101(0x1851), pkt type 0x800,
> >> datagramsize 104
> >>
> >> So it looks like the normal priority queue is selected...
> >>
> >> Rack1R5#sh frame-relay map
> >> Serial0/1 (up): ip 192.168.100.4 dlci 100(0x64,0x1840), dynamic,
> >> broadcast,, status defined, active
> >> Priority DLCI Group 1, DLCI 100 (HIGH), DLCI 101 (MEDIUM)
> >> DLCI 101 (NORMAL), DLCI 101 (LOW)
> >>
> >> Any ideas?
> >> Thaks
> >> Rado
> >>
> >> _______________________________________________________________________
> >> 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
> 

-- 
Petr Lapukhov, CCIE #16379
petr@internetworkexpert.com

Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344

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