HP 2610/2626 QoS Questions

[Tim4u]

Hello,
within QoS IP-Device Priority configuration do i have to configure more than the following to assure that the outbound queues are used correctly (2626)? If yes, does this also count for the (via route 0.0.0.0) connected Router?

qos device-priority x.x.x.x dscp 101110
qos type-of-service diff-services
(qos dscp-map 101110 priority 7 is already in the running config)

The 2610 offers a qos-passthrough configuration. Unfortunatly this command is not descibed in the advanced traffic guide, so which command would be optimal output in my qos configuration?

[Pieter 't Hart]

Packets need to be "classified" to treat them differntly for QoS.
Packets can be "marked" so that not all devices need to do their own classification based on packet protocol/source/destination, but do the classification based on the marking done by a previous device that handled the packet.

qos-passthrough means the 2610 will not alter the marking of a packet when it allready has a mark.
packets not yet marked will be processed same way with or without qos-passtrhrough.

[Tim4u]

Hello Pieter,

thanks a lot for your answer. I think i should clearify my questions.

With my shown configuration, does the switch queue packets destinated (or source) to the ip x.x.x.x in the low latency queue?

Is there a command where I can verify this queuing? (sh qos resources doesnt tell me enough)

The qos-passthrough command is described with:
"Specify the queue configuration mode for the switch."
Offering typical and optimized.

Which queing mode is better suited for low latency traffic?

Please give me another hint!

[Tim4u]

Does a HP2610/2626 queue pakets on the outgoing interface destined to a Router?
Is queuing active over a static ip route?
(with the uppon described qos configuration)

[Pieter 't Hart]

without QoS you will allready have
1) a dedicated hardware queue per interface
2) a software queue per interface.

With QoS you create multiple (software) queues, where packets are treated differently according to properties.
These software queues may be partially implemented in "hardware" (ASIC's).
Those queues can exist per interface dpending how the manufacturer implements this.

It doesn't matter if the interface is connected to a router or which path is selected by a (static) route.