QoS priority tag configured in User-defined network resource pool in NIOC are not applied
search cancel

QoS priority tag configured in User-defined network resource pool in NIOC are not applied

book

Article ID: 328412

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • QoS priority tag configured in User-defined network resource pool in NIOC are not applied when capturing traffic
  • In /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

    "2017-05-17T10:15:35.908Z cpu38:34299 opID=6ce59183)WARNING: netsched: NetSchedMClkApplyCfg:3440: vmnic4: failed to apply configuration for queue netsched.pools.vm.50331660: Bad parameter
    2017-05-17T10:15:35.908Z cpu38:34299 opID=6ce59183)NIOC: 2368: Fail to apply NIOC Config of port: 300000c to uplink: 3000006, status =Bad parameter
    2017-05-17T10:15:35.908Z cpu38:34299 opID=6ce59183)DVSDev: DVSDevDataSet:1025: setting data com.vmware.common.port.respools.cfg on port 1594
    2017-05-17T10:15:35.908Z cpu38:34299 opID=6ce59183)WARNING: netsched: NetSchedMClkSanityCheckQueueCfg:3108: vmnic5: invalid pTag value 255 requested for queue netsched.pools.vm.50331661
    2017-05-17T10:15:35.908Z cpu38:34299 opID=6ce59183)WARNING: netsched: NetSchedMClkCreateOrUpdateQueue:3166: vmnic5: Invalid queue configuration passed for queue netsched.pools.vm.50331661: Bad parameter"


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Cause

The issue occurs when using QoS priority tag configured in User-defined network resource pool in NIOC.

Resolution

This issue is resolved in VMware ESXi 5.5, Patch Release ESXi550-201608001 (Build 4179633), available at VMware Downloads.

Additional Information



VMware ESXi 5.5, Patch Release ESXi550-201608001

Impact/Risks:
This issue will cause QoS priority tag (CoS) to not being applied on relevant network traffic.