|
|
|
|
|
|
| Features in |
|
|
| 53 | ||||
Level 4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S |
| Rapier i | AT8800- |
| x900 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00000396 | IGMP | 4 | If a static IGMP port went link down, it was not shown in the “Static Ports” list | Y | Y | Y |
| Y | Y | Y |
| Y | Y- | Y | Y |
|
| in the output of the show ip igmp command. This was only a display issue. |
|
|
|
|
|
|
|
|
| 48 |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011560 | Install | 4 | It is no longer possible to specify a compact flash file as the boot configuration | - | - | Y |
| - | - | - |
| - | Y | Y | Y |
|
|
| file. If the command set config=cf:filename.cfg is entered, the router or switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| does not change the current boot configuration file and instead displays the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| following error message: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Cannot specify configuration file in Compact Flash |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00013976 | IGMP | 4 | The list of parameters output by the “?” help for show ip igmp ? incorrectly | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| included “IGMP”. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00015543 | Bridge | 4 | In output of the command show bridge spanning, the bridge identifier was | Y | Y | Y |
| - | - | - |
| - | - | - | - |
|
|
| correctly displayed as a hexadecimal number, but it was not obvious that the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| number was hexadecimal. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The output now has 0x in front of the hexadecimal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| number, to make it clear that it is hexadecimal. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016126 | QoS, Switch | 4 | When a QoS policy was associated with a port that was set to a speed less than | - | - | - |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| the maximum speed of the port, a warning message would be displayed on the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| console session and in the log when the port state changed to UP. This message |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| stated that the QoS policy operation may be affected by the speed setting of the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| port. Having this message displayed on the console was considered unnecessary |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| and potentially confusing. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved.The message is now only displayed in the log. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016451 | IP Gateway | 4 | When a second metric was displayed in the output of the command show ip | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| route (because of OSPF, for example) this metric was truncated to 2 characters. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The output now displays both metrics in a field up |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| to 10 characters long. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version