Figure 17: E-Line Services Network with SS-PWs
Prerequisites for Configuring L2VPN Single Segment Pseudowires
MPLS LDP, IGP, BGP, L2VPN, and interfaces must be configured on the two end points of the PW:
• Configuring MPLS Label Distribution Protocol.
• Configuring Interior Gateway Protocol (IGP).
• Configure Border Gateway Protocol (BGP).
• Configuring an Interface or Connection for L2VPN.
Restrictions for Configuring L2VPN Single Segment Pseudowires
• The routed pseudowire can only be enabled on Virtual Private Wire Service (VPWS) cross connects.
• A cross-connect cannot have both ends configured as “neighbor routed” pseudowire.
• SS-PW is not supported as the other member of the cross-connect, that is, at a T-PE, one end of the
cross-connect can be the termination of the SS-PW and the other end can either be an attachment circuit
(AC) or a PW-HE.
• Source AII and AC-ID (attachment circuit identifier) are unique per router.
• L2TP and MPLS static are not supported.
Configuring L2VPN Single Segment Pseudowire
To configure single segment pseudowire in the network, do the following:
1. (Optional) Configuring the related L2VPN Global Parameters. See Configuring L2VPN Global Parameters
This procedure is used to overwrite the default BGP Route Distinguisher (RD) auto-generated value and
also the Autonomous System Number (ASN) and Route Identifier (RID) of BGP.
2. Configuring L2VPN VPWS SS-PW
3. Configuring L2VPN MS-PW Address Family Under BGP
The address family is configured under BGP to exchange the dynamic pseudowire routes.
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
93
Implementing Point to Point Layer 2 Services
Prerequisites for Configuring L2VPN Single Segment Pseudowires