Log Interface Based on Syslog
|
Availability: This feature was introduced in M2000 V200R011C00. Summary: The M2000 forwards operating system logs, M2000 logs, and NE logs to a third-party system using the Syslog protocol. In this way, the third-party system manages the device logs on the entire network in a centralized manner. Benefits: A third-party system can obtain the log data on the entire network from the M2000 by using the Syslog interface. This implements centralized log management. This improves O&M efficiency and reducing OPEX. The Syslog interface adopts the standard Syslog protocol, which protects the investments of users and reduces interconnection costs. This interface also has the real-time advantage. Description: Before using the Syslog interface to obtain M2000 logs and NE logs from the M2000, users need to set the information about the third-party log server on the M2000 client, such as its IP address, port, protocol, and risk level. In addition, operating system logs are forwarded by the operating system of the M2000 to a third-party system directly . Therefore, a third-party log server must be set for the operating system especially . After the settings of the third-party log server take effect, the M2000 sets the mapping level of newly generated M2000 logs, NE logs,and operating system logs to the Syslog log level and forwards the logs to third-party systems by using the Syslog Protocol. Both M2000 logs and NE logs consist of security logs, operation logs, and system logs. The Syslog interface applies to the following scenarios: ? Centralized log storageIn this scenario, users deploy an independent log storage server to extract the logs on the entire network at any time for analysis and auditing. Therefore, the long-term storage is expected. ? Centralized log auditing In this scenario, users parse logs by using a third-party system, which provides dedicated log management, analysis, and auditing functions. Enhancement: None Dependency: None |

Favorite (0)