Configuring Intelligent Traffic Steering

CloudCampus Solution V100R019C10 Deployment Guide for Large- and Medium-Sized Campus Networks (Virtualization Scenario)

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

Context

To improve reliability of Internet access, the egress of a campus network is usually connected to different carrier networks. In multi-egress traffic steering scenarios, you can use the ISP-based traffic steering function. This function enables traffic to be forwarded based on carriers, so that traffic destined for different carrier networks is forwarded through the corresponding outbound interfaces, optimizing the traffic forwarding path.

Data Plan

Table 4-15 Data plan for health check

Device	Name of a Health Check Task	Health Check Source IP	Protocol	Destination IP to Be Detected	Port	Outbound Interface	Other Parameters	Description
FW-a	isp1_health	192.0.2.2	Simple TCP	192.0.2.1	1000	XGE0/0/1	Default	Check whether the link to ISP1 is normal.
FW-a	isp2_health	198.51.100.2	Simple TCP	198.51.100.1	1000	XGE0/0/2	Default	Check whether the link to ISP2 is normal.
FW-b	isp1_health	192.0.2.3	Simple TCP	192.0.2.1	1000	XGE0/0/1	Default	Check whether the link to ISP1 is normal.
FW-b	isp2_health	198.51.100.3	Simple TCP	198.51.100.1	1000	XGE0/0/2	Default	Check whether the link to ISP2 is normal.

Table 4-16 Data plan for the carrier address library

Device	Carrier Address Library Name	Address Library File	Description
FW-a	isp1	isp1.csv	The carrier address library can be obtained from the corresponding carrier, and the format must be the same as the template.
FW-a	isp2	isp2.csv
FW-b	isp1	isp1.csv
FW-b	isp2	isp2.csv

Table 4-17 Data plan for multiple egresses connecting to carrier networks

Device	Interface	Carrier	Carrier Route	Default Route	Health Check	Description
FW-a	XGE0/0/1	isp1	Enabled	Enabled	isp1_health	Deploy multi-egress for the interface connected to isp1.
FW-a	XGE0/0/2	isp2	Enabled	Enabled	isp2_health	Deploy multi-egress for the interface connected to isp2.
FW-b	XGE0/0/1	isp1	Enabled	Enabled	isp1_health	Deploy multi-egress for the interface connected to isp1.
FW-b	XGE0/0/2	isp2	Enabled	Enabled	isp2_health	Deploy multi-egress for the interface connected to isp2.

Procedure

Choose Object > Health Check, and click Add to create a health check task based on the data plan. The following example creates the health check task isp1_health on FW-a.
Choose Network > Route > Intelligent Uplink Selection. On the Carrier Address Library tab, click Import. In the dialog box that is displayed, click Download Template. Fill in information about the carrier address library in the template, and import the template. The following example imports the carrier address library isp1 to FW-a.
Choose Network > Interface. Select a physical interface from the interface list, click , and configure multi-egress options for the interface according to the data plan. The following example configures multi-egress options for XGE0/0/1 on FW-a connecting to isp1.