Mpls-Relay - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - COMMAND REFERENCE A TO M 2010-10-19 Command Reference Manual

JunosE 11.3.x Command Reference Guide A to M

mpls-relay

Syntax
Release Information
Description
Options
1388
mpls-relay remoteIpAddress [ vc-id ] vcidValue [ group-id groupIdValue ]
[ control-word | no-control-word ] [ sequencing | no-sequencing ]
[ relay-format { ethernet | frame-relay | ppp | vlan | ethernet-raw-mode } ]
no mpls-relay
Command introduced before JunosE Release 7.1.0.
control-word, no-control-word, no-sequencing, and vlan keywords added in JunosE
Release 7.1.0.
frame-relay keyword added in JunosE Release 9.1.0.
ethernet-raw-mode keyword added in JunosE Release 10.0.0.
Routes layer 2 traffic to the specified router by creating an MPLS shim interface on the
layer 2 interface. The router can use any MPLS LSP to the remote destination address
that you specify. You must issue this command in the virtual router where the remote
address can be reached; that is, in the virtual router providing core connections. The no
version removes the shim interface. See also the route interface command.
NOTE: This command is supported for configuration on an ATM port (ATM
Adaptation Layer 5 [AAL5] over an ATM major interface). Before you can
specify VPI/VCI ranges and cell concatenation parameters on the ATM port
to enable transmission of multiple ATM virtual circuits over a single
pseudowire, you must associate the ATM port with the corresponding
pseudowire using the mpls-relay or router interface tunnel command. For
more information about the support for multiple VCs over a single pseudowire,
see Multiple ATM Virtual Circuits over a Single Pseudowire Overview in the
JunosE BGP and MPLS Configuration Guide
remoteIpAddress—IP address of the router on the remote end of the layer 2 circuit
vcidValue—Integer in the range 1–4294967295 that identifies the virtual connection;
the two ends across the MPLS core must match inside each VC type
NOTE: The VLAN ID, DLCI, or ATM VPI/VCI are not related to the VC ID and
can be different on each end of the connection.
groupIdValue—Integer in the range 0–4294967295 that identifies a group of virtual
connections; not currently used
control-word—Indicates that the local preference is to use the control word for the
layer 2 packets encapsulated in MPLS packets sent to the remote PE router. The default
preference is determined by the interface stack on which the MPLS interface is stacked.
Copyright © 2010, Juniper Networks, Inc.