|
|
|
|
|
|
| Features in |
|
|
| 6 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44x / AR450 | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00008699 | Switch | 2 | Previously, when 300 MAC address filters were added to a port and the port was | - | - | - |
| Y | Y | Y |
| Y | - | - | - |
|
|
| reset, the CPU became 100% utilised. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00008992 | IPv6 | 2 | The router or switch sometimes unexpectedly stopped forwarding IPv6 multicast | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| traffic if the multicast’s upstream path changed. This could occur, for example, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| when the path changed because an interface went down. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00009201 | ARP | 2 | An ARP timeout caused the removal of the ARP entry, resulting in packet loss until | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| the entry was |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00009280 | ATM | 2 | When the router was using IPsec and either IPoEoA or IPoA, and it received traffic | Y | - | - |
| - | - | - |
| - | - | - | - |
|
|
| from a VLAN at a higher rate than it could transmit over the ADSL link, eventually |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the ATM interface would intermittently stop transmitting traffic. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00009283 | Switch | 2 | If a | - | - | - |
| Y | Y | Y |
| Y | - | - | - |
|
|
| the addresses timed out. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00009539 | IP Gateway | 2 | The IP DNS cache feature was not designed to include MX (Mail Exchange) DNS | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| requests for the affected domain name. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved by ensuring that MX entries are never added to the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| IP DNS cache. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00010265 | Switch | 2 | When the ingress and egress port were defined in an Layer 3 filter with an action | - | - | - |
| Y | Y | Y |
| Y | - | - | - |
|
|
| of deny, the filter denied the traffic to be sent out all the egress ports and not |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| just the egress port specified in the filter. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version