Specifications

Summit WM Maintenance Guide, Software Version 5.3 87
7 Logs, traces, audits, and DHCP messages
The Summit WM Controller generates four types of messages:
● Logs (including alarms) – Messages that are triggered by events
● Traces – Messages that display activity by component, for system debugging, troubleshooting and
internal monitoring of software
CAUTION
In order for the Debug Info option on the Altitude AP Traces page to return trace messages, this option must be
enabled while Altitude AP debug commands are running. To do so, you need to run a Altitude AP CLI command
to turn on a specific Altitude AP debug. Once the CLI command is run, select the Debug Info option, and then
click Retrieve Traces. For more information, see the Summit WM CLI Reference Guide.
Because Altitude AP debugging can affect the normal operation of Altitude AP service, enabling debugging is not
recommended unless specific instructions are provided.
● Audits – Messages that record administrative changes made to the system
● DHCP – Messages that record DHCP service events
The topics in this chapter are organized as follows:
● Working with logs
● Working with trace messages
● Viewing audit messages
● Viewing DHCP messages
● Viewing software upgrade and operating system patch messages
● Viewing restore/import messages
Working with logs
The log messages contain the time of event, severity, source component, and any details generated by
the source component. Log messages are divided into three groups:
● Summit WM Controller logs
● Altitude AP logs
● Login logs
Log severity levels
Log messages are classified at four levels of severity:
● Information (the activity of normal operation)
● Minor (alarm)
● Major (alarm)