On switch one at the moment show IP route shows us that we've learned one IP route so DX being IP in
the routing table, but we haven't got a gateway of last resort set.
On switch to show IP route gateway of last resort is not set.
We're learning about one route through ISP, the loopback of router three, but no other routes are
being learnt.
This is the configuration on router three.
So router erp 100.
We advertising the loopback and enabling ERP on the first ethernet interface and we've disabled automatic
summarization, but nothing else is being configured at the moment.
No gateway of last resort is configured.
Show IP interface.
Brief.
We're having a problem with the IP address on this interface which was allocated previously through
DHCP.
So I'll shut the interface down and then no, shut it.
But while we're waiting for that.
I'll configure a static default route on this router to what I know is the default gateway on the cloud.
So I'm going to configure a default route on this router to point to my internet facing router here
at home.
When this interface comes up, we should have a default route show in the routing table.
Now.
Instead of waiting for that, I'll configure the address manually.
So 192168124 is an example.
Make sure the interface is no shut.
Show IP rot.
So.
Writer three now has a gateway of last resort being 1921681254.
And the static route is appearing in the routing table.
Ping that router.
And I'm having a problem with the cloud, but I'll resolve that later.
For now, I just want to advertise the default route through air GOP.
So rather air GOP 100.
And I'm going to type, redistribute, redistribute allows me to take a route from one routing protocol
and advertise it in another.
So I'm going to redistribute, in this case, a static route, the static default route.
And I need to create what's called a seed metric or beginning metric to bring it into ERP.
So I'm going to specify a bandwidth value of 10,000.
A delay value of 100, a reliability of 255 where 255 is 100% reliable, a load of one which means no
load and a MTU of 500.
You just need to specify some kind of value so that you can bring that route into ERP.
So on switch to.
Previously we didn't have a gateway of last resort, but now we do.
So the default route is being advertised into ERP.
So in other words, on router three, we have a static default route pointing to my internet facing
router in the cloud that's being redistributed into ERP and being advertised to switch to and to switch
one.
So on switch one.
Previously, once again, no gateway of last resort and no default route shown in the routing table.
But notice now we do have a gateway of last resort and we have a static route advertised through IRP
X means external ERP route.
In other words, it was advertised from another writing protocol.
Notice this route has a administrative distance or believability factor of 90 because we advertise that
into ERP using the network command on router three.
But the aesthetic default route has an administrative distance of 170.
In other words, it's much less believable than the route that came directly into ERP through the network
command.
Once again, we can see that on switch to measure of distance for the static route there was advertised
into ERP is 170 administrative distance of the route that was brought directly into ERP has administrative
distance of 90.
Show IP protocols shows me what the default administrative distances are in IRP.
So at the moment we've enabled ERP on these two switches.
We've created a static default route on router three and advertised that into ERP.
In the next video, I'm going to troubleshoot the cloud.
If you're not interested in seeing that, then skip ahead.
But I'd like to get my cloud working so that we can configure Nat in a later video.
In this video, I'm going to troubleshoot an issue with the cloud in three.
This is not a CCAR specific topic, so if you're not interested, then skip ahead.
But at the moment, Rada three has an IP address configured on Fost Ethernet zero one, the interface
of 1921681 124.
My local PC that Ginny three is running on has an IP address of 1921681199 in that subnet.
So ping one on 21681 124.
That's not working, but I can ping my default gateway on the Windows PC, so I'll configure this cloud.
At the moment it's being connected to the local area connection, which is the correct interface to
use on my PC.
So what I'll simply do is delete the cloud.
And then create another cloud.
So drag a cloud across.
Or configure the cloud should be using the local area connection.
Click.
Okay.
I'll connect Foster Ethernet zero one to the cloud and.
Hopefully now my PC can ping rather three, which it's able to do.
And hopefully rather three can now ping one on 21681254, which is the local internet facing router
in the cloud, which it can.
So I've successfully resolved the issue in Genesis three.
This router can now ping the internet facing router.