MPLS-VPN-MIB-DRAFT-05: View SNMP OID List / Download MIB

This MIB contains managed object definitions for the Multiprotocol Label Switching (MPLS)/Border Gateway Protocol (BGP) Virtual Private Networks (VPNs) as defined in : Rosen, E., Viswanathan, A., and R. Callon, Multiprotocol Label Switching Architecture, RFC3031, January 2001.

This notification is generated when: a. The ifOperStatus of an interface associated with a VRF changes to the up(1) state. b. When an interface with ifOperStatus = up(1) is associated with a VRF.

This notification is generated when: a. The ifOperStatus of an interface associated with a VRF changes to the down(1) state. b. When an interface with ifOperStatus = up(1) state is disassociated with a VRF.

This notification is generated when the number of routes contained by the specified VRF exceeds the value indicated by mplsVrfMidRouteThreshold. A single notification MUST be generated when this threshold is exceeded, and no other notifications of this type should be issued until the value of mplsVpnVrfPerfCurrNumRoutes has fallen below that of mplsVpnVrfConfMidRouteThreshold.

This notification is generated when the number of routes contained by the specified VRF reaches or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold. In cases where mplsVpnVrfConfHighRouteThreshold is set to the same value as mplsVpnVrfConfMaxRoutes, mplsVpnVrfConfHighRouteThreshold need not be exceeded; rather, just reached for this notification to be issued. Note that mplsVpnVrfConfRouteMaxThreshTime denotes the interval at which the this notification will be re-issued after the maximum value has been exceeded (or reached if mplsVpnVrfConfMaxRoutes and mplsVpnVrfConfHighRouteThreshold are equal) and the initial notification has been issued. This value is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added to a VRF after it has reached its maximum value. The default value is 10 minutes. If this value is set to 0, the agent should only issue a single notification at the time that the maximum threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value.

This notification is generated when the number of illegal label violations on a VRF as indicated by mplsVpnVrfSecIllegalLblVltns has exceeded mplsVpnVrfSecIllegalLblRcvThrsh. The threshold is not included in the varbind here because the value of mplsVpnVrfSecIllegalLblVltns should be one greater than the threshold at the time this notification is issued.

This notification is generated only after the number of routes contained by the specified VRF reaches or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold, and then falls below this value. The emission of this notification informs the operator that the error condition has been cleared without the operator having to query the device. Note that mplsVpnVrfConfRouteMaxThreshTime denotes the interval at which the the mplsNumVrfRouteMaxThreshExceeded notification will be re-issued after the maximum value has been exceeded (or reached if mplsVpnVrfConfMaxRoutes and mplsVpnVrfConfHighRouteThreshold are equal) and the initial notification has been issued. Therefore, the generation of this notification should also be emitted with this same frequency (assuming that the error condition is cleared). Specifically, if the error condition is reached and cleared several times during the period of time specified in mplsVpnVrfConfRouteMaxThreshTime, only a single notification will be issued to indicate the first instance of the error condition as well as the first time the error condition is cleared. This behavior is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added and removed to/from a VRF after it has reached its maximum value. The default value is 10 minutes. If this value is set to 0, the agent should issue a notification whenever the maximum threshold has been cleared.

The number of VRFs which are configured on this node.

The number of VRFs which are active on this node. That is, those VRFs whose corresponding mplsVpnVrfOperStatus object value is equal to operational (1).

Total number of interfaces connected to a VRF.

If this object is true, then it enables the generation of all notifications defined in this MIB.

Denotes maximum number of routes which the device will allow all VRFs jointly to hold. If this value is set to 0, this indicates that the device is unable to determine the absolute maximum. In this case, the configured maximum MAY not actually be allowed by the device.

Denotes the interval in seconds, at which the route max threshold notification will be re-issued after the maximum value has been exceeded (or has been reached if mplsVpnVrfConfMaxRoutes and mplsVpnVrfConfHighRouteThreshold are equal) and the initial notification has been issued. This value is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added to a VRF after it has reached its maximum value. The default value is 10 minutes (600 seconds). If this value is set to 0, the agent should only issue a single notification at the time that the maxium threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value.

This table specifies per-interface MPLS capability and associated information.

An entry in this table is created by an LSR for every interface capable of supporting MPLS/BGP VPN. Each entry in this table is meant to correspond to an entry in the Interfaces Table.

This is a unique index for an entry in the MplsVPNInterfaceConfTable. A non-zero index for an entry indicates the ifIndex for the corresponding interface entry in the MPLS-VPN-layer in the ifTable. Note that this table does not necessarily correspond one-to-one with all entries in the Interface MIB having an ifType of MPLS-layer; rather, only those which are enabled for MPLS/BGP VPN functionality.

Either the providerEdge(0) (PE) or customerEdge(1) (CE) bit MUST be set. Enumeration: 'providerEdge': 1, 'customerEdge': 2.

Denotes whether this link participates in a carrier-of-carrier's, enterprise, or inter-provider scenario. Enumeration: 'interProvider': 3, 'carrierOfCarrier': 1, 'enterprise': 2.

Denotes the route distribution protocol across the PE-CE link. Note that more than one routing protocol may be enabled at the same time. Bits: 'none': 0, 'isis': 4, 'rip': 3, 'bgp': 1, 'other': 5, 'ospf': 2.

The storage type for this entry.

The row status for this entry. This value is used to create a row in this table, signifying that the specified interface is to be associated with the specified interface. If this operation succeeds, the interface will have been associated, otherwise the agent would not allow the association. If the agent only allows read-only operations on this table, it will create entries in this table as they are created.

This table specifies per-interface MPLS/BGP VPN VRF Table capability and associated information. Entries in this table define VRF routing instances associated with MPLS/VPN interfaces. Note that multiple interfaces can belong to the same VRF instance. The collection of all VRF instances comprises an actual VPN.

An entry in this table is created by an LSR for every VRF capable of supporting MPLS/BGP VPN. The indexing provides an ordering of VRFs per-VPN interface.

The human-readable name of this VPN. This MAY be equivalent to the RFC2685 VPN-ID, but may also vary. If it is set to the VPN ID, it MUST be equivalent to the value of mplsVpnVrfVpnId. It is strongly recommended that all sites supporting VRFs that are part of the same VPN use the same naming convention for VRFs as well as the same VPN ID.

The VPN ID as specified in RFC 2685. If a VPN ID as not been specified for this VRF, then this variable SHOULD be set to an empty string.

The human-readable description of this VRF.

The route distinguisher for this VRF.

The time at which this VRF entry was created.

Denotes whether a VRF is operational or not. A VRF is up(1) when at least one interface associated with the VRF, which ifOperStatus is up(1). A VRF is down(2) when: a. There does not exist at least one interface whose ifOperStatus is up(1). b. There are no interfaces associated with the VRF. Enumeration: 'down': 2, 'up': 1.

Total number of interfaces connected to this VRF with ifOperStatus = up(1). This counter should be incremented when: a. When the ifOperStatus of one of the connected interfaces changes from down(2) to up(1). b. When an interface with ifOperStatus = up(1) is connected to this VRF. This counter should be decremented when: a. When the ifOperStatus of one of the connected interfaces changes from up(1) to down(2). b. When one of the connected interfaces with ifOperStatus = up(1) gets disconnected from this VRF.

Total number of interfaces connected to this VRF (independent of ifOperStatus type).

Denotes mid-level water marker for the number of routes which this VRF may hold.

Denotes high-level water marker for the number of routes which this VRF may hold.

Denotes maximum number of routes which this VRF is configured to hold. This value MUST be less than or equal to mplsVrfMaxPossibleRoutes unless it is set to 0.

The value of sysUpTime at the time of the last change of this table entry, which includes changes of VRF parameters defined in this table or addition or deletion of interfaces associated with this VRF.

This variable is used to create, modify, and/or delete a row in this table.

The storage type for this entry.

This table specifies per-VRF route target association. Each entry identifies a connectivity policy supported as part of a VPN.

An entry in this table is created by an LSR for each route target configured for a VRF supporting a MPLS/BGP VPN instance. The indexing provides an ordering per-VRF instance.

Auxiliary index for route-targets configured for a particular VRF.

The route target export distribution type. Enumeration: 'import': 1, 'export': 2, 'both': 3.

The route target distribution policy.

Description of the route target.

Row status for this entry.

Each entry in this table specifies a per-interface MPLS/EBGP neighbor.

An entry in this table is created by an LSR for every VRF capable of supporting MPLS/BGP VPN. The indexing provides an ordering of VRFs per-VPN interface.

This is a unique tertiary index for an entry in the MplsVpnVrfBgpNbrAddrEntry Table.

Denotes the role played by this EBGP neighbor with respect to this VRF. Enumeration: 'ce': 1, 'pe': 2.

Denotes the address family of the PE address.

Denotes the EBGP neighbor address.

This variable is used to create, modify, and/or delete a row in this table.

The storage type for this entry.

This table specifies per-VRF vpnv4 multi-protocol prefixes supported by BGP.

An entry in this table is created by an LSR for every BGP prefix associated with a VRF supporting a MPLS/BGP VPN. The indexing provides an ordering of BGP prefixes per VRF.

Address type of the mplsVpnVrfBgpPAtrPeer object.

The IP address of the peer where the path information was learned.

Length in bits of the IP address prefix in the Network Layer Reachability Information field.

Address type of the mplsVpnVrfBgpPAtrIpAddrPrefix object.

An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by mplsVpnVrfBgpPAtrIpAddrPrefixLen. Any bits beyond the length specified by mplsVpnVrfBgpPAtrIpAddrPrefixLen are zeroed.

The ultimate origin of the path information. Enumeration: 'egp': 2, 'incomplete': 3, 'igp': 1.

The sequence of AS path segments. Each AS path segment is represented by a triple . The type is a 1-octet field which has two possible values: 1 AS_SET: unordered set of ASs a route in the UPDATE message has traversed 2 AS_SEQUENCE: ordered set of ASs a route in the UPDATE message has traversed. The length is a 1-octet field containing the number of ASs in the value field. The value field contains one or more AS numbers, each AS is represented in the octet string as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;

Address type of the mplsVpnVrfBgpPAtrNextHop object.

The address of the border router that should be used for the destination network.

This metric is used to discriminate between multiple exit points to an adjacent autonomous system. A value of -1 indicates the absence of this attribute.

The originating BGP4 speaker's degree of preference for an advertised route. A value of -1 indicates the absence of this attribute.

Whether or not the local system has selected a less specific route without selecting a more specific route. Enumeration: 'lessSpecificRrouteNotSelected': 1, 'lessSpecificRouteSelected': 2.

The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute.

Address type of the mplsVpnVrfBgpPAtrAggrAddr object.

The IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute.

The degree of preference calculated by the receiving BGP4 speaker for an advertised route. A value of -1 indicates the absence of this attribute.

An indication of whether or not this route was chosen as the best BGP4 route. Enumeration: 'true': 2, 'false': 1.

One or more path attributes not understood by this BGP4 speaker. Size zero (0) indicates the absence of such attribute(s). Octets beyond the maximum size, if any, are not recorded by this object.

This table specifies per MPLS/BGP VPN VRF Table security features.

An entry in this table is created by an LSR for every VRF capable of supporting MPLS/BGP VPN. Each entry in this table is used to indicate security-related information for each VRF entry.

Indicates the number of illegally received labels on this VPN/VRF.

The number of illegally received labels above which this notification is issued.

This table specifies per MPLS/BGP VPN VRF Table performance information.

An entry in this table is created by an LSR for every VRF capable of supporting MPLS/BGP VPN.

Indicates the number of routes added to this VPN/VRF over the coarse of its lifetime.

Indicates the number of routes removed from this VPN/VRF.

Indicates the number of routes currently used by this VRF.

This table specifies per-interface MPLS/BGP VPN VRF Table routing information. Entries in this table define VRF routing entries associated with the specified MPLS/VPN interfaces. Note that this table contains both BGP and IGP routes, as both may appear in the same VRF.

An entry in this table 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.

The address type of the mplsVpnVrfRouteDest entry.

The destination IP address of this route. This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bit-wise logical-AND of x with the value of the corresponding instance of the mplsVpnVrfRouteMask object is not equal to x.

The address type of mplsVpnVrfRouteMask.

Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the mplsVpnVrfRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the mplsVpnVrfRouteMask by reference to the IP Address Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bit-wise logical-AND of x with the value of the corresponding instance of the mplsVpnVrfRouteDest object is not equal to mplsVpnVrfRouteDest.

The IP TOS Field is used to specify the policy to be applied to this route. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30.

The address type of the mplsVpnVrfRouteNextHopAddrType object.

On remote routes, the address of the next system en route; Otherwise, 0.0.0.0. .

The ifIndex value that identifies the local interface through which the next hop of this route should be reached. If this value is set to 0, this indicates that no interface is associated with this route.

The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for that the next hop is not the final destination. Routes which do not result in traffic forwarding or rejection should not be displayed even if the implementation keeps them stored internally. reject (2) refers to a route which, if matched, discards the message as unreachable. This is used in some protocols as a means of correctly aggregating routes. Enumeration: 'remote': 4, 'other': 1, 'local': 3, 'reject': 2.

The routing mechanism via which this route was learned. Inclusion of values for gateway rout- ing protocols is not intended to imply that hosts should support those protocols. Enumeration: 'esIs': 10, 'isIs': 9, 'ggp': 6, 'ospf': 13, 'ciscoEigrp': 16, 'egp': 5, 'rip': 8, 'bgp': 14, 'idpr': 15, 'ciscoIgrp': 11, 'other': 1, 'bbnSpfIgp': 12, 'icmp': 4, 'local': 2, 'hello': 7, 'netmgmt': 3.

The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.

A reference to MIB definitions specific to the particular routing protocol which is responsi- ble for this route, as determined by the value specified in the route's mplsVpnVrfRouteProto value. If this information is not present, its value SHOULD be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identif-ier, and any implementation conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value.

The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. When this object is unknown or not relevant its value should be set to zero.

The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's mplsVpnVrfRouteProto value. If this metric is not used, its value should be set to -1.

Row status for this table. It is used according to row installation and removal conventions.

Storage type value.

Collection of scalar objects required for MPLS VPN management.

Collection of objects needed for MPLS VPN VRF management.

Collection of objects needed for MPLS VPN interface management.

Collection of objects needed for MPLS VPN performance information.

Collection of objects needed for MPLS VPN bgp neighbor-related information.

Collection of objects needed for MPLS VPN bgp neighbor-related information.

Collection of objects needed for MPLS VPN security-related information.

Objects required for VRF route table management.

Objects required for VRF route target management.

Objects required for MPLS VPN notifications.

Compliance statement for agents that support the MPLS VPN MIB.