Michael McNamara

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!