Juniper L2Circuit Config

3 01 2008

Just posting a basic l2circuit configuration for my own reference… Piece of cake really, but it won’t work unless you use a dynamic routing protocol – the static that I had configured wasn’t enough.


In the below snippet of config, the fe-0/0/1 interface is the customer-facing interface, and fe-0/0/0 is the ISP side. Customer traffic is expected with a VLAN tag of 512.

set version 8.3R2.8
set interfaces fe-0/0/0 unit 0 family inet address 192.168.0.1/24
set interfaces fe-0/0/0 unit 0 family mpls
set interfaces fe-0/0/1 vlan-tagging
set interfaces fe-0/0/1 speed 100m
set interfaces fe-0/0/1 link-mode full-duplex
set interfaces fe-0/0/1 encapsulation vlan-ccc
set interfaces fe-0/0/1 unit 0 vlan-id 1
set interfaces fe-0/0/1 unit 100 encapsulation vlan-ccc
set interfaces fe-0/0/1 unit 100 vlan-id 512
set interfaces lo0 unit 0 family inet address 127.0.0.1/32
set interfaces lo0 unit 0 family inet address 10.1.1.2/32 primary
set routing-options static route 0.0.0.0/0 next-hop 192.168.0.2
set protocols mpls interface all
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface fe-0/0/0.0
set protocols ldp interface all
set protocols l2circuit neighbor 10.1.1.1 interface fe-0/0/1.100 virtual-circuit-id 2
set protocols l2circuit neighbor 10.1.1.1 interface fe-0/0/1.100 no-control-word

These routers were just back-to-back, so it was a pretty simple layout. Once the other side was configured and there was carrier on the customer ports, the circuit came up. Check it using the following command:

root# run show l2circuit connections
Layer-2 Circuit Connections:
-
Legend for connection status (St)
EI -- encapsulation invalid NP -- interface h/w not present
MM -- mtu mismatch Dn -- down
EM -- encapsulation mismatch VC-Dn -- Virtual circuit Down
CM -- control-word mismatch Up -- operational
VM -- vlan id mismatch CF -- Call admission control failure
OL -- no outgoing label XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad
-
Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.1.1.1
Interface Type St Time last up # Up trans
fe-0/0/1.100(vc 2) rmt Up Jan 3 18:12:44 2008 1
Local interface: fe-0/0/1.100, Status: Up, Encapsulation: VLAN
Remote PE: 10.1.1.1, Negotiated control-word: No
Incoming label: 100000, Outgoing label: 100000

Advertisements

Actions

Information

One response

25 07 2008
tsw

do you have same example for cisco side in case CSCO-JNPR connection?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: