OID reference
1.3.6.1.4.1.629.10.7.1.2.1.9
The destination of the routing information. This is usually an RPM, joined to DC-RTM on the Routing Protocol Input interface. It can also be set to 'all' or 'all-incl-connected', meaning that this entry applies to all routing information destinations.
Identification
{1 3 6 1 4 1 629 10 7 1 2 1 9}
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.
rtmRedistInfoDest OBJECT-TYPE
SYNTAX InfoSourceDest
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The destination of the routing information. This is usually an
RPM, joined to DC-RTM on the Routing Protocol Input
interface. It can also be set to 'all' or 'all-incl-connected',
meaning that this entry applies to all routing information
destinations."
DEFVAL { infoSourceAll }
::= { rtmRedistEntry 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The destination of the routing information. This is usually an RPM, joined to DC-RTM on the Routing Protocol Input interface. It can also be set to 'all' or 'all-incl-connected', meaning that this entry applies to all routing information destinations.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rtmRedistInfoDest
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rtmRedistInfoDest",
"OBJECT-TYPE",
"SYNTAX",
"InfoSourceDest",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The destination of the routing information. This is usually an RPM, joined to DC-RTM on the Routing Protocol Input interface. It can also be set to 'all' or 'all-incl-connected', meaning that this entry applies to all routing information destinations.\"",
"DEFVAL",
"{",
"infoSourceAll",
"}",
"::=",
"{",
"rtmRedistEntry",
"9",
"}"
],
"syntax_tree": [
[
"row",
"InfoSourceDest"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The destination of the routing information. This is usually an RPM, joined to DC-RTM on the Routing Protocol Input interface. It can also be set to 'all' or 'all-incl-connected', meaning that this entry applies to all routing information destinations."
],
null,
null,
null,
[
"DEFVAL",
"infoSourceAll"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: DC-RTM-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Integer32', 'Unsigned32', 'IpAddress'], 'DC-OSPF-MIB': ['RouterID'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'DC-MASTER-TC': ['AdminStatus', 'OperStatus', 'RouteAction', 'AdminDistance', 'PathType', 'InetSubAddressType', 'BfdSessionStatus', 'NumericIndexOrZero'], 'IANA-RTPROTO-MIB': ['IANAipRouteProtocol'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'MPLS-LSR-STD-MIB': ['MplsIndexType']}Related source files and packages:
Registration