Local Cross-Connects for VPWS Overview
You configure a local cross-connect between two local customer sites by first configuring
the two local sites and then configuring the correct local and remote site IDs on the two
local interfaces that you are cross-connecting. Figure 133 on page 655 illustrates
cross-connects by showing a portion of a sample VPWS topology.
Figure 133: VPWS Cross-Connects
The following example shows the creation of a cross-connect between sites Westford
and Boston. On one customer-facing interface, Westford is considered local and Boston
is remote; on the other customer-facing interface, Boston is considered local and Westford
is remote. From the perspective of the PE router, both sites are local.
Multihoming is not applicable for VPWS local cross-connects because the local and
remote CE devices are connected to the same PE.
Configuring a Local Cross-Connect for VPWS
To configure a local cross-connect between two local sites:
1. Configure the two local sites.
host1(config)#l2vpn exampleco encapsulation-type ethernet
host1(config)#l2vpn exampleco site-name westford site-id 1
host1(config)#l2vpn exampleco site-name boston site-id 2
host1(config)#l2vpn exampleco site-range 10
host1(config)#l2vpn exampleco rd 100:11
host1(config)#l2vpn exampleco route-target both 100:1
2. Configure the correct local and remote site IDs on the two local interfaces that are
being cross-connected.
host1(config)#interface fastEthernet 4/0
host1(config-if)#l2vpn exampleco local-site-id 1 remote-site-id 2
host1(config-if)#exit
host1(config)#interface fastEthernet 4/1
host1(config-if)#l2vpn exampleco local-site-id 2 remote-site-id 1
host1(config-if)#exit
655Copyright © 2010, Juniper Networks, Inc.
Chapter 15: Configuring VPWS
To Next Page
Loading...
Need help?
General
