Pseudowire switching is supported with a BGP VPWS service allowing the cross connection between a BGP VPWS signaled spoke-SDP and a static GRE tunnel, the latter being a spoke SDP configured with static MPLS labels using a GRE SDP. No other spoke SDP types are supported. Support is not included for BGP multihoming using an active and a standby pseudowire to a pair of remote PEs.
Operational state changes to the GRE tunnel are reflected in the state of the Epipe and propagated accordingly in the BGP VPWS spoke SDP status signaling, specifically using the BGP update D and CSV bits.
The following configuration is required:
The Epipe service must be created using the vc-switching parameter.
The GRE tunnel spoke SDP must be configured using a GRE SDP with signaling off and have the ingress and egress vc-labels statically configured.
Example: BGP VPWS service configured to allow pseudowire switching
configure
service
sdp 1 create
signaling off
far-end 192.168.1.1
keep-alive
shutdown
exit
no shutdown
exit
pw-template 1 create
exit
epipe 1 customer 1 vc-switching create
description "BGP VPWS service"
bgp
route-distinguisher 65536:1
route-target export target:65536:1 import target:65536:1
pw-template-binding 1
exit
exit
bgp-vpws
ve-name "PE1"
ve-id 1
exit
remote-ve-name "PE2"
ve-id 2
exit
no shutdown
exit
spoke-sdp 1:1 create
ingress
vc-label 1111
exit
egress
vc-label 1122
exit
no shutdown
exit
no shutdown
exit