Alcatel-Lucent ESD IP Networking Service Release 8.1.1.555.

R01 - 8/20/2014

Intermediate Release Notes

OmniSwitch 6860/6860E
Release 8.1.1.555.R01
The following is a list of issues that have been identified and corrected in
an AOS software release. This document is intended to be used as a preupgrade guide and does not replace the Release Notes which are created
for every GA release of software.
Important Notice: For a copy of software release not posted on the Web or if you have any
questions or concerns please contact Alcatel-Lucents Technical Support Department.

Problems Fixed Between Builds 478 and 555 ........................................................................... 2

Known Issues ............................................................................................................................. 2
Feature Support .......................................................................................................................... 3

1/3

Alcatel-Lucent ESD IP Networking Service Release 8.1.1.555.R01 - 8/20/2014

Problems Fixed Between Builds 478 and 555

PR
Summary:

192203
Dhcp-snooping hardware resource limits are reached in a VC which has IP
source filtering enabled on a linkagg when one of the VC units is reloaded.

PR
Summary:

193578
High CPU utilization may be seen on slave chassis after multiple takeovers.

Known Issues
PR
Summary:
Workaround:

PR
Summary:

Workaround:

197145
When inserting PS-1 as a redundant power supply the show power supply
command does not display any information regarding PS-1.
The system detects the power supply when the power cord is connected.
There is no functional impact, this is a display issue only. Power supply
redundancy works as expected.
197280
In the case where DHCP snooping is enabled on an OmniSwitch and the
DHCP client VLAN does not have an IP interface. If the OmniSwitch has a
route to the client subnet and the DHCP reply is sent as a unicast packet,
the DHCP reply will not be forwarded to the DHCP client.
Note: the route need not be specific to the client subnet, it could be a
default route for 0.0.0.0.
Add an IP interface for the client VLAN.

2/3

Alcatel-Lucent ESD IP Networking Service Release 8.1.1.555.R01 - 8/20/2014

Feature Support
PoE Microcontroller Firmware Update Capability
The PoE microcontoller firmware can now be upgraded using the CLI. This should only be done by direction of
Service & Support.

Loopback Detection (LBD)

Note: This feature is being introduced with the 8.1.1.555.R01 release as an early availability feature. It is
available for demonstration purposes only but is not officially supported. Most CLI and feature functionality is
available; however, the feature has not gone through the complete Alcatel-Lucent qualification process. For
additional information please contact the Product Line Manager.
Loopback Detection can detect and prevent layer 2 forwarding loops on port in the absence of other loopdetection mechanisms such as STP/RSTP/MSTP. There are some scenarios that can prevent STP/RSTP/MSTP
based loop detection from being used, such as:

Existing equipment that drops the BPDUs

The loop detection protocols are restricted such as on an edge network

The LBD feature detects that a port has been looped back or looped. If a loop-back/loop is detected, the port is
disabled (forced down) and the appropriate error log is issued. The switch periodically sends out layer 2
Ethernet frames (LBD frame) from all loop-back detection enabled ports. The LBD frame is not a BPDU frame.
In normal state of the access line this frame is removed from the network segment by the subscriber equipment.
In case of a failure (cable fault, NIC, etc.) the switch receives the LBD frame back on the port. After receiving
the frame, the switch forces the access port down and issues an SNMP trap indicating the loopback violation.
The port can automatically be re-enabled or manually re-enabled by the administrator through the CLI.
Note: Clearing a loopback detection violation on a link aggregate using the auto-recovery feature is not
currently supported. For a link aggregate the violation must be manually cleared.

Deep Packet Inspection (DPI)

Note: DPI was introduced in the 8.1.1.R01 GA release as an early availability feature. It is available for
demonstration purposes only but is not officially supported. Most CLI and feature functionality is available;
however, the feature has not gone through the complete Alcatel-Lucent qualification process.
DPI is still available in 8.1.1.555.R01 as an early availability feature but please note the following:

DPI is not compatible with ISSU from 8.1.1.497.R01(GA) to 8.1.1.555.R01. After an ISSU upgrade
modification of configuration and statistics counters may not work properly.

DPI statistics support is introduced in this release but statistics may not always represent correct values.

OmniVista 2500 NMS Application Visibility feature evaluation requires a minimum AOS version of
8.1.1.555.R01.

3/3