Avaya Inc. – Proprietary & Confidential.
Use pursuant to the terms of your signed agreement or Avaya policy.
10
IS upgrade download verification file.
Nortel_TPS_IS_Upgrade_4.5.0_to_4.5.1_
Upgrade-47.sh.md5
Trace files
MPLS trace file
Trace file for MPLS. This is auto generated and
appears on the PCMCIA after upgrade.
nbpdtrc.lo0 variable
NOTE:
dpc194.xsvf is a new DPC FPGA image for R-modules that can only be used with post 5.1.3GA
release. Do not use this DPC FPGA image with pre5.1.3 releases; it may result in R-modules not booting up
successfully and one may need RMA to get the card back in good state.
Version
of
Previous
Release
Software Versions
5.1.3, 5.1.2,
5.1.1.1
and
5.0.5.0.
Compatibility
This software release is managed with Java Device Manager (JDM) release 6.1.8.0 or higher.
This software release supports the Web Switching Module (WSM) release WebOS 10.0.34.0. This code is found on Nortel
web site under Content Networking -> Web Switches -> Ethernet Routing Switch Web Switch Module.
This software release supports SDM FW Release up to 2.3.7.0. This code is found on Nortel web site under Security & VPN
-> Service Delivery Module 8660, which provides a link to CheckPoint web site.
This software release supports SDM TPS Release up to 4.7.0.2. This code is found on Nortel web site under Security &
VPN -> Service Delivery Module 8660.
To download any of these code releases requires valid Nortel support web access, as well as valid CheckPoint support site
access for most FW code.
Changes
in
This
Release
New
Features
in
This
Release
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
