Screen component |
| Description |
|
|
|
|
|
|
|
Refresh |
| 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. | ||
|
|
|
|
|
Export |
| 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. | ||
|
|
|
|
|
Level |
| The severity level for the entry. Levels are: | ||
|
|
|
|
|
|
| Value | Description | |
|
|
|
|
|
|
| ERROR | Recorded in support logs |
|
|
|
|
|
|
|
| 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 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 NodeManager configuration component. | ||
|
|
|
|
|
Logger |
|
|
|
|
|
|
|
|
|
Thread |
|
|
|
|
|
|
|
|
|
Message |
|
|
|
|
|
|
|
|
|
Data |
| Detailed information about the log entry. | ||
|
|
|
|
|
Controller ID |
| A hexadecimal number that identifies controller that generated the log entry. When | ||
|
| you use controller teaming, this ID enables you to identify which controller in the team | ||
|
| generated the alert. | ||
|
|
|
|
|
The default queue size is 100 lines. To configure a different queue size, change the value for the max.display.rows key of the LogManager component.
1.From the Configurations screen, under Component, select the com.hp.sdn.adm.log.impl.LogManager component.
2.Click Modify.
The Modify Configuration dialog box appears.
3.Change the value for the max.display.rows key.
4.Click Apply.
3.10.4 Configure signed application zip file verificationBy default, the SDN Controller does verify that an application zip file has been signed from a trusted source as defined in your /opt/sdn/admin/sdnjar_trust.jks truststore. To enable or disable checking that all application zip files downloaded through the application manager are signed and are from a trusted source, you must change the value for the “verifyZips” key.
3.10 Support logs screen | 35 |