OID reference
1.3.6.1.4.1.2076.41.39.1.1.3
Direction of route map to indicate the route map is for in or out. In direction routemap is to apply the routemap rules for incoming routes from the peer.Out direction routemap is to apply the routemap for on the advertising routes to the peer. 1 - in 2 - out
Identification
{1 3 6 1 4 1 2076 41 39 1 1 3}
| Value | Name |
|---|---|
| 1 | in |
| 2 | out |
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. The index encoding is not inferred here.
Published row index: fsBgp4NeighborRouteMapPeerAddrType, fsBgp4NeighborRouteMapPeer, fsBgp4NeighborRouteMapDirection.
A query example is omitted because the source variants do not establish compatible read access.
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.
fsBgp4NeighborRouteMapDirection OBJECT-TYPE
SYNTAX INTEGER{ in(1) ,
out(2)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Direction of route map to indicate the route map is for in or out.
In direction routemap is to apply the routemap rules for incoming routes from
the peer.Out direction routemap is to apply the routemap for on the
advertising routes to the peer.
1 - in
2 - out"
::= { fsBgp4NeighborRouteMapEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Direction of route map to indicate the route map is for in or out. In direction routemap is to apply the routemap rules for incoming routes from the peer.Out direction routemap is to apply the routemap for on the advertising routes to the peer. 1 - in 2 - out
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: fsBgp4NeighborRouteMapDirection
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsBgp4NeighborRouteMapDirection",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"in",
"(",
"1",
")",
",",
"out",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Direction of route map to indicate the route map is for in or out. In direction routemap is to apply the routemap rules for incoming routes from the peer.Out direction routemap is to apply the routemap for on the advertising routes to the peer. 1 - in 2 - out\"",
"::=",
"{",
"fsBgp4NeighborRouteMapEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"in",
1
],
[
"out",
2
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Direction of route map to indicate the route map is for in or out. In direction routemap is to apply the routemap rules for incoming routes from the peer.Out direction routemap is to apply the routemap for on the advertising routes to the peer. 1 - in 2 - out"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-BGP-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'IpAddress', 'Unsigned32', 'Integer32', 'enterprises', 'Gauge32', 'Counter32']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.41.39.1.1.1 | fsBgp4NeighborRouteMapPeerAddrType | 0 | 0 | |
| 1.3.6.1.4.1.2076.41.39.1.1.2 | fsBgp4NeighborRouteMapPeer | 0 | 0 | |
| 1.3.6.1.4.1.2076.41.39.1.1.4 | fsBgp4NeighborRouteMapName | 0 | 0 | |
| 1.3.6.1.4.1.2076.41.39.1.1.5 | fsBgp4NeighborRouteMapRowStatus | 0 | 0 |