Anda di halaman 1dari 19

Accedian Networks

4878 Levy street, suite 202


Saint-Laurent, QC, H4R 2P1
Canada
Tel.: (514) 331-6181
www.accedian.com

Release Notes
MetroNID™ Release 5.2.1.2_19888
(2011/04/21)

Overview

The Release Notes cover the requirements, important notes, new features and changes,
addressed issues and known limitations for MetroNID™ Release 5.2.1.2

Please read all the notes prior to installing this release.

For more information, please see the MetroNID™ Administrator‟s Guide.

Requirements

This release and release notes document apply to the following models from Accedian
Networks Inc.:
 MetroNID™ TE-R (AMN-1000-TE-R)
 MetroNID™ TE-S (AMN-1000-TE-S)
 MetroNID™ TE (AMN-1000-TE)
 MetroNID™ TE-RS (AMN-1000-TE-RS)
Note: Changes described in this section capture developments since firmware Release
5.0.2

Release 5.2.1.2_19888 (2011/04/21)

New features and enhancements


None

Addressed issues

ATRC-4523 Message on console while editing interface configuration


When editing interface, the NTP communication with the NTP server is lost temporarily
until the interface is up aging. This caused the error message on the console. The error
message was removed on the console.

ATRC-4580 Factory reset using reset button or CLI does not have the
same behavior
The factory reset using the reset button does not have the same behaviour than the CLI.
When using the reset button, the OEM configuration is not applied. The CLI has the
desired behaviour where the OEM configuration is applied.

Operational Considerations

 When computing the local time, TAI offset is now added to the UTC time (factory
default value for TAI offset is +34). This requires additional validation of TAI offset
compatibility when new units that run 5.1 firmware or higher are added to an
existing network (see ATRC-3749 for details)

ATRC-4076 SCP not working with some servers


Some SSH servers do not support the SCP –z option to specify the user name. This is
the case with Solaris and some Linux enterprise version. Once the SCP failed, FTP is no
longer working since they are using the same process. The CPU needs to be restarted for
FTP to work.

ATRC-3284 Chrome web browser not supported


Google Chrome web browser not supported. The Chrome web browser implementation is
not compatible with our web server implementation and cause a lot a delays refreshing
the web pages and auto-refresh was not working properly.

ATRC-3533 Sync-E not working with Copper SFP


Copper SFP are not using the Sync-E recovered clock but the internal 25 MHz oscillator.
This makes the Sync-E not usable with copper SFP.

ATRC-3637 When modifying a filter, the OAM loopback is still using


previous value
When editing an existing filter, the changes made are not applied to Loopbacks in use
when you click Apply. If you want those loopbacks to use the modified Layer-2 filter,
you need to disable the loopback and re-enable it

ATRC-3285 Web browser refresh deletes the current search filter


Using the browser‟s Refresh command does not simply refresh the values or list shown
in the page, it reloads the page completely, eliminating any filter that was applied.

ATRC-3191 CFM link trace initiated by Up MEP ignore egress port MIP
configuration
A link trace initiated by an Up MEP must be queued to the link trace responder instead of
being transmitted directly to the egress port. This problem can be seen where a MEP and
a MIP are configured on the same NID.

ATRC-3767 RFC-2544 test suite without filename is undeletable and


not editable
When creating a RFC-2544 test suite without specifying a filename, the test suite
becomes undeletable and it is not editable.

ATRC-3169 Wrong number of CRC error detected on the received path


after packet truncation
If we attempt to pass a frame larger than MTU, the frame is truncated and propagated
with a non-valid CRC value. On the return path, the modified frame will produce two
errors: CRC and PHY.

ATRC-3457 RFC-2544 minimum packet size not restricted when using


QinQ over Layer 3
When performing layer 3 with QinQ using the generator or the RFC-2544 test suite, the
minimum packet size should be greater than 68 bytes.

ATRC-3548 Bridge configured with beacon, inventory is empty


When the Advertisement frame filtering option is enabled in the inventory page, the
inventory ignores advertisement frames coming from interfaces which do not have the
beacon enabled. The purpose of this was to be able to ignore advertisement frames
coming from unwanted ports. In order to catch all advertisement frames coming from
the bridge sub-interfaces, the beacon state must be specified on sub-interfaces.

MIB changes
None
Release 5.2.1.1_19590 (2011/04/04)

New features and enhancements


None

Addressed issues

ATRC-2198 LACP configuration change required a system reboot


Changing the LACP configuration required a system reboot. The configuration can now
be changed without a system reboot.

ATRC-4420 LACP protection not working


The LACP protection was not working. The protection mechanism was broken with the
introduction of link protection on the MetroNODE. The LACP protection is now working as
expected.

ATRC-4422 NTP server with GPS disabled


The GPS functionality was disabled and the NTP server could synchronize with the GPS.
The functionality was re-enabled.

ATRC-4424 Inventory show API with EchoAgent exceeded buffer size


and caused error
The inventory show API with EchoAgent used a limited buffer size. When the number of
units in the inventory reached the maximum buffer size, the inventory show caused an
execution error. The API with EchoAgent has been redesigned to allow an infinite
number of units in the inventory.

ATRC-4474 Included EchoAgent 4.9.2 r9757

ATCR-EA-1227 EchoAgent inventory show API exceeded buffer size


and caused error
The inventory show API used a limited buffer size. When the number of units in the
inventory reached the maximum buffer size, the inventory show caused an execution
error. The API has been redesigned to allow an infinite number of units in the
inventory.

MIB changes
None
Release 5.2.1_19416 (2011/03/22)

New features and enhancements

ATRC-4202 RFC-2544 testsuite report does not report the type of


layer-2 tested
The testsuite was not reporting the type of layer-2 tested. Instead the web GUI reported
the ethertype and the opcode. The web GUI now reports the layer-2 tested.

ATRC-4374 Include EchoAgent 4.9.1


Added the new EchoAgent 4.9.1 supporting EchoVault release 4.9.1

Addressed issues

ATRC-4348 Firmware upgrade temporary file


When upgrading a firmware older than 5.2 with a firmware older than 5.2 and the
upgrade is aborted. Trying to upgrade afterward with release 5.2, the firmware upgrade
failed. The system needed to be rebooted before executing the upgrade. This was
caused by a temporary firmware upgrade file created in RAM. The file is incompatible
between releases and must be deleted before starting an upgrade. The temporary file is
now deleted before executing a firmware upgrade.

ATRC-4394 ACP discovery configuration is updated every time a


beacon is received
The ACP discovery configuration is updated every time a beacon is received. The
configuration is now updated only when the beacon contains new configuration
parameters.

ATRC-4374 Included EchoAgent 4.9.1 r9669

ATCR-EA-1205 EchoAgent Reset enters an infinite loop and takes all


available CPU in case Agent has never been initialized
When a user issues EchoAgent Reset and the Agent has never been initialized
(enabled) the reset clean-up process utilizes all available CPU resources and does not
recover from this state without a restart of the system. This is because the Agent
tries to remove a directory that has not been created yet. This special case has now
been addressed properly.

ATCR-EA-1196 EchoAgent prints incorrect error messages with two


port version of MetroNODE when parsing port names
Each time an EchoAgent process is restarted, for instance during reset or
communication problems, the following error messages are incorrectly printed:

Error:acdPortdConf:readPorts: Could not read mac for (null).


Error:acdPortdConf:readPorts: Unknown interface 6
Error:acdPortdConf:readPorts: Could not read mac for (null).
Error:acdPortdConf:readPorts: Unknown interface 5

This happens on two ports MetroNODE. This issue has now been fixed.

ATCR-EA -1211 ATCR-EA -1211 EchoAgent creates incorrect error


message when provisioning RFC-2544 testsuite
EchoAgent, RFC 2544 Testsuite provisioning error message is incorrectly not created
for missing Interface / Network Label, if the destination Network Label is for example
removed by the user through EchoVault UI, and the EchoAgent provisioning process
is restarted by configuration change. This issue has now been fixed.

ATCR-EA -1191 EchoAgent, only partial collection of SLA-Meter


Y.1731 metrics are realized in Hub and Spoke topology
while bidirectional data is expected
When bidirectional performance data collection for Y.1731 is set and topology is Hub
and Spoke, the results from measurements toward the spokes are not collected. This
issue has now been fixed.

ATCR-EA -1157 EchoAgent, Service Creator and Regulator stats


reports incorrect values if EchoAgent data collection
process is restarted
Service Creator and Regulator stats policies report incorrect values in case an event
causes the EchoAgent provisioning and data collection process to restart. Restarts
occur when test configurations change. This issue has now been fixed.

ATCR-EA -1165 EchoAgent: Invalid RFC-2544 testsuite destination


parameters creates 14 extra error messages
There are 14 extra error messages if there is an attempt to create a test suite
destination with an invalid parameter. This issue has now been fixed.

ATCR-EA -1177 EchoAgent, the incorrect status is sent once after a


'Not Associated' status
After a 'Not associated' status code has been sent (e.g. after a bad connection) one
incorrect status code 'missing sample(s)' is sent. The incorrect status is sent with
one reporting interval only. This issue has now been fixed.

MIB changes
None
Release 5.2_19068 (2011/03/09)

New features and enhancements

ATRC-3691 Added level in ACP tunneling


The ACP frames level. This level is used in transmitted advertisement and beacon
frames. A unit receiving a beacon frame will automatically set it's system ACP level to
the one included in the beacon frame. The choices are:
0–7: for a specific level. The ACP frames level defines how far the ACP frames can go.
A unit requires a higher level to be used to run „above‟ a lower level. For example, a
unit using ACP frames level 3 will be able to reach another unit if the other units in
between have an ACP frame level of 2 or below.
All: All ACP frames will go through this unit without processing.

ATRC-3841 MEG name can be configured with 45 characters long


To comply with ICC standards, the MEG name should be 13 characters or less. However,
the system will allow you to enter up to 45 characters for MEG name. In the case of a
MEG name more than 13 characters long, the CCM is generated with a non-compliant
MEG ID field.

ATRC-3855 VeEX discovery process and loopback procedure support


Add the support for VeEX discovery process and loopback procedure. The layer 2, 3, and
4 are supported.

ATRC-3904 Increase regulator sets to 60 on TE-R


Increase the number of regulator sets on TE-R and TE (4x1 mode) to 60.

ATRC-3759 Add GPS coordinates


When the GPS functionality is enabled, the GPS coordinates are reported and available in
both in Web and CLI.

ATRC-4048 Fault propagation configuration


The fault propagation configuration in the Web interface is re-located in the individual
port configuration page. Previously, it was configurable in the port main page. NOTE:
The two-way fault propagation configuration is now done differently. The two-way fault
propagation configuration is done by configuring both ports in one-way fault
propagation.

ATRC-4090 Increased the number of L2PT rules


The number of L2PT rules was increased from 64 to 128.

ATRC-4180 Add DHCP option 12 and 61 information in beacon


The beacon setting has been enhanced to add the ability the send DHCP option 12 and
option 61 in the beacon. The beacon information received for DHCP option 12 and option
61 are used to change the DHCP configuration in the receiving host.

ATRC-3380 SNMP add the ability to identify the incoming port for a
policy
Two new tables are added in ACD-POLICY-MIB, the first one is a table to associate the
table ID with the name and the number of policies:
AcdPolicyListEntry ::= SEQUENCE {
acdPolicyListEntryID Unsigned32,
acdPolicyListName DisplayString,
acdPolicyListNbrEntries Unsigned32
}

The second is the list of port with the ID of the list associated. For Management port or
monitor port the list id is set to 0, for traffic port the corresponding list ID is set.
AcdPolicyPortEntry ::= SEQUENCE {
acdPolicyPortEntryID Unsigned32,
acdPolicyPortListID Unsigned32
}

Addressed issues

ATRC-4177 SNMP get returns always 0 for accPaaResult MIB


The accPaaResults MIB values was returning the far-end measurements instead of the
near-end measurements for the following parameters:
1.3.6.1.4.1.22420.2.5.1.1.98 acdPaaResultPktLossCurrGaps
1.3.6.1.4.1.22420.2.5.1.1.99 acdPaaResultPktLossPrevGaps
1.3.6.1.4.1.22420.2.5.1.1.100 acdPaaResultPktLossCurrLargestGap
1.3.6.1.4.1.22420.2.5.1.1.101 acdPaaResultPktLossPrevLargestGap

ATRC-4075 CPU flooding protection not working properly when runt


frames are sent to CPU
The CPU flooding protection was not working properly when runt frames are sent to the
CPU. The runt frames get larger when frames are padded before being sent to the CPU.

ATRC-3964 Cannot enable beacon and advertisement with the web


when the interface is disabled
The web interface did not allow enabling the beacon or the advertisement on the
interface when the interface is disabled.

ATRC-4005 CLI display error on policy show statistics when configured


in ring mode
When the configured in ring mode, the CLI command policy sown statistics displays the
error “Error: Unknown policy list”.
ATRC-4014 CLI traffic show command does not display traffic-C
The CLI command traffic show now includes traffic-C.

ATRC-3834 Port statistics in receive for long frames are not properly
updated
For received frame longer than the configured MRU, the received long frames with good
CRC are counted in Long OK and Bytes total instead of Long OK, Bytes good and Bytes
total. The received long frames with bad CRC are counted in Long bad and Bytes total
instead of Bytes good and Bytes total.

ATRC-4060 Maximum MTU size


The maximum MTU size is limited to 10K 10240 bytes, before the UI erroneously
allowing up to 16K.

ATRC-4112 CLI rfc2544 testsuite add jumbo frame failed in 4x1 mode
In 4x1 aggregator mode, the CLI rfc2544 testsuite add command failed when specifying
the jumbo frame size. The error message was jumbo frame size too big even if the size
was valid.

ATRC-3632 Remove ip-multicast from CLI command rfc2544 monitor


edit packet-type
The CLI was wrongly allowing the ip-multicast in command rfc2544 monitor “monitor
name” packet packet-type.

ATRC-4227 NTP client lost server communication alarm is not raised


when NTP server communication is lost
The alarm NTP client lost server communication was not raised when the NTP server
communication is lost. The alarm was raised only when the server name was not
resolved at start up.

ATRC-3945 Create a Vision EMS adapter


Updated Vision EMS adapter to support release 5.2.

ATRC-3944 Inventory show old IP value when Auto interface is part of


bridge and unicast beacon IP DHCP is used
The web interface does not refresh the IP value when the Auto interface is part of a
bridge and unicast beacon IP DHCP is used.

MIB changes
---------------------------------------------------------------------------
-- The Policy lists table
This table contains all Policy list for this unit.
---------------------------------------------------------------------------
acdPolicyListTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcdPolicyListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of all Policy list contains in this unit."
::= { acdPolicyList 1 }

acdPolicyListEntry OBJECT-TYPE
SYNTAX AcdPolicyListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table describe a policy list contains in this unit."
INDEX { acdPolicyListEntryID }
::= { acdPolicyListTable 1 }

AcdPolicyListEntry ::= SEQUENCE {


acdPolicyListEntryID Unsigned32,
acdPolicyListName DisplayString,
acdPolicyListNbrEntries Unsigned32
}

acdPolicyListEntryID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Unique value for each list. This value is the same than acdPolicyListID
for each entry in acdPolicyTable."
::= { acdPolicyListEntry 1 }

acdPolicyListName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..31))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a string to identify the policy list."
::= { acdPolicyListEntry 2 }

acdPolicyListNbrEntries OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of entries currently in this list."
::= { acdPolicyListEntry 3 }

---------------------------------------------------------------------------
-- The Policy port table
-- This table contains the one to one relation between port and policy list.
---------------------------------------------------------------------------

acdPolicyPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcdPolicyPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of all Port and the correspondant policy list."
::= { acdPolicyPort 1 }

acdPolicyPortEntry OBJECT-TYPE
SYNTAX AcdPolicyPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A Policy port entry is the mapping between this port and a policy list."
INDEX { acdPolicyPortEntryID }
::= { acdPolicyPortTable 1 }

AcdPolicyPortEntry ::= SEQUENCE {


acdPolicyPortEntryID Unsigned32,
acdPolicyPortListID Unsigned32
}

acdPolicyPortEntryID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Unique value for each port. This value is the same than acdPortConfigIndex
used in ACD-PORT-MIB."
::= { acdPolicyPortEntry 1 }

acdPolicyPortListID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Numerical value coresponding to acdPolicyListEntryID."
::= { acdPolicyPortEntry 2 }
Release 5.1.2_18398 (2011/02/14)

New features and enhancements

ATRC-3947 MTU default value changed to 2000 bytes


The MTU default for all ports has been changed to 2000 bytes.

ATRC-3936 Display alarm SA/NSA in configuration page


Under the alarm configuration page, a column displaying the SA/NSA has been added.
The information was not available in the configuration page summary before.

ATRC-3938 Support DHCP option 12 (hostname) and option 61 (client


identifier)
The support for DHCP option 12 was added and user can specify his own string or use
the serial number. The option 61 is also added and user can use the MAC address or his
own identifier.

Addressed issues

ATRC-3881 Service Mapping maximum VID set validation for Network


port is invalid
The maximum number of VID set was not well validated in 3x1, 3x1 ring and 4x1
modes. The software now allows configuring 7 VID set instead of 15 for Network ports.

ATRC-3816 Wrong error message displayed in web UI when maximum


number of session is reached
When the maximum number of web sessions is reached, a user who tries to log in will
fail and got the following message displayed in the login page: ERROR: Session has
expired. Please login again. The error message is now ERROR: Maximum simultaneous
users has been reached.

ATRC-4054 Restart web UI does not work when certificates are used
The web UI does not restart when using the restart button in maintenance/certificates
page. The web is now restarted a few second after the restart button is used.

ATRC-3940 Disabling an interface in CLI disabled the discovery


When disabling an interface in CLI, the discovery mechanism is disabled. The discovery
mechanism should be disabled only when disabling the AUTO interface.

MIB changes
None
Release 5.1.1_18295 (2011/02/11)

New features and enhancements

ATRC-3986 Include EchoAgent 4.9.0


Added the new EchoAgent 4.9.0 supporting EchoVault release 4.9.0

Addressed issues

ATRC-3720 NID becomes very slow and eventually enters a reboots


loop after long communication loss with EchoVault server

The observed behaviour was that the NID became increasingly slow to respond to
management commands, then became completely unreachable and eventually entered a
reboot loop. This occurred only in situations in which the NID had the EchoAgent enabled
and configured to report statistics and in which the NID was unable to communicate with
the EchoVault server for an extended period of time (e.g. 30 days or more). The
problem was caused by the very large number of statistics files that were temporarily
saved into flash memory by the EchoAgent. For numbers of files above 20,000, the
entire CPU was used to process file system access and the NID rebooted due to a
watchdog reset.

The implemented fix consists in enforcing following limits on flash memory usage by the
EchoAgent:
 maximum number of files created = 5,000
 maximum flash space used = 5M
 minimum free space in flash at all times = 1M
The EchoAgent now checks current flash memory usage before attempting to write into
the flash. If one of the three limits described above is reached, the EchoAgent will stop
writing to the flash, until the communication with EchoVault is re-established and the
buffer space cleared.

ATRC-3953/4010 CFM process is always restarting


The CFM process is always restarting after the upgrade to 4.7.6.2.
The memory limit for CFM in previous version was not reinforced; a method to reinforce
memory usage was introduced but the CFM limit for maximum usage was not increased.
This limit has been increased to allow for all possible CFM configurations.

MIB changes
None
Release 5.1_17732 (2011/01/19)

IMPORTANT

 EtherNID GE and EtherNID EE are not supported in release 5.1

 When computing the local time, TAI offset is now added to the UTC time (factory
default value for TAI offset is +34). This requires additional validation of TAI offset
compatibility when new units that run 5.1 firmware are added to an existing network
(see ATRC-3749 for details)

New features and enhancements

ATRC-3332 Support for GPS timing source


 GPS enabled NID can act as NTP server
 Report loss of GPS fix
 GPS feature may be enabled/disabled (user configurable)
 Report number of satellites, SNR
 Reporting shall be done via:
o syslog
o alarms

Note: Refer to Application Note for more information

ATRC-3267 Support SyncE


 Must meet G-8261/8262 requirements Single TX clock for all physical ports -
Configurable
 Source of clock can be RX clock of any port
 Support for clock source redundancy - up to 2 sources
 Change of source RX clock must be hitless
 Indirect requirement on copper 1 Gbps ports (master/slave)
 Report synchronization status (LOS, LOC) via:
o Alarm
o Syslog

Note: Refer to Application Note for more information

ATRC-3044 Added Ability to Map any number of discrete VLAN IDs into
one policy
Service mapping-3 is a new feature intended to support a list of VLAN IDs (VID Set).
The VID Set can be used in the policies as a filter type. When the VID Sets are used as
filters outside of policies, the VID Sets can be configured for inner or outer traffic per
port. The inner/outer traffic configuration does not apply to policies.
NID Net Net Client Client Client Client Client Client Client Client
Model work work 1 1 2 2 3 3 4 4
and
Mode
Max Max Max Max Max Max Max Max Max Max
Pol. VID Pol. VID Pol. VID Pol. VID Pol. VID
sets sets sets sets sets
TE-1x1 16 15 16 15 N/A N/A N/A N/A N/A N/A
TE-2x1 20 20 16 15 16 15 N/A N/A N/A N/A
TE-3x1 20 7 16 3 16 3 16 3 N/A N/A
TE-3x1 20 7 Net- Net- 16 3 16 3 N/A N/A
Ring work2 work2
TE-4x1 40 7 16 3 16 3 16 3 16 3
TE-R 60 60 60 60 N/A N/A N/A N/A N/A N/A

ATRC-2565 Added support for environmental alarms


Added alarms for temperature sensor and power supply.
 8.0000.01 First overheat threshold
 8.0000.02 Second overheat threshold
 8.0000.03 No power supply +5V DC
 8.0000.04 No power supply on -48V feed A
 8.0000.05 No power supply on -48V feed B

ATRC-3330 Alternate HTTPS port


The unit uses IP port number 443 (HTTP) for connecting with the Management Web-
Interface. If your network blocks this port number, you can change it to another number
using the CLI interface.

Note: The CLI command is mode edit webs-port <port number>

ATRC-3247 Support RFC-2544 with a far end device supporting only


MAC swap loopback
Customers require being able to run RFC2544 test suites from a MetroNID when the
device at the remote site does not support Y.1731 loopbacks, only MAC swap.
To do this a new type of packet is send by the hardware generator. This packet is
composed of an Accedian Ethertype (0x88FC), an CFM packet with the opcode 11, and
the other fields normally include in a LBM CFM packet. To work a manual loopback is
configure at the remote NID and the inspector is program with the corresponding fields.

ATRC-2760 Deny local authentication if RADIUS denied access


Added a new authentication rule strict RADIUS-Local. When selected, the local
authentication is not used if the RADIUS authentication fails. The local authentication is
used only when the RADIUS authentication timeout.

ATRC-2915 Cannot delete Admin user or change the Admin privileges


The Admin user cannot be deleted and the Admin privileges cannot be changed.
ATRC-3210 Add alarms for GPS module
Add alarms for GPS module integration. The following alarms were added:
 8.0000.50 Communication lost with GPS module
 8.0000.51 Loss of fix for the GPS module

ATRC-2088 RFC-2544 test suite verifies port MTU at runtime


When starting a test suite the frame size selected must be smaller than MTU size. If the
MTU size is smaller, the test suite cannot be run.

ATRC-3059 Support alternate ethertype for traffic generator and RFC-


2544 test suite
The traffic generator and RFC-2544 test suite supports configuring the ethertype. The
possible are: layer-2, layer-2 Accedian, layer-2 generic, layer-3 and IP multicast. See
user manual for details.

ATRC-3117 Support dynamic trap handler


An auto trap handler was added on top of the existing 10 fixed trap handlers. Using the
auto trap receiver, the unit sends SNMP traps (v1 or v2c) to other compatible
notification receivers. With the auto trap receiver, the IP address of the compatible
notification receiver is automatically updated when the receiver connects to the unit and
sends the appropriate CLI commands.

Note: the CLI command is: snmp-trap edit auto host-name-refresh

ATRC-3143 Support media selection in 3X1 aggregation mode


In this operation mode the media-selection is used to select the connector to be used by
the Network port.
Media Selection Option SFP-A SFP-B Management RJ45-A RJ45-B
SFP-A Network Client-1 Management Client-2 Client-3
SFP-B Client-1 Network Management Client-2 Client-2
RJ45-A Client-2 Client-1 Management Network Client-3
RJ45-B Client-3 Client-1 Management Client-2 Network

ATRC-3248 Layer 3 Accedian advertisement


The advertisements function for the Plug & Go feature at layer 3 was added. The
advertisement can be done at layer 2 and/or layer 3. The destination IP address to be
used in layer 3 advertisement frames is configurable.

ATRC-2649 Create a Vision EMS adapter


Updated Vision EMS adapter to support release 5.1.

Addressed issues

ATRC-3395 RFC-2544 test suite back2back test results faulty


The test results for back2back test indicate only one frame received back2back. The
register first gap instead of following the next sequence register stays to zero and if in
the case of no gap it remains zero at the end of the test.

ATRC-2246 RFC-2544 test suite throughput not accurate when


changing port speed
The test suite throughput test is not accurate if the port speed change after the test
suite is created. The test suite now verifies the port speed before starting the test.

Note: If the port speed changes while the test suite is performed, the pot speed change
is not taken into account. The results won‟t be accurate.

ATRC-2449 Transparent Pause Frame not working


The transparent mode flow control for pause frame was not working properly. The pause
frame was dropped instead of being forwarded. The pause frames are now forwarded by
the CPU when the transparent mode is configured.

ATRC-3377 SNMP acdPolicyOutgoingPort is read-only


The acdPolicyOutgoingPort field was read only and the set functionality has been added.
Also the field was not returning the right value.

ATRC-3570 RFC-2544 test suite fails when configured using CLI


Configuring the RFC-2544 test suite with the CLI, the test suite always fails with the
error message “Fail to reach peer”. The same test suite configured with the web always
pass.

ATRC-3755 Cannot display more than one bandwidth regulator set in


the web page
When more than one bandwidth regulator set is configured, it was not possible them
display them in the web pages. The web server was entering in an infinite loop and
required a CPU reset to recover.

ATRC-2254 Edit filter changes not applied


When editing an IPv4 filter, a L2 filter, or VID set the changes are not applied to policies
or loopback. The filters were still using the old values even if the configuration reflects
the new values.

ATRC-2964 No error when deleting a L2PT that does not exist


When deleting a L2PT that does not exist with the CLI, no error was returned. The error
“Unknown instance” is added.

ATRC-3165 RFC-2544 test suite support in EchoVault


Added support of RFC-2544 test suite with EchoVault.
ATRC-3804 OAM loopback traffic counted in RFC-2544 statistics
The OAM loopback with an IPv4 filters gets counted in the RFC-2544.

ATRC-3749 TAI offset wrongly applied


In previous releases, the TAI offset was subtracted instead of being added to the UTC
time. As a result, there was an intrinsic difference of 2*TAI offset between Accedian
NIDs and other manufacturers‟ equipment when interworking for Y.1731 delay
measurements.

In order to ensure compatibility with previous releases, the Web GUI and CLI now allow
TAI negative values. When upgrading from a previous release, the TAI offset current
value is set to negative value.

Note: Factory default value for TAI offset will be +34 instead of -34. When installing a
new device into an existing deployment, it is necessary to verify the TAI offset
configuration on the existing system and align configuration of the new unit if required.

ATRC-3435 Layer 2 Filter matching both C-VLAN and S-VLAN for a


specific VLAN ID not working
A layer 2 filter configured to match both C-VLAN and S-VLAN for a specific VLAN ID was
not working. None of them was matching the filter.

ATRC-3171 Port statistics: no TX statistics for S-VLAN frames


When generating traffic using the generator, the S-VLAN traffic is not reported in the TX
port statistics.

ATRC-3212 Web link to other pages not working


The “Open Link in New Tab” or “Open Link in New window” does not work for links in
Traffic\Policies and Port\Statistics.

ATRC-3543 OAM instances and loopback are duplicated in the web


page.
The OAM instances and loopbacks are duplicated in the web page. The instance is
displays for a number of times equivalent to his index.

ATRC-3554 Rollback button enable event if session write lock is


disabled
The rollback button is enabled even if session write lock is disabled. Validation was
added to disabled the button when write lock is disabled.

ATRC-3715 SNMP acdRegulatorIsCouple value are inverted


A regulator with a coupling flag enabled (true) appears as disabled (false) in SNMP.
ATRC-3649 Sync-E secondary source status shows present when
secondary clock is set to none
Sync-E secondary source status shows present when the secondary clock is set to none.
The CLI now shows absent and the web shows “---“.

ATRC-2584 When an auto interface is part of a bridge, it sends


advertisement frames with IP 0.0.0.0
A bridge sub-interface configured with advertisement uses the sub-interface IP address
(0.0.0.0) instead of the bridge IP address.

ATRC-3316 Bridge interface receiving a beacon will reconfigured itself


The bridge interface configured with auto interface updates only his network mask and
gateway address with the beacon information instead of IP address, network mask and
gateway address.

ATRC-2911 Bandwidth regulator optimization when changing


configuration
The bandwidth regulator configuration for CBS and EBS are independent. Changing the
EBS configuration will not impact the CBS traffic.

MIB changes
None

Documentation
Administrator's Guide Release 4.7 and Application Notes