|
|
|
|
|
|
|
| Features in |
|
|
| 30 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014304 | LLDP | 3 | The help displayed for the LLDP port parameter (in such commands as | Y | - | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| show lldp port=?) incorrectly indicated that the port parameter is a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| “string 1 to 255 characters long”. The port parameter is instead an |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ethernet switch port number or a range of numbers. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The help is now correct. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014330 | Ping | 3 | The maximum value for the delay parameter of the ping command was | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| too long. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved by changing the range for the delay from |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| in one week. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014879 | Switching, | 3 | Previously, an incorrect value was returned for the port number when | - | - | - | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
| RSTP, SNMP |
| responding to an SNMP Request for MIB object dot1dSTPRootPort. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015466 | Core, Install, | 3 | The output of the show cpu command on the | - | - | - | - |
| - | - | Y |
| - | - | - | - |
| PoE |
| relatively high CPU usage when the device was idle. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016183 | File | 3 | If a user attempted to delete a locked file, such as the | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| GUI resource file, the router or switch displayed both an operation error |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| message and an operation successful message. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved by removing the incorrect operation successful |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| message. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016429 | OSPF | 3 | Previously, OSPF logged the same message for two separate errors. These | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| errors were when OSPF rejected a database description message because: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ the neighbour was in a state of “down” or “attempt”, or |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ the MTU received from the neighbour was larger than the receiving |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| system could handle. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. Separate error log messages are now |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| generated for these two errors. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version