OID reference

ipDhcpPoolSendRepliesToRelay

1.3.6.1.4.1.272.4.5.52.3.1.16

Description

As soon as a DHCP request includes a client IP address (ciaddr), RFC 1542 recommends that the server unicast the relevant DHCP reply message to the client IP address. Nevertheless, situations exist where it is desirable to send the reply to a BOOTP relay IP address if one has been included in the DHCP request. This ob…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.5.52.3.1 (ipDhcpPoolEntry)
Node code
16
Node name
ipDhcpPoolSendRepliesToRelay
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.5.52.3.1.16
URN notation
urn:oid:1.3.6.1.4.1.272.4.5.52.3.1.16
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 5 52 3 1 16}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpPoolTable(3) ipDhcpPoolEntry(1) ipDhcpPoolSendRepliesToRelay(16)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/272/4/5/52/3/1/16
  • /ISO/Identified-Organization/6/1/4/1/272/4/5/52/3/1/16
  • /ISO/3/6/1/4/1/272/4/5/52/3/1/16
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/biboip/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/biboipold/dynipMIB/ipDhcpPoolTable/ipDhcpPoolEntry/ipDhcpPoolSendRepliesToRelay
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
no

Enumerated values

ValueName
1yes
2no

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: ipDhcpPoolIfIndex, ipDhcpPoolDynAddrPoolId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.272.4.5.52.3.1.16

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

ipDhcpPoolSendRepliesToRelay OBJECT-TYPE
  	SYNTAX      INTEGER { yes(1), no(2) }
	MAX-ACCESS  read-write
	STATUS      current
	DESCRIPTION
	    "As soon as a DHCP request includes a client IP address 
	     (ciaddr), RFC 1542 recommends that the server unicast the 
	     relevant DHCP reply message to the client IP address. 
	     Nevertheless, situations exist where it is desirable to send 
	     the reply to a BOOTP relay IP address if one has been included 
	     in the DHCP request. This object specifies how the DHCP server 
	     must behave in this aspect:
	     - If this object is set to 'no' (default) and a client IP 
	     address was included in the DHCP request, DHCP replies are 
	     sent to this client IP address, regardless of a BOOTP relay 
	     address being included or not in the DHCP request.
	     - If this object is set to 'yes' and a BOOTP relay IP address 
	     was included in the DHCP request, DHCP replies are sent to 
	     this BOOTP relay IP address, regardless of a client IP address 
	     being included or not in the DHCP request."
	DEFVAL { no }
	::= { ipDhcpPoolEntry 16 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

As soon as a DHCP request includes a client IP address (ciaddr), RFC 1542 recommends that the server unicast the relevant DHCP reply message to the client IP address. Nevertheless, situations exist where it is desirable to send the reply to a BOOTP relay IP address if one has been included in the DHCP request. This object specifies how the DHCP server must behave in this aspect: - If this object is set to 'no' (default) and a client IP address was included in the DHCP request, DHCP replies are sent to this client IP address, regardless of a BOOTP relay address being included or not in the DHCP request. - If this object is set to 'yes' and a BOOTP relay IP address was included in the DHCP request, DHCP replies are sent to this BOOTP relay IP address, regardless of a client IP address being included or not in the DHCP request.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

ipDhcpPoolSendRepliesToRelay · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: ipDhcpPoolSendRepliesToRelay

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipDhcpPoolSendRepliesToRelay",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "yes",
    "(",
    "1",
    ")",
    ",",
    "no",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"As soon as a DHCP request includes a client IP address (ciaddr), RFC 1542 recommends that the server unicast the relevant DHCP reply message to the client IP address. Nevertheless, situations exist where it is desirable to send the reply to a BOOTP relay IP address if one has been included in the DHCP request. This object specifies how the DHCP server must behave in this aspect: - If this object is set to 'no' (default) and a client IP address was included in the DHCP request, DHCP replies are sent to this client IP address, regardless of a BOOTP relay address being included or not in the DHCP request. - If this object is set to 'yes' and a BOOTP relay IP address was included in the DHCP request, DHCP replies are sent to this BOOTP relay IP address, regardless of a client IP address being included or not in the DHCP request.\"",
    "DEFVAL",
    "{",
    "no",
    "}",
    "::=",
    "{",
    "ipDhcpPoolEntry",
    "16",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "yes",
            1
          ],
          [
            "no",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "As soon as a DHCP request includes a client IP address (ciaddr), RFC 1542 recommends that the server unicast the relevant DHCP reply message to the client IP address. Nevertheless, situations exist where it is desirable to send the reply to a BOOTP relay IP address if one has been included in the DHCP request. This object specifies how the DHCP server must behave in this aspect: - If this object is set to 'no' (default) and a client IP address was included in the DHCP request, DHCP replies are sent to this client IP address, regardless of a BOOTP relay address being included or not in the DHCP request. - If this object is set to 'yes' and a BOOTP relay IP address was included in the DHCP request, DHCP replies are sent to this BOOTP relay IP address, regardless of a client IP address being included or not in the DHCP request."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "no"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Siblings (15)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.5.52.3.1.1 ipDhcpPoolIfIndex00
1.3.6.1.4.1.272.4.5.52.3.1.2 ipDhcpPoolDynAddrPoolId00
1.3.6.1.4.1.272.4.5.52.3.1.3 ipDhcpPoolAssignmentMode00
1.3.6.1.4.1.272.4.5.52.3.1.4 ipDhcpPoolEnabled00
1.3.6.1.4.1.272.4.5.52.3.1.5 ipDhcpPoolLeaseTime00
1.3.6.1.4.1.272.4.5.52.3.1.6 ipDhcpPoolGateway00
1.3.6.1.4.1.272.4.5.52.3.1.7 ipDhcpPoolRadiusAcct00
1.3.6.1.4.1.272.4.5.52.3.1.8 ipDhcpPoolRadiusGroupId00
1.3.6.1.4.1.272.4.5.52.3.1.9 ipDhcpPoolAliveCheck00
1.3.6.1.4.1.272.4.5.52.3.1.10 ipDhcpPoolAliveInterval00
1.3.6.1.4.1.272.4.5.52.3.1.11 ipDhcpPoolTftpServer100
1.3.6.1.4.1.272.4.5.52.3.1.12 ipDhcpPoolTftpServer200
1.3.6.1.4.1.272.4.5.52.3.1.13 ipDhcpPoolOfferOptionsGroupID00
1.3.6.1.4.1.272.4.5.52.3.1.14 ipDhcpPoolAckOptionsGroupID00
1.3.6.1.4.1.272.4.5.52.3.1.15 ipDhcpPoolGatewayEnabled00