QoS on Tagged VLAN Sub-interface

[Amnuay]

Hi there,

I try to implement QoS on Tagged VLAN sub-interface. Found some configuration on main interface but not sub-interface one.

Any suggestion? ^^

Thank you    

[kprakash]

Good Morning,

You can apply Qos on the sub interface under the "Clear text Traffic" section as shown below. You still have to bind it to a physical interface, and I would use the Physical interface that is serving as a trunk for the vlan, that the vlan interface is associated with.

Thanks and best regards,

Karthik

[Amnuay]

Hello Karthik,

Thank you for your reply. I have applied it under clear Text but seems that on "QoS Interface" Level it allow only physical interface.

In this section is specified as source interface so no problem for incoming but outgoing wise. ^^

Any other suggestion you may have?

Cheers,

AM

[_slv_]

the same ... could anyone confirm that these links are working for him?

Regards

Slawek

[mbutt · Accepted solution]

I have just confirmed the first link is working. Make sure you have an account to login to live.paloaltonetworks.com. you can go to main site support.paloaltonetworks.com and then click on the communities. However see the answer below

QoS can only be applied on physical interfaces. To apply it on sub-interfaces will not be possible.

One possible workaround would be since there are 8 different class you can define. you can add different subnet ranges in QoS profiles with different class.

Look at the following document which is for a single user but it can be tweaked to have different subnets

https://live.paloaltonetworks.com/docs/DOC-3158

Policy match is only for classification purposes to assign traffic to a particular queue on a given egress interface. The actually servicing of queues though is done on the physical egress interface. We cannot differentiate between one sub-interface or the other when servicing queues as QoS can only be applied to physical interface. So I believe that what customer is asking for would need to be a feature request.

Presently the only way that this can be done is to assign traffic from each sub-interface to different queues. However since we only can have up to 8 queues, then this will limit how many sub-interfaces and types of traffic you can classify.

Hope this helps.

Thanks

Numan

[Amnuay]

I will change it back to Physical Interface then ^^

[JimMcGrady]

Hi Karthik. The logic of this has me confused. QoS applies to egress traffic. Say i have a firewall with eth1/1 connected to internet and subinterface eth1/2.1 connected to my internal network.  Applying egress QoS to eth2.1 would appear to be the way. But the QoS Interface config appears to only allow a sub-interface to be specified as a source interface. My think is that, since the traffic is coming in from internet and out to internal, the ingress (source) is eth1/1 and egress (destination) is eth1/2.1.  Or am i reading that wrong?