OID reference
1.3.6.1.4.1.29601.2.89.1.2.8.1.1
This object specifies the human-readable name of the EVPN VRF. It is strongly recommended that all sites supporting VRFs that are part of the same EVPN use the same naming convention for VRFs.
Identification
{1 3 6 1 4 1 29601 2 89 1 2 8 1 1}
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.
fsEvpnVxlanVrfName OBJECT-TYPE
SYNTAX EvpnVxlanVrfName
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the human-readable name of the EVPN VRF.
It is strongly recommended that all sites supporting
VRFs that are part of the same EVPN use the same
naming convention for VRFs."
::= { fsEvpnVxlanVrfEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This object specifies the human-readable name of the EVPN VRF. It is strongly recommended that all sites supporting VRFs that are part of the same EVPN use the same naming convention for VRFs.
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: fsEvpnVxlanVrfName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsEvpnVxlanVrfName",
"OBJECT-TYPE",
"SYNTAX",
"EvpnVxlanVrfName",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This object specifies the human-readable name of the EVPN VRF. It is strongly recommended that all sites supporting VRFs that are part of the same EVPN use the same naming convention for VRFs.\"",
"::=",
"{",
"fsEvpnVxlanVrfEntry",
"1",
"}"
],
"syntax_tree": [
[
"row",
"EvpnVxlanVrfName"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object specifies the human-readable name of the EVPN VRF. It is strongly recommended that all sites supporting VRFs that are part of the same EVPN use the same naming convention for VRFs."
],
null,
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.8.1.2 | fsEvpnVxlanVrfRD | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.89.1.2.8.1.3 | fsEvpnVxlanVrfRowStatus | 0 | 0 |