CPU - SMP OIDs

[Mohammad-Khan]

The customer is unable to accurately monitor Data-Plane and Management CPU/memory utilization on Prisma SD-WAN ION 1200-S-C5G-WW (Tenant ID: 1285229497, Firmware 6.5.3-i-b10) via NetSpyGlass because previously provided OIDs for these metrics return 'No such object', and required ION-COMMON-MIB and ION-SMI files are not recognized; initial issues included hrProcessorLoad returning 'No such instance', inconsistent tunnel status via OID .1.3.6.1.4.1.50114.10.2.10.1.1.3,

Tried below OIDs for CPU

1.3.6.1.2.1.25.3.3.1.2
1.3.6.1.2.1.25.2.3.1.6.1020
1.3.6.1.4.1.50114.10.1.1.1.0

Can i please other OIDs other then above mentioned OIDs to SNMP data for CPU Data-Plane and Management-Plane

[monika532lara]

On Prisma SD‑WAN ION devices, CPU and memory utilization isn’t exposed through the standard HOST‑RESOURCES‑MIB OIDs you tried. Instead, Palo Alto provides custom OIDs in the ION MIBs: typically 1.3.6.1.2.1.25.3.3.1.2.1 for management‑plane CPU, 1.3.6.1.2.1.25.3.3.1.2.2 for data‑plane CPU, and memory via hrStorageTable under 1.3.6.1.2.1.25.2.3. If those still return “No such object,” it means the firmware build doesn’t expose them via SNMP, and you’ll need to rely on Prisma SD‑WAN’s API/portal metrics rather than alternate OIDs.

[ThomasBehne001]

The `No Such Object` errors and MIB import failures in NetSpyGlass stem from how Prisma SD-WAN separates its underlying Linux management plane from the proprietary data plane on 6.x firmware. Standard Host Resources OIDs like `hrProcessorLoad` are often restricted, while custom enterprise OIDs fail to compile if NetSpyGlass hasn't loaded `ION-SMI` prior to `ION-COMMON-MIB` to define the `.1.3.6.1.4.1.50114` tree. To fix this, ensure the full MIB hierarchy is compiled in order and verify that extended SNMP views are enabled in the controller. If SNMP polling remains unreliable, shifting NetSpyGlass to ingest metrics via the Prisma SD-WAN REST API or telemetry streams is the recommended path for accurate data-plane performance tracking.