|
|
|
|
|
|
|
| Features in |
|
|
| 29 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013832 | EPSR, SNMP | 3 | When a user destroyed an EPSR domain, SNMP Requests returned | - | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| information about the domain even though it no longer existed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013920 | Ping, | 3 | If a user attempted to perform a traceroute without specifying the address | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
| Traceroute |
| to trace (either in the trace or set trace commands), the router or switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| attempted to trace 0.0.0.0. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The router or switch now displays an error |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| message. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014103 | VRRP, GUI | 3 | The VRRP priority could not be modified through the | Y | Y | Y | Y |
| - | Y | Y |
| Y | - | Y | Y |
|
|
| option was there but did nothing. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014137 | PPP | 3 | A PPPoE Access Concentrator service that had been added by using the | Y | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| acinterface parameter to specify a VLAN (or by using the deprecated vlan |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| parameter) could be deleted without specifying the acinterface parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (or the deprecated vlan parameter). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014159 |
| 3 | RSTP (correctly) only uses the top 4 of the available 16 bits for the bridge | - | - | - | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| priority. If a user enters a value that is not a multiple of 4096, the switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| rounds the value down. Previously, the switch did not inform users when it |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| rounded the value. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The switch now displays an info message |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| when it rounds the bridge priority. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Note that this only happens for RSTP. STP uses all 16 bits for the bridge |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| priority. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014203 | OSPF | 3 | When OSPF was disabled and a BGP redistribution definition existed, then | Y | Y | Y | Y |
| Y | Y | – |
| – | Y | Y | Y |
|
|
| the obsolete command set ospf bgplimit=limit did not update the limit |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| in the BGP redistribution definition. This meant that the limit was incorrect |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| when OSPF was enabled again. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version