Allied Telesis Patch 1 AT-S63 Release Release - Pagina 6
Blader online of download pdf Release Release voor {categorie_naam} Allied Telesis Patch 1 AT-S63. Allied Telesis Patch 1 AT-S63 14 pagina's. At-9400 series basic layer 3 gigabit ethernet switches at-s63 version 3.1.0 patch 1 software release notes
AT-S63 Version 3.1.0 Patch 1 Software Release Notes
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
PN 613-000915 Rev A
6
Allied Telesis, Inc.