Hi all,
I did open a case and the following was the solution...
On VSX it seems that you need to enable the memory statstics and reboot the host after:
In VS:
# vsx mstat enable
VSX memory resource control status: disabled
VSX memory resource control will start running after you reboot the machine
# reboot
After this I could see the used memory via snmp:
# snmpwalk -v 2c -c public 127.0.0.1 .1.3.6.1.4.1.2620.1.16.22.3
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.1.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.1.2.0 = INTEGER: 1
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.1.3.0 = INTEGER: 2
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.1.4.0 = INTEGER: 3
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.2.1.0 = STRING: "vsx01"
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.2.2.0 = STRING: "fw01"
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.2.3.0 = STRING: "fw02"
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.2.4.0 = STRING: "sw01"
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.3.1.0 = Gauge32: 1062617
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.3.2.0 = Gauge32: 131390
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.3.3.0 = Gauge32: 321672
SNMPv2-SMI::enterprises.2620.1.16.22.3.1.3.4.0 = Gauge32: 60435