Login fails after upgrade ERS4500 to agent 5.5

[Johan Witters]

Hello,

I've run into an issue with upgrading stand-alone units to agent version 5.5: after the upgrade I'm unable to log on to the box. Units in a stack do not have this issue.

As far as I've been able to track the issue, Avaya has abandoned the "cli password switch/stack serial/telnet" command in favour of "cli password telnet/serial...". Units in a stack are automatically altered to use the new authentication mechanism, but apparently the single units not.

Until now I've not been able to solve the issue without factory resetting the box.

Did anyone else experience these issue?


Thanks,

Johan

[Flintstone]

Hi Johan,

I have also seen the same problem:

http://forums.networkinfrastructure.info/nortel-ethernet-switching/edm-performance-on-new-sw5-5-for-the-ers-4500-switches/

I was able to login using the default passwords?

CheerZ

[Johan Witters]

Flintstone,

I used all "default" passwords Nortel has used throughout the years, but untill now I haven't been able to get in the box.

Strange thing is that it only seems to be happening on 4550's.. I also upgraded some 4526's, after the upgrade I could access these machines without user/password through EDM/telnet..

Avaya techsupport is investigating the issue at the moment.


Johan

[Flintstone]

Hi Johan,

I had SSH enabled and was able to get in using 'secure' for user 'RW'?
The configuration docs state that the password for the SSH software image should be 'securepasswd', but in my case was 'secure'? 

Default password and default password security
For the non-SSH image, the default password for RO is user and secure for RW. For the SSH
software image, the default password for RO is userpasswd and securepasswd for RW.

I had the same thing as you also with web access.  I just set the passwords up again and everything went back to normal.

CheerZ

[Johan Witters]

No luck logging in, I even tried the SSH password..

If Avaya would only have added the possibility to backup the ascii config through EDM/DM, like on the 5500. In that case I would have been able to backup the config through DM to see what's in the config after the upgrade..

I't will be factory reset I'm afraid..

[Johan Witters]

I have some more info on the issue:

- stacks are not affected.
- standalone units with diag 5.3.0.3 running before the upgrade of the agent have issues
- standalone units with diag 5.1.0.8 running before the upgrade of the agent loose authentication settings and are accessible without logging in...

[robbiebrown34]

Morning All,

I too had the same issue with a switch I upgraded on Friday.
Does anyone know of or have any documentation from Avaya regarding this issue? Is there any workaround?

I have a customer with 3 sites, 9 switches in total that all need to be upgraded and ideally could do with some form of plan.

Thanks

[Dominik]

If the SNMP communitys are not effected, you can send a script with tftp and configure a password with the new CLI command.
So long SNMP works you can always get a new password on your Avaya switch.

Your script should look like this:

!
enable
configure terminal
!
username USERNAME PASSWORD rw
!
exit
exit

Good Luck

[Johan Witters]

The issue is still under investigation at Avaya support.....

Apparently they have problems replicating the behaviour.

[robbiebrown34]

Dominik,

Thanks for that - Just tried it on the switch I upgraded Friday - Works a treat.

Hopefully the other sites will go OK.

Shame to hear Avaya are struggling to replicate the issue - I have no problem sending them my configuration for them to copy and test. Lets see what they come back with - I am checking the support site daily.

Thanks for your help.

[KT]

Always something! I did not have any issues after upgraded ERS4500 to 5.5 couple of wks ago. But i saw some ODD or Bogus when you cml of "show run". I'll post it next time.

Thanks, KT

[Dominik]

@KT

I found something in the known issue section of the SW 5.5 release notes:

wi00484096
show running-config: When you execute the show runningconfig
or show running-config module commands the
system may take a longer time than expected to display the output.
In systems with very large and complex configurations of 8 units in a
stack it can take up to 4 minutes to complete the display of the
command. This is considered normal behavior.

They also started to do it like Cisco and show only the div of the default config.

Cheers