DHCP-V4-RELAY-MIB :: dhcpv4RelaySystemObjectID

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DHCP-V4-RELAY-MIB › dhcpv4RelaySystemObjectID

dhcpv4RelaySystemObjectID

Module: DHCP-V4-RELAY-MIB

OID (symbolic): DHCP-V4-RELAY-MIB::dhcpv4RelaySystemObjectID

OID (numeric): 1.3.6.1.2.1.0.3.1.1.2

Node type: OBJECT-TYPE

Type: OBJECT IDENTIFIER

Access: read-only

Description: The vendor's authoritative identification of the network management subsystem contained in this entity. This value is allocated within the SMI enterprise subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining what kind of relay is being managed. For example, if vendor Ohso Soft, Inc. is assigned the subtree 1.3.6.1.4.1.4242, it may assign the identifier 1.3.6.1.4.1.4242.1.1 to its Ursa DHCP Relay.

What is dhcpv4RelaySystemObjectID?

This object returns an OID that uniquely identifies the vendor and model of the DHCP relay implementation running on this device, drawn from the vendor's private enterprise subtree. An admin can read it to programmatically determine what kind of relay is being managed without depending on a free-text sysDescr string. As the MIB's own example illustrates, a vendor assigned enterprise number 1.3.6.1.4.1.4242 might publish 1.3.6.1.4.1.4242.1.1 here to identify its "Ursa DHCP Relay" product.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.0.3.1.1.2
snmpwalk -v2c -c public <target> DHCP-V4-RELAY-MIB::dhcpv4RelaySystemObjectID

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.0.3.1.1.2.1
snmpget -v2c -c public <target> DHCP-V4-RELAY-MIB::dhcpv4RelaySystemObjectID.1

Start monitoring Router/Layer 3 switch (vendor-neutral, DHCP/BOOTP relay agent, RFC draft) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DHCP-V4-RELAY-MIB::dhcpv4RelaySystemObjectID OID value, configure state conditions and alerts, and monitor any Router/Layer 3 switch (vendor-neutral, DHCP/BOOTP relay agent, RFC draft) 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.0dhcpDHCP-V4-RELAY-MIB
1.3.6.1.2.1.0.3dhcpv4RelayDHCP-V4-RELAY-MIB
1.3.6.1.2.1.0.3.1dhcpv4RelayObjectsDHCP-V4-RELAY-MIB
1.3.6.1.2.1.0.3.1.1dhcpv4RelaySystemDHCP-V4-RELAY-MIB
1.3.6.1.2.1.0.3.1.1.2dhcpv4RelaySystemObjectIDDHCP-V4-RELAY-MIB