- Table of Contents
-
- 07-Network Management and Monitoring Configuration Guide
- 00-Preface
- 01-Information center configuration
- 02-Fast log output configuration
- 03-Packet capture configuration
- 04-Interface collaboration configuration
- 05-System maintenance and debugging configuration
- 06-NQA configuration
- 07-BFD configuration
- 08-Track configuration
- 09-Monitor Link configuration
- 10-CWMP configuration
- 11-NTP configuration
- 12-EAA configuration
- 13-Process monitoring and maintenance configuration
- 14-NETCONF configuration
- 15-SNMP configuration
- 16-RMON configuration
- 17-Event MIB configuration
- 18-NetStream configuration
- 19- configuration
- 20-Process placement configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
02-Fast log output configuration | 70.98 KB |
Contents
Restrictions and guidelines: fast log output configuration
Configuring fast output of logs to log hosts
Configuring fast log output to use the UTF-8 encoding
Fast log output configuration examples
Example: Configuring fast log output to a log host
Configuring fast log output
About fast log output
The fast log output feature enables fast output of logs to log hosts.
Typically, logs generated by a service module are first sent to the information center, which then outputs the logs to the specified destination (such as to log hosts). When fast log output is configured, logs of service modules are sent directly to log hosts instead of to the information center. Compared to outputting logs to the information center, fast log output saves system resources. For more information about the information center, see "Configuring the information center."
Logs are classified into eight severity levels from 0 through 7 in descending order.
Severity value |
Level |
Description |
0 |
Emergency |
The system is unusable. For example, the system authorization has expired. |
1 |
Alert |
Action must be taken immediately. For example, traffic on an interface exceeds the upper limit. |
2 |
Critical |
Critical condition. For example, the device temperature exceeds the upper limit, the power module fails, or the fan tray fails. |
3 |
Error |
Error condition. For example, the link state changes. |
4 |
Warning |
Warning condition. For example, an interface is disconnected, or the memory resources are used up. |
5 |
Notification |
Normal but significant condition. For example, a terminal logs in to the device, or the device reboots. |
6 |
Informational |
Informational message. For example, a command or a ping operation is executed. |
7 |
Debugging |
Debug message. |
Log header formats
The log header formats of fast output logs are as follows:
Table 2 Log header formats
Log header types |
Format |
Standard format |
Example: |
Customized format |
URL filtering UNICOM format: Example: NAT CMCC format: Example: NAT UNICOM format: Example: NAT TELECOM format: Example: |
Log field description
Table 3 Log field description
Field |
Description |
PRI |
Log type code. · Standard format and NAT UNICOM format: 134. · URL filtering UNICOM format, NAT CMCC format, and NAT TELECOM format: 142. |
Timestamp |
Records the time when the log was generated. The timestamp is in the format of YYYY Mon DD hh:mm:ss. |
AppName |
Name of the device that generated the log. |
%%10 |
Vendor of the device that generated the log. |
SN |
Serial number of the device that generated the log. To view the device serial number, see the DEVICE_SERIAL_NUMBE field in the output of the display device manuinfo command. This field is available only when the device is configured to carry the serial number in fast output logs by using the customlog with-sn command. |
VsysId |
Virtual system that generated the log. |
HostName |
Source IPv4 address of the device that generated the log. |
MsgID |
Log type. |
Len |
Total length of the log header, in bytes. |
ProcID |
- |
Restrictions and guidelines: fast log output configuration
The device supports outputting logs from service modules to log hosts by using the following methods in descending order of priority:
1. Fast log output.
2. Information center.
If you configure multiple log output methods for a service module, the service module outputs its logs in the method that has the highest priority.
Configuring fast output of logs to log hosts
1. Enter system view.
system-view
2. Enable fast log output.
customlog format { attack-defense | dns | dpi [ anti-virus | audit | ip-reputation | ips [ sgcc ] | url-filter [ unicom ] | waf ] | keepalive sgcc | packet-filter [ sgcc ] | scd | security-policy sgcc | session }
By default, fast log output is disabled.
3. Configure fast log output parameters.
customlog host [ vpn-instance vpn-instance-name ] { hostname | ipv4-address | ipv6 ipv6-address } [ port port-number ] export { attack-defense | dns | dpi [ anti-virus | audit | ip-reputation | ips | url-filter | waf ] * | keepalive | packet-filter | scd | security-policy | session } *
By default, no fast log output parameters are configured.
The value for the port-number argument must be the same as the port number configured on the log host. Otherwise, the log host cannot receive logs.
4. (Optional.) Specify the source IP address for fast log output.
customlog host source interface-type interface-number
By default, the source IP address of fast output logs is the primary IP address of the outgoing interface.
If this command is configured, the primary IP address of the specified interface is used as the source IP address of fast output logs regardless of the outgoing interface.
Configure this command when you need to filter logs by source IP address on the log host.
5. (Optional.) Configure the timestamp of fast output logs to show the system time.
customlog timestamp localtime
By default, the timestamp of fast output logs shows the Greenwich Mean Time (GMT).
Configuring fast log output to use the UTF-8 encoding
About this task
The fast log output module and the log host must use the same character set encoding. If they use different encodings, the log host cannot correctly display Chinese characters in the log messages received from the fast log output module. By default, fast log output uses the GB18030 encoding. You can perform this task to configure fast log output to use the UTF-8 encoding.
Procedure
1. Enter system view.
system-view
2. Configure fast log output to use UTF-8 encoding.
customlog character-encoding utf-8
By default, fast log output uses the GB18030 encoding.
Fast log output configuration examples
Example: Configuring fast log output to a log host
Network configuration
As shown in Figure 1, configure fast log output on the device to send session logs to the log server.
Procedure
1. Assign IP addresses to interface GigabitEthernet 1/0/2.
<Device> system-view
[Device] interface gigabitethernet 1/0/2
[Device-GigabitEthernet1/0/2] ip address 1.1.0.1 255.255.0.0
[Device-GigabitEthernet1/0/2] quit
2. Configure settings for routing.
This example configures a static route, and the next hop in the router is 1.1.0.2.
[Device] ip route-static 1.2.0.0 16 1.1.0.2
3. Add interface GigabitEthernet 1/0/2 to security zone untrust.
[Device] security-zone name untrust
[Device-security-zone-Untrust] import interface gigabitethernet 1/0/2
[Device-security-zone-Untrust] quit
4. Configure a security policy:
# Configure a rule named loglocalout to allow the device to send fast log output messages to the server.
[Device] security-policy ip
[Device-security-policy-ip] rule name loglocalout
[Device-security-policy-ip-1-loglocalout] source-zone local
[Device-security-policy-ip-1-loglocalout] destination-zone untrust
[Device-security-policy-ip-1-loglocalout] source-ip-host 1.1.0.1
[Device-security-policy-ip-1-loglocalout] destination-ip-host 1.2.0.1
[Device-security-policy-ip-1-loglocalout] action pass
[Device-security-policy-ip-1-loglocalout] quit
[Device-security-policy-ip] quit
5. Configure fast log output. Enable fast log output, configure log output to the log server, and enable logging for session creation and deletion. Enable IPv4 session logging in the inbound direction of the interface connected to the internal network.
[Device] customlog format session
[Device] customlog host 1.2.0.1 port 1000 export session
[Device] session log flow-begin
[Device] session log flow-end
[Device] interface gigabitethernet 1/0/1
[Device-GigabitEthernet1/0/1] session log enable ipv4 inbound
Verifying the configuration
On the server, verify that logs are received from the device successfully.