Original subtitles

This is a packet tracer campus network topology that we're going to use in multiple videos in this course.

This topology gives us a nice basis to learn many of the technologies found in the CCMA exam.

This is a campus network consisting of two core switches and three access switches.

Even though this topology is quite small.

Imagine that you have many access switches in this topology configuring more than three axis switches

is redundant and will simply take up time rather than you learning new things so I've limited the topology

to three access switches.

We've also got three pieces in the topology one connected to each axis switch as well as a server connected

to one of the core switches.

We have an Internet router that will configure to connect the campus network to the Internet on the

Internet.

We have a Google DNS server.

8 8 8 8 8 8 and a Cisco dot com server in the real world.

If I'm paying Google dot com that DNS name needs to be resolved by a DNS server.

In my example I'm using 8 2 2 8 8 8 8 8 8 8 as my DNS server.

So that is a Google DNS server and we'll replicate that in our packet tracer network.

Now there's a lot to do and hence we going to split up the configuration of this topology into multiple

videos.

You'll firstly need to power up the switches.

You'll have to configure basics such as host names IP addresses usernames and passwords and into VLAN

routing on the call switches.

As this is a layer to topology you're going to need to configure the links between the switches as trunk

ports and the ports to the pieces as access ports.

The pieces in this network are in different villains.

P.S. One is in VLAN 10.

P.S. 2 is in VLAN 20.

And P.S. 3 is in VLAN 40 so you'll need to configure these ports on the access switches with the relevant

v glands.

You'll also need to configure the server in vlan 100 on this course switch.

In addition because this is a layer to topology spanning tree is going to be used spanning tree runs

by default on Cisco switches but it's not optimized.

You will need to optimize the spanning tree in this network.

You going to configure the switch on the left as the route switch for some villains and the switch on

the right as the route switch for other villains in the real world on your access switches as you may

have devices in multiple villains so as an example you may have IP phones as well as pieces in your

topology and you're going to want to send some traffic to the call using this uplink and other traffic

to the core using this uplink.

So we're going to want to optimize spanning tree for load sharing but also to ensure that we are not

blocking links that can negatively affect the throughput through our network.

As an example if access switch too became the route it would mess up the forwarding of traffic through

the network.

So we need to optimize our spending tree to make sure that the course switches all the route switches

and that we load share traffic across them.

We also are going to want to make sure that these two links in the core are configured to use ether

channel so that both are forwarding rather than having one of the ports blocking.

We need to configure the call switches for interview land routing so they're going to need multiple

switched virtual interfaces configured.

They're going to have to be configured with writing protocols such as EAI GOP so that they can exchange

routes with the ISIL router.

The ISIL rider needs to be configured with basic configurations but it also needs to be configured with

EAI GOP and net or network address translation to ensure that these devices in our network can get to

the Internet now one of the things to think about when you have multiple course switches is which switch

becomes the default gateway for your pieces after the access layer.

We want multiple call switches for redundancy and full load sharing traffic across uplinks but which

switch will be the default gateway for this P.C. if we configured the switch as the default gateway

and that switch went down.

P.S. One wouldn't be able to send traffic to other villains.

So what we gonna want to do in the Corps is enable protocols such as H.S. IP or hot standby running

protocol.

So we need to configure H.S. or p on our core network.

That means that rather than P.S. One P.S. two and P.S. three using one of the switches in the call as

the default gateway they point to the virtual H.S. IP router if one of the course switches goes down.

It's not a problem because traffic can be intervened and routed by the remaining core router however

whenever you enable H.S. IP and you using it.

In addition to spanning tree you're going to want to optimize the link between spanning tree and H.S.

IP.

In other words if so which one is the H.S. or P primary Rada or monster rider for VLAN 10 you're going

to want it to be the spending tree root for VLAN 10.

In other words you don't want a mismatch between your spending tree roots and your HS or P primary routers

or active routers if he's the HS or P active Rata for VLAN 10 he needs to be the root for VLAN 10 if

the switches the HSR P active router for VLAN 20 it needs to be the root for VLAN 20 so as you can see

there's a lot to do we going to configure some of the basics initially and then as we continue we'll

configure more and more to get this network fully working.

I'm hoping that this gives you a practical real world example of how to configure networks but in addition

I'm confident that It'll prepare you well for the CCMA exam so try and do the labs yourself.

Download the packet tracer files and see if you can complete the list of tasks yourself.

If you struggle or if you'd like to learn some additional tips and tricks watch my videos where I can

figure the devices.

Per the requirements given to us so let's get started configuring the campus network.