OID reference

iploadBExtHandlingTable

1.3.6.1.4.1.272.4.5.66

Description

The iploadBExtHandlingTable contains IP-related parameters in order to specify special load balancing handling for specific traffic like HTTPS sessions for example. The intention is to share the same load balancing decision (which means usage of the same destination interface) for different but subsequent sessions bel…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.5 (biboip, biboipold)
Node code
66
Node name
iploadBExtHandlingTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.5.66
URN notation
urn:oid:1.3.6.1.4.1.272.4.5.66
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 5 66}

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

SNMP properties

Value type
SEQUENCE OF IploadBExtHandlingEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

iploadBExtHandlingTable OBJECT-TYPE
	    SYNTAX SEQUENCE OF IploadBExtHandlingEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                "The iploadBExtHandlingTable contains IP-related parameters
		 in order to specify special load balancing handling
		 for specific traffic like HTTPS sessions for example.
		 The intention is to share the same load balancing decision
		 (which means usage of the same destination interface) for
		 different but subsequent sessions belonging together on higher
		 level context. This stickiness of a load balancing decision
		 has a configurable minimum livetime.
		 Entries can only be added or deleted by the user."

        ::= { biboip 66 }

Meaning

Descriptions

1 unique

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

The iploadBExtHandlingTable contains IP-related parameters in order to specify special load balancing handling for specific traffic like HTTPS sessions for example. The intention is to share the same load balancing decision (which means usage of the same destination interface) for different but subsequent sessions belonging together on higher level context. This stickiness of a load balancing decision has a configurable minimum livetime. Entries can only be added or deleted by the user.

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

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

Status in source: current.

Names: iploadBExtHandlingTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "iploadBExtHandlingTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "IploadBExtHandlingEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The iploadBExtHandlingTable contains IP-related parameters in order to specify special load balancing handling for specific traffic like HTTPS sessions for example. The intention is to share the same load balancing decision (which means usage of the same destination interface) for different but subsequent sessions belonging together on higher level context. This stickiness of a load balancing decision has a configurable minimum livetime. Entries can only be added or deleted by the user.\"",
    "::=",
    "{",
    "biboip",
    "66",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "IploadBExtHandlingEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The iploadBExtHandlingTable contains IP-related parameters in order to specify special load balancing handling for specific traffic like HTTPS sessions for example. The intention is to share the same load balancing decision (which means usage of the same destination interface) for different but subsequent sessions belonging together on higher level context. This stickiness of a load balancing decision has a configurable minimum livetime. Entries can only be added or deleted by the user."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.5.66.1 iploadBExtHandlingEntry1616

Siblings (65)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.5.55 bootprelayMIB112
1.3.6.1.4.1.272.4.5.56 msdpMIB165
1.3.6.1.4.1.272.4.5.57 ipLfiTable16
1.3.6.1.4.1.272.4.5.58 ipRTPSessionTable114
1.3.6.1.4.1.272.4.5.60 ipNatExcludeTable113
1.3.6.1.4.1.272.4.5.61 ipNatOutOperTable119
1.3.6.1.4.1.272.4.5.62 hacc680
1.3.6.1.4.1.272.4.5.63 ipNatPresetOperTable116
1.3.6.1.4.1.272.4.5.64 ipDropinGroupTable117
1.3.6.1.4.1.272.4.5.65 ipDropinIfTable16
1.3.6.1.4.1.272.4.5.67 ipWolRuleTable110
1.3.6.1.4.1.272.4.5.249 ipDropinMIB00
1.3.6.1.4.1.272.4.5.250 ipExtMIB00
1.3.6.1.4.1.272.4.5.251 dnsMIB00
1.3.6.1.4.1.272.4.5.252 iploadbMIB00