No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


MIB Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).


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

The indexes of this table are mplsL3VpnVrfName and mplsL3VpnIfConfIndex.


Object Name


Max Access


Implemented Specifications




This is a unique index for an entry in the mplsL3VpnIfConfTable.

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 that are enabled for MPLS L3VPN functionality.

This object is implemented as defined in the corresponding MIB files.


INTEGER{carrierOfCarrier (1)enterprise (2)interProvider (3)}


Denotes whether this link can be applied to a carrier's carrier, enterprise, or inter-provider scenario.

Currently, the link can be applied to only carrier's carrier and enterprise scenarios.


BITS{none (0)bgp (1)ospf (2)rip (3)isis (4)static (5)other (6)}


Denotes the route distribution protocol across the PE-CE link.

Note that more than one routing protocol may be enabled at the same time; thus, this object is specified as a bitmask.

For example, static(5) and ospf(2) are a typical configuration.

Currently, the maximum access is read-only.

Currently, only three types of IGP are supported.




The storage type for this VPN If entry. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.

Currently, the maximum access is read-only.

Currently, only the returned value volatile is supported.




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

Rows in this table signify that the specified interface is associated with this VRF.

If the row creation operation succeeds, the interface will have been associated with the specified VRF, otherwise the agent MUST not allow the association.

If the agent only allows read-only operations on this table, it MUST create entries in this table as they are created on the device.

When a row in this table is in active(1) state, no objects in that row can be modified except mplsL3VpnIfConfStorageType and mplsL3VpnIfConfRowStatus.

This object is implemented as defined in the corresponding MIB files.

Create Restriction

Only for attaching of interface to VRF.

Modify Restriction

Only for attaching of interface to VRF.

Delete Restriction

Not Allowed

Access Restriction

The entries in this table can be read without restriction.

Updated: 2019-06-05

Document ID: EDOC1000097213

Views: 120671

Downloads: 681

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next