OID reference
1.3.6.1.4.1.29601.2.89.1.2.6.1.3
This object specifies the route distinguisher for the EVPN. This object take Type 0, Type 1 and Type 2 RD as per RFC 4364. In case of auto-discover, Type 0 RD shall be considered.
Identification
{1 3 6 1 4 1 29601 2 89 1 2 6 1 3}
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.
fsEvpnVxlanEviVniMapBgpRD OBJECT-TYPE
SYNTAX EvpnVxlanBgpRD
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies the route distinguisher for the EVPN. This object
take Type 0, Type 1 and Type 2 RD as per RFC 4364.
In case of auto-discover, Type 0 RD shall be considered."
REFERENCE
"[RFC4364]"
::= { fsEvpnVxlanEviVniMapEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This object specifies the route distinguisher for the EVPN. This object take Type 0, Type 1 and Type 2 RD as per RFC 4364. In case of auto-discover, Type 0 RD shall be considered.
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: fsEvpnVxlanEviVniMapBgpRD
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsEvpnVxlanEviVniMapBgpRD",
"OBJECT-TYPE",
"SYNTAX",
"EvpnVxlanBgpRD",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\" This object specifies the route distinguisher for the EVPN. This object take Type 0, Type 1 and Type 2 RD as per RFC 4364. In case of auto-discover, Type 0 RD shall be considered.\"",
"REFERENCE",
"\"[RFC4364]\"",
"::=",
"{",
"fsEvpnVxlanEviVniMapEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"EvpnVxlanBgpRD"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object specifies the route distinguisher for the EVPN. This object take Type 0, Type 1 and Type 2 RD as per RFC 4364. In case of auto-discover, Type 0 RD shall be considered."
],
[
"REFERENCE",
"[RFC4364]"
],
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-VXLAN-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'StorageType', 'MacAddress', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.1 | fsEvpnVxlanEviVniMapEviIndex | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.2 | fsEvpnVxlanEviVniMapVniNumber | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.4 | fsEvpnVxlanEviVniESI | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.5 | fsEvpnVxlanEviVniLoadBalance | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.6 | fsEvpnVxlanEviVniMapSentPkts | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.7 | fsEvpnVxlanEviVniMapRcvdPkts | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.8 | fsEvpnVxlanEviVniMapDroppedPkts | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.9 | fsEvpnVxlanEviVniMapRowStatus | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.6.1.10 | fsEvpnVxlanEviVniMapBgpRDAuto | 0 | 0 |