Cisco CRS Configuration Manual page 142

Configuring Pseudowire Headend: Example
110.110.110.110 Gig0/3/0/0
A.B.C.D/N 110.110.110.110
CE2
interface Gig0/3/0/1
ipv4 address 10.1.2.1/24
router static
address-family ipv4 unicast
110.110.110.110 Gig0/3/0/1
A.B.C.D/N 110.110.110.110
A-PE Configuration
At A-PE, one xconnect is configured for each CE connection. Here, CE connections are L2 links, which are
in xconnects. Each xconnect has a pseudowire connected to S-PE, though connected to different neighbor
addresses, depending on where the pseudowire is to be pin downed: [L1, L4] or [L2, L3].
interface Gig0/3/0/0
l2transport
interface Gig0/3/0/1
l2transport
l2vpn
xconnect group pwhe
p2p pwhe_spe_1
interface Gig0/3/0/0
neighbor 111.111.111.111 pw-id 1
p2p pwhe_spe_2
interface Gig0/3/0/1
neighbor 112.112.112.112 pw-id 2
P Router Configuration
Static routes are required on P routers for Rx pindown on S-PE to force PWs configured with a specific address
to be transported over certain links.
P1
router static
address-family ipv4 unicast
111.111.111.111 Gig0/1/0/0
112.112.112.112 Gig0/2/0/0
P2
router static
address-family ipv4 unicast
111.111.111.111 Gig0/2/0/1
112.112.112.112 Gig0/1/0/1
S-PE Configuration
At S-PE, two PWHE interfaces (one for each PW) is configured, and each uses a different interface list for
Tx pin-down. (This must match the static configuration at P routers for Rx pin-down). Each PWHE has the
PW connected to A-PE (The pw-id must match the pw-id at A-PE.)
generic-interface-list il1
interface gig0/1/0/0
interface gig0/2/0/0
Cisco IOS XR Virtual Private Network Configuration Guide for the Cisco CRS Router, Release 6.1.x
128
Implementing Multipoint Layer 2 Services