PseudoWire

In an LDP-signaled L2VPN, the MPLS Topology Server checks the VC IDs and peer ForwarderEndpoint IP addresses that are associated with the discovered ForwarderEndpoints, and creates a PseudoWire instance for each complementary match. For example, due to the following complementary match, the MPLS Topology Server will create a PseudoWire instance between ForwarderEndpoint1 and ForwarderEndpoint2:

• ForwarderEndpoint1: VC ID = 122, peer IP = 192.168.5.1, local IP = 192.168.19.1

• ForwarderEndpoint2: VC ID = 122, peer IP = 192.168.19.1, local IP = 192.168.5.1

  In a BGP-signaled L2VPN, the MPLS Topology Server checks the incoming VC ID/ outgoing VC ID pairs that are associated with the discovered ForwarderEndpoints, and creates a PseudoWire instance for each complementary match. For example, due to the following complementary match, the MPLS Topology Server will create a PseudoWire instance between ForwarderEndpointA and ForwarderEndpointB:

• ForwarderEndpointA: incoming VC ID/ outgoing VC ID = 262401/262406

• ForwarderEndpointB: incoming VC ID/ outgoing VC ID = 262406/262401

  A PseudoWire is TerminatedBy two ForwarderEndpoints, where one ForwarderEndpoint is HostedBy one PE device, and the second ForwarderEndpoint is HostedBy another PE device. The PseudoWire is associated with a pair of LSPs, and provides a bidirectional data path between the two PE devices. The LSPs can be TE LSPs or LDP LSPs.

  Because the MPLS Topology Server can discover LSPs that traverse a mixture of multi-vendor devices as long as the LSPs originate and terminate on same-vendor devices, the same can be said of PseudoWires. For example, the MPLS Topology Server can discover a PseudoWire that traverses any mixture of Cisco and Juniper M/T devices, as long as the PseudoWire originates and terminates on same-vendor PE devices (a pair of Cisco PEs, for example).

  The MPLS Topology Server relates a ForwarderEndpoint with a PseudoWire and other discovered objects through the following computed relationships:

• ForwarderEndpoint relationship Terminates

  Relates a ForwarderEndpoint to the PseudoWire that is terminated by the ForwarderEndpoint.

• ForwarderEndpoint relationship LayeredOver

  Points from a ForwarderEndpoint to the pair of LSPs that are underlying the PseudoWire.

  Also points to the interface, on the host PE device, that is associated with the ForwarderEndpoint.

• ForwarderEndpoint relationship Underlying

  For a ForwarderEndpoint that is associated with an Ethernet VLAN, points from the ForwarderEndpoint to the VLAN.

• ForwarderEndpoint relationship Peer

  Points from a ForwarderEndpoint to the ForwarderEndpoint that terminates the other end of the PseudoWire.

• ForwarderEndpoint relationship PartOf

  Points to the Forwarder to which this ForwarderEndpoint belongs.

  Points to the VPN to which this ForwarderEndpoint belongs.

• ForwarderEndpoint relationship HostedBy

  Relates a ForwarderEndpoint to the PE device that is hosting the ForwarderEndpoint.

• BGP-signaled L2VPN only: ForwarderEndpoint relationship RT

  Relates a ForwarderEndpoint to the RouteTarget of the L2VPN to which the ForwarderEndpoint belongs.

  Some computed relationships for PseudoWires are:

• PseudoWire relationship LayeredOver

  Points from a PseudoWire to the pair of LSPs that are underlying the PseudoWire.

  Points to the interface, on the host PE device, that is associated with the PseudoWire.

  LDP-signaled L2VPN only: Points from a PseudoWire to the LdpAdjacency that is providing the signaling for the L2VPN to which the PseudoWire belongs.

• PseudoWire relationship VLANs

  For a PseudoWire that is associated with an Ethernet VLAN, points from the PseudoWire to the VLAN.