Allied Telesis AR700 Series - Manual (Page 4)

Features in 275-05 4
Version 275-05
C613-10473-00 REV D
CR00005490 Switch 2 When ports within a trunk went down or came back up again, the switch
sometimes stopped forwarding IP multicast packets.
This issue has been resolved.
- - - - - - - Y Y -
CR00006475 IP Gateway,
PIM
2 When PIM-DM or PIM-SM was forwarding traffic through the CPU at high data
rates and an SG entry was deleted, it was possible for the router or switch to
reboot.
This issue has been resolved.
Y Y Y - - - - Y Y -
CR00007522 IP Gateway 2 The switch’s hardware IP route table occasionally did not contain the most
optimal route to a destination. This meant packets were sometimes sent via sub-
optimal routes. An additional effect was that when multiple equal-cost routes
existed a less than complete set of those routes would be utilised.
This issue has been resolved, so that the switch forwards packets via the best IP
route(s) available.
- - - - - - - Y Y -
CR00008992 IPv6 2 The router or switch sometimes unexpectedly stopped forwarding IPv6 multicast
traffic if the multicast’s upstream path changed. This could occur, for example,
when the path changed because an interface went down. Y Y Y - - - - Y Y -
CR00009201 ARP 2 An ARP timeout caused the removal of the ARP entry, resulting in packet loss until
the entry was re-added.
This issue has been resolved.
Y Y Y - - - - Y Y -
CR00009539 IP Gateway 2 The IP DNS cache feature was not designed to include MX (Mail Exchange) DNS
records. In some circumstances, MX DNS entries were added to the IP DNS cache
and the name of a DNS record was incorrectly associated with the IP address of
the MX entry. This stopped the router or switch from correctly resolving A-record
requests for the affected domain name.
This issue has been resolved by ensuring that MX entries are never added to the
IP DNS cache.
Y Y Y - - - - Y Y -
CR Module Level Description AR400 AR7x5 AR750
S
Rapi
er
i
A
T-
880
0
A
T-
860
0
A
T-
870
0XL
A
T-
894
8
A
T-
990
0
A
T-
980
0