|
|
|
|
|
|
| Features in |
|
|
| 20 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44xS/ AR450S | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011598 | PIM, PIM6 | 3 | Previously the SPTbit on a PIM device was not set under the following conditions: | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| ■ when a PIM neighbor was the RP (Rendezvous Point), and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ when the PIM neighbor was not the RPF (Reverse Path Forwarding) neighbor |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| to the Source; that is, it did not have a direct connection to the Source traffic |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| stream. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| In this situation, the SPTbit remained unset. This resulted in the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| device continually sending register messages awaiting a register STOP. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| register messages. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011710 | Core | 3 | When the router sent a RADIUS accounting STOP packet, the packet’s Acct- | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| for. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012128 | IP Gateway | 3 | When the router or switch recalculated the IP checksum after decrementing the | Y | - | Y |
| Y | Y | Y |
| Y | - | - | - |
|
|
| TTL value, it was possible for the checksum to be 0xFFFF. This conformed to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RFC 1141 but not to RFC 1624. For switches, note that this issue did not affect |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| IP hardware routing, only packets routed by the CPU. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. Checksums are now calculated in accordance with |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RFC 1624. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012194 | IPv6 | 3 | When a user changed the settings for IPv6 Neighbour Discovery advertisement of | Y | - | Y |
| Y | Y | - |
| - | - | - | - |
CR00002547 |
|
| the prefix of an existing IPv6 interface route, then the changes were not saved in |
|
|
|
|
|
|
|
|
|
|
|
|
|
| the configuration file or output resulting from the commands create config and |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| show config dynamic. If the router or switch rebooted, the changes were lost. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue only occurred if the existing interface route and the modified prefix had |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the same prefixlength. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version