• September 26, 2020, 05:32:13 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Heads up with minor bug in 4.0.0.x  (Read 2845 times)

0 Members and 1 Guest are viewing this topic.

Offline Řyvind Nikolaisen

  • Full Member
  • ***
  • Posts: 52
Heads up with minor bug in 4.0.0.x
« on: March 20, 2015, 09:05:42 AM »
Just thought some of you might want to know about a potentially nasty bug that bit us last week. We have a fair number og VSP4450s running MacSec on 10G links between them. After upgrading the far end to 4.1.0.0, we lost connection while it rebooted - but it stayed down. Link was up, but VLACP kept it down. Solution: Upgrade the other box to 4.1.0.0 also....

Nothing major, but a bit interesting while we waited for software to be transferred, installed and activated on the central 4450s. If you do have a similar setup, make certain that you have a way out of it! 8)

Brgds
Řyvind
Best regards,

Řyvind Nikolaisen
Senior Network Architect
NetNordic Communications AS
Avaya ACE Fx #204


Offline Telair

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 965
Re: Heads up with minor bug in 4.0.0.x
« Reply #1 on: March 20, 2015, 04:07:14 PM »
So VLACP between 4.1.0.0 and 4.0.0.0 isn't compatable you found?  Humm.  Interesting.  Have to keep that in mind and poke at it in a lab at some point.

Thanks for the heads-up!

Offline telecom116

  • Sr. Member
  • ****
  • Posts: 217
Re: Heads up with minor bug in 4.0.0.x
« Reply #2 on: March 25, 2015, 05:43:45 PM »
So is the MacSec or the VLACP causing the issue?  I'm running 2 VSP4850s adjacent to each other with one running 4.0.0.2 and the other 4.1.0.0 without issues, but not running either MacSec or VLACP on the link between the two.

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1564
    • Networkautobahn
Re: Heads up with minor bug in 4.0.0.x
« Reply #3 on: March 26, 2015, 02:40:37 AM »
I had a similar problem with the VSP8k. In my case I had to reconfigure the vlacp timers from short to long to get back the connectivity. It looks like that the problem only shows up in the combination of vlacp und spbm.

Thanks onikolaison for sharing the information.

Cheers
It´s always the networks fault!
networkautobahn.com