Skylight Element LX v7.9.4 Release Notes

Release Notes
Skylight element: LX
Version 7.9.4_24917 (2022-08-01)
Revision 1 — August 1, 2022
Release Notes Skylight element: LX Version 7.9.4
Publication Information
Skylight element: LX Version 7.9.4 Release Notes
Revision 1 — Publication date: August 1, 2022
Trademark Information
© 2022 Accedian Networks Inc. All rights reserved. Accedian™, the Accedian logo™, Skylight™, Skylight
Interceptor™ and per-packet intel™, are trademarks or registered trademarks of Accedian Networks Inc.
To view a list of Accedian trademarks visit: http://accedian.com/legal/trademarks.
All other company and product names may be trademarks of their respective companies. Accedian may,
from time to time, make changes to the products or specifications contained herein without notice. Some
certifications may be pending final approval; please contact Accedian for current certifications.
Accedian’s products are protected by patents as indicated on Accedian’s website, located at
http://www.accedian.com/en/legal.html
The mention of any product herein does not constitute an endorsement by Accedian Networks Inc.
The content of this publication is provided for informational use only, is subject to change without notice
and should not be construed as a commitment by Accedian Networks Inc. Accedian Networks Inc. assumes
no responsibility or liability for any errors or inaccuracies that may appear in this document.
Except as expressly permitted in writing, no part of this publication may be reproduced, stored in any
retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or
otherwise, without prior written consent of Accedian Networks Inc.
Changes are periodically made to the information herein; these changes will be incorporated into new
editions of this publication. Accedian Networks Inc. may make improvements and/or changes in the
products and/or software programs described in this publication at any time.
Contact
If you have comments regarding this manual, please address them to:
Accedian Networks Inc.

Attention: Technical Publications
2351 Alfred-Nobel Blvd., Suite N-410
Saint-Laurent, Québec
Canada H4S 2A9
techpubs@accedian.com
Tel: 514-331-6181
Fax: 514-331-2210
Toll free: 1-866-685-8181
accedian.com
Revision 1 — August 2022 2

Table of Contents
1. About This Document ........................................................................................ 4

1.1 Organization................................................................................................................................................. 4
1.2 Conventions ................................................................................................................................................. 4
1.3 Related Documentation ............................................................................................................................. 5
1.4 Product Name Changes ............................................................................................................................. 5
2. Requirements........................................................................................................6
3. Firmware Version 7.9.4_24917 (2022-08-01) ............................................... 7
3.1 New Features and Enhancements ......................................................................................................... 7
3.2 Addressed Issues ........................................................................................................................................ 8
3.3 Operational Considerations and Known Limitations ...................................................................... 10
3.4 MIB Changes ............................................................................................................................................... 22
4. Firmware Version 7.9.3_24427 (2021-12-15) ............................................... 23

4.1 New Features and Enhancements ....................................................................................................... 23
4.2 Addressed Issues ...................................................................................................................................... 24
4.3 Operational Considerations and Known Limitations ......................................................................25
4.4 MIB Changes ............................................................................................................................................... 37
5. Firmware Version 7.9.2_24262 (2021-09-24) ............................................ 38

5.1 New Features and Enhancements ...................................................................................................... 38
5.2 Addressed Issues ....................................................................................................................................... 41
5.3 Operational Considerations and Known Limitations ..................................................................... 43
5.4 MIB Changes .............................................................................................................................................. 56
6. Firmware Version 7.9.1_23673 (2020-11-12) ................................................ 57

6.2 Addressed Issues ...................................................................................................................................... 58
6.4 MIB Changes ............................................................................................................................................... 72
7. Firmware Version 7.9_22663 (2020-03-25)................................................ 73

7.2 Addressed Issues ....................................................................................................................................... 73
7.4 MIB Changes .............................................................................................................................................. 86

1. About This Document

These release notes cover the requirements, new features, changes, addressed issues and
known limitations for the Skylight Element: LX firmware version 7.9.4. Please read all the
notes prior to installing this firmware version. For more information, refer to docs.accedian.io,
features and user material for Skylight performance elements: LX.
1.1 Organization
This manual includes the following sections:
Requirements
This section provides requirements for Firmware Version 7.9.4.
Firmware Version 7.9.4_24917 (2022-08-01)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.4.
Firmware Version 7.9_22663 (2020-03-25)
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.
1.2 Conventions
This section explains the conventions that are used in Accedian user documentation.
General conventions used in all documents

Notes contain information that emphasizes or supplements certain points in the main text.
Notes are enclosed in blue lines, for example:
Note: This description cannot be modified.

Cautions describe situations in which failure to take an action or avoid an action could result in
damage to equipment or make it impossible to access the system. Cautions are enclosed in red
lines, for example:
CAUTION: If you modify a Management interface, you and other users may lose
access to the Web interface and the CLI.
1.3 Related Documentation

The following documents provide additional information about the Skylight Element: LX:
• Skylight Element: LX CLI Command Guide (embedded in docs.accedian.io).
1.4 Product Name Changes

The following Accedian products were renamed in March 2020. References to these products
in this document may reflect the new naming conventions. Skylight element: LX is a new
product and is therefore not in the list below.
Former Name Former Name New Name
antMODULE ant Module Skylight sensor: module 10G

Skylight element: 1GE
MetroNID GT GT Performance Element Skylight element: GT
MetroNID GX GX Performance Element Skylight element: GX
MetroNID TE TE Performance Element Skylight element: TE
MetroNODE 10GE 10GE Performance Element Skylight element: 10GE
MetroNODE CE CE Performance Element Skylight element: 1GE
MetroNODE GE GE Performance Element n/a
MetroNODE NE NE Performance Element n/a
MetroNODE LT LT Performance Element Skylight element: LT
NanoNID/nanoNID Nano Module Skylight sensor: module 1G
VeloCITY FS FS Performance Element Skylight element: FS
VeloCITY FS 10G FS 10G Performance Element Skylight element: FS-10G

2. Requirements
This firmware version applies to Skylight element: LX 7.9.4, and is compatible with Skylight
orchestrator 20.02 and above.
Note: There is a patch available for earlier versions of Skylight orchestrator. Please
contact Accedian support for further information.

3. Firmware Version 7.9.4_24917 (2022-08-01)
3.1 New Features and Enhancements
AC-22957 Update dropbear SSH to version 2022.82

Updated to latest dropbear version to avoid vulnerabilities.
AC-22729 ICMP redirect security issue

The ICMP Redirect configuration feature supports disabling/enabling ICMP Redirect
feature via CLI/WEB interface.

3.2 Addressed Issues
AC-24913 ERP ring traffic interrupted after configuration change and reboot
User changed ERP version from 2 to 1, and then back to 2, on a working ERP ring in the
LAG port. Traffic was initially okay but the device stopped traffic after reboot.
This issue has been fixed.
AC-24300 Consolidated interface with ":" unable to show/edit using CLI

User cannot show or edit interface using the CLI. If the interface is created using the
GUI, and user tries to edit/show using the CLI they, received the error message: Error:
Invalid alias number.
AC-24153 Unit unable to sync with NTP server after upgrade to 7.9.2
The unit is unable to sync with NTP server after upgrade to 7.9.2. One-Way delay
measurements were impacted and high-resolution sync was not established.
AC-22118 Security assessment reported vulnerabilities

User performed security assessment using firmware 7.9, and discovered vulnerabilities on
this device, including:
• Empty password field in /etc/passwd
• No authentication for single user mode
• DOM-based cross site scripting vulnerability
• ICMP redirection enabled
• TLS/SSL Server supports the use of Static Key Ciphers
• ICMP timestamp response
• TCP timestamp response
• TLS/SSL Server Does Not Support Any Strong Cipher Algorithms
• Password hashes in /etc/passwd
• User home directory mode unsafe
• User home directory mode unsafe
• Weak permissions for Password, Shadow and Group Files
• Logging of Security authorization messages.
These issues have been fixed.

AC-22103 LLDP not advertising IP address correctly

User did some testing using firmware 7.9 and 7.9.1 and observed error with LLDP. When
trying to display the LLDP information, user could not see Neighbor IP management
advertisement. This would only be displayed when user enabled the "Primary" (System
>Configuration > Interface) checkbox of the management IP that was configured.
These issues have been fixed.
AC-21895 The PTP Master port does not work after deleting interface
While the PTP is running, changing the configuration of the assigned interface on a
specific PTP port will result in non-deterministic behavior, for example: change VLAN type
T-Vlan to C-Vlan, delete interface. A good practice is to disable and re-enable the PTP
after changing the interface's configuration.
AC-21754 Unable to become PTP slave port after IPv6 VLAN connection re-establishment
specific PTP port will result in non-deterministic behavior, for example: change VLAN
type T-VLAN to C-VLAN.
A good practice is to disable and re-enable the PTP after changing the interface's
configuration.

3.3 Operational Considerations and Known Limitations

Important Notes
 The Skylight element: LX firmware is delivered in a consolidated file prefixed by “ACC”,

e.g. ACC_7.X_YYYY.afl. This file contains the firmware for the GT, GX , LX and LT
Performance Element products. It cannot be used with any other product.
 IMPORTANT: Prior to upgrading the firmware on a unit where the History Buckets
feature is enabled, certain precautions may need to be taken to prevent a loss of history
data during the upgrade. Refer to ATRC-B10797 for details.
 In a G.8032 ring configuration, the Skylight element: LX supports a maximum of 62
policies on the LAG port (i.e. policies that govern how traffic is dropped from the ring to
UNI ports). This limitation does not apply to the UNI ports (i.e. policies that govern how
traffic is added to the ring) unless the VLAN-tagged customer traffic is passed
transparently from the UNI port to the ring through one-to-one mapping.
One way to avoid this limitation and maximize the number of usable UNI policies is to
encapsulate multiple customer VLANs (coming from the UNI) under a single service
provider VLAN on the ring. Doing so reduces the number of policies required by the LAG
port.
AC-24052 Unable to send file after upgrade due to syntax change

After upgrading to 7.9.1 or 7.9.2, the SCP is no longer able to send files, reporting the
following error: Code = 3: URL using bad/illegal format or missing URL.
Workaround: Customer needs to edit the URL after upgrading to 7.9.2 or 7.9.3.
AC-20838 ERP ring using CFM with VLAN does not work when applied to the port with RPL
link
The ERP ring, using CFM with VLAN, does not work when applied to the port with the
RPL link and therefore CCM is not received.
Workaround: Use releases before version 7.7.
AC-22752 TWAMP Sync issue when reflector is an Accedian device with 6.4.x software or
older
A sync compatibility with older software will cause a sync error when generating
TWAMP towards a device using older software (ex: TE device). The impact is the

absence of one-way delay measurement. There is no workaround available for this

issue.
ATRC-D15900 LBR message still occurs when MIP and MEP are different VLAN type
Unicast CFM-LBM frames sent to Accedian Demarcation devices are VLAN TPID unaware.
ATRC-D17907 Missing packets on RFC2544 generator layer-3 (2 flows)

With an RFC2544 generator layer-3 that has flow 1 set as QinQ and flow 2 set as no
encapsulation (or QinQ), packets are missing on flow 2 after completing the RFC2544 with
two flows.
ATRC-D17871 Error loading proper page indexing when loading pages via URL/back
Possible error loading proper page indexing when loading WEB pages that contain paged
tables via URL (i.e. back). Some WEB pages contain a table paging feature that displays a
certain number of instances per page within a table. As the user cycles through the
different pages, he will be able to view different instances and the URL will be updated to
save this information. This allows a user to re-load the same view by using the URL (i.e.
saving bookmark, clicking back to reload page, etc.). However, when reloading a web
page using this method, incorrect index offsets may be observed for instances on certain
pages.
ATRC-D13944 Generator RFC2544 in-service and monitor operate incorrectly

When an L2PT rule is enabled with forwarding mode set to either pop or replace and the
frame is S-VLAN tagged, the frame is dropped instead of being forwarded.
ATRC-D16848 Filter does not catch IPv6 Extension Headers

Because the frame header fields extraction depth is limited to the first 96 bytes of a
frame, any fields of an IPv6 frame that are beyond the first 96 bytes will not be extracted.
Therefore, they will not be found in the classification key used against an IPv6 filter.
Also, the following IPv6 Next Headers identifying Extension Headers will be skipped.
Therefore, they will not be found in the classification key used against an IPv6 filter:
• Hop-by-Hop options (0)
• Destination options (60)
• Routing header (43)
• Fragment header (44)
• Authentication header (51)
• Mobility header (135)

ATRC-D17233 SNMP IPv6 Filtering and Loopback is not supported

SNMP IPv6 Filtering and Loopback is not supported in this release.
ATRC-D15894 LBR message still occurring when MIP is created with MD level
Unicast CFM-LBM frames sent to Accedian Demarcation devices do not validate the MEG
level in the frame.
ATRC-D15523 DOWN MEP using VCE does not work with un-tag packet
We do not support EVC Client Interface for an untagged MEP on a VCE. We only support
untagged MEPs, if it is a Down MEP on a physical port of the VCE.
ATRC-D15473 The TP-Z-PCP-Mapping does not work properly

An Up MEP defined on the TP-Z port of a VCE, which is defined with frame-type ‘all-to-
one’, does not support the PCP mapping since it necessarily becomes untagged when
egressing TP-A. The PCP value used is then inherited from the CFM object when
additional components are in the transmission path.
ATRC-D15229 DownMEP_VCE: VCE is using TPID but it is affected by changing s-vlan mode
0x9100
The user needs to configure the S-VLAN ethertype located under General system settings,
prior to configuring any VCE or CFM elements. If the user changes this setting after
configuring other elements, they may see some display discrepancies.
ATRC-D07187 LAG Port remains DOWN with LACP, but UP with Link status
When using LACP, if the catchall L2PT rules are enabled, LACP frames will not be handled
correctly to allow LACP to operate correctly.
Workaround: Create LACP rules that also apply to the L2PT configuration.
ATRC-D05982 Limited availability of the OAM Loopback feature

The 802.3ah OAM loopback feature is not functional on the following platforms:
• Skylight element: GT
• Skylight element: GX
• Skylight element: LT
• Skylight element: LX

ATRC-D05907 Reserved value no longer allowed in a Y.1731 configuration

As of firmware version 6.4.2, VLAN ID 4095 is a reserved value and is no longer allowed in
Y.1731 configurations.
If VLAN 4095 was used in a previous firmware version, support in version 6.4.2 will be
maintained through a firmware upgrade. However, any MA/MEG instances using VLAN
4095 cannot be recreated in the event of a deletion.
ATRC-D05812 SNMP returns incorrect values for certain PAA configuration parameters
Polling the following PAA configuration OIDs with SNMP returns “0” instead of the actual
value:
• acdPaaUdpCfgOneWayDelayMax
• acdPaaUdpCfgOneWayDelayThresh
• acdPaaUdpCfgOneWayAvgDelayThresh
• acdPaaUdpCfgOperationMode
• acdPaaUdpCfgPktSize
• acdPaaUdpCfgSamplingPeriod
• acdPaaUdpCfgPeerID
ATRC-D05755 L2PT rules for ESMC also catch other slow protocols
An L2PT rule configured for the ESMC protocol may also catch the following protocol
frames:
• Link OAM
• LAMP
• LACP
If separate L2PT rules are not required for these protocols, no specific intervention is
necessary.
If separate L2PT rules are required for these protocols, assign a higher rule ID to ESMC to
ensure that it does not interfere with other protocols. As a result, other protocol filter
rules will be processed before the ESMC rule.
ATRC-D05720 VC Agent: Changing the local time can cause a disconnection from Vision EMS
Changing the local time on a unit can cause the Vision Collect agent to disconnect from
Vision EMS. The agent will reconnect automatically. No PM data is lost; if a transfer is
interrupted, the data will be retransferred once the connection is restored.

ATRC-D05446 Slight variation in BLUE queue full/empty threshold percentage values

The Web interface for the following products accepts values between 0 and 100 for the
BLUE Queue Full Threshold and BLUE Queue Empty Threshold parameters:
These values are expressed as percentages. However, this percentage value is
subsequently converted to a binary number and mapped to the range 0-128, as the
underlying register is 7 bits in length.
In most cases, the initial percentage will not correspond to an exact binary value. When
this value is then converted back to a decimal percentage for display purposes, the end
result may differ slightly from what was initially entered.
ATRC-D05432 History CSV files may not all contain the same range of period numbers
The exported history CSV files may not all contain the identical range of period numbers,
depending on when the given history metrics were collected. Enabling multiple categories
of history metrics with many instances requires more processing than history metrics with
fewer categories and instances. Since the history files are processed sequentially, some
exported files may consequently present different period numbers compared to others.
For example, the CFM DMM file may show periods 16-30, whereas the CFM SLM file may
show periods 17-31, since it was processed afterwards. The reason for this variation is that
new periods are included in the CSV file as soon as they become available.
This is the expected behavior. There is no period number synchronization between history
categories. Note that all periods are exported in the CSV files and no data is lost.
ATRC-D05382 CoS Mapping: Yellow PCP Out is not mapped to a queue

The following products use CoS mapping to define the internal CoS that service frames
will use in the unit.
However, the pre-marking color parameter (set to Green or Yellow) is disregarded when
mapping a flow to a traffic queue. The system’s internal CoS always uses the configured
Green PCP value to map a flow to a queue, regardless of whether the pre-marking is set
to Green or Yellow.

ATRC-D04263 Web Interface: VLAN ID value not properly validated when creating a VID set
The VLAN ID value is not properly validated when creating a VID set in the Web Interface.
Entries outside the valid range (0–4095) are accepted, as well as character strings;
however, the resulting VID set instance is empty with no VLAN ID assigned.
This issue only concerns the Web Interface; the CLI performs the proper validation and
rejects invalid entries as expected.
The following products and firmware versions are affected:
Product Name Firmware Versions
TE-x Performance Element 5.1 – 6.4.3
GT/GT-S Performance Element, now 6.3 – 7.3

Skylight element: GT/GT-S (7.9) 7.9.1
GT-Q/GT-QE Performance Element 7.1.1 – 7.3
GX/GX-S Performance Element, now 6.3 – 7.3

Skylight element: GX/GX-S (7.9) 7.9.1
10GE CE/NE Performance Element 5.0 – 6.3
LT/LT-S Performance Element, now 6.3 – 7.3

Skylight element: LT/LT-S (7.9) 7.9.1
Skylight element: LX-S 7.9.1
FS/FS 10G Performance Element 1.0 – 1.1
ATRC-D04040 Syslog error message at login after configuring RADIUS

After a first-time RADIUS configuration, a false syslog error may be generated due to
start-up conditions when the user logs in.
The syslog message is as follows:
Jan 1 00:19:13 C074-0010 dropbear[1620]: rc_get_seqnbr: fscanf
failure: /tmp/radius.seq
This message has no consequence and can be ignored.
ATRC-D03949 Modified syntax for CLI command “bandwidth-generator add”

Starting in firmware version 6.4, the CLI command bandwidth-generator add is used to
configure regulators and bandwidth sharing envelopes.
Previous syntax (before 6.4):
bandwidth-regulator add <regulator-name> …

New syntax (6.4 and later):

bandwidth-regulator add regulator <regulator-name> …
or
bandwidth-regulator add envelope <envelope-name> …
Consequently, the word regulator is reserved as of firmware version 6.4 and cannot be
used as a regulator name, although the former syntax is still supported for backward
compatibility.
These changes are illustrated in the following examples.
Preferred syntax:
bandwidth-regulator add regulator regulator1 cir 20000 …
Allowed (for backward compatibility):
bandwidth-regulator add regulator1 cir 20000 …
Not allowed (triggers an error message):
bandwidth-regulator add regulator cir 20000 …
(invalid parameter value)
ATRC-D03939 Maximum number of complex rules for ERP traffic

For any unit that supports G.8032, the system automatically creates a default Layer-2
filter traffic policy (used for the ring pass-through traffic) whenever a LAG port is
configured for ERP.
Since this default policy consumes one of the unit’s available complex rules (i.e., using a
Layer-2 or IPv4 filters), the number of complex rules available to users on that LAG port is
reduced by 1. This situation has no impact on other ports.
ATRC-D02695 Timestamps of report periods are not always contiguous

The data collected by Vision EMS in high-resolution mode can occasionally show
consecutive records with timestamps that are not contiguous.
Be aware of the following limitations:
• When data is collected in high-resolution (1 second) mode, two consecutive
measurements can sometimes present the same timestamp, or show a gap
between the timestamps. This is caused by rounding the time value to a
granularity of 1 second.
Please note that in this case, no periods or measurements are lost, i.e. all periods
are consecutive, and none are missing.
• There can be a timestamp gap or overlap when the unit is first synchronized by
NTP, PTP or GPS. As the Flow meter may be acquiring data before the
synchronization is complete, a time adjustment could affect the timestamps. No
periods or measurements are lost.

Inconsistencies may also surface in the timestamps collected before a system reboot
when compared to those collected after the reboot.
ATRC-D02648 New behavior when re-enabling CFM-PL instances

In firmware version 6.3.1, the CFM packet loss (PL) behavior has been modified as follows:
Previous behavior (before 6.3.1): When a packet loss (PL) instance is re-enabled after
being disabled, the current period results contain the last values from the point at which
the instance was disabled.
New behavior (6.3.1. and later): When a packet loss (PL) instance is re-enabled after being
disabled, the current period results are cleared, and measurements begin from 0.
ATRC-D02057 Syslog: Entries are sometimes not displayed in the system log
When a large number of events occur at the same time (e.g. raising or clearing hundreds
of alarms simultaneously), some entries may be absent from the syslog. Missing entries
do not imply that the corresponding events/actions were not properly executed.
For example, in the case of alarm storms, although syslog messages for some status
changes are not displayed, all the alarms are updated to the correct status and the
corresponding SNMP traps are reported.
ATRC-7830 RFC-2544 testsuite: Report displays incorrect unit identifier information

When running the RFC-2544 testsuite after modifying the unit identifier (System ▶ DNS ▶
host name), the generated report contains the previous unit identifier.
ATRC-B10797 Firmware upgrade considerations pertaining to history buckets

Since firmware version 6.3.1, several software modifications have optimized how the
history data is handled and stored to flash memory. Before proceeding with the firmware
upgrade, take the following precautions:
• To prevent any loss of history data, ensure that all data has been transferred to
the file server.
• Be aware of certain side-effects caused by these optimizations on systems on
which the History Buckets feature is enabled.
Upgrading from any pre-6.3.1 version to 6.3.1. and later:
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• No history data is deleted during the upgrade process.
Upgrading from version 6.3.1 or 6.4.2 to any later version:

process.
Upgrading from version 6.4.2.1 to 7.0:
• All history data present on the flash memory for the Policy, Regulator, Shaper,
SOAM DMM and SOAM PL is deleted during the upgrade process.
ATRC-7572 Y.1564 one-way flows must be received on the same SAT server port
If one-way test flows from multiple Y.1564 generators are sent to a SAT server (i.e. a
remote unit), all flows must terminate on the same physical port. For example,
terminating eight flows on one port and eight other flows on a different port is not
supported.
ATRC-7028 No VLAN information in LLDP frames

LLDP frames sent by the unit only contain the interfaces’ IP address and index values.
Information on the interfaces’ VLAN settings is not available at this time.
ATRC-6906 RFC-2544 monitors are not independent

When using both RFC-2544 monitors in bypass mode to monitor Layer-2 and Layer-3 test
traffic flows, both monitors will report the Layer-3 flow statistics. If the monitor
configured for Layer-2 is disabled, the other monitor (Layer-3) does not report any
statistics.
ATRC-6869 Obtaining the UTC offset from the PTP master is not supported
The option to obtain the UTC offset from the PTP master is not yet supported. As such,
the offset provided in the announce messages from the PTP master are not applied to the
time information on the unit. Only the locally defined UTC offset can be used.
ATRC-6846 IPv6 router-advertised addresses are lost when configuring other addresses
After an interface has configured itself with one or several addresses from IPv6 router
advertisements, configuring any other address (whether static or DHCP) will flush the
router-advertised addresses.
This is the intended implementation, since configuring a static IP or enabling DHCP
supersedes the router advertisements.

ATRC-6758 Higher number of Y.1731 frames sent over a period

The number of Y.1731 sample frames (CCM, DMM or SLM) sent over a period can be
slightly higher than expected.
For example, if SLM is configured with an interval of 100 ms and a period of 60 seconds, it
is possible that 601 or 602 samples will be sent during the period instead of 600. This is
caused by a rounding issue related to timer division.
This issue does not lead to packet loss or inaccurate delay results; it is merely a variation
of the number of samples sent over a period.
ATRC-6672 Plug & Go ring protection from customer beacon

When a new unit is added to a G.8032 ERP ring and is in the process of being provisioned
using the Plug & Go feature, it is important to ensure that no foreign beacons enter the
ring from the UNI side (e.g. from a customer). Taking this measure prevents the new ring
unit from being provisioned by the wrong beacon.
ATRC-6604 Web interface may be slow with Mozilla Firefox version 14.0.1 to 22
When using the Mozilla Firefox Web browser version 14.0.1 to 22 to manage the unit, the
response time can sometimes increase, which makes the Web interface slow to operate.
Workaround: Use Firefox version 23 or higher.
ATRC-6509 LAG-Protection: ETH-CSF cannot validate port state on LACP-based UNI links
If enabled, ETH-CSF cannot validate the link status of an LACP-based protected UNI link.
Under such circumstances, the remote fault cannot be propagated. Since ETH-CSF is
based on link-status and LACP is based on signaling, it is currently impossible to indicate
to CSF that the link is logically down, yet still physically up.
ATRC-6425 CLI traceroute command does not support all listed options
The CLI traceroute command does not support the following options:
• -q (number of queries)
• -s (source IP address)
• -g (gateway)
ATRC-6132 VSP reflector responds to invalid MAC addresses on the management port
The V-NID reflector functionality is only intended for use on traffic ports, not on out-of-
band management ports. However, the out-of-band management port will reflect any
ETH-VSP frames it receives. While traffic ports only reflect VSP frames that match the
port’s specific MAC address, the out-of-band management port will reflect VSP frames
that match the MAC address belonging to any of the unit’s ports (MAC range).

ATRC-5790 EVC Mapping: “Preserve VLAN - New CFI/PCP” limitations

When setting EVC Mapping to “Preserve VLAN - New CFI/PCP”, the following limitations
should be taken into consideration:
• DSCP/IP Precedence information is not extracted from triple-tagged frames.
• DSCP/ IP Precedence information is not extracted from 802.2 SNAP/LLC frames.
• DSCP/ IP Precedence/PCP information is not extracted from S-VLAN (0x9100)
tagged frames, unless 0x9100 is set globally as the default S-VLAN Ethertype.
This EVC mapping action can corrupt untagged frames. Therefore, a filter matching at
least one VLAN must be used to ensure the classified frames are tagged.
ATRC-5646 EVC mapping actions that modify VLAN tags must not be used with untagged
traffic
EVC mapping actions that involve replacing or modifying a VLAN tag should not be used if
the traffic is untagged. These EVC mapping actions are:
• Replace
• Pop & Replace
• Preserve VLAN – New CFI/PCP
Performing VLAN modifications on untagged traffic could result in altering the frames.
There is no traffic policy validation to enforce the presence of a VLAN filter with these
EVC mapping actions. You must therefore ensure that any policy using these EVC
mapping actions is configured with a VLAN filter.
ATRC-5474 Frame count statistics may be inconsistent if SLM is disabled in mid-period

If an SLM instance is disabled in the middle of a reference period, the ETH-SLM and
ETH-SLR frame counts shown in the MEP statistics may not be consistent with those
shown in the SLM statistics. This is normal, as the information may not have been
refreshed at the very moment when the SLM instance was disabled.
This behavior is a normal consequence of disabling the SLM instance during a period and
is by design. SLM functions as expected in continuous operation.
ATRC-5364 CPU-destined ingress traffic can be processed on an LACP link while not in the
collecting/distributing state
When using LACP status-based protection, CPU-destined traffic received on a port can be
processed by the software even when the local (actor) LACP link status is not in the
collecting/distributing state. This situation applies to CFM traffic (LBM, LTM, DMM, CCM,
etc.), PAA traffic and L2PT traffic.

ATRC-5254 Web session does not time out if automatic refresh is enabled
The active session of the Web interface will never time out if automatic refresh is enabled
in a page.
ATRC-5197 ARP Requests are sent out on a port when interface is disabled
Many ARP requests are sent out on a port even if the interface associated with the port is
disabled.
ATRC-5196 “cfm show statistics” CLI command shows incorrect RDI and CCM sequence errors
This CLI command does not accurately report the count of CCM sequence errors. This
information can be displayed using the cfm show mep statistics command.
ATRC-5107 Users without “Policy” permissions can clear policy statistics in the Web interface
Users are currently able to clear the Policy statistics in the Web interface (but not in the
CLI), regardless of their assigned permission settings.
ATRC-4560 CLI: CFM naming convention (MEP, Pkt-loss, DMM)

When assigning a CFM name to an instance in the GUI, the name must not be composed
solely of digits; CFM names must always include at least one letter. If the name contains
only digits, the CLI interprets the name as an instance index.
ATRC-4076 SCP -z option not working with certain servers

Certain SSH servers, such as Solaris and several Linux enterprise versions, do not support
the SCP -z option to specify the username. Once the SCP fails, FTP no longer functions
since it uses the same process. The CPU must be restarted for FTP to function.
This issue is related to how the SSHd server is configured. Servers are usually configured
to use PAM (Pluggable Authentication Modules) for account and session management.
SSHd can also rely on PAM for authentication; PAM then executes its authentication
scheme based on its configuration for that login method (for example: /etc/pam.d/sshd).
Configuring Response Authentication:
• With OpenSSH, ChallengeResponseAuthentication in /etc/ssh/sshd_config should
be set to No.
• On Solaris, PAMAuthenticationViaKBDInt in /etc/sshd_config should be set to No.
Alternate Solutions:
• Change the PAM configuration for SSHd (expert).
• Use a public key authentication.
Modification Procedure:

• Solaris:
o Log in with administrative privileges.
o Edit file /etc/ssh/sshd_config to set PAMAuthenticationViaKBDInt to No.
o Save file and exit.
o Restart service: svcadm restart network/ssh.
• Ubuntu Linux (OpenSSH):
o Edit file /etc/ssh/sshd_config to set ChallengeResponseAuthentication to No.
o Restart service: sudo service ssh restart.
ATRC-3533 SyncE is not supported with copper SFP

Copper SFPs use the internal 25 MHz oscillator instead of the SyncE recovered clock.
Consequently, SyncE is not supported for copper SFPs.
ATRC-3285 Web browser refresh deletes the current search filter

Using the browser Refresh command (F5 or Ctrl+R) does not only refresh the page
values, it also reloads the page completely. Doing so eliminates any search filters that
were entered. This behavior is considered normal.
3.4 MIB Changes

None

AC-22907 SW Watchdog Enhancement

Enhancements to watchdog software to monitor additional functionalities that could block or
impact normal operation. Added robustness in case such errors occur that will restart the
device and avoid having to send a technician on site.
AC-22977 Elements: TACACS+CHAP and ASCII

TACACS+ now supports ASCII and CHAP authentication methods.
The user will have to modify the user interfaces (CLI/WEB) to support this new
authentication method. And The TACACS+ is used for user authentication purposes only
in Accedian platforms.
AC-20904 Generate a trap when Clock class Changes in SyncE and PTP
When advertising a new clock class a trap will now be generated and provide the new
clock class.
AC-23039 Accedian MIBs Include Flex 100 sub OIDs

Enhancements to include Flex 100 sub OIDs in Accedian MIBs.
AC-23037 Web help removed from firmware deliveries

The web help is no longer available through the user interface and has been added to the
new documentation platform: docs.accedian.io. This new platform is searchable and
provides access to all web help as of release 7.9.3. Previous versions can be located within
older firmware or on salesforce.

AC-23593 Need to remove the fake IP address configuration on layer-2 interface for PTP-BC
This fake IP was unnecessary and lead to confusion. Need to remove the IP address.
AC-22137 Reboot after rollback version was loaded with the current configuration
Performance element using the back up firmware after a reboot had a database mismatch
after loading current configuration.
AC-22134 LAG status automatically enabled after NID reboot

When Port LAG-1 and LAG-2 on GTS NID was disabled after NID reboot, both LAG ports
were enabled automatically.
AC-22046 Y.1564 Generator rate layer-2 test duration performing shorter than expected
testing period
When running the Y1564 test suite with layer 2 rate Performance test duration:1440
minutes, the test was 44 minutes short from the 24h full period it was supposed to test.
AC-21989 Loss shaping queues and profiles (ERP)

Unable to default select queuing profile in policy configuration during deployment and all
queues were lost.
AC-21716 Traffic shaping configuration loss after restart and unit came back
Restarted system after traffic shaping configuration loss and version went from 7.8.2.1 to
7.1.1.7.


Important Notes

port.
AC-24052 Unable to send file after upgrade due to syntax change

After upgrading to 7.9.1 or 7.9.2, the SCP is no longer able to send files, reporting the
following error: Code = 3: URL using bad/illegal format or missing URL.
Workaround: Customer needs to edit the URL after upgrading to 7.9.2 or 7.9.3.
AC-20838 ERP ring using CFM with VLAN does not work when applied to the port with RPL
link
The ERP ring, using CFM with VLAN, does not work when applied to the port with the
RPL link and therefore CCM is not received.
Workaround: Use releases before version 7.7.
AC-22752 TWAMP Sync issue when reflector is an Accedian device with 6.4.x software or
older
A sync compatibility with older software will cause a sync error when generating
TWAMP towards a device using older software (ex: TE device). The impact is the

absence of one-way delay measurement. There is no workaround available for this

issue.

two flows.
pages.




level in the frame.

0x9100



value:
frames:
• Link OAM
• LAMP
• LACP
necessary.



to Green or Yellow.








or
compatibility.
Preferred syntax:

configured for ERP.





the file server.
process.

process.
supported.


statistics.



• -g (gateway)


traffic
• Replace
• Pop & Replace


in a page.
disabled.


be set to No.

• Solaris:


4.4 MIB Changes

None

AC-20406 Enhanced Software Behavior in Detecting 1000B-T SFP Speed

A generic SFP detection mechanism for all Copper SFPs has been implemented to avoid
the exception list method and to complement the existing SFP speed override function
implemented for fiber SFP.
It is recommended to use the SFP Speed Override feature to configure the port speed for
Fiber SFPs and Copper SFPs. When the port speed/rate is overridden, the configured
value will be persistent.
AC-20865 AutoNEG Off

This feature was designed to adapt Accedian Performance Elements with other networking
units that is not supported ANEG by default in 1G interface.
Accedian units have now enabled ANEG by default and this change will avoid the ports
going down when they first connect and user intervention is required every time when
the connection is changed to get the link-up.
This feature helps to solve this issue by silently setting the local ANEG in PHY to be
ON/OFF based on the partner ANEG:
When the Accedian PORT is configured with ANEG enable, If the signal of partner ANEG
is not detected and the link is sane (no errors detected) the software will bring the link-up
by updating the local ANEG in PHY to be OFF.
The feature will not change the user's ANEG configuration to be disabled. The customer
can change the port connection later on and the PORT will be able to link-up again.
Please note that some functionalities using auto-negotiation advertisement as a
prerequisite will not work properly if the ANEG silently is disabled, these include:
• The protection with link-status mode.
• The Link Loss Return.
AC-20881 Update OpenSSL Library

The new OpenSSL requires the CURL library version 7.73, which has a major impact to
dealing with IPv6 addresses. The following details have been impacted:
• CURL 7.37: The [] style is not a MUST. A warning will pop up.
• CURL 7.73: The [] style as expressed in [RFC3986] must be used. An invalid url error
message will pop up and action is canceled.
The following has also been introduced to the new OpenSSL Library:

• TLSv1.3 (new compared to 1.0.2o):

o TLS_AES_256_GCM_SHA384
o TLS_CHACHA20_POLY1305_SHA256
o TLS_AES_128_GCM_SHA256
o TLS_AES_128_CCM_8_SHA256
o TLS_AES_128_CCM_SHA256
TLSv1.3 includes major changes and for this reason, some things may work very
differently. A brief, incomplete, summary of some things that you are likely to notice
follows:
• There are new ciphersuites that only work in TLSv1.3. The old ciphersuites cannot be
used for TLSv1.3 connections.
• The new ciphersuites are defined differently and do not specify the certificate type
(e.g. RSA, DSA, ECDSA) or the key exchange mechanism (e.g. DHE or ECHDE). This
has implications for ciphersuite configuration.
• Clients provide a “key_share” in the ClientHello. This has consequences for “group”
configuration.
• Sessions are not established until after the main handshake has been completed.
There may be a gap between the end of the handshake and the establishment of a
session (or, in theory, a session may not be established at all). This could have impacts
on session resumption code.
• Renegotiation is not possible in a TLSv1.3 connection
• More of the handshake is now encrypted.
• More types of messages can now have extensions (this has an impact on the custom
extension APIs and Certificate Transparency)
• DSA certificates are no longer allowed in TLSv1.3 connections
Note: Only TLSv1.3 is supported at this time, therefore there is no OpenSSL to support
DTLSv1.3 at this time.
AC-20566 PTP Boundary Clock on the LX (Class-B) including OC Multicast Mode

Accedian is delivering clock transport functionality in its LX-SY platform. This new feature
highlights some changes in the Synchronization functionality applicable to the LT/LX platform.
In order to achieve this functionality, some low-level functional changes have been made.
These changes affect both Software and FPGA components.
The changes include:
• Enhanced Timestamp accuracy
• Enhanced clock servo functionality
• Enhanced Synchronization software stack (PTP, NTP, GPS)

As the LX-S product shares the same platform design with the LT-X products, these changes
apply to all products in the platform.
• LT-X
• LX-S
• LX-SY
These changes are improvements that have been introduced carefully to keep backward
compatibility with previous implementations; there is still a possibility some customers might
report differences in behavior compared to the previous versions of the firmware.
Differences Include:
• Servo Clock functionality:
o This functionality is in charge of adjusting both the frequency and phase of
the slave packet clock in function of the measured time offset between the
local unit and the master source (NTP, PTP, GPS). The servo clock has been
replaced by a more performant implementation.
Possible Negative Effects (or Known Limitations):

• The convergence time may be longer than in the previous firmware versions under
some circumstances.
• PTP Stack:
o The PTP stack has been upgraded in the mentioned platform. New UI is
available to the entire platform. CLI and configuration backward compatibility
is offered to simplify the upgrade from previous firmware versions.
• New UI and commands are introduced.
• The rates at which the packets are transmitted have been normalized to 2n for all
packet clock functionalities (ntp and ptp).

AC-18313 Y.1564 FLR criteria is confusing for the users

In the Y-1564 test, the FLR criterion is unclear, and additional information about the scale
of the value would be useful for the user.
AC-19736 Continuous syslog of laser bias current low and high alarm when the port is down
due to fault propagation in 1G optics
Customer observed the following alarms: "SEVERITY: informational (nsa), MSG: SFP-8
laser bias current high warning" when the port goes into fault propagation.
AC-20416 Unusual log reported “Server write error: wanted 20 got -1”
After installation or upgrade, customer reported the following unusual log - Server write
error: wanted 20 got -1.
AC-20510 Periodic log is flooding the syslogs

Customer reported the following log (appearing every hour) is flooding the syslogs:
FLASHD: Config changed /flashmond_bootrefresh.conf
AC-21752 Power Supply OID for devices

Customer is not able to get status of power supplies using snmp.
AC-4316 Cannot create the second VCA when 2 Operator’s TPID are different
When Operator1’s TPID and Operator2’s TPID are different, only 1 VCA will be successfully
created. In this scenario, a second VCA cannot be created. This is a limitation of the
VCE/VCA model and it will result in the following error message: “This platform doesn’t
support this feature”.

AC-4324 Flow-1 automatically switches back to out-of-service mode during upgrade

process
When upgrading the performance element from a pre-7.7 release, if both RFC2544 flows
were enabled, then the “Flow type” field in the “First flow profile settings” will be
automatically reconfigured to the “Out-of-service” state as part of the upgrade process.


Important Notes

e.g. ACC_7.X_YYYY.afl. This file contains the firmware for the GT, GX, LX and LT
port.
AC-22217 PTP-BC noise transfer performances limitation

PTP to PTP noise transfer does not fully meet ITU-T G.8273.2 Clause 7.3.
The Pk-Pk output goes slightly over the maximum value. Two failed values are
217.80 and 232.03.
SyncE to PTP noise transfer does not fully meetITU-TG.8273.2 Clause 7.3.2. ThePk-Pk
output is greater than the maximum value specified. E.g. 2 failed cases are679.86 > 625
and 662.74 > 555.
AC-22718 Intermittent IPC issue found on usoam

The current LX PTP-BC solution does not meet the Synce to PTP Transient Response
performance criteria, as usoam will intermittently show an IPC error while creating the
MEP in automation test.
AC-22779 [PTPv2] Clock selector in SyncE does not switch to Secondary source port when
disabling the Primary source port
On LX with SyncE (LX SY), the SyncE Clock Selection status is updated incorrectly when
the ESMC QL mode is disabled. If the Primary port is physically lost or the link down and
the Secondary port is still up, the Clock Selection is changed to Holdover, instead of

Secondary. This is a display issue in UI (CLI, WEB). The SyncE state and its functionalities
are still working properly in the hardware layer.
AC-22784 PTP-BC: Transient Response performances not met at the first running after
reboot
After rebooting the unit, the first PTP transient response test fails. The test passed when
running the test a second time.
AC-21802 [PTPv2 G8275.1] Error message not being raised when passing unsupported
parameters in CLI
When adding a new PTP port by CLI command with unsupported parameters (ex: dscp,
unicast-renew-interval, ttl), the command is executed successfully without any error
message.
AC-21754 [PTPv2 G8265.1] Unable to become slave after IPv6 VLAN connection re-
established
T-Vlan to C-Vlan, delete interface
configuration.
AC-21895 [7.9.2 PTPv2] Default Profile: The PTP Master port should not work after deleting
interface
T-Vlan to C-Vlan, delete interface
configuration.

two flows.

pages.



level in the frame.


0x9100


value:

frames:
• Link OAM
• LAMP
• LACP
necessary.



to Green or Yellow.






or
compatibility.
Preferred syntax:



configured for ERP.





the file server.
process.
process.

supported.


statistics.



• -g (gateway)

traffic

• Replace
• Pop & Replace

in a page.
disabled.



be set to No.
• Solaris:



5.4 MIB Changes

None

AC-18551 Disregard Pbit in DMM

Disregards Pbit in DMM available in the uSOAM stack by inserting of the Test-Id-TLV in
each DMM packet sent. This TLV is to be used to differentiate DMR flows (in RX) instead
of the currently used p-bit.
AC-17898 Skylight performance element GUI Enhancements

The GUI has been enhanced to make it easier to read, these changes include:
• Deep navy color for the text.
• Changed the font to medium instead of normal or bold.
• Borders are thicker and deep navy colour.
• More space was added between blocks to ensure the GUI is less compact.
• Menu has more space and menu items selected are bolder with shading in the
selected menu tabs.
AC-13822 Support for SyncE G8262.1 on LX platform

LX will support SyncE G8262.1 configuration/inventory.

AC-19850 User Permission “traffic” does nothing

Traffic privilege in the group permission does not seem to do anything.
AC-19432 Transmission path interferes with existing MEP

When using firmware 7.8.3 we cannot configure the same vlan using different Meg
Levels. When creating the MEP, the system returns with the following error:
Transmission path interferes with existing MEP.
AC-18080 RFC2544 Testsuite Fails to start

The RFC 2544 testsuite fails to start. As soon the test is started, it fails at the binary test
with an error message: “Fail to reach peer”.
AC-17830 Software 7.9 restricts creation of PAA with QnQ via the web interface
Software 7.9 does not allow the user to create a PAA with QnQ via the web interface, if
user creates a PAA with 2 VLAN and it will display error message: "ERROR: Invalid VLAN
ID". The CLI is working correctly.
AC-17286 Management unreachable

Management access failed.
AC-16957 Y.1564 test aborts with CIR = 0 and EIR > 0

Software does not allow the user to preform Y.1564 test with CIR=0 and EIR>0.
AC-14277 Y.1564 test result - IR display is not as expected

When user performs a test at 1M with EMIX, the IR in the result is 0.999, which is not
expected.

AC-16539 LACP timeout options clarification request

LACP timeout option descriptions are incorrect in user documentation and on-line web
help.
AC-20341 RFC 2544 testsuite report display issue when test fails
When the test passes, the results display is correct, however when it fails (Binary search
failure (1)) the RX rate (in frames/sec) is greater the TX rate (in frame/sec).
AC-20067 Update online help for Traffic privileges

Online help for traffic privileges stated: Edit/Enable VLAN encapsulation settings:
forwarding. This was incorrect, and should have stated: Edit/Enable VLAN level and
Working Rate settings from the Traffic configuration.
AC-19794 Copper SFP Manual speed at 100 Mbps not persistent

When a copper SFP is inserted on a 7.9 or 7.8.3, speed is configured at 100 Mbps full
duplex, and the device reboot, the port came back down and the speed is changed to
1Gbps.
AC-18313 Y.1564 FLR criteria is confusing for the users

In the 1564 test, the FLR criterion is unclear, and additional information about the
scale of the value would be useful for the user.


Important Notes

e.g. ACC_7.X_YYYY.afl. This file contains the firmware for the GT, GX, LX and LT
port.
AC-11198 Copper LAG port state changes from Up > Dormant > Down instead of Up >Down
while link is disconnected
When a connected link goes down, the port is expected to switch from Up to Down
quickly, however, the port is switching from Up to Dormant and then to Down.

process


two flows.
pages.




level in the frame.

0x9100



value:
frames:
• Link OAM
• LAMP
• LACP
necessary.



to Green or Yellow.






or

compatibility.
Preferred syntax:

configured for ERP.





the file server.
process.
process.

supported.


statistics.



• -g (gateway)


traffic
• Replace
• Pop & Replace


in a page.
disabled.


be set to No.

• Solaris:


6.4 MIB Changes

None

7. Firmware Version 7.9_22663 (2020-03-25)
AC-12571 Web UI branding alignment with other Skylight user interfaces

WebUI colors, logos and product names have been updated to further align with other
Skylight products and user interfaces.
AC-14205 Session cookies should have httpOnly flag

All sensitive cookies, such as session cookies, are issued with the HttpOnly flag unless the
application specifically needs to access the cookie via scripts. This helps ensure cookies are
handled securely.
AC-15723 Skylight performance element Software Robustness Improvement for FPGA

Communication Loss
Robustness enhancement for Skylight element units has been introduced in order to
restore the device operation quickly and not depend on a physical intervention.
AC-11727 Adjustment to Loopback warning message

The loopback warning message will appear if you change the filter or change the timeout
in order to warn the user the action will be traffic affecting.
AC-15557 Tech-support export does not accept “$” in the password

Tech-support export will truncate the password if there is a "$" in the password.
AC-12204 Syslog error when disabling and enabling a port

If running LT or GT 7.8.2.1 factory default configuration, an unusual error message is
displayed when disabling or enabling a port. This is because the system is sending a reply
which is not being received by the calling feature. This issue has been fixed.

AC-13713 Port Phy config loses configuration when copper SFP is inserted after setting
100M fixed speed
When performing a software upgrade on a copper SFP unit, from version 7.1.1.3 to 7.1.1.8,
the Port Link speed changes to 1G even if the current setting 100base. This issue has been
fixed.
AC-14111 RADIUS to authenticate using Skylight but only have Read Only on the NIDs
When connecting to the Skylight 19.06 via a user with Radius credentials and while
connecting to the NID via reverse proxy, you only have “Read Only” permissions; if
connecting via a separate user RADIUS (one for Skylight and one for the NIDS), this
problem doesn’t happen. This issue has been fixed.
AC-15352 Layer-3 RFC2544 JDSU/Acterna loopback on GT does not work

Layer-3 RFC2544 JDSU/Acterna loopback on version 6.4.2.7 was working and reflecting
traffic until upgrading the firmware to version 7.8.1. After the upgrade, the loop was still
being discovered and traffic was not reflected. This issue has been fixed.

Important Notes

port.

AC-11198 Copper LAG port state changes from Up > Dormant > Down instead of Up >Down
while link is disconnected
When a connected link goes down, the port is expected to switch from Up to Down
quickly, however, the port is switching from Up to Dormant and then to Down.

process

two flows.
pages.




level in the frame.

0x9100



value:
frames:
• Link OAM
• LAMP

• LACP
necessary.



to Green or Yellow.

Skylight element: GT/GT-S (7.9) 7.9

Skylight element: GX/GX-S (7.9) 7.9

Skylight element: LT/LT-S (7.9) 7.9
Skylight element: LX-S 7.9



or
compatibility.
Preferred syntax:

configured for ERP.






the file server.
process.
process.
supported.


statistics.




• -g (gateway)

traffic
• Replace
• Pop & Replace


in a page.
disabled.



be set to No.
• Solaris:


7.4 MIB Changes

None

Skylight Element LX v7.9.4 Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Skylight Element LX v7.9.4 Release Notes

Uploaded by

Copyright:

Available Formats

Release Notes

Accedian Networks Inc.

Revision 1 — August 2022 2

1. About This Document ........................................................................................ 4

4. Firmware Version 7.9.3_24427 (2021-12-15) ............................................... 23

5. Firmware Version 7.9.2_24262 (2021-09-24) ............................................ 38

6. Firmware Version 7.9.1_23673 (2020-11-12) ................................................ 57

7. Firmware Version 7.9_22663 (2020-03-25)................................................ 73

Revision 1 — August 2022 3

1. About This Document

General conventions used in all documents

Note: This description cannot be modified.

Revision 1 — August 2022 4

1.3 Related Documentation

1.4 Product Name Changes

Former Name Former Name New Name

antMODULE ant Module Skylight sensor: module 10G

Revision 1 — August 2022 5

Revision 1 — August 2022 6

3. Firmware Version 7.9.4_24917 (2022-08-01)

3.1 New Features and Enhancements

AC-22957 Update dropbear SSH to version 2022.82

AC-22729 ICMP redirect security issue

Revision 1 — August 2022 7

3.2 Addressed Issues

AC-24300 Consolidated interface with ":" unable to show/edit using CLI

AC-22118 Security assessment reported vulnerabilities

These issues have been fixed.

Revision 1 — August 2022 8

AC-22103 LLDP not advertising IP address correctly

Revision 1 — August 2022 9

3.3 Operational Considerations and Known Limitations

 The Skylight element: LX firmware is delivered in a consolidated file prefixed by “ACC”,

AC-24052 Unable to send file after upgrade due to syntax change

Workaround: Use releases before version 7.7.

Revision 1 — August 2022 10

absence of one-way delay measurement. There is no workaround available for this

ATRC-D17907 Missing packets on RFC2544 generator layer-3 (2 flows)

ATRC-D13944 Generator RFC2544 in-service and monitor operate incorrectly

ATRC-D16848 Filter does not catch IPv6 Extension Headers

Revision 1 — August 2022 11

ATRC-D17233 SNMP IPv6 Filtering and Loopback is not supported

ATRC-D15473 The TP-Z-PCP-Mapping does not work properly

ATRC-D05982 Limited availability of the OAM Loopback feature

Revision 1 — August 2022 12

ATRC-D05907 Reserved value no longer allowed in a Y.1731 configuration

Revision 1 — August 2022 13

ATRC-D05446 Slight variation in BLUE queue full/empty threshold percentage values

ATRC-D05382 CoS Mapping: Yellow PCP Out is not mapped to a queue

Revision 1 — August 2022 14

Product Name Firmware Versions

TE-x Performance Element 5.1 – 6.4.3

GT/GT-S Performance Element, now 6.3 – 7.3

GT-Q/GT-QE Performance Element 7.1.1 – 7.3

GX/GX-S Performance Element, now 6.3 – 7.3

10GE CE/NE Performance Element 5.0 – 6.3

LT/LT-S Performance Element, now 6.3 – 7.3

Skylight element: LX-S 7.9.1

FS/FS 10G Performance Element 1.0 – 1.1

ATRC-D04040 Syslog error message at login after configuring RADIUS

ATRC-D03949 Modified syntax for CLI command “bandwidth-generator add”

Revision 1 — August 2022 15

New syntax (6.4 and later):