|
|
|
|
|
|
|
| Features in |
|
|
| 22 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00004004 | File | 3 | The show file command did not check whether the specified file system | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| was valid. If an invalid file system type was entered (such as show |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| file=abc:*.*), the router or switch reported that no files found instead of |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| reporting that the file system abc did not exist. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00005048 | GUI | 3 | The following issues occurred with the GUI: | Y | - | Y | - |
| - | - | - |
| - | - | - | - |
|
|
| ■ the menu item and related page title for configuring PPPoE and PPPoA |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| interfaces was incorrectly named “PPP”. This issue has been resolved by |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| changing the names to “PPPoE / PPPoA”. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ the UPnP selection option on the firewall pages did not work. This issue |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Note that if you want to use the GUI to configure a PPP interface over ISDN, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| use the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00005187 | LACP | 3 | If a user attempted to enable LACP on | - | - | - | - |
| - | - | - |
| - | - | - | Y |
|
|
| not support |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| enabled. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The switch now displays an error message |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| instead. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00005894 | Classifier | 3 | Previously, a classifier with protocol=ip matched both IPv4 and IPv6 | Y | Y | Y | Y |
| Y | - | - |
| - | - | - | - |
|
|
| packets when used with software QoS, instead of only matching IPv4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| packets. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00005940 | BGP | 3 | There were several cases in BGP where an error was discovered in an | Y | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| incoming packet, but the incorrect error subcode was reported in the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| accompanying NOTIFICATION message. Also, NOTIFICATION messages did |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| not contain the aberrant data in their data fields, as required by the RFC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| These issues have been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version