So here are the lab tasks. So let's go to the lab environment and let's set it
up.
So I have reset my lab so it's back to square one. Let me go ahead and open up
the topology by
double clicking here on the desktop. Fantastic. And let's go to server one and
open it up by
selecting it and double clicking and give that a moment to initialize. Here it
comes. Great, great,
great. So just as a test, let's go down to PC7 right here. And let's just do a
trace to the
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
loop back address in our six. Just to verify it takes the normal path. So what
I expect based on
the routing that's currently in place is PC7 would forward to its default
gateway are seven,
who would send it to our five, who would send it to our three, then to our one,
etc.
And it wouldn't go straight over on the serial link because the 1070 zero
network is not
included as part of OSPF. So let's go to PC7 and we'll click on the right tab
for that. Super,
super. It's IP address is 10.1.7.10 and let's do first a ping over to the loop
back on our six.
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
Just to verify basic connectivity and that is working and then we'll do a trace
. We'll do the
trace over to six. Six. Six. Six. Six. Six. And survey says there's our path
and by default it's
using UDP hence the port unreachable at the final destination. But if we go
ahead and do a trace
and say dash capital P and protocol one that'll use ICMP and that'll avoid that
last destination
port unreachable message. All right, so there's our path to our seven, then our
five, and then our three,
and then our one, two, and four, and then finally to our six. So let's go to
our seven and let's see
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
what we have in the way of access control lists show access lists and nothing
there show route map.
And that's because I reset the lab fantastic. So let's go ahead and do
configuration mode. Let's
create access control list to identify the traffic that we want to policy base
route. So let's go
ahead and use access list, how about one, two, three, and then we'll print and
the lab didn't ask for any
specific protocols. So let's say IP and let's take a look at the lab tasks one
more time. And we've got
a source to traffic from 10.1.7 anything. That's this network down here going
to the loopback address of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to the loopback address of
6666 over here on r6. So for the source address will specify 10.1.7.0 and then
for wildcard bits we'll
say we want to match on the first octet and the second octet and the third oct
et. But we don't care
about the fourth octet. So we'll put wildcard bits there space. So that's the
source and the destination
is the specific IP address of 6666 and we are done. So there's our access
control list. Then let's
create a route map. So route map space is called PBR and let's go ahead and
make sequence number 10.
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
So permit 10 and in this route map entry of sequence 10 we want to match on the
IP address
specified in access list 1 2 3 including the source and destination there.
Fantastic. And if that
happens we're going to set the IP next top to the IP address and let's take a
look at our topology
for a moment to 10.78.0.8. And that way our 7 will pulse you base route that
directly over to r8
instead of sending it up to r5 etc. So let's go ahead and put that IP address
in of r8 which is 10.78.0.8 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in of r8 which is 10.78.0.8
and then we'll go ahead and apply this to interface let's take a look at our
topology. We'll apply this
to interface gig 0 0 on our 7 that way traffic from PC 7 as it goes into router
7 can be policy
base routed. So we'll go into interface gig 0 slash 0 and we'll use command IP
policy the keyword
route map and then the name of our policy which is PBR so I'll go ahead and
copy paste that in
and press enter. And now let's go ahead and test from PC 7 where just a moment
ago I was taking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ago I was taking
that full path. This is the up arrow key press enter and that should be going
directly over to
r8 which it is because of the policy base routing. Fantastic so what about
traffic being sourced from
our 7 itself. So here are 7 if we'd have been paying space let's do a trace.
Let's do a trace to
6.6.6.6 and let's source it from our interface let's go ahead and look at the
topology. Let's
source it from our gig 0 0 so we'll put gig 0 0 there press enter. Notice this
traffic is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
from r7 to r5 as shown right there and then up to r3 and then to r1 and r2 and
r4. So this traffic
is not being policy based routed but in the lab tasks it asks us to also
include traffic source from
r7 from this gig 0 0 interface address which implies we need to do local policy
based routing so
currently if we do a show IP policy press enter currently we only have gig 0 0
and ingress traffic
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
coming in there from other devices based on this route map called pbr. So what
we could do is go
into configuration mode say you know what in addition to ingress traffic coming
on the interface
let's also specify any traffic use source is also going to be considered for
policy based routing
and to do that we're going to do the command IP local policy and then route map
and then
then in a route map which is pbr and press enter and now if we do the command
show IP policy
we're now doing traffic coming in on gig 0 0 which we like traffic coming in
from pc7 and we also have
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
local pbr also set up that's for traffic source by the route or so now if we
hit the up here a few
times and we do a trace route to 6666 sourcing it from gig 0 0 which is our 10.
1.7.7 address and press enter
now it should also be routed as shown right here so the traffic from r7 with
policy based routed
over to r8 and then r8 forwarded up to r6 and if we did a debug IP policy and
did that same trace again
we could verify with the output here that is being policy routed as shown in
these entries
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
or right here and if we did the trace without specifying a source address what
that's going to do
is going to basically cause r7 to use the interface from its routing table
closest to the destination
so the egress interface would be gig 2 0 and the source address would be 10.1.
57.7 so we did the
trace without specifying the source of gig 0 0 it's going to be routed as
normal and let me turn off
debugging and then we'll look at the output here so we'll drop debugging the
path went from r7 to r5
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
and then to r3 and then to r1 and r2 and then it went to r4 as shown right
there and if we scrolled
down a little bit it hit r6 as shown right there and because that traffic didn
't match the policy didn't
match the ACL as part of the route map that was used for the local policy the
policy was rejected
meaning it just forwarded based on its normal routing table so thanks for
joining me in this set
of videos regarding policy based routing and I look forward to seeing you my
friend in another set
of videos very very soon until then I hope this has been informative and I'd
like to thank you