TUBS-IBR-XEN-MIB :: xenHostCPUs

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › TUBS-IBR-XEN-MIB › xenHostCPUs

xenHostCPUs

Module: TUBS-IBR-XEN-MIB

OID (symbolic): TUBS-IBR-XEN-MIB::xenHostCPUs

OID (numeric): 1.3.6.1.4.1.1575.1.14.1.1.3

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: The total number of CPUs on the physical host.

What is xenHostCPUs?

This value reports the total number of CPUs installed on the physical Xen host. An admin uses it to understand the host's total CPU capacity when planning how many virtual CPUs can reasonably be allocated across guest domains. For example, xenHostCPUs reading 16 tells the admin this host has 16 physical CPU cores available to back virtual CPU allocations.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1575.1.14.1.1.3
snmpwalk -v2c -c public <target> TUBS-IBR-XEN-MIB::xenHostCPUs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1575.1.14.1.1.3.1
snmpget -v2c -c public <target> TUBS-IBR-XEN-MIB::xenHostCPUs.1

Start monitoring Xen hypervisor host, virtualization server (per-domain state/memory/vCPU allocation status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TUBS-IBR-XEN-MIB::xenHostCPUs OID value, configure state conditions and alerts, and monitor any Xen hypervisor host, virtualization server (per-domain state/memory/vCPU allocation status) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1575tubsTUBS-SMI
1.3.6.1.4.1.1575.1ibrTUBS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.1575.1.14xenMIBTUBS-IBR-XEN-MIB
1.3.6.1.4.1.1575.1.14.1xenObjectsTUBS-IBR-XEN-MIB
1.3.6.1.4.1.1575.1.14.1.1xenHostTUBS-IBR-XEN-MIB
1.3.6.1.4.1.1575.1.14.1.1.3xenHostCPUsTUBS-IBR-XEN-MIB