Avaya has released software 5.5 for the Ethernet Routing Switch 4500 series switch.

• 802.1AB customization
• 802.1AB integration
• 802.1X non-EAP Accounting
• 802.1X non-EAP re-authentication
• 802.1AB new default parameters
• AUR enhancement
• DHCP Snooping External Save
• EAP Fail Open with multi-VLAN
• Layer 3 Virtual Router Redundancy Protocol
• RADIUS EAP or non-EAP requests from different servers
• SLPP Guard
• SNMP Trap enhancements
• STP BPDU filtering ignore-self
• Unified Authentication
• VLACP enhancements
• Enterprise Device Manager enhancements
• Web server client browser requests

The known issues and resolved issues are mysteriously blank although there is a note there that indicates those sections will be updated on May 20, 2011.

Please refer to the release notes for all the specific details and tidbits.

It appears that Avaya is trying to address the performance issues with EDM that many of us have documented;

Enterprise Device Manager enhancements

In Release 5.5 Enterprise Device Manager (EDM) is enhanced with improved data retrieval and request handling for significantly faster GUI response. In the navigation tree the IP Routing folder is renamed IP and the paths in related procedures have been updated. The Switch Summary tab contents have been enhanced to include basic switch information and stack information. A toolbar has been added above the EDM navigation tree. The 5 buttons in the toolbar add the following functions:

• Switch Summary — you can use the Switch Summary toolbar button to open or reopen the switch summary tab.
• Refresh Status — in addition to the existing refresh methods you can use the Refresh Status toolbar button to refresh the device status.
• Edit Selected — in addition to the existing edit methods, and depending on which object you select on the Device Physical View, you can use this toolbar button to open Edit > Chassis, Edit > Unit, or Edit > Ports tabs. If you do not select an object from the Device Physical View and you click the Edit Select toolbar button, the Edit > Chassis tab opens.
• Graph Selected — depending on which object you select on the Device Physical View, you can use this toolbar button to open Graph > Chassis or Graph > Port tabs. If you do not make a selection on the Device Physical View, or if you select Unit, the Graph > Chassis tab opens.
• Help Setup Guide — this button connects you to the help setup guide for embedded EDM and it replaces the link that appeared on the top right of work panes.

Cheers!

Avaya has released software v5.1.5.1 for the Ethernet Routing Switch 8600. It should be noted that Avaya has pulled software release 5.1.5.0 from their website. The release notes indicate that the reason for this was “a datapath issue has been identified that may impact the ability to learn MAC addresses and forward packets for which the source MAC address is unknown. This will only happen if the traffic enters the same LANE as the IST is located on and if the IST occupies the first port in the LANE. Also, this is only seen on card types 8630GBR, 8648GBRS, 8634XGRS and 8612XLRS. (wi00866354)”.

Cheers!

Avaya has released software 6.1.6 for the Ethernet Routing Switch 5500/5600 series switches.

The following issues have been resolved with this software release;

• The dhcp-relay agent changed the MAC destination address of acknowledgments from a unicast address to a multicast address (wi00835598).
• 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).

I’ve personally seen issue wi00555121 above while working with a large HP MAS (Medical Archive Solution) implementation. I also believe that someone (either on this blog or in the discussion forums) also brought up issue wi00835598.

The new feature includes VLACP enhancements with support for DOWN and HOLD subtypes which were introduced in 5.1.4.0 software for the Ethernet Routing Switch 8600. The goal of the new VLACP subtypes it to provide a means to allow the core ample time to get up to speed before the edge starts forwarding traffic. I’ve personally seen many an occasion where one Ethernet Routing Switch 8600 in a cluster goes down with minimal packet loss but upon recovery there are all sorts of packet loss and network interruption. This new feature is designed to mitigate that problem by allowing link to come up… VLACP to come active but hold the actual network traffic back until the core is ready to start bridging/routing packets.

VLACP Enhancements – support for DOWN and HOLD subtypes

The VLACP implementation prior to this release did not detect a unidirectional communication outage. A VLACP partner will now send VLACP PDUs with the subtype DOWN (value of 2) when no PDUs are received from its link partner. These PDUs indicate the remote VLACP partner is down and the link partner should logically bring down its port. Shortly after reboot, a VLACP partner will send PDUs with the subtype HOLD (value of 3) to its link partner. In this case, receiving a PDU with subtype HOLD indicates the VLACP partner should logically bring down its port for a VLACP hold time. When receiving VLACP PDUs with HOLD or DOWN subtypes, the VLACP partner will respond with normal PDUs (LACP subtype). The interval between PDUs is configurable by the user. The VLACP support for HOLD subtype is disabled by default, it will be enabled only when a positive value for VLACP HOLD Time is configured. VLACP is an Avaya proprietary protocol and hence this enhancement will not work when connecting to devices from other vendors.

You’ll recall from the Ethernet Routing Switch 8600 5.1.4.0 release notes that Avaya introduce a new VLACP subtype on the core side;

VLACP HOLD Enhancement

During SMLT node failure scenarios, traffic loss may be observed in certain scaled SMLT configurations with hundreds of SLTs, hundreds of ports and tens of VLANs. The root cause for the traffic loss was that the ERS8600 ports would come up prematurely at the physical layer causing the remote end to start sending traffic toward the ERS8600 that just came up. On the ERS8600 that just rebooted, the communication between the line cards and the CP may take several seconds in such scaled configurations. This resulted in black-holing the traffic arriving on such ports which were physically up but all operational configuration was not yet performed on those ports by the CP. The VLACP SUBTYPE HOLD feature introduces a new VLACP PDU with a new subtype HOLD to help reduce traffic loss in such scenarios.
The goal of this new implementation is to “hold down” all VLACP enabled links for a specific period of time after a reboot. This prevents remote VLACP enabled devices that understand the new VLACP HOLD PDU from sending data to the ERS8600. This will ensure that all VLACP enabled ports on the ERS8600 have had sufficient time to come up with all operational configuration and are ready to receive and forward the ingress traffic.
ERS8600 switches with 5.1.4.0 release are capable of both sending and receiving VLACP HOLD PDUs. Future code revisions of the Baystack switch family will support receipt and processing of VLACP HOLD PDUs, but will not generate them. Please refer to the applicable product release notes for information regarding product specific software levels required for support of this VLACP enhancement. VLACP is an Avaya proprietary protocol and hence this enhancement in not applicable when connecting to switches from other vendors.
By default, the VLACP HOLD feature will be disabled. The feature is enabled by configuring a positive value for VLACP HOLD Time. The VLACP Hold Time value configured should be selected based on the specific recovery implementation requirements, size and recovery characteristics for your network implementation.

You can find the release notes here. (I’m going to try linking to Avaya’s support website instead of hosting the files myself).

Cheers!