Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

2015-11-04 Thread ThienDuc Nguyen 
Hi,
On Wed, Nov 4, 2015 at 7:28 PM, Tobias Heister 
wrote:

> Hi,
>
> Am 03.11.2015 um 23:23 schrieb ThienDuc Nguyen:
>
>> I was trying to create a LACP bundle between two ports : one on a EX4300,
>> the other on a QFX5100.
>> Both link have their speed negotiated at 1GE (but the interface name on
>> the
>> QFX is xe-, I can't force it to ge-, and their are no way to force the
>> speed on the QFX).
>> if I set the lacp speed to 1ge, the configuration can't commit because it
>> sees the QFX interface as a 10G interface...
>>
>>
>> Is their a special knob to activate it, or I need to create LACP on the
>> same device family ?  (the version is  14.1X53-D30.3)
>>
>
> From what you wrote i would suspect that you use a QFX5100 copper version?
> If they behave anything like the EX45XX Copper Versions the interfaces
> will always be xe- regardless of them being only used with 1GE neighbors.
> Would be funny if the interface name would change when lower speeds are
> negotiated.
>

Yes, it's the 48T version. When I rename it to ge-, the xe- interface is
still here, and yes it would be funny ;-)
Note that this version is 3 rate (100m, 1g, 10g).


> Probably the config parser checks the physical interfaces and finds out
> that it is a 10G interface on QFX and 1G Interface on EX and will not
> commit as mixed speed AEs are only supported in later MX code.
>
> I do not know a way around that and do not have copper QFX at hand to
> check. Probably you will have hit one of these corner case situations that
> nobody thought about and nobody ever encountered and nobody ever asked
> about (at least if you ask jtac :))


Thanks a lot, I think next step will be jtac and new code.

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

Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

2015-11-04 Thread Chris Burton 
As far as I know there is no way to set the link speed (only the link-mode
for duplex) on the underlying interfaces in a AE bundle (and they are always
labeled xe-), at least on the code I am running on the QFX5100-48T.  You ca
specify the link-speed for a AE interface which I presume sets the speed of
the underlying bundled interfaces, but I have not tested this out as I have
no EX switches.

set ae9 aggregated-ether-options link-speed ?
Possible completions:
  100g Links are 100G
  100m Links are 100M
  10g  Links are 10G
  1g   Links are 1G
  40g  Links are 40G
  50g  Links are 50G
  80g  Links are 80G
  8g   Links are 8G
  oc192Links are OC-192

Chris

-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Tobias Heister
Sent: Wednesday, November 04, 2015 10:28 AM
To: ThienDuc Nguyen; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

Hi,

Am 03.11.2015 um 23:23 schrieb ThienDuc Nguyen:
> I was trying to create a LACP bundle between two ports : one on a 
> EX4300, the other on a QFX5100.
> Both link have their speed negotiated at 1GE (but the interface name 
> on the QFX is xe-, I can't force it to ge-, and their are no way to 
> force the speed on the QFX).
> if I set the lacp speed to 1ge, the configuration can't commit because 
> it sees the QFX interface as a 10G interface...
>
>
> Is their a special knob to activate it, or I need to create LACP on 
> the same device family ?  (the version is  14.1X53-D30.3)

 From what you wrote i would suspect that you use a QFX5100 copper version?
If they behave anything like the EX45XX Copper Versions the interfaces will
always be xe- regardless of them being only used with 1GE neighbors. Would
be funny if the interface name would change when lower speeds are
negotiated.

Probably the config parser checks the physical interfaces and finds out that
it is a 10G interface on QFX and 1G Interface on EX and will not commit as
mixed speed AEs are only supported in later MX code.

I do not know a way around that and do not have copper QFX at hand to check.
Probably you will have hit one of these corner case situations that nobody
thought about and nobody ever encountered and nobody ever asked about (at
least if you ask jtac :))

--
Kind Regards
Tobias Heister
___
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] LACP on mixed virtual chassis QFX5100/EX4300

2015-11-04 Thread Chris Burton 
Have you tried just setting the EX side and leaving the link-speed statement 
off of the QFX side, since the QFX interfaces are hardcoded to auto negotiate 
only that might work?

 

Chris

 

From: ThienDuc Nguyen [mailto:thienduc.ngu...@zayo.com] 
Sent: Wednesday, November 04, 2015 14:19 PM
To: Chris Burton
Cc: Tobias Heister; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

 

 

On Wed, Nov 4, 2015 at 11:03 PM, Chris Burton  
wrote:

As far as I know there is no way to set the link speed (only the link-mode
for duplex) on the underlying interfaces in a AE bundle (and they are always
labeled xe-), at least on the code I am running on the QFX5100-48T.  You ca
specify the link-speed for a AE interface which I presume sets the speed of
the underlying bundled interfaces, but I have not tested this out as I have
no EX switches.

set ae9 aggregated-ether-options link-speed ?

   

If you set the speed to 1G for example, the commit script failed because of the 
xe- interface seen as a 10G interface.

And yes, the speed is blocked as auto (in the show interface extensive | match 
speed)

 

 

Thien Duc

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

Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

2015-11-04 Thread Vincent Clement 
Hello,

Pretty sure QFX in 10G only, so if you want to achieve that, you'll have to
use a uplink module to have 10G on 4300 side.

Vincent

2015-11-04 2:23 GMT+01:00 Michael Loftis :

> I'd take a closer look at show interfaces. When a link is 1gig QFX calls it
> ge-. So you can have an ex-0/0/1 and a ge-0/0/1 but only one is active as I
> do not believe tri rate SFP+ is supported.
>
> On Tuesday, November 3, 2015, ThienDuc Nguyen 
> wrote:
>
> > Hi
> >
> > I was trying to create a LACP bundle between two ports : one on a EX4300,
> > the other on a QFX5100.
> > Both link have their speed negotiated at 1GE (but the interface name on
> the
> > QFX is xe-, I can't force it to ge-, and their are no way to force the
> > speed on the QFX).
> > if I set the lacp speed to 1ge, the configuration can't commit because it
> > sees the QFX interface as a 10G interface...
> >
> >
> > Is their a special knob to activate it, or I need to create LACP on the
> > same device family ?  (the version is  14.1X53-D30.3)
> >
> > Thanks,
> >
> > *Thien Duc Nguyen*
> > ___
> > juniper-nsp mailing list juniper-nsp@puck.nether.net 
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
>
> --
>
> "Genius might be described as a supreme capacity for getting its possessors
> into trouble of all kinds."
> -- Samuel Butler
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Vincent Clément
+33 6 74 49 66 30
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] LACP on mixed virtual chassis QFX5100/EX4300

2015-11-04 Thread Tobias Heister 

Hi,

Am 03.11.2015 um 23:23 schrieb ThienDuc Nguyen:

I was trying to create a LACP bundle between two ports : one on a EX4300,
the other on a QFX5100.
Both link have their speed negotiated at 1GE (but the interface name on the
QFX is xe-, I can't force it to ge-, and their are no way to force the
speed on the QFX).
if I set the lacp speed to 1ge, the configuration can't commit because it
sees the QFX interface as a 10G interface...


Is their a special knob to activate it, or I need to create LACP on the
same device family ?  (the version is  14.1X53-D30.3)


From what you wrote i would suspect that you use a QFX5100 copper version?
If they behave anything like the EX45XX Copper Versions the interfaces will 
always be xe- regardless of them being only used with 1GE neighbors. Would be 
funny if the interface name would change when lower speeds are negotiated.

Probably the config parser checks the physical interfaces and finds out that it 
is a 10G interface on QFX and 1G Interface on EX and will not commit as mixed 
speed AEs are only supported in later MX code.

I do not know a way around that and do not have copper QFX at hand to check. 
Probably you will have hit one of these corner case situations that nobody 
thought about and nobody ever encountered and nobody ever asked about (at least 
if you ask jtac :))

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