Functions of submission on the USG6000

11

Functions of submission on the USG6000 are as follows:
Configurations can take effect only after they are submitted.

Other related questions:
Submission of Spark tasks
After preparing the job.properties file, log in to the Oozie client, run the Oozie job command in the corresponding working directory to execute the workflow file, and submit the Oozie tasks. For details, see the service operation guide of the Oozie component in the HD Product Documentation.

Submission of Oozie tasks
Log in to the Oozie client and use Hue to submit Oozie tasks. For details, see the service operation guide of the Oozie component in the HD Product Documentation.

Blacklist definition and implementation mechanism of the USG6000 series
The USG6000 series supports configuring the blacklist. The definition and mechanism of a blacklist are as follows: The blacklist is a typical measure for security defense. The system discards all packets that match the blacklist. The blacklist is more efficient in filtering packets from or to specific IP addresses when compared with security policies. The USG6000 series supports blacklisting users, source addresses, or destination addresses to form three types of blacklists. -User blacklist After a user is added to the blacklist, the device discards the packets from or to the user. -Source IP address blacklist After a source IP address is added to the blacklist, the device discards all packets from this IP address. -Destination IP address blacklist After a destination IP address is added to the blacklist, the device discards the packets destined for this IP address.

Function of the traffic report for the USG6000 series
The function of the traffic report for the USG6000 series is as follows: Traffic reports display traffic trends and top rankings in various dimensions. You can effectively learn the traffic status of the current network based on traffic reports and therefore formulate the corresponding traffic measurement measures.

USG6000 interface overview
USG6000 interface overview Interface types An NGFW supports physical and logical interfaces. 1. Physical interface a. Layer 3 Ethernet interface. Description: Works at the network layer to process Layer 3 packets with an IPv4 or IPv6 address specified and supports routing functions. b. Layer 2 Ethernet interface. Description: Works at the data link layer and processes Layer 2 packets, implementing rapid Layer 2 forwarding. 2. Logical interface a. Virtual template (VT) interface. Description: Helps a Point-to-Point Protocol over Ethernet (PPPoE) server with PPP negotiation or encapsulates Layer 2 Tunneling Protocol (L2TP) packets. b. Dialer interface. Description: Used by a PPPoE client. c. Tunnel interface. Description: Applies to packet encapsulation and decapsulation and IPv6 transition technologies. GRE and IPSec are common encapsulation protocols. d. Null interface. Description: Any packets transmitted over this interface are discarded. It is mainly used for route filtering. The null interface cannot be configured through the web UI. e. VLAN interface. Description: A Layer 3 logical interface that is assigned an IPv4 or IPv6 address. VLAN interfaces transmit packets between VLANs. f. Layer 3 Ethernet subinterface. Description: Layer 3 Ethernet subinterfaces are Layer 3 logical interfaces created on a physical interface. f. Layer 2 Ethernet subinterface. Description: Layer 2 Ethernet subinterfaces are Layer 2 logical interfaces created on a physical interface. h. Eth-Trunk interface (interface aggregation). Description: A logical interface that consists of multiple Layer 2 or Layer 3 Ethernet interfaces. An Eth-Trunk interface provides high bandwidth and reliability. i. Loopback interface. Description: Remains in the Up state and is assigned a 32-bit subnet mask.

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