QOS on a ERS switch port

[Faiyaaa]

Hi All, 

I have been banging my head to configure QoS, as the PC is connected to an ERS 4950GTS switch (v7.9.6.015) on interface port 2/35, running the Avaya Workspace Attendant Software.

The third-party company managing Avaya CC informed me that they cannot see the DSCP value as 46 on their portal—instead, it's showing as -1.

Please review the configuration below and let me know what might be missing

Switchname(config)#sh run mod qos!

! Displaying only parameters different to default
!================================================
enable
configure terminal
!
! *** QOS ***
!
qos if-group name "Trust_VOIP" class untrusted
qos ip-element 1 name dsClfr1 ds-field 46
qos classifier 1 set-id 1 name "Trust_VOIP" element-type ip element-id 1
qos if-assign port 2/35 name Trust_VOIP
!qos agent queue-set 4
qos policy 1 name "Trust_VOIP" if-group "Trust_VOIP" clfr-type classifier clfr-id 1 in-profile-action 7 precedence 6 track-statistic
s
qos traffic-profile classifier name "VOIP-POL" addr-type ipv4 ethertype 0x800 update-dscp 0 update-1p 0 eval-order 10
qos if-assign port 1/ALL,2/1-34,2/36-50 name $qosDisabledIfcs

[Shoibsi]

Hi Faiyaaa

Depending on the specifics of what you want to trust or not trust, you can choose to configure port 2/35 as trusted Or untrusted.
Based on what you have posted the following should work with below minimum config after existing ip-element 1, policy, classifier configured for the very purpose removed.

qos if-group name "Trust_VOIP" class untrusted
qos if-assign port 2/35 name Trust_VOIP
qos traffic-profile classifier name "VOIP-POL" addr-type ipv4 ethertype 0x800 update-dscp 46 update-1p 6 eval-order 10
qos traffic-profile set port 2/35 name "VOIP-POL" track-statistics aggregate

You may also need to consider the return packet flow depending on the application requirements. If the return traffic destined to PC is marked with DSCP 46 and is required to be retained across the ERS, then you would need to configure ERS uplink port as trusted.

If the above config does not work for you it may be worth engaging technical support for a deeper look to make sure all of the packet flow requirements on the port are evaluated in detail.