Extranet Configuration Example - 3Com 8800 Configuration Manual

3Com Switch 8800 Configuration Guide

37.4.3 Extranet Configuration Example

I. Network requirements
Company A and Company B are located at City A and City B respectively. Their
headquarters is located at City C. They respectively own VPN1 and VPN2.
In this case, VPN function is provided by MPLS. There are some shared resources at
the City C for the two VPNs. All subscribers in both VPNs can access the shared
resources, but VPN subscribers in City A and City B cannot access each other.
The two companies cannot use identical IP addresses, for they share the same
VPN-instance at PE-C.
Note:
In the case the configuration is focused on controlling access authority of VPN
subscribers at different cities by configuring different VPN-target attributes at different
PEs.
II. Network diagram
VLAN301 VLAN301 VLAN301
172.15.0.1/16 172.15.0.1/16 172.15.0.1/16
City A City A City A
AS65011 AS65011 AS65011
PC PC PC
VPN 1 VPN 1 VPN 1
Figure 37-10 Network diagram for Extranet
AS100 AS100 AS100
PE-A PE-A PE-A
10.1.1.1 10.1.1.1 10.1.1.1
VLAN301 VLAN301 VLAN301
172.16.0.1/16 172.16.0.1/16 172.16.0.1/16
VLAN201 VLAN201 VLAN201
172.15.1.1/16 172.15.1.1/16 172.15.1.1/16
City C City C City C
CE-A CE-A CE-A
AS65012 AS65012 AS65012
10.11.1.0/24 10.11.1.0/24 10.11.1.0/24
PC PC PC PC PC PC
Chapter 37 BGP/MPLS VPN Configuration
SP network SP network
PE-C PE-C PE-C
20.1.1.1 20.1.1.1 20.1.1.1
172.17.0.1/16 172.17.0.1/16 172.17.0.1/16
VLAN201 VLAN201 VLAN201
172.16.1.1/16 172.16.1.1/16 172.16.1.1/16
CE-C CE-C CE-C
AS65013 AS65013 AS65013
PC PC PC PC PC PC
37-40
PE-B PE-B PE-B
30.1.1.1 30.1.1.1 30.1.1.1
VLAN301 VLAN301 VLAN301
VLAN201 VLAN201 VLAN201
172.17.1.1/16 172.17.1.1/16 172.17.1.1/16
City B City B City B CE-B CE-B CE-B
10.12.1.0/24 10.12.1.0/24 10.12.1.0/24
PC PC PC PC PC PC
VPN 2 VPN 2 VPN 2