Nortel has released software 5.1.1.1 for the Ethernet Routing Switch 8600. Here some highlights from the release notes;
- Previously certain IST message handling could be delayed by other system functions, thereby potentially causing IST instability (up/down/up). As well, system instability associated with SMLT (IST Peers) in association with high CPU utilization and potentially SLPP operations have both now been resolved. For those who disabled SLPP on their systems/network, SLPP can now be re-enabled with the 5.1.1.1 release. (Q02055292-02/Q02053200/Q02055101/Q02066500)
- Static routes usage in a VRF configured system for non-default VRFs (non-VRF 0 usage) will no longer cause a spike in CPU utilization. Now even after reboot all the static routes will remain active and CPU utilization will remain normal. This situation was introduced in 5.1.1.0 code, so only applies to that specific release. (Q02060978-03)
- Previously unicast traffic could be flooded with the VLAN when some SMLT/RSMLT associated link failed; this is now resolved. (Q02037171)
There were two additional items of interest in the release notes that were included under the “Important Notes” section. The first reference the configuration of the system-monitor flag, it should be set in the enabled position and can only be set via SNMP by Nortel’s Java Device Manager (JDM) or by sending the proper SNMP command. The second item referenced a possible crash of the SNMP task within the 8600 software if the retry value for SNMP trap hosts was set greater than 0. I would suggest everyone reference the release notes for additinoal information on both of those items.
You can find the complete release notes here.
Cheers!
This looks like a scary upgrade.
I performed the upgrade this afternoon in my lab and it was pretty straight forward. I did find the system-monitor flag set to false (disabled) on both of the ERS8600 switches in my testlab so I needed to enable that flag (via Device Manager) and reboot each switch before I performed the actual software upgrade.
In production rebooting twice could be a pain for those sites where uptime is a 24x7x365 requirement.
Nice!
Well you should be able to walk into a upgrade now a days.
FYI to anybody who:
1)may be listening
2)is considering upgrading to (or initially implementing) release 5.1.1.1, AND
3)relies on the ERS8600 for RIP and/or RIPv2
I have an open support case, that will likely be further escalated shortly, relating to what appears to be an inability to correctly receive RIP updates and then use those to populate and maintain the routing table. I’ve worked for several hours with my SE (in addition to with GNTS) and we are both fairly convinced that this a bug instead of a configuration error. Feel free to email me directly and I’ll be happy to share more detail if you are interested.
Hi Mike,
Thanks for sharing… we’re always interested!
I’ll be honest in saying that I don’t personally use RIPv1 or RIPv2 anymore but I’m sure there are many folks here that would be interested in hearing more about the problem.
Perhaps you could start a topic over on the forums?
http://forums.networkinfrastructure.info/nortel-ethernet-switching/
Thanks!
see my previous post….I forgot to list my address
[Moderator removed email address]
Are you sure you what to post your email address? We could start a topic over on the forums?
http://forums.networkinfrastructure.info/nortel-ethernet-switching/
Let me know and I can “prune” your email address from your reply.l
Cheers!
Mike,
I’ll cut and paste my first post into a topic on the forum. It looks like others are already experiencing plenty with the 5.1.x stream, so I’ll be adding to the list. And, sure, go ahead and edit out my post with the email address.
thanks. Mike.