Status in source: current.
Names: fsMplsL3VpnVrfEgressRteEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMplsL3VpnVrfEgressRteEntry",
"OBJECT-TYPE",
"SYNTAX",
"FsMplsL3VpnVrfEgressRteEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This object specifies an entry in the fsMplsL3VpnVrfEgressRteTable which is created by an LSR for every route present configured (either dynamically or statically) within the context of a specific VRF capable of supporting MPLS/BGP VPN. The indexing provides an ordering of VRFs per-VPN interface. Implementers need to be aware that there are quite a few index objects that together can exceed the size allowed for an Object Identifier (OID). So implementers must make sure that OIDs of column instances in this table will have no more than 128 sub-identifiers, otherwise they cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.\"",
"INDEX",
"{",
"fsMplsL3VpnVrfEgressRtePathAttrLabel",
"}",
"::=",
"{",
"fsMplsL3VpnVrfEgressRteTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"FsMplsL3VpnVrfEgressRteEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object specifies an entry in the fsMplsL3VpnVrfEgressRteTable which is created by an LSR for every route present configured (either dynamically or statically) within the context of a specific VRF capable of supporting MPLS/BGP VPN. The indexing provides an ordering of VRFs per-VPN interface. Implementers need to be aware that there are quite a few index objects that together can exceed the size allowed for an Object Identifier (OID). So implementers must make sure that OIDs of column instances in this table will have no more than 128 sub-identifiers, otherwise they cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
],
null,
null,
[
"INDEX",
[
[
0,
"fsMplsL3VpnVrfEgressRtePathAttrLabel"
]
]
],
null
]
}