WEBVTT

00:08.920 --> 00:17.590
We have discussed distances one wrote attribute that will be looked over.

00:17.620 --> 00:26.910
Whenever we have to step the crowds to the same destination the lower the distance the better the route.

00:26.970 --> 00:34.680
Now there is another route attribute which is priority we use priority whenever we have two static crowds

00:35.160 --> 00:37.650
with the same distance.

00:37.860 --> 00:44.250
The lower the priority the better the route the better the path.

00:44.250 --> 00:53.160
Now on your routing table you will see both routes but the one with the lowest priority is the best

00:53.310 --> 00:54.040
path.

00:54.060 --> 01:01.960
So we have one step the crowd towards our remote land that uses the land interface and another one that

01:01.960 --> 01:04.110
uses the when one interface.

01:04.110 --> 01:06.930
Now let's see what is its priority.

01:06.930 --> 01:09.100
Currently it has a priority of five.

01:09.820 --> 01:20.840
OK another static crowd to the same destination which uses when one and its priority is zero.

01:21.020 --> 01:29.590
All right so the when one static crowd is the best or the preferred route.

01:29.680 --> 01:31.450
Now let's look at it.

01:32.620 --> 01:34.300
Using our routing table

01:37.650 --> 01:46.000
to get around to info routing table or not take a look.

01:46.020 --> 01:53.190
We have a static crowd this static crowd leads to the eleven not eleven the 11 dot 0 subnet.

01:53.190 --> 01:55.410
Now we have two static crowds.

01:55.410 --> 02:01.530
We have one road which is the preferred route which uses when one interface.

02:01.770 --> 02:07.440
And this second road which is our second best route.

02:07.620 --> 02:12.300
And this one uses a priority of five.

02:12.330 --> 02:22.990
Now if we have two routes it can be static crowds but it can also be dynamic routing protocols that

02:22.990 --> 02:27.240
share the same distance and the same priority.

02:27.670 --> 02:34.080
And in dynamic routing protocols we also have another route attribute which is metric.

02:34.510 --> 02:44.200
If we have two routes that share the same right attributes 48 will load balance the traffic between

02:44.200 --> 02:46.750
the two routes.

02:46.780 --> 02:50.230
This is called equal cost multi path.

02:50.230 --> 02:54.680
Now we can control the load balancing parameters.

02:54.910 --> 02:57.540
We will look at that in our next lesson.