|
|
|
|
|
|
| Features in |
|
|
| 45 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016727 | TCP, Telnet | 2 | The speed of the output from the Telnet server has been increased. | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016762 | ISDN | 2 | For AR44xS series routers with system territory set to USA, the ISDN Q.931 SPIDs | Y | - | - |
| - | - | - |
| - | - | - | - |
|
|
| failed to initialize to the ISDN exchange/ISDN USA profile simulator (both manual |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| and auto SPIDs) after a reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This happened because the router did not write *.spd files to Flash memory, so |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the SPID initialization failed on reboot because the SPIDs did not exist. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The *.spd files are now correctly written to Flash |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| memory, which allows SPIDs to initialise after a reboot. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016804 | Bridge | 2 | If an Ethernet packet, including its FCS (Frame Check Sequence), was | Y | Y | Y |
| - | - | - |
| - | - | - | - |
|
|
| encapsulated in PPP and bridged to a VLAN interface, the packet could contain |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| two FCS values. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016855 | Frame Relay | 2 | When the MTU of a Frame Relay logical interface was modified (by using the | Y | Y | Y |
| Y | - | - |
| - | - | - | - |
|
|
| command set |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| settings were displayed in output of the command show config dyn and were |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| saved in the configuration file produced by the command create config. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016856 | Firewall | 2 | When the firewall policy for an interface had a NAT type of ENAPT, the firewall | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| did not correctly translate the destination addresses of incoming packets that |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| matched “allow” rules. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016911 | Classifier | 2 | When a | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| that protocol setting was not 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 resulting configuration file on |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| protocol setting was lost. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version