HiSecEngine USG6000F Typical Configuration Examples
Web: Example for Configuring Load Balancing Based on Link Weight
Networking Requirements
In Figure 5-9, an enterprise has a 50M link connected to ISP1, and a 150M link connected to ISP2.
The enterprise requires that the ISP2 link forward 80% of the traffic and ISP1 link forward 20% of the traffic to improve the Internet access experience of most users.
When one link becomes faulty, follow-up traffic will be forwarded on the other link to ensure transmission availability.
In this example, interface 1, interface 2, and interface 3 represent GE 0/0/1, GE 0/0/2, and GE 0/0/3, respectively.
Configuration Roadmap
The enterprise requires that the traffic ratio on ISP2 and ISP1 links is 4:1. Therefore, set the intelligent uplink selection mode to load balancing based on link weight and set the weights of ISP2 and ISP1 links to 4 and 1, respectively. To ensure that DeviceA can use other links to forward traffic when a link is faulty, you need to configure health check function.
- Set interface IP addresses, security zones, gateway addresses, bandwidth.
- Optional: Configure the health check function, and configure a health check task for ISP1 and ISP2, respectively.
Configure a global route selection policy. Set the intelligent uplink selection mode to load balancing based on link weight, configure the outbound interfaces on DeviceA connecting to ISP1 and ISP2 networks as intelligent uplink selection member interfaces, set weights for the interfaces, and reference health check.
Configure a basic security policy to allow intranet users to access the Internet.
This example focuses on the configuration related to intelligent uplink selection. Configure other data such as NAT based on the actual networking.
Procedure
- Set IP addresses for interfaces on the firewall and add the interfaces to security zones.
- Enable the health check function and create a health check for ISP1 and ISP2 link respectively. Assume that the destination network segment is 192.0.2.0/24 for ISP1 and is 198.51.100.0/24 for ISP2.
- Configure a global route selection policy to load balance traffic by link bandwidth and reference the health check.
- Configure a Trust-to-Untrust interzone security policy to allow enterprise intranet users to access Internet resources. Assume that the intranet user network segment is 10.3.0.0/24.
Verifying the Configuration
- After the network has been running for a period of time, run the display interface brief command on interface 1 (GE 0/0/1) and interface 2 (GE 0/0/2) to check the average bandwidth usage (OutUti field) in the outbound direction within the last 300s and verify that the OutUti ratio of the two interfaces is close to 1:4.
- Run the display firewall session table interface ge 0/0/1 and display firewall session table interface ge 0/0/2 commands to check the number of sessions on the two interfaces and verify that the ratio is close to 1:4.
Configuration Scripts
# sysname DeviceA # healthcheck enable # healthcheck name isp_health destination 192.0.2.1 interface GE0/0/1 next-hop 10.10.1.2 protocol tcp destination-port 10001 destination 198.51.100.1 interface GE0/0/2 next-hop 10.20.1.2 protocol tcp destination-port 10003 # interface GE0/0/1 ip address 1.1.1.1 255.255.255.0 gateway 1.1.1.254 bandwidth ingress 50000 bandwidth egress 50000 # interface GE0/0/2 ip address 2.2.2.2 255.255.255.0 gateway 2.2.2.254 bandwidth ingress 150000 bandwidth egress 150000 # interface GE0/0/3 ip address 10.3.0.1 255.255.255.0 # firewall zone trust set priority 85 add interface GE0/0/3 # firewall zone untrust set priority 5 add interface GE0/0/1 add interface GE0/0/2 # multi-interface mode proportion-of-weight add interface GE0/0/1 add interface GE0/0/2 weight 4 healthcheck isp_health # security-policy rule name policy_sec_trust_untrust source-zone trust destination-zone untrust source-address 10.3.0.0 mask 255.255.255.0 action permit # return