Figure 53: Sdps - Uni-Directional Tunnels - Alcatel-Lucent 7750 SR Manual

Configuring SDP Bindings
Figure 53
identifying the service and customer IDs, and the uni-directional SDPs required to communicate to
the far-end routers.
A spoke SDP is treated like the equivalent of a traditional bridge "port" where flooded traffic
received on the spoke SDP is replicated on all other "ports" (other spoke and mesh SDPs or SAPs)
and not transmitted on the port it was received.
ALA-1
EPIPE 2 FOR
CUSTOMER 6
Use the following CLI syntax to create a spoke SDP binding with an Epipe service:
CLI Syntax: config>service# epipe service-id [customer customer-id]
The following example displays the command usage to bind an Epipe service between ALA-1 and
ALA-2. This example assumes the SAPs have already been configured (see
SAPs on page
7750 SR OS Services Guide
displays an example of a distributed Epipe service configuration between two routers,
demux
SDP 2
Figure 53: SDPs — Uni-Directional Tunnels
spoke-sdp sdp-id:vc-id [vc-type {ether | vlan}]
vlan-vc-tag 0..4094
egress
filter {ip ip-filter-id}
vc-label egress-vc-label
ingress
filter {ip ip-filter-id}
vc-label ingress-vc-label
no shutdown
257).
SPOKE-SDP 3
SPOKE-SDP 2
Virtual Leased Line Services
ALA-2
SDP 3
EPIPE 2 FOR
CUSTOMER 6
demux
Distributed Epipe
Page 261