ERS3500 firmware upgrade 1

[IPGuru]

Does anyone have simple instructions for upgrading the firmware in ERS3500 series switch.
the ones we are getting do not support the run ipoffice command


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[tlpeter]

I never done it on the 3500 but once on the 2500 and you need two files.
I am only not sure which one needs to be done first.
Biv434 knows it best so have a little patience.


BAZINGA!

I'm not insane, my mother had me tested!

 

[VanZenden]

First you need to upgrade Diagnostic file and then SW Image file

ACIS-SME

 

[biv343]

Download the diag and firmware images and drop them on your TFTP server. From the CLI of the switch:

download address x.x.x.x diag 3500_1006_diag.bin (switch will download the diag image and reboot)

After its back online, enter this:

download address x.x.x.x image 3500_501006.img (switch will download the software image and reboot).

Not sure if 5.01.006 is the current firmware or not, but thats what I used when I put a pile of them in back in November.

There might be a way to do it via the web interface, but I've been working on these style switches since they were called Bay Networks , so I've always done them via CLI.

 

[VanZenden]

5.0.2 is the latest FW (30 Nov 2012)

https://support.avaya.com/downloads...30117233890_6&productId=P0998&releaseId=5.0.x

ACIS-SME

 

[biv343]

I was hoping that 5.1 would be out by now as that will introduce stacking capability. Of course 5.0.2 came out November 30, as the switches I put in went in the week before Thanksgiving. 5.0.1.6 has a nasty bug that causes the management interface (both telnet and web) to go out to lunch requiring a reboot to clear it. The release notes for 5.0.2 don't mention that was fixed, but it wouldn't be the first time Avaya left some details out of the release notes.

 

[jamie77]

Does this nasty bug you speak of also stop broadcast traffic. I have seen this a couple of times. It's ok after a power cycle.

Got caught in a big Avaya style loop trying to talk to someone about it!!!!

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[biv343]

It stops lots of things from what I've seen. Devices that are connected to the switch will continue to function, but if you plug in a new device you don't get a link light or anything. Very strange. Power cycling it fixes the problem for a day, week, or month. That gets old especially in an environment running two shifts and no way to access the switch remotely to cycle it.

I didn't even bother opening a support case with Avaya for the issue because I knew what the answer would be. I do need to get back to that customer and zap them up to 5.0.2 and see if it cures it. If not then I'll open a case and send logs and get put in the "wait for next release" queue.

Lots of folks on here bash Nortel, but their support for the data products was a lot better than the way Avaya handles it. I remember back when you'd call in an issue, get a real engineer on the phone working with you to figure out what was happening and get a new build in a day or two. Now it's logs, sniffer captures that show absolutely nothing relevant and waiting for days or weeks to get an answer.

Sorry for going off on that tangent.

 

[tlpeter]

Biv343, don't be sorry as this is how it is these days.
Avaya support used to be better too but somehow they kicked out some of the good people and there are not much left.


BAZINGA!

I'm not insane, my mother had me tested!