# mpls l2transport load-balancing-group

#### Syntax

mpls l2transport load-balancing-group groupNumber
[ mpls-relay remoteIpAddress | route interface tunnel lspName ]
[ vc-id ] vcIdValue [ group-id groupIdValue ]
[ control-word | no-control-word ] [ sequencing | no-sequencing ]
[ relay-format { ethernet | ppp | vlan } ]

no mpls l2transport load-balancing-group groupNumber
{ mpls-relay remoteIpAddress | route interface tunnel lspName } [ vc-id ] vcId

#### Release Information

Command introduced before JunosE Release 7.1.0.
control-word, no-control-word, sequencing, and no-sequencing keywords added in JunosE Release 7.1.0.

#### Description

Specifies a Martini layer 2 transport circuit, associates it with a load-balancing group, and accesses L2 Transport Load-Balancing-Circuit Configuration mode. The no version removes a circuit from the load-balancing group and all subinterfaces that the circuit was configured on.

| Note: Using the mpls-relay keywords has the same effect as using the mpls-relay command. Using the route interface keywords has the same effect as using the route interface commands. The relay-format frame-relay option is not supported for the mpls l2transport load-balancing-group command.

#### Options

- groupNumber—Integer in the range 1–127
- remoteIpAddress—IP address of the router on the remote end of the layer 2 circuit
- lspName—Name of the route interface tunnel
- 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
- 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.
- no-control-word—Indicates that the local preference is to not 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.
- sequencing—Specifies that the local preference is to include nonzero sequence numbers with the control word; enabling the remote PE to detect out-of-order packets; has no effect if no control word is sent in the packets. The router always accepts zero sequence numbers and checks the order of nonzero sequence numbers of MPLS packets received from the remote PE; any out of order packets are dropped, regardless of whether sequencing is configured.
- no-sequencing—Specifies that the sequencing number in the control word is set to zero, instructing the remote PE router to not attempt to detect out-of-order packets; has no effect if no control word is sent in the packets.
- relay-format ethernet—Specifies that the router uses Ethernet signaling and encapsulation, which causes the VLAN interface to appear as an Ethernet interface to the other side of the connection; enables a VLAN interface on one side of an MPLS tunnel to communicate with an Ethernet or a bridged Ethernet interface on the other side of an MPLS tunnel. The VLAN tag is not included in the MPLS encapsulation. This option is not available on serial or POS interfaces for HDLC layer 2 circuits. It is available only on VLAN interfaces
- relay-format frame-relay—Specifies that the router uses legacy (pre-RFC 4619) Frame Relay pseudowire type value for signaling and encapsulation. Enables a router running JunosE Software that supports the pseudowire type value defined in RFC 4619, Encapsulation methods for transport of Frame Relay over MPLS Networks, to interoperate with a router that uses the legacy (pre-RFC 4619) pseudowire type value. This option is available on serial or POS interfaces for Frame Relay layer 2 circuits. It is not supported on E120 and E320 routers.
- relay-format ppp—Specifies that the router uses VC-type PPP signaling and PPP encapsulation instead of VC-type HDLC signaling and HDLC encapsulation. The router uses VC-type HDLC signaling and HDLC encapsulation by default. This option is available only on serial and POS interfaces for HDLC layer 2 circuits.
- relay-format vlan—Specifies that the router uses VLAN signaling and encapsulation. This option is not available on serial or POS interfaces for HDLC layer 2 circuits. It is available for VLAN interfaces.

#### Mode

Global Configuration

#### Related Documentation

- Configuring CE-Side Load Balancing for Martini Layer 2 Transport in the JunosE BGP and MPLS Configuration Guide