|
|
|
|
|
|
| Features in |
|
|
| 63 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014714 | PIM | 2 | If a PIM interface was set as the BSR candidate interface (by using the command | Y | Y | Y |
| Y | Y | – |
| – | Y | Y | Y |
|
|
| add pim bsrcandidate interface=interface) and that interface went down, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| PIM would select another interface as the BSR candidate interface. The router or |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| switch also set the new interface as the BSR candidate interface in the dynamic |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| configuration. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. PIM only looks for a new interface to use as the BSR |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| candidate address if the user has not specified an interface. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014748 | Reverse Telnet | 2 | Reverse Telnet used to filter out | Y | Y | Y |
| Y | – | – |
| – | – | – | – |
|
|
| perform certain actions on the remote device. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014795 | RIPv6 | 2 | When a user disabled RIPv6 or deleted a RIPv6 interface, the router or switch | Y | Y | Y |
| Y | Y | – |
| – | Y | Y | Y |
|
|
| correctly set the metric of any affected RIPv6 routes to 16, indicating that the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| route was unavailable. However, the router or switch continued to try to use such |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| routes to route packets if no alternative better routes existed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. When a route’s metric is 16, it is no longer used to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| route traffic. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014834 | Switch | 2 | When STP detected a topology change and therefore the switch flushed its ARP | – | – | – |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| table entries, sometimes the switch did not remove entries for |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ports. Therefore, ARP entries for these ports contained incorrect routing |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| information. These incorrect entries were not replaced until after they timed out. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00014925 | IP Gateway | 2 | When the switch had a static route to a destination, and a user added a more | – | – | – |
| Y | Y | Y |
| Y | – | – | – |
|
|
| specific static route to the same destination, then the switch should have |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| removed the less specific route from its hardware switching table, but did not. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This stopped the switch from routing packets to that destination. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version