3.9.2 Licenses screen details
Screen component | Description |
|
|
Refresh | Updates the screen with the latest license information. |
|
|
Add | Adds and activates the specified license key on this controller. |
|
|
Deactivate | Deactivates the selected license. |
|
|
Install ID | Contains the installation identifier for this controller. |
|
|
Serial# |
|
|
|
Product |
|
|
|
Licensed For |
|
|
|
Qty |
|
|
|
Type |
|
|
|
Status |
|
|
|
Expire By |
|
|
|
Uninstall Key |
|
|
|
3.9.3 Installing, activating, uninstalling, or transferring licenses
For information about installing, activating, uninstalling, and transferring licenses, see “License Registration and Activation” (page 52).
3.10 Support logs screen
3.10.1 About support logs
The support logs maintain an internal record of events of interest from the operations of an active SDN controller. This information is the type of data a support engineer would request when troubleshooting an SDN installation.
Support logs and controller teams
In a controller team environment:
•Each controller maintains its own support logs.
•Changing the 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.
Multiple support logs
The controller allows up to five support logs; one active and four in storage:
•When the current log reaches 10MB, the controller copies the log to storage and starts a new log.
•When the space allocated for all support logs is full, the controller purges the oldest log file to make room for continued logging operation.
•Support logs are stored in the controller /var/log/sdn/virgo/logs directory.
•Support logs can be exported to a file (see “Exporting the support logs ” (page 36))
34 Navigating the controller user interface