technology, networking and IP telephony
Posts tagged SOFTWARE RELEASE
Ethernet Routing Switch 5000 Software Release v6.2.0.200
Aug 20th
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).
ARPs would timeout in certain scenarios only when using 5520/5530 devices in stacks as IST peers and when connected through SLT (not SMLT) to edge devices. - Power is cut off when AES is deactivated (Q02146930)
Please review the release notes for all the specific details.
We recently had a discussion regarding why Avaya released 6.1.4 software after releasing 6.2.0. This is a perfect example of why you don’t rush into major software releases unless you’re prepared to bleed alittle. I wonder how they came up with the phrase bleeding edge? This isn’t just an issue with Avaya either, I’ve see it with every vendor I’ve ever worked with including Cisco, Juniper, Blue Coat, etc. Now it’s definitely true that some vendors are much better than others in both their software development and their QA testing but there are always going to be some issues.
Cheers!
Ethernet Routing Switch 5000 Software Release v6.1.4
Aug 16th
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!
SIP Software Release 3.0 for IP Deskphones
Aug 16th
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 Login, Emergency Services support, USB device support, Wide-band Codec, Provisioning and Licensing.
The SIP software Release 3.0 for IP Deskphones also continues to improve the overall quality of the IP Deskphone software through the delivery of ongoing resolution of CRs. Numerous quality improvements have been delivered and 9 customer cases have been closed in SIP 3.0.
I’ve only performed very limited SIP testing with the 1120E, 1140E, and 1220 IP phones in non-production environments. I did notice a few feature called “Multi-user Login” which allows a SIP IP phone to connect to multiple SIP servers at the same time. Here’s the blurb from Avaya on the feature (it’s a direct quote from the release notes);
Multi-user Login
The Multiuser feature in SIP Release 3.0 allows multiple SIP user accounts to be in use on the IP Deskphone at the same time. Multiple users, each with their own account, can share a single IP Deskphone allowing each user to receive calls without logging off other users. One user can have multiple user accounts (for example, a work account and a personal account) active at the same time on the same IP Deskphone. You can register each account to a different server, and for each account, the IP Deskphone exposes the functionality available to that account. One account is considered a primary account and is used by default for most IP Deskphone operations. Each account is associated to a line key; the primary account is always on the bottom right line key of the IP Deskphone (this is the first key, Key 01), and an arbitrary key (including a key on an Expansion Module) can be selected for additional accounts.
The following operations are supported:
- Start dialing
- Place a call using the corresponding user account
- Answer an incoming call targeted to that account
- Initiate a call without pressing a line key (for example, by dialing digits at the idle screen and lifting the handset) uses the primary account.
A running IP Deskphone is associated to a single profile that represents one configuration of the IP Deskphone with all relevant persistent data such as preferences and call logs. A different profile is associated to each account used as a primary account. The IP Deskphone can store up to five different profiles; the IP Deskphone takes data from the profile associated to the current primary account. A number of configurations are independent of profiles and tied directly to an account making them available to that account regardless of the primary account you use (for example, voice mail ID).
The IP Deskphone receives and answers calls targeted at any of the registered accounts; the incoming call screen indicates who the call is for. You can place an outgoing call using any of the accounts; the account that you use is displayed on the dialing screen. When a call is active, information from both local and remote parties appear on the screen.
Regardless of which account receives the call, incoming call logs, outgoing call logs, and instant messages appear in a single list. The IP Deskphone indicates the local user in the detailed view of the entry.
Some features are only available to the primary account, such as instant messaging, retrieving parked calls by token, and establishing ad-hoc conference calls.
Please refer to the product bulletin and the release notes for all the details.
Cheers!
Ethernet Routing Switch 8600 Software Release v5.1.3.0
Aug 12th
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)
- The egress queue service rates configured in NNCLI mode were previously getting lost after a reboot. The egress queue service rates configured are now retained after a reboot. (Q02116358)
- In NNCLI mode “show qos egress-queue-set <queue-set-id>” command was showing no output. ERS 8600 now displays the proper output on executing this command. (Q02116618)
- Initiating a traceroute via JDM to an unknown destination while other ping or traceroute activities were being performed simultaneously from the same switch could potentially lead to system instability. This has been corrected. (Q02137566)
Platform
- In specific scenarios with filters and port mirroring being used simultaneously, the ERS8600 will no longer see an increase in CPU utilization due to packets being sent to the CP/SF incorrectly. (Q02141867)
- In some specific ACL configurations with a default-action specified, the ERS8600 previously blocked certain traffic patterns improperly. The issue has been addressed. (Q02068243)
- Previously links on an R-module could stay up for 60 seconds when the primary SF/CPU (of a dual non-HA SF/CPU configuration only) was not properly removed (module pulled out without prior master reset or switchover). The ERS 8600 now ensures that the links are brought down immediately when the primary SF/CPU is removed for this configuration. (Q02102654)
- The radius secret key will now be stored as encrypted in the shadov.txt file. Before upgrading to 5.1.3.0, it is now required of the user to delete the radius secret key and then re-add it after the up-grade is complete to avoid accessibility problem with RADIUS. This situation has already been addressed in 7.0.0.0 code release. (Q01881817-03)
- When multiple failovers are performed on an ERS 8600 in HA environments, some R module I/O modules could come back up off-line. This situation is now addressed in the 5.1.3.0 code release but also requires the use of the new updated DPC FPGA image (see File Names section). Associated with this 5.1.3.0 Release, the DPC firmware image must be upgraded for all R-module I/O modules to the dpc194.xsvf firmware image. If the firmware image is not upgraded, the user will receive a warning log message upon any re-boot of 5.1.3.0 code release, warning them that DPC FPGA firmware image is out of revision. (Q02053766-01)
- On E/M module cards, receiving 802.3x pause frames on gigabit Ethernet ports could previously result in port level resets. (Q02101087)
- For an ERS 8600 running with 8692 SF/CPU with SuperMezz, the SuperMezz physical LED will now display properly. (Q02102364)
- During boot-up, the potential for 8612XLRS 10Gig port flapping will no longer occur. (Q02138423)
- An error in loading configuration file previously resulted in all of the line cards being disabled. This behavior was added in 5.1 code. This behavior is now changed such that the rest of the correct config will be loaded and all the remaining line cards will not be disabled, but only the line card associated with the improper configuration will be disabled. This situation is different than an “invalid config file, with verify-config flag enabled”, in which case the system will not load the config and will bring up the system with all I/O modules disabled (versus loading the default config). This situation has already been addressed in 7.0.0.0 code release. (Q02056382-01)
- A power usage calculation error has been corrected for 8648TXE and 8691SF cards which previously lead to improper warnings being generated in some configurations indicating that the chassis was running on low power. (Q02072016)
- The value of the ingress records was showing improper values via the command show ip mroute-hw resource usage. This has been now been addressed and the proper values for these records are now displayed. (Q02120442)
- The software power tables embedded in the ERS 8600 were out of sync with the Power Supply Calculator posted via the web. This inconsistency has now been addressed. This issue has already been addressed in 7.0.0.0 code release. (Q02020261-01)
RSTP/MSTP
- An outage of 30sec has been observed in some RSTP setups when one of the root ports was disabled. This issue has now been addressed and the ERS 8600 re-converges within the proper time interval. (Q01984762-02)
- In RSTP mode, the log file transfer feature was not working properly. This issue has been addressed and the log file transfer feature is now working as expected when RSTP mode is enabled. (Q02101565-01)
IP Unicast
BGP
- In a specific aggregation scenario, when an ERS 8600 forms a neighbour relationship with Cisco, the BGP session will no longer go down due to a malformed AS path. (Q02085844-01)
- During some specific BGP transition scenarios, system instability was previously seen for the ERS 8600. This issue is now addressed. (Q02134841)
- BGP instabilities are no longer observed associated with a HA failover. (Q02135118)
- After an HA failover with a BGP route policy enabled, some BGP routes could be rejected and not re-advertised by the ERS 8600. This issue has been addressed. (Q02136224)
OSPF
- After an upgrade it is now ensured that the OSPF MD5 keys are no longer lost. (Q02127996)
VRRP
- Enabling and then disabling the IST protocol will no longer lead to improper values displayed in the VRRP records. (Q02106080-01)
IP Multicast
- ERS 8600 now ensures that when an IP Multicast sender and the receiver are connected to the same ERS 8600, that SPM (Source Path Messages – specific message type within PGM) packets are no longer dropped. This is independent of PGM being enabled or not, as PGM packet flows can function with PIM-SM enabled. (Q02119454)
MLT / SMLT
- ERS8600 will now deterministically (and properly) hash traffic flows for IPVPN Lite traffic on MLT links. (Q02142913)
- MLTs will now come up properly when the LACP Min Link feature is enabled. (Q02034692-02)
- In some rare network events, it is possible to learn the fdb-entry for an IP interface of an SMLT peer on the SMLT associated port instead of the IST MLT. In this scenario, the fdb-entry will now be properly updated afterward to correctly point to the IST MLT. (Q02142730)
- CPU high buffer utilization and associated IST instabilities will no longer be observed in specific high CPU and high traffic load conditions for the ERS 8600. (Q02109963)
- The 8632TXE module will now properly go offline in the scenario where both master and slave CPU’s are removed in systems running with smlt-on-single-cp enabled. (Q02123052)
VLACP
- If a mismatching VLACP configuration exists on two ends of a connection associated with a SLT, the SLT will no longer show as SMLT up improperly after a reboot. (Q02119095)
BFD
- On an ERS8600 running both BGP and BFD, when one tries to enable BGP first and then BFD on the BGP neighbour, the BFD related config can now be set properly. (Q02141063)
Cheers!
Loading ...
RECENT COMMENTS