lbelza
Contributor
Contributor

Network usage perf. counter returns bad values

Hello,

I have one ESX server (v4.1) that contains two NIC instances. When I try to get value of "net.usage.average" perf. counter I got zero values. When I look at the network counters using vSphere Client I can see the values for NIC instances but counters for ESX contains zero values. Do you have any idea why the usage for ESX doesn't contain any values?

From reference guide I get that "net.usage" is sum of data transmitted and received across all physical NIC instances connected to the host.

10540_10540.png

Thanks, Lukas.

0 Kudos
3 Replies
KostyantynUA
Contributor
Contributor

Hi,

I'm experiencing the same problem(post - http://communities.vmware.com/message/1606861). For ESXi 4.0 all works fine, but in case of 4.1 all host perf counters are zero.

From soap response it doesn't look like a client response processing bug :

<QueryPerfResponse xmlns="urn:vim25">

<returnval xsi:type="PerfEntityMetricCSV">

<entity type="HostSystem">ha-host</entity>

<sampleInfoCSV>20,2010-09-10T10:33:00Z,20,2010-09-10T10:33:20Z</sampleInfoCSV>

<value>

<id>

<counterId>196609</counterId>

<instance></instance>

</id>

<value>

0,0

</value>

</value>

</returnval>

</QueryPerfResponse>

So, it's server side problem.

PS: it can be related to a privilages or to a configuration options. First one isn't a case, beacuse I'm using administrator(but still). Maybe some advanced option can turn this on/off. But in general something other can cause this problem.

0 Kudos
sbourdeaud
Contributor
Contributor

Hello,

I am having the same problem.

I compared over a dozen hosts across different clusters: all the vSphere 4.1 return only zero values for net.usage.average whereas their individual vmnic instances show Kbps in and out. vSphere 4.0 and ESX 3.5 hosts return good values for net.usage.average.

This looks like a bug to me...

Regards,

Stéphane B.

0 Kudos
dlecorfec
Contributor
Contributor

Had a similar problem of zero values for network counter on ESX 4.1 U1. Solved by using the latest bnx2x driver (1.62, 23 March 2011)

0 Kudos