Professional Documents
Culture Documents
Skylight element: LT
Version 7.9.4_24917 (2022-08-01)
Revision 1 — August 1, 2022
Release Notes Skylight element: LT Version 7.9.4
Publication Information
Skylight element: LT 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:
Tel: 514-331-6181
Fax: 514-331-2210
Toll free: 1-866-685-8181
accedian.comaccedian.com
Table of Contents
1. About This Document ......................................................................................... 5
1.1 Organization.................................................................................................................................................. 5
1.2 Conventions ..................................................................................................................................................6
1.3 Related Documentation ............................................................................................................................. 7
1.4 Product Name Changes ............................................................................................................................. 7
2. Requirements....................................................................................................... 8
3. Firmware Version 7.9.4_24917 (2022-08-01) ...............................................9
3.1 New Features and Enhancements .........................................................................................................9
3.2 Addressed Issues ....................................................................................................................................... 10
3.3 Operational Considerations and Known Limitations ...................................................................... 12
3.4 MIB Changes .............................................................................................................................................. 24
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.3_24427 (2021-12-15)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.3.
Firmware Version 7.9.2_24262 (2021-09-24)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.2
Firmware Version 7.9.1_23673 (2020-11-12)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.1.
Firmware Version 7.9_22663 (2020-03-25)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.9.
Firmware Version 7.8.3_20905 (2019-08-16)
This section provides New Features and Enhancements, Addressed Issues, Operational
Considerations/Known Limitations and MIB Changes, if any, for Firmware Version 7.8.3.
Firmware Version 7.8.2.1_20416 (2019-06-04)
This section provides New Features and Enhancements as well as Addressed Issues for
Firmware Version 7.8.2.1.
Firmware Version 7.8.2_20146 (2019-05-10)
This section provides New Features and Enhancements as well as Addressed Issues for
Firmware Version 7.8.2.
1.2 Conventions
This section explains the conventions that are used in Accedian user documentation.
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.
2. Requirements
This firmware version applies to the following Skylight element: LT, resulting from changes in
the TLS version, the following software versions are compatible with SkyLIGHT Director
Vision 1.3 (now Skylight orchestrator) and above:
• 7.1.1.1
• 7.3.0.3
• 7.4
• 7.5
• 7.6
• 7.7
• 7.8
• 7.8.1
• 7.8.2
• 7.8.2.1
• 7.8.3
• 7.9
• 7.9.1
• 7.9.2
• 7.9.3
• 7.9.4
Note: There is a patch available for earlier versions of Skylight orchestrator. Please
contact Accedian support for further information.
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-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.
This issue has 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.
This issue has been fixed.
AC-21754 Unable to become PTP slave port after IPv6 VLAN connection re-establishment
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.
A good practice is to disable and re-enable the PTP after changing the interface's
configuration.
This issue has been fixed.
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-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-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-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.
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.
• Skylight element: LT
• Skylight element: LX
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-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.
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-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.
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• All history data present on the flash memory is deleted during the upgrade
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.
Upgrading from version 6.4.2.1 to 7.2:
• 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-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.
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-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-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-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.
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.
This issue has been fixed.
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.
This issue has been fixed.
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.
This issue has been fixed.
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.
This issue has been fixed.
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-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-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-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.
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.
• Skylight element: LT
• Skylight element: LX
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-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.
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-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.
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• All history data present on the flash memory is deleted during the upgrade
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.
Upgrading from version 6.4.2.1 to 7.2:
• 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-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.
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-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-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-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.
Note: Only TLSv1.3 is supported at this time, therefore there is no OpenSSL to support
DTLSv1.3 at this time.
AC-16152 Port Phy config loses configuration with 100M fixed speed for Copper SFP
Customer reported Port Phy config loses configuration with 100M fixed speed for others
Copper SFP (not 7SV-000).
This issue has been fixed.
AC-16540 LACP timeout setting not following when going from custom 1000 to sub50
Customer reported LACP does not revert to sub50ms timeout properly when changing
from "custom 1000" to "sub50" setting.
This issue has been fixed.
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.
This issue has been fixed.
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.
This issue has been fixed.
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”.
This issue has been fixed.
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-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-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-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-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-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-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:
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.
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• All history data present on the flash memory is deleted during the upgrade
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.
Upgrading from version 6.4.2.1 to 7.2:
• 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-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-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-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-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.
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.
This issue has been fixed.
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).
This issue has been fixed.
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.
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”.
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-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-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-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.
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.
• Skylight element: LT
• Skylight element: LX
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-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.
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-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.
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• All history data present on the flash memory is deleted during the upgrade
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.
Upgrading from version 6.4.2.1 to 7.2:
• 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-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.
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-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-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-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.
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-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.
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”.
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-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-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-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-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-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-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:
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 test suite: Report displays incorrect unit identifier information
When running the RFC-2544 test suite after modifying the unit identifier (System ▶ DNS ▶
host name), the generated report contains the previous unit identifier.
• All history data present on the flash memory is deleted during the upgrade
process.
Upgrading from version 6.3.1 to 6.4.2:
• All history data present on the flash memory is deleted during the upgrade
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.
Upgrading from version 6.4.2.1 to 7.2:
• 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-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-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-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.
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.
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 Log in with administrative privileges.
o Edit file /etc/ssh/sshd_config to set ChallengeResponseAuthentication to No.
o Save file and exit.
o Restart service: sudo service ssh restart.
AC-11668 Configuration export does not include the updated information of the user
When updating user information (e.g. first name, last name, phone number) then
performing configuration export, this information was not being updated. This issue has
been fixed and the information is now properly updated in the configuration file and device.
AC-7666 Showing IPv6 addresses in Link Layer Discovery Protocol (LLDP) Neighbors
information
LLDP Neighbors information now shows IPv6 management addresses (in addition to IPv4
management addresses).
ATRC-D07991 UNI port flapping issue when FP and CSF are enabled on multiple UNI ports
When Fault Propagation (FP) and Client Signal Fail (CSF) are enabled on a combo port (port
9 to 12) and media selection is set to auto, certain events can cause the UNI ports to start
flapping. This issue has been fixed.
AC-6241 RFC-2544 test suite with frames size bigger than 256 bytes generates low
throughput results
Low throughput results are generated when running an RFC-2544 test suite (working rate
layer-2) with a maximum rate set to 6 Gbps and frame size that exceeds 256 bytes. This
issue has been fixed.
AC-7466 Y.1564 test fails, showing “ERROR: Mismatch between port MTU configuration
and frame size”
The Y.1564 test will fail if there is a mismatch between the port MTU configuration and the
frame size when the frame size type is initially set to “Fixed” and then changed to “EMIX”,
even if the frame size is also reset to match the MTU configuration. This issue has been
fixed.
AC-7494 RFC2544 test suite fails when using same value for maximum and minimum rate
When performing a RFC-2544 test suite using similar maximum and minimum rate, the test
will take a very long time to complete and will fail when it finally does complete. This issue
has been fixed.
AC-7621 RFC-2544 test fails, showing “ERROR: Mismatch between port MTU configuration
and frame size”
The RFC-2544 test will fail if there is a mismatch between the port MTU configuration and
the frame size when the frame size type is initially set to “Fixed” and then changed to
“EMIX”, even if the frame size is also reset to match the MTU configuration. This issue has
been fixed.
AC-7940 Ethertype value in RFC2544 layer-2 always 0x8902 even if a custom Ethertype is
defined
This parameter (Ethertype) is now deprecated and no longer needed. Its syntax remains
valid for backward compatibility and its value is set automatically based on the value of
packet-type. For example: 0x0800 for Layer-3, 0x8902 for Layer-2, 0x88FC for Layer-2
Accedian or Layer-2 generic. This issue has been fixed.
AC-7941 Layer-2 filter set for Ethertype 0x88fc traffic catches Ethertype 0x8902 traffic
This issue occurs because Layer-2 Ethertype 0x88fc and 0x8902 are filtered as the same
value. This issue has been fixed.
AC-8966 Synthetic Loss Measurement (SLM) streaming to SkyLIGHT Director Vision is not
working
When the SLM index is manually configured, starting at a high number (11 to 18, 21 to 38),
streaming to SkyLIGHT Director Vision does not work (no SLM csv file will be produced).
This issue has been fixed.
AC-9126 RFC-2544 test results not showing the exact bandwidth rate
The test suite results throughput display is no longer the integer value. As an example, it
could show 99.999 Mbps instead of the expected 100 Mbps. This issue has been fixed.
AC-9302 SFP statistics data not collected when port-1 is not present
No history data (SFP statistics) is collected when history data is enabled (with filling for
SFP, PORT and System Health enabled as well) if port-1 is not present but other ports are.
This issue has been fixed.
• Changing any parameter from VLAN Settings and/or VLAN in VLAN Settings
(Ethertype, Priority and VLAN ID) of an interface
• Disabling Regular port or LAG port
• Deleting an interface
• Perform OAM Loopbacks (Loopback Enable box checked in OAM Loopback)
• Set loopback with Drop Opposite Traffic enabled
AC-5256 EVC and CoS parameters in CSV file do not match CLI/WEB UI
The following fields in the CSV file do not match the configuration that can be seen in the
CLI and WEB UI:
• EVC Mapping Encapsulation
• COS Mapping Choice 1 Profile
• COS Mapping Choice 1 Regulator
• COS Mapping Choice 2 Profile
• Mapping Choice 2 Regulator
This issue has been fixed.
AC-3860 Using ACL to deny or allow ICMP packets from specific MAC/IP addresses
This release introduces the capability to drop ICMP frames from the network management
interface by using access control lists (ACLs).
AC-4327 Exclude VLAN tags from RFC-2544 test suite frame size
This release introduces the capability to exclude the VLAN tag size from the RFC-2544 test
suite configuration. When excluding the VLAN tag size, the frame length is increased by
the size of the VLAN tag header(s) being added to the frame.
Note: Web browser can restrict the usage of certain reserved ports for security reason. It
is up to the user to select a valid port.
AC-3867 Vulnerabilities when Dropbear SSH Server version is lower than 2016.72
LT, GT and GX performance elements are affected by the following vulnerabilities when
Dropbear version is lower than 2016.72:
• CVE-2016-7406
• CVE-2016-7407
• CVE-2016-7408
• CVE-2016-7409
This issue has been addressed by implementing Dropbear Version 2018.76.
• Supported HMAC algorithms:
o SHA2_256
o SHA2_512
• Supported KEX algorithms:
o curve25519-sha256
o curve25519-sha256@libssh.org
o diffie-hellman-group14-sha256
o diffie-hellman-group14-sha1
o kexguess2@matt.ucc.asn.au
• Supported Ciphers:
o aes128-ctr
o aes256-ctr
AC-4309 Multiple TWAMP generator sessions can cause less packets to be sent
When running multiple TWAMP sessions, it may occur that less packets than expected in
a period will be sent. This issue has been fixed.
AC-4325 SDVM csv files having inconsistent time results depending on product and
grouping period
The csv files should be generated based on the grouping period, streaming period and
device, since different devices and streaming periods will have different time results. This
issue has been fixed.
AC-4340 Layer-2 rate generator allows Layer-1 rate that are higher than 1G
As it is not possible to send a test Layer-2 rate that exceeds 761 Mbps (when using 64-byte
frames) on a 1G line, users should not be allowed to configure a 800 Mbps test Layer-2 rate
(on a 1G line). This issue has been fixed.
AC-4347 ERP Ring - Management bridge leaking into the protected segment causing a
broadcast storm
Broadcast packets are forwarded across a bridge between a traffic port and the
Management port even though the port is blocked due to a “Manual Switch (MS)”. This
issue has been fixed.
ATRC-E03676 Netconf/Yang
Release 7.7 introduces the Netconf/Yang feature. This feature provides service providers
the ability to perform basic service provisioning and receive notifications by configuring a
Netconf agent. This feature supports:
• Port configuration
• Port statistics
• Traffic policies
• Traffic filters
• System configuration
• System alarms
• Traffic regulators
• Traffic mapping
• Traffic shaping
• Traffic vlan
• Traffic monitors
• Traffic configuration
• Netconf: State & Timeout
• Notification for Alarms
• SOAM CFM
• System agent
• System session
• SOAM TWAMP
• VCE/VCA
• PAA
• SOAM SA
• Plug & go
ATRC-B20549 System Monitoring
System Monitor allows for the monitoring, logging and alerting of system resources (CPU,
Memory and Disk Usage) and Network statistics. This feature can be enabled or disabled.
Three Probes can be configured when System Monitor is enabled:
System Probe, to measure and report on CPU and memory usage as well as number of top-
level processes.
• Disk Probe, to measure and report on disk usage.
• Network Probe, to report statistics (packets sent/received, bytes sent/received)
about currently active network devices. The Network Probe can only be used in
• Debug mode and does not have any threshold limits.
ATRC-D17296 CPU usage history graph will not show on Firefox web browser
The CPU usage history graph is not displayed when the Firefox web browser is used to
access a performance element Web GUI.
ATRC-D17292 No error message when editing the VCE_Tunnel with an invalid configuration
through CLI
When a user tries to specify the physical ID, the request will be ignored as the port is
internal and is set to an internal value. No error message will indicate that behavior.
ATRC-D17490 LTS 10G ports: auto-nego command should be removed from the CLI
The LTS 10G ports do not have the auto nego option in the web interface but this was
present in the CLI. This command has been removed because it created confusion.
ATRC-D17539 Fan aging test timeout to be increased to 300 seconds instead of 60 seconds
The new fan test timeout period has been increased to 300 seconds from 60 seconds, as
per specs of fan.
ATRC-D17162 Redesign the loopback drop opposite traffic to prevent accidental usage
The default value has been changed from 0 to 30 min and timeout value range is now 0-
1440 min. If Drop-opposite traffic is Enabled user will receive a pop-up message: “Drop-
opposite traffic will drop all the traffic entering the device on the opposite port.” If Loopback
is Enable another message will show: “Loopback is service affecting. Are you OK?”
ATRC-D18038 RFC-2544 L3 flowtype In-service Monitor fails to detect if the Frame has a TTL less
than 255
If the unit is reconfigured to have a TTL value of 254 or lower the Monitor does not count
these incoming frames any longer.
ATRC-E03674 IPv6 Two-Way Active Measurement Protocol (TWAMP) generator and reflector
1G/10G Release 7.6 introduces IPv6 support for TWAMP Lite Generator and TWAMP
Reflector, similar to the current IPv4 TWAMP support on the performance elements.
ATRC-E03675 Component ID
When creating a MA/MEG in SOAM, a new optional parameter has been added to specify
the desired component ID, instead of specifying the VCE name.
When creating a VCE, the user can optionally specify the desired component ID. If not
specified (0), the system will assign an ID.
When upgrading from 7.5, the system will create implicit VCAs for all VCEs of type Tunnel.
As part of the upgrade process, any VCAs containing VCEs of type Tunnel will be
automatically replaced with their corresponding implicit VCAs.
Note: If the maximum implicit VCA count is reached or if the implicit VCA creation would
result in a name clash with an existing VCA, then the upgrade process will skip that VCE
of type Tunnel and a corresponding error will appear in the syslog.
ATRC-D06620 Historical Data: The first period in certain categories may contain inconsistent
values
After enabling historical data collection, either through the History Buckets or Vision Collect
features, the data pertaining to the very first period can contain inconsistent values due to
the counters not being properly initialized. However, all subsequent periods will report
valid, consistent data. This applies only to the Policy, Regulator, Shaper and Port categories.
This issue has been fixed.
ATRC-D15068 Y.1564: Error displayed when running 1-Way configuration test for multiple
service
Corrected an issue where Initial 1-Way Y.1564 test for multiple services would complete
successfully but subsequent attempts would fail with the following error message:
“ERROR: Hardware resource not available for the moment”.
ATRC-D15502 LT-S/GT 7.4 SOAM PAA and SAT Y.1564 do not function correctly together
PAA reports lots of errors on a link between a GT and a LT-S when starting a Y.1564 test
on that same link. This issue has been fixed.
ATRC-D16592 RFC2544 test suite giving wrong results (Generator working rate Layer-2)
If a test is configured at Layer-2 and the port where the test is going to be originated from
is at 100Mbps, the test suite starts and passes giving wrong values. This issue has been
fixed.
ATRC-D16679 Incorrect decoding of the Reply Ingress TLV in LTR packets prevents the LTM test
from working
The incorrect decoding and validation of the Reply Ingress TLV contained in the LTR
response frames leads to the incorrect operation of the LTM test. This occurs when the
entity replying to the LTM packets adds its Ingress Port Id attributes in the Reply Ingress
TLV.
This issue has been fixed.
ATRC-D16831 Creating a VCE external to external with a long name results in implicit VCA errors
The maximum VCE name size and the maximum VCA name size are 58 characters not
including NULL space. If a user creates a VCE between two external ports with a name size
between 56-58 characters, an error will occur. The system will try to create an implicit VCA
with name size VCA-VCE_name. This can lead to overwriting VCA data and multiple errors
in system. This issue has been fixed.
ATRC-D17232 Specify in the GUI that CBS and EBS values within Y.1564 tests are for future use
This issue has been fixed in Release 7.6. The CBS and EBS values used for Y.564 Service
Configuration testing are 8 KiB. The system will generate an error message when
attempting to configure a value other than 8.
ATRC-D17245 Getting “error invalid internal loopback timeout” when adding Alias to
management port via Web GUI
Users cannot add any information in the Alias column under Management Port
Configuration. When attempting to do so, users get the “error invalid internal loopback
timeout” error message. This issue has been fixed.
ATRC-D16548 NTP status always shows “synchronized” when enabling the NTP server
Addressed a case where enabling/disabling the NTP server could erroneously display a sync
status of “Synchronized”.
ATRC-E03274 VCE/VCA
A Virtual Circuit Access (VCA) describes a customer’s traffic flow access to the service
provider’s network through the edge performance element. VCAs specify the inward path
(TP A towards TP Z) actions performed at different edge (boundary) points in the network
(the outward path TP Z towards TP A actions are inferred).
A VCA element is formed by an ordered list of one or more individual Virtual Circuit
Endpoints (VCE) elements in order to form an external port-to-external port definition for
the Virtual Connection Access.
The Virtual Connection defines the traffic path to be used by UP MEP and MIP.
ATRC-E03504 UpMEP/MIP
Added support to configure a Down Mep, Up MEP or MIP, on a VLAN component created
via the VCA (Virtual Circuit Access).
ATRC-E03576 Supporting CCM Config Commands for Integration with Provisioning Tool
An enhancement to provide a more user-friendly feature allows CMM Config Commands to
be referenced not just by number but also by name. This enables more flexibility is searching
for the command.
ATRC-D07190 Y.1564: Loss of sync causes one-way tests to fail even when Sync is disabled
When a one-way Y.1564 test is executed without enabling the Mandatory Time Sync
option, a large time synchronization adjustment (NTP or PTP) can sometimes affect the
FDV measurements, causing the test to fail.
Normally, when the Mandatory Time Sync option is not enabled, the test ignores any time
adjustments. Although this issue is rare, it is more likely to occur in a long-duration test
(e.g., 24 hours).
ATRC-B17560 Align TWAMP Generated Measurement Periods to time of day fixed boundaries
A Network Operator would like the option to have the generated reports of TWAMP Gen
with the PAA aligned to the global time boundary. PAA sessions do align to preset time
boundaries.
Example of alignment (hh:mm) of measurements vs reference period for a session:
• 1 minute reference period → measurement timestamps should align with
hh:00, hh:01, hh:02, hh:03.
• 15 minute reference period → measurement timestamps should align with
hh:00, hh:15, hh:30, hh+1:00.
ATRC-B18168 Support for Transport Layer Security (TLS) library version 1.2
The TLS encryption protocol library has been upgraded to version 1.2 across all platforms in
order to protect Accedian products from Denial of Service (DoS) attacks.
ATRC-D10696 Connectivity Fault Management (CFM) alarm status does not update
Under specific race conditions in the CFM fault-handling mechanism, certain alarms could
have remained in the present state, even after the initial condition for raising the alarm has
been successfully cleared.
ATRC-E03101 Add UDP port 862 for TWAMP generation and reflection
The TWAMP feature has been expanded to include UDP port 862 for generation and
reflection. The accepted range of UDP ports now includes 862, as well as any value within
the range of 1025 to 65535.
occasionally become stuck in the idle state and will not send the Signal Fail following the
Clear operation on the ring.
ATRC-D10386 Adding SA metric source names that start with a zero no longer results in error
Adding SA metric source names that began with a zero would result in the following error:
“invalid metric source”.
ATRC-D08684 Upgrading the firmware through the Web interface would fail
When using the Web interface to upgrade the firmware, the upgrade process would
terminate unexpectedly and fail to upgrade the firmware.
ATRC-D08515 Filter VLAN stack size attribute was ignored if either vlan1-ethertype or vlan2-
ethertype attributes were set
When defining a filter, if a value was specified for the vlan1-ethertype or vlan2-ethertype
attributes, the value of the VLAN stack size attribute would be ignored.
ATRC-D06908 LACP would not recover from rapid switching back and forth
The LACP state machine has been adjusted to be more responsive to link up events.
ATRC-D05526 LAG revertive feature and WTR logic would cause traffic loss when failed over in
specific scenario
LAG protection was waiting for full Wait to Restore period to switch over to primary link,
even though secondary link falls into fault state: now the Wait to Restore time is bypassed
when a fault is detected on the secondary active link.
ATRC-D03774 LACP: Forwarding to Ring LAG was permitted while in Defaulted state
The IEEE802.1AX standard specifies that no Tx/Rx traffic should be allowed in an
LACP-based link if it is not in the Collecting/Distributing state. The implementation
previously allowed forwarding frames that were in the Defaulted state from an
LACP-based LAG to an ERP-based LAG.
ATRC-D03378 Creating a second ring on a pass-through NID is causing traffic disruption on the
first ring
Previously, updating the classification engine required a temporary disable of the rules logic.
This has now been changed to support no hit updates.