|
|
|
|
|
|
|
| Features in |
|
|
| 28 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013494 | IP Gateway | 3 | Once a default local IP address had been set, it could not be deleted. This | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| was because the default interface does not have an interface number, but |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| to delete a local interface, the user must specify the interface’s number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved, by adding an option called default to the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| delete ip local command. To delete the default local interface’s address, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| use the command: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| delete ip local=default |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Note that this resets the interface, including removing its IP address, but |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| does not remove the interface itself. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013543 | DHCP | 3 | If a user attempted to add a policy option to a DHCP policy by using the set | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| command instead of the add command, then the resulting error message |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| did not clearly indicate the cause of the error. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| For example, entering the command: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| set dhcp policy=test arptimeout=234 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| resulted in the error message: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Error (3070061): ARPTIMEOUT not found. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The error message now reads: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Error (3070279): Option ARPTIMEOUT was not found in policy test or |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| was not added using the ADD DHCP POLICY command. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013635 | Ping, | 3 | In the set trace command, it was possible to specify a minimum TTL value | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
| Traceroute |
| that was higher than the maximum TTL value. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The minttl and maxttl parameter are now |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| checked to ensure that the value of minttl is less than or equal to the value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| of maxttl. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013637 | Ping, | 3 | If the value specified for the minimum | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
| Traceroute |
| the traceroute command exceeded the value set for the maximum time- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| the trace rather than generate an error message. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version