Avaya has released software 6.1.4.0 for the Ethernet Routing Switch 5500/5600 series switch.
New Features
- Ability to set password, username and type of security for any switch in stack (Q02132910, Q02143365)
The 6.1.4 release includes the ability to set password, username and type of authentication for any switch in stack. I can’t really see (right now) how this would be a feature in great demand but I’m sure someone out there will enlighten me! ;)
Problems Resolved
- Base unit crashed with data exception in PP task (Q02119687)
- Invalid binding entries via DHCP engineering menu caused fluctuations in the binding table within seconds.(Q02143834).
- IGMP reports received from Client with TTL greater than 1 were forwarded and when an ERS 8600 connected to an ERS 5520 received the IGMP report with TTL set any value but 1, it dropped the packet (Q02141971)
- Problems changing switch passwords (Q02132910).
- Custom user password profiles were not consistently applied to all units in the stack (Q02143365)
- TACACS authentication caused an exception (Q02126732)
- In a Triangular IST/SMLT environment, with ERS 8300 as core and ERS 5520 as edge switches, with ARP Inspection enabled, the edge switches lost Arp entry for its default gateway and thus the gateway was no longer reachable. (Q02153086)
- Under certain conditions, broadcast traffic looped into the stack could generate a broadcast storm (Q02162104).
Known Issues
- CLI password type for switch is changing from TACACS to Local when we change software image (wi00557586)
This issue happens only when the authentication type for switch is set to TACACS.
Workaround: Remove the switch settings for authentication type before downloading the new software.
- Password security goes from enable to disable when upgrade/downgrade (wi00557570).
When upgrading from 6.1.4 to 6.2.0, if the password security is enabled, it will become disabled after upgrade. This issue will be fixed with 6.2.1 release. When downgrading from 6.1.4 release to a 6.1.x release, if the password security is enabled, it will become disabled.
Workaround: Enable password security.
You can find the complete release notes here.
Cheers!
Micheal, why does Nortel/Avaya release a v6.2, then weeks later release a v6.1.4??
Makes customers think whether or not they shouldve upgraded in the first place.
Hi Wayne,
Nortel/Avaya maintains multiple code branches/trees for good reason. This is done to help maintain a stable software code base while still allowing the developers to release new features which can be worked into the stable software code base over time.
I’m very happy with the approach that Nortel/Avaya has taken with respect to their software releases. It allows users to test out new software releases (if those features are needed) yet they continue to maintain the older stable release with patches and fixes.
Why did you upgrade? Hopefully you’re not just upgrading for the sake of upgrading.
The vast majority of my network is still running 5.1.x software on the ERS 5000 series switches. I’ve only recently started deploying 6.1.x in new installations and really only to take advantage of some new features and fixes (Jumbo Frames, LLDP-MED, ADAC, etc)
You might not realize that 6.0 software was released in December 2008, almost 2 years ago, so the code has had a lot of time to mature. The 6.1 software was released in June 2009, more than a year ago now.
It may also be that the fixes introduced in 6.1.4 were already a part of 6.2 or might be coming down the road in the form of 6.2.1. So I don’t believe there’s any real reason to be concerned or alarmed.
I wouldn’t advise you to blast out 6.2 within your organization unless you’ve done a serious amount of testing, even if you need some of the new features you should still be prepared to suffer being on the bleeding edge.
Cheers!
Wayne,
6.2 is a new folk of code that adds a web-based device manager instead of java device manager. This would make this folk an unstable release.
6.1 is still supporting java device manager and is stable code.
Nortel has weird release cycles. Hopefully Avaya will fix this and standardize the release cycle.
I would welcome a standardized release cycle/schedule but as this point I’m happy (delighted) to see that Avaya is continuing to improve the product and issues are being resolved even if the schedule is somewhat erratic.
It still would be nice to have a clear note saying this is unstable and this is a stable release. No point to have us guess what’s good and what’s not. I’m lucky to have a test system to mess around with code. But for others they don’t have that.
Well that knowledge comes from experience… while some vendors are better than others you always need to be cautious of any major release. Look at Microsoft’s Windows Vista for a relevant example. There were quite a few issues with Windows Vista until Service Pack 2 came along.
Also, I’m using the word “stable” to communicate the impression that a specific software release has a significant amount of run-time under it’s belt with very few unknown and/or open issues. I’m sure that many folks will find the 6.2 release to be stable but there are hugely different requirements in say an academic student lab network and a hospital intensive care unit telemetry network. It’s one thing to have an issue in a student lab, it’s a complete different thing to potentially interrupt life-saving patient care.
Cheers!
Thanks guys. We upgraded to 6.2 to take advantage of the increased amount of multicast groups supported for the 5520-24T-PWR to 492.
So far we have only found 1 issue in v6.2 which is allowing mutlicast packets to ingress through a blocked RSTP port causing a broadcast loop
That’s a highly specific problem but a great example of issues that can sneak into major releases… how long did it take you to track that down? Nice find!
If you have the time and don’t mind, please keep us updated.
Cheers!
Michael, Nortel were able to replicate the problem we found which is good. Patch may come out with v6.2.1 or a separate release.
6.2.1 may fix your issue.