Solaris 11 non global zone

Hello!

Can you post how your zone is configured?

It is entirely possible for dlstat to show the data you require, while the Zabbix agent not to show it because they are using 2 completely different libraries to obtain the data.

zonecfg -z <zone> info output

Hi,

I've attached the configuration of the zone in question.

confirming with 2.2.1rc1 agent on SunOS 5.11 11.1 sun4v

Also noticed today that it doesn't work on the global zone for vlan interfaces

Could you help us with environment to reproduce the problem and test fix patch? ahowell

Could you please be so kind and provide full dlstat command ? Thanks !
Also it would be nice if you could print as much information as possible to see values of fields such as obytes and obytes64
For example by calling

kstat link:0:net0

The problem rely on the fact we don't check properly what
field the network driver decided to populate and how.
For example, obytes and obytes64 are exactly the same
thing as are rbytes and rbytes64. The difference is that the
former fields are 32 bit unsigned integer, while the latter
are 64 bit unsigned integer.

There are three possible cases how those fields are when
a driver implement it's kstat structures:

• A really old driver is still working and it will still populate
  the 32 bit field only and the 64 bit one will be 0.

• An old driver is updated and it will store the same data in
  both for backward compatibility

• A new driver is implemented and as suggested, store the
  data in the 64 bit field only, thus leaving the 32 bit one
  set to 0.

If both the field are set, they MUST have the same value, but
there is the problem that the 32 bit field can wrap-around and
restart from 0 after some time, leaving the two field with
different values.

I would go for a solution as proposed by vso
as modern drivers will always prefer the 64 bit integer field.
Also, I think we should also always prefer it if possible when
it's > 0

Hi ahowell

I attached a patch to test. can you apply it to the zabbix agent
and check if the values are reported properly?

Regards

The file is:

net_c-fix_network_statistics_solaris_11.diff

Forgot to mention: The patch is for the zabbix agent 3.0 (currently
supported), but it should work also with 2.0

Hi aleksejs.petrovs

Oh, well, if one of our customers can test this, much appreciated!
Yes, the patch is for 3.0. We can't compile it here, so report if there
are compilation errors.

Thanks!

Corrected patch attached

Would it be possible to get log files from our customer who is having this issue? Specially interested if there has been any "Something impossible has just happened." entries in logs.

Added a fixed version of the patch that was added to this ticket previously.

Successfully tested