|
|
|
|
|
|
| Features in |
|
|
| 44 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016489 | BGP | 2 | When BGP capability matching was changed to strict, that setting was not | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| displayed in output of the command show config dyn or saved in the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| configuration file produced by the command create config. When the router or |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| switch ran the configuration file on |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| reverted to the default of loose. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016526 | PPP | 2 | An interoperability issue with a malfunctioning PPP peer meant that the peer | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| could ACK an IP address of 0.0.0.0 when it was required to offer a valid public IP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| address. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The router or switch now refuses to accept this |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| incorrect negotiation and instead resends a configure request for an IP address. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016576 | IPv6 | 2 | The router or switch sometimes rebooted after receiving an IPv6 router | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| advertisement, or after the command set ipv6 interface was entered. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016621 | Switch | 2 | On | - | - | - |
| Y | Y | Y |
| Y | - | - | - |
|
|
| always behave correctly. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016698 | BGP | 2 | The following issues occurred when using BGP aggregate specifications (created | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| using the command add bgp aggregate): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ When an aggregate route was originated from routes learnt from external |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| peers, and then all of the contributing child routes were withdrawn by the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| external peers, the aggregate route was not removed from the routing table. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| It could still be advertised to external peers. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ When a network or import entry (add bgp network or add bgp import) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| resulted in a route entry that had the same prefix length as the aggregate |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| specification, then BGP (correctly) originated the aggregate route. However, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| deleting the network or import definition did not remove the aggregate route |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| from the routing table. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| These issues have been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version