|
|
|
|
|
|
| Features in |
|
|
| 7 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44xS/ AR450S | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011994 | IPsec | 1 | When both Software QoS and IPSec were configured on the router or switch, it | Y | - | Y |
| Y | - | - |
| - | - | - | - |
|
|
| sometimes rebooted. This happened if the IPSec SA bundle was suddenly deleted |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| while packets were still queued in Software QoS. For example, this issue was |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| more likely to occur if the expirykbytes parameter of the create ipsec |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| bundlespecification command was configured, and the hard expiry kilobyte |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| limit for an IPSec SA bundle was reached quickly. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012196 | IPv6 | 1 | When RIPng deleted a route from the IPv6 route table, routing for associated IPv6 | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| flows was not updated correctly. This caused data forwarding on those flows to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| use invalid routes. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012461 | IPv6 | 1 | Sometimes the router or switch rebooted when it received Neighbour | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| Advertisements that did not properly conform to RFC 2461. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The router or switch no longer reboots if it receives |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| also displays useful information about the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012571 | IPv6 | 1 | The router or switch sometimes rebooted when running a configuration script | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
CR00013183 |
|
| that included RIPng (RIPv6). |
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012614 | Switch | 1 | When PIM6 was configured on the switch, and it received an IPv6 multicast | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| stream for which it had no downstream interface to forward the stream to, a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| reboot could occur. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue was resolved in a previous software version (as CR00012097) but this |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| version includes an improved resolution. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013025 | DVMRP | 1 | Receiving a DVMRP Graft or Prune message occasionally caused the router or | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| switch to reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version