[rbak-nsp] [j-nsp] L2VPN between Juniper MX and SmartEdge

[Olivier Benghozi]

OK, found the problem in my config that prevented the stuff to just work.

One does not simply walk into new JunOS fancy features.
Conclusion is that the only piece of code behind the chained composite next-hop ingress for l2ckt is drop_the packets_directed_toward_the other_PE.c.

Thanks for your help, though :)


> Le 10 juil. 2015 à 15:26, Olivier Benghozi <olivier.benghozi at wifirst.fr> a écrit :
> 
> Thanks David;
> 
> how was configured the port or lag itself on the SE side? Between encap rw, transport, or whatever, I don't have much success.
> 
> thank,
> Olivier
> 
>> Le 10 juil. 2015 à 12:00, david.roy at orange.com a écrit :
>> 
>> Here the config part of SE :
>> 
>> 
>> 
>> l2vpn profile L2PROFILE 
>> peer X.X.X.X
>>   log-pw-up-down
>>   remote-encap ethernet
>> 
>> l2vpn
>> 
>> xc-group collect
>>  xc lg GEC3  vlan-id  1668 vc-id 1668 profile L2PROFILE
>> 
>> 
>> 
>> David Roy 
>> IP/MPLS NOC engineer - Orange France
>> Ph. : +33 2 99 28 57 66
>> Mob. : +33 6 85 52 22 13
>> SkypeID : davidroy.35
>> david.roy at orange.com
>> 
>> JNCIE x3 (SP #703 ; ENT #305 ; SEC #144)
>> 
>> 
>> -----Original Message-----
>> From: Olivier Benghozi [mailto:olivier.benghozi at wifirst.fr] 
>> Sent: jeudi 9 juillet 2015 23:26
>> To: ROY David DTSI/DERS
>> Cc: redback-nsp at puck.nether.net; juniper-nsp
>> Subject: Re: [j-nsp] L2VPN between Juniper MX and SmartEdge
>> 
>> Hi David,
>> 
>> any suggestions about the SE config part ?
>> I tried both in dot1q and dot1q tunnel, on the port.
>> 
>> 
>> Olivier
>> 
>>> Le 9 juil. 2015 à 23:19, david.roy at orange.com a écrit :
>>> 
>>> Hello
>>> 
>>> Here my config on MX which works with SE routers:
>>> 
>>> 
>>> xe-19/0/2 {
>>> vlan-tagging;
>>>      mtu 4488;
>>>      encapsulation flexible-ethernet-services;
>>> 	unit 1668 {
>>>                  encapsulation vlan-ccc;
>>>                  vlan-id 1668;
>>>                  input-vlan-map pop;
>>>                  output-vlan-map push;
>>>              }
>>> l2circuit {
>>>              neighbor X.X.X.X {
>>>                  interface xe-19/0/2. 1668{
>>>                      virtual-circuit-id 1668;
>>>                      encapsulation-type ethernet;
>>>                  }
>>> 	}
>>> }
>>> 
>>> David Roy
>>> IP/MPLS NOC engineer - Orange France
>>> Ph. : +33 2 99 28 57 66
>>> Mob. : +33 6 85 52 22 13
>>> SkypeID : davidroy.35
>>> david.roy at orange.com
>>> 
>>> JNCIE x3 (SP #703 ; ENT #305 ; SEC #144)
>>> 
>>> 
>>> -----Original Message-----
>>> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On 
>>> Behalf Of Olivier Benghozi
>>> Sent: jeudi 9 juillet 2015 22:07
>>> To: redback-nsp at puck.nether.net; juniper-nsp
>>> Subject: [j-nsp] L2VPN between Juniper MX and SmartEdge
>>> 
>>> Hi guys,
>>> 
>>> any clue about interoperability issue between Juniper (some MX in JunOS 13.3R5, MPC cards) and Redback (SE600, SEOS 12.1.1.9, PPA3 20x1GE card) about L2VPN pseudowire, Martini style (using LDP signaling and LDP LSP) ?
>>> 
>>> I'm trying to use such feature to forward a vlan between some equipments plugged to those two routers; the tunnel is up, packets flow from the Redback dot1q pvc to the stuff plugged behind the MX vlan-tagged unit (in family vlan-ccc), but in the other direction, the SmartEdge keeps saying "packets sent: 0" on the physical port...
>>> 
>>> 
>>> Thanks.
>>> Olivier
>>> 
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net 
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>> 
>>> ______________________________________________________________________
>>> ___________________________________________________
>>> 
>>> Ce message et ses pieces jointes peuvent contenir des informations 
>>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
>>> exploites ou copies sans autorisation. Si vous avez recu ce message 
>>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>> 
>>> This message and its attachments may contain confidential or 
>>> privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>>> Thank you.
>>> 
>> 
>> 
>> _________________________________________________________________________________________________________________________
>> 
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>> 
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>> 
>