HCP-MIB :: tenantPhysicalBytesUsed

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HCP-MIB › tenantPhysicalBytesUsed

tenantPhysicalBytesUsed

Module: HCP-MIB

OID (symbolic): HCP-MIB::tenantPhysicalBytesUsed

OID (numeric): 1.3.6.1.4.1.116.5.46.4.1.1.24

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Total amount of storage, in bytes, used by all the namespaces owned by the tenant to store object data and metadata. (System Management Console: Tenants)

What is tenantPhysicalBytesUsed?

Total bytes the tenant's namespaces actually use on disk for object data and metadata. This is what counts against storage capacity, and it can exceed the logical size because of copies kept for protection.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.116.5.46.4.1.1.24
snmpwalk -v2c -c public <target> HCP-MIB::tenantPhysicalBytesUsed

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.116.5.46.4.1.1.24.1
snmpget -v2c -c public <target> HCP-MIB::tenantPhysicalBytesUsed.1

Start monitoring Hitachi Content Platform (HCP) storage node/cluster with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HCP-MIB::tenantPhysicalBytesUsed OID value, configure state conditions and alerts, and monitor any Hitachi Content Platform (HCP) storage node/cluster from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.116hitachiHCP-MIB
1.3.6.1.4.1.116.5systemExMibHCP-MIB
1.3.6.1.4.1.116.5.46hcpHCP-MIB
1.3.6.1.4.1.116.5.46.4hcpTenantsHCP-MIB
1.3.6.1.4.1.116.5.46.4.1hcpTenantTableHCP-MIB
1.3.6.1.4.1.116.5.46.4.1.1hcpTenantTableEntryHCP-MIB
1.3.6.1.4.1.116.5.46.4.1.1.24tenantPhysicalBytesUsedHCP-MIB