interface hold-queue, QoS question

wilson_1234_2 · ‎01-11-2009

If I have a serial interface configured per below, is the hold-queue doing anything?

My understanding is hold-queue is a fifo function and by applying the QoS policy aren't I using CBWFQ in the interface?

policy-map P-QoS

class VOICE

priority 256

set dscp ef

class DATA-Priority

bandwidth 128

set dscp af31

class class-default

set dscp default

fair-queue

random-detect

map-class frame-relay P-class

frame-relay cir 1536000

service-policy output P-QoS

interface Serial0/1/0

bandwidth 1536

no ip address

encapsulation frame-relay IETF

no fair-queue

frame-relay traffic-shaping

frame-relay lmi-type cisco

hold-queue 256 in

hold-queue 256 out

!

interface Serial0/1/0.400 point-to-point

ip address 1.2.1.54 255.255.255.252

ip nbar protocol-discovery

ip flow ingress

ip flow egress

frame-relay interface-dlci 400 IETF

class P-class

crypto map P_Crypt

Giuseppe Larosa · ‎01-11-2009

Hello Richard,

hold-queues are used for process-switched traffic like routing protocols hellos and updates.

QoS applies to user traffic

It shouldn't be a problem.

Hope to help

Giuseppe

wilson_1234_2 · ‎01-12-2009

Is there any reason to change these parameters from the default?

Also on the interface is:

"no fair-queue"

If I have a qos policy aren't I using CBWFQ?

How would this be affecting the policy applied to the sub-interface?