Riverstone Networks RS Switch Router User Guide Release 8.0 17-67
MPLS Configuration Configuring L2 Tunnels
-If you are using the VLAN ID as the FEC, specify the vlan option with the ldp add l2-fec
command.
-If you are using the incoming port as the FEC, specify the customer-id option with the ldp
add l2-fec command.
-If you are using a combination of VLAN ID and incoming port as the FEC, specify both the
vlan and customer-id options with the ldp add l2-fec command.
3. Configure the LDP-signaling VLAN and interface. The ports at both ends of a link between two
LSRs must belong to the same VLAN, i.e., the VLAN ID must be the same on both routers.
Note Ports in the LDP-signaling VLAN must be trunk ports. If “untagged” packets are
to be transported on the LSP, the tunnel port must be configured as a trunk port
that does not send 802.1q-tagged packets (use the untagged option with the
vlan make trunk-port command).
4. Configure the tunnel LSP. If you are using RSVP for signaling in the tunnel LSP, use mpls
commands, as described in Section17.5, "Configuring L3 Label Switched Paths." If you configure
more than one tunnel LSP to the same destination, you can specify the preferred LSP to be used with
the transport-lsp option of the ldp set l2-fec command. You can also specify if an alternate
LSP can be used. Enable and start MPLS and the signaling protocol (either LDP or RSVP) for the
tunnel LSP.
Note The transport-lsp option of the ldp set l2-fec command allows you to
assign a specific LSP to specific customer traffic. This provides a way to offer
different LSP services to different customers.
5. Configure the IGP routing protocol, either OSPF or IS-IS.

Transit LSR Configuration for L2 Dynamic Labels

On the transit LSRs, configure the following:
1. Configure the LDP- or RSVP-signaling VLAN and interface.
2. Enable and start MPLS and the signaling protocol (either LDP or RSVP) for the tunnel LSP.
3. Configure the IGP routing protocol, either OSPF or IS-IS.