H3C-DHCP4-MIB :: h3cDhcpServer2ExpiredTime

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › H3C-DHCP4-MIB › h3cDhcpServer2ExpiredTime

h3cDhcpServer2ExpiredTime

Module: H3C-DHCP4-MIB

OID (symbolic): H3C-DHCP4-MIB::h3cDhcpServer2ExpiredTime

OID (numeric): 1.3.6.1.4.1.2011.10.2.122.2.13.1.3

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Expired time. The structure of the OCTET STRING is month/day/year hour:munite:second (MM/DD/YYYY hh:mm:ss).

What is h3cDhcpServer2ExpiredTime?

The timestamp, as MM/DD/YYYY hh:mm:ss text, when this binding expired.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.122.2.13.1.3
snmpwalk -v2c -c public <target> H3C-DHCP4-MIB::h3cDhcpServer2ExpiredTime

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.122.2.13.1.3.1
snmpget -v2c -c public <target> H3C-DHCP4-MIB::h3cDhcpServer2ExpiredTime.1

Start monitoring H3C router/switch (DHCPv4 server/relay) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the H3C-DHCP4-MIB::h3cDhcpServer2ExpiredTime OID value, configure state conditions and alerts, and monitor any H3C router/switch (DHCPv4 server/relay) from a single console.

OID Breakdown

Upper-level ancestors (9 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.2011huaweiEXPERTV2-MIB
1.3.6.1.4.1.2011.10h3cHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10.2h3cCommonHUAWEI-3COM-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.10.2.122h3cDhcp4H3C-DHCP4-MIB
1.3.6.1.4.1.2011.10.2.122.2h3cDhcpServer2TablesH3C-DHCP4-MIB
1.3.6.1.4.1.2011.10.2.122.2.13h3cDhcpServer2ExpiredTableH3C-DHCP4-MIB
1.3.6.1.4.1.2011.10.2.122.2.13.1h3cDhcpServer2ExpiredEntryH3C-DHCP4-MIB
1.3.6.1.4.1.2011.10.2.122.2.13.1.3h3cDhcpServer2ExpiredTimeH3C-DHCP4-MIB

Module

This MIB depends on