Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX/QFX] MPLS based CCC using a Layer 2 circuit with EX and MX as PE routers

0

0

Article ID: KB24409 KB Last Updated: 05 Mar 2017Version: 2.0
Summary:
This article provides information to administrators on how to configure the EX and MX devices as PE routers to transfer the tagged and untagged traffic of multiple customers.

You can send any kind of traffic over a CCC (Circuit cross-connect), including non-standard bridge protocol data units (BPDUs) that are generated by other vendor equipment.  
Symptoms:
  • To carry the tagged and untagged Layer 2 traffic across the MPLS CCC network, with the routers at the edge with the combination of EX and MX.

  • In this example, it is EX4200/EX3200 at one side and MX80 on the other side.  
Cause:
You configure the customer edge interface of the PE switches as a circuit cross-connect (CCC) to create a transparent connection between two circuits. When you configure an interface as a CCC, the interface is removed from the default VLAN, if it was a member of the VLAN.

The interface becomes an MPLS tunnel, which is used exclusively for MPLS packets. You can create different CCCs for different customers or to segregate different traffic streams over different MPLS tunnels. Using a CCC configuration, you can connect the following types of circuits:

  • Local interface with remote interface or VLAN

  • Local VLAN with remote interface or VLAN

Note: The VLAN CCC configuration must use the same type of switch for both of the PE switches. For example, you cannot use an EX8200 switch for one PE switch and an EX3200 or EX4200 switch for the other PE switch.
 
Solution:
Due to the limitation of VLAN-CCC to have the same type of switch for both of the PE devices, you can use a workaround to get VLAN-CCC carry the L2 traffic of different customers. 

In this scenario, a different platform is used; EX4200 and MX80 are configured as the PE devices. You need to use the VLAN-CCC configuration at the MX end and the Ethernet-CCC configuration at the EX end.

This example shows the configuration for only for one CE device. To connect multiple customers, you need to configure different LSP’s to carry the traffic of different customers. The configuration is as follows:

Note: This workaround does not work with the combination of different EX platforms. For example, EX8200 and EX4200/EX3200.





On the MX device:
set interfaces ge-1/1/3 flexible-vlan-tagging
set interfaces ge-1/1/3 encapsulation vlan-ccc
set interfaces ge-1/1/3 unit 0 encapsulation vlan-ccc
set interfaces ge-1/1/3 unit 0 vlan-id-range 700-800
set interfaces ge-1/1/3 unit 0 family ccc

set interfaces ge-1/1/2 unit 0 family inet address 192.168.1.2/30
set interfaces ge-1/1/2 unit 0 family mpls

set protocols mpls label-switched-path lsp-to-ex3200 to 10.0.0.1
set protocols mpls interface ge-1/1/2.0

set protocols rsvp interface lo0.1
set protocols rsvp interface ge-1/1/2.0

set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface lo0.1
set protocols ospf area 0.0.0.0 interface ge-1/1/2.0

set protocols connections remote-interface-switch test interface ge-1/1/3.0
set protocols connections remote-interface-switch test transmit-lsp lsp-to-ex3200
set protocols connections remote-interface-switch test receive-lsp lsp-to-mx

On the EX device:
set interfaces ge-0/0/10 unit 0 family ccc

set interfaces ge-0/0/0 unit 0 family inet address 192.168.1.1/30
set interfaces ge-0/0/0 unit 0 family mpls

set protocols mpls label-switched-path lsp-to-mx to 10.0.0.2
set protocols mpls interface ge-0/0/0.0

set protocols rsvp interface lo0.0
set protocols rsvp interface ge-0/0/0.0

set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface ge-0/0/0.0

set protocols connections remote-interface-switch test interface ge-0/0/10.0
set protocols connections remote-interface-switch test transmit-lsp lsp-to-mx
set protocols connections remote-interface-switch test receive-lsp lsp-to-ex3200


On CE:

Configure the trunk port on the customer device, which is connected to the PE routers, to carry multiple VLAN traffic.

Troubleshooting:

user@switch> show mpls lsp

Ingress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
10.0.0.1 10.0.0.2 Up 0 1 FF - 300064 lsp-to-ex3200
Total 1 displayed, Up 1, Down 0

Egress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
10.0.0.2 10.0.0.1 Up 0 1 FF 299840 - lsp-to-mx
Total 1 displayed, Up 1, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

user@switch>
show connections

CCC and TCC connections [Link Monitoring On]
Legend for status (St) Legend for connection types
UN -- uninitialized if-sw: interface switching
NP -- not present rmt-if: remote interface switching
WE -- wrong encapsulation lsp-sw: LSP switching
DS -- disabled tx-p2mp-sw: transmit P2MP switching
Dn -- down rx-p2mp-sw: receive P2MP switching
-> -- only outbound conn is up
<- -- only inbound conn is up Legend for circuit types
Up -- operational intf -- interface
RmtDn -- remote CCC down tlsp -- transmit LSP
Restart -- restarting rlsp -- receive LSP
Connection/Circuit Type St Time last up # Up trans
test rmt-if Up May 7 14:36:29 20
ge-1/1/3.0 intf Up
lsp-to-ex3200 tlsp Up
lsp-to-mx rlsp Up

Ingress LSP: 1 sessions
To From State Rt P ActivePath LSPname
10.0.0.1 10.0.0.2 Up 0 * lsp-to-ex3200
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
10.0.0.2 10.0.0.1 Up 0 1 FF 299840 - lsp-to-mx
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

user@switch>
show rsvp session

You can verify the tagging on the CE device via a capture:

00:19:e2:55:ed:4d > 00:19:e2:52:31:80, ethertype 802.1Q (0x8100), length 102: vlan 700, p 0, ethertype IPv4, (tos 0x0, ttl 64, id 62699, offset 0, flags [none], proto: ICMP (1), length: 84) 5.5.5.1 > 5.5.5.2: ICMP echo request, id 7286, seq 0, length 64
00:19:e2:55:ed:4d > 00:19:e2:52:31:80, ethertype 802.1Q (0x8100), length 102: vlan 800, p 0, ethertype IPv4, (tos 0x0, ttl 64, id 63478, offset 0, flags [none], proto: ICMP (1), length: 84) 8.8.8.1 > 8.8.8.2: ICMP echo request, id 7288, seq 0, length 6


 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search