Restrictions In Networking Of Various Mpls Cards - H3C S9500 Series Operation Manual

Operation Manual – MPLS
H3C S9500 Series Routing Switches
[PE2-Ethernet3/1/1] flow-template user-defined
[PE2-Ethernet3/1/1] traffic-redirect inbound ip-group 2000 rule 0 link-group
4000 rule 0 interface GigabitEthernet 2/1/1 10 l3-vpn
# Bind VPN A on the VLAN interface between PE2 and CE3.
[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
# Import the interface routes of private network between PE2 and CE 3 for VPNA.
[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 MBGP neighbor relationship between PE and PE to exchange VPN routing
information between PEs and activate IBGP peers 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
Note:
The configuration of L2 VPN VLL intermixing is similar to that of L3VPN intermixing, so
the description of configuration process is omitted. The configuration of L2 VPN VLL
intermixing is also implemented through the traffic-redirect command. You do not
need to customize the flow template needed for VLL redirection and you can use the
default flow template. In addition, the flow template only needs to match Layer 2 ACL of
4000 series and only the VLAN ID needs to be specified in ACL rules.

5.4 Restrictions in Networking of Various MPLS Cards

Chapter 5 Card Intermixing for MPLS Support
5-13