Allied Telesis Patch 1 AT-S63 Instruction Manual

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 1 Allied Telesis, Inc.
AT-S63 Version 3.1.0 Patch 1
Management Software for the
AT-9400 Basic Layer 3 Gigabit Ethernet Switches
Software Release Notes
Please read this document before you begin to use the management software.
Supported Platforms
AT-S63 Version 3.1.0 Management Software is supported on the following AT-9400 Gigabit
Ethernet Switches:
Note:
AT-9400 Basic Layer 3 Switches running Version 2.1.0 or earlier of the AT-S63 Management
Software have to be upgraded to Version 2.2.0 before they can be upgraded to Version 3.1.0.
For the Internet locations of the management software for Allied Telesis products, refer to
“Obtaining Management Software Updates” on page 14.
This version is not supported on the following AT-9400 Switches:
For information on the availability of future releases of the management software for the Layer 2+
switches, contact your Allied Telesis sales representative.
This release supports the following redundant power supply on the AC models:
AT-RPS3204
For a list of supported GBIC, SFP, and XFP modules, contact your Allied Telesis sales
representative.
Basic Layer 3 Models AT-9424T (AC)
AT-9424Ts (AC)
AT-9424Ts/XP (AC)
AT-9448T/SP (AC)
AT-9448Ts/XP (AC)
Layer 2+ Models AT-9408LC/SP (AC)
AT-9424T/GB (AC)
AT-9424T/SP (AC)
AT-9424T/GB-80 (DC)
AT-9424T/SP-80 (DC)

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 2 Allied Telesis, Inc.
Caution:
The software described in the documentation contains certain cryptographic functionality and its
export is restricted by U.S. law. As of this writing, it has been submitted for review as a “retail
encryption item” in accordance with the Export Administration Regulations, 15 C.F.R. Part 730-
772, promulgated by the U.S. Department of Commerce, and conditionally may be exported in
accordance with the pertinent terms of License Exception ENC (described in 15 C.F.R. Part
740.17). In no case may it be exported to Cuba, Iran, Iraq, Libya, North Korea, Sudan, or Syria. If
you wish to transfer this software outside the United States or Canada, please contact your local
Allied Telesis sales representative for current information on this product’s export status.
Product Documentation
Refer to the Allied Telesis web site at www.alliedtelesis.com for the latest installation and user
guides.
Switch Models and Management Software Versions
The following table lists the AT-9400 Switches and the version number of the AT-S63
Management Software where each model was initially supported. If you decide to load an older
version of the management software onto a unit, refer to the table to determine whether the
version supports the switch. For example, support for the AT-9424Ts Switch was introduced in
version 2.1.1. Any attempt to load an earlier version of the software on that model will be
unsuccessful.
Model AT-S63 Management
Software Version
AT-9424T/GB 1.0.0
AT-9424T/SP 1.0.0
AT-9408LC/SP 1.1.0
AT-9448Ts/XP 1.3.0
AT-9448T/SP 2.0.0
AT-9424Ts/XP 2.0.0
AT-9424Ts 2.1.1
AT-9424T 3.1.0

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 3 Allied Telesis, Inc.
Stacking Features supported in Version 3.1.0 Patch 1
The following features are supported across a stack
Port statistics
Port configurations
Remote Telnet management
Event log
Spanning tree protocol (STP)
Port-based and tagged VLANs
All other features in the AT-S63 Management Software are automatically deactivated when a
stack is powered on.
Stacking Configuration Tips
When stacking more than two switches, use the AT-9424Ts or AT-9424Ts/XP as the master
and backup master switches.
When adding a member switch to a stack, add one switch at a time. Ensure that the stack is
up and stable before adding another member switch.
All ports are disabled during stack discovery. This means that each time you add or remove a
switch from the stack, switching is suspended across all ports until the discovery process is
complete.
Remember that there are different configuration files for the standalone configuration and the
stacking configuration. Be sure to create your desired configuration on both images in case
there is a stack failure.
Table sizes do NOT increase in Stack mode. The table sizes in a stack are:
— 16k MAC Addresses
— 2k ARP Entries
— 4094 VLANs
A stack can have up to four 48-port AT-9448Ts/XP Switches and two 24-port AT-9424Ts / AT-
9424Ts/XP (Master) or eight 24-port AT-9424Ts / AT-9424Ts/XP Switches.

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 4 Allied Telesis, Inc.
Known Issues
MAC address-based port security and the limited security mode. The limited security mode in
MAC address-based port security is nonfunctional. (5327)
Enhanced stacking. The AT-9400 Switch must have an IP address to be a slave switch in an
enhanced stack. A routing interface that specifies the switch’s IP address has to be assigned
to the common VLAN of the stack and the interface has to be designated as the switch’s local
interface. This rule applies even when the Default_VLAN is acting as the common VLAN of
the switches. (5369)
802.1x Control Direction parameter. The Control Direction parameter for 802.1x authenticator
ports has an Ingress option for forwarding egress broadcast and multicast traffic when the
ports are in the unauthorized state. This option is nonfunctional and instead blocks these
packets. (5487)
Routing Information Protocol (RIP) and new, inactive routing interfaces. When transmitting a
switch’s routing table, RIP erroneously includes inactive routing interfaces. This problem is
limited to new routing interfaces and disappears after a routing interface has changed to the
active status for the first time. Afterwards, RIP transmits the interface only when it is active.
(5753)
Enhanced stacking and the web browser management interface. The enhanced stacking
feature in the web browser interface is nonfunctional. As an alternative, use the menus or
command line interface to access switches with enhanced stacking. (5871)
802.1x authentication ports and ARP packets. 802.1x authentication ports in the
unauthorized state forward ARP packets instead of blocking them. (5880)
LACP aggregators. Allied Telesis does not recommend using the LACP feature in this release
of the management software unless the aggregators will be part of the Default_VLAN. A
problem occurs if you create LACP aggregators consisting of ports from VLANs other than
the Default_VLAN. During the next reset the switch will not recreate the VLANs and will
instead add the aggregators to the Default_VLAN. (5894)
Unknown unicast rate limiting. Unknown unicast rate limiting has been changed at the driver
level to accommodate stacking and can no longer be disabled. At the default setting, the rate
limit for unknown unicast packets for each port is 25 packets per second. This should not be
changed when a switch is part of a stack. If you are operating the switch as a stand-alone
device and want to increase rate limiting for unknown unicast packets on all the ports, issue
this command:
set switch port=all unkucastratelimiting=yes unkucastrate=
value
The value parameter has a range of 0 to 262,143 packets per second.
Since this change was made at the driver level, the SHOW SWITCH PORT command will not
display the correct status of unknown unicast rate limiting on the ports of a switch at the
default setting. It will show the feature as disabled, when in fact it is enabled.
Routing Information Protocol (RIP) on the AT-9448Ts/XP Switch. The performance of RIP on
the AT-9448Ts/XP Switch might not be predictable. The switch might not update its routing
table in response to routes received from other units and may lose routes. (5422)

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 5 Allied Telesis, Inc.
Stack Configuration limit with AT-9448Ts/XP as a “Master”. The AT-9448Ts/XP can act as the
master in a stack of two switches only. The AT9424Ts or AT9424Ts/XP must be used as the
master with three or more switches in a stack.
IP Addressing and Routing. Although software will allow you to configure IP interfaces on any
VLAN within the switch, only one IP address per stack is supported. Layer 3 switching is not
supported. (6074)
Forwarding Database (FDB). In a stacking configuration, the master FDB may display
addresses that have moved or no longer exist on a member of the stack for a period up to the
age out time. This occurs because all addresses on a port are deleted on the member switch
when a port is disconnected on the member and this information is not communicated to the
master. In addition, addresses on a member switch may not appear on the software FDB
even though they are learned locally. (6159)
Default Gateway/Route. If the topology of the stack is changed from a ring to a chain or from
a chain to a ring, the default gateway/route will be lost until you reboot the stack. This affects
both static and dynamic addresses. (6146)
Adding Ports to VLANs. If you add ports to an existing VLAN, the ports are not be included in
the VLAN until the configuration is saved and the stack is rebooted. This issue does not apply
to new VLANs. (6121)
Setting stack to default configuration. Do not use the “set config=none“ command while in
stack mode. If this command is used in the stack mode, the standalone “boot.cfg” file will be
loaded after a reboot. To set a stack to the default configuration, delete the “stack.cfg” file and
then reboot. Once a “save config” is performed, the stack.cfg will be created with the default
configuration. (6158)
Resolved Issues
Multiple supplicants and 802.1x port-based network access control. The multiple operating
mode for 802.1x authenticator ports was nonfunctional. This problem has been resolved. In
order for authenticator ports to work properly when set to the multiple operating mode, the
ports have to be connected to other Ethernet switches or other point-to-point devices.
Authenticator ports do support multiple supplicants when connected to devices that are not
point-to-point, like Ethernet hubs, but you have to configure the ports to single operating
mode and enable the piggy-back feature. (5431)
MAC address-based authentication in 802.1x port-based network access control. The MAC
address-based method of authentication in 802.1x port-based network access control was
unreliable. This problem has been resolved. (5425)
Class of Service (CoS) priority override. The priority override feature, for applying a
temporary CoS priority value to the tagged and untagged ingress traffic on a port, was
nonfunctional. This problem has been resolved. (5492)
MAC address-based virtual LANs. MAC address-based virtual LANs did not work. This
problem has been resolved. (5384, 5387)
Compact flash memory card slot. This AT-S63 Management Software periodically had
difficulties accessing a compact flash memory card on the AT-9424Ts, AT-9424Ts/XP, and
AT-9448Ts/XP switches. This problem has been resolved. (5509)
Operational Notes

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 6 Allied Telesis, Inc.
Maximum bandwidth parameter in QoS policies. A QoS policy that has multiple traffic classes
with different values for the maximum bandwidth parameter uses the lowest specified
maximum bandwidth value for traffic flows that match more than one traffic class. (4137)
VLAN ingress filtering. Untagged packets on the AT-9424Ts and AT-9424Ts/XP Switches may
periodically cross VLAN boundaries and be retransmitted as tagged packets when the VLAN
ingress filtering feature for tagged packets is disabled. (4455)
LACP aggregators. The ports of an LACP trunk must be untagged members of the same
VLAN. The management software does not always display an error message if you violate
this rule while modifying port-based and tagged VLANs on the switch. For example, the
management software will not display an error message if you move a port that is part of an
LACP trunk to a different VLAN or if you change the port’s status from untagged to tagged.
(4585)
Web server. The default setting for the web server on the switch has been changed from
enabled to disabled. To use a web browser to manage the switch, you must first enable the
server with the ENABLE HTTP SERVER command.
Classifier criteria. Access control lists and Quality of Service policies cannot filter on the
following combinations of classifier criteria:
— VLAN ID with source or destination IP address.
— Protocol with source or destination IP address
This rule applies whether the criteria are in the same classifier or in different classifiers
applied to the same access control list or Quality of Service policy.
Spanning tree and LACP trunks. A spanning tree protocol on a switch with two or more LACP
trunks uses the trunk ID number to select a trunk to place in the blocking state if the trunks
form a network loop. The trunk ID number is automatically assigned by the management
software when an aggregator is created, starting with 0 (zero) and incremented by 1 with
each new aggregator. The lower the trunk ID number, the higher the priority. For instance, if a
switch has two LACP trunks, a spanning tree protocol will block the ports of the trunk with the
higher ID number (lower priority) should it determine that the trunks form a loop. (4261)
Denial of Service defense mechanisms. The operation of a Denial or Service defense
mechanism on the switch might be unpredictable when a defense is assigned to more than
one port or when more than one defense is assigned to the same port. This issue can be
avoided by not assigning a defense mechanism to more than one port or more than one
defense mechanism to a port. This issue is limited to the AT-9424Ts and AT-9424Ts/XP
switches. (4196)
QoS policies and unicast and multicast addresses. The filtering properties of a QoS policy
are designed for known unicast addresses. The behavior of a policy may be unpredictable if it
filters on unknown unicast addresses or known or unknown multicast addresses. (3196)
Lowest numbered port in an LACP aggregator. You cannot delete the lowest numbered port
from an LACP aggregator, referred to as the base port, or add a port to an aggregator that is
below the base port. The OperKey parameter for the ports in an aggregator is based on the
lowest numbered port and cannot be changed after the aggregator is created. For example, if
you create an aggregator of ports 10 to 15 on a switch, you cannot later delete port 10 from
the aggregator or add a port less than port 10. You must recreate the aggregator if you need
to change the base port. (4369)
Saving a configuration. The management software on the switch may experience a problem if
you save configuration changes in rapid succession. To avoid this issue, you should wait for

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 7 Allied Telesis, Inc.
the Fault LED on the front panel of the switch to go off after saving a configuration change
and before saving another configuration change. If you are in a different location from the
switch and cannot view the Fault LED, wait 30 to 45 seconds between your save commands.
(2683)
Multiple VLAN modes and IPv4 packet routing. The 802.1Q-compliant and non-802.1Q-
compliant multiple VLAN modes do not support IPv4 packet routing. You cannot configure
routing interfaces when the switch is running in either of these VLAN modes, and all existing
routing interfaces, with the exception of the local interface, are deleted when one of these
VLAN modes is activated. To assign an IP address to a switch running one of these VLAN
modes, you must create one routing interface and designate it as the local interface while the
switch is running in the user-configured VLAN mode, and afterwards change the switch’s
VLAN mode to 802.1Q-compliant or non-802.1Q-compliant. The local interface is
automatically moved to the VLAN on port 1 of the switch. (3806)
Switch to switch upload of a configuration file. The AT-S63 Management Software User
Guides state that the routing interface commands in the configuration file on a master switch
are retained when the file is uploaded to a slave switch. This is incorrect when the file being
uploaded is the master switch’s active configuration file. To prevent an IP address conflict on
the units, the transfer automatically removes all routing interface commands from the active
configuration file as it is uploaded. This rule only applies to the master switch’s active
configuration file. The transfer retains the routing interface definitions when you upload any
other configuration file from a master switch to a slave switch. To avoid an IP address conflict
in this situation, it may be necessary to modify the IP address assignments of the routing
interfaces on the switch that received the file.(4272, 5873)
Telnet management session. Changing the VLAN mode of a switch (e.g., from the user-
configured VLAN mode to a multiple VLAN mode) from a remote Telnet management session
may end your management session. To continue managing the switch, you must reestablish
the management session (3806)
SNMPv3 management. The enhanced stacking feature is not supported from SNMPv3.
(4065)
AtiStkSwVlanConfigEntry MIB table. The response time of the management firmware on the
switch will be slow if you have more than one instance of the AtiStkSwVlanConfigEntry MIB
table open at a time. (2231)
Compact flash card. Removing a compact flash card from the switch while the management
software is writing a file to it may cause the switch to stop responding to management
commands and forwarding network packets. To avoid this issue, never remove a compact
flash card from the switch while the Fault LED on the front panel is on. Wait for the Fault LED
to turn off before removing the card.(4253)
LACP priority value and the event log. A change to a switch’s LACP priority value is
registered in the event log with a message that reflects the current status of LACP, rather
than the change to the priority value. The log message is either “lacp:enabled” or
“lacp:disabled.” (3345)
MAC address-based VLANs and static trunks. The documentation states that the ports of a
MAC address-based VLAN form a community and that the assignment of a MAC address to
one port in a VLAN is equivalent to assigning it to all ports. This is true except in the case
where the ports of a MAC address-based VLAN encompass a static port trunk, in which case
the same MAC addresses must be assigned to all the ports in the trunk. (3249)

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 8 Allied Telesis, Inc.
File upload or download. The switch’s response to management instructions may be slow
while it uploads or downloads a file to the file system.
Flow control and back pressure. Flow control and back pressure are operational among
devices connected to ports 1 through 12 or ports 13 through 24 on the AT-9424T/GB and
AT-9424T/SP switches, but not between devices connected to ports 1 through 12 and 13
through 24. (1321, 1322)
Reserved multicast traffic and port mirroring. The destination port of a port mirror may
transmit duplicates of some reserved multicast traffic, such as STP BPDUs and other control
packets. The duplication results from the destination mirror port transmitting both the
reserved multicast traffic it receives from flooded multicast traffic and the same multicast
traffic from the mirrored ports. (3055)
Fiber optic port configuration display. The Auto-Negotiation, speed, and duplex mode settings
in the menus interface for ports 23 and 24 on the AT-9424T/GB and AT-9424T/SP switches
always reflect the settings of the corresponding twisted pair ports 23R and 24R. They do not
reflect the current settings of an active GBIC or SFP fiber optic port. (3047)
GVRP compatibility. There may be some compatibility issues with GVRP and other switches.
To work around this issue, change the Join and Leave time from the defaults to: Join Timer =
60 and Leave Timer = 120.
Port configuration. The speed, duplex mode, and MDI/MDIX settings of a 10/100/1000Base-T
twisted pair port are changed as a unit when multiple ports are configured simultaneously.
The settings of the lowest numbered port being configured are automatically copied to the
other ports. For example, if you configure ports 1 to 4 simultaneously and change the MDI/
MDIX setting, the speed and duplex mode settings of port 1, along with the new MDI/MDIX
setting, are copied to ports 2 to 4. (1262)
Static and LACP port trunks and load distribution methods. The following load distribution
methods for static and LACP port trunks are nonfunctional: source IP address, destination IP
address, and source/destination IP addresses. The switch uses source MAC address,
destination MAC address, or source/destination MAC addresses, respectively, if a
nonfunctional load distribution method is selected.
Jumbo frames. Frame loss may occur when jumbo frames (1522 bytes or larger) are
transferred to more than two ports. (1412, 2783, 2792)
Xmodem downloads. The switch does not respond to echo requests or send or respond to
STP BPDU packets during an Xmodem download of system software. Also, echo request
responses are slowed when there is a TFTP transfer in progress and the echo requests are
received within the same port group as the TFTP server. (1663, 1582)
SFP and GBIC ports. The switch considers the fiber optic port on an optional SFP or GBIC
module in the AT-9424T/GB and AT-9424T/SP switches as active even if the port is receiving
a signal but has not established a valid link with the remote node. If an optional fiber optic port
loses or is unable to establish a link but is receiving a signal, it remains as the active port and
the switch does not activate the corresponding twisted pair port 23R or 24R. (2850)
Web browser interface. The web browser interface works best with Microsoft Internet
Explorer version 6.0 and above. Results using other versions or other web browser
applications may vary.
Configuration files. Do not use Microsoft NotePad to edit or view a configuration file. Some
versions of NotePad may add formatting codes to the file. Use WordPad instead or some

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 9 Allied Telesis, Inc.
other text editor that will not add formatting codes to the file. When saving the file, do not
change the “.cfg” extension in the filename or save the file with formatting codes.
Enhanced stacking. The IP address 172.16.16.16 is reserved for the enhanced stacking
feature. Do not assign this address to any device in the same subnet as an enhanced stack.
Login password. The maximum length of a login password is 16 alphanumeric characters for
manager accounts created through the RADIUS and TACACS+ authentication protocols and
supplicant accounts for 802.1x port-based network access control. Passwords that exceed
this limit will not work.
TACACS+. The TACACS+ client software on the switch supports Password Protection
Protocol (PAP), but not Challenge Handshake Authentication Protocol (CHAP) or AppleTalk
Remote Access Protocol (ARAP). (1078)
Port settings. When removed from a port trunk, a port retains the settings (e.g., speed and
duplex mode) that it had as a member of the trunk. The parameter settings are not returned
to the default values. (2144)
MAC addresses. You must move the cursor manually from field to field when entering an IP
or MAC address in the web browser interface. The cursor does not move automatically as
you enter the parts of an address. (1699, 2123)
SNTP. The SNTP client software on the switch sends a Transmit Time Stamp with a value
NULL when synchronizing with a Network Time Protocol server. This does not affect the
operation of the SNTP client software. (1676)
IGMP snooping. When IGMP snooping is enabled and ingress filtering is disabled, the switch
does not register tagged IGMP queries in the IGMP routers list. (1493)
SFP modules and the AT-9408LC/SP switch. Always disconnect the fiber optic cable from an
SFP module in an AT-9408LC/SP switch before removing the module. The L/A LED for the
slot may remain on if you remove an SFP module while it has a link to an end node. This
problem does not affect the operation of the switch or the SFP slot. The L/A LED goes off the
next time you install an SFP module in the slot.
“set stack” command. When you are in a standalone (and Auto mode) configuration, the
command “set stack moduleid=1 newmoduleid=static” does not work. You must enter “set
stack moduleid=1 newmoduleid=1” for the standalone configuration. When you are in a
stacking configuration, either of the above commands will work.
Features History
Version 3.1.0
Support for the AT-9424T Basic Layer 3 Switch
Version 3.0.0:
Stacking
Virtual Router Redundancy Protocol (VRRP)
Ethernet Protection Switching Ring (EPSR) snooping
Internet Protocol version 4 packet routing enhancements:
— Auto-summarization of routes
— Split horizon with poison reverse
— DHCP/BOOTP relay

AT-S63 Version 3.1.0 Patch 1 Software Release Notes
PN 613-000915 Rev A 10 Allied Telesis, Inc.
802.1x port-based network access control. Added the following authentication methods:
— EAP-TLS (Extensible Authentication Protocol - Transport Layer Security)
— EAP-TTLS (Extensible Authentication Protocol - Tunneled Transport Layer Security)
— PEAP (Protected Extensible Authentication Protocol)
Version 2.2.0:
No new features.
Version 2.1.1:
The number of cooling fans in the AT-9424Ts switch was reduced from four to three. The
AT-S63 Management Software was updated to reflect the change.
Version 2.1.0:
Multiple IPv4 routes with Equal Cost Multi-path (ECMP). The switch now supports ECMP and
multiple routes to the same remote destination.
Variable length subnet masks for IPv4 routing. Previously, a byte in a subnet mask for a route
in the IPv4 routing table had to be 0 or 255. The switch now accepts masks of variable length.
Multiple default routes. In the previous version, there could be only one default route for the
IPv4 packet routing feature and the route was not propagated by RIP. In this version, the
routing table can store and propagate multiple static and dynamic default routes.
802.1x authenticator ports. The maximum number of supplicants that can be logged on to an
authenticator port running in the multiple operating mode has been increased from 20 clients
to 320 clients. However, the maximum number of logged on clients per switch remains the
same at 480 clients. (4186)
Note:
The IPv4 routing feature is not supported on the AT-9408LC/SP, AT-9424T/GB, and
AT-9424T/SP Switches. These switches support only one routing interface for assigning the
device an IP address.
Version 2.0.0:
Internet Protocol Version 4 (IPv4) packet routing. The AT-9400 Series switch features IPv4
packet routing with routing interfaces, static routes, and the Routing Information Protocol
versions 1 and 2.
Secure Shell (SSH) protocol server. The security of the SSH server on the switch has been
enhanced to prevent unauthorized management access to the switch. The AT-S63
Management Software now disables the SSH server, logs an event in the event logs with the
client’s IP address, and sends an SNMP trap if it detects fifty consecutive failed login
attempts from an SSH client.
Class of Service and Queue 7. The range of the maximum number of transmitted packets for
the CoS weighted round robin scheduling method has been changed for Queue 7 (Q7). The
range was 1 to 15; the new range is 0 (zero) to 15. Setting Q7 to 0 gives its packets priority
over packets in the other queues. No packets are transmitted from the lower priority queues
so long as there are packets in Q7. (3803)
Temperature threshold alert. The temperature threshold alert feature now has two levels. An
ambient temperature of 55°to 60° Celsius for ten minutes activates the first level. The switch
sends a SNMP trap and enters a warning event message in the event logs. The second level,