hi kconnnell
Looks like a bug, I will raise it with the MAS devs. By the way, something you will come across too when playing cacti with MAS, is that the datapath NPUs (which are visible in AOS MIB and also from the CLI command 'show datapath utilisation') are missing from MAS. Design is aware of it and plans to add it back in, but they did note that these datapath CPUs are not currently used in MAS hence the reason they were removed. However, they did concede that for completeness and future use, that they should be added.
I will try to convince them to address both of these at the same time, if you need to chase up on this, please contact support and refer to bug 66315.
Finally, if you're using cacti, you could work around this with a custom data query like below.
regards
-jeff
<interface>
<name>Get Aruba CPU/NPU Util</name>
<description>Get CPU load info from wlsxSysXProcessorTable</description>
<oid_index>.1.3.6.1.4.1.14823.2.2.1.1.1.9.1.3</oid_index>
<index_order_type>numeric</index_order_type>
<oid_index_parse>OID/REGEXP:.*\.([0-9]+)$</oid_index_parse>
<fields>
<cpuIndex>
<name>CPU #</name>
<method>walk</method>
<source>OID/REGEXP:.*\.([0-9]+)$</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.14823.2.2.1.1.1.9.1.3</oid>
</cpuIndex>
<sysXProcessorLoad>
<name>Processor Load</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.14823.2.2.1.1.1.9.1.3</oid>
</sysXProcessorLoad>
<sysXProcessorDescr>
<name>Description</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.14823.2.2.1.1.1.9.1.2</oid>
</sysXProcessorDescr>
</fields>
</interface>