Activar Web Allied

AlliedWare Plus Software Maintenance Release Note: 5.4.6-2.
4 1
Software Maintenance Release Note
AlliedWare Plus™ Software Version 5.4.6-2.4

For SwitchBlade x8100, SwitchBlade x908, DC2552XS/L3, x930, x610, x510,
IE200, IE300, IE500 Series Switches, IX5, x310, x230, x210, FS980M, GS900,
and XS900 Series Switches, AR2010V, AR2050V VPN Firewalls, AR3050S
and AR4050S NGFWs, and VAA.
Introduction
This document lists the issues addressed in AlliedWare Plus™ software
maintenance version 5.4.6-2.4.
Read this maintenance release note in conjunction with the:

 New and Enhanced Features in AlliedWare Plus 5.4.6 Major and Minor Versions,
which describes new and enhanced features in AlliedWare Plus software
version 5.4.6-0.x.
 For more information, see the Command Reference for your switch or
AR-Series firewall.
Contents
Introduction .................................................................................................................. 1
Installing the GUI to your Switch using an SD Card or USB Device .......................... 5
Installing the GUI to your Switch via TFTP Server ..................................................... 7
Installing and Enabling this Version ............................................................................. 9
Important Information about Compatibility with Earlier Software Versions ............. 12
ISSU (In-Service Software Upgrade) on SBx8100 with CFC960 ............................ 15
Enhancements in 5.4.6-2.3 ......................................................................................... 16
Enhancements in 5.4.6-1.5 ......................................................................................... 17
Enhancements in 5.4.6-1.2 ......................................................................................... 17
Enhancements in 5.4.6-0.3 ......................................................................................... 18
Issues Resolved in 5.4.6-2.4 ....................................................................................... 20
C613-10524-00-REV L
AlliedWare Plus Software Maintenance Release Note: 5.4.6-2.4 2
Supported Models and Software File Names

Table 1: Supported switch models and software file names
Models Series Release File Date GUI file
FS980M/9 FS980M FS980-5.4.6-2.4 rel January/2017 FS980-gui_546_20.jar

FS980M/9PS
FS980M/18
FS980M/18PS
FS980M/28
FS980M/28PS
FS980M/52
FS980M/52PS
AT-GS924MX GS900 GS900-5.4.6-2.4.rel January/2017 GS900-gui_546_04.jar

AT-GS924MPX
AT-GS948MX
AT-GS948MPX
AT-XS916MXT XS900 XS900-5.4.6-2.4.rel January/2017 XS900-gui_546_11.jar

AT-XS916MXS
AT-x210-9GT x210 x210-5.4.6-2.4.rel January/2017 x210-gui_546_11.jar

AT-x210-16GT
AT-x210-24GT
AT-x230-10GP x230 x230-5.4.6-2.4.rel January/2017 x230-gui_546_20.jar

AT-x230-18GP
AT-x230-18GT
AT-x230-28GP
AT-x230-28GT
AT-x310-26FT x310 x310-5.4.6-2.4.rel January/2017 x310-gui_546_11.jar

AT-x310-50FT
AT-x310-26FP
AT-x310-50FP
AT-IE200-6FT IE200 IE200-5.4.6-2.4.rel January/2017 ie200-gui_546_11.jar

AT-IE200-6FP
AT-IE200-6GT
AT-IE200-6GP
AT-IE300-12GT IE300 IE300-5.4.6-2.4.rel January/2017 n/a
AT-IE300-12GP
AT-IE510-28GSX-80 IE510 IE510-5.4.6-1.4.rel January/2017 ie510-gui_546_04.jar
AT-IX5-28GPX IX5-5.4.6-2.4.rel January/2017 IX5-gui_546_11.jar
C613-10524-00-REV L
Table 1: Supported switch models and software file names
Models Series Release File Date GUI file
AT-x510-28GTX x510 x510-5.4.6-2.4.rel January/2017 x510-gui_546_11.jar

AT-x510-52GTX
AT-x510-28GPX
AT-x510-52GPX
AT-x510-28GSX
AT-x510-28GSX-80
AT-x510DP-28GTX
AT-x510DP-52GTX
AT-x510L-28GT
AT-x510L-28GP
AT-x510L-52GT
AT-x510L-52GP
IE510-28GSX-80 IE500 IE510-5.4.6-2.4.rel January/2017 IE510-gui_546_04.jar
AT-x610-24Ts x610 x610-5.4.6-2.4.rel January/2017 x610-gui_546_11.jar

AT-x610-24Ts-PoE+
AT-x610-24Ts/X
AT-x610-24Ts/X-PoE+
AT-x610-24SPs/X
AT-x610-48Ts
AT-x610-48Ts-PoE+
AT-x610-48Ts/X
AT-x610-48Ts/X-PoE+
SwitchBlade x908* SBx908 SBx908-5.4.6-2.4.rel January/2017 SBx908-gui_546_11.jar
AT-x930-28GTX x930 x930-5.4.6-2.4.rel January/2017 x930-gui_546_11.jar

AT-x930-28GPX
AT-x930-52GTX
AT-x930-52GPX
AT-x930-28GSTX
AT-DC2552XS/L3 dc2500-5.4.6-2.4.rel January/2017 dc2500-gui_546_11.jar
AT-SBx81CFC400 SBx8100 SBx81CFC400-5.4.6- January/2017 SBx81CFC400_gui_546_20.jar

AT-SBx81CFC960 2.4.rel SBx81CFC960_gui_546_20.jar
SBx81CFC960-5.4.6-
2.4.rel
AT-AR2010V VPN AR2010V-5.4.6-2.4.rel January/2017 n/a

AT-AR2050V Firewalls AR2050V-5.4.6-2.4.rel
AT-AR3050S NGFW AR3050S-5.4.6-2.4.rel January/2017 n/a

AT-AR4050S AR4050S-5.4.6-2.4.rel
AMF Cloud vaa-5.4.6-2.4.iso January/2017 n/a
*Under version 5.4.6, not all models of XEM are supported in the SwitchBlade
x908. The following table lists which XEMs are and are not supported under
version 5.4.6.
C613-10524-00-REV L
Table 2: Support of XEM modules for the SwitchBlade x908 in version 5.4.6-x.x
Product Supported in
version 5.4.6-x.x
XEM-1XP No
XEM-2XP Yes
XEM-2XS Yes
XEM-2XT Yes
XEM-12S No
XEM-12T No
XEM-12Sv2 Yes
XEM-12Tv2 Yes
XEM-24T Yes
Caution: 
Using a software version file for the wrong switch model may cause
unpredictable results, including disruption to the network. Information in this
release note is subject to change without notice and does not represent a
commitment on the part of Allied Telesis, Inc. While every effort has been made
to ensure that the information contained within this document and the features
and changes described are accurate, Allied Telesis, Inc. can not accept any type
of liability for errors in, or omissions arising from, the use of this information.
C613-10524-00-REV L
Installing the GUI to your Switch using an SD Card or

USB Device
1. Download a GUI Java applet.
The GUI Java applet file is available in a compressed (zip) file with the
AlliedWare Plus Operating System software from the Software Download
area of the Allied Telesis Website: http://www.alliedtelesis.com/support/
software/restricted. Log in using your assigned Email Address and
Password. Download the Java applet file. This file will have a .zip file
name extension. You need to extract the Java .jar file from the compressed
.zip file. The version number of the software applet file (.jar) gives the
earliest version of the software file (.rel) that the GUI can operate with.
2. Copy the GUI Java applet .jar file to an SD card or USB storage device.
Insert the SD card in the SD slot on the front of your switch or the USB
device into the USB port on the switch. Connect to the management port,
then login to the switch.
Copy the GUI Java applet to your switch, using the below commands:
awplus# copy card:/<filename.jar> flash:/
or
awplus# copy usb:/<filename.jar> flash:/
Where <filename.jar> is the GUI Java applet file you downloaded in
Step 1.
Note: Where the GUI file is not in the root directory of the USB flash drive, you must
enter the full path to the GUI file. For example, where the GUI file resided in the folder
gui_files, you would enter the command: copy usb:/gui_files/filename.jar flash:/
3. Assign IP addresses.
Use the following commands to assign the IP addresses for connecting to
the Java applet.
awplus# configure terminal
awplus(config)# interface vlan1
awplus(config-if)# ip address <address>/<prefix-length>
Where <address> is the IP address that you will subsequently browse to
when you connect to the GUI Java applet. For example, to give the switch
an IP address of 192.168.2.6, with a subnet mask of 255.255.255.0,
use the following command: awplus(config-if)# ip address 192.168.2.6/24
4. Configure the gateway.

Configure your switch with a default gateway, if necessary, using these
commands:
awplus(config-if)# exit
awplus(config)# ip route 0.0.0.0/0 <gateway-address>
Where <gateway-address> is the IP address for your gateway device.
Note that you do not need to define a default gateway if you browse to the
switch from within its own subnet.
C613-10524-00-REV L
5. Create a user account.

In order to log into the GUI, you must first create a user account. Use these
commands to setup a user account:
awplus(config)# username <username> privilege 15 password
<password>
awplus(config)# exit
Note that you can create multiple users to log into the GUI. See the
AlliedWare Plus Software Reference for information about the username
command.
6. Ensure HTTP service is enabled.

The HTTP service needs to be enabled on the switch before it accepts
connections from a web browser. The HTTP service is enabled by default.
However, if the HTTP service has been disabled, you must enable the HTTP
service again. If the HTTP service is disabled, use the following command
to enable it:
awplus(config)# service http
See the AlliedWare Plus Software Reference for information about the service
http command.
7. Log into the GUI.

Start a browser and enter the IP address you configured in Step 3 as the
URL. You will be presented with a login screen after the GUI Java applet has
started. Log in with the username and password that you defined in the
earlier step, named Create a user account.
Note: Any configuration changes should be saved to ensure the device settings are
retained.
C613-10524-00-REV L
Installing the GUI to your Switch via TFTP Server

1. Download a GUI Java applet file from the support site.
The GUI Java applet file is available in a compressed (.zip) file with the
AlliedWare Plus Operating System software. You can download the applet
from the Allied Telesis Download Center by logging into your account.
You need to extract the Java .jar file from the compressed .zip file. The
version number of the software applet file (.jar) gives the earliest version of
the software file (.rel) that the GUI can operate with.
2. Copy the GUI applet.

Copy the GUI applet .jar file onto a TFTP server. Ensure this TFTP server is
enabled and ready for the switch. Connect to the management port of the
switch, then login to the switch. Do not connect to the management port of
the TFTP server
3. Assign the IP addresses.

Use the following commands to configure your switch with an appropriate
IP address:
awplus(config)# interface vlan1
awplus(config-if)# ip address 192.168.2.6/24
Where <address> is the IP address that you will subsequently browse to
when you connect to the GUI Java applet. For example, to give the switch
an IP address of 192.168.2.6, and a subnet mask of 255.255.255.0,
use the following command:
awplus(config-if)# ip address 192.168.2.6/24
Use the following commands to configure your switch with a default
gateway:
awplus(config)# ip route 0.0.0.0/0 <gateway-address>
4. Configure the default gateway.

In necessary, use the following commands to configure the default gateway.
awplus(config)# ip route 0.0.0.0/0 <gateway address>
Where <gateway-address> is the IP address for your gateway device.
Note that you do not need to define a default gateway if you browse to the
switch from within its own subnet.
5. Copy the GUI Java applet to your switch.

Use the following commands to copy the GUI Java applet to your switch:
awplus# copy tftp://<server-address>/<filename.jar>
flash:/
Where <server-address> is the IP address for the TFTP server, and
where <filename.jar> is the GUI Java applet file you downloaded in
Step 1.
C613-10524-00-REV L
6. Create a user account.

In order to log into the GUI, you must first create a user account. Use the
following commands to setup a user account.
awplus(config)# username <username> privilege 15 password
<password>
awplus(config)# exit
Note that you can create multiple users to log into the GUI. See the
AlliedWare Plus Software Reference for information about the username
command.
7. Start the Java Control Panel, to enable Java within a browser .

On your PC, start the Java Control Panel by opening the Windows Control
Panel from the Windows Start menu. Then enter Java Control Panel in the
search field to display and open the Java Control Panel.
Next, click on the ‘Security’ tab. Ensure the ‘Enable Java content in the
browser’ checkbox is selected on this tab.
8. Enter the URL in the Java Control Panel Exception Site List.
Click on the ‘Edit Site List’ button in the Java Control Panel dialog Security
tab to enter a URL in the Exception Site List dialog. In the ‘Exception Site
List’ dialog, enter the IP address you configured in Step 4, with a http://
prefix.
After entering the URL click the Add button then click OK.
9. Log into the GUI.

Start a browser then enter the IP address you configured in Step 3 as the
URL. You will then be presented with a login screen after the GUI Java
applet has started. You can then Log in with the username and password
that you defined previously in Step 6.
Note: Any configuration changes should be saved to ensure the device settings are
retained.
For more information please refer to the 5.4.6 Command Reference for your
product available from the Support area of the Allied Telesis Website.
C613-10524-00-REV L
Installing and Enabling this Version

To use this version, your switch must already be running AlliedWare Plus.
Contact your distributor or reseller for more information.
To install this version:

1. Put the version file onto your TFTP server.
2. If necessary, delete or move files to create space in the switch’s Flash
memory for the new file.
Note that you cannot delete the current boot file.
To list files, use the command:
awplus# dir
To see the memory usage, use the command:
awplus# show file systems
To delete files, use the command:
awplus#del <filename>
3. Copy the new release from your TFTP server onto the switch.
To do this, enter Privileged Exec mode and use the command:
awplus#copy tftp flash
Follow the onscreen prompts to specify the server and file.
4. Set the switch to boot from the new release.
Enter Global Configuration mode.
On the x210 Series switches, use the command:
awplus(config)#boot system x210-5.4.6-2.4.rel
On the IX5-28GPX switch, use the command:
awplus(config)#boot system ix5-5.4.6-2.4.rel
On the SwitchBlade x908, use the command:
awplus(config)#boot system SBx908-5.4.6-2.4.rel
On the DC2552XS/L3 switch, use the command:
awplus(config)#boot system dc2500-5.4.6-2.4.rel
C613-10524-00-REV L
On the SwitchBlade x8100 Series switches with a SBxCFC400 controller card

installed, use the command:
awplus(config)#boot system SBx81CFC400-5.4.6-2.4.rel
On the SwitchBlade x8100 Series switches with a SBxCFC960 controller card
installed, use the command:
awplus(config)#boot system SBx81CFC960-5.4.6-2.4.rel
On the ARxx series (NGFW) security appliances, use the commands for
each product as follows:
awplus(config)#boot system AR2010v-5.4.6-2.4.rel
awplus(config)#boot system AR2050v-5.4.6-2.4.rel
awplus(config)#boot system AR3050S-5.4.6-2.4.rel
awplus(config)#boot system AR4050S-5.4.6-2.4.rel
If desired, check the boot settings by entering Privileged Exec mode and
using the following command:
awplus#show boot
On the GS900MX/MPX Series switches, use the command:
awplus(config)#boot system GS900-5.4.6-2.4.rel
On the XS900MX Series switches, use the command:
awplus(config)#boot system XS900-5.4.6-2.4.rel
On the IE200 Series switches, use the command:
awplus(config)#boot system IE200-5.4.6-2.4.rel
5. Reboot.
To do this, enter Privileged Exec mode and use the command:
awplus#reload
C613-10524-00-REV L
Upgrading the Software of a VAA

VAA does not need to be the same release as the products it is managing,
however, as VAA is intended to be used as an AMF Master or Controller, it is
recommended it be on the latest release. Before you begin, you will first need to
upload a VAA ISO image to a data store on your ESXi server. For the complete
set of instructions on uploading a VAA ISO image, please refer to the VMware
vSphere 6.0 Documentation Centre. To upgrade or downgrade the current
installed image, you will need to change the current.iso software image in the
virtual-machine configuration, then reboot the virtual-machine.
To change the current .iso software image:

 Power off the virtual-machine you wish to upgrade/downgrade.
 Edit the settings of the virtual-machine.
 Select CD/DVD Drive 1 item
 Ensure that Connect at power on check-box is ticked.
 Select the Datastore ISO File radio button.
 Browse for the desired VAA iso image.
Start the virtual machine, during boot you will see a menu that looks like this:
Alliedware+
Boot from CD
 Select the Boot from CD option.
You will only have 5 seconds to select "Boot from CD" before the boot continues with
the previously installed release.
This will boot using the new .iso software image, and next time you login using
the console you will be presented with the “Install this release to disk? (y/n)”
option.
Upgrading a VAA running under Amazon Web Services (AWS)

To update an existing VAA running under AWS, follow these steps:
1. Download the file, for example: vaa-5.4.6-2.4.iso, and copy it onto the VAA.
2. Run the command software-upgrade vaa-5.4.6-2.4.iso
C613-10524-00-REV L
Important Information about Compatibility with Earlier

Software Versions
Loss of auto-synchronization compatibility on VCS

and on dual-CFC SBx8100 chassis
Auto-synchronization compatibility has not been maintained for VCStack or
dual-CFC SBx8100 chassis between AlliedWare Plus version 5.4.6-1.2 and any
previous software version (including v5.4.6-1.1).
This affects VCStack, standalone dual-CFC SBx8100 switches, and VCStack

Plus.
Consequences for VCStacks

On VCStacks, the loss of auto-synchronization means:
1. If you want to upgrade an existing VCStack to 5.4.6-1.2, this should not
cause any problems. The boot system command will automatically copy the
new software release to all stack members. Do not reboot any individual
stack members after installing the new release - instead reboot the stack as
a whole.
If you encounter any errors from the boot system command, then check that
the release file was copied to all stack members before rebooting. If it was
not, then address any problems reported, such as freeing up space in Flash
for the new release file, and then repeat the boot system command again.
2. If a stack is running v5.4.6-1.2, and you connect a switch running an older
release to the stack, then the v5.4.6-1.2 software will not be automatically
copied over to the newly-added stack member, even if stack software-auto-
synchronize has been enabled on the stack. Instead, upgrade the switch that
is to be added to the stack to v5.4.6-1.2 before you add it to the stack.
3. If a stack is running an older release, and you connect a switch running
v5.4.6-1.2 to the stack, then the older software cannot be automatically
copied over to the newly-added stack member, even if stack software-auto-
synchronize has been enabled on the stack. Instead, downgrade the switch
that is to be added to the stack to the older release before you add it to the
stack.
4. If you do boot up a stack with a switch running an incompatible version, the
incompatible switch will boot up as a standalone unit. To recover, simply
leave the incompatible switch cabled into the stack, log into it, upgrade or
downgrade it to the desired release, and reboot the switch.
Consequences for a single SBx8100

If you want to insert a new CFC into a chassis, the loss of auto-synchronization
means:
1. If you want to upgrade an existing SBx8100 that has two CFCs installed to
5.4.6-1.2, this should not cause any problems. The boot system command
will automatically copy the new software release to both CFCs. Do not
C613-10524-00-REV L
reboot any individual CFCs after installing the new release - instead reboot
the chassis as a whole.
the release file was copied to both CFCs. If it was not, then address any
problems reported, such as freeing up space in Flash for the new release file,
and then repeat the boot system command again.
2. If a standalone SBx8100 has a CFC installed that is running an older release,
and you add a CFC running v5.4.6-1.2 to the chassis, then the older software
cannot be automatically copied over to the newly-added CFC.
3. If a standalone SBx8100 has a CFC installed that is running v5.4.6-1.2, and
you add a CFC running an older release to the chassis, then the v5.4.6-1.2
software cannot be automatically copied over to the newly-added CFC.
4. If you connect a CFC running an incompatible release to an SBx8100 chassis,
you will be unable to log into the added CFC. For example, if the Active
CFC is running 5.4.6-1.2 and another CFC joins with 5.4.6-0.x, the error you
get is:
======
cfc960 login: manager
Password:
Last login: Thu Aug 18 02:15:21 UTC 2016 on ttyS0
All 1 lines for VR:PVR are busy. Try again later
======
To recover from this situation, see “Upgrading/downgrading a CFC” on

page 14.
To determine what release a CFC is running without logging in, look for the
“Current release filename” console output when the CFC first boots up, e.g.
______________ ____
/\ \ / /______\
/ \ \_ __/ /| ______ |
/ \ | | / | ______ |
/ \ \ / / \ ____ /
/______/\____\ \/ /____________/
Allied Telesis Inc.

AlliedWare Plus (TM) v5.4.6
Current release filename: SBx81CFC400-5.4.6-1.2.rel
Consequences for a VCStack Plus Pair of SBx8100 chassis

If you are dealing with VCStack Plus, the effect of the loss of auto-
synchronization depends on whether you are installing a new CFC or a whole
new chassis:
1. If you want to upgrade an existing SBx8100 VCStack Plus system to 5.4.6-
1.2, this should not cause any problems. The boot system command will
automatically copy the new software release to all stack members. Do not
reboot any individual CFCs or stack members after installing the new
release - instead reboot the stack as a whole.
the release file was copied to all CFCs. If it was not, then address any
problems reported, such as freeing up space in Flash for the new release file,
and then repeat the boot system command again.
C613-10524-00-REV L
2. If you want to insert a new dual CFC into a chassis that is part of an existing
VCStack Plus system, refer to “Consequences for a single SBx8100” on
page 12.
3. If you want to insert a new SBx8100 chassis into a VCStack Plus system,
refer to “Consequences for VCStacks” on page 12.
Upgrading/downgrading a CFC
Because auto-synchronization does not work, you have to manually upgrade
or downgrade the CFC to match your existing SBx8100. This section describes
two different ways to do this:
1. Insert the new CFC into the chassis. Load the desired software version onto
a USB stick and insert the USB stick into the chassis. Via the bootloader
menu (CTRL+B), perform a one-off boot (option 1), select USB, then select
the desired software version. Both CFCs should detect each other. Log in
and enter boot system to ensure the desired software version is set on the
new CFC.
2. Remove the new CFC if you had already inserted it. Upgrade or downgrade
the existing SBx8100 so that it is running the same software version as the
new CFC. Reinsert the new CFC. Both CFCs should then detect each other
successfully. You can then log in and set the desired software version on
both CFCs.
C613-10524-00-REV L
ISSU (In-Service Software Upgrade) on SBx8100 with

CFC960
ISSU is available on standalone SBx8100 Series switches with dual CFC960
control cards, and on switches using VCStack Plus™ to create a single virtual
unit out of two chassis (where each chassis has a pair of CFC960 control cards).
ISSU allows you to upgrade the software release running on the CFCs with no
disruption to network traffic passing through the chassis.
For each issue resolved on these platforms, the resolution will take effect as
indicated when:
 CFCs upgraded: The issue will be resolved once all CFCs have rebooted
and are running the same SW version.
 ISSU Complete: The issue will be resolved once all cards in the system are
running the same SW version. This maintenance release cannot be
upgraded from any previous release using ISSU.
Please refer to the ISSU compatibility matrix below to determine ISSU release
compatibility. C= Compatible, I = Incompatible.
TO
RELEASE 5.4.6-2.1 5.4.6-2.2 5.4.6-2.3 5.4.6-2.4
5.4.6-2.1 C I I
5.4.6-2.2 C I
FROM
5.4.6-2.3 C
Additional information
For more information about ISSU, see the ISSU Commands chapter in the SwitchBlade
x8100 Series Command Reference for AlliedWare Plus.
ISSU is not supported on other platforms.
You may also find the following How To Note useful:

 How to Use the In-Service Software Upgrade (ISSU) Feature
C613-10524-00-REV L
Enhancements in 5.4.6-2.3
CR Module Description
ER-1146 PKI With this software update, the certificate-using processes like HTTPS connections to Webauth, HTTPS browsing to the switch, RestFUL
API calls, etc., can now be pointed at a configured trustpoint, in the same way that SYLog-over-TLS and RADIUS-over-TLS can.
The commands auth-web-server trustpoint NAME and http trustpoint NAME are added to link a certificate created in the
specified trustpoint.
The commands no auth-web-server trustpoint NAME and no http trustpoint NAME are added to remove the association with
the trustpoint.
ER-147 EPSR LACP links can now be configured as part of an EPSR ring.
Please note that this enhancement applies ONLY to the following devices: SBx908, SBx81CFC400, SBx81CFC960, FS980M Series.
EPSR is supported unchanged over LACP on all other devices.
C613-10524-00-REV L
ER-783 Pluggable transceivers Previously there were some differences between switch devices with regard to which pluggable modules and cables could be used
for stacking.
With this software update, there is now no differing requirements between switches with regard to which pluggable modules and
cables could be used for stacking.There is now a single definition for all switches that use stacking ports of the type that accept
insertion of pluggable modules.
ER-1089 SNMP IE200, IE300, IE510, x210, x230, x310, x510, x610, x930, IX5, DC2552XS/L3, x900, SBx908, SBx8100 CFC400, SBx8100
CFC960, AR2050, AR3050, AR4050, VAA
With this software update, it is now possible to generate an SNMP trap when the syslog-ng process fails.
C613-10524-00-REV L
ER-809 VLAN Classifier IE200, IE300, IE510, x210, x230, x310, x510, x610, x930, IX5, DC2552XS/L3, x900, SBx908, SBx8100 CFC400, SBx8100
CFC960, AR2050, AR3050, AR4050, VAA
With this software update, it is now possible to configure VLAN classifiers directly on an aggregator interface (not on their member
ports) using the command vlan classifier activate.
Use this command in Interface Configuration mode to associate a VLAN classifier group with the switch port.
Use the no variant of this command to remove the VLAN classifier group from the switch port.
Syntax:
vlan classifier activate <vlan-class-group-id>
no vlan classifier activate <vlan-class-group-id>
You cannot enter this command on a link aggregator. Enter it on the aggregator's switch ports instead.
Example:
To associate VLAN classifier group 3 with switch port1.0.3, enter the following commands:
awplus(config)# interface port1.0.3
awplus(config-if)# vlan classifier activate 3
To remove VLAN classifier group 3 from switch port1.0.3, enter the following commands:
awplus(config)# interface port1.0.3
awplus(config-if)# no vlan classifier activate 3
ER-891 Healthcheck Previously, on a stack of x310, IX5, x510, x610, x903 or DC2552 switches, under an extremely rare condition, a resiliency-link
healthcheck packet would be corrupted during transmission and this corrupted packet would loop continuously around the
resiliency-link VLAN, causing higher CPU utilisation than normal. With this software update, extra diagnostic logging has been
added to detect a corrupted healthcheck packet. Also, additional internal software checks have been put in place to prevent a
corrupted packet loop occurring.
C613-10524-00-REV L
ER-958 VRRP x210, x230, x310, IX5, x510, x610, SBx908, x930, DC2552, SBx81CFC400, SBx81CFC960, AR3050S, AR4050S, AR2050V,
IE200, IE300, IE510
Previously, only one circuit-failover interface would be allowed per VRRP instance, so configuring a new circuit-failover interface
would replace the existing one. With this software update, up to 32 circuit-failover interfaces can be configured and monitored per
VRRP instance. The VRRP priority is cumulatively decremented/incremented when a circuit-failover interface goes down and up.
This command adds a new circuit failover interface instead of overwriting existing one.
circuit-failover <interface> <1-253>
This command removes the circuit failover interface with the specified interface name.
no circuit-failover [<interface> <1-253>]
This command removes all circuit failover interfaces on a VRRP instance.
no circuit-failover
Example
To configure circuit failover on an IPv4 VRRP instance, so that if interface VLAN3 goes down, then the priority of VRRP instance
1 is reduced by 30, use the commands:
awplus(config)# router vrrp 1 vlan2
awplus(config-router)# circuit-failover vlan3 30
C613-10524-00-REV L
Issues Resolved in 5.4.6-2.4

This AlliedWare Plus maintenance version includes the resolved issues in the following table, ordered by feature.
CR number format: A new issue tracking system is being introduced. The CRs in the new system use a new format (CR-5xxxx). The
previous system used the format: CR000xxxx.
For the next while, both systems will be used and both formats may appear in these tables. When referring to CRs, use the full CR format,
e.g. CR-5xxxx.
AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
GS900MX
XS900MX
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x550
x610
x930
x950
IX5
CR-56148 NTP Previously, NTP would fail to synchronize the time. Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y –
CR-56219 IDS/IPS Previously, the Suricata process would look like it was – – – – – – – – – – – – – – – – – – – – – Y –
IP Reputation using 100% of the CPU even when there was no load.
Malware This issue has been resolved.
Protection
URL Filtering
CR-56272 Firewall Previously, when using the WebAPI to configure a – – – – – – – – – – – – – – – – – – – – – Y –
NAT Firewall NAT rule, it was possible to create a portfwd
rule in the running config that was invalid.
This issue has been resolved.
C613-10524-00-REV L

AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
GS900MX
XS900MX
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x550
x610
x930
x950
IX5
CR-56049 ACL Previously, the DHCP Snooping database would not be – – – – – – Y Y – – – – – – – – – – – – – – –

DHCP correctly written to non volatile memory on x210 and
Snooping x230 variant switches.
CR-56053 AMF Previously, a software initialization issue would Y – – – – – – – – Y Y – Y Y – Y – Y Y – – Y Y
incorrectly set the internal AMF backup state and
prevented the backups from being triggered.
ISSU: Effective when CFCs upgraded.
CR-56054 Antivirus Previously, if two AlliedWare Plus routers had the proxy- – – – – – – – – – – – – – – – – – – – – – Y –
Webcontrol based features Web-control or Antivirus enabled, the
second device could falsely detect a forwarding loop and
block the HTTP traffic.
CR-56062 ARP Previously, IPv4 ARP and IPV6 ND entries that used port- Y Y – – – Y – – Y Y Y – Y Y – Y Y Y Y – – – –
Neighbor groups or flood to a VLAN would not be correctly
Discovery synchronized across stack members during a stack
failover.
C613-10524-00-REV L
AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
GS900MX
XS900MX
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x550
x610
x930
x950
IX5
CR-56168 BGP Previously, when BGP password authentication was – – – – – – – – – – – – – – – – – – – Y Y Y –

configured on an AR-Series Firewall, the BGP session
with its peer would not be successfully established.
CR-55910 CLI Previously, entering the command: Y – Y Y Y Y Y Y Y Y Y – Y Y – – Y Y Y Y Y Y –
copy <file> startup-config could cause a system
reboot if the operation was invalid.
CR-56131 DPI Previously, if two feature resource updates occurred at a – – – – – – – – – – – – – – – – – – – – – Y –
Malware similar time, it was possible for the stream engine to be
Protection restarted. As a result, a leak of queued hardware buffers
URL Filtering could occur. In the worst case, it could reduced the
hardware buffer pool to a level where no packets could
then be transmitted or received.
CR-55406 Firewall Previously, changing the configuration of an entity used in – – – – – – – – – – – – – – – – – – – – – Y –
a firewall rule would not trigger an update of the rule.
CR-56147 Firewall Previously, if a zone was used in a Firewall rule, a traffic- – – – – – – – – – – – – – – – – – – – – – Y –
shaping rule, or NAT rule and that zone had two
networks with the same IP subnet range, then an error
would be produced and the rule would never become
active.
C613-10524-00-REV L
AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
GS900MX
XS900MX
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x550
x610
x930
x950
IX5
CR--56008 Firewall Previously, a host attached to a VLAN on an AR-series – – – – – – – – – – – – – – – – – – – – – Y –

VRF-lite firewall could not ping an interface in a VRF instance when
the firewall module was enabled.
CR-55249 IPv4 Previously, the dot1q ETH sub-interfaces could – – – – – – – – – – – – – – – – – – – Y Y Y –
occasionally fail to forward traffic.
CR-55901 IPv4 Previously, when a VLAN was configured to be Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y – – – –
'shutdown' and after the first port in that VLAN was
linked up, the switch would incorrectly add an interface
route to the hardware table, resulting in high CPU load.
CR-56037 IPv6 Previously, if a prefix was explicitly specified to be – – – – – – – – Y Y Y Y Y Y – – Y Y Y – – Y –
advertised in an IPv6 router advertisement, the prefix
would be advertised twice in the same RA packet with
conflicting life times.
This resulted in confusion in hosts processing the router
advertisement.
CR-56098 NTP This software update addresses multiple NTP denial of Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y Y Y Y Y Y –
service vulnerabilities that is stated under "Vulnerability
Note VU#633847".
CR-56140 NTP Previously, the hardware clock would not be – – – – – – Y – Y – Y – – – – – – – – Y Y Y –
synchronised correctly with NTP time.
C613-10524-00-REV L
AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
GS900MX
XS900MX
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x550
x610
x930
x950
IX5
CR-56112 RMON Previously, the AlarmValue and AlarmThreshold were Y – Y – – – – Y – – – – – – – – – – – – – – –

incorrectly displayed as "0" in the SNMP trap.
CR-55913 Stacking Previously, if a member of an x930 stack was restarted – – – – – – – – – – – – – Y – – – – – – – – –
from the CLI, there was a chance that one of the stack
ports would fail to re-join the stack.
CR-51836 Stacking Previously, rebooting a LIF card or a stack member on a – – – – – – – – – – – – – – – – – – Y – – – –
SBx8100 with CFC960 could result in a memory leak.
ISSU: Effective when ISSU complete.
CR-55821 System Previously, an uncorrected "L3 Parity Error" would result – – – – – – – – – – Y – – – – – – – – – – – –
in the "parity log" error to be displayed continuously,
unnecessarily filling up the log table. This type of parity
error can be automatically corrected and the issue has
been resolved without flooding the log table.
C613-10524-00-REV L

AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
AR2010V
AR2050V
FS980M
SBx908
IE200
IE300
IE510
x210
x230
x310
x350
x610
x930
IX5
Previously, entering the command: copy <file> startup-config Y Y Y Y Y Y Y – Y Y Y Y – Y Y Y Y Y Y –
CR-55910 CLI could cause a system reboot if the operation was invalid.
Previously, if a member of an x930 stack was restarted from the – – – – – – – – – – – Y – – – – – – – –
CLI, there was a chance that one of the stack ports would fail
CR-55913 Stacking to re-join the stack.
CR-56037 IPv6 Previously, if a prefix was explicitly specified to be advertised in – – – – – – Y – Y Y Y Y – Y Y Y Y Y Y –
an IPv6 router advertisement, the prefix would be advertised
twice in the same RA packet with conflicting life times.
This resulted in confusion in hosts processing the router
advertisement.
CR-56054 Antivirus Previously, if two devices had the proxy-based features Web- – – – – – – – – – – – – – – – – – – Y –
Webcontrol control or Antivirus enabled, the second device could falsely
detect a forwarding loop and block the HTTP traffic.
CR-56055 Antivirus Previously, Antivirus on the device would not handle HTTP – – – – – – – – – – – – – – – – – – Y –
responses, for example, the "302 redirect," correctly.
C613-10524-00-REV L

AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
AR2010V
AR2050V
SBx908
IE200
IE300
IE510
x210
x230
x310
x350
x610
x930
IX5
CR-55337 802.1x Previously, the 802.1q tagged packets that contained PPPoE – – – – – – – – – – – – – – – – – Y –
Malware Protection session headers would not be processed by the Malware
PPPoE Protection engine.
CR-55328 AMF Previously, the AMF auto-recovery would occasionally fail to – – – – Y Y Y Y Y Y Y – Y Y Y – – – Y
work.
CR-54815 Energy Efficient With this software update, the supported port speed on the – – – – – – – – – – – – – – Y – – – –
Ethernet SBx81XLEM/XT4 expansion module for the SBx81XLEM is
limited to 10G only when EEE is enabled.
In other words, the port will only go into EEE mode when it is
running at 10G speed. If the port is running at 1G, it will not be
able to go into EEE mode.
CR-55372 HTTP Service Previously, it was possible to access the HTTP SSL certificates Y Y Y Y Y Y – Y Y Y Y – Y Y Y – – Y –
and HTTP server configuration over HTTPs without
authentication if a GUI was not installed.
CR-55034 Logging Previously, there was an unnecessary amount of logging of the – – – – – – – – – – Y – – – – – – – –
Switching Layer 2 switching processes to the tech-support.
With this software update, this logging has been reduced to a
more useful amount.
CR-55246 SSH With this software update, as required by Common Criteria, the – – – – – – – – – – Y – – – – – – – –
ECDSA host and user key generation for SSH is now supported
in secure mode.
C613-10524-00-REV L
AR3050S/AR4050S
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
AMF Cloud
x510, 510L
AR2010V
AR2050V
SBx908
IE200
IE300
IE510
x210
x230
x310
x350
x610
x930
IX5
CR-55423 SSH Previously, SSH did not work with Digital Signature Algorithm Y Y Y Y Y Y – Y Y Y Y – Y Y Y – – Y –
(DSA).
CR-55472 SSH Previously, in the crypto secure mode, it was possible to select – – – – – – – – – – Y – – – – – – – –
DSA and RSA1 public key-chain to known hosts. This should
not be allowed under Common Criteria secure mode.
CR-55592 SSH With this software update, the DSA with diffie-hellman group1 – – – – – – – – – – Y – – – – – – – –
key exchange algorithm is re-enabled for SSH server.
CR-55292 Stacking Previously, on a SBx8100 stack, a backup member rejoining the – – – – – – – – – – – – – – Y – – – –

stack could fail to rejoin due to software lock-up.
CR-55311 System Previously, on an AR-Series router, the firewall TCP connection – – – – – – – – – – – – – – – – – Y –
timeout would reset to the default value of 300 seconds, even if
it was configured to a different timeout value.
CR-55342 Triggers Previously, there was a delay before linkdown triggers would – – – – – – – – – – Y – – – – – – – –
execute their associated script(s).
CR-55605 VRRP SH310, IE200, IE300, x230, x310, IX5, x510, x610, SBx908, x930, – – – – Y Y – Y – Y Y Y Y Y Y – Y Y Y
DC2552, SBx81CFC400, SBx81CFC960, AR4050S, AR3050S, AR2050V
Previously, a VRRP role change from backup to master would
occasionally cause packets to be routed via the CPU rather than
in hardware, and hence severely impacted the performance of
the switch.
CR-55451 Web Control With this software update, Web Control now consumes less – – – – – – – – – – – – – – – – – Y –
system resources whilst blocking an HTTP POST.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x510, 510L
AR2010V
AR2050V
AR3050S
AR4050S
SBx908
IE200
IE300
IE510
VAA
x210
x230
x310
x610
x930
IX5
CR-55440 Stacking Previously, on certain x510, x610, and DC2500 variant – – – – – – – Y Y – Y – – – – – – – –
switches, when stacking was disabled, pluggable modules
could fail to be detected by the switch in combo ports, SFP+
ports or QSFP ports and would not be shown in the command
show system pluggable.
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x510, 510L
AR2010V
AR2050V
AR3050S
AR4050S
SBx908
IE200
IE300
IE510
VAA
x210
x230
x310
x610
x930
IX5
CR-55297 Malware Previously, IDS could restart unnecessarily after a Malware – – – – – – – – – – – – – – – – Y Y –
Protection protection resource file update occurred.
C613-10524-00-REV L
CR-55327 802.1x Previously, a supplicant that was connected to a switch via Y Y Y Y Y Y Y Y Y – Y Y Y Y – – – – –

MAC-based authentication would only be successfully
authenticated once.
If the MAC authentication failed, then the supplicant could fail
to be re-authenticated unless the clear mac or dot1x init
command was issued.

SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x510, 510L
AR2010V
AR2050V
AR3050S
AR4050S
SBx908
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-55203 AMF Previously, a switch configured as an AMF controller would – – – – – – – – – – – – – Y – – – – –
reboot unexpectedly due to unnecessary memory
consumption.
CR-55191 Antivirus Previously, HTTP traffic may have been improperly blocked – – – – – – – – – – – – – – – Y Y Y –
when Antivirus protection was enabled.
CR-55278 DPI Firewall Previously, if an AR Series Firewall was already running – – – – – – – – – – – – – – – – Y Y –
under high load, DNS changes on the unit could cause
Antivirus or Web Control to block all HTTP traffic.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x510, 510L
AR2010V
AR2050V
AR3050S
AR4050S
SBx908
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-55217 Environmental Previously, the speed of the fan on a DC2500 Series switch – – – – – – – – – – Y – – – – – – – –
Monitoring would not return to normal speed after restart.
CR-55295 Environmental Previously, entering the show system command on a CFC400 – – – – – – – – – – – – Y – – – – – –
Monitoring would not display the DC power supply unit.
CR-55051 GUI Previously, the SBx8100 series switches used incorrect – – – – – – – – – – – – Y Y – – – – –
SNMP indexing for the resource MIB.
CR-54655 Hardware Health Previously, on extremely rarely occasions, the backplane ports – – – – – – – – – – – – – Y – – – – –
Monitoring of a VCS plus switch might not link up after a system reboot.
CR-54971 Hot Swap Previously, rebooting a line card would sometimes cause a – – – – – – – – – – – – Y Y – – – – –
CFC960 to restart unexpectedly.
CR-55066 IDS, IPS Previously, FTP throughput on AR-series firewalls was less – – – – – – – – – – – – – – Y Y Y Y –
than expected when the intrusion detection feature was
enabled.
CR-55157 Pluggable Previously, the “Methode Elec 40G DAC” cable with part – – – – – – – – – – – – Y Y – – – – –
Transceivers number “S1348” was not recognised on the SBx81XLEM.
CR-55200 Pluggable Previously, the ports on the SBx81GS24a line card would – – – – – – – – – – – – – Y – – – – –
Transceivers display “down” in the output of the command show interface
even when they were linked up.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x510, 510L
AR2010V
AR2050V
AR3050S
AR4050S
SBx908
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-55323 PPP Previously, packets received on an Ethernet interface that had – – – – – – – – – – – – – – – – Y Y –
Malware PPPoE session headers, were not being scanned by some
Protection Malware detection processes, even when the Malware
protection was enabled.
CR-55250 System Bootup Previously, it was possible for continuous reboot prevention to – – Y – – Y Y Y Y Y Y – – – – – – – –
fail to detect process failures.
CR-55321 System Bootup With this software update, it is now possible to configure the – – – – – – – – – – – – – Y – – – – –
atmf controller command even if the device does not have an
AMF controller license installed on it.
However, the controller feature will not actually function until
a valid AMF controller license is added.
CR-55109 VCStack Previously, when triggers were used to change configuration – – Y – – Y Y Y Y Y Y Y Y Y – – – – –
Trigger on a stack, it was possible for part of the configuration to be
lost in an failover event. Any OSPF, RIP and BGP
configuration would be affected.
CR-55096 VRF-lite Previously, if a switch was configured with a VRF interface, – – – – – – – – Y Y Y Y Y Y – – – – –
the following error message would appears in log after reboot:
“[DECODE] Open: Invalid Router ID”
C613-10524-00-REV L

SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x900 / SBx908
x510, x510L
AR2050
AR2010
AR3050
AR4050
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-53339 AMF Previously, when an AMF node was replaced and – – – – Y Y Y Y Y Y Y Y Y Y – – – – Y
automatically recovered, it occasionally failed to
communicate with the adjoining AMF node for recovery file
retrieval, causing the recovery to fail.
CR-54357 AMF Previously, the "no valid release license" error message would – – – – – – – – – – – – – – – – – – Y
be displayed at login on an AMF Cloud Master or Controller
even though there was a proper license installed.
CR-54391 AMF Previously, the AMF Link Information Database was not Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y Y
updating correctly when a transition event occurred.
For example, when a ‘master’ transitioned to a ‘member’ and
vice versa, the event was not reflected on the Link Information
Database.
CR-54108 CLI Previously, the alarm relay output from the command show – – Y – – – – – – – – – – – – – – – –
system environment on a stacked IE510 switch, was
inconsistent across stack members.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x900 / SBx908
x510, x510L
AR2050
AR2010
AR3050
AR4050
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-54389 IGMP Previously, repeated IGMP group Join and Leave events could Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y –
cause a slow memory leak.
CR-54488 IGMP, Previously, a switch could unnecessarily log info-level Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y –

Multicast messages like ‘Stopping STAT timer’ and ‘Starting STAT
Routing timer with 210 seconds’ when static IGMP groups were
configured.
CR-53205 LACP Previously, configuring static or dynamic link aggregation on Y – – – – – – – – – – – – – – – – – –

an IE200 switch was not working as expected.
CR-53705 OSPFv3 Previously, adding an IPSec authentication on a VLAN Y Y Y – – – – – Y Y Y Y Y Y – – – – –

interface with already established OSPFv3 neighbours would
cause a "Failed to write IPSec interface configuration" error
message being logged, although the IPSec configuration had
been successfully implemented. The error message was
spurious.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x900 / SBx908
x510, x510L
AR2050
AR2010
AR3050
AR4050
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-52980 OSPFv3, Previously, there was a small chance that IPv6 routes leant by – – Y – – Y – Y Y Y Y Y Y Y – – Y Y –
IPv6, OSPFv3 could be installed without the link-local nexthop
Stacking address set. This affected the traffic forwarding for all intra-
area and AS external prefixes associated with that missing
nexthop.
CR-51527 PoE Previously, on an IE200 switch, if the"power-inline usage- Y – – – – – – – – – – – – – – – – – –

threshold" was reached and then set to a higher value, no
SNMP trap would be sent after a PoE-device was disabled or
unplugged.
CR-54432 PoE Previously, the PoE Firmware Updater on the SBx81GP24 – – – – – – – – – – – – – Y – – – – –

Line card might fail to run a firmware update.
CR-54224 Policy-based Previously, policy-based routing would still route packets as – – – – – – – – – – – – – – Y – Y Y –

Routing per the configured rule even if the destination network was
unavailable.
CR-54326 QoS Previously, attaching a policy-map on a port would cause an Y – – – – – – – – – – – – – – – – – –

Hardware IE200 switch to reboot unexpectedly.
C613-10524-00-REV L
SBx8100 CFC400
SBx8100 CFC960
DC2552XS/L3
x900 / SBx908
x510, x510L
AR2050
AR2010
AR3050
AR4050
IE200
IE300
IE510
x210
x230
x310
x610
x930
VAA
IX5
CR-54312 QoS Previously, on a IE200 switch, some traffic such as STP and Y – – – – – – – – – – – – – – – – – –
hardware LLPD was being incorrectly allocated to a lower priority
queue on the link between the switch chip and the CPU. This
could result in these packets being lost if a high rate of less
important data was being sent to the CPU.
CR-54213 System Previously, the error message: “ECO button could not be – Y – – – – – – – – – – – – – – – – –
found” was displayed at bootup, even though the IE300 switch
does not have an ECO button.
CR-54382 System Previously, the SBx81XLEM linecard could restart – – – – – – – – – – – – – Y – – – – –

unexpectedly.
CR-54407 System Previously, the device would send packets from the CPU via – – – – – – – – – – Y – – – – – – – –
an incorrect CPU priority queue.
CR-54535 Unicast Previously, equal-cost multi-path routing was not working – Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y –

Routing properly.
C613-10524-00-REV L

Activar Web Allied

Uploaded by

Copyright:

Available Formats

Activar Web Allied

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Activar Web Allied

Uploaded by

Copyright:

Available Formats

AlliedWare Plus Software Maintenance Release Note: 5.4.6-2.

Software Maintenance Release Note

AlliedWare Plus™ Software Version 5.4.6-2.4

Read this maintenance release note in conjunction with the:

Supported Models and Software File Names

Models Series Release File Date GUI file

FS980M/9 FS980M FS980-5.4.6-2.4 rel January/2017 FS980-gui_546_20.jar

AT-GS924MX GS900 GS900-5.4.6-2.4.rel January/2017 GS900-gui_546_04.jar

AT-XS916MXT XS900 XS900-5.4.6-2.4.rel January/2017 XS900-gui_546_11.jar

AT-x210-9GT x210 x210-5.4.6-2.4.rel January/2017 x210-gui_546_11.jar

AT-x230-10GP x230 x230-5.4.6-2.4.rel January/2017 x230-gui_546_20.jar

AT-x310-26FT x310 x310-5.4.6-2.4.rel January/2017 x310-gui_546_11.jar

AT-IE200-6FT IE200 IE200-5.4.6-2.4.rel January/2017 ie200-gui_546_11.jar

AT-IE510-28GSX-80 IE510 IE510-5.4.6-1.4.rel January/2017 ie510-gui_546_04.jar

AT-IX5-28GPX IX5-5.4.6-2.4.rel January/2017 IX5-gui_546_11.jar

Table 1: Supported switch models and software file names

Models Series Release File Date GUI file

AT-x510-28GTX x510 x510-5.4.6-2.4.rel January/2017 x510-gui_546_11.jar

IE510-28GSX-80 IE500 IE510-5.4.6-2.4.rel January/2017 IE510-gui_546_04.jar

AT-x610-24Ts x610 x610-5.4.6-2.4.rel January/2017 x610-gui_546_11.jar

SwitchBlade x908* SBx908 SBx908-5.4.6-2.4.rel January/2017 SBx908-gui_546_11.jar

AT-x930-28GTX x930 x930-5.4.6-2.4.rel January/2017 x930-gui_546_11.jar

AT-DC2552XS/L3 dc2500-5.4.6-2.4.rel January/2017 dc2500-gui_546_11.jar

AT-SBx81CFC400 SBx8100 SBx81CFC400-5.4.6- January/2017 SBx81CFC400_gui_546_20.jar

AT-AR2010V VPN AR2010V-5.4.6-2.4.rel January/2017 n/a

AT-AR3050S NGFW AR3050S-5.4.6-2.4.rel January/2017 n/a

AMF Cloud vaa-5.4.6-2.4.iso January/2017 n/a

Installing the GUI to your Switch using an SD Card or

4. Configure the gateway.

5. Create a user account.

6. Ensure HTTP service is enabled.

7. Log into the GUI.

Installing the GUI to your Switch via TFTP Server

2. Copy the GUI applet.

3. Assign the IP addresses.

4. Configure the default gateway.

5. Copy the GUI Java applet to your switch.

6. Create a user account.

7. Start the Java Control Panel, to enable Java within a browser .

9. Log into the GUI.

Installing and Enabling this Version

To install this version:

On the SwitchBlade x8100 Series switches with a SBxCFC400 controller card

Upgrading the Software of a VAA

To change the current .iso software image:

Upgrading a VAA running under Amazon Web Services (AWS)

Important Information about Compatibility with Earlier

Loss of auto-synchronization compatibility on VCS

This affects VCStack, standalone dual-CFC SBx8100 switches, and VCStack

Consequences for VCStacks

Consequences for a single SBx8100

To recover from this situation, see “Upgrading/downgrading a CFC” on

Allied Telesis Inc.

Consequences for a VCStack Plus Pair of SBx8100 chassis

ISSU (In-Service Software Upgrade) on SBx8100 with

ISSU is not supported on other platforms.

You may also find the following How To Note useful:

Issues Resolved in 5.4.6-2.4

CR-56148 NTP Previously, NTP would fail to synchronize the time. Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y –

Issues Resolved in 5.4.6-2.3