OID reference

lanIpRipVersion

1.3.6.1.4.1.890.1.2.1.3.3.4

Description

This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.890.1.2.1.3.3 (lanTcpIp)
Node code
4
Node name
lanIpRipVersion
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.890.1.2.1.3.3.4
URN notation
urn:oid:1.3.6.1.4.1.890.1.2.1.3.3.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 890 1 2 1 3 3 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyxel(890) products(1) prestige(2) prestigeCommon(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyxel(890) products(1) prestige(2) prestigeCommon(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyxel(890) products(1) prestige(2) pSysVariables(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyxel(890) products(1) prestige(2) pSysVariables(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyXEL(890) products(1) prestige(2) prestigeCommon(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyXEL(890) products(1) prestige(2) prestigeCommon(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyXEL(890) products(1) prestige(2) pSysVariables(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zyXEL(890) products(1) prestige(2) pSysVariables(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyxel(890) products(1) prestige(2) prestigeCommon(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyxel(890) products(1) prestige(2) prestigeCommon(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyxel(890) products(1) prestige(2) pSysVariables(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyxel(890) products(1) prestige(2) pSysVariables(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyXEL(890) products(1) prestige(2) prestigeCommon(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyXEL(890) products(1) prestige(2) prestigeCommon(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyXEL(890) products(1) prestige(2) pSysVariables(1) pSysRouteIP(3) lanTcpIp(3) lanIpRipVersion(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zyXEL(890) products(1) prestige(2) pSysVariables(1) prestigeLAN(3) lanTcpIp(3) lanIpRipVersion(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/890/1/2/1/3/3/4
  • /ISO/Identified-Organization/6/1/4/1/890/1/2/1/3/3/4
  • /ISO/3/6/1/4/1/890/1/2/1/3/3/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/prestige/prestigeCommon/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/prestige/prestigeCommon/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/prestige/pSysVariables/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/prestige/pSysVariables/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/Prestige/prestigeCommon/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/Prestige/prestigeCommon/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/Prestige/pSysVariables/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/products/Prestige/pSysVariables/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/prestige/prestigeCommon/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/prestige/prestigeCommon/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/prestige/pSysVariables/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/prestige/pSysVariables/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/Prestige/prestigeCommon/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/Prestige/prestigeCommon/prestigeLAN/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/Prestige/pSysVariables/pSysRouteIP/lanTcpIp/lanIpRipVersion
  • /iso/identified-organization/dod/internet/private/enterprise/ZyXEL/Products/Prestige/pSysVariables/prestigeLAN/lanTcpIp/lanIpRipVersion
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

Notes below names come from selected MIB definitions.

ValueName and source notes
1ohter
none of the following
2rip1
3rip2B
4rip2M

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.890.1.2.1.3.3.4.0

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.

lanIpRipVersion OBJECT-TYPE
		SYNTAX  INTEGER {
			ohter(1),          -- none of the following
			rip1(2),
			rip2B(3),
			rip2M(4)
		}
		ACCESS  read-write
		STATUS  mandatory
		DESCRIPTION
			"This object controls the format and the broadcasting 
			method of the RIP packets that the Prestige sends (it 
			recognizes both formats when receiving). RIP-1 is 
			universally supported; but RIP-2 carries more 
			information. RIP-1 is probably adequate for most 
			networks, unless you have a unusual network topology.
			Both RIP-2B and RIP-2M sends the routing data in 
			RIP-2 format; the difference being that RIP-2B uses
			subnet broadcasting while RIP-2M uses multicasting."
		::= { lanTcpIp 4 }

Meaning

Descriptions

1 unique

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

This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B and RIP-2M sends the routing data in RIP-2 format; the difference being that RIP-2B uses subnet broadcasting while RIP-2M uses multicasting.

Sources for this description

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

Description 1

lanIpRipVersion · mandatoryZyxel MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: lanIpRipVersion

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lanIpRipVersion",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "ohter",
    "(",
    "1",
    ")",
    ",",
    "rip1",
    "(",
    "2",
    ")",
    ",",
    "rip2B",
    "(",
    "3",
    ")",
    ",",
    "rip2M",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B and RIP-2M sends the routing data in RIP-2 format; the difference being that RIP-2B uses subnet broadcasting while RIP-2M uses multicasting.\"",
    "::=",
    "{",
    "lanTcpIp",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "ohter",
            1
          ],
          [
            "rip1",
            2
          ],
          [
            "rip2B",
            3
          ],
          [
            "rip2M",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B and RIP-2M sends the routing data in RIP-2 format; the difference being that RIP-2B uses subnet broadcasting while RIP-2M uses multicasting."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.890)

Harry Chou

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.890.1.2.1.3.3.1 lanIpAddress00
1.3.6.1.4.1.890.1.2.1.3.3.2 lanIpSubnetMask00
1.3.6.1.4.1.890.1.2.1.3.3.3 lanIpRipDirection00
1.3.6.1.4.1.890.1.2.1.3.3.5 lanIpMulticast00