
AT-S63 Version 4.1.0 Patch 2 Software Release Notes
PN 613-001278 Rev A 9 Allied Telesis, Inc.
Version 4.1.0 Operational Notes
Stacking and IGMP snooping. IGMP snooping on a stack requires that a multicaster be on
the master switch.
Web server. The default setting for the web server on the switch has been changed from
enabled to disabled. To manage the switch with a web browser, 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 and source or destination IP address.
— Protocol and source or destination IP address
This rule applies whether the criteria are in the same classifier or in different classifiers that
are applied to the same access control list or Quality of Service policy.
Protocol (Layer 2) IP criterion - Do not use the IP value in the Protocol (Layer 2) variable of a
classifier to filter IP traffic. The results may be unpredictable. Instead, use the IP source or
the IP destination criterion. The following values can be used to filter large IP address ranges:
ID numbers of ACLs. The ID numbers of permit ACLs have to be less than the ID numbers of
deny ACLs. Otherwise, the results might be unpredictable on ports that have both permit and
deny ACLs. To avoid this issue, start numbering your permit ACLs at ID number 1 and your
deny ACLs at ID number 100.
ID numbers of QoS policies. If you assign two QoS policies to the same port and one of the
policies is filtering on a subset of the IP addresses of the other policy, the ID number of the
subset policy has to be lower than the ID number of the other policy. Otherwise, the results
might be unpredictable.
Port Mirroring. In order for a switch to mirror tagged packets, the VLANs of the packets must
exist on a switch. Packets that contain VIDs of nonexistent VLANs are not mirrored.
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
Value Range
128.0.0.0/1 128.0.0.0 to 255.255.255.255
64.0.0.0/2 64.0.0.0 to 126.255.255.255
32.0.0.0/3 32.0.0.0 to 63.255.255.255
16.0.0.0/4 16.0.0.0 to 31.255.255.255
8.0.0.0/5 8.0.0.0 to 15.255.255.255
4.0.0.0/6 4.0.0.0 to 7.255.255.255
2.0.0.0/7 2.0.0.0 to 3.255.255.255
1.0.0.0/8 0 to 1.255.255.255
Kommentare zu diesen Handbüchern