WEBVTT

1
00:00.000 --> 00:04.320
So here are the lab tasks. So let's go to the lab environment and let's set it

2
00:04.320 --> 00:04.480
up.

3
00:04.480 --> 00:08.320
So I have reset my lab so it's back to square one. Let me go ahead and open up

4
00:08.320 --> 00:09.120
the topology by

5
00:09.120 --> 00:13.480
double clicking here on the desktop. Fantastic. And let's go to server one and

6
00:13.480 --> 00:14.480
open it up by

7
00:14.480 --> 00:17.950
selecting it and double clicking and give that a moment to initialize. Here it

8
00:17.950 --> 00:18.800
comes. Great, great,

9
00:18.800 --> 00:26.190
great. So just as a test, let's go down to PC7 right here. And let's just do a

10
00:26.190 --> 00:26.960
trace to the

11
00:26.960 --> 00:30.090
loop back address in our six. Just to verify it takes the normal path. So what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.960 --> 00:30.090
loop back address in our six. Just to verify it takes the normal path. So what

12
00:30.090 --> 00:31.600
I expect based on

13
00:31.600 --> 00:35.000
the routing that's currently in place is PC7 would forward to its default

14
00:35.000 --> 00:36.000
gateway are seven,

15
00:36.000 --> 00:38.640
who would send it to our five, who would send it to our three, then to our one,

16
00:38.640 --> 00:39.440
etc.

17
00:39.440 --> 00:42.840
And it wouldn't go straight over on the serial link because the 1070 zero

18
00:42.840 --> 00:43.680
network is not

19
00:43.680 --> 00:48.380
included as part of OSPF. So let's go to PC7 and we'll click on the right tab

20
00:48.380 --> 00:49.200
for that. Super,

21
00:49.200 --> 00:55.850
super. It's IP address is 10.1.7.10 and let's do first a ping over to the loop

22
00:55.850 --> 00:56.960
back on our six.

23
00:56.960 --> 01:00.680
Just to verify basic connectivity and that is working and then we'll do a trace
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:56.960 --> 01:00.680
Just to verify basic connectivity and that is working and then we'll do a trace

24
01:00.680 --> 01:01.440
. We'll do the

25
01:01.440 --> 01:06.400
trace over to six. Six. Six. Six. Six. Six. And survey says there's our path

26
01:06.400 --> 01:07.440
and by default it's

27
01:07.440 --> 01:11.050
using UDP hence the port unreachable at the final destination. But if we go

28
01:11.050 --> 01:12.320
ahead and do a trace

29
01:12.320 --> 01:17.670
and say dash capital P and protocol one that'll use ICMP and that'll avoid that

30
01:17.670 --> 01:18.560
last destination

31
01:18.560 --> 01:22.480
port unreachable message. All right, so there's our path to our seven, then our

32
01:22.480 --> 01:24.000
five, and then our three,

33
01:24.000 --> 01:28.240
and then our one, two, and four, and then finally to our six. So let's go to

34
01:28.240 --> 01:29.440
our seven and let's see

35
01:29.440 --> 01:33.030
what we have in the way of access control lists show access lists and nothing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:29.440 --> 01:33.030
what we have in the way of access control lists show access lists and nothing

36
01:33.030 --> 01:34.240
there show route map.

37
01:34.240 --> 01:37.040
And that's because I reset the lab fantastic. So let's go ahead and do

38
01:37.040 --> 01:38.160
configuration mode. Let's

39
01:38.160 --> 01:41.580
create access control list to identify the traffic that we want to policy base

40
01:41.580 --> 01:42.720
route. So let's go

41
01:42.720 --> 01:47.230
ahead and use access list, how about one, two, three, and then we'll print and

42
01:47.230 --> 01:48.640
the lab didn't ask for any

43
01:48.640 --> 01:52.820
specific protocols. So let's say IP and let's take a look at the lab tasks one

44
01:52.820 --> 01:53.840
more time. And we've got

45
01:53.840 --> 01:58.890
a source to traffic from 10.1.7 anything. That's this network down here going

46
01:58.890 --> 02:00.320
to the loopback address of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
01:58.890 --> 02:00.320
to the loopback address of

47
02:00.320 --> 02:06.230
6666 over here on r6. So for the source address will specify 10.1.7.0 and then

48
02:06.230 --> 02:07.280
for wildcard bits we'll

49
02:07.280 --> 02:10.630
say we want to match on the first octet and the second octet and the third oct

50
02:10.630 --> 02:11.760
et. But we don't care

51
02:11.760 --> 02:15.830
about the fourth octet. So we'll put wildcard bits there space. So that's the

52
02:15.830 --> 02:17.120
source and the destination

53
02:17.120 --> 02:22.370
is the specific IP address of 6666 and we are done. So there's our access

54
02:22.370 --> 02:23.600
control list. Then let's

55
02:23.600 --> 02:27.750
create a route map. So route map space is called PBR and let's go ahead and

56
02:27.750 --> 02:29.520
make sequence number 10.

57
02:29.520 --> 02:34.700
So permit 10 and in this route map entry of sequence 10 we want to match on the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:29.520 --> 02:34.700
So permit 10 and in this route map entry of sequence 10 we want to match on the

58
02:34.700 --> 02:35.840
IP address

59
02:35.840 --> 02:39.720
specified in access list 1 2 3 including the source and destination there.

60
02:39.720 --> 02:40.720
Fantastic. And if that

61
02:40.720 --> 02:44.120
happens we're going to set the IP next top to the IP address and let's take a

62
02:44.120 --> 02:45.200
look at our topology

63
02:45.200 --> 02:51.590
for a moment to 10.78.0.8. And that way our 7 will pulse you base route that

64
02:51.590 --> 02:52.480
directly over to r8

65
02:52.480 --> 02:56.730
instead of sending it up to r5 etc. So let's go ahead and put that IP address

66
02:56.730 --> 03:01.360
in of r8 which is 10.78.0.8
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:56.730 --> 03:01.360
in of r8 which is 10.78.0.8

67
03:01.360 --> 03:04.810
and then we'll go ahead and apply this to interface let's take a look at our

68
03:04.810 --> 03:05.920
topology. We'll apply this

69
03:05.920 --> 03:11.530
to interface gig 0 0 on our 7 that way traffic from PC 7 as it goes into router

70
03:11.530 --> 03:12.640
7 can be policy

71
03:12.640 --> 03:18.670
base routed. So we'll go into interface gig 0 slash 0 and we'll use command IP

72
03:18.670 --> 03:19.840
policy the keyword

73
03:19.840 --> 03:23.700
route map and then the name of our policy which is PBR so I'll go ahead and

74
03:23.700 --> 03:25.120
copy paste that in

75
03:25.120 --> 03:29.560
and press enter. And now let's go ahead and test from PC 7 where just a moment

76
03:29.560 --> 03:30.240
ago I was taking
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:29.560 --> 03:30.240
ago I was taking

77
03:30.240 --> 03:34.020
that full path. This is the up arrow key press enter and that should be going

78
03:34.020 --> 03:35.200
directly over to

79
03:35.200 --> 03:39.650
r8 which it is because of the policy base routing. Fantastic so what about

80
03:39.650 --> 03:40.640
traffic being sourced from

81
03:40.640 --> 03:45.870
our 7 itself. So here are 7 if we'd have been paying space let's do a trace.

82
03:45.870 --> 03:47.280
Let's do a trace to

83
03:47.280 --> 03:52.180
6.6.6.6 and let's source it from our interface let's go ahead and look at the

84
03:52.180 --> 03:52.960
topology. Let's

85
03:52.960 --> 03:58.740
source it from our gig 0 0 so we'll put gig 0 0 there press enter. Notice this

86
03:58.740 --> 04:00.000
traffic is going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:00.000 --> 04:06.900
from r7 to r5 as shown right there and then up to r3 and then to r1 and r2 and

88
04:06.900 --> 04:08.080
r4. So this traffic

89
04:08.080 --> 04:11.950
is not being policy based routed but in the lab tasks it asks us to also

90
04:11.950 --> 04:13.440
include traffic source from

91
04:13.440 --> 04:18.560
r7 from this gig 0 0 interface address which implies we need to do local policy

92
04:18.560 --> 04:19.280
based routing so

93
04:19.280 --> 04:25.050
currently if we do a show IP policy press enter currently we only have gig 0 0

94
04:25.050 --> 04:26.080
and ingress traffic

95
04:26.080 --> 04:30.600
coming in there from other devices based on this route map called pbr. So what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:26.080 --> 04:30.600
coming in there from other devices based on this route map called pbr. So what

96
04:30.600 --> 04:31.600
we could do is go

97
04:31.600 --> 04:35.330
into configuration mode say you know what in addition to ingress traffic coming

98
04:35.330 --> 04:36.320
on the interface

99
04:36.320 --> 04:41.040
let's also specify any traffic use source is also going to be considered for

100
04:41.040 --> 04:42.000
policy based routing

101
04:42.000 --> 04:46.370
and to do that we're going to do the command IP local policy and then route map

102
04:46.370 --> 04:46.480
and then

103
04:46.480 --> 04:50.740
then in a route map which is pbr and press enter and now if we do the command

104
04:50.740 --> 04:52.080
show IP policy

105
04:52.080 --> 04:56.410
we're now doing traffic coming in on gig 0 0 which we like traffic coming in

106
04:56.410 --> 04:57.840
from pc7 and we also have

107
04:57.840 --> 05:01.800
local pbr also set up that's for traffic source by the route or so now if we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:57.840 --> 05:01.800
local pbr also set up that's for traffic source by the route or so now if we

108
05:01.800 --> 05:02.720
hit the up here a few

109
05:02.720 --> 05:08.250
times and we do a trace route to 6666 sourcing it from gig 0 0 which is our 10.

110
05:08.250 --> 05:10.560
1.7.7 address and press enter

111
05:10.560 --> 05:14.530
now it should also be routed as shown right here so the traffic from r7 with

112
05:14.530 --> 05:15.920
policy based routed

113
05:15.920 --> 05:20.970
over to r8 and then r8 forwarded up to r6 and if we did a debug IP policy and

114
05:20.970 --> 05:22.800
did that same trace again

115
05:22.800 --> 05:26.730
we could verify with the output here that is being policy routed as shown in

116
05:26.730 --> 05:27.600
these entries

117
05:27.600 --> 05:31.470
or right here and if we did the trace without specifying a source address what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:27.600 --> 05:31.470
or right here and if we did the trace without specifying a source address what

118
05:31.470 --> 05:32.640
that's going to do

119
05:32.640 --> 05:36.240
is going to basically cause r7 to use the interface from its routing table

120
05:36.240 --> 05:37.440
closest to the destination

121
05:37.440 --> 05:42.120
so the egress interface would be gig 2 0 and the source address would be 10.1.

122
05:42.120 --> 05:43.520
57.7 so we did the

123
05:43.520 --> 05:47.440
trace without specifying the source of gig 0 0 it's going to be routed as

124
05:47.440 --> 05:48.640
normal and let me turn off

125
05:48.640 --> 05:51.960
debugging and then we'll look at the output here so we'll drop debugging the

126
05:51.960 --> 05:54.320
path went from r7 to r5

127
05:54.320 --> 06:01.210
and then to r3 and then to r1 and r2 and then it went to r4 as shown right
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
05:54.320 --> 06:01.210
and then to r3 and then to r1 and r2 and then it went to r4 as shown right

128
06:01.210 --> 06:02.320
there and if we scrolled

129
06:02.320 --> 06:06.280
down a little bit it hit r6 as shown right there and because that traffic didn

130
06:06.280 --> 06:07.760
't match the policy didn't

131
06:07.760 --> 06:11.820
match the ACL as part of the route map that was used for the local policy the

132
06:11.820 --> 06:12.720
policy was rejected

133
06:12.720 --> 06:16.140
meaning it just forwarded based on its normal routing table so thanks for

134
06:16.140 --> 06:17.040
joining me in this set

135
06:17.040 --> 06:19.840
of videos regarding policy based routing and I look forward to seeing you my

136
06:19.840 --> 06:20.720
friend in another set

137
06:20.720 --> 06:25.870
of videos very very soon until then I hope this has been informative and I'd

138
06:25.870 --> 06:26.960
like to thank you