ADWAN scenario load sharing classic configuration

The networking is as shown above. The requirement is to perform load sharing between PE1 and the server. There are four links between PE1 and P without aggregation, and each link needs to carry traffic. PE2.1 and PE2.2 serve as mutual backups.

(1) PE1-P1link1-PE2.1-server

(2) PE1-P1link2-PE2.1-server

(3) PE1-P2link1-PE2.2-server

(3) PE1-P3link2-PE2.2-server

Step 1: On the [Automation > Transport Network > Policy Management > Application Group] page, click the <Add> button to create an application group, and select Custom for the path creation method.

Step 2: After deploying the application group, the normal application instance distribution progress is 92%, and path constraints need to be applied.

Step 3: Perform path constraint deployment. (Note: Since PE2.1 and PE2.2 are mutual active-standby, there are two policies corresponding to PE-PE2.1 and PE2.2. Each policy should have 4 paths, so the maximum number of candidate paths for the corresponding application group is 4.)

（1）PE-PE2.1

Path 1: Link mode, PE-P1link1-PE2.1

Path 2: Link mode, PE-P1link2-PE2.1

Path 3: Link mode, PE-P2link1-PE2.2-PE2.1

Path 4: Link mode, PE-P2link2-PE2.2-PE2.1

（2）PE-PE2.2

Path 1: Link mode, PE-P2link1-PE2.2

Path 2: Link mode, PE-P2link2-PE2.2

Path 3: Link mode, PE-P1link1-PE2.1-PE2.2

Path 4: Link mode, PE-P1link2-PE2.1-PE2.2

After configuring path constraints, the application instance distribution reaches 100%.

You can check the deployment status of the four paths in the instance details. If all four are valid, the configuration is correct.