WEBVTT

00:07.300 --> 00:15.610
Well we have different grounds to the same destination and the roads all have the same road attributes

00:16.150 --> 00:25.970
that is distance priority or maybe metric then differing it will load balanced the traffic.

00:25.970 --> 00:36.050
Now this is called equal cost multi path ICMP but we can change the way or the parameters that 48 loan

00:36.050 --> 00:38.090
balances the traffic.

00:38.090 --> 00:39.470
Let's see how we do it.

00:40.620 --> 00:46.680
Let's get over to our command line config system settings

00:54.490 --> 00:58.170
set V4 ECM P mode.

00:58.200 --> 01:04.270
Now if you scroll you will see four different methods.

01:04.270 --> 01:11.260
The first one source IP based all traffic that comes from the same source will be destined to the same

01:11.350 --> 01:16.660
route weighted IP based wav IP based.

01:16.750 --> 01:26.390
That is all traffic will be routed or will be distributed between different interfaces.

01:26.680 --> 01:33.760
And that is according to a weak number that we will configure on the different interface.

01:33.760 --> 01:39.740
We will look at it in a minute usage IP based.

01:39.910 --> 01:47.890
All traffic will be distributed towards a specific interface.

01:48.040 --> 01:52.760
And that is until a volume threshold is approached.

01:52.840 --> 02:00.190
We will also see how we configure and volume threshold to an interface.

02:00.190 --> 02:06.910
When it approaches the threshold approaches then the traffic will move to another route.

02:07.810 --> 02:10.630
And the last one is the source destination IP.

02:10.960 --> 02:13.180
And that is the same as source site.

02:13.210 --> 02:15.570
But it also includes the destination.

02:15.580 --> 02:23.110
That is all traffic that comes from the same source and destined to the same destination will follow

02:23.110 --> 02:25.660
the same route.

02:26.130 --> 02:30.850
That's config await to our

02:33.720 --> 02:35.120
tor interface.

02:40.560 --> 02:46.120
Let's use when one set way.

02:46.710 --> 02:52.140
And now higher weights are likely to be chosen.

02:52.140 --> 03:00.060
That is the traffic will be distributed between the different interfaces all the different rules but

03:00.150 --> 03:06.630
interfaces or routes that has higher weights will probably get more traffic.

03:06.630 --> 03:15.050
Now we can set up the weight between 0 and 255 so let's set it up to two hundred and fifty five.

03:15.810 --> 03:17.260
And that's it.

03:18.920 --> 03:30.050
So if we choose the wafer PE method one one would probably get more traffic than other arouse other

03:30.050 --> 03:38.860
same routes that has lower weights when we use these pill over method.

03:38.870 --> 03:48.350
That is when threshold volume is approached on a specific round or an interface the traffic will flow

03:48.350 --> 03:51.560
to the second route.

03:51.560 --> 03:55.430
Now how do we set up a volume threshold.

03:55.430 --> 04:00.110
We use the same config sys interface.

04:00.560 --> 04:10.960
Edit the interface or the rule that we want to configure the threshold and then we use the set spill

04:10.960 --> 04:19.820
over threshold and that is a value between 0 and 16 million so that's just choose

04:27.700 --> 04:28.510
no right.