Hi, everyone!
For details about OLT alarm and log analysis, see the following sections:
Alarm Analysis:
An alarm indicates that a fault or event occurs. The alarm information includes a detailed description of a fault or exception, possible causes, and troubleshooting suggestions. The information involves multiple sectors, such as hardware, link, service, and CPU usage, and is important in fault analysis and location.
When a fault occurs, check whether the system reports an alarm. If the system reports an alarm, analyze the alarm related to the fault and clear the alarm based on the alarm information to rectify the fault.
The difference between an alarm and an event is as follows: An alarm is generated when an exception occurs or will occur; an event is a notification sent by the system in the proper running.
Querying Alarm Information
Run the display alarm active command to query the alarm information saved in the system.
Run the display alarm configuration command to query the alarm settings based on an alarm ID.
Run the display alarm history command to query historical alarms.
Run the display alarm jitter-proof command to check whether the alarm jitter-proof function is enabled and query the alarm jitter-proof period.
Querying Event Information
Run the display event configuration command to query the event settings based on an event ID.
Run the display event history command to query historical events.
Run the display event list command to query the event's basic information.
Run the display event statistics command to query event statistics records.
Log analysis:
Log analysis is a daily maintenance method. Recorded logs help users to better know system maintenance information and therefore facilitate troubleshooting. Network managers can query and save logs periodically to better detect unauthorized logins or operations and locate a fault in a timely manner.
Log Types
Logs are classified into security logs and operation logs.
Security logs are recorded after security events occur. The system supports three types of security logs: maintenance user online and offline events, user lock events, and automatic backup success events.
Operations logs record configuration commands that are issued using the CLI or SNMP successfully. The system records successful and failed operations.
Both security logs and operation logs are reported to the NMS.
[Remarks]
In versions earlier than V008R012, the system supports a maximum of 512 operation logs and the number is increased to 5000 in V008R012.
Common Operations
display log: queries the names and IP addresses of users that have performed operations in the system, and the operation time and detailed operations.
display log failure: queries the configuration failure logs about a user that has the same level or lower level than the current user.
loghost add: enables the log servers to save device logs because the device has limited space for saving logs.
loghost activate: activates the log host. The system reports logs to a log host only after the activation.
Thank you for reading!
