Example for Configuring the Pipe MPLS DiffServ Mode
Networking Requirements
As shown in Figure 1, CE1 and CE3 are in VPN-A. CE2 and CE4 are in VPN-B. The VPN target attribute of VPN-A is 111:1, and that of VPN-B is 222:2. Users in different VPNs cannot access each other. The MPLS DiffServ mode is set to Pipe on PE1 and PE2 so that VPN data services are forwarded based on the priorities configured by the carrier on the MPLS network. The P node also needs to schedule data based on priorities.
Interfaces 1 through 3 in this example represent GE 0/1/0, GE 0/1/8, and GE 0/1/16, respectively.
Configuration Roadmap
The configuration roadmap is as follows:
Configure OSPF on the backbone network to enable interworking between PEs.
Configure basic MPLS functions and MPLS LDP on the PEs, and establish the MPLS LSPs between the PEs.
Configure MP-IBGP to exchange VPN routing information between the PEs.
Configure a VPN instance on each PE connected to each directly connected CE on the backbone network, and bind the PE interface connected to the CEs to the corresponding VPN instances.
Configure EBGP between the CEs and PEs to exchange VPN routing information.
Configure the Pipe mode on VPN-A and VPN-B and apply different DiffServ domains to different VPN instances.
- Configure behavior aggregate classification on the P node.
Data Preparation
To configure the Pipe MPLS DiffServ mode, you need the following data:
MPLS LSR IDs on PEs and the P
RDs of VPN-A and VPN-B
VPN targets of VPN-A and VPN-B
Different DiffServ domains on PE1 and PE2
Procedure
- Configure an IGP on the MPLS backbone to allow the PEs and the Ps to reach each other.
# Configure PE1.
<HUAWEI> system-view [~HUAWEI] sysname PE1 [*HUAWEI] commit [~PE1] interface loopback 1 [*PE1-LoopBack1] ip address 1.1.1.9 32 [*PE1-LoopBack1] commit [~PE1-LoopBack1] quit [~PE1] interface gigabitethernet0/1/16 [~PE1-GigabitEthernet0/1/16] ip address 172.21.1.1 24 [*PE1-GigabitEthernet0/1/16] commit [~PE1-GigabitEthernet0/1/16] quit [~PE1] ospf [*PE1-ospf-1] area 0 [*PE1-ospf-1-area-0.0.0.0] network 172.21.1.0 0.0.0.255 [*PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0 [*PE1-ospf-1-area-0.0.0.0] commit [~PE1-ospf-1-area-0.0.0.0] quit [~PE1-ospf-1] quit
# Configure the P.
<HUAWEI> system-view [~HUAWEI] sysname P [*HUAWEI] commit [~P] interface loopback 1 [*P-LoopBack1] ip address 2.2.2.9 32 [*P-LoopBack1] commit [~P-LoopBack1] quit [~P] interface gigabitethernet 0/1/0 [~P-GigabitEthernet0/1/0] ip address 172.21.1.2 24 [*P-GigabitEthernet0/1/0] commit [~P-GigabitEthernet0/1/0] quit [~P] interface gigabitethernet 0/1/8 [~P-GigabitEthernet0/1/8] ip address 172.22.1.1 24 [*P-GigabitEthernet0/1/8] commit [~P-GigabitEthernet0/1/8] quit [~P] ospf [*P-ospf-1] area 0 [*P-ospf-1-area-0.0.0.0] network 172.21.1.0 0.0.0.255 [*P-ospf-1-area-0.0.0.0] network 172.22.1.0 0.0.0.255 [*P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0 [*P-ospf-1-area-0.0.0.0] commit [~P-ospf-1-area-0.0.0.0] quit [~P-ospf-1] quit
# Configure PE2.
<HUAWEI> system-view [~HUAWEI] sysname PE2 [*HUAWEI] commit [~PE2] interface loopback 1 [*PE2-LoopBack1] ip address 3.3.3.9 32 [*PE2-LoopBack1] commit [~PE2-LoopBack1] quit [~PE2] interface gigabitethernet 0/1/16 [~PE2-GigabitEthernet0/1/16] ip address 172.22.1.2 24 [*PE2-GigabitEthernet0/1/16] commit [~PE2-GigabitEthernet0/1/16] quit [~PE2] ospf [*PE2-ospf-1] area 0 [*PE2-ospf-1-area-0.0.0.0] network 172.22.1.0 0.0.0.255 [*PE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0 [*PE2-ospf-1-area-0.0.0.0] commit [~PE2-ospf-1-area-0.0.0.0] quit [~PE2-ospf-1] quit
After completing the configuration, verify that the OSPF neighbor relationships have been established between PE1, P and PE2. Run the display ospf peer command. The command output shows that the OSPF neighbor relationships are in Full state. Run the display ip routing-table command on the PEs. The command output shows that the PEs have learned the routes of the Loopback1 interface of each other.
The command output on PE1 is used as an example.
[~PE1] display ospf peer (M) Indicates MADJ interface OSPF Process 1 with Router ID 1.1.1.9 Neighbors Area 0.0.0.0 interface 172.21.1.1(GigabitEthernet0/1/16)'s neighbors Router ID: 2.2.2.9 Address: 172.21.1.2 State: Full Mode:Nbr is Master Priority: 1 DR: 172.21.1.1 BDR: 172.21.1.2 MTU: 0 Dead timer due in 38 sec Retrans timer interval: 5 Neighbor is up for 00h02m45s Neighbor Up Time : 2020-08-15 01:41:57 Authentication Sequence: [ 0 ] [~PE1] display ip routing-table Route Flags: R - relay, D - download to fib, T - to vpn-instance, B - black hole route ------------------------------------------------------------------------------ Routing Table: _public_ Destinations : 8 Routes : 8 Destination/Mask Proto Pre Cost Flags NextHop Interface 1.1.1.9/32 Direct 0 0 D 127.0.0.1 LoopBack1 2.2.2.9/32 OSPF 10 1 D 172.21.1.2 GigabitEthernet0/1/16 3.3.3.9/32 OSPF 10 2 D 172.21.1.2 GigabitEthernet0/1/16 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 172.21.1.0/24 Direct 0 0 D 172.21.1.1 GigabitEthernet0/1/16 172.21.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 172.22.1.0/24 OSPF 10 2 D 172.21.1.2 GigabitEthernet0/1/16
- Configure basic MPLS capabilities and MPLS LDP on the MPLS backbone network to set up LDP LSPs.
# Configure PE1.
[~PE1] mpls lsr-id 1.1.1.9 [*PE1] mpls [*PE1-mpls] commit [~PE1-mpls] quit [~PE1] mpls ldp [*PE1-mpls-ldp] commit [~PE1-mpls-ldp] quit [~PE1] interface gigabitethernet 0/1/16 [~PE1-GigabitEthernet0/1/16] mpls [*PE1-GigabitEthernet0/1/16] mpls ldp [*PE1-GigabitEthernet0/1/16] commit [~PE1-GigabitEthernet0/1/16] quit
# Configure the P.
[~P] mpls lsr-id 2.2.2.9 [*P] mpls [*P-mpls] commit [~P-mpls] quit [~P] mpls ldp [*P-mpls-ldp] commit [~P-mpls-ldp] quit [~P] interface gigabitethernet 0/1/0 [~P-GigabitEthernet0/1/0] mpls [*P-GigabitEthernet0/1/0] mpls ldp [*P-GigabitEthernet0/1/0] commit [~P-GigabitEthernet0/1/0] quit [~P] interface gigabitethernet 0/1/8 [~P-GigabitEthernet0/1/8] mpls [*P-GigabitEthernet0/1/8] mpls ldp [*P-GigabitEthernet0/1/8] commit [~P-GigabitEthernet0/1/8] quit
# Configure PE2.
[~PE2] mpls lsr-id 3.3.3.9 [*PE2] mpls [*PE2-mpls] commit [~PE2-mpls] quit [~PE2] mpls ldp [*PE2-mpls-ldp] commit [~PE2-mpls-ldp] quit [~PE2] interface gigabitethernet 0/1/16 [~PE2-GigabitEthernet0/1/16] mpls [*PE2-GigabitEthernet0/1/16] mpls ldp [*PE2-GigabitEthernet0/1/16] commit [~PE2-GigabitEthernet0/1/16] quit
After completing the configuration, verify that LDP sessions have been set up between PE1, P and PE2. Run the display mpls ldp session command on the routers. The command output shows that the session status is Operational. Run the display mpls ldp lsp command to view the LDP LSP status.
The command output on PE1 is used as an example.
[~PE1] display mpls ldp session LDP Session(s) in Public Network Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM) An asterisk (*) before a session means the session is being deleted. ------------------------------------------------------------------------- PeerID Status LAM SsnRole SsnAge KASent/Rcv ------------------------------------------------------------------------- 2.2.2.9:0 Operational DU Passive 0000:00:01 5/5 ------------------------------------------------------------------------- TOTAL: 1 Session(s) Found. [~PE1] display mpls ldp lsp LDP LSP Information ------------------------------------------------------------------------------- Flag after Out IF: (I) - RLFA Iterated LSP, (I*) - Normal and RLFA Iterated LSP ------------------------------------------------------------------------------- DestAddress/Mask In/OutLabel UpstreamPeer NextHop OutInterface ------------------------------------------------------------------------------- 1.1.1.9/32 3/NULL 2.2.2.9 127.0.0.1 Loopback1 *1.1.1.9/32 Liberal/48061 DS/2.2.2.9 2.2.2.9/32 NULL/3 - 172.21.1.2 GigabitEthernet0/1/16 2.2.2.9/32 48061/3 2.2.2.9 172.21.1.2 GigabitEthernet0/1/16 3.3.3.9/32 NULL/48062 - 172.21.1.2 GigabitEthernet0/1/16 3.3.3.9/32 48062/48062 2.2.2.9 172.21.1.2 GigabitEthernet0/1/16 ------------------------------------------------------------------------------- TOTAL: 5 Normal LSP(s) Found. TOTAL: 1 Liberal LSP(s) Found. TOTAL: 0 FRR LSP(s) Found. An asterisk (*) before an LSP means the LSP is not established An asterisk (*) before a Label means the USCB or DSCB is stale An asterisk (*) before an UpstreamPeer means the session is stale An asterisk (*) before a DS means the session is stale An asterisk (*) before a NextHop means the LSP is FRR LSP
- Establish an MP-IBGP peer relationship between the PEs.
# Configure PE1.
[~PE1] bgp 100 [*PE1-bgp] peer 3.3.3.9 as-number 100 [*PE1-bgp] peer 3.3.3.9 connect-interface loopback 1 [*PE1-bgp] ipv4-family vpnv4 [*PE1-bgp-af-vpnv4] peer 3.3.3.9 enable Warning: This operation will reset the peer session. Continue? [Y/N]:y [*PE1-bgp-af-vpnv4] commit [~PE1-bgp-af-vpnv4] quit [~PE1-bgp] quit
# Configure PE2.
[~PE2] bgp 100 [*PE2-bgp] peer 1.1.1.9 as-number 100 [*PE2-bgp] peer 1.1.1.9 connect-interface loopback 1 [*PE2-bgp] ipv4-family vpnv4 [*PE2-bgp-af-vpnv4] peer 1.1.1.9 enable Warning: This operation will reset the peer session. Continue? [Y/N]:y [*PE2-bgp-af-vpnv4] commit [~PE2-bgp-af-vpnv4] quit [~PE2-bgp] quit
After completing the configuration, run the display bgp peer command or the display bgp vpnv4 all peer command. The command output shows that the BGP peer relationship has been set up between the PEs, and the peer status is Established.
[~PE1] display bgp vpnv4 all peer BGP local router ID : 1.1.1.9 Local AS number : 100 Total number of peers : 1 Peers in established state : 1 Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv 3.3.3.9 4 100 12 18 0 00:09:38 Established 0 - Configure VPN instances on PEs and bind the instances to the interfaces connected to CEs.
# Configure PE1.
[~PE1] ip vpn-instance vpna [*PE1-vpn-instance-vpna] route-distinguisher 100:1 [*PE1-vpn-instance-vpna-af-ipv4] vpn-target 111:1 both [*PE1-vpn-instance-vpna-af-ipv4] commit [~PE1-vpn-instance-vpna-af-ipv4] quit [~PE1-vpn-instance-vpna] quit [~PE1] ip vpn-instance vpnb [*PE1-vpn-instance-vpnb] route-distinguisher 100:2 [*PE1-vpn-instance-vpnb-af-ipv4] vpn-target 222:2 both [*PE1-vpn-instance-vpnb-af-ipv4] commit [~PE1-vpn-instance-vpnb-af-ipv4] quit [~PE1-vpn-instance-vpnb] quit [~PE1] interface gigabitethernet 0/1/0 [~PE1-GigabitEthernet0/1/0] ip binding vpn-instance vpna [*PE1-GigabitEthernet0/1/0] ip address 10.1.1.2 24 [*PE1-GigabitEthernet0/1/0] commit [~PE1-GigabitEthernet0/1/0] quit [~PE1] interface gigabitethernet 0/1/8 [~PE1-GigabitEthernet0/1/8] ip binding vpn-instance vpnb [*PE1-GigabitEthernet0/1/8] ip address 10.2.1.2 24 [*PE1-GigabitEthernet0/1/8] commit [~PE1-GigabitEthernet0/1/8] quit
# Configure PE2.
[~PE2] ip vpn-instance vpna [*PE2-vpn-instance-vpna] route-distinguisher 200:1 [*PE2-vpn-instance-vpna-af-ipv4] vpn-target 111:1 both [*PE2-vpn-instance-vpna-af-ipv4] commit [~PE2-vpn-instance-vpna-af-ipv4] quit [~PE2-vpn-instance-vpna] quit [~PE2] ip vpn-instance vpnb [*PE2-vpn-instance-vpnb] route-distinguisher 200:2 [*PE2-vpn-instance-vpnb-af-ipv4] vpn-target 222:2 both [*PE2-vpn-instance-vpnb-af-ipv4] commit [~PE2-vpn-instance-vpnb-af-ipv4] quit [~PE2-vpn-instance-vpnb] quit [~PE2] interface gigabitethernet 0/1/0 [~PE2-GigabitEthernet0/1/0] ip binding vpn-instance vpna [*PE2-GigabitEthernet0/1/0] ip address 10.3.1.2 24 [*PE2-GigabitEthernet0/1/0] commit [~PE2-GigabitEthernet0/1/0] quit [~PE2] interface gigabitethernet 0/1/8 [~PE2-GigabitEthernet0/1/8] ip binding vpn-instance vpnb [*PE2-GigabitEthernet0/1/8] ip address 10.4.1.2 24 [*PE2-GigabitEthernet0/1/8] commit [~PE2-GigabitEthernet0/1/8] quit
# Configure an IP address for the CE interface according to Figure 1. Configuration details are not provided here.
After completing the configuration, run the display ip vpn-instance verbose command on the PEs to check the configuration of VPN instances. Each PE can successfully ping its directly connected CEs.
If multiple interfaces on a PE are bound to the same VPN, you must specify the source IP address when running the ping -vpn-instance command to ping the CE connected to the peer PE. That is, you must specify the -a source-ip-address parameter in the ping -vpn-instance vpn-instance-name -a source-ip-address dest-ip-address command. Otherwise, the ping operation may fail.
The command output on PE1 connected to CE1 is used as an example.
[~PE1] display ip vpn-instance verbose Total VPN-Instances configured : 2 Total IPv4 VPN-Instances configured : 2 Total IPv6 VPN-Instances configured : 0 VPN-Instance Name and ID : vpna, 4 Interfaces : GigabitEthernet0/1/0 Address family ipv4 Create date : 2020/09/21 11:30:35 Up time : 0 days, 00 hours, 05 minutes and 19 seconds Vrf Status : UP Route Distinguisher : 100:1 Export VPN Targets : 111:1 Import VPN Targets : 111:1 Label Policy : label per route The diffserv-mode Information is : uniform The ttl-mode Information is : pipe Log Interval : 5 Interfaces : GigabitEthernet0/1/0 VPN-Instance Name and ID : vpnb, 5 Interfaces : GigabitEthernet0/1/8 Address family ipv4 Create date : 2020/09/21 11:31:18 Up time : 0 days, 00 hours, 04 minutes and 36 seconds Vrf Status : UP Route Distinguisher : 100:2 Export VPN Targets : 222:2 Import VPN Targets : 222:2 Label Policy : label per route The diffserv-mode Information is : uniform The ttl-mode Information is : pipe Log Interval : 5 Interfaces : GigabitEthernet0/1/8 [~PE1] ping -vpn-instance vpna 10.1.1.1 PING 10.1.1.1: 56 data bytes, press CTRL_C to break Reply from 10.1.1.1: bytes=56 Sequence=1 ttl=255 time=56 ms Reply from 10.1.1.1: bytes=56 Sequence=2 ttl=255 time=4 ms Reply from 10.1.1.1: bytes=56 Sequence=3 ttl=255 time=4 ms Reply from 10.1.1.1: bytes=56 Sequence=4 ttl=255 time=52 ms Reply from 10.1.1.1: bytes=56 Sequence=5 ttl=255 time=3 ms --- 10.1.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/23/56 ms
- Establish the EBGP peer relationships between the PEs and CEs to import VPN routes.
# Configure CE1.
[~CE1] bgp 65410 [*CE1-bgp] peer 10.1.1.2 as-number 100 [*CE1-bgp] import-route direct
The configurations of CE2, CE3, and CE4 are similar to the configuration of CE1.
# Configure PE1.
[~PE1] bgp 100 [*PE1-bgp] ipv4-family vpn-instance vpna [*PE1-bgp-vpna] peer 10.1.1.1 as-number 65410 [*PE1-bgp-vpna] import-route direct [*PE1-bgp-vpna] commit [~PE1-bgp-vpna] quit [~PE1-bgp] ipv4-family vpn-instance vpnb [*PE1-bgp-vpnb] peer 10.2.1.1 as-number 65420 [*PE1-bgp-vpnb] import-route direct [*PE1-bgp-vpnb] commit [~PE1-bgp-vpnb] quit [~PE1-bgp] quit
The configuration of PE2 is similar to that of PE1. Configuration details are not provided here.
After completing the configuration, run the display bgp vpnv4 vpn-instance peer command on each PE. The command output shows that the BGP peer relationship has been set up between the PE and CEs, and the peer status is Established.
Information about the peer relationship between PE1 and CE1 is used as an example.
[~PE1] display bgp vpnv4 vpn-instance vpna peer BGP local router ID : 1.1.1.9 Local AS number : 100 VPN-Instance vpna, Router ID 1.1.1.9: Total number of peers : 1 Peers in established state : 1 Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv 10.1.1.1 4 65410 11 9 0 00:06:37 Established 1 - Verify the configuration.
Run the display ip routing-table vpn-instance command on the PE to view the routes to peer CEs.
The command output on PE1 is used as an example.
[~PE1] display ip routing-table vpn-instance vpna
Route Flags: R - relay, D - download to fib ------------------------------------------------------------------------------ Routing Table: vpna Destinations : 3 Routes : 3 Destination/Mask Proto Pre Cost Flags NextHop Interface 10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet0/1/0 10.1.1.2/32 Direct 0 0 D 127.0.0.1 GigabitEthernet0/1/0 10.3.1.0/24 IBGP 255 0 RD 3.3.3.9 GigabitEthernet0/1/16 [~PE1] display ip routing-table vpn-instance vpnb Route Flags: R - relay, D - download to fib ------------------------------------------------------------------------------ Routing Table: vpnb Destinations : 3 Routes : 3 Destination/Mask Proto Pre Cost Flags NextHop Interface 10.2.1.0/24 Direct 0 0 D 10.2.1.2 GigabitEthernet0/1/8 10.2.1.2/32 Direct 0 0 D 127.0.0.1 GigabitEthernet0/1/8 10.4.1.0/24 IBGP 255 0 RD 3.3.3.9 GigabitEthernet0/1/16The CEs in the same VPN can successfully ping each other whereas two CEs in different VPNs cannot ping each other.
For example, CE1 can successfully ping CE3 (10.3.1.1/24) but cannot ping CE4 (10.4.1.1/24).
[~CE1] ping 10.3.1.1 PING 10.3.1.1: 56 data bytes, press CTRL_C to break Reply from 10.3.1.1: bytes=56 Sequence=1 ttl=253 time=72 ms Reply from 10.3.1.1: bytes=56 Sequence=2 ttl=253 time=34 ms Reply from 10.3.1.1: bytes=56 Sequence=3 ttl=253 time=50 ms Reply from 10.3.1.1: bytes=56 Sequence=4 ttl=253 time=50 ms Reply from 10.3.1.1: bytes=56 Sequence=5 ttl=253 time=34 ms --- 10.3.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 34/48/72 ms [~CE1] ping 10.4.1.1 PING 10.4.1.1: 56 data bytes, press CTRL_C to break Request time out Request time out Request time out Request time out Request time out --- 10.4.1.1 ping statistics --- 5 packet(s) transmitted 0 packet(s) received 100.00% packet loss
- Configure DiffServ on PE1 and PE2 and apply DiffServ domains to different VPN instances.
# Configure PE1.
[~PE1] ip vpn-instance vpna [*PE1-vpn-instance-vpna] ipv4-family [*PE1-vpn-instance-vpna-af-ipv4] diffserv-mode pipe af1 green [*PE1-vpn-instance-vpna-af-ipv4] commit [~PE1-vpn-instance-vpna-af-ipv4] quit [~PE1-vpn-instance-vpna] quit [~PE1] ip vpn-instance vpnb [*PE1-vpn-instance-vpnb] ipv4-family [*PE1-vpn-instance-vpnb-af-ipv4] diffserv-mode pipe be yellow [*PE1-vpn-instance-vpnb-af-ipv4] commit [~PE1-vpn-instance-vpnb-af-ipv4] quit [~PE1-vpn-instance-vpnb] quit
# Configure PE2.
[~PE2] ip vpn-instance vpna [*PE2-vpn-instance-vpna] ipv4-family [*PE2-vpn-instance-vpna-af-ipv4] diffserv-mode pipe af1 green [*PE2-vpn-instance-vpna-af-ipv4] commit [~PE2-vpn-instance-vpna-af-ipv4] quit [~PE2-vpn-instance-vpna] quit [~PE2] ip vpn-instance vpnb [*PE2-vpn-instance-vpnb] ipv4-family [*PE2-vpn-instance-vpnb-af-ipv4] diffserv-mode pipe be yellow [*PE2-vpn-instance-vpnb-af-ipv4] commit [~PE2-vpn-instance-vpnb-af-ipv4] quit [~PE2-vpn-instance-vpnb] quit
- Configure behavior aggregate classification on the P node.
# Configure P.
[~P] interface gigabitethernet 0/1/0 [~P-GigabitEthernet0/1/0] trust upstream default [*P-GigabitEthernet0/1/0] quit [*P] interface gigabitethernet 0/1/8 [*P-GigabitEthernet0/1/8] trust upstream default [*P-GigabitEthernet0/1/8] quit [*P] commit
- Verify the configuration.
You can view the DiffServ mode of the VPN instance after running the display ip vpn-instance verbose vpna command on the PE.
The command output on PE1 is used as an example.
[~PE1] display ip vpn-instance verbose vpna VPN-Instance Name and ID : vpna, 23 Address family ipv4 Create date : 2020/09/21 11:08:12 Up time : 0 days, 00 hours, 06 minutes and 32 seconds Vrf Status : UP Label Policy : label per route The diffserv-mode Information is : pipe af1 green The ttl-mode Information is : pipe Log Interval : 5
Configuration Files
PE1 configuration file
# sysname PE1 # ip vpn-instance vpna ipv4-family route-distinguisher 100:1 apply-label per-instance vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity diffserv-mode pipe af1 green # ip vpn-instance vpnb ipv4-family route-distinguisher 100:2 apply-label per-instance vpn-target 222:2 export-extcommunity vpn-target 222:2 import-extcommunity diffserv-mode pipe be yellow # mpls lsr-id 1.1.1.9 # mpls # mpls ldp # interface GigabitEthernet0/1/0 undo shutdown ip binding vpn-instance vpna ip address 10.1.1.2 255.255.255.0 # interface GigabitEthernet0/1/8 undo shutdown ip binding vpn-instance vpnb ip address 10.2.1.2 255.255.255.0 # interface GigabitEthernet0/1/16 undo shutdown ip address 172.21.1.1 255.255.255.0 mpls mpls ldp # interface LoopBack1 ip address 1.1.1.9 255.255.255.255 # bgp 100 peer 3.3.3.9 as-number 100 peer 3.3.3.9 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 3.3.3.9 enable # ipv4-family vpnv4 policy vpn-target peer 3.3.3.9 enable # ipv4-family vpn-instance vpna import-route direct peer 10.1.1.1 as-number 65410 # ipv4-family vpn-instance vpnb import-route direct peer 10.2.1.1 as-number 65420 # ospf 1 area 0.0.0.0 network 1.1.1.9 0.0.0.0 network 172.21.1.0 0.0.0.255 # return
P configuration file
# sysname P # mpls lsr-id 2.2.2.9 # mpls # mpls ldp # interface GigabitEthernet0/1/0 undo shutdown ip address 172.21.1.2 255.255.255.0 mpls mpls ldp trust upstream default # interface GigabitEthernet0/1/8 undo shutdown ip address 172.22.1.1 255.255.255.0 mpls mpls ldp trust upstream default # interface LoopBack1 ip address 2.2.2.9 255.255.255.255 # ospf 1 area 0.0.0.0 network 2.2.2.9 0.0.0.0 network 172.21.1.0 0.0.0.255 network 172.22.1.0 0.0.0.255 # return
PE2 configuration file
# sysname PE2 # ip vpn-instance vpna ipv4-family route-distinguisher 200:1 apply-label per-instance vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity diffserv-mode pipe af1 green # ip vpn-instance vpnb ipv4-family route-distinguisher 200:2 apply-label per-instance vpn-target 222:2 export-extcommunity vpn-target 222:2 import-extcommunity diffserv-mode pipe be yellow # mpls lsr-id 3.3.3.9 # mpls # mpls ldp # interface GigabitEthernet0/1/0 undo shutdown ip binding vpn-instance vpna ip address 10.3.1.2 255.255.255.0 # interface GigabitEthernet0/1/8 undo shutdown ip binding vpn-instance vpnb ip address 10.4.1.2 255.255.255.0 # interface GigabitEthernet0/1/16 undo shutdown ip address 172.22.1.2 255.255.255.0 mpls mpls ldp # interface LoopBack1 ip address 3.3.3.9 255.255.255.255 # bgp 100 peer 1.1.1.9 as-number 100 peer 1.1.1.9 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 1.1.1.9 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.9 enable # ipv4-family vpn-instance vpna peer 10.3.1.1 as-number 65430 import-route direct # ipv4-family vpn-instance vpnb peer 10.4.1.1 as-number 65440 import-route direct # ospf 1 area 0.0.0.0 network 3.3.3.9 0.0.0.0 network 172.22.1.0 0.0.0.255 # return
CE1 configuration file
# sysname CE1 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.1.1.1 255.255.255.0 # bgp 65410 peer 10.1.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.1.1.2 enable # returnCE2 configuration file
# sysname CE2 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.2.1.1 255.255.255.0 # bgp 65420 peer 10.2.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.2.1.2 enable # returnCE3 configuration file
# sysname CE3 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.3.1.1 255.255.255.0 # bgp 65430 peer 10.3.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.3.1.2 enable # returnCE4 configuration file
# sysname CE4 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.4.1.1 255.255.255.0 # bgp 65440 peer 10.4.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 10.4.1.2 enable # return