
  | 
  | 
  | 
  | 
  | 
  | 
  | Features in   | 
  | 
  | 
  | 22  | ||
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
CR  | Module | Level  | Description  | AR44x / AR450  | AR7x5  | AR750S  | Rapier i  | ||||||
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
CR00012413  | Logging | 3  | When a user creates permanent log filters, the existing default filter is moved to  | -  | Y  | -  | Y  | Y  | -  | Y  | Y  | Y  | Y  | 
  | 
  | 
  | the bottom of the list of filters, instead of being deleted. This behaviour is correct.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | However, output of the command show config dyn=log previously included  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | commands to delete the default filter then add it back in, which was confusing.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | This issue has been resolved. The output of the command show config dyn=log  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | now only includes the default filter if the user has specified the default filter in a  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | command. To see all existing filters, use the command show log  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | output=permanent full. | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
CR00012427  | Logging  | 3  | If a user modified the permanent log by destroying it and creating a new one,  | -  | Y  | -  | Y  | Y  | -  | Y  | Y  | Y  | Y  | 
  | 
  | 
  | and then saved the configuration with the command create config, the  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | resulting configuration file included the command destroy log  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | output=permanent. Therefore when the router or switch restarted it destroyed  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | the log and all entries.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | This issue has been resolved. The command create config now writes the  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | command set log output=permanent to the configuration file instead of the  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | destroy and create commands. | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
CR00012468 | OSPF | 3  | An OSPF router or switch could show large numbers of entries in its  | Y  | Y  | Y  | Y  | Y  | Y  | Y  | Y  | Y  | Y  | 
  | 
  | 
  | retransmission lists to certain neighbours under certain conditions (for example,  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | in a congested Frame Relay network). In some cases, the number of items in the  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | list was larger than the number of LSAs in the database.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | This issue has been resolved.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | Also, a new NRL debugging option has been added to OSPF, to show additions  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | to and deletions from the neighbour retransmission list. To enable NRL  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | debugging, use the command:  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
enable ospf debug=nrl
Note that this option may generate large amounts of debugging output on a large OSPF network. Use it with care.
To disable NRL debugging, use the command:
disable ospf debug=nrl
Version