HCP-MIB :: systemDplUnsafe

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HCP-MIB › systemDplUnsafe

systemDplUnsafe

Module: HCP-MIB

OID (symbolic): HCP-MIB::systemDplUnsafe

OID (numeric): 1.3.6.1.4.1.116.5.46.7.1.14

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indication of whether (1) or not (2) the HCP system DPL setting is below what is considered safe. It is highly recommended that systems with internal storage have a DPL of at least two.

What is systemDplUnsafe?

Says whether the system's DPL (data protection level, the number of copies kept) is below what is considered safe: yes(1) or no(2). The source recommends a DPL of at least two for systems with internal storage; a yes means a single disk failure can lose data.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.116.5.46.7.1.14
snmpwalk -v2c -c public <target> HCP-MIB::systemDplUnsafe

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.116.5.46.7.1.14.1
snmpget -v2c -c public <target> HCP-MIB::systemDplUnsafe.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::systemDplUnsafe 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.7hcpMonitoringHCP-MIB
1.3.6.1.4.1.116.5.46.7.1systemStatusHCP-MIB
1.3.6.1.4.1.116.5.46.7.1.14systemDplUnsafeHCP-MIB