From: gladston@br.ibm.com
Date: Fri Oct 08 2004 - 16:14:41 GMT-3
==========
quoted
When using FR fragment w/o MQC, all below fragment size packets go to the priority "second stage" queue. When using MQC, all first stage priority go to the second stage priority. Second stage queues are plain FIFOs. So as long as you don't change the composition of the traffic,
it should not matter which way you configure the thing.
==========
Thanks to clarify. I missed up things. This url also helped: http://www.cisco.com/warp/public/105/queuing_fr_interfaces.pdf
=============
quoted
BTW, your show output is from a PQ config, so either is from another interface or your config is clipped.
=============
Oh, no, it is serial 0, with the previous command. If I remove "frame-relay fragment..." it removes the 'priority' showed:
r6#sh queuein in
r6#sh queuein interface ser 0
Interface Serial0 queueing strategy: priority
Output queue utilization (queue/count)
high/0 medium/0 normal/765 low/0
r6#c
Enter configuration commands, one per line. End with CNTL/Z.
r6(config)#map-class frame-relay Taskqos
r6(config-map-class)#no frame-relay fragment 1500
r6#sh queuein interface ser 0
Interface Serial0 queueing strategy: none
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:45 GMT-3