|
|
|
|
|
|
| Features in |
|
|
| 10 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR750S / AR770S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012846 | ASYN, Log | 2 | The following issues occurred with sending log messages to an asynchronous | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| port: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ The log messages output on an asynchronous port were corrupt. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ When log messages were output to an asynchronous port, that port was |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (correctly) locked. However, the port remained locked after the asynchronous |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| log output definition was destroyed, and after the log output's destination |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| was changed from asynchronous to something else. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ It was possible for a user to change the log output destination to an |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| asynchronous port while the user was logged into the asynchronous port. This |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| resulted in the user losing access to the command line interface. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ It was possible to create a log output definition with an asynchronous port as |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the destination even when another user was logged into that asynchronous |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| port. This resulted in the other user losing access to the command line |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| interface. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ If a user changed the log output destination to an asynchronous port and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| specified invalid parameters in the command, an error message was displayed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| but the new output destination was saved anyway. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ The set command allowed a user to specify an asynchronous port as the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| destination without specifying the asynchronous port number. The number |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| defaulted to asyn0, which may not have been the desired port. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| These issues have been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012855 | Core | 2 | If the switch was rebooted at a time when there was a high level of packet traffic | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| between the switch ports and the switch CPU, then during the reboot process it |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| was possible for RAM test errors to occur. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012868 | ENCO | 2 | Entering the command create enco key=number ip=? caused the router or | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| switch to reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version
