Connecting the USG2000&5000 series to the log server


The method of connecting the USG2000&5000&6000 to the log server is as follows:
1. Run the system-view command to access the system view.
2. Optional: Run the info-center source { module-name | default } channel { channel-number | channel-name } [ log { state { on | off } | level severity } * ] command to add log information to the information channel.
By default, the information center dispatches the logs destined for a log server to information channel 2. Log output is enabled and the severity of the logs is informational. This command is used only to change the default configuration.
module-name specifies the module that outputs logs, and severity specifies the log severity.
3. Bind an information channel to a log server, so that logs are output to the log server through the information channel.
4. Configure the IP address and other parameters of the log server.
info-center loghost ip-address [ port ] [ module { module-name } &<1-6> ]
info-center loghost ip-address [ port ] [ channel { channel-number | channel-name } | facility local-number | language { chinese | english } ]*
The channel-number or channel-name configured here shall be consistent with that in step 1.
5. Optional: Run the info-center loghost source ip-address command to specify the IP address that sends log information.

Other related questions:
Defining services for the USG2000&5000 series
The USG2000&5000 series supports defining services using the web UI or CLI. Service can be used as a security policy matching condition. The system has a predefined service set, and you can define services by specifying such information as the port. Defining services using the web UI: Choose Firewall > Service > User-defined Service and click Create in User-defined Service List. Enter or select service information, including the name, description, and protocol, and click Apply. Defining services using the CLI: 1. Run the ip service-set service-set-name type object [ vpn-instance vpn-instance-name ] command in the system view to create a service set and access its view. 2. Add members to this service set. a. Run the service [ id ] protocol { udp | tcp | sctp } [ source-port { src-port-number-1 [ to src-port-number-2 ] } &<1-64> | destination-port { dst-port-number-1 [ to dst-port-number-2 ] } &<1-64> ] * [ description description ] command to specify protocol types, such as TCP, UDP, or SCTP, by port number ranges. b. Run the service [ id ] protocol icmp [ icmp-type { icmp-name | icmp-type-number icmp-code-number } ] [ description description ] command to specify the ICMP message type or code. c. Run the service [ id ] protocol protocol-number [ description description ] command to specify the protocol field value in IP packet headers to specify the protocol type. 3. Run the description text command to configure the service set description.

First login to the USG2000&5000
Administrators can log in to the web UI through the console interface or HTTPS.

Whether the USG2000&5000&6000 series can serve as an FTP server
They can serve as an FTP server to upload configuration files and system software versions but not as a server to provide public services for intranet users.

The USG2000 & 5000 connect with the vsm lite network management server
USG2000 & 5000 and vsm lite network management server connect method are as follows: 1. Configure the interface address, route, and security zone of the USG so that the USG and the VSM can communicate with each other. 2. Configure the SNMP protocol parameters and Trap alarm function of the USG so that the alarms generated by the USG can be sent to the VSM network. 3. Configure the USG's Telnet protocol parameters to be consistent with the VSM network management so that the USG can be successfully added to the VSM network. 4. Configure the VSM SNMP protocol parameters and Telnet protocol parameters. Because the default SNMP protocol template can meet the requirements, you need to configure the Telnet protocol template in the NMS and add the USG to the VSM through the configured Telnet protocol template. 5. Add the USG to the VSM mainframe topology. Immediately after the synchronization operation, so that VSM can get the latest USG data.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top