So to help reinforce what we've discussed in this set of videos and help
improve your skills,
here's a hands-on lab for you to practice with policy-based routing.
And on R7, I'd like you to go ahead and set up policy-based routing so that
traffic sourced
from 10.1.7 anything going to the R6 loopback address, which is 6.6.6.6 over
here.
I want that traffic flow to go ahead and use R8 as the next top. So R8's serial
3-slash-2
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
interfaces 10.78.0.8 you can also go over to R8 and verify that IP address.
So because the 10.1.7 network is over here we want to apply that policy to the
gig 0.0 interface
that would identify incoming traffic, see if it's matched, then if it is,
to policy-based routing over to R8. Who would then, once he gets the packet,
use its routing table to forward traffic up to R6 and its loopback.
But in addition, I'd also like you to include traffic sourced from R7 itself
from its gig 0.0.0
interface, which implies not only a policy being applied to this interface for
incoming traffic,
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
but also setting up local policy-based routing as well. So if R7 does a ping to
6.6.6.6,
sourcing it from its interface gig 0.0 address, I also want that to be policy-
based routed over.
So those are my friend, your lab tasks. Have some fun in this hands-on lab for
policy-based
routing and then when you are done, join me in the next video and we'll do a
walk-through of these
lab tasks together.