On which interfaces can MPLS be enabled

15

MPLS can be enabled for the following interfaces:
-GE interface
-GE sub-interface
-XGE interface (in V200R005C10 and later versions)
-XGE sub-interface (in V200R005C10 and later versions)
-Ethernet interface
-Ethernet sub-interface
-Eth-Trunk interface
-Eth-Trunk sub-interface
-Serial interface
-POS interface

In V200R001C01 and later versions, MPLS can be enabled on MP-Group interfaces.
In V200R005C10 and later versions, MPLS can be enabled on IP-Trunk interfaces.

Other related questions:
Which interfaces can be configured with MPLS
MPLS can be configured on the following interfaces: - GE interface - GE sub-interface - XGE interface (V200R005C10 and later versions) - XGE sub-interface (V200R005C10 and later versions) - Ethernet interface - Ethernet sub-interface - Eth-Trunk - Eth-trunk sub-interface - Serial interface - POS interface - MP-Group - IP-Trunk (V200R005C10 and later versions)

How to check whether MPLS is enabled on an AR interface
Run the display mpls interface [ interface-type <interface-number> ] [ verbose ] command to check information about MPLS-enabled interfaces.
[Huawei] display mpls interface
Interface  Status  TE Attr  LSP Count  CRLSP Count Effective MTU
GE1/0/0    Up       Dis        2                   0                        1500
Note:
- Interface: indicates the type and number of the interface enabled with MPLS.
- Status: indicates the status of the interface, which is Up or Down.
- TE Attr: indicates whether the TE attribute is enabled. Dis indicates that the TE attribute is disabled, and En indicates that the TE attribute is enabled.
- LSP Count: indicates the number of established LSPs on the interface.
- CRLSP Count: indicates the number of established CR-LSPs on the interface.
- Effective MTU: indicates the MTU used for forwarding MPLS packets.

USG firewalls supporting interfaces with MPLS attributes
The USG2000, USG5000, and USG6000 support the following interfaces with MPLS attributes: 1. L3 Ethernet interfaces 2. Ethernet subinterfaces 3. VLANIF interfaces 4. L3 Eth-Trunk interfaces 5. Eth-Trunk subinterfaces Note: Tunnel interfaces do not support the MPLS attributes.

On which interfaces does PIM need to be enabled
When receiving a multicast packet, a switch performs Reverse Path Forwarding (RPF) check on the packet and searches for the optimal route to the destination. The outbound interface of the route is the RPF interface and the next hop of the route is the RPF neighbor. A multicast forwarding entry can be created only after PIM is enabled on the RPF interface and the RPF neighbor. In this way, a complete multicast distribution tree can be set up along the forwarding path of the packet. It is recommended that you enable PIM on all non-edge interfaces in the PIM domain because all these interfaces have a chance to become an RPF interface or RPF neighbor. On the switch directly connecting to a multicast source, the RPF interface for packets sent from the multicast source is the interface connected to the multicast source. Therefore, PIM must be enabled on this interface.

Which cards on an S series switch do not support MPLS
Cards' support for MPLS is as follows: - X1E series cards on switches running V200R005 and SA series cards do not support MPLS. - On a switch running V200R005, XGE interfaces connected to the ACU2 card do not support MPLS. - On a switch running V200R005, XGE interfaces connected to the ET1D2IPS0S00, ET1D2FW00S00, ET1D2FW00S01, and ET1D2FW00S02 cards do not support MPLS. - On a switch running V200R005, XGE interfaces connected to the LE1D2FW00S01 card do not support MPLS. - On a switch running a version earlier than V200R008C00, the penultimate device cannot use the LE2D2X48SEC0 card (on the S9300 or S9300E), EH1D2X48SEC0 card (on the S9700), and ET1D2X48SEC0 card (on the S12700) to transmit MPLS services in penultimate hop popping (PHP) scenarios. - Other cards support MPLS.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top