Hi,
to conclude my issue for future reference: Brocade replaced my line-card
and the LACP and remote-fault issues was gone and I am error-free for
about 3 months now.
We are also on the 6.1 code path for almost 5 months now, except TSB
2017-253-A, that did not affect us, I have no issues, running mostly
BGP, OSPF, …
Jörg
On 25 Jan 2017, at 9:16, Youssef Bengelloun-Zahr wrote:
> Dear Jörg,
>
> I'm more concerned (surprised !?!) about the LACP flaps you've been
> noticing as 5.8f seems to be really mature.
>
> Have you been able to pinpoint to root cause ? Is it related to the OS
> version or a local issue ?
>
> Best regards.
>
>
>
> 2017-01-24 13:15 GMT+01:00 Wayne Lee via foundry-nsp <
> foundry-nsp@puck.nether.net>:
>
>> Hello
>>
>> I've found that most versions have had this issue for me, I tend to
>> do
>> them via TFTP or using the "paste slowly" command in iTerm. I was
>> actually
>> pasting in a load of VPLS config but the effect was the same.
>>
>>
>>
>> On 24 January 2017 at 12:13, Jörg Kost <jk@ip-clear.de> wrote:
>>
>>> Hello,
>>>
>>> I am currently running the annoying issue with 5.8f, that I cant
>>> paste
>>> large ip prefix-lists via ssh into the router anymore. The session
>>> will
>>> hang and I have already opened a ticket down at Brocade. Somebody
>>> can
>>> verify this? E.g. try to paste the the content of
>>> http://pastebin.com/YEf6c1aT several times into the shell.
>>>
>>> Also I am seeing some LACP out of sync errors randomly popping out
>>> since
>>> the upgrade, however I still investigate if there is some other
>>> (faulty)
>>> reason for this ones:
>>>
>>> Jan 23 10:40:23:W:LACP: ethernet 2/4 state changes from LACP-BLOCKED
>>> to
>>> FORWARD
>>> Jan 23 10:40:23:I:LACP: Port 2/4 mux state transition: not aggregate
>>> ->
>>> aggregate
>>> Jan 23 10:40:23:W:LACP: ethernet 2/4 state changes from DOWN to
>>> LACP-BLOCKED
>>> Jan 23 10:40:22:W:LACP: ethernet 2/4 state changes from LACP-BLOCKED
>>> to
>>> DOWN
>>> Jan 23 10:40:22:I:LACP: Port 2/4 mux state transition: aggregate ->
>>> not
>>> aggregate (reason: peer is out of sync)
>>>
>>> Jörg
>>>
>>>
>>> On 16 Dec 2016, at 18:42, Youssef Bengelloun-Zahr wrote:
>>>
>>> All,
>>>>
>>>> It came out à few weeks ago and seems it to be the lucky charm...
>>>> At
>>>> least for us. It was also designated as the new official target
>>>> path.
>>>>
>>>> Any feedbacks from out there ? Any head acks in perspective ?
>>>>
>>>> Thank you.
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
to conclude my issue for future reference: Brocade replaced my line-card
and the LACP and remote-fault issues was gone and I am error-free for
about 3 months now.
We are also on the 6.1 code path for almost 5 months now, except TSB
2017-253-A, that did not affect us, I have no issues, running mostly
BGP, OSPF, …
Jörg
On 25 Jan 2017, at 9:16, Youssef Bengelloun-Zahr wrote:
> Dear Jörg,
>
> I'm more concerned (surprised !?!) about the LACP flaps you've been
> noticing as 5.8f seems to be really mature.
>
> Have you been able to pinpoint to root cause ? Is it related to the OS
> version or a local issue ?
>
> Best regards.
>
>
>
> 2017-01-24 13:15 GMT+01:00 Wayne Lee via foundry-nsp <
> foundry-nsp@puck.nether.net>:
>
>> Hello
>>
>> I've found that most versions have had this issue for me, I tend to
>> do
>> them via TFTP or using the "paste slowly" command in iTerm. I was
>> actually
>> pasting in a load of VPLS config but the effect was the same.
>>
>>
>>
>> On 24 January 2017 at 12:13, Jörg Kost <jk@ip-clear.de> wrote:
>>
>>> Hello,
>>>
>>> I am currently running the annoying issue with 5.8f, that I cant
>>> paste
>>> large ip prefix-lists via ssh into the router anymore. The session
>>> will
>>> hang and I have already opened a ticket down at Brocade. Somebody
>>> can
>>> verify this? E.g. try to paste the the content of
>>> http://pastebin.com/YEf6c1aT several times into the shell.
>>>
>>> Also I am seeing some LACP out of sync errors randomly popping out
>>> since
>>> the upgrade, however I still investigate if there is some other
>>> (faulty)
>>> reason for this ones:
>>>
>>> Jan 23 10:40:23:W:LACP: ethernet 2/4 state changes from LACP-BLOCKED
>>> to
>>> FORWARD
>>> Jan 23 10:40:23:I:LACP: Port 2/4 mux state transition: not aggregate
>>> ->
>>> aggregate
>>> Jan 23 10:40:23:W:LACP: ethernet 2/4 state changes from DOWN to
>>> LACP-BLOCKED
>>> Jan 23 10:40:22:W:LACP: ethernet 2/4 state changes from LACP-BLOCKED
>>> to
>>> DOWN
>>> Jan 23 10:40:22:I:LACP: Port 2/4 mux state transition: aggregate ->
>>> not
>>> aggregate (reason: peer is out of sync)
>>>
>>> Jörg
>>>
>>>
>>> On 16 Dec 2016, at 18:42, Youssef Bengelloun-Zahr wrote:
>>>
>>> All,
>>>>
>>>> It came out à few weeks ago and seems it to be the lucky charm...
>>>> At
>>>> least for us. It was also designated as the new official target
>>>> path.
>>>>
>>>> Any feedbacks from out there ? Any head acks in perspective ?
>>>>
>>>> Thank you.
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp