HP VAN SDN Controller Administrator Guide v3

4. Click on the Value field and type in the queue size you want.
Figure 22 Entering the Queue Size
5. Click Apply in the lower right corner of the window.
NOTE: In a controller team environment, changing the log.queue.size on any controller propagates
to all active controllers in the team.
2.7.2 Log Message Levels
Log message levels include the following:
• ERROR
• WARN
• INFO
• DEBUG
• TRACE
In the default configuration, the ERROR, WARN, and INFO levels are recorded in the Support
Logs. DEBUG and TRACE are verbose logging that are used in troubleshooting situations that may
involve support engineering. The logging level for a given component that is writing to the support
log can be dynamically changed using the Virgo Administrator console. For example, DEBUG
level logging can be enabled for just the Node Manager (nodemgr.impl.NodeManager)
Configuration Component.
2.7.3 Multiple Support Logs
The controller allows up to five support logs; one active and four in storage. When the current log
reaches 10MB, it rolls over to storage and the controller starts a new log. When all Support Log
space is full, the oldest log file is purged to make room for continued logging operation. Support
logs are maintained in the controller var/log/sdn/virgo/logs directory.
2.7.4 Export the Support Logs
The "Export" operation moves the set of log files from the controller (as a compressed file) to the
local system running the browser (that is, to the sdn-all-logs.zip file in the directory in which the
controller is configured to store downloads). In Ubuntu installations, this is usually the Downloads
directory. In a controller team environment, the Export operation gathers the set of support log file
data from all active controllers in the team, and stores them as a single compressed archive.
2.7 Support Logs 33