You can learn traffic information of the FW based on applications by checking application traffic logs on the eLog.
As shown in Figure 1, the FW is deployed as a gateway on the network boundary. Security policies are configured for the FW to control packets accessing the external network from the internal network.
You need to learn traffic information of the FW based on applications by checking application traffic logs on the eLog.
To fulfill the preceding requirement, configure the system as follows:
Table 1 describes data planning for the FW and eLog.
Data Planning on the FW |
Data Planning on the eLog |
Description |
||
|---|---|---|---|---|
Interface and IP Address |
Security Policy |
IP Address |
Collection Mode |
|
Interface interworking with the eLog: GigabitEthernet 0/0/1 Security zone: DMZ IP address: 172.16.81.1/16 |
Security policy for service traffic:
|
172.16.110.168 |
Collection mode: Dataflow Port: 9002 Log hosts that support dataflow service logs and session logs are configured using the firewall log host host-id ip-address port command. When outputting logs in the dataflow format, the FW uses port 9903 by default, irrelevant to the port number set on the log host. To allow users to send both dataflow service logs and session logs, you are advised to set the log host's port number the same as the port number for session logs. For example, to send binary session logs and dataflow service logs, you are advised to set the port number to 9002. Port 9002 is used as an example. |
The eLog collects logs over port 9903 in dataflow mode. |
Before configuring the FW and eLog, pay attention to the following important check items and complete the configuration based on the actual situation:
The time zone and time of the FW shall be the same as those of the eLog.
If the time zone or time of the FW is different from that of the eLog collector, log query results will be affected. You are advised to use NTP to make the FW and eLog as the clients to synchronize time from the clock source. If NTP is not deployed on the network, you can manually adjust the time on the FW to ensure time consistency between the FW and eLog.
Specify the method of managing the log source (that is, the FW) on the eLog.
Currently, the eLog supports two FW management methods: manual adding and automatic discovery. You are advised to manually add the FW because this method is simple and you do not need to perform extra configuration on the FW. When there are a large number of FW, you can use the other method, automatic discovery. If this method is used, you need to set SNMP parameters on the FW.
Check whether the time zone and time of the FW are the same as those of the eLog collector. In the case of inconsistency, run the following commands to adjust the time zone or time of the FW.
# Adjust the time zone of theFW to keep consistency with that of the eLog collector. Assume that the eLog collector is in the Beijing time zone. The time of the collector is 8 hours earlier than Universal Time Coordinated (UTC). Use the add 08:00:00 parameter. If the eLog collector is in a time zone where the time is later than UTC, use the minus parameter.
<FW> clock timezone BJ add 08:00:00
# Adjust the time of the FW to keep consistency with that of the eLog collector. Assume that the current time of the eLog collector is 00:00:00 on December 1, 2018.
<FW> clock datetime 0:0:0 2018/12/01
After the preceding configuration, run the display clock command to view configuration results.
<FW> display clock
2018-12-01 00:00:06
Tuesday
Time Zone(Default Zone Name) : UTC
Daylight saving time :
Name : utc
Repeat mode : repeat
Start year : 2011
End year : 2018
Start time : 01-01 12:11:00
End time : 12-04 01:00:00
Saving time : 01:00:00
If the eLog manages FW through automatic discovery, SNMP parameters must be configured on the FW. However, if the eLog manages FW through manual adding, skip this step.
# Configure SNMP parameters on FW, so that they can be automatically discovered by the eLog. As SNMPv3 is securer than SNMPv1 or SNMPv2c, you are advised to use SNMPv3. At the same time, you are advised to use SHA2-256 as the authentication protocol and AES128 as the encryption protocol.
<FW> system-view [FW] snmp-agent sys-info version v3 [FW] snmp-agent group v3 group privacy [FW] snmp-agent usm-user v3 admin group group [FW] snmp-agent usm-user v3 admin authentication-mode sha2-256 Please configure the authentication password (8-64) Enter Password: Confirm Password: [FW] snmp-agent usm-user v3 admin privacy-mode aes128 Please configure the authentication password (8-64) Enter Password: Confirm Password:
Complete the basic configuration such as the configuration of the IP address and security zone of the interface.
# Configure the IP address of the interface and assign the interface to the security zone. Here the interface connecting the firewall to the eLog is taken as an example. If the firewall and eLog belong to different networks, configure a route on the firewall to the eLog.
[FW] interface GigabitEthernet 0/0/1 [FW-GigabitEthernet 0/0/1] ip address 172.16.81.1 16 [FW-GigabitEthernet 0/0/1] quit [FW] firewall zone dmz [FW-zone-dmz] add interface GigabitEthernet 0/0/1 [FW-zone-dmz] quit
If the eLog manages firewalls through automatic discovery, you need to run the service-manage SNMP permit command to enable the access permission on SNMP after running the ip address 172.16.81.1 16 command; if the eLog manages firewalls through manual adding, you do not need to run the command.
Configure security policies.
# Configure the security policy for service traffic.
[FW] security-policy [FW-policy-security] rule name policy1 [FW-policy-security-rule-policy1] source-zone trust [FW-policy-security-rule-policy1] destination-zone untrust [FW-policy-security-rule-policy1] source-address 192.168.0.0 24 [FW-policy-security-rule-policy1] action permit [FW-policy-security-rule-policy1] quit
[FW] firewall log host 1 172.16.110.168 9002
[FW] firewall log source 172.16.81.1 6666
[FW] dataflow enable
[FW] dataflow type traffic enable
Enable the function of generating traffic logs. This step is optional. By default, the function of generating traffic logs is enabled. If it is disabled, run the following command to enable it.
[FW] log type traffic enable
After the function of generating traffic log is enabled, the firewall generates a traffic log after the corresponding traffic ends.
Assume that the eLog has been successfully installed; the collector works normally; and the disk space has been planned. Operations for managing log sources and viewing log reports on the eLog are as follows.
For details about how to install and use the eLog, see the product documentation of the corresponding version in .
After the preceding configuration is complete, when traffic generated for the access to the external network from the internal network, the firewall generates traffic logs and outputs the logs to the eLog. You can view the application traffic logs on the eLog.
Click the Log Details tab and set a reasonable query time range. The query results are as shown in the following figure. The log information given here is only an example. Log information in different network environments should conform to the actual conditions.

The query result displays various application traffic passing through the FW interface in a bar graph. In this way, you can learn application traffic rankings of the FW in a timely manner.
This example provides configuration scripts only related to the cooperation between the FW and the eLog.
# sysname FW # dataflow enable dataflow type traffic enable log type traffic enable # firewall log host 1 172.16.110.168 9002 firewall log source 172.16.81.1 6666 # interface GigabitEthernet 0/0/1 ip address 172.16.81.1 255.255.0.0 # firewall zone dmz set priority 50 add interface GigabitEthernet 0/0/1 # snmp-agent snmp-agent sys-info version v3 snmp-agent group v3 group privacy snmp-agent usm-user v3 admin group group snmp-agent usm-user v3 admin authentication-mode sha2-256 cipher %^%#ZgL-L2HsZ<5P]s+:6d)LcBG5)~mdl=te snmp-agent usm-user v3 admin privacy-mode aes128 cipher %^%#i!rs46cpF"_)d#.cJ,'1>wE_>wE # security-policy rule name policy1 source-zone trust destination-zone untrust source-address 192.168.0.0 mask 255.255.255.0 action permit # return