Reference record for OID 1.3.6.1.4.1.5.1.1.23.1.7

Parent
1.3.6.1.4.1.5.1.1.23.1 (ipMultiPathEntry)
Node code
7
Node name
ipMultiPathType
Numeric OID
1.3.6.1.4.1.5.1.1.23.1.7
URN notation
urn:oid:1.3.6.1.4.1.5.1.1.23.1.7
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 4 1 5 1 1 23 1 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) acc(5) accSBAR(1) accBRG(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) acc(5) accSBAR(1) sbe4000(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) acc(5) accSBEngr(1) accBRG(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) acc(5) accSBEngr(1) sbe4000(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) acc(5) accSBAR(1) accBRG(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) acc(5) accSBAR(1) sbe4000(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) acc(5) accSBEngr(1) accBRG(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) acc(5) accSBEngr(1) sbe4000(1) ipMultiPathTable(23) ipMultiPathEntry(1) ipMultiPathType(7)}
  • ...skipped...
OID-IRI notation
  • /1/3/6/1/4/1/5/1/1/23/1/7
  • /ISO/Identified-Organization/6/1/4/1/5/1/1/23/1/7
  • /ISO/3/6/1/4/1/5/1/1/23/1/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/acc/accSBAR/accBRG/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprise/acc/accSBAR/sbe4000/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprise/acc/accSBEngr/accBRG/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprise/acc/accSBEngr/sbe4000/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprises/acc/accSBAR/accBRG/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprises/acc/accSBAR/sbe4000/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprises/acc/accSBEngr/accBRG/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • /iso/identified-organization/dod/internet/private/enterprises/acc/accSBEngr/sbe4000/ipMultiPathTable/ipMultiPathEntry/ipMultiPathType
  • ...skipped...
All recorded component names

Each component can use any of its recorded names. The examples above show up to eight combinations. ASN.1 names do not necessarily have registered OID-IRI labels.

  • 1: iso
  • 1.3: identified-organization, org, iso-identified-organization
  • 1.3.6: dod
  • 1.3.6.1: internet
  • 1.3.6.1.4: private
  • 1.3.6.1.4.1: enterprise, enterprises
  • 1.3.6.1.4.1.5: acc
  • 1.3.6.1.4.1.5.1: accSBAR, accSBEngr
  • 1.3.6.1.4.1.5.1.1: accBRG, sbe4000
  • 1.3.6.1.4.1.5.1.1.23: ipMultiPathTable
  • 1.3.6.1.4.1.5.1.1.23.1: ipMultiPathEntry
  • 1.3.6.1.4.1.5.1.1.23.1.7: ipMultiPathType

Source records

The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP archi- tecture. Setting this object to the value in- valid(2) has the effect of invalidating the corresponding entry in the ipMultiPathTable ob- ject. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not current- ly in use. Proper interpretation of such en- tries requires examination of the relevant ip- ForwardType object.

Status in source: mandatory.

Names: ipMultiPathType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipMultiPathType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "invalid",
    "(",
    "2",
    ")",
    ",",
    "direct",
    "(",
    "3",
    ")",
    ",",
    "indirect",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\" The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP archi- tecture. Setting this object to the value in- valid(2) has the effect of invalidating the corresponding entry in the ipMultiPathTable ob- ject. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not current- ly in use. Proper interpretation of such en- tries requires examination of the relevant ip- ForwardType object.\"",
    "::=",
    "{",
    "ipMultiPathEntry",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "invalid",
            2
          ],
          [
            "direct",
            3
          ],
          [
            "indirect",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP archi- tecture. Setting this object to the value in- valid(2) has the effect of invalidating the corresponding entry in the ipMultiPathTable ob- ject. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not current- ly in use. Proper interpretation of such en- tries requires examination of the relevant ip- ForwardType object."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Preserved mibdepot archive · Archived source file
    Source location: ACC-MIB::ipMultiPathType.
    Source version and references

    Archived: 2026-10-19T00:22:07.099514+00:00. SHA-256: e149fdca45a5f60079f8673df3f9a2e046419532e7d4ec2ff312a21c5535b3fe

    {'kind': 'OBJECT-TYPE', 'details': {'module': 'ACC-MIB', 'imports': {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['enterprises', 'Counter', 'Gauge', 'IpAddress', 'NetworkAddress', 'TimeTicks'], 'RFC1213-MIB': ['ifIndex', 'ipRouteDest', 'ipAdEntAddr', 'egpNeighAddr'], 'RFC1243-MIB': ['atportIndex']}, 'smi_kind': 'OBJECT-TYPE', 'definition': 'ipMultiPathType OBJECT-TYPE\r\n             SYNTAX   INTEGER {\r\n                         other(1),   -- not specified by this MIB\r\n                         invalid(2),   -- logically deleted\r\n                         direct(3),   -- local interface\r\n                         indirect(4)    -- remote destination\r\n                      }\r\n             ACCESS   read-write\r\n             STATUS   mandatory\r\n            DESCRIPTION\r\n                 " The type  of  route.   Note  that  the  values\r\n                   direct(3)  and  indirect(4) refer to the notion\r\n                   of direct and indirect routing in the IP archi-\r\n                   tecture.   Setting this object to the value in-\r\n                   valid(2) has the  effect  of  invalidating  the\r\n                   corresponding  entry  in the ipMultiPathTable ob-\r\n                   ject.  That is,  it  effectively  dissasociates\r\n                   the destination identified with said entry from\r\n                   the route identified with said entry.  It is an\r\n                   implementation-specific  matter  as  to whether\r\n                   the agent removes an invalidated entry from the\r\n                   table.   Accordingly,  management stations must\r\n                   be prepared to receive tabular information from\r\n                   agents that corresponds to entries not current-\r\n                   ly in use.  Proper interpretation of  such  en-\r\n                   tries  requires examination of the relevant ip-\r\n                   ForwardType object."\r\n            ::= { ipMultiPathEntry 7 }', 'syntax_tree': [['SimpleSyntax', 'INTEGER', ['enumSpec', [['other', 1], ['invalid', 2], ['direct', 3], ['indirect', 4]]]], None, ['MaxAccessPart', 'read-write'], ['Status', 'mandatory'], ['DESCRIPTION', 'The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP archi- tecture. Setting this object to the value in- valid(2) has the effect of invalidating the corresponding entry in the ipMultiPathTable ob- ject. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not current- ly in use. Proper interpretation of such en- tries requires examination of the relevant ip- ForwardType object.'], None, None, None, None], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

ipMultiPathtype
View at oid-base.com

Alternative description: Circitor

The type of route. Note that the values
direct(3) and indirect(4) refer to the notion
of direct and indirect routing in the IP archi-
tecture. Setting this object to the value in-
valid(2) has the effect of invalidating the
corresponding entry in the ipMultiPathTable ob-
ject. That is, it effectively dissasociates
the destination identified with said entry from
the route identified with said entry. It is an
implementation-specific matter as to whether
the agent removes an invalidated entry from the
table. Accordingly, management stations must
be prepared to receive tabular information from
agents that corresponds to entries not current-
ly in use. Proper interpretation of such en-
tries requires examination of the relevant ip-
ForwardType object.

Parsed from file ACC-IP.mib
Module: ACC-IP

Source file: Download ACC-IP.mib SHA-256: 6813bc045b18b1969866105d18df98688ecd6a5c2fe9a86649f831ee3a15f140

Source file: Download ericsson/acc-mib_12_4_0.mib.txt SHA-256: 297150331610307e0c6c4bcca9aff63408b8db5c1b743e049e1a760a7561b471

Source file: Download acc/accIpMpath.my.txt SHA-256: 95511afdebbcdab810aff659127b6cd42a4e85652a28ad784bb829970de000ee

Alternative description: MIBdepot

The type of route. Note that the values
direct(3) and indirect(4) refer to the notion
of direct and indirect routing in the IP archi-
tecture. Setting this object to the value in-
valid(2) has the effect of invalidating the
corresponding entry in the ipMultiPathTable ob-
ject. That is, it effectively dissasociates
the destination identified with said entry from
the route identified with said entry. It is an
implementation-specific matter as to whether
the agent removes an invalidated entry from the
table. Accordingly, management stations must
be prepared to receive tabular information from
agents that corresponds to entries not current-
ly in use. Proper interpretation of such en-
tries requires examination of the relevant ip-
ForwardType object.

Source file: Download ericsson/mib_txt_12_3_1_5.txt SHA-256: 6e5a467219721141d6f9e1c3a07a1c9d9c30ad6b6af4918e62cab182b7fda9b5

Information from OID Repository

Vendor: ACC
Module: ACC-IP

[Automatically extracted from oidview.com]

Information from MIBdepot

ipMultiPathType OBJECT-TYPE
             SYNTAX   INTEGER {
                         other(1),   
                         invalid(2),   
                         direct(3),   
                         indirect(4)    
                      }
             ACCESS   read-write
             STATUS   obsolete
            ::= { ipMultiPathEntry 7 }

Information from Circitor

ipMultiPathType OBJECT-TYPE
             SYNTAX   INTEGER {
                         other(1),   
                         invalid(2),   
                         direct(3),   
                         indirect(4)    
                      }
             ACCESS   read-write
             STATUS   obsolete
            DESCRIPTION
                 " The type  of  route.   Note  that  the  values
                   direct(3)  and  indirect(4) refer to the notion
                   of direct and indirect routing in the IP archi-
                   tecture.   Setting this object to the value in-
                   valid(2) has the  effect  of  invalidating  the
                   corresponding  entry  in the ipMultiPathTable ob-
                   ject.  That is,  it  effectively  dissasociates
                   the destination identified with said entry from
                   the route identified with said entry.  It is an
                   implementation-specific  matter  as  to whether
                   the agent removes an invalidated entry from the
                   table.   Accordingly,  management stations must
                   be prepared to receive tabular information from
                   agents that corresponds to entries not current-
                   ly in use.  Proper interpretation of  such  en-
                   tries  requires examination of the relevant ip-
                   ForwardType object."
            ::= { ipMultiPathEntry 7 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5)

Berggreen Art

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5.1.1.23.1.1 ipMultiPathDest00 The destination IP address of this route. An
entry with a value of 0.0.0.0 is considered a
default route.
1.3.6.1.4.1.5.1.1.23.1.2 ipMultiPathPolicy00 An instantiator for the relevant policy table.
1.3.6.1.4.1.5.1.1.23.1.3 ipMultiPathIfIndex00 The index value which uniquely identifies the
local interface through which the next hop of
this route should be reached. T…
1.3.6.1.4.1.5.1.1.23.1.4 ipMultiPathMask00 Indicate the mask to be logical-ANDed with the
destination address before being compared to
the value in the ipMultiPathDes…
1.3.6.1.4.1.5.1.1.23.1.5 ipMultiPathNextHop00 The IP address of the next hop of this route.
(In the case of a route bound to an interface
which is realized via a broadcast…
1.3.6.1.4.1.5.1.1.23.1.6 ipMultiPathMetric00 The primary routing metric for this route.
The semantics of this metric are determined by
the routing-protocol specified in …
1.3.6.1.4.1.5.1.1.23.1.8 ipMultiPathProto00 The routing mechanism via which this route was
learned.
1.3.6.1.4.1.5.1.1.23.1.9 ipMultiPathAge00 The number of seconds since this route was
last updated or otherwise determined to be
correct. Note that no semantics o…
1.3.6.1.4.1.5.1.1.23.1.10 ipMultiPathApplId00 Adaptive routing application identifier.