Download Allied Telesis AT-S63 Installation guide

AT-S63 Version 2.1.0
Management Software for the
AT-9400 Series Layer 2+ Gigabit Ethernet Switches
Software Release Notes
Please read this document before you begin to use the management software.
Supported Platforms
The AT-S63 Version 2.1.0 management software is supported on the following AT-9400 Series
Layer 2+ Gigabit Ethernet switches:
AC Models:
ˆ
AT-9408LC/SP
ˆ
AT-9424T/GB
ˆ
AT-9424T/SP
ˆ
AT-9424Ts
ˆ
AT-9424Ts/XP
ˆ
AT-9448T/SP
ˆ
AT-9448Ts/XP
DC Models:
ˆ
AT-9424T/GB-80
ˆ
AT-9424T/SP-80
This release supports the following redundant power supply:
ˆ
AT-RPS3204
(The redundant power supply is only supported on AC models.)
For a list of supported GBIC, SFP, and XFP modules, contact your Allied Telesis sales
representative.
Product Documentation
For hardware installation instructions, refer to the following guide:
ˆ
AT-9400 Series Layer 2+ Gigabit Ethernet Switches Installation Guide (PN 613-000357-00)
For management instructions, refer to the following guides:
ˆ
AT-S63 Management Software Menus Interface User’s Guide (PN 613-50570-00)
ˆ
AT-S63 Management Software Web Browser Interface User’s Guide (PN 613-50592-00)
ˆ
AT-S63 Management Software Command Line Interface User’s Guide (PN 613-50571-00)
All documents are available from the Allied Telesis web site at www.alliedtelesis.com.
PN 613-000631 Rev A
1
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
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.
Note:
The Public Key Infrastructure (PKI), Secure Sockets Layer (SSL), and Secure Shell (SSH)
encryption features, offered separately prior to version 2.0.0, are now standard components
of the AT-S63 management software.
What’s New in Version 2.1.0
Features
ˆ
Multiple IPv4 routes with Equal Cost Multi-path (ECMP). The switch now supports ECMP and
multiple routes to the same remote destination. For further information, refer to “Changes to
Internet Protocol Version 4 (IPv4) Routing in Version 2.1.0,” later in these software release
notes. For background information on the IPv4 packet routing feature and descriptions of the
command line commands, refer to Chapter 32, “Internet Protocol Version 4 Packet Routing,”
in the latest version of the AT-S63 Management Software Command Line Interface User’s
Guide.
ˆ
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.
For further information, refer to “Changes to Internet Protocol Version 4 (IPv4) Routing in
Version 2.1.0,” later in these software release notes.
ˆ
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. For further
information, refer to “Changes to Internet Protocol Version 4 (IPv4) Routing in Version 2.1.0,”
later in these software release notes.
ˆ
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)
PN 613-000631 Rev A
2
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
Note:
The IPv4 routing feature is fully supported on the following AT-9400 Series switches: AT-9424Ts,
AT-9424Ts/XP, AT-9448T/SP, and AT-9448Ts/XP. This feature is not supported on the
AT-9408LC/SP, AT-9424T/GB, and AT-9424T/SP switches. The latter switches support only one
routing interface to assign the device an IP address. For further information, refer to the latest
version of the AT-S63 Management Software Command Line Interface User’s Guide,
Known Issues
ˆ
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)
ˆ
802.1x "control direction" feature. The "control direction" feature of 802.1x port-based
network access control is nonfunctional for IGMP multicast packets when IGMP snooping is
enabled on the switch. This feature is suppose to control the forwarding of multicast and
broadcast packets by an authenticator port in the unauthorized state. When IGMP snooping
is enabled, an authenticator port always forwards IGMP multicast packets, regardless of the
status of the "control direction" feature. (4206)
ˆ
VLAN ingress filtering. Untagged packets may periodically cross VLAN boundaries and be
retransmitted as tagged packets from the switch’s ports when the VLAN ingress filtering
feature is disabled. The VLAN ingress filtering feature controls whether tagged packets are
filtered on the ingress or egress ports for the packets. Untagged packets are not suppose to
be affected by this feature and should never cross VLAN boundaries. (4455)
ˆ
LACP trunks. When a link is lost and later reestablished on an active port in an LACP trunk,
the switch may take upwards of 30 seconds before it begins to forward traffic again over the
reestablished link. (4514)
ˆ
SET IP ARP Command. The format of this command in AT-S63 versions 2.0.0 was as
follows: (4521)
set ip arp arp=ipaddress [interface=interface] [port=port]
[ethernet=macaddress]
In version 2.1.0 and all future versions, the format will not include the first “arp”:
set ip arp=ipaddress [interface=interface] [port=port]
[ethernet=macaddress]
ˆ
Tagged ports and LACP aggregators. An LACP aggregator can not contain tagged ports, but
the management software does allow it if you create the aggregator first and the VLANs
afterwards. The performance of an aggregate trunk in an aggregator with tagged ports may
be unpredictable. To avoid this issue, you should verify that the ports of an aggregator are not
tagged ports of any VLAN on the switch. (4585)
ˆ
Static port trunks and dynamic LACP port trunks. The management software allows you to
create up to seven static and dynamic port trunks on the switch, though the actual maximum
number is six. The performance of one or more of the trunks may be unpredictable when a
switch has seven port trunks. (4630)
ˆ
Guest VLAN. The Guest VLAN feature of 802.1x port-based network access control is
nonfunctional. An authenticator port assigned a Guest VLAN will remain in the unauthorized
state and will not transition to the VLAN when an unauthorized individual accesses the port.
(4641)
PN 613-000631 Rev A
3
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
Filter-based features. The following filter-based features are not fully supported on the
AT-9424Ts and AT-9424Ts/XP switches: Quality of Service, access control lists, denial of
service defenses, IGMP snooping, and MLD snooping. (4199)
ˆ
Switch’s MAC address and IP multicast packets. The switch might stop forwarding network
traffic if it receives an IP multicast packet that has its MAC address as the destination
address and a TCP header in the payload. To resolve this problem, you must reset the unit.
(4722)
ˆ
MAC address-based VLANS. Version 2.0.0 documentation incorrectly states which switches
in the AT-9400 Series support this feature. The feature is supported on the AT-9424Ts,
AT-9424Ts/XP, AT-9448T/SP, and AT-9448Ts/XP switches, but not on the AT-9408LC/SP,
AT-9424T/GB, and AT-9424T/SP switches.
Resolved Issues
ˆ
Remote management session through an 802.1x authenticator port. It was not always
possible to remotely manage a switch through an authenticator port set to the 802.1x
authentication method and the multiple mode. This issue has been resolved. (4557)
ˆ
RIP and the spanning tree protocol. The switch, when running both RIP and a spanning tree
protocol (STP, RSTP, or MSTP), did not always immediately update the ARP table when
there was a change to the spanning tree topology. This caused the switch to discard some IP
packets. This issue has been resolved. (4168)
Changes to Internet Protocol Version 4 (IPv4) Routing for Version 2.1.0
This section discusses the changes to the IPv4 routing feature in version 2.1.0 of the AT-S63
management software: The new features and changes are:
ˆ
Multiple Routes with ECMP
ˆ
Variable Length Subnet Masks
ˆ
Multiple default routes
ˆ
Interface Names
Multiple Routes with ECMP
In AT-S63 version 2.0.0, the IPv4 routing table of the switch could store only one static route or
dynamic RIP route to a specific remote destination and would not add a new route if there was
already an existing entry in the table to the same destination. Version 2.1.0 adds Equal Cost
Multi-path (ECMP), which enables the routing table to store up to 32 routes to the same remote
destination. Up to eight of the routes can be active at the same time. Multiple routes to the same
remote destination can be all static, RIP, or a combination of the two.
When the routing table contains eight or less routes to the same destination, all of the routes can
be active and available to route packets. The distribution of the traffic between the active routes
is controlled through a hash that combines the packet source and destination IP addresses to
select a route for packets from a source node. The traffic from a source destined for a remote
destination is assigned to a specific route in the table and all traffic from the source to the remote
destination is forwarded using that route. The assignment of a source to a route does not change
unless the path is lost (.e.g., the state of an interface changes from up to down), in which case
the traffic which had been using the route is redirected to one of the remaining routes.
PN 613-000631 Rev A
4
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
When there are more than eight routes in the table to the same destination, the active routes are
selected by their preference value, metric value, and age, in that order. The routes with the eight
lowest preference values are selected as the active routes. Where routes have the same
preference value, selection is based on the lowest metric values. Otherwise, the selections are
based on when the routes were added to the routing table, with older routes given preference
over newer routes.
Routes not selected as active routes are placed in a standby mode.
The selection of the active destination routes by the switch is dynamic and can change as routes
are added and deleted from the routing table, and when they change status. For instance, if a
new static or RIP route is added to the routing table when there are already eight active routes to
the same destination, the new route will replace an existing active route if it has a lower
preference value.
An interface must be physically up with at least one active port in the VLAN for its routes to be
considered as available for use. If an interface is down, meaning there are no active ports in the
VLAN, the routes of the interface are considered inactive and are not assigned any traffic. For
example, if there are eight routes to the same destination, but two of the routes reside in an
interface that is down, those routes are not used, leaving six available routes.
The ECMP feature can be enabled and disabled on the switch. The operating status of ECMP
does not affect the switch’s ability to store multiple routes to the same destination in its routing
table. Rather, it controls how many of the available routes the switch can use to route packets to
the same remote destination. When ECMP is enabled, the default setting, the switch can use
multiple routes to route packets to a remote destination, as explained above. When ECMP is
disabled, the switch uses only one route, selected by preference value, metric, or age, to route
packets to a remote destination, even when there are multiple routes to the destination in the
table.
To determine the status of a static or RIP route, use the FDB parameter of the SHOW IP ROUTE
command, as explained later in these software release notes.
A local subnet or directly connected network of a switch is typically represented just once in the
routing table by its routing interface. However, in some situations a local subnet might have
several routes to it if it is also remotely reachable through other routing interfaces on the switch
via other routers. One of the routes would be the subnet’s routing interface and the others could
be RIP and static routes. Here, even if ECMP is enabled, the switch uses only the routing
interface to route packets to the local subnet, because the preferred route to a local subnet is
always the routing interface. Any RIP or static routes to the local subnet are held in the standby
mode for fail-over protection and are only used when the status of the routing interface to the
local subnet is down.
Several of the IPv4 routing commands have been changed to accommodate the new features
described above. The changes are described here:
ENABLE IP ROUTE MULTIPATH
DISABLE IP ROUTE MULTIPATH
These two new commands enable and disable the ECMP feature on the switch. When ECMP is
enabled, the switch can route packets over multiple paths to the same remote destination. When
disabled, the switch routes packets to a remote destination using only one path, selected by
preference value, metric value, or age, even if the routing table contains multiple paths to a same
destination. The commands do not have any options. The default setting for ECMP is enabled.
PN 613-000631 Rev A
5
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
The following example enables ECMP on the switch:
enable ip route multipath
ADD IP ROUTE Command
SET IP ROUTE Command
These commands, used to create and modify static routes, have the new parameter
PREFERENCE to assign a preference value to a route. As explained previously, when ECMP is
enabled on the switch, the preference value is used to select the active routes when there are
more than eight static or dynamic routes in the routing table to the same remote destination.
When ECMP is disabled, the preference value is used to select the one active route to a remote
destination.
The range for the PREFERENCE parameter is 0 to 65535. The lower the value, the higher the
preference. The default value for a static route is 60.
The following example illustrates the PREFERENCE parameter. It creates a new static route with
the ADD IP ROUTE command to the remote subnet 149.22.22.0 with the subnet mask
255.255.255.0 and a preference value of 7. The next hop for the route is 149.44.44.4:
add ip route=149.22.22.0 nexthop=149.44.44.4 mask=255.255.255.0
preference=7
DELETE IP ROUTE Command
Previously, this command could only delete static routes and the default route. In the latest
version of the management software it can also delete dynamic RIP routes.
An additional change to this command relates to the NEXTHOP parameter. This parameter,
which was optional, is now required. The following example deletes the static route to the
149.125.55.0 remote destination with the subnet mask of 255.255.255.0 and a next hop of
149.125.66.12
delete ip route=149.125.55.0 mask=255.255.255.0 nexthop=149.125.66.12
This example deletes a default route that has the IP address 149.44.44.44 as its next hop:
delete ip route=0.0.0.0 nexthop=149.44.644.44
DELETE IP ARP
Previously, you could use this command to delete static ARP entries from the ARP table, but not
dynamic entries. The command can now delete both static and dynamic entries.
SET IP ARP TIMEOUT Command
The range and default values for the ARP cache timeout value have been changed to 150 to
260000 for the range and 600 for the default value.
SHOW IP ROUTE Command
This command has two changes. The command, when entered without any parameters, now
includes the preference value for the routes in the routing table. Refer to the AT-S63
Management Software Command Line Interface User’s Guide for a description of the information
displayed by this command.
PN 613-000631 Rev A
6
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
The second change is the addition of the new parameter FDB. Here is an example of the
information displayed by this parameter:
IP FDB
------------------------------------------------------------Destination
Mask
NextHop
Interface
Installed
Protocol
RipMetric
Preference
------------------------------------------------------------149.222.66.0
255.255.255.0
149.111.22.11
VLAN2-0
Yes
Static
1
60
149.222.66.0
255.255.255.0
149.111.22.22
VLAN8-0
Yes
Static
1
60
149.222.66.0
255.255.255.0
149.111.55.17
VLAN8-0
Yes
Static
1
60
149.125.10.0
255.255.255.0
149.111.22.11
VLAN2-0
Yes
Static
1
60
The FDB parameter displays much of the same information as when the command is entered
without any parameters, with the difference being the addition of the Installed variable. This
variable displays the status of the static, RIP, and default routes. (The FDB parameter does not
display interface routes.) You can use the variable to determine which static and RIP routes are
actively being used by the switch. A route with an Installed status of Yes has been installed by
the switch in its routing hardware and is ready for use or is already being used to route packets.
A route must meet both of the following conditions to have a status of Yes:
ˆ
The interface with the next hop of the route is up (i.e., there is at least one active port in the
VLAN)
ˆ
There is a static or dynamic ARP entry for the next hop in the routing table.
A route with a status of No has not been installed by the switch in its routing hardware and is not
currently being used. Any one of the following conditions can cause a route to have this status:
ˆ
The interface for the next hop of the route is down (i.e., there are no active ports in the
VLAN).
ˆ
The ARP table does not contain a static or dynamic entry for the next hop.
ˆ
There are already eight active routes to the same remote destination in the routing table and
the route has been placed in the standby mode in the routing table.
Variable Length Subnet Masks
In the previous version of the management software, the value for a byte in a subnet mask for a
routing interface or a static or dynamic route was restricted to either 0 or 255. This limited the
choices for a subnet mask to 255.0.0.0, 255.255.0.0, and 255.255.255.0. A subnet mask can
now be of variable length, so long as the “1”s in the masks are consecutive (e.g., 128, 192, 224,
etc.).
The following example adds a new routing interface with the ADD IP INTERFACE command.
The interface is assigned the IP address 149.222.66.12 and a subnet mask of 255.255.255.128.
The interface is assigned to the VLAN with the VID of 5 and given the interface number 0.:
add ip interface=vlan5-0 ipaddress=149.222.66.12
netmask=255.255.255.128
PN 613-000631 Rev A
7
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
Multiple Default Routes
A default route is used by the switch when it cannot find a route in its routing table for a packet
that needs to be forwarded to a remote destination. In version 2.0.0 of the switch’s management
software, a switch could have only one default route. It had to be a static route and it was not
propagated by RIP to other routers.
The latest version of the management software now supports multiple default routes. The routes
can be static or dynamic and are propagated by RIP to other routers should the switch be
running that routing protocol.
Multiple default routes are handled by a switch in exactly the same manner as it does multiple
routes to other remote destinations. There can be up to 32 default routes and up to eight routes
can be active at a time. It uses ECMP to distribute the traffic over the routes using a hash that
combines the source and destination addresses. When there are more than eight default routes,
the active routes are selected by preference value, metric, and age, as explained previously.
After traffic from a source to a particular destination is assigned a default route, the assignment is
changed only if there is a change to the status of the route, such as if is replaced by a route with
a lower preference value.
Routing Interface Names
You can now specify an interface name two ways in an IPv4 command. Previously, you
designated an interface name by entering “VLAN” followed by the ID (VID) number of the VLAN
and an interface number (e.g., VLAN5-0). You can now use the actual VLAN name, preceded by
a dash, rather than the VID, (e.g., VLAN-Production-0).
The following examples illustrate the two methods for specifying an interface name. The first
creates a new routing interface with the ADD IP INTERFACE command by specifying the ID of
the VLAN, which in the example is 28. The interface is assigned an interface number of 0, an IP
address of 149.44.22.22, and a subnet mask of 255.255.255.224:
add ip interface=vlan28-0 ipaddress=149.44.22.22 mask=255.255.255.224
This command is identical to the previous command, except the VLAN is identified by its name,
Sales, instead of its VID:
add ip interface=vlan-Sales-0 ipaddress=149.44.22.22
mask=255.255.255.224
PN 613-000631 Rev A
8
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
Operational Notes
ˆ
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)
ˆ
Enhanced stacking and slave switches. The AT-S63 Version 2.0.0 Management Software
User Guides incorrectly state that slave switches in an enhanced stack do not need a routing
interface on the common VLAN that interconnects them with the master switch. Actually, a
routing interface is required in the common VLAN of a slave switch, but it does not have to be
designated as the local interface, except on the master switch. The only exception to this rule
is if you use the Default_VLAN (VID 1) as the common VLAN, in which case the common
VLAN on a slave switch does not need a routing interface. (4517)
ˆ
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 its 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
the Fault LED on the front panel of the switch to go off after you save a configuration change
and before you save another configuration change. If you are in a different location from the
switch and cannot view the Fault LED, you should wait 30 to 45 seconds between your save
commands. (2683)
ˆ
Multiple VLAN modes and IPv4 packet routing. The 802.1Q-compliant and non-802.1Qcompliant 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)
PN 613-000631 Rev A
9
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
Switch to switch upload of a configuration file. The AT-S63 Management Software User
Guides state that the configuration file on a master switch retains its routing interface
commands when uploaded to a slave switch. This is incorrect when the file is the master
switch’s active configuration file. All routing interface commands are removed from the
master switch’s active configuration file when it is uploaded to a slave switch to prevent an IP
address conflict on the units. However, the routing interface definitions in the file are retained
when you upload any other configuration file from a master switch to a slave switch. (4272)
ˆ
Telnet management session. Changing the VLAN mode of a switch (e.g., from the userconfigured 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 slow if you have more than one instance of the AtiStkSwVlanConfigEntry MIB table
open at a time. (2231)
ˆ
Compact flash card. The removal of 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)
ˆ
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)
PN 613-000631 Rev A
10
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
GVRP compatibility. There may be some compatibility issues with GVRP and other switches.
To work around this situation, 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 configuring multiple ports 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 are being transferred on 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 if it is receiving a signal,
even if the port 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’s NotePad to edit or view a configuration file. Some
versions of NotePad may add formatting codes to the file. Use WordPad instead or some
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. A port, when removed from a port trunk, retains its settings as a member of the
trunk. The parameter settings (e.g., speed and duplex mode) are not returned to the default
values. (2144)
PN 613-000631 Rev A
11
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
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. The switch, when configured for IGMP, will not register tagged IGMP queries in the
IGMP routers list if ingress filtering is disabled. (1493)
ˆ
SFP modules and the AT-9408LC/SP switch. Be sure to 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.
Features History
Version 2.0.0 of the AT-S63 and AT-S63 NE management software introduced the following new
features:
ˆ
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. For background information, refer to Chapter 32, “Internet Protocol Version
4 Packet Routing,” in the latest version of the AT-S63 Management Software Command Line
Interface User’s Guide.
ˆ
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,
activated if the ambient temperature exceeds 60° Celsius for five minutes, sends another
SNMP trap, logs an error event message, and activates the Fault LED on the front panel.
Version 1.3.0 introduced the following new features:
ˆ
Added the following new features to 802.1x port-based network access control:
— Guest VLANs
— VLAN Assignment and Secure VLAN features for supporting dynamic VLAN assignments
with supplicant accounts.
— MAC address-based authentication as an alternative to 802.1x username and password
authentication.
PN 613-000631 Rev A
12
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
Simplified the menu interface for managing the access control entries in the Management
ACL.
Version 1.2.0 introduced the following new features:
ˆ
MLD snooping for MLDv1 and MLDv2.
ˆ
802.1x port-based network access control supports up to 20 supplicants simultaneously on
an authenticator port.
ˆ
Quality of Service has the following new actions:
— Set Type of Service (ToS)
— Move Type of Service to 802.1p Priority
— Move 802.1p Priority to Type of Service
— Send to Mirror Port
ˆ
The command line interface has new command parameters for displaying and deleting
specific types of MAC addresses from the MAC address table.
Version 1.1.0 introduced the following new features:
ˆ
LACP (802.3ad)
ˆ
Policy-based QoS (Classifiers, Flow Groups, Traffic Classes, and Policies)
ˆ
Flash memory operations
ˆ
Access Control Lists (ACLs)
ˆ
Syslog support
ˆ
Password reset
ˆ
Redundant power supply information
ˆ
IGMP v3 Snooping
ˆ
New web browser interface procedures
Version 1.0.0 supported the following features:
ˆ
Auto-Negotiation (IEEE 803.3u-compliant) for speed and duplex mode
ˆ
Auto and manual MDI/MDI-X
ˆ
Flow control (IEEE 802.3x and 802.3z-compliant)
ˆ
Head of line blocking prevention
ˆ
Unicast, multicast, and broadcast rate control
ˆ
Port mirroring
ˆ
Port trunking (IEEE 802.3ad) (static link aggregation, non LACP)
ˆ
Port security
ˆ
Port statistics (RMON)
ˆ
1000 static MAC addresses, 16K dynamic MAC addresses, 256 static multicast addresses,
255 dynamic MAC addresses (snooping)
ˆ
Spanning Tree Protocol (IEEE 802.1D)
ˆ
Rapid Spanning Tree Protocol (IEEE 802.1w)
ˆ
Multiple Spanning Tree Protocol (IEEE 802.1s)
ˆ
Virtual LANs (IEEE 802.1Q)
PN 613-000631 Rev A
13
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
ˆ
Protected ports VLANs
ˆ
Ingress filtering
ˆ
GARP VLAN Registration Protocol (GVRP)-based dynamic VLANs
ˆ
Secure Sockets Layer (SSL) Protocol (not included in AT-S63 NE)
ˆ
Secure Shell (SSH) Protocol (not included in AT-S63 NE)
ˆ
Public Key Infrastructure (PKI) Certificates (not included in AT-S63 NE)
ˆ
Static and dynamic system time (SNTP client)
ˆ
Management VLAN
ˆ
Multiple VLAN modes
ˆ
Event log
ˆ
Enhanced stacking (for management)
ˆ
IGMP Snooping (RFC 2236)
ˆ
Class of Service (IEEE 802.1p-compliant)
ˆ
Queuing - map 802.1p to CoS queue to prioritize traffic at egress
ˆ
Strict priority and weighted round robin priority scheduling
ˆ
RRP Snooping
ˆ
File system
ˆ
SNMPv1, SNMPv2c and SNMPv3 management
ˆ
CLI-based configuration file
ˆ
Denial of Service detection
ˆ
802.1x Port-based Network Access Control
ˆ
RADIUS accounting
ˆ
Menus, CLI, web, and SNMP interfaces
ˆ
Password protected management access
ˆ
Management access control list
ˆ
Local authentication
ˆ
RADIUS and TACACS+ authentication protocols
ˆ
Xmodem and TFTP downloads and uploads, HTTP and enhanced stacking
ˆ
Static IP configuration
ˆ
BOOTP and DHCP
ˆ
Fan and temperature information
ˆ
CPU, Flash, and RAM information
ˆ
Power supply, redundant power supply, and transceiver information
PN 613-000631 Rev A
14
Allied Telesis, Inc.
AT-S63 Version 2.1.0 Software Release Notes
Contacting Allied Telesis
This section provides Allied Telesis contact information for technical support as well as sales or
corporate information.
Online Support
You can request technical support online by accessing the Allied Telesis Knowledge Base at
www.alliedtelesis.com/kb. You can use the Knowledge Base to submit questions to our
technical support staff and review answers to previously asked questions.
Email and Telephone Support
For Technical Support via email or telephone, refer to the Support & Services section of the
Allied Telesis web site: www.alliedtelesis.com.
Returning Products
Products for return or repair must first be assigned a return materials authorization (RMA)
number. A product sent to Allied Telesis without an RMA number will be returned to the sender at
the sender’s expense.
To obtain an RMA number, contact the Allied Telesis Technical Support group through our web
site: www.alliedtelesis.com.
For Sales or Corporate Information
You can contact Allied Telesis for sales or corporate information on four web site:
www.alliedtelesis.com. To find the contact information for your country, select
Contact Us -> Worldwide Contacts.
Obtaining Management Software Updates
New releases of management software for our managed products are available from either of the
following Internet sites:
ˆ
Allied Telesis web site: www.alliedtelesis.com
ˆ
Allied Telesis FTP server: ftp://ftp.alliedtelesis.com
You must have FTP client software to download new software from the Allied Telesis FTP server
from your workstation’s command prompt and you must log in to the server. The user name is
“anonymous” and your email address is the password.
PN 613-000631 Rev A
15
Allied Telesis, Inc.