R3102-R3103-HP 6600/HSR6600 Routers MPLS Configuration Guide
313
[PE1-GigabitEthernet2/1/1] ip address 10.1.1.2 24
[PE1-GigabitEthernet2/1/1] quit
[PE1] interface gigabitethernet 2/1/2
[PE1-GigabitEthernet2/1/2] ip binding vpn-instance vpn2
[PE1-GigabitEthernet2/1/2] ip address 10.2.1.2 24
[PE1-GigabitEthernet2/1/2] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 200:1
[PE2-vpn-instance-vpn1] vpn-target 111:1
[PE2-vpn-instance-vpn1] quit
[PE2] ip vpn-instance vpn2
[PE2-vpn-instance-vpn2] route-distinguisher 200:2
[PE2-vpn-instance-vpn2] vpn-target 222:2
[PE2-vpn-instance-vpn2] quit
[PE2] interface gigabitethernet 2/1/1
[PE2-GigabitEthernet2/1/1] ip binding vpn-instance vpn1
[PE2-GigabitEthernet2/1/1] ip address 10.3.1.2 24
[PE2-GigabitEthernet2/1/1] quit
[PE2] interface gigabitethernet 2/1/2
[PE2-GigabitEthernet2/1/2] ip binding vpn-instance vpn2
[PE2-GigabitEthernet2/1/2] ip address 10.4.1.2 24
[PE2-GigabitEthernet2/1/2] quit
# Configure IP addresses for the CEs according to Figure 139. (Details not shown.)
After completing the configurations, execute the display ip vpn-instance command on the PEs to
view the configuration of the VPN instances. Use the ping command to test connectivity between
the PEs and their attached CEs. The PEs can ping their attached CEs. Take PE 1 and CE 1 as
examples:
[PE1] display ip vpn-instance
Total VPN-Instances configured : 2
VPN-Instance Name RD Create time
vpn1 100:1 2009/01/22 13:02:21
vpn2 100:2 2009/01/22 13:02:40
[PE1] ping -vpn-instance vpn1 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
4. Establish IBGP peer relationships between PEs and CEs to redistribute VPN routes, and configure
routing policies to change the next hop of the routes: