|
|
|
|
|
|
| Features in |
|
|
| 78 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013463 | Ping | 4 | Previously, if you used the ? or Tab keys to obtain help about the timeout | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| parameter for the ping command, the resulting help said that the maximum |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| timeout was 65535. However, the correct maximum is 60 seconds. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The “?” help now displays the correct range of |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| values. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013589 | Install | 4 | When a router or switch was using a trial licence for release software and the trial | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| period elapsed, the router or switch rebooted without indicating the reason for |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The following error messages now explain why the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| router or switch is rebooting: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ERROR: There are no valid licences available for the current software release. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The device will now reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ERROR: The trial licence for the current software release has expired. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The device will now reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013640 | NTP | 4 | Output of the command show ntp displays a “Host Address” field. This is the | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| address of the interface from which the router or switch sends NTP packets. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Previously, if the IP address changed, the “Host Address” field did not change, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| even though NTP used the new address. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014106 | Core | 4 | If the router or switch runs a configuration file on | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| command set summertime before the command enable summertime, a log |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| message on |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| summertime is correctly applied to the router or switch. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Previously, if you configured summertime then saved the configuration by using |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the command create config, set summertime came before enable |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| summertime in the resulting configuration file. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. When you save the configuration, enable |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| summertime now comes before set summertime in the resulting configuration |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| file, so the log message is not produced. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version