about 1 week ago - 3 comments
Avaya has released software 6.2.0.200/201 for the Ethernet Routing Switch 5500/5600 series switches. The following issues were identified and resolved in this release; SMLT – IST/SMLTs may bounce every 2-3 hours (Q02161349) Issue was present on 56XX devices when used as IST peers. Issue not present on 55XX devices. ERS5600 vt6.2-trials: ARP table timeout (Q02162399).
about 2 weeks ago - 11 comments
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
about 2 weeks ago - No comments
Avaya has released SIP software release 3.0 for their 1120E and 1140E IP deskphones. (There was no mention of the 1110E, 1150E, 1165E or 1200 series IP phones in any of the accompanying material). Several enhancements have been included in SIP Release 3.0 for the 1100 series phones including User Interface and Preferences enhancements, Multi-user
about 3 weeks ago - No comments
Avaya has released v5.1.3.0 software for the Ethernet Routing Switch 8600. Please review the release notes for all the resolved issues, known issues and known limitations. Switch management The command “show ports stats show-all” was previously not displaying all of the associated port statistics information. The ERS 8600 now will display the proper information. (Q02012952-01)
about 1 month ago - 12 comments
Avaya has released software 6.2.0 for the Ethernet Routing Switch 5500/5600 series switches. In order to upgrade to 6.2 software the switch will already need to be running 6.x software along with firmware (diagnostic software) 6.0.0.6. Switches that are running older software will need to first be upgraded to 6.0 and then to 6.2 software.
about 1 month ago - 2 comments
Avaya has released software 3.7.5 for the Ethernet Switch 460 and 470 switch models. While there were no new features added but there were a number of bug fixes; The status of the stack ports are now correctly displayed when interrogating the MIB for the stack (Q02082410) If MAC addresses are quickly aged out of
about 3 months ago - 6 comments
Avaya has released software 5.4 for the Ethernet Routing Switch 4500 series switch. New features; 802.1AB (LLDP) MED Network Policy CLI 802.1D Compliancy Support ADAC and Auto QoS Interoperability ADAC Enhancements Additional SFP Support Automatic QoS and 802.1AB MED Interoperability DHCP Client DHCP Option 82 Support DHCP Snooping Improvements Dual Syslog Server Support Dynamic Route
about 3 months ago - No comments
Avaya has released software 6.1.3.0 for the Ethernet Routing Switch 5500/5600 series switch. New Features Stack Health Monitoring and Recovery Modify 802.1ab detection mechanism in ADAC to ensure full compatibility with the Avaya IP handsets (Q02109202). Problems Resolved After upgrading from 6.0 to 6.1, interface names for the non-base unit were lost (Q02024643, Q02019044) Using
about 4 months ago - No comments
Avaya has released 2.1.8.0 software for the Ethernet Routing Switch 1600 series. This release is significant in that it adds three previously missing features; VLACP SLPP ECMP The Ethernet Routing Switch 1600 series also supports IST/SMLT configurations for use in small core designs. Until recently I had been using a large number of ERS 1648
about 4 months ago - 3 comments
Avaya has released software 7.0 for the Ethernet Routing Switch 8600. Almost four months in controlled availability (CA) Avaya has finally moved the software release to general availability (GA). As I mentioned last week, although I can’t remember where I mentioned it now – either here or over on the discussion forums, Avaya is re-branding
Loading ...
about 10 months ago
I think this refers to the fact that, with older software versions, you could turn on VLACP at the edge and not lose connectivity before it was turned on at the core/distribution layer. I know with the 4500 series, once you turn it on at the edge, traffic stops till VLACP is up downstream as well. My guess is this is what will happen now with the 470s and 3.7.4
about 10 months ago
Hi Jeremy,
I believe your correct. I think the major change is that VLACP will immediately mark the port as down when it’s initially enabled both at the port and globally. The software won’t wait the retry time (500ms X 5 retries = 2.5 seconds) before declaring the port down as it did in the past. I have yet to test this but I believe this might have been the change they referenced. I’ve also noticed strange behavior if you enable VLACP at the port but forget to enable it globally.
Thanks for the comment!
about 10 months ago
There’s another possible VLACP change that this could be referencing–I haven’t verified this yet–it has to do with the MAC address utilized by VLACP.
In 5xxx pre-v5.1 and in 45xx pre 5.2 (I think this is where the change took place, so I’d encourage double-checking) the same mcast MAC address was recommended for use at VLACP global and at VLACP port level. This is, I’m almost certain, true for the 470 pre-v3.7.4
I’d guess that 470s at v3.7.4 will now behave like the 5xxx @ v5.1+ and 45xx @ v5.2+ : the recommended mcast MAC is now valid only for the global VLACP parameter. At the VLACP port level, the previously recommended mcast MAC is no longer permitted. You may, optionally, leave the port level MAC at all zeros or configure a unicast MAC. If you choose to leave it at all zeros, VLACP will establish a partnership with any other VLACP -enabled device at the far end of that port’s connection.
If you choose to configure a MAC address, it must match the system MAC of the VLACP -enabled device at the far end of that port’s connection in order for a partnership to be established. That means that if you have to replace the far end device, the near end port’s VLACP MAC address MUST be changed to reflect the new MAC of the far end device.