Known Limitations - Avaya ERS 8600 Manual


648GTS and 8648GTRS modules do not negotiate speed and duplex as expected once Customer Auto-
negotiation (CANA) is enabled on these ports. (

ERS8600 does not recognize ERS4550GT in the CLI topology database (Q02012675).

In NNCLI mode, with scaled routes (thousands), one may notice that routes are not relearned after they are
cleared with clear ip route command (Q02119580)

PIM join message received on specific port is discarded if the egress towards the source is on the same port
but on a different VLAN. In this specific case, multicast traffic may not work as expected (Q02142356)

In SMLT configurations with both aggregation switches having SMLT ports disabled when the switch comes up
after reboot and when the ports are enabled, the MLT type remains norm on one of the switches. Disabling
and re-enabling the SMLT port will recover from the problem. (Q02150122)

In a setup with BGP running on VRFs, on disabling and re-enabling BGP or doing a BGP restart globally or on
the BGP neighbor, one may notice that BGP sessions do not bring up routes successfully. Having a vfrf id of 1
with BGP enabled alleviates the problem. (Q02153885)

In systems with RS modules, when pcap is enabled and then disabled, a particular bit in the hardware in RS
modules ends up with an incorrect value. This results in unintended packets hitting the CPU causing high cpu
utilization. (Q02160154)

When using XFPs with RS modules and while performing queries for certain rcPlug MIBs, the switch may
experience high cpu utilization and one may notice inconsistancies in related statistics. (Q02138919)

The commands "config ip forwarding disable" does not work (Q02140861)

In HA-mode, following a CPU switch-over, IGMP Static entries, if configured, in a PIM-SSM config, will not be
active on the new master CPU (Q02141640)

In Microsoft NLB cluster and layer2 environments, one may not be able to ping the cluster IP from a client if
IGMP snooping is enabled and the ingress port on the ERS8600 is a R-module (Q02145862)

In BGP environments with VRFs, a switch may experience a crash upon disabling and re-enabling a route
policy. The problem can be avoided by using vrf id 1 (Q02156040)

Upon enable and disable of pcap feature on RS modules, one may notice unintended packets reaching the cpu
causing high cpu utilization.(Q02160154)

In a square SMLT with LACP enabled on the SMLT, when one of the aggregation switches is rebooted, SMLT
may enter into normal state in one of the aggregation switches in the opposite pair of aggregation switches.
Toggling LACP on the affected switch recovers the SMLT. (Q02156133)

High CPU utilization may be observed on a box running HA with Mezz present and enabled after Primary CP is
failed and the Standby CP takes over with the following traffic pattern. The traffic arriving to an end station
which is directly connected to the HA box (VRF2) via routing and this end station was disconnected from the
network for a while (Q02165596)
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)
Use pursuant to the terms of your signed agreement or Avaya policy.
Q02139324)
Avaya Inc. – Proprietary & Confidential.
25