Switching

Hello.
Does anyone have an experience of configuring l2circuit on ex4550?
I'm trying to deploy an eompls (VLANID:600) between ex4550[12.3R9.4] and cisco 6504. But I didn't see any eompls outgoing packets from ex4550. NOTHING.

PE interface:

 ex4550 and cisco6504 are directly-connected mpls/ldp-neighbors:

l2c is UP and labels are right at both ends

 labels push-pop behavior is corect:

Where could I go wrong?
P.S. MPLS/MPLS L3 VPN works fine.

Did you enable family l2 vpn signaling under protocols bgp ?

family l2vpn {
                signaling;
            }

That's unnecessary, I guess.
This l2c is only ldp-based

OK. What have we got here...

EX4550:

CISCO-6504: 

And xconnect vc on C6504:

let me see If i can make any attempt in my lab today. for building your setup

Some info :

http://www.juniper.net/documentation/en_US/junos14.1/topics/task/configuration/mpls-ex-series-provider-edge-switches-ccc-cli.html

Forgot to say: In Wireshark I can see incoming mpls packets on ge-0/0/0 from the side of C6504 (label:299776), but I have no any outgoing packets on ge-0/0/0 toward C6504.

I just tought of something, It can be that Cisco and Juniper do not understand each others TPIDs for vlan-ccc

you can change the encapsulation on your juniper to extended-vlan-ccc instead of vlan-ccc see the note below

Note: Some vendors use the proprietary TPIDs 0x9100 and 0x9901 to encapsulate a VLAN-tagged packet into a VLAN-CCC tunnel to interconnect a geographically separated metro Ethernet network. By configuring the extended-vlan-ccc encapsulation type, a Juniper Networks router can accept all three TPIDs (0x8100, 0x9100, and 0x9901).

You can give this a try

Can you please use RVIs on the uplink interface instead of vlan-tagging?

You might be running into this:

https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR823566

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

can't assign a mpls family on RVI....

interfaces vlan unit 967                        
family inet {
    address 192.168.128.102/30;
}
family iso {
    mtu 1497;
}
family mpls {
    mtu 1546;
}

commit and...

[edit interfaces vlan unit 967]
  'family'
     family mpls not valid on VLAN interface
error: configuration check-out failed

 Without this family I have very tiny mpls routing table:

cisco@JUN-EX4550-ATS-54# run show route table mpls.0 

mpls.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 14:58:59, metric 1
                      Receive
1                  *[MPLS/0] 14:58:59, metric 1
                      Receive
2                  *[MPLS/0] 14:58:59, metric 1
                      Receive
13                 *[MPLS/0] 14:58:59, metric 1
                      Receive
16                 *[VPN/0] 14:58:57
                      to table ETTH-MGMT.inet.0, Pop      
17                 *[VPN/0] 14:58:57
                      to table IPDSLAM.inet.0, Pop      
18                 *[VPN/0] 14:58:57
                      to table IPTV.inet.0, Pop      
19                 *[VPN/0] 14:58:57
                      to table SIP-KMR.inet.0, Pop      
299776             *[L2CKT/7] 00:05:46
                    > via ge-0/0/24.600, Pop       Offset: 4

 That's why I've used sub-interface for mpls/ldp neighbor.

About PR823566. Result of this problem - untagged encapsulated ethernet frames. Right? In my case even this didn't happens.

Please read the url below,  half way down the page I have pasted the Noted mentioned on the page:

Routing Protocol

MPLS works in coordination with the interior gateway protocol (IGP). Therefore, you must configure OSPF or IS-IS as the routing protocol on the loopback interface and core interfaces of both the PE switches and the provider switches.

The core interfaces can be either Gigabit Ethernet or 10-Gigabit Ethernet interfaces, and they can be configured as either individual interfaces or as aggregated Ethernet interfaces.

http://www.juniper.net/techpubs/en_US/junos13.3/topics/concept/mpls-ex-series-components.html

Useless 😞
http://www.juniper.net/techpubs/en_US/junos13.3/to​pics/concept/mpls-ex-series-components.html - this document was published 2011-08-16 and maybe obsoleted.

http://www.juniper.net/techpubs/en_US/junos12.3/topics/task/configuration/mpls-ex-series-provider-edge-switches-ip-cli.html

Let me have a look today to start building your setup in the lab, so I can fidle a bit around and see how we can work around it.

UPDATE: captured incoming (EX4550 ge-0/0/0) ARP-packet:

EssentialRoot

Can you dump traffic incoming to Cisco port.

I have 2 EX4500 with to links between them. One link is a fiber, another via l2 switching network. When mpls traffic flows via fiber - works fine, when mpls traffic flows via l2 switching network - l2vpn, l2circuit, l3vpn not work (ospf - ok, rsvp - ok, ldp - ok). When I see dump - random tag 4093 insert before mpls (555 vlan id of service). 

Could you show both EX configs?

We do not have flat switching network. All of our nodes are L3 IP/MPLS P/PE devices (it may be switches or routers), but all links between them are P-to-P IP/MPLS/ISIS (over vlans).

I haven't solved this problem yet and I'm really tired. CCC on EX8208 works great even through CISCO P-routers.

But EX4550... Bummer dude 😞

Read this document carefully.

http://www.juniper.net/techpubs/en_US/junos15.1/topics/concept/mpls-ex-series-components.html

With any junos you MUST forget about VLANs on mpls-core interfaces. They MUST have only unit 0 subinterface and no vlan-tagging anymore. It's true.
But wait a minute, what have we got here:
1. Say goodbye to switching .
2. Say goodbye to other vendors.
3. CCC is very unstable.

I have no AFL for EX4550 and JTAC adviced me to buy AFL as solution for my issue.