Differences; Ce-Side Load Balancing For Martini Layer 2 Transport; Understanding Ce Load Balancing For Martini Layer 2 Transport - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

Software for e series broadband services routers bgp and mpls configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12:
Table of Contents

Advertisement

Local Cross-Connects for HDLC Layer 2 Services Configuration Differences

CE-Side Load Balancing for Martini Layer 2 Transport

Understanding CE Load Balancing for Martini Layer 2 Transport

Copyright © 2010, Juniper Networks, Inc.
host1(config-if)#route interface tunnel mpls:tunnel-to-pe2 1 relay-format ppp
(Optional) Attach an MPLS policy to the HDLC layer 2 circuit by using the mpls policy
3.
command.
host1(config-if)#mpls policy input hdlc-policy
Configure the serial or POS interface and MPLS on the remote PE device.
4.
The interfaces at either end of the HDLC layer 2 circuit can be different types and have
different speeds. For example, you can configure an HDLC layer 2 circuit between a
serial interface on a T1 circuit and a POS interface on an OC3 circuit.
Local Cross-Connects for HDLC Layer 2 Services Configuration Differences on page 545
You can also configure an HDLC layer 2 circuit in a local cross-connect configuration
between serial or POS interfaces within the same router.
The procedure is basically the same for configuring an HDLC layer 2 interface between
two PE routers and for a local cross-connect, with the following differences for local
cross-connects:
You must use the mpls-relay command instead of the route interface command to
configure a local cross-connect for HDLC layer 2 services.
You use the IP address of the local router as the value for the destination IP address
(remote address) in the mpls-relay command.
This section contains the following subsections:
Understanding CE Load Balancing for Martini Layer 2 Transport on page 545
Configuration of Many Shim Interfaces with the Same Peer, VC Type, and VC
ID on page 546
Example: Configuring Many Shim Interfaces with the Same Peer, VC Type, and VC
ID on page 546
Load-Balancing Group Configuration on page 547
MPLS Interfaces and Labels on page 549
Configuring Load-Balancing Groups on page 549
For layer 2 circuits over an MPLS core, each circuit normally has a single shim interface
on the local router. In the case of a local cross-connects configuration, each end of the
cross-connect has a single shim interface, creating a two-way cross-connect.
Alternatively, a given layer 2 circuit or each end of a local cross-connect can have many
shim interfaces. In these cases, traffic destined for the CE routers is load-balanced among
the multiple shim interfaces. This is known as CE-side load balancing. In the case of
Chapter 9: Configuring Layer 2 Services over MPLS
545

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents