[GTER] Juniper MX aggregated ethernet não fica UP

Fri Apr 29 14:59:18 -03 2016

bpdu :D 

----------------------------------------
> Date: Wed, 27 Apr 2016 23:27:47 -0300
> From: markinn at gmail.com
> To: gter at eng.registro.br
> Subject: Re: [GTER] Juniper MX aggregated ethernet não fica UP
>
> Caros ,
> o problema era realmente no transporte .
> A operadora atualizou o switch e liberou o lacp normalmente .
> Agradeço a força
>
> Em 27 de abril de 2016 13:52, willian pires <willian_pires at hotmail.com>
> escreveu:
>
>> Bom dia,
>>
>> Garante as seguintes condições:
>>
>> 1 ou os dois lados estão em dynamic lacp
>> 1 dos lados deve estar como passivo
>> 1 dos lados deve estar como ativo
>>
>> Peque 2 dessas condições.
>>
>> 1 lado como ativo 1 lado como passivo
>> quer dizer que 1 vai mandar bpdu outro vai receber -- link ok
>>
>> 1 lado como ativo outro como dynamic o lado dynamic vai
>> mandar bpdu o lado ativo tambem, porem o lado ativo quando recebe
>> bpdu ele descarta, ja o lado dynamic quando recebe 1 bpdu active ele
>> comuta para passive.
>>
>> 1 lado como passivo e outro como dynamic, o lado passivo não manda bpdu
>> mas o lado active manda e recebe um bpdu de resposta do passive.
>>
>> Não conheço nada de Juniper, porem entre cisco e huawei aqui tive esse tipo
>> de evento, e em equipamentos da hp tambem.
>>
>> Forte abraço.
>>
>> ----------------------------------------
>>> Date: Sun, 24 Apr 2016 13:28:54 +1000
>>> From: diogo.montagner at gmail.com
>>> To: gter at eng.registro.br
>>> Subject: Re: [GTER] Juniper MX aggregated ethernet não fica UP
>>>
>>> Defaulted significa que vc nao esta recebendo lacp PDUs.
>>>
>>> On Sunday, 24 April 2016, Marcos Tp <markinn at gmail.com> wrote:
>>>
>>>> show lacp interfaces ae0
>>>> Aggregated interface: ae0
>>>> LACP state: Role Exp Def Dist Col Syn Aggr Timeout
>>>> Activity
>>>> xe-1/3/0 Actor No Yes No No No Yes Fast
>>>> Active
>>>> xe-1/3/0 Partner No Yes No No No Yes Fast
>>>> Passive
>>>> LACP protocol: Receive State Transmit State Mux State
>>>> xe-1/3/0 Defaulted Fast periodic Detached
>>>>
>>>>
>>>> Em 22 de abril de 2016 19:03, Diogo Montagner <
>> diogo.montagner at gmail.com
>>>> <javascript:;>>
>>>> escreveu:
>>>>
>>>>> O que o output do show lacp interfaces mostra ?
>>>>>
>>>>> On Saturday, 23 April 2016, Marcos Tp <markinn at gmail.com
>> <javascript:;>>
>>>> wrote:
>>>>>
>>>>>> vou verificar com eles
>>>>>>
>>>>>> Em 22 de abril de 2016 13:23, Ricardo Oliveira <ricardo.btu at gmail.com
>>>> <javascript:;>
>>>>>> <javascript:;>>
>>>>>> escreveu:
>>>>>>
>>>>>>> Marcos boa tarde.
>>>>>>>
>>>>>>> Seu transporte também é Algar? Caso sim, é muito provável que não
>>>>>> ativaram
>>>>>>> o L2PT no seu transporte impedindo a transmissão de BDPUs do LACP,
>>>> isso
>>>>>>> ocorreu em todas as vezes que ativamos transporte para o PTT com a
>>>>> Algar.
>>>>>>>
>>>>>>> Obrigado.
>>>>>>> Ricardo Freitas.
>>>>>>>
>>>>>>> Em 22 de abril de 2016 11:54, Marcos Tp <markinn at gmail.com
>>>> <javascript:;>
>>>>>> <javascript:;>> escreveu:
>>>>>>>
>>>>>>>> Olá ,
>>>>>>>> a caixa Mx80 não tem ether-options , substituída por giga conforme
>>>>> meu
>>>>>>>> exemplo .
>>>>>>>> Removi a opção fast e tambem não teve efeito .
>>>>>>>> O que reparei é que deve existir algum parametro a mais para fexar
>>>> o
>>>>>>> lacp ,
>>>>>>>> pois
>>>>>>>> se removo da interface agregada o lacp , a interface sobe .
>>>>>>>> Qual a sua operadora de transito até o IX ?
>>>>>>>> Estou usando a algar
>>>>>>>>
>>>>>>>> Em 22 de abril de 2016 11:32, Leonardo Amaral - Listas <
>>>>>>>> listas at leonardoamaral.com.br <javascript:;> <javascript:;>>
>>>> escreveu:
>>>>>>>>
>>>>>>>>> Bom dia!
>>>>>>>>>
>>>>>>>>> Aqui não estamos usando o periodic fast:
>>>>>>>>>
>>>>>>>>> aggregated-ether-options {
>>>>>>>>> link-speed 10g;
>>>>>>>>> lacp {
>>>>>>>>> active;
>>>>>>>>> }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Outro ponto, mais critico:
>>>>>>>>>
>>>>>>>>> interface-range UpStream-PTT {
>>>>>>>>> member xe-0/0/14;
>>>>>>>>> member xe-1/0/14;
>>>>>>>>> description "UpStream PTT-SP";
>>>>>>>>> ether-options {
>>>>>>>>> 802.3ad ae4;
>>>>>>>>> }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Perceba ether-options e não gigether-options. As duas confs estão
>>>>> num
>>>>>>>> QFX,
>>>>>>>>> mas imagino que talvez ajudem diretamente no MX.
>>>>>>>>>
>>>>>>>>> Att,
>>>>>>>>>
>>>>>>>>> Em 22 de abril de 2016 10:08, Marcos Tp <markinn at gmail.com
>>>> <javascript:;>
>>>>>> <javascript:;>> escreveu:
>>>>>>>>>
>>>>>>>>>> Caros ,
>>>>>>>>>> seguindo orientações do ix.br para ativação de um novo
>>>> circuito
>>>>>> com
>>>>>>>>> eles ,
>>>>>>>>>> me solicitaram um lacp entre o meu juniper MX80 e eles .
>>>>>>>>>> Porem a minha porta aggregated ethernet (ae0) nao fica UP
>>>>>>>>>>
>>>>>>>>>> Já fiz agregação de portas em outro cliente com os mesmos
>>>>>> parâmetros
>>>>>>> /
>>>>>>>>>> versão de roteador e firmware e não deu problema .
>>>>>>>>>>
>>>>>>>>>> Alguém tem uma sugestão do que esteja ocorrendo ?
>>>>>>>>>> Segue a minha cfg : Valores de vlan e ips ocultados :p
>>>>>>>>>>
>>>>>>>>>> run show interfaces xe-1/3/0
>>>>>>>>>> Physical interface: xe-1/3/0, Enabled, Physical link is Up
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> run show interfaces ae0
>>>>>>>>>> Physical interface: ae0, Enabled, Physical link is Down
>>>>>>>>>> Interface index: 162, SNMP ifIndex: 577
>>>>>>>>>> Description: Ptt ix
>>>>>>>>>> Link-level type: Ethernet, MTU: 1518, Speed: Unspecified,
>>>> BPDU
>>>>>>> Error:
>>>>>>>>>> None,
>>>>>>>>>> MAC-REWRITE Error: None, Loopback: Disabled, Source
>>>> filtering:
>>>>>>>>> Disabled,
>>>>>>>>>> Flow control: Disabled
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> show chassis
>>>>>>>>>> aggregated-devices {
>>>>>>>>>> ethernet {
>>>>>>>>>> device-count 5;
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>> network-services enhanced-ip;
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> show interfaces xe-1/3/0
>>>>>>>>>> description "PTT IX PIAF 10G";
>>>>>>>>>> gigether-options {
>>>>>>>>>> 802.3ad ae0;
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> show interfaces ae0
>>>>>>>>>> description "Ptt ix";
>>>>>>>>>> vlan-tagging;
>>>>>>>>>> aggregated-ether-options {
>>>>>>>>>> minimum-links 1;
>>>>>>>>>> link-speed 10g;
>>>>>>>>>> lacp {
>>>>>>>>>> active;
>>>>>>>>>> periodic fast;
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>> unit 0 {
>>>>>>>>>> vlan-id ZXXXXXX;
>>>>>>>>>> family inet {
>>>>>>>>>> filter {
>>>>>>>>>> input Cachemara_Internet;
>>>>>>>>>> }
>>>>>>>>>> address XXXXXXXXXXX;
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>> unit 1 {
>>>>>>>>>> vlan-id XXXX;
>>>>>>>>>> family inet6 {
>>>>>>>>>> address XXXXXXXXXX;
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>> --
>>>>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>>> --
>>>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>> --
>>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>>
>>>>>>> --
>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>
>>>>>> --
>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ./diogo -montagner
>>>>> JNCIE-SP 0x41A
>>>>> --
>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>
>>>> --
>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>
>>>
>>>
>>> --
>>> ./diogo -montagner
>>> JNCIE-SP 0x41A
>>> --
>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>
>> --
>> gter list https://eng.registro.br/mailman/listinfo/gter
>>
> --
> gter list https://eng.registro.br/mailman/listinfo/gter