Status in source: current.
Names: mplsVpnVrfRouteXCPointer
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsVpnVrfRouteXCPointer",
"OBJECT-TYPE",
"SYNTAX",
"MplsIndexType",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Index into mplsXCTable which identifies which cross- connect entry is associated with this VRF route entry by containing the mplsXCIndex of that cross-connect entry. The string containing the single octet 0x00 indicates that a label stack is not associated with this route entry. This can be the case because the label bindings have not yet been established, or because some change in the agent has removed them. When the label stack associated with this VRF route is created by the agent, it MUST establish the associated cross-connect entry in the mplsXCTable and then set that index to the value of this object. Changes to the cross-connect object in the mplsXCTable MUST automatically be be reflected the value of this object. If this object represents a static routing entry, then the manager must ensure that this entry is also maintained consistently in the corresponding mplsXCTable as well.\"",
"::=",
"{",
"mplsVpnVrfRouteEntry",
"19",
"}"
],
"syntax_tree": [
[
"row",
"MplsIndexType"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Index into mplsXCTable which identifies which cross- connect entry is associated with this VRF route entry by containing the mplsXCIndex of that cross-connect entry. The string containing the single octet 0x00 indicates that a label stack is not associated with this route entry. This can be the case because the label bindings have not yet been established, or because some change in the agent has removed them. When the label stack associated with this VRF route is created by the agent, it MUST establish the associated cross-connect entry in the mplsXCTable and then set that index to the value of this object. Changes to the cross-connect object in the mplsXCTable MUST automatically be be reflected the value of this object. If this object represents a static routing entry, then the manager must ensure that this entry is also maintained consistently in the corresponding mplsXCTable as well."
],
null,
null,
null,
null
]
}
- IETF historical Internet-Draft definitions
· Publisher's source file: draft-ietf-l3vpn-mpls-vpn-mib-01 — MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base
Module: MPLS-L3VPN-MIB-DRAFT-01
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'TimeStamp', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'experimental', 'Integer32', 'Counter32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'PPVPN-TC-MIB': ['VPNId'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'MPLS-LSR-STD-MIB': ['MplsIndexType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Source data warning: Historical Internet-Draft draft-ietf-l3vpn-mpls-vpn-mib-01; current Datatracker states: RFC, RFC Published. An Internet-Draft is not an RFC or proof of final registration. Its numbers and descriptions may be provisional or obsolete; the SMI STATUS field describes the source object, not the publication status. Consult the exact draft and the relevant device or protocol edition.
Related ASN.1 definitions
mplsVpnVrfRouteXCPointer OBJECT-TYPE
SYNTAX MplsIndexType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Index into mplsXCTable which identifies which cross-
connect entry is associated with this VRF route entry
by containing the mplsXCIndex of that cross-connect entry.
The string containing the single octet 0x00 indicates that
a label stack is not associated with this route entry. This
can be the case because the label bindings have not yet
been established, or because some change in the agent has
removed them.
When the label stack associated with this VRF route is created
by the agent, it MUST establish the associated cross-connect
entry in the mplsXCTable and then set that index to the value
IETF L3 Working Group Expires July 2004 [Page 24]
Internet Draft MPLS L3 VPN MIB January 30, 2004
of this object. Changes to the cross-connect object in the
mplsXCTable MUST automatically be be reflected the value of
this object. If this object represents a static routing entry,
then the manager must ensure that this entry is also maintained
consistently in the corresponding mplsXCTable as well."
::= { mplsVpnVrfRouteEntry 19 }
· Download draft-ietf-l3vpn-mpls-vpn-mib-01 — MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base
Related source files and packages:
Show more related files and packages