l MPLS hybrid insertion configuration does not involve the actual networking. It simply demonstrates the MPLS processing capability, that is, a system that does not support MPLS can provide MPLS/MPLS VPN services after configuration of MPLS hybrid insertion.

l For detailed configuration information about service loopback group, ACL, and QoS, refer to related manuals.

l A routing switch running MPLS has the functions of a router. The term "router” in this document refers to a router in a generic sense or a Layer 3 Ethernet switch running MPLS.

l For an S9500 Series routing switch, only line processor units (LPUs) with a suffix of C, CA or CB and VPLS service processor cards (SPCs) support MPLS. For S9500 Series routing switches to support MPLS VPN functions, you need to equip them with MPLS capable LPUs or VPLS SPCs. You can identify the suffix of an LPU by the silkscreen in the upper right corner of the LPU’s front panel. As an example, the silkscreen of an LSB1P4G8CA0 LPU is P4G8CA, and therefore the suffix of the LPU is CA.

1.1 Overview of MPLS Hybrid Insertion

1.1.1 Introduction to Hybrid Insertion

Currently, the device supports both the SPUs with or without the MPLS function. In the following description, these two types of SPUs are respectively referred to as MPLS board and non-MPLS board. In order to provide the MPLS/MPLS VPN service in an environment that does not support the MPLS, a lot of users require adding MPLS SPUs without changing the original networking. To meet this requirement, LPUs supporting MPLS must be configured to redirect the MPLS service to the MPLS SPUs for service processing. With the hybrid insertion feature, the MPLS VPN service can be deployed on boards that do not support MPLS. The device supports the MPLS VPN in several modes. It provides diversified MPLS VPN services to address different MPLS VPN requirements, such as service performance, reliability, and port utilization ratio.

1.1.2 Classification of Hybrid Insertion

Although LPUs with a suffix of C, CA, or CB and L3+ SPUs support the MPLS function, their functions and configurations are different. Accordingly, hybrid insertion is classified into two types: hybrid insertion based on LPUs with a suffix of C, CA, or CB, and hybrid insertion based on L3+ SPUs.

Here, MPLS hybrid insertion includes both L2VPN and L3VPN hybrid insertions.

I. Hybrid insertion based on LPUs with a suffix of C, CA, or CB

l Support hybrid insertion of LPUs with a suffix of C, CA, or CB and non-MPLS SPUs.

l The service at the L3VPN private network side must be redirected to the MPLS service loopback group on the MPLS board for processing.

II. Hybrid insertion based on L3+ SPUs

l Support hybrid insertion of L3+ SPUs and non-L3+ SPUs.

l VPLS service and MPLS packets with the outer label assigned by the public network must be redirected to different virtual service interfaces on the L3+ SPUs for processing.

1.2 Configuring Hybrid Insertion Based on LPUs with a Suffix of C, CA, or CB

Before configuring hybrid insertion based on LPUs with a suffix C, CA, or CB, you need to:

l Configure the MPLS service loopback group.

l Configure the QoS policy to redirect the private network packets to the MPLS service loopback group in the case of L3VPN hybrid insertion.

1.2.1 Configuring Redirection of MPLS Service at Private Network Side

I. Configuration prerequisites

Before redirecting MPLS service at private network side, complete the following tasks:

l Configure the basic MPLS capability.

l Configure the service loopback group with the MPLS processing capability.

II. Configuring MPLS service redirection at private network side

Redirect the MPLS service at the private network side to the service loopback group with the MPLS processing capability.

1.2.2 Configuring MPLS Service Loopback Group

Follow these steps to configure an MPLS service loopback group:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Create a manual aggregation group	link-aggregation group agg-id mode { manual \| static }	Required The type of the aggregation group must be manual.
Set the type of service loopback group to MPLS	link-aggregation group agg-id service-type { ipv6 \| ipv6mc \| mpls \| tunnel }	Required
Add the port of MPLS board to the loopback group	port link-aggregation group agg-id	Required

1.2.3 Configuring Port-based QoS Policy

Follow these steps to configure a port-based QoS policy:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Enter ACL view	acl number acl-number [ match-order { config \| auto } ]	Required
Configure the IP ACL	rule [ rule-id ] { permit \| deny } [ rule-string ]	Required
Enter QACL class view	traffic classifier tcl-name [ operator { and \| or } ]	Required
Configure the rule	if-match match-criteria	Required
Enter QACL behavior view	traffic behavior behavior-name	Required
Configure the behavior	remark service-vlan-id vlan-id-value	Required
Configure the traffic redirection action for the traffic behavior	redirect { cpu \| interface interface-type interface-number \| next-hop { ipv4-add [ ipv4-add ] \| ipv6-add [ interface-type interface-number ] [ ipv6-add [ interface-type interface-number \| link-aggregation group group-number ] ] } }	Required
Enter QoS policy view	qos policy policy-name	Required
Configure the QoS policy	classifier tcl-name behavior behavior-name	Required
Apply QoS policy to the port	qos apply policy policy-name { inbound \| outbound }	Required

& Note:

l Configure the port-based QoS policy only in the case of L3VPN hybrid insertion.

l You can add multiple ports to an MPLS loopback group for load sharing purpose.

l LSB1GV48DA0, LSB1GV48DB0, and LSB1XP4DB0 do not support L2VPN hybrid insertion.

1.3 Configuring Hybrid Insertion Based on L3+ SPUs

Before configuring the hybrid insertion based on L3+ SPUs, you need to:

l Redirect the MPLS and VPLS services at the public network side to the virtual service interface on the L3+ board for processing.

l Bind the VPLS instance with different MPLS-VPLS virtual service interfaces to share the load of VPLS service.

In the configuration of hybrid insertion based on L3+ SPUs, two types of virtual service interface on the L3+ board are used:

l MPLS virtual service interface

l MPLS-VPLS virtual service interface

1.3.1 Configuring MPLS Service Redirection at Public Network Side

MPLS service redirection is to redirect the MPLS service to the MPLS virtual service interface on the L3+ board capable of MPLS processing.

& Note:

The MPLS service here refers to the service processed by the device that functions as a P device. It does not include the L3VPN or VLL services on the PE.

Follow these steps to configure MPLS service redirection at the public network side:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Enter MPLS virtual service interface view	interface MPLS interface-number	—
Redirect the MPLS service to the MPLS virtual service interface on the L3+ board capable of MPLS processing	mpls service binding	Required

1.3.2 Configuring VPLS Service Redirection at Public Network Side

VPLS service redirection is to redirect the VPLS service to the MPLS-VPLS virtual service interface on the L3+ board capable of MPLS processing.

Follow these steps to configure VPLS service redirection at the public network side:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Enter MPLS-VPLS virtual service interface view	interface MPLS-VPLS interface-number	—
Redirect the VPLS service to the MPLS-VPLS virtual service interface on the L3+ board capable of MPLS processing	l2vpn-vpls service binding service-id service-id	Required

1.3.3 Binding VPLS Virtual Service Interface with VPLS Instance

I. Configuration prerequisites

Before binding the VPLS virtual service interface with the VPLS instance, complete the following tasks:

l Configure the VPLS virtual service interface, to which the VPLS service at the public network side is redirected.

l Create a VPLS instance, VSI.

& Note:

For configuration of VPLS instance, refer to VPLS Configuration.

II. Binding VPLS virtual service interface with VPLS instance

By binding the MPLS-VPLS virtual service interface with the VPLS instance, the load can be shared among virtual service interfaces on the L3+ board.

Follow these steps to bind a VPLS virtual service interface with an MPLS-VPLS instance:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Enter MPLS-VPLS virtual service interface view	interface MPLS-VPLS interface-number	—
Specify the VPLS instance to be bound on the MPLS-VPLS virtual service interface	l2vpn-vpls service binding vsi vsi-name	Required

1.3.4 Configuring Backup Interface for Virtual Service Interface

With the backup interface of virtual service interface, the service can be switched to the backup interface once the virtual service interface is in down state, thus ensuring uninterrupted traffic forwarding.

Follow these steps to configure the backup interface for the virtual service interface:

To do...	Use the command...	Remarks
Enter system view	system-view	—
Enter virtual service interface view	interface interface-type interface-number	—
Specify the backup interface for the virtual service interface	backup interface interface-type interface-number	Required

& Note:

l At present, you can configure two virtual service interfaces only for an L3+ board: MPLS virtual service interface and MPLS-VPLS virtual service interface.

l The backup virtual service interface must be in available state and have the same interface type as the active virtual service interface.

1.3.5 Displaying and Maintaining Hybrid Insertion Configuration

To do...	Use the command...	Remarks
Display the current configuration	display current-configuration	Available in any view
Display information about service loopback groups	display link-aggregation service-type [ agg-id ]	Available in any view
Display information about configured IPv4 ACLs	display acl { acl-number \| all }	Available in any view
Display configuration information about a specified class or all classes and the associated actions in a specified or all policies	display qos policy user-defined [ policy-name [ classifier tcl-name ] ]	Available in any view
Display configuration and operation information about policies of a specified interface or all interfaces	display qos policy interface [ interface-type interface-number ] [ inbound \| outbound ]	Available in any view
Display information about configured traffic behaviors	display traffic behavior user-defined [ behavior-name ]	Available in any view
Display information about configured classes	display traffic classifier user-defined [ tcl-name ]	Available in any view

1.4 Hybrid Insertion Configuration Example

1.4.1 Example for Configuring L3VPN Hybrid Insertion

I. Network requirements

l Configure the service loopback group with MPLS processing capability.

l Redirect the service at the L3VPN private network side to the above service loopback group.

II. Network diagram

Figure 1-1 Network diagram for configuring MPLS hybrid insertion

In the figure above:

l CE 1 and CE 3 constitute VPN A. CE 2 and CE 4 constitute VPN B.

l PE 1 and PE 2 are H3C S9500 series routing switches that support the MPLS function. CE 1 and CE 2 are common low-end or mid-range routing devices. CE 3 and CE 4 are Layer-2 switches that directly connect with users.

l LPU configurations are the same on two PEs. A non-MPLS board with FE ports resides in Slot 3, and an MPLS board with GE ports in Slot 2.

III. Configuration procedure

1) Configure CE 1

# Establish the EBGP neighbor relationship between CE 1 and PE 1. Inject a directly connected route and a static route to redistribute the VPN private network user routes of CE 1 to BGP routes and then advertise injected routes to PE 1.

<CE1> system-view

[CE1] vlan 10

[CE1] interface vlan-interface 10

[CE1-vlan-interface10] ip address 10.10.10.10 255.255.255.0

[CE1-vlan-interface10] quit

[CE1] bgp 65410

[CE1-bgp] group vpna external

[CE1-bgp] peer 10.10.10.1 group vpna as-number 100

[CE1-bgp] import-route direct

[CE1-bgp] import-route static

& Note:

The configuration on CE 2 is similar with that on CE 1, and is therefore omitted

2) Configure PE 1

# Configure the global MPLS.

[PE1] mpls lsr-id 1.1.1.1

[PE1] mpls

[PE1] mpls ldp

# Configure a public network interface and enable MPLS on it.

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 1.1.1.1 32

[PE1-LoopBack0] quit

[PE1] vlan 100

[PE1-vlan100] port GigabitEthernet 2/2/1

[PE1-vlan100] interface vlan-interface 100

[PE1-vlan-interface100] ip address 196.168.1.1 255.255.255.0

[PE1-vlan-interface100] mpls

[PE1-vlan-interface100] mpls ldp

[PE1-vlan-interface100] quit

# Start the OSPF on the interface connecting PE 1 and the P routing device and on the loopback interface.

[PE1] ospf 1 router-id 1.1.1.1

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

# Configure the VPN-instance. The configuration on VPN B is similar with that on VPN A. The following provides the configuration on VPN A only.

<PE1> system-view

[PE1] ip vpn-instance vpna

[PE1-vpn-vpna] route-distinguisher 100:1

[PE1-vpn-vpna] vpn-target 100:1 both

[PE1-vpn-vpna] quit

# Configure the MPLS service loopback group:

[PE1] link-aggregation group 1 mode manual

[PE1] link-aggregation group 1 service-type mpls

# Add multiple ports to the MPLS service loopback group.

[PE1] interface GigabitEthernet 2/2/3

[PE1-GigabitEthernet2/2/3] stp disable

[PE1-GigabitEthernet2/2/3] port link-aggregation group 1

[PE1-GigabitEthernet2/2/3] interface GigabitEthernet 2/2/4

[PE1-GigabitEthernet2/2/4] stp disable

[PE1-GigabitEthernet2/2/4] port link-aggregation group 1

# Configure the port-based QoS policy.

[PE1] acl number 2000

[PE1-acl-basic-2000] rule 0 permit source any

[PE1] traffic classifier one

[PE1-classifier-one] if-match acl 2000

[PE1-classifier-one] traffic behavior one

[PE1-behavior-one] remark service-vlan-id 10

[PE1-behavior-one] redirect link-aggregation group 1

[PE1] qos policy one

[PE1-qospolicy-one] classifier one behavior one

[PE1-qospolicy-one] interface Ethernet 3/1/1

[PE1-Ethernet3/1/1] qos apply policy one inbound

[PE1-Ethernet3/1/1] quit

# Configure the VLAN interface.

[PE1] vlan 10

[PE1-vlan10] port Ethernet 3/1/1

[PE1-vlan10] interface vlan-interface 10

[PE1-vlan-interface10] quit

# Bind the VPN A to the VLAN interface that connects PE 1 and CE 1.

[PE1-Vlan-interface10] ip binding vpn-instance vpna

[PE1-Vlan-interface10] ip address 10.10.10.1 24

[PE1-Vlan-interface10] quit

# Establish the EBGP neighbor relationship between PE 1 and CE 1 and inject the interface routes of VPN-instance.

[PE1] bgp 100

[PE1-bgp] ipv4-family vpn-instance vpna

[PE1-bgp-af-vpn-instance] group vpna external

[PE1-bgp-af-vpn-instance] peer 10.10.10.10 group vpna as-number 65410

[PE1-bgp-af-vpn-instance] import-route direct

[PE1-bgp-af-vpn-instance] quit

[PE1-bgp] quit

# Establish the MBGP neighbor relationship between PEs to exchange VPN routing information among PEs. Activate the IBGP peer in VPNv4 address family view.

[PE1] bgp 100

[PE1-bgp] group 100

[PE1-bgp] peer 2.2.2.2 group 100

[PE1-bgp] peer 2.2.2.2 connect-interface loopback0

[PE1-bgp] ipv4-family vpnv4

[PE1-bgp-af-vpn] peer 100 enable

[PE1-bgp-af-vpn] peer 2.2.2.2 group 100

3) Configure the P device

# Configure the global MPLS.

[P] mpls lsr-id 3.3.3.3

[P] mpls

[P] mpls ldp

# Configure an interface and enable MPLS on the interface.

[P] interface loopback0

[P-LoopBack0] ip address 3.3.3.3 32

[P-LoopBack0] quit

[P] vlan 100

[P-vlan100] port GigabitEthernet 2/1/1

[P-vlan100] interface vlan-interface 100

[P-vlan-interface100] ip address 196.168.1.2 255.255.255.0

[P-vlan-interface100] mpls

[P-vlan-interface100] mpls ldp

[P-vlan-interface100] quit

[P] vlan 200

[P-vlan200] port GigabitEthernet 2/1/2

[P-vlan200] interface vlan-interface 200

[P-vlan-interface200] ip address 196.168.2.2 255.255.255.0

[P-vlan-interface200] mpls

[P-vlan-interface200] mpls ldp

[P-vlan-interface200] quit

# Configure the OSPF.

[P] ospf 1 router-id 3.3.3.3

[P-ospf-1] area 0

[P-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 196.168.2.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0

4) Configure PE 2

# Configure the global MPLS.

[PE2] mpls lsr-id 2.2.2.2

[PE2] mpls

[PE2] mpls ldp

# Configure a public network interface and enable MPLS on the interface.

[PE2] interface loopback0

[PE2-LoopBack0] ip address 2.2.2.2 32

[PE2-LoopBack0] quit

[PE2] vlan 200

[PE2-vlan200] port GigabitEthernet 2/2/1

[PE2-vlan200] interface vlan-interface 200

[PE2-vlan-interface200] ip address 196.168.2.1 255.255.255.0

[PE2-vlan-interface200] mpls

[PE2-vlan-interface200] mpls ldp

[PE2-vlan-interface200] quit

# Start the OSPF on the interface connecting PE 2 and the P routing device and on the loopback interface.

[PE2] ospf 1 router-id 2.2.2.2

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] quit

# Configure the VPN-instance. The configuration on VPN B is similar with that on VPN A. The following provides the configuration on VPN A only.

[PE2] ip vpn-instance vpna

[PE2-vpn-vpna] route-distinguisher 100:1

[PE2-vpn-vpna] vpn-target 100:1 both

[PE2-vpn-vpna] quit

# Configure the MPLS service loopback group:

[PE2] link-aggregation group 1 mode manual

[PE2] link-aggregation group 1 service-type mpls

# Add multiple ports to the MPLS service loopback group.

[PE2] inter GigabitEthernet 2/2/3

[PE2-GigabitEthernet2/2/3] stp disable

[PE2-GigabitEthernet2/2/3] port link-aggregation group 1

[PE2-GigabitEthernet2/2/3] interface GigabitEthernet 2/2/4

[PE2-GigabitEthernet2/2/4] stp disable

[PE2-GigabitEthernet2/2/4] port link-aggregation group 1

# Configure the port-based QoS policy:

[PE2] acl number 2000

[PE2-acl-basic-2000] rule 0 permit source any

[PE2] traffic classifier one

[PE2-classifier-one] if-match acl 2000

[PE2-classifier-one] traffi behavior one

[PE2-behavior-one] remark service-vlan-id 10

[PE2-behavior-one] redirect link-aggregation group 1

[PE2] qos policy one

[PE2-qospolicy-one] classifier one behavior one

[PE2-qospolicy-one] interface e3/1/1

[PE2-Ethernet3/1/1] qos apply policy one inbound

[PE2-Ethernet3/1/1] quit

# Bind the VPN A to the VLAN interface that connects PE 2 and CE 3.

[PE2] interface vlan-interface 10

[PE2-vlan-interface10] ip binding vpn-instance vpna

[PE2-vlan-interface10] ip address 20.2.1.2 255.255.255.0

[PE2-vlan-interface10] quit

# Inject the PE 2-CE 3 private network interface route for VPN A.

[PE2] bgp 100

[PE2-bgp] ipv4-family vpn-instance vpna

[PE2-bgp-af-vpn-instance] import-route direct

[PE2-bgp-af-vpn-instance] quit

[PE2-bgp] quit

# Establish the MBGP neighbor relationship between PEs to exchange VPN routing information among PEs. Activate the IBGP peer in VPNv4 address family view.

[PE2] bgp 100

[PE2-bgp] group 100

[PE2-bgp] peer 1.1.1.1 group 100

[PE2-bgp] peer 1.1.1.1 connect-interface loopback0

[PE2-bgp] ipv4-family vpnv4

[PE2-bgp-af-vpn] peer 100 enable

[PE2-bgp-af-vpn] peer 1.1.1.1 group 100

1.4.2 Example for Configuring L2VPN Hybrid Insertion

I. Network requirements

l Configure the service loopback group with MPLS processing capability.

l Redirect the service at the L2VPN private network side to the above service loopback group.

II. Network diagram

Figure 1-2 Network diagram for configuring L2VPN hybrid insertion

In the figure above:

l CE 1 and CE 3 constitute VPNA. CE 2 and CE 3 constitute VPNB.

l LPU configurations are the same on two PEs. A non-MPLS board with FE ports resides in Slot 3, and an MPLS board with a suffix of CA or CB that provides GE ports in Slot 2.

III. Configuration procedure

1) Configure CE 1

# Configure the IP address of the interface.

<CE1> system-view

[CE1] vlan 10

[CE1] interface vlan-interface 10

[CE1-vlan-interface10] ip address 10.10.10.1 255.255.255.0

[CE1-vlan-interface10] quit

2) Configure PE 1

# Configure the global MPLS.

[PE1] mpls lsr-id 1.1.1.1

[PE1] mpls

[PE1] mpls ldp

# Configure a public network interface and enable MPLS on the interface.

[PE1] interface loopback0

[PE1-LoopBack0] ip address 1.1.1.1 32

[PE1-LoopBack0] quit

[PE1] vlan 100

[PE1-vlan100] port GigabitEthernet 2/2/1

[PE1-vlan100] interface vlan-interface 100

[PE1-vlan-interface100] ip address 196.168.1.1 255.255.255.0

[PE1-vlan-interface100] mpls

[PE1-vlan-interface100] mpls ldp

[PE1-vlan-interface100] quit

# Start the OSPF on the interface connecting PE 1 and the P routing device and on the loopback interface.

[PE1] ospf 1 router-id 1.1.1.1

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

# Configure the LDP remote session.

[PE1] mpls ldp remote-peer 1

[PE1-mpls-ldp-remote-1] remote-ip 2.2.2.2

# Configure the MPLS service loopback group:

[PE1] link-aggregation group 1 mode manual

[PE1] link-aggregation group 1 service-type mpls

# Add multiple ports to the MPLS service loopback group.

[PE1] interface GigabitEthernet 2/2/3

[PE1-GigabitEthernet2/2/3] stp disable

[PE1-GigabitEthernet2/2/3] port link-aggregation group 1

[PE1-GigabitEthernet2/2/3] interface GigabitEthernet 2/2/4

[PE1-GigabitEthernet2/2/4] stp disable

[PE1-GigabitEthernet2/2/4] port link-aggregation group 1

# Configure the VLAN interface.

[PE1] vlan 10

[PE1-vlan10] port Ethernet 3/1/1

[PE1-vlan10] interface vlan-interface 10

[PE1-vlan-interface10] quit

# Bind the VPNA to the VLAN interface that connects PE 1 and CE 1.

[PE1-Vlan-interface10] mpls l2vc 2.2.2.2 100

[PE1-Vlan-interface10] quit

3) Configure the P device

# Configure the global MPLS.

[P] mpls lsr-id 3.3.3.3

[P] mpls

[P] mpls ldp

# Configure an interface and enable MPLS on the interface.

[P] interface loopback0

[P-LoopBack0] ip address 3.3.3.3 32

[P-LoopBack0] quit

[P] vlan 100

[P-vlan100] port GigabitEthernet 2/1/1

[P-vlan100] interface vlan-interface 100

[P-vlan-interface100] ip address 196.168.1.2 255.255.255.0

[P-vlan-interface100] mpls

[P-vlan-interface100] mpls ldp

[P-vlan-interface100] quit

[P] vlan 200

[P-vlan200] port GigabitEthernet 2/1/2

[P-vlan200] interface vlan-interface 200

[P-vlan-interface200] ip address 196.168.2.2 255.255.255.0

[P-vlan-interface200] mpls

[P-vlan-interface200] mpls ldp

[P-vlan-interface200] quit

# Configure the OSPF.

[P] ospf 1 router-id 3.3.3.3

[P-ospf-1] area 0

[P-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 196.168.2.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0

4) Configure PE 2

# Configure the global MPLS.

[PE2] mpls lsr-id 2.2.2.2

[PE2] mpls

[PE2] mpls ldp

# Configure a public network interface and enable MPLS on the interface.

[PE2] interface loopback0

[PE2-LoopBack0] ip address 2.2.2.2 32

[PE2-LoopBack0] quit

[PE2] vlan 200

[PE2-vlan200] port GigabitEthernet 2/2/1

[PE2-vlan200] interface vlan-interface 200

[PE2-vlan-interface200] ip address 196.168.2.1 255.255.255.0

[PE2-vlan-interface200] mpls

[PE2-vlan-interface200] mpls ldp

[PE2-vlan-interface200] quit

# Start the OSPF on the interface connecting PE 2 and the P routing device and on the loopback interface.

[PE2] ospf 1 router-id 2.2.2.2

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 196.168.1.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] quit

# Configure the LDP remote session.

[PE2] mpls ldp remote-peer 1

[PE2-mpls-ldp-remote-1] remote-ip 1.1.1.1

# Configure the MPLS service loopback group:

[PE2] link-aggregation group 1 mode manual

[PE2] link-aggregation group 1 service-type mpls

# Add multiple ports to the MPLS service loopback group.

[PE2] interface GigabitEthernet 2/2/3

[PE2-GigabitEthernet2/2/3] stp disable

[PE2-GigabitEthernet2/2/3] port link-aggregation group 1

[PE2-GigabitEthernet2/2/3] interface GigabitEthernet 2/2/4

[PE2-GigabitEthernet2/2/4] stp disable

[PE2-GigabitEthernet2/2/4] port link-aggregation group 1

# Bind the VPNA to the VLAN interface that connects PE 2 and CE 3.

[PE2] interface vlan-interface 10

[PE2-vlan-interface10] mpls l2vc 1.1.1.1 100

[PE2-vlan-interface10] quit

& Note:

l Currently, only MPLS boards with a suffix of CA or CB support VLL (L2VPN). Thus, VLL hybrid insertion includes:

- Hybrid insertion of non-MPLS boards and MPLS boards with a suffix of CA

- Hybrid insertion of MPLS boards with a suffix of C and MPLS boards with a suffix of CA

l All MPLS boards support MPLS L3VPN. Thus, L3VPN hybrid insertion refers to hybrid insertion of non-MPLS boards and MPLS boards only.

l You need to configure the port-based QoS policy for L3VPN hybrid insertion only, but not for VLL hybrid insertion.

1.4.3 Example for Configuring L3+ Hybrid Insertion

I. Network requirements

l Bind the VPLS virtual service interface with the VPLS instance.

l Configure the backup virtual service interface.

II. Network diagram

Figure 1-3 Network diagram for configuring L3+ hybrid insertion

III. Configuration procedure

1) Configure PE 1

# Configure the IGP protocol, which is OSPF in this example.

# Configure the basic MPLS capability.

<Sysname> system-view

[Sysname] sysname PE1

[PE1] interface LoopBack 0

[PE1-LoopBack0] ip address 1.1.1.9 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 1.1.1.9

[PE1] mpls

[PE1-mpls] quit

[PE1] mpls ldp

[PE1-mpls-ldp] quit

# Redirect the service to the virtual service interface on the L3+ board and configure the backup interface for the virtual service interface.

[PE1] interface MPLS-VPLS 0/0/2

[PE1-MPLS-VPLS0/0/2] l2vpn-vpls service binding service-id 1

[PE1-MPLS-VPLS0/0/2] backup interface MPLS-VPLS 1/0/2

[PE1-MPLS-VPLS0/0/2] quit

# Configure VLAN 10 and create VLAN-interface 10.

[PE1] vlan 10

[PE1-vlan10] port Ethernet 4/1/1

[PE1-vlan10] quit

[PE1] interface Vlan-interface 10

[PE1-Vlan-interface10] ip address 10.10.10.10 24

# Configure the basic MPLS capability on the VLAN interface.

[PE1-Vlan-interface10] mpls

[PE1-Vlan-interface10] mpls ldp

[PE1-Vlan-interface10] quit

# Configure MPLS L2VPN.

[PE1] mpls l2vpn

# Configure LDP VPLS instance aaa.

[PE1] vsi aaa static

[PE1-vsi-aaa] pwsignal ldp

[PE1-vsi-aaa-ldp] vsi-id 500

[PE1-vsi-aaa-ldp] peer 2.2.2.9

[PE1-vsi-aaa-ldp] quit

[PE1-vsi-aaa] quit

# Bind the MPLS-VPLS virtual service interface with the VPLS instance aaa.

[PE1] interface MPLS-VPLS 0/0/2

[PE1-MPLS-VPLS0/0/2] l2vpn-vpls service binding vsi aaa

[PE1-MPLS-VPLS0/0/2] quit

# Configure VLAN 100 and create VLAN-interface 100.

[PE1] vlan 100

[PE1-Vlan-100] port Ethernet 4/1/2

[PE1-Vlan-100] interface Vlan-interface 100

# Bind VPLS instance aaa with VLAN-interface 100.

[PE1-Vlan-interface100] l2 binding vsi aaa

2) Configure PE 2

# Configure the IGP protocol, which is OSPF in this example.

# Configure the basic MPLS capability.

<Sysname> system-view

[Sysname] sysname PE2

[PE2] interface Lookback 0

[PE2-LoopBack0] ip address 2.2.2.9 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 2.2.2.9

[PE2] mpls

[PE2-mpls] quit

[PE2] mpls ldp

[PE2-mpls-ldp] quit

# Redirect the service to the virtual service interface on the L3+ board and configure the backup interface for the virtual service interface.

[PE2] interface MPLS-VPLS 0/0/2

[PE2-MPLS-VPLS0/0/2] l2vpn-vpls service binding service-id 1

[PE1-MPLS-VPLS0/0/2] backup interface MPLS-VPLS 1/0/2

[PE2-MPLS-VPLS0/0/2] quit

# Configure VLAN 10 and create VLAN-interface 10.

[PE2] vlan 10

[PE2-vlan10] port Ethernet 4/1/1

[PE2-vlan10] quit

[PE2] interface Vlan-interface 10

[PE2-Vlan-interface10] ip address 10.10.10.11 24

# Configure the basic MPLS capability on the VLAN interface.

[PE2-Vlan-interface10] mpls

[PE2-Vlan-interface10] mpls ldp

[PE2-Vlan-interface10] quit

# Configure MPLS L2VPN.

[PE2] mpls l2vpn

# Configure LDP VPLS instance aaa.

[PE2] vsi aaa static

[PE2-vsi-aaa] pwsignal ldp

[PE2-vsi-aaa-ldp] vsi-id 500

[PE2-vsi-aaa-ldp] peer 1.1.1.9

[PE2-vsi-aaa-ldp] quit

[PE2-vsi-aaa] quit

# Bind the MPLS-VPLS virtual service interface with the VPLS instance aaa.

[PE2] interface MPLS-VPLS 0/0/2

[PE2-MPLS-VPLS0/0/2] l2vpn-vpls service binding vsi aaa

[PE2-MPLS-VPLS0/0/2] quit

# Configure VLAN 100 and create VLAN-interface 100.

[PE2] vlan 100

[PE2-vlan-100] port Ethernet 4/1/2

[PE2-vlan-100] quit

[PE2] interface Vlan-interface 100

# Bind VPLS instance aaa with VLAN-interface 100.

[PE2-Vlan-interface100] l2 binding vsi aaa

3) Verify the configuration

After completing the above configurations, you may perform the display vpls connection on a PE. There should be a PW connection established and in the state of up.

H3C S9500 Operation Manual-Release2132[V2.03]-05 MPLS VPN Volume

1.1.2 Classification of Hybrid Insertion

I. Hybrid insertion based on LPUs with a suffix of C, CA, or CB

II. Hybrid insertion based on L3+ SPUs

I. Configuration prerequisites

II. Configuring MPLS service redirection at private network side

I. Configuration prerequisites

II. Binding VPLS virtual service interface with VPLS instance

I. Network requirements

II. Network diagram

III. Configuration procedure

I. Network requirements

II. Network diagram

III. Configuration procedure

I. Network requirements

II. Network diagram

III. Configuration procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us