Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 236)

208 Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Adding additional parameters
Modify exit overflow interval
If a database overflow condition occurs on a router, the router eliminates the condition by removing
entries that originated on the router. The exit overflow interval allows you to set how often a device
checks to see if the overflow condition has been eliminated. The default value is 0. The range is 0 –
86400 seconds (24 hours). If the configured value of the database overflow interval is zero, then
the router never leaves the database overflow condition.
To modify the exit overflow interval to 60 seconds, enter the following command.
Brocade(config-ospf-router)# database-overflow-interval 60
Syntax: [no] database-overflow-interval value
The value can be from 0 – 86400 seconds. The default is 0 seconds.
Specify types of OSPF Syslog messages to log
You can specify which kinds of OSPF-related Syslog messages are logged. By default, the only OSPF
messages that are logged are those indicating possible system errors. If you want other kinds of
OSPF messages to be logged, you can configure the device to log them.
For example, to specify that all OSPF-related Syslog messages be logged, enter the following
commands.
Brocade(config)# router ospf
Brocade(config-ospf-router)# log all
Syntax: [no] log all | adjacency [ dr-only ] | bad_packet [checksum] | database | memory |
retransmit
The log command has the following options:
The all option causes all OSPF-related Syslog messages to be logged. If you later disable this option
with the no log all command, the OSPF logging options return to their default settings.
The adjacency option logs essential OSPF neighbor state changes, especially on error cases. This
option is disabled by default. The dr-only sub-option (added in version 03.3.00) only logs essential
OSPF neighbor state changes where the interface state is designated router (DR).
NOTE
For interfaces where the designated router state is not applicable, such as point-to-point and virtual
links, OSPF neighbor state changes will always be logged irrespective of the setting of the dr-only
sub-option.
NOTE
A limitation with the dr-only sub-option is that when a DR/BDR election is underway, OSPF neighbor
state changes pertaining to non-DR/BDR routers are not logged. Logging resumes once a DR is
elected on that network.
The bad_packet checksum option logs all OSPF packets that have checksum errors. This option is
enabled by default.
The bad_packet option logs all other bad OSPF packets. This option is disabled by default.
The database option logs OSPF LSA-related information. This option is disabled by default.