Re: [j-nsp] EVPN + QinQ, individual bridge-domains for CVID's

2017-10-24 Thread Andrew Thrift 
This is on MX boxes running 15.1R6

I suspect I am going to end up implementing a hack to get this working !



On Wed, Oct 25, 2017 at 4:16 AM, Alain Hebert  wrote:
> Hi,
>
> Depending of your relation with your local JNP resellers.
>
> You could get vMX, vQFX and vSRX and build yourself a lab using (ESXi in
> our case).
>
> In the past vMX wasn't working correctly for EVPN but 17.x is working
> with our MX240+vMX+QFX lab.
>
> But we're staying away from LS since we had a series of crashes in 16.x.
>
> TLDR: Good luck =D
>
> -
> Alain Hebertaheb...@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
>
> On 10/24/17 10:47, Aaron Gould wrote:
>>
>> Since you mentioned it Evpn in lsys ?  I don't think that works.  If
>> so please tell me it does so I can try it.  I really would like to know if I
>> can run EVPN in LSYS on MX104... let me know if I need to simply change to a
>> different version of JUNOS and I'll do it.
>>
>> [edit]
>> r2@lab-mx104:r2# set routing-instances test instance-type ?
>> Possible completions:
>>forwarding   Forwarding instance
>>l2backhaul-vpn   L2Backhaul/L2Wholesale routing instance
>>l2vpnLayer 2 VPN routing instance
>>layer2-control   Layer 2 control protocols
>>mpls-internet-multicast  Internet Multicast over MPLS routing instance
>>no-forwardingNonforwarding instance
>>virtual-router   Virtual routing instance
>>virtual-switch   Virtual switch routing instance
>>vpls VPLS routing instance
>>vrf  Virtual routing forwarding instance
>> [edit]
>>
>> [edit]
>> r2@lab-mx104:r2# run show version
>> Hostname: lab-mx104
>> Model: mx104
>> Junos: 14.2R7.5
>>
>> -Aaron
>>
>>
>>
>
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] EVPN + QinQ, individual bridge-domains for CVID's

2017-10-24 Thread Alain Hebert 

    Hi,

    Depending of your relation with your local JNP resellers.

    You could get vMX, vQFX and vSRX and build yourself a lab using 
(ESXi in our case).


    In the past vMX wasn't working correctly for EVPN but 17.x is 
working with our MX240+vMX+QFX lab.


    But we're staying away from LS since we had a series of crashes in 
16.x.


    TLDR: Good luck =D

-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 10/24/17 10:47, Aaron Gould wrote:

Since you mentioned it Evpn in lsys ?  I don't think that works.  If so 
please tell me it does so I can try it.  I really would like to know if I can 
run EVPN in LSYS on MX104... let me know if I need to simply change to a 
different version of JUNOS and I'll do it.

[edit]
r2@lab-mx104:r2# set routing-instances test instance-type ?
Possible completions:
   forwarding   Forwarding instance
   l2backhaul-vpn   L2Backhaul/L2Wholesale routing instance
   l2vpnLayer 2 VPN routing instance
   layer2-control   Layer 2 control protocols
   mpls-internet-multicast  Internet Multicast over MPLS routing instance
   no-forwardingNonforwarding instance
   virtual-router   Virtual routing instance
   virtual-switch   Virtual switch routing instance
   vpls VPLS routing instance
   vrf  Virtual routing forwarding instance
[edit]

[edit]
r2@lab-mx104:r2# run show version
Hostname: lab-mx104
Model: mx104
Junos: 14.2R7.5

-Aaron





___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] EVPN + QinQ, individual bridge-domains for CVID's

2017-10-24 Thread Aaron Gould 
Since you mentioned it Evpn in lsys ?  I don't think that works.  If so 
please tell me it does so I can try it.  I really would like to know if I can 
run EVPN in LSYS on MX104... let me know if I need to simply change to a 
different version of JUNOS and I'll do it.

[edit]
r2@lab-mx104:r2# set routing-instances test instance-type ?
Possible completions:
  forwarding   Forwarding instance
  l2backhaul-vpn   L2Backhaul/L2Wholesale routing instance
  l2vpnLayer 2 VPN routing instance
  layer2-control   Layer 2 control protocols
  mpls-internet-multicast  Internet Multicast over MPLS routing instance
  no-forwardingNonforwarding instance
  virtual-router   Virtual routing instance
  virtual-switch   Virtual switch routing instance
  vpls VPLS routing instance
  vrf  Virtual routing forwarding instance
[edit]

[edit]
r2@lab-mx104:r2# run show version
Hostname: lab-mx104
Model: mx104
Junos: 14.2R7.5

-Aaron


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] EVPN + QinQ, individual bridge-domains for CVID's

2017-10-24 Thread Alain Hebert 

    Expected hack with QFX5100

    PE with CVID <-> Trunk Port <-> P or PE with EVPN

    Or Logical System, but we stop using those on MXs after some 
crashes in the past.


-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 10/23/17 23:33, Andrew Thrift wrote:

Hello All,

I have been working on a scenario that I have not been able to solve.

I have an ae interface that has multiple QinQ services coming in, some
of these are terminating into l2circuits(CCC) and others are
terminating into EVPN routing instances.

So far with EVPN I have only been dealing with L2 transport,
effectively bridging the outer tag to an EVPN routing-instance, which
happily transports all the inner tags across the EVPN transport to the
other PE routers.

What I am now trying to achieve is to terminate some of the inner-tags
(CVID's) to IRB instances.

I started by trying to split the inner-cvid's into their own
bridge-domains, but JunOS seems to not like mapping inner-vlan's into
bridge-domains with EVPN instances.

Has anyone else managed to terminate inner tags in an EVPN instance
into separate bridge domains?  Or is this just an unsupported
configuration ?


Regards,



Andrew
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] EVPN + QinQ, individual bridge-domains for CVID's

2017-10-23 Thread Andrew Thrift 
Hello All,

I have been working on a scenario that I have not been able to solve.

I have an ae interface that has multiple QinQ services coming in, some
of these are terminating into l2circuits(CCC) and others are
terminating into EVPN routing instances.

So far with EVPN I have only been dealing with L2 transport,
effectively bridging the outer tag to an EVPN routing-instance, which
happily transports all the inner tags across the EVPN transport to the
other PE routers.

What I am now trying to achieve is to terminate some of the inner-tags
(CVID's) to IRB instances.

I started by trying to split the inner-cvid's into their own
bridge-domains, but JunOS seems to not like mapping inner-vlan's into
bridge-domains with EVPN instances.

Has anyone else managed to terminate inner tags in an EVPN instance
into separate bridge domains?  Or is this just an unsupported
configuration ?


Regards,



Andrew
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp