[j-nsp] ether-options vs gigether-options in MX series

[Olivier Benghozi]

On MX, SRX, PTX, ACX, it's «gigether-options» for all ports.
On EX, QFX, it's «ether-options» for all ports.

Ridiculous.

> Le 18 sept. 2018 à 17:58, Drew Weaver <drew.weaver at thenap.com> a écrit :
> 
> Does that mean they're the same, even for xe interfaces?
> 
> -----Original Message-----
> From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> On Behalf Of Olivier Benghozi
> Sent: Tuesday, September 18, 2018 11:57 AM
> To: Juniper List <juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] ether-options vs gigether-options in MX series
> 
> ether-options -> gigether-options
> 
>> Le 18 sept. 2018 à 17:47, Drew Weaver <drew.weaver at thenap.com> a écrit :
>> 
>> Greetings,
>> 
>> I am attempting to create a link aggregation on an MX80.
>> 
>> Reading the documentation it indicates:
>> 
>> ether-options {
>>       802.3ad ae0;
>>   }
>> 
>> To an interface will add that physical link to an aggregation.
>> 
>> However, when I use that and look at the configuration it says:
>> 
>> ether-options {
>>   ##
>>   ## Warning: This feature can be configured only in Ethernet LAN services mode
>>   ## Warning: This feature can be configured only in Ethernet LAN services mode
>>   ## Warning: This feature can be configured only in Ethernet LAN services mode
>>   ## Warning: This feature can be configured only in Ethernet LAN services mode
>>   ## Warning: This feature can be configured only in Ethernet LAN services mode
>>   ##
>>   802.3ad ae0;
>> }
>> If I use gigether-options it accepts it.
>> 
>> What is the correct way of doing this on an MX80 running v 15?
>> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp