|
|
|
|
|
|
| Features in |
|
|
| 40 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015569 | Firewall | 2 | When only NAT was enabled on the firewall, during some TCP connections in | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| which either end of the connection sends FIN (finished) messages immediately |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| after sending some data and the other end ACKs (acknowledges) the data and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the FIN message consecutively, the firewall sometimes incorrectly interpreted the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| first ACK message (intended for the data) as belonging to the FIN message and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| prematurely shut the connection down. This could prevent the firewall from |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| opening up new connections using the same port numbers. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015592 | BGP, | 2 | When BGP learned new best routes for a particular destination, it did not always | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
| IP Gateway |
| clear any active IP flows that used the previous best route. Therefore, the router |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| or switch continued to forward traffic |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. Now, when BGP inserts new routes into the IP route |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| table, it deletes all active route flows, so any active flows change to using the new |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| route. The time taken to delete a full table of IP flows has also been greatly |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| reduced. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015736 | Switch | 2 | Sometimes IP routed traffic would be sent out the correct port, but with the | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| destination MAC of another device on the network. This issue was most likely to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| occur in configurations that use |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| end devices. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015822 | Switch | 2 | When the command enable ip macdisparity was used, and a static ARP entry | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| was configured with an L2 multicast MAC address, the switch should have |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| broadcast traffic to that multicast MAC address out all ports in the VLAN. This |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| was not happening. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015861 | VRRP | 2 | After manually disabling the master VRRP router, sometimes a backup router that | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| should assume master status would not do so, and VRRP would cease to function |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| properly. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version