OID reference

ospfRedistributeType

1.3.6.1.4.1.13464.1.2.5.3.2.1.3

Description

OSPF将所引入的自治系统外部路由分成两类:type1和type2, 第一类是指引入的是IGP路由(例如RIP,IGRP,STATIC), 由 于这类路由的可信程度高一些,所以计算出的外部路由的花费 与自治系统内部的路由花费的数量级是相同的,即到第一类外部 路由的花费值 = 本路由器到相应的ASBR的花费值+ASBR到该路由 目的地址的花费值。对于第二类外部路由是指引入的是BGP路由, 由于这类路由的可信度比较低,所以OSPF协议认为从ASBR到自治 系统之外的花费远远大于在自治系统之内到达ASBR的花费。所以 计算路由花费时将主要考虑前者,即到第二类外部路由的花费值 = ASBR到该路由目的地址的花费值。如果该值相等,再考虑本路…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.13464.1.2.5.3.2.1 (ospfRedistributeEntry)
Node code
3
Node name
ospfRedistributeType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.13464.1.2.5.3.2.1.3
URN notation
urn:oid:1.3.6.1.4.1.13464.1.2.5.3.2.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 13464 1 2 5 3 2 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) admin(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) admin(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) greentech(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) greentech(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) admin(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) admin(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) greentech(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) greentech(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) admin(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) admin(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) greentech(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) greentech(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) admin(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) admin(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) greentech(13464) dataCom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) greentech(13464) datacom(1) gbn(2) gbnL3(5) gbnL3OspfMib(3) ospfRedistributeTable(2) ospfRedistributeEntry(1) ospfRedistributeType(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/13464/1/2/5/3/2/1/3
  • /ISO/Identified-Organization/6/1/4/1/13464/1/2/5/3/2/1/3
  • /ISO/3/6/1/4/1/13464/1/2/5/3/2/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/13464/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprise/13464/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprise/admin/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprise/admin/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprise/greentech/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprise/greentech/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/13464/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/13464/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/admin/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/admin/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/greentech/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/enterprises/greentech/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/13464/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/13464/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/admin/dataCom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/admin/datacom/gbn/gbnL3/gbnL3OspfMib/ospfRedistributeTable/ospfRedistributeEntry/ospfRedistributeType
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1type1
2type2

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.

In GBNL3Ospf-MIB, the row index ospfRedistributeProtocal is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.13464.1.2.5.3.2.1.3.<ospfRedistributeProtocal>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.13464.1.2.5.3.2.1.3

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.

ospfRedistributeType OBJECT-TYPE
      SYNTAX   INTEGER    {
                    type1 (1),
                    type2 (2)
                  }
        MAX-ACCESS   read-write
        STATUS   current
        DESCRIPTION
           "OSPF将所引入的自治系统外部路由分成两类:type1和type2,
           第一类是指引入的是IGP路由(例如RIP,IGRP,STATIC), 由
           于这类路由的可信程度高一些,所以计算出的外部路由的花费
           与自治系统内部的路由花费的数量级是相同的,即到第一类外部
           路由的花费值 = 本路由器到相应的ASBR的花费值+ASBR到该路由
           目的地址的花费值。对于第二类外部路由是指引入的是BGP路由,
           由于这类路由的可信度比较低,所以OSPF协议认为从ASBR到自治
           系统之外的花费远远大于在自治系统之内到达ASBR的花费。所以
           计算路由花费时将主要考虑前者,即到第二类外部路由的花费值 
           = ASBR到该路由目的地址的花费值。如果该值相等,再考虑本路
           由器到相应的ASBR的花费值。如果加上前面所述的两种路由类型."
       ::= { ospfRedistributeEntry 3 }

Meaning

Descriptions

1 unique

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

OSPF将所引入的自治系统外部路由分成两类:type1和type2, 第一类是指引入的是IGP路由(例如RIP,IGRP,STATIC), 由 于这类路由的可信程度高一些,所以计算出的外部路由的花费 与自治系统内部的路由花费的数量级是相同的,即到第一类外部 路由的花费值 = 本路由器到相应的ASBR的花费值+ASBR到该路由 目的地址的花费值。对于第二类外部路由是指引入的是BGP路由, 由于这类路由的可信度比较低,所以OSPF协议认为从ASBR到自治 系统之外的花费远远大于在自治系统之内到达ASBR的花费。所以 计算路由花费时将主要考虑前者,即到第二类外部路由的花费值 = ASBR到该路由目的地址的花费值。如果该值相等,再考虑本路 由器到相应的ASBR的花费值。如果加上前面所述的两种路由类型.

Sources for this description

FS.COM 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 1FS.COM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

ospfRedistributeType · currentFS.COM MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: ospfRedistributeType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ospfRedistributeType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "type1",
    "(",
    "1",
    ")",
    ",",
    "type2",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"OSPF将所引入的自治系统外部路由分成两类:type1和type2, 第一类是指引入的是IGP路由(例如RIP,IGRP,STATIC), 由 于这类路由的可信程度高一些,所以计算出的外部路由的花费 与自治系统内部的路由花费的数量级是相同的,即到第一类外部 路由的花费值 = 本路由器到相应的ASBR的花费值+ASBR到该路由 目的地址的花费值。对于第二类外部路由是指引入的是BGP路由, 由于这类路由的可信度比较低,所以OSPF协议认为从ASBR到自治 系统之外的花费远远大于在自治系统之内到达ASBR的花费。所以 计算路由花费时将主要考虑前者,即到第二类外部路由的花费值 = ASBR到该路由目的地址的花费值。如果该值相等,再考虑本路 由器到相应的ASBR的花费值。如果加上前面所述的两种路由类型.\"",
    "::=",
    "{",
    "ospfRedistributeEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "type1",
            1
          ],
          [
            "type2",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "OSPF将所引入的自治系统外部路由分成两类:type1和type2, 第一类是指引入的是IGP路由(例如RIP,IGRP,STATIC), 由 于这类路由的可信程度高一些,所以计算出的外部路由的花费 与自治系统内部的路由花费的数量级是相同的,即到第一类外部 路由的花费值 = 本路由器到相应的ASBR的花费值+ASBR到该路由 目的地址的花费值。对于第二类外部路由是指引入的是BGP路由, 由于这类路由的可信度比较低,所以OSPF协议认为从ASBR到自治 系统之外的花费远远大于在自治系统之内到达ASBR的花费。所以 计算路由花费时将主要考虑前者,即到第二类外部路由的花费值 = ASBR到该路由目的地址的花费值。如果该值相等,再考虑本路 由器到相应的ASBR的花费值。如果加上前面所述的两种路由类型."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.13464)

Ke Qin

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.13464.1.2.5.3.2.1.1 ospfRedistributeProtocal00
1.3.6.1.4.1.13464.1.2.5.3.2.1.2 ospfRedistributeMetric00
1.3.6.1.4.1.13464.1.2.5.3.2.1.4 ospfRedistributeTag00
1.3.6.1.4.1.13464.1.2.5.3.2.1.5 ospfRedistributeStatus00
1.3.6.1.4.1.13464.1.2.5.3.2.1.6 ospfRedistributeAlways00