|
|
|
|
|
|
| Features in |
|
|
| 66 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015936 | Switch | 2 | It was not possible to set a | – | – | – |
| – | – | – |
| – | – | Y | – |
|
|
| script that the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved, so the SFP can be set to a fixed speed from the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| configuration script |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Also, it was possible to use the command set swi port=number speed on an |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| empty SFP bay. The command reported that the operation had been successful, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| but an inserted SFP was instead set to its previous or default setting. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. It is no longer possible to set the speed of an empty |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SFP bay. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015949 | IPv6 | 2 | Sometimes, when a router or switch received an IPv6 router advertisement | Y | Y | Y |
| Y | Y | – |
| – | Y | Y | Y |
|
|
| message, it incorrectly created a duplicate of an |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If a user then deleted the IPv6 interface that these two routes belonged to, the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| router or switch could reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015971 | WAN Load | 2 | The following issues occurred with WAN load balancing (WANLB): | Y | Y | Y |
| – | – | – |
| – | – | – | – |
| Balancing |
| ■ when a WANLB resource port became unavailable, existing sessions on the |
|
|
|
|
|
|
|
|
|
|
|
|
CR00015937 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| unavailable resource did not move to a backup resource |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CR00015864 |
|
| ■ if packets were sent over a WANLB session, then that session timed out, and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| then the same packets were sent again, a new session did not establish. This |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| stopped the packets from being sent the second time. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ when WANLB was used with Firewall NAT, the orphan timeout setting of |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| WANLB sessions was not updated correctly. This could mean that WANLB |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| resources appeared to be available when they were not. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| These issues have been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016037 | User | 2 | If the router or switch used RADIUS authentication and all the RADIUS servers | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| were unavailable, then the device correctly checked its user database for a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RADIUS backup user and authenticated that user. However, if that user then |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| logged out, they were unable to log in again until after the RADIUS server Dead |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Time timer had expired. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version