5500 6.1.6 upgrade issues

[telecom116]

Anyone having problems with upgrades from 6.1.4 to 6.1.6, using  the secure code?  I have managed to blow up two switches with continuous reboots and Data Access Exception errors after the upgrade.  I have had a ticket open for a couple of weeks and Avaya has been able to duplicate the problem, but no resolution as of now.

[Dominik]

Hi telecome116,

I updated recently a few ERS5xxx switches from 6.1.1 to 6.1.6. Worked without any issues in my case.

When does the error start ?
Do you where able to complete the DIAG update ?
Does your switches hang on the Bootloader ?

Can you plaese provide the output that you get on the console.

bye

[telecom116]

- Diagnostics has been updated to current version;
- Error starts after Decompressing the Image

Test 212  Internal Loopback          - PASSED
 Press Esc to Enter Diag
Run Agent 2 Ver:6.1.6.019
Decompressing the image   
done.
Target Name: tgt
User: target
Attaching interface lo0... done
Code Segment 0x100000 -- 0xf23fff protection=2

Initializing ......
Broadcom Command Monitor: Copyright (c) 1998-2005 Broadcom Corporation

======================
Data Access Exception
======================

Error: could not write exception info to i2c
Error: could not write exception info to i2c
Error: could not write exception info to i2c
...
Error: could not write exception info to i2c
Error: could not write exception info toĸõc

Booting...

Testing Memory...............................

Starting..

Ethernet Routing Switch 5520-48T-PWR

Hardware Rev :    8
...and repeat.

[Michael McNamara]

Have you tried factory resetting the switch (erasing the configuration)?

[qazzie]

I've seen the continous rebooting with 6.1.6 but not from the software code you had running.

Factory default en copy&paste the config in cli worked as a workaround.

[telecom116]

Unfortunately, I have 50-60 5500 switches, and quite a few of these are in isolated locations - like 600 miles from me, and each can be 1-2 hours from my closest technician.  Factory reset, therefore is NOT an option. 

I do also know another organization that had issues with an upgrade last week.  Hopefully between the two of us we will get some traction at Avaya.

[qazzie]

Question is more that you've some serious urge to upgrade from 6.1.4 to 6.1.6?

Feels like you ate a large bug. As I'm feeling you on your situation, I'm a little curious why you have that upgrade urge?
Sry we can't help.

[telecom116]

Primarily because of this issue that Nortel told me years ago was not going to be fixed. It's nice having your local file servers and desktop Gig ports running at 10 Mbps; mostly saw this with Intel chipsets.

After a reboot, some client ports with active connections would autonegotiate to a lower speed (10/100) than expected (1000).This issue affected some Intel 82556 and Broadcom NICs (wi00555121).

[Flintstone]

Hi,

I believe there is a work around for your autonegotiate issues?

You can force the port to only autonegotiate using 1000.  You can disable 10/100 from the autonegotiation process?

CheerZ

[svl0r]

A bug has been found. If a pre 6.x config has been build, you upgrade from any 6.x to 6.1.6 will fail. This has been scheduled to be fixed in 6.1.7 (Q3/4).

[Dominik]

I could replicate the error on one of my ERS5520.
I also found that the CLI Pasword doesnīt worked after the upgrade.

Here are my test steps:
Update from 5.0 to 6.0
Update from 6.0 to 6.1.6
>>> switch endless reboots.
>>> Downgrade to release 6.1.5 from DIAG.

Old config was still working, only the CLI password doesnīt work on 6.1.5.

In fact of this issue AVAYA should remove 6.1.6 from their homepage or make at least a comment in the release notes.

[svl0r]

If you rebuild the config on 6.x then the upgrade will work.

[Michael McNamara]

I'm going to sticky this thread... so unless you're deploying a new switch (or prepared to rebuild the configuration from factory defaults) you should avoid upgrading to 6.1.6 software.

Cheers!

[telecom116]

I just heard from Avaya support and that the cause appears to be a wrong pointer passed to VLACP code.

At this point I'm standing firm with the 6.1.4 code I have until this is worked out.

[telecom116]

In fact of this issue AVAYA should remove 6.1.6 from their homepage or make at least a comment in the release notes.

That is a very good question, since Avaya has been very proactive in pulling 8600/8800 code that have issues;  the 6.1.6 code is still available on the website.  I'd rather see them pull it since it appears to not have a lot of fixes.  They'll have much more bad reaction by leaving it out there, even though some people have not had issues.

I sure hope that the fixed code would be sooner than the Q3/Q4 stated later in the thread.