WEBVTT

1
00:00.000 --> 00:03.760
So to help reinforce what we've discussed in this set of videos and help

2
00:03.760 --> 00:04.640
improve your skills,

3
00:04.640 --> 00:08.160
here's a hands-on lab for you to practice with policy-based routing.

4
00:08.160 --> 00:11.930
And on R7, I'd like you to go ahead and set up policy-based routing so that

5
00:11.930 --> 00:13.120
traffic sourced

6
00:13.120 --> 00:20.090
from 10.1.7 anything going to the R6 loopback address, which is 6.6.6.6 over

7
00:20.090 --> 00:20.560
here.

8
00:20.560 --> 00:25.680
I want that traffic flow to go ahead and use R8 as the next top. So R8's serial

9
00:25.680 --> 00:26.240
3-slash-2

10
00:26.240 --> 00:32.000
interfaces 10.78.0.8 you can also go over to R8 and verify that IP address.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:26.240 --> 00:32.000
interfaces 10.78.0.8 you can also go over to R8 and verify that IP address.

11
00:32.000 --> 00:35.600
So because the 10.1.7 network is over here we want to apply that policy to the

12
00:35.600 --> 00:36.720
gig 0.0 interface

13
00:36.720 --> 00:40.160
that would identify incoming traffic, see if it's matched, then if it is,

14
00:40.160 --> 00:43.680
to policy-based routing over to R8. Who would then, once he gets the packet,

15
00:43.680 --> 00:47.520
use its routing table to forward traffic up to R6 and its loopback.

16
00:47.520 --> 00:53.090
But in addition, I'd also like you to include traffic sourced from R7 itself

17
00:53.090 --> 00:54.320
from its gig 0.0.0

18
00:54.320 --> 00:58.470
interface, which implies not only a policy being applied to this interface for

19
00:58.470 --> 00:59.200
incoming traffic,

20
00:59.200 --> 01:05.120
but also setting up local policy-based routing as well. So if R7 does a ping to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.200 --> 01:05.120
but also setting up local policy-based routing as well. So if R7 does a ping to

21
01:05.120 --> 01:05.840
6.6.6.6,

22
01:05.840 --> 01:09.630
sourcing it from its interface gig 0.0 address, I also want that to be policy-

23
01:09.630 --> 01:10.720
based routed over.

24
01:10.720 --> 01:14.580
So those are my friend, your lab tasks. Have some fun in this hands-on lab for

25
01:14.580 --> 01:14.960
policy-based

26
01:14.960 --> 01:18.560
routing and then when you are done, join me in the next video and we'll do a

27
01:18.560 --> 01:19.520
walk-through of these

28
01:19.520 --> 01:20.640
lab tasks together.