•
When the log file has rolled over four times, the controller purges the oldest log file when it
needs to roll over again. The core controller has at most 5 log files.
•
Support logs can be exported to a file.
In a controller team environment:
•
Each controller maintains its own support logs.
•
Changing the support log queue size on any controller propagates to all active controllers
in the team.
•
The
Export
action gathers the set of support log file data from all active controllers in the
team, and stores the data as a single compressed archive.
See also:
•
“Configuring the support log queue size ” (page 55)
•
“Exporting the support logs ” (page 56)
)
Support logs screen details
Figure 18 Selecting the Support Logs screen
Description
Screen component
Displays a listing of the most recent log messages, as determined by the currently
configured queue size. For example, with a queue size of 100,
Refresh
lists the 100
most recent log messages.
Refresh
Gathers the set of support log file data from the standalone controller or all active
controllers in the team, and stores the data as a single compressed archive.
Export
The severity level for the entry.
Level
The logging levels are hierarchical. Messages are logged with the lowest logging
level and above. The lowest level is TRACE, which results in all messages being
logged for the selected logger when the TRACE logging level is specified. INFO is
the logging level In the default configuration.
54
Using the SDN controller UI