• September 19, 2020, 10:29:03 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Software Release 5.8.1.301 s for the ERS4800  (Read 1904 times)

0 Members and 1 Guest are viewing this topic.

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1564
    • Networkautobahn
Software Release 5.8.1.301 s for the ERS4800
« on: July 06, 2015, 04:41:59 AM »
Hi,

I stumbled recently at a bug taht is present in all ERS4800 SW releaeses prior to 5.8.1.301s.

You can find a bug discription here on my blog:
http://networkautobahn.com/2015/06/23/10-days-of-troubleshooting/

The SW 5.8.1.301s contains only one bugfix for the specific bug that I discovered recently:
wi01225337
–ERS 4850 v5.8.1: After adding 30 more SPB nodes to the network, high CPU utilization was
observed on the newly added nodes and the end devices were intermittently not reachable. The root cause for this behavior was a defect in the code where multicast entries populating the FIB were not properly programmed when the number of SPB nodes and common I-SIDs were large enough.


You can find the release notes here:
https://downloads.avaya.com/css/P8/documents/101012182

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


Offline Řyvind Nikolaisen

  • Full Member
  • ***
  • Posts: 52
Re: Software Release 5.8.1.301 s for the ERS4800
« Reply #1 on: July 10, 2015, 02:43:28 AM »
I have also gotten some information that it also relates to the number of i-sids on the 4850. The behaviour has been reported in an 80-node spbd network with 20+ i-sids on the 4850s.


Brgds
Řyvind
Best regards,

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

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1564
    • Networkautobahn
Re: Software Release 5.8.1.301 s for the ERS4800
« Reply #2 on: July 10, 2015, 05:17:29 AM »
Actually the number of configured I-SIDS and the number of ative ISIS/SPB notes are both relevant.
Both factors will produce more CPU utilization when the ISIS adjancencies is formed up with larger numbers.
General a high CPU utilization for e few minutes should also be no problem , but in the mement the CPU spike is longer as the ISIS hello interval (wich is 3 minutes in default) you end up in a endless ISIS Link Flapping.
VLACP can also be a problem here.

I heared from the Avaya support that they will change the tests that are done before the release lunch to cover this scaling issues.

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