CPU Utilisation OID

[IG]

Hello. I am trying to monitor our VSP devices with Zabbix and the Extreme Template (EXOS) does not fully translate over 100% on all OID's. I have managed to work out all the other OIDs that were incorrect, but the last one I am stuck on is CPU utilisation %

I have tried 1.3.6.1.4.1.2272.1.85.10.1.1.2 (rcKhiSlotCpuCurrentUtil) but this is not working. Does anybody know which OID I can use?

They are VSP 7400's running VOSS 8.3.1.0

Thanks

[donna641 · Accepted solution]

---

@IG wrote:

Hello. I am trying to monitor our VSP devices with Zabbix and the Extreme Template (EXOS) does not fully translate over 100% on all OID's. I have managed to work out all the other OIDs that were incorrect, but the last one I am stuck on is CPU utilisation %

I have tried 1.3.6.1.4.1.2272.1.85.10.1.1.2 (rcKhiSlotCpuCurrentUtil) but this is not working. Does anybody know which OID I can use?

They are VSP 7400's running VOSS 8.3.1.0

Thanks

---

You've correctly identified the problem: the standard EXOS templates are not compatible with VSP devices because they run a different operating system, VOSS (Virtual Operating System), and use a different set of MIBs. The OID you attempted belongs to a different vendor (`2272` is a KHI Systems OID).

For Extreme VSP devices running VOSS, the most commonly used OID for global CPU utilization is:

**1.3.6.1.4.1.1916.1.32.1.1.1.3.0**

This OID corresponds to `s5GlbMonCpuUtil.0` within the **Extreme-VOSS-S5-GLOBAL-MONITORING-MIB**. This OID will provide the overall CPU utilization percentage for the device.

If you are looking for per-slot or per-module CPU utilization, you may need to use a different OID from the `Extreme-VOSS-ENTITY-MIB`, which often has a table of values indexed by slot number. However, the first OID is the most direct solution for overall device CPU monitoring.

I recommend trying this OID and running a simple `snmpwalk` or `snmpget` command from your Zabbix server to the VSP device to confirm that it returns a value before adding it to your template.

[IG · Accepted solution]

Thanks both for your responses.

I am aware that EXOS and VOSS are very different, but in Zabbix there is no default Template for VOSS devices. So I used the EXOS template which was able to cover many things such as network interface discovery and metrics.

However, there were a few items that unfortunately did not translate over fully. These being CPU utilisation, memory utilisation, Fan & PSU discovery.

For anyone that finds this post who is using Zabbix with the same issue as myself I was able to get this working with the following:

CPU Utilisation: 1.3.6.1.4.1.2272.1.85.10.1.1.2.1
Memory Utilisation: 1.3.6.1.4.1.2272.1.85.10.1.1.8.1
PSU Discovery: 1.3.6.1.4.1.2272.1.4.8.1.1.1
Fan Discovery: 1.3.6.1.4.1.2272.1.101.1.1.4.1.3

[donna641 · Accepted solution]

---

@IG wrote:

Hello. I am trying to monitor our VSP devices with Zabbix and the Extreme Template (EXOS) does not fully translate over 100% on all OID's. I have managed to work out all the other OIDs that were incorrect, but the last one I am stuck on is CPU utilisation %

I have tried 1.3.6.1.4.1.2272.1.85.10.1.1.2 (rcKhiSlotCpuCurrentUtil) but this is not working. Does anybody know which OID I can use?

They are VSP 7400's running VOSS 8.3.1.0

Thanks

---

You've correctly identified the problem: the standard EXOS templates are not compatible with VSP devices because they run a different operating system, VOSS (Virtual Operating System), and use a different set of MIBs. The OID you attempted belongs to a different vendor (`2272` is a KHI Systems OID).

For Extreme VSP devices running VOSS, the most commonly used OID for global CPU utilization is:

**1.3.6.1.4.1.1916.1.32.1.1.1.3.0**

This OID corresponds to `s5GlbMonCpuUtil.0` within the **Extreme-VOSS-S5-GLOBAL-MONITORING-MIB**. This OID will provide the overall CPU utilization percentage for the device.

If you are looking for per-slot or per-module CPU utilization, you may need to use a different OID from the `Extreme-VOSS-ENTITY-MIB`, which often has a table of values indexed by slot number. However, the first OID is the most direct solution for overall device CPU monitoring.

I recommend trying this OID and running a simple `snmpwalk` or `snmpget` command from your Zabbix server to the VSP device to confirm that it returns a value before adding it to your template.

[Brent_Addis]

Hi,

You have mentioned using the EXOS template, and then using the VOSS operating system. They are quite different things from what was once different manufacturers.

I didn't set this up, but one of ours we are using:

Average CPU utilisation (1 minute): 1.3.6.1.4.1.2272.1.1.1.1.1.6

Average CPU utilisation (5 minutes): 1.3.6.1.4.1.2272.1.1.1.1.1.7

Average CPU utilisation (15 minutes): 1.3.6.1.4.1.2272.1.1.1.1.1.8