[c-nsp] CBWFQ-LLQ on Frame Relay

[virendra rode //]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Tassos Chatzithomaoglou wrote:
> If i remember right, "sh frame pvc xxx" will show you the "truth".
> 
> -- 
> Tassos
- --------------------
It doesn't give anything related to queuing that I know of.


regards,
/virendra

> 
> 
> virendra rode // wrote on 8/4/2008 10:56 μμ:
> Hi,
> 
> I have a class based weighted fair queue/LLQ defined and applied in a
> frame-relay lab environment.
> 
> 
> 1. class-map defined
> 2. policy-map qos-policy
> 3. applied to interface (see below)
> 
> 
> interface Serial0/0/0:0
>  no ip address
>  encapsulation frame-relay
>  no fair-queue
>  frame-relay traffic-shaping
> !
> interface Serial0/0/0:0.666 point-to-point
>  description lab pvc
>  bandwidth 1024
>  ip address 192.168.0.1 255.255.255.252
>  frame-relay class shaper-queue-policy
>  frame-relay interface-dlci 666 ietf
> 
> 
> map-class frame-relay shaper-queue-policy
>  frame-relay cir 1024000
>  frame-relay be 0
>  frame-relay mincir 1024000
>  service-policy output queuing-policies
> 
> 
> The question I have is when I look at Serial0/0/0:0 interface queue (see
> below output) it shows queuing as "fifo" but looking at the show queuing
> interface on the same interface  (see below output)  list queue
> strategy as
> "priority". Is this correct behavior or do I need to apply "service
> service-policy output" to the main interface (Serial0/0/0:0) in
> order for it to be doing "class-based queueing" as opposed to "fifo"?
> 
> 
> lab-gw#sh interface Serial0/0/0:0
> Serial0/0/0:0 is up, line protocol is up
>   Hardware is GT96K Serial
>   MTU 1500 bytes, BW 1024 Kbit, DLY 20000 usec,
>      reliability 255/255, txload 5/255, rxload 241/255
>   Encapsulation FRAME-RELAY, loopback not set
>   Keepalive set (10 sec)
>   LMI enq sent  9293, LMI stat recvd 9294, LMI upd recvd 0, DTE LMI up
>   LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
>   LMI DLCI 1023  LMI type is CISCO  frame relay DTE
>   FR SVC disabled, LAPF state down
>   Broadcast queue 0/64, broadcasts sent/dropped 9293/1, interface
> broadcasts 9293
>   Last input 00:00:00, output 00:00:00, output hang never
>   Last clearing of "show interface" counters 1d01h
>   Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
>   Queueing strategy: fifo
>   Output queue: 0/40 (size/max)
>   30 second input rate 970000 bits/sec, 85 packets/sec
>   30 second output rate 21000 bits/sec, 58 packets/sec
> 
> 
> lab-gw#sh queueing int Serial0/0/0:0
> Interface Serial0/0/0:0 queueing strategy: priority
> 
> Output queue utilization (queue/count)
>         high/0 medium/0 normal/62520 low/0
> 
> 
> Any insight will be appreciated.
> 
> 
> 
> regards,
> /virendra
> 
> 
> 
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH++UGpbZvCIJx1bcRAm5xAKCtoPyI6CLUZSVkzQ4jXivD8bpXUgCdEa6+
s10f28NwWiixrgnuJ6YSm+I=
=WoDM
-----END PGP SIGNATURE-----