Avaya Ers 8600 User manual

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 1

EthernetRoutingSwitch8600

Readme

SoftwareRelease5.1.4.0

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 2

TableofContent

Ethernet Routing Switch 8600 .................................................................................................................................................. 1

Readme.................................................................................................................................................................................... 1

Software Release 5.1.4.0.......................................................................................................................................................... 1

Table of Content.................................................................................................................................................................... 2

Software Release 5.1.4.0...................................................................................................................................................... 6

Important Notices............................................................................................................................................................... 6

Platforms Supported.......................................................................................................................................................... 7

Notes for Upgrade ............................................................................................................................................................. 7

File Names for This Release................................................................................................................................................. 8

Version of Previous Release ........................................................................................................................................... 10

Compatibility.................................................................................................................................................................... 10

Changes in This Release.................................................................................................................................................... 10

New Features in This Release......................................................................................................................................... 10

Old Features Removed From This Release .................................................................................................................... 12

Problems Resolved in This Release................................................................................................................................ 13

Outstanding Issues.............................................................................................................................................................. 15

Known Limitations............................................................................................................................................................... 15

Documentation Corrections................................................................................................................................................. 16

Software Release 5.1.3.0.................................................................................................................................................... 17

Important Notices............................................................................................................................................................. 17

Platforms Supported........................................................................................................................................................ 18

Notes for Upgrade ........................................................................................................................................................... 18

File Names for This Release............................................................................................................................................... 19

Version of Previous Release ........................................................................................................................................... 21

Compatibility.................................................................................................................................................................... 21

Changes in This Release.................................................................................................................................................... 21

New Features in This Release......................................................................................................................................... 21

Old Features Removed From This Release .................................................................................................................... 21

Problems Resolved in This Release................................................................................................................................ 21

Outstanding Issues.............................................................................................................................................................. 24

Known Limitations............................................................................................................................................................... 25

Documentation Corrections................................................................................................................................................. 26

Ethernet Routing Switch 8600 ................................................................................................................................................ 27

Readme.................................................................................................................................................................................. 27

Software Release 5.1.2.0........................................................................................................................................................ 27

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 3

Table of Content.................................................................................................................................................................. 28

Software Release 5.1.2.0.................................................................................................................................................... 30

Important Notices............................................................................................................................................................. 30

Platforms Supported........................................................................................................................................................ 31

Notes for Upgrade ........................................................................................................................................................... 31

File Names for This Release............................................................................................................................................... 32

Version of Previous Release ........................................................................................................................................... 34

Compatibility.................................................................................................................................................................... 34

Changes in This Release.................................................................................................................................................... 34

New Features in This Release......................................................................................................................................... 34

Old Features Removed From This Release .................................................................................................................... 34

Problems Resolved in This Release................................................................................................................................ 34

Outstanding Issues.............................................................................................................................................................. 38

Known Limitations............................................................................................................................................................... 39

Documentation Corrections................................................................................................................................................. 39

Ethernet Routing Switch 8600.......................................................................................................................................... 40

Software Release 5.1.1.1................................................................................................................................................... 40

Software Release 5.1.1.1 ................................................................................................................................................ 40

1. Release Summary...................................................................................................................................................... 40

2. Important Notes before Upgrading to This Release.................................................................................................... 40

3. Platforms Supported................................................................................................................................................... 41

4. Notes for Upgrade ...................................................................................................................................................... 42

5. File Names for This Release ...................................................................................................................................... 42

6. Version of Previous Release....................................................................................................................................... 46

7. Compatibility............................................................................................................................................................... 46

8. Changes in This Release............................................................................................................................................ 47

9. Outstanding Issues..................................................................................................................................................... 49

10. Known Limitations..................................................................................................................................................... 49

11. Documentation Corrections ....................................................................................................................................... 49

Ethernet Routing Switch 8600.......................................................................................................................................... 50

Software Release 5.1.1.0................................................................................................................................................... 50

Software Release 5.1.1.0 ................................................................................................................................................ 50

1. Release Summary...................................................................................................................................................... 50

2. Important Notes before Upgrading to This Release.................................................................................................... 50

3. Platforms Supported................................................................................................................................................... 51

4. Notes for Upgrade ...................................................................................................................................................... 51

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 4

5. File Names for This Release ...................................................................................................................................... 52

6. Version of Previous Release....................................................................................................................................... 56

7. Compatibility............................................................................................................................................................... 56

8. Changes in This Release............................................................................................................................................ 56

9. Outstanding Issues..................................................................................................................................................... 60

10. Known Limitations..................................................................................................................................................... 61

11. Documentation Corrections ....................................................................................................................................... 61

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 5

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 6

SoftwareRelease5.1.4.0

Release Date: December 03rd, 2010

Purpose: Software maintenance release to address externally found customer issues.

ImportantNotices

Avaya Inc has acquired the Enterprise Solutions business from Nortel. This acquisition includes the ERS 8600 and software

described in this document. During the transition of all assets and support infrastructure of products and services to Avaya,

Nortel provides certain infrastructure support. As such, you will find the Nortel name, and pointers to Nortel support locations

on the Internet being referenced intermixed with Avaya in this document.

REGARDLESS OF SOFTWARE VERSION, the system-monitor flag should be checked on all systems to be sure it is

enabled. This flag should always be enabled as it enables a software monitoring capability to detect and respond to

abnormal software loop conditions. The flag setting can be checked via the command “show config”. NOTE: Enabling this

flag only takes effect after a reboot and must be saved in the config prior to reboot.

The display should be similar to the following:

ERS8600:6#showconfig

PreparingtoDisplayConfiguration...



#!flagsm‐modefalse

#!flagsenhanced‐operational‐modefalse

#!flagsvlan‐optimization‐modefalse

#!flagsglobal‐filter‐orderingfalse

#!flagsr‐modetrue

#!resource‐reservationmax‐vlanfalse

#!resource‐reservationmulticast2048

#!flagsmulticast‐check‐packettrue

#!flagssystem‐monitortrue(enabled) orpotentiallyfalse(disabled)

#!flagsregular‐Autonegfalse

#!record‐reservationfilter4096

If the system-monitor flag is set false, then it should be changed to true which can be accomplished through JDM by

following the menu option sequence “Edit Chassis” -> “System Flags” and then look under “System Monitoring” at the bottom

of the screen. Checked equals enabled.

To set via SNMP use:

MIBisrapidCity.rcMgmt.rcChassis.rcChasSystemMonitorEnable

snmpset -v 1 -c public x.x.x.x enterprises.2272.1.4.41.0 1

Where x.x.x.x = some IP address associated with the switch.

To view the setting via SNMP use:

snmpget -v 1 -c public x.x.x.x enterprises.2272.1.4.41.0

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 7

Output is either:

FALSE - SNMPv2-SMI::enterprises.2272.1.4.41.0 = INTEGER: 2 (disabled)

TRUE - SNMPv2-SMI::enterprises.2272.1.4.41.0 = INTEGER: 1 (enabled)

In prior releases, the SNMP timer task could potentially crash if the SNMP retry counter is set to a value greater than zero

and multiple concurrent SNMP inform events are generated which do not receive an acknowledgement. While multiple

factors and conditions need to align in order to encounter this SNMP task crash, it was recommended to set the SNMP retry

count within the snmp-v3 target-address to zero in order to avoid the issue altogether. An example of such a configuration is

(see the bolded entry):

Config snmp-v3 target-addr create "NNM" 10.10.10.1:162 "TparamV2" tdomain ipv4_tdomain timeout 1500 retry 0 taglist

informTag mms 484

This is resolved in the 5.1.2.0 release, and the retry value can now be set to values greater than zero. (Q02052753)



PlatformsSupported

All Ethernet Routing Switch 8600 modules are supported in the 8006, 8010, and 8010co Chassis. Full slot support for all

modules may be dependent on the presence of the High Performance (HP) Backplane. There is an orderable (and

chargeable) upgrade option for the HP Backplane.

The following modules are not supported in the 8003 chassis:

8692SF/CPU

All R/RS modules

NOTE: R/RS-series modules are supported in the 8010co chassis only with a High Performance Backplane installed.

Please refer to the following documents for extra details and as reference material in addition to this Readme:

Release Notes for the Ethernet Routing Switch 8600 Series Switch Software Release 5.1.0.0 (Doc # NN46205-402,

Rev 3.01)

Readme for Ethernet Routing Switch 8600 Series Switch Software Release 5.0.5.0. Release 5.1.2.0 has equivalent

CR fix functionality as Release 5.0.5.0.

Nortel Ethernet Routing Switch 8600 5.1 Upgrade Manual (Doc # NN46205-400, Rev 3.01)

Nortel Ethernet Routing Switch 8600 Installation – Modules, for Software Release 5.1 (Doc # NN46205-304, Rev

3.02)

Nortel Ethernet Routing Switch 8600 Administration, for Software Release 5.1 (Doc # NN46205-605, Rev 2.03)

Nortel Ethernet Routing Switch 8600 Routine Maintenance, for Software Release 5.1 (Doc # NN46205-312, Rev

2.01)



NotesforUpgrade

Please see Upgrade Guide and Release Notes for the Ethernet Routing Switch 8600 Series Switch Software Release

5.1.0.0 available at www.nortel.com/support.

NOTE: If upgrading to 5.1.4.0 code within any SMLT designed network from a release prior to 4.1.8.2 or 5.0.1.0, i.e. a

release which runs the ‘older’ SMLT architecture, then care should be taken to follow the proper upgrade steps. Please

review the 5.1.0.0 or the 5.0.1.0 Release Notes for specific details.

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 8



FileNamesforThisRelease

Module or file Type Description File name Size in

bytes

Software tar file Tar file of all

software Deliverables (includes images that also contain

encryption software) pr86_5140.tar.gz 62067142

Ethernet Routing Switch images

Boot monitor image CPU and switch fabric firmware p80b5140.img 1140094

Run-time image Run-time image p80a5140.img 12639154

Run-time image for R

modules Image for R modules p80j5140.dld 1525240

Run-time image for RS

modules Run-time image for RS modules p80k5140.dld 1586120

Run-time image for

Enterprise Enhanced

SF/CPU Daughter Card

(SuperMezz)

Image for the SuperMezz card p80m5140.img 12740040

3DES Encryption module for privacy protocol with Secure

Shell (SSH) p80c5140.img 55928

AES Encryption module for privacy protocol for

SNMPv3. Includes AES and DES p80c5140.aes (this

image includes the

DES image)

26947

MIB MIB files p80a5140.mib 4150092

MIB (zip file) Zip file containing MIBs p80a5140.mib.zip 674875

MD5 checksum file md5 checksums of all Release 5.1 software files p80a5140.md5 1358

Runtime image for ATM Runtime image for the ATM module p80t5140.dld 906024

Runtime image for POS Runtime image for the POS module p80p5140.dld 701771

Firmware images

FOQ for R modules Feedback output queuing FPGA firmware Foq267.xsvf 5320469

BMC for R modules BAP memory controller FPGA firmware bmc776.xsvf 2640266

DPC for R modules Dual port Controller FPGA firmware dpc194.xsvf 2642001

PIM8630GBR Programmable I/O module FPGA firmware; for the

8630GBR only PI_769.xsvf 2284578

Firmware for RS modules Contains FOQ, BMC, DPC, mirroring, and

loopback images rs_dpm_fpga.bin 4538368

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 9

PIM images for

RS modules

PIM FPGA firmware required for 8612XLRS

module only pim8612XLRS.bin 60183

PIM FPGA firmware required for 8634XGRS

module only pim8634XGRS.bin 78173

PIM FPGA firmware required for 8648GBRS

module only pim8648GBRS.bin 79891

PIM FPGA firmware required for 8648GTRS

module only pim8648GTRS.bin

54441

SSL images

SSL cluster upgrade Ethernet Routing Switch 8600 clustered SSL

modules self-installing runtime image/upgrade p80s5140.pkg 5988896

SSL boot monitor Ethernet Routing Switch 8600 SSL module boot

monitor p80s5140.img 7528448

SSL upgrade instructions Ethernet Routing Switch 8600 SSL upgrade

instructions p80s5140.upgrade 1481

SSL installation instructions Ethernet Routing Switch 8600 SSL installation

instructions p80s5140.install 2895

SSL diagnostics Ethernet Routing Switch 8600 SSL diagnostics p80s5140.diag 19460381

WSM images for Ethernet Routing Switch 8600

WebOS firmware image WSM WebOS v10.0.34.0 firmware image Wsm1003400_mp.img 845560

WebOS binary WSM WebOS v10.0.34.0 binary image Wsm1003400_bin.img 1376256

WebOS boot image WSM WebOS v10.0.34.0 boot image Wsm1003400_boot.img 43004

Device Manager images

Solaris for SPARC image Device Manager software image jdm_6200_solaris_sparc.sh 239157758

Microsoft Windows image Device Manager software image jdm_6200.exe 215146471

Linux image Device Manager software image jdm_6200_linux.sh 218350078

Service Delivery Module images

Service Delivery Module

Firewall Boot ISO for the NSF Service Delivery

Module Firewall booting from CD-ROM NSF5100_2.3.7.0_SDM_R60.iso

NSF5100_2.3.7.0_SDM_R65.iso

Upgrade package for the NSF Service

Delivery Module Firewall NSF5100_2.3.7.0_SDM_R60.pkg.gz

NSF5100_2.3.7.0_SDM_R65.pkg.gz

Service Delivery

Module TPS

Boot image for TPS Intrusion Sensor Nortel_TPS_Intrusion_Sensor-SDM-

v4.5.0-627-Install.iso

Boot ISO for TPS Defense Center booting

from CD-ROM NortelTPSDefenseCenter_2x70v4.5.0_62

7_Install.iso

Upgrade script (patch) to upgrade TPS IS

from 4.5.0 to 4.5.1. Nortel_TPS_IS_Upgrade_4.5.0_to_4.5.1_

Upgrade-47.sh

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

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 11

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.

The following new CLI commands are introduced to support:

ERS-8610:6/config/vlacp#?

Sub-Context:

Current Context:

disable

enable

info

hold-time <seconds>

ERS-8610:6/config/vlacp# hold-time ?

value in seconds for hold time

Required parameters:

<seconds> = vlacp hold time {0..60}

Command syntax:

hold-time <seconds>

ERS-8610:6/config/vlacp# info

Vlacp : enable

Vlacp hold-time : 20

ERS-8610:6/show/vlacp# info

=======================================================================

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 12

Vlacp Global Information

=======================================================================

SystemId: 00:18:b0:5c:a0:00

Vlacp : enable

Vlacp hold-time : 20

SLPP Enhancement

Introduced New EtherType for SLPP PDU:

From this release EtherType 0x8104 is replaced by 0x8102 as the default EtherType for SLPP PDUs. SLPP

EtherType can still be configured through CLI. Old EtherType 0x8104 will be processed to handle the backward

compatibility and upgrade scenarios.

If the received ether type is old default ether type (0x8104 ) or current default ether type (0x8102) or currently

configured ethertype, then the packet is classified as SLPP PDU.

The Ethertype can be displayed using following existing CLI command.

CLI Command:

config slpp info

Sub-Context:

Current Context:

add :

etherType (hex) : 0x8102

operation : disabled

tx-interval : 500

Re-Arm per port SLPP PDU Receive Counter issue:

Currently per-port SLPP PDU receive counter is never reset, resulting in shutting down links wrongly after months

of running when the counter hit the pre-defined limit. This issue has been addressed in this release by resetting the

counter if the switch not received expected number of SLPP packets on the port in a certain period of time. This

timer is set to 24 hours.



OldFeaturesRemovedFromThisRelease

None.

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 13

ProblemsResolvedinThisRelease

Platform

8648GTS and 8648GTRS modules do not negotiate speed and duplex as expected once Customizable

Auto-negotiation Advertisements (CANA) has been used on to limit link speed on a port and is

subsequently disabled on that port. This issue is resolved (wi00518718)

When PCAP is enabled and disabled, a control bit in fast path was not cleared correctly. This results in

packets received on the port that had been monitored through PCAP being forwarded to the CP incorrectly

and potentially cause high CPU utilization. This issue is resolved (wi00564156)

In prior releases, a timing issue existed in single CPU systems where physical reseating of the CPU card

would result in a COP-SW Exception event to be copied to the CPU during switch recovery. To avoid this

scenario, the chassis should be power cycled rather than reseating the single CPU. (wi00508448)

Port based shaper functionality may be disabled in hardware for R/RS modules after a port state change.

This issue is resolved (wi00564813)

SNMP get failed on rcIpfixExporterStatsTable since the length field passed in the OID is not supported by

the agent code. This issue is resolved (wi00564237).

For tagged ports, the QoS queue mapping for Layer 3 packets received on R/RS modules has been

corrected to align with E-modules. (wi00518702).

In prior releases, a very rare scenario exists where the system monitor could potentially incorrectly detect

the tTrapD task to be in an infinite loop and initiate recovery action. This issue is resolved (wi00508402).

If ‘ctrl-C’ is entered at certain points in the boot up sequence the normal boot sequence is aborted and the

user is entered into the shell access level of the switch. Sending ‘ctrl-C’ no longer results in user access to

the shell level. (wi00675102).

TFTP packets egressing out of line card port are marked with dscp 0x30, instead of default value. This

issue is resolved (wi00564778).

Executing the 'show sys pluggable-optical-modules info' command no longer results in repeated GBIC

inserted messages being generated. (wi00564844).

PIM mroute flapping could potentially be encountered in networks configured with short timer values for

the multicast forward cache timeout. This was only encountered for multicast streams with low data rates

in MLT or SMLT topologies and was dependent on which link in the S/MLT the data stream was active.

Mroute flapping will no longer be encountered in this scenario. (wi00564358)

CLI/NNCLI

Executing the ‘show fulltech’ command in NNCLI mode in some configurations would previously lead to

unexpectedly high CPU utilization. Optimizations in the execution flow have now been made to minimize

the impact of running the show ‘fulltech’. (wi00564789).

Deletions of VLAN IP did not previously remove the associated IP records in the HW. This could lead to

initial connectivity failure if the deleted VLAN IP address were re-used on a different device until an ARP

request was issued by the new device. This issue is resolved (wi00564233).

Routed ipv6 packets were previously dropped when ECMP was configured for IPv4. This issue is resolved

(wi00564341).

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 14

When changing the IP address of a VLAN, the previous VLAN IP address would still be advertised to

adjacent devices in the topology tables. This resulted in the “show sys topology” command from the

adjacent boxes still displaying the previous IP address of the neighbour until a cold boot of the neighbour

was performed. This issue is resolved (wi00507312)

DHCP

DHCP Replies are flooded by Relay Agent instead of sending unicast DHCP reply packet. This issue is

resolved (wi00564847).

IP Multicast

A PIM message received on a specific port was discarded if the egress towards the source is on the same

port but different VLAN. This issue is resolved. (wi00564777)

In multicast over SMLT environments, aggregation switches could never age out certain S,G entries even

after the source stopped sending multicast traffic. These stale entries would eventually prevent new entries

from being created and could also result in high cpu utilization. This issue is resolved (wi00697430)

MLT / SMLT

An infrequent scenario has been identified which could result in a CPU reset in the SMLT module during

upgrades to 5.1.2.0. This issue is now resolved. (wi00564781).

The VLAN MAC addresses of an IST peer switch should be learned only via IST links in a normal

operating environment. It has been noted in some transient network scenarios that flooded control plane

packets may be reflected and result in these addresses being learnt temporarily on SMLT links. SMLT

behaviour has now been enhanced to ensure that the IST peer switch VLAN MAC addresses are never

learnt on SMLT links. (wi00733200).

In full mesh SMLT with both LACP and VLACP configured, a higher than expected number of VLACP

packets may be forwarded to the CPU. This issue is resolved (wi00564193).

In ERS 8600 with static-mcast mac configured in a SMLT setup, when the links are disabled/enabled, the

error message "rarIsPortInMgid(4095): Invalid Mgid" was seen. This issue is resolved (wi00564321).

When both aggregation switches in an IST pair are rebooted with SMLT ports disabled in the saved

configuration file, the SMLT state will remain “normal” on one of the switches when the SMLT ports are

subsequently restored. This issue is resolved (wi00564214).

In an LACP SMLT, the SMLT status would incorrectly remain in SMLT state if the established LACP

aggregation times out on the link without a link failure. This issue is resolved (wi00828218)

BGP/VRF

Disable/enable of route-policy configured within a VRF results in a crash because of NULL pointer

dereference. This issue is resolved (wi00564289).

On disabling/re-enabling BGP or doing BGP restart on the VRF, routes updates were not being processed

properly in configurations where VRF 1 was not configured. This issue is resolved (wi00564348).

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 15

OutstandingIssues

Please refer to the Outstanding Issues Section of the Release Notes for Ethernet Routing Switch 8600 Software Release

5.1.0.0. Additionally, the following issues have also been classified outstanding issues.

If there is a static route/static default route entry in intermediate switches and ospf is disabled at the

multicast source vlan, pim and igmp tables are updated to point to static route/static default route on the

intermediate switches. If the static route/static default route direction does not point to the multicast

source then multicast traffic will not resume even after enabling ospf at the multicast source vlan.

(wi00564227)

QoS ingress-map configuration entries may not be synchronized properly to the slave CPU in HA-CPU

configurations and could potentially be lost on CPU failover. This will be addressed in a future release.

(wi00698375)

The option to reset the switch Out of Band management IP address currently responds with an error

indicating the subnet mask is invalid. (wi00730804)

For SMLT/MLT setup, while L4 hashing is done for Jumbo packets, the last fragment of the packet does

not follow the same link as the rest of the fragments. So, there will be chances of fragments reaching the

destination out of sequence, which may lead to packet drop at the application layer. (wi00564807)

In a PIM-SSM network, the configuration of static IGMP entries will not function properly after a CPU

failover. The static entry can be recovered by deleting and re-adding the static igmp configuration or

disabling and re-enabling the ssm-channel. (Wi00564255)

In an ANYCAST RP routed square topology, a traffic interruption may be encountered when the link which

is a part of the primary routed data path is toggled. The traffic impact will last a maximum of 60 seconds

until the next MSDP SA is received. (Wi00564776)

As part of the enhanced support for virtualization, the total number of DHCP instances supported has been

limited to 512 although DHCP relay may be enabled on more than 512 VLANs. (wi00716374)

VLACP PDU transmission and processing will behave at double the configured timer values in systems

with CPU mezz cards. (wi00728743, wi00728749)

KnownLimitations

Please refer to the Known Limitations Section of the Release Notes for Ethernet Routing Switch 8600 Software Release

5.1.0.0. Additionally, the following issues have also been classified as operation not to be changed.

ERS8600 might have an I/O module COP (I/O co-processor) crash in an HA configuration, if the

master/standby SF/CPU reset/reboot interaction is not properly performed. When resetting or rebooting the

master, always allow the standby to take over as new master before any additional resets or reboots are

attempted. When resetting or rebooting the standby, always make sure the master recognizes the standby is

now off-line (5-10 seconds generally) before any additional reset or reboot activity on master is performed.

(Q02068289)

The ERS 1600 will not pass IP packets that contain a received IP header checksum value of 0xffff. The ERS

8600 E/M modules will potentially create and pass such packets. The RFC regarding this area of operation is

not 100% clear as to how a product should behave, and what is valid. Therefore it is now recommended to not

connect an ERS 1600 running in L3 operation to the egress port of an E/M module of an ERS 8600, to avoid

the potential for this situation to be seen. If seen, the application will fail, as the required packet passing will

always be dropped. In these situations, the user must now design their network differently (such as use R/RS

modules instead), and not at Avaya’s expense. (Q02154661)

It is not good practice to pull master CPU card in dual CPU environments. The recommended

method is to failover to the standby before removing the "old" master CPU. For single CPU

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 16

systems, or when removing the second CPU in dual CPU system, it is recommended to power cycle

as part of the switch recovery.

DocumentationCorrections

None.

Nortel. The Ethernet Routing Switch 8100/8300/8600 is a trademark of Avaya, Inc.

The information in this document is subject to change without notice. The statements, configurations, technical data, and

recommendations in this document are believed to be accurate and reliable, but are presented without express or implied

warranty. Users must take full responsibility for their applications of any products specified in this document. The information

in this document is proprietary to Avaya.

To access more technical documentation, search our knowledge base, or open a service request online, please visit Avaya

Technical Support on the web hosted by Nortel: http://www.nortel.com/support

Avaya Inc. – Proprietary & Confidential.

Use pursuant to the terms of your signed agreement or Avaya policy. 17

SoftwareRelease5.1.3.0

Release Date: August 06th, 2010