User guide

HWC_Ongoing.fm
A31003-W1010-A100-1-7619, July 2005
HiPath Wireless Controller, Access Points and Convergence Software V3.0: User Guide
149
Ongoing operation
Controller, Access Points and Convergence Software logs and traces
12.4 Controller, Access Points and Convergence Software logs and
traces
Controller, Access Points and Convergence Software log and data files
The Controller, Access Points and Convergence Software system stores configuration data and
log files. These files include:
● event and alarm logs (triggered by events, described below)
● trace logs (triggered by component activity, described below)
● accounting files (created on a half-hourly basis, up to six files)
The files are stored in the operating system and have a maximum size of 1 GB.
The accounting files are stored in flat files in a directory that is created every day. Eight
directories are maintained in a circular buffer (when all are full, the most recent replaces the
earliest).
12.4.1 Viewing log, alarm and trace messages
To view the logs and traces, select the Logs & Traces tab. The HiPath Wireless Controller
generates three 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
● Audits: files that record administrative changes made to the system (the GUI Audit displays
changes to the Graphical User Interface on the HiPath Wireless Controller)
Logs and alarms
The log messages contain the time of event, severity, source component and any details
generated by the source component. The messages are classified at four levels of severity:
● Informational, the activity of normal operation
● Minor (alarm)
● Major (alarm)
● Critical (alarm)
The alarm messages (minor, major or critical log messages) are triggered by activities that
meet certain conditions that should be known and dealt with.
Examples of events on the HiPath Wireless Controller that generate an alarm message: