Okay, so at the switch 2, show VLAN shows us that we only have the default VLANs so interface gigabit
01.
No shut, switch port mode trunk.
Make it a trunk port and I'll save VTP mode client to make it a client, so show VTP status.
It's a client as we can see over here hasn't learned the VLANs yet, show VLAN,
we still need to learn the remaining VLANs.
We can see the interface is still orange.
just gone green now, so hopefully it'll learn the VLANs
while we're waiting let's confirm our configuration.
This port is a trunk port,
it's a good idea to check what you've done on your other switches that are working to confirm that you've
done something similar.
Notice that's all we did on switch 1 and that's all we need to do on switch 2, so show VLAN brief,
show VTP status still hasn't learnt the domain as an example.
So I'll say VTP domain CCNA, shouldn't have to do that it should automatically learn that
but notice now that I've done that the number of existing VLANs has increased, show VLAN brief
there are the VLANs.
So that's something in Packet Tracer you shouldn't have to do that in the real world but with Packet
Tracer you may need to set your VTP domain and set it to a client.
Okay,
so that configuration is being done.
So interface f 0/1 switch port mode, access switch port, access VLAN, in this case, will be 20.
We need to configure the IP address on the switch which is 10 112 for this specific switch
per the instructions over here, no shut
that SVI, it's now come up IP
default gateway will be 10 112 54 which is the core switch.
So can we ping the core switch in our topology?
Yes, we can.
Can we ping switch 1? Yes, we can.
Just took a bit longer there but there we go we can ping switch 1.
So at this point, it looks like switch 2 is configured show interface f 0/1 switch port,
F 0/1 is configured as a access port, is operating as an access port it's configured in VLAN 20
so that looks good. So last switch is switch 3, I'll use different access switches in other labs to get
round this issue with the fonts but hopefully, you can kind of see what I'm doing here.
Interface gigabit 01, switch port mode trunk, interfaces come up now
show VTP status, VALNs haven't been learnt yet
so what I'll do now is wait for this interface to go green and then let's see if packet tracer updates
correctly.
Okay, so the link has gone green, show VTP status still a server, domain name hasn't been learned.
So what I'll do is make it a client.
Let's see if it's learned that now, still not learned that, so VTP domain CCNA
VTP status now shows us that the VLANs have been updated, show VLAN brief notice there are the VLANs
that we've learnt from the core switch. So interface f 0/1 switch port mode, access switch
port access VLAN 30. So for the real world, you need to be careful switches can dynamically learn the
VTP domains and other information from other switches and automatically synchronize their databases.
So let's see what we've done we've configured this interface as a access port in VLAN 30, scrolling
down this interface is configured as a trunk, we now need to configure interface VLAN 1 with an IP address
of 10 113 for the switch slash 24 subnet mask. So can it ping the core switch? Yes it can. Can it ping
switch 1? Yes it can. Can it ping switch 2?
Yes it can.
One thing I need to do is configure a default gateway, which is the core switch. So can it ping 10.1.
10.254 the IP address of the course switch in other VLANs? Yes, it can.
So that looks good, I'll save the config let's confirm that we can on switch 2 that works.
So everything on switch to looks good
and on switch 1, can we ping other VLANs on the core switch?
Yes, we can.
So I think our switches are now configured, let's configure the PCs and make sure that they can ping
each other. So on PC 1, we are going to configure the switch with a default gateway of the core switch.
I'll set the DNS server to the core switch as well on the interface.
I'm gonna configure it with an IP address of 10.1.10.10 per our instructions
here the mask is gonna be 255 255 255 0.
So on the desktop, IP config shows us our IP address and default gateway, Can we ping the default gateway?
Yes, we can.
Can we ping other IP addresses on the default gateway?
Yes, we can.
Can we ping switch 1?
Yes, we can.
What you'll notice is that traffic goes via the core switch to get to switch 1 and to switch 2
and to switch 3.
So
PC 1 is correctly configured, let's configure PC 2, so config default gateway will be 10.
1.20.254.
I'll do the same for the DNS server, IP address here will be 10.1.20.20/
24 subnet mask
that's correct per our instructions.
So on the desktop
open up a command prompt, IP config
IP address looks good,
default gateway looks good.
Can we ping PC1?
Yes, we can.
So that proves that inter VLAN routing is working and we can ping switch 2, PC 3 do something similar
default gateway will be 10.1.30.254/24 subnet mask, IP address will be
10.1.30.30/24 subnet mask, that's correct per instructions
so open up a command prompt IP config that looks good. Can we ping PC 1? Yes, we can.
Can we ping PC 2?
Yes, we can.
Can we ping switch 1 as an example?
Yes, we can. Switch 2, switch 3
we have full connectivity between our PCs and switches so the last device to configure is the server.
Gateway here will be 10.1.100 254/24 mask, IP address will be 10.
1.100.100/24 mask.
DNS server will be the same IP address, so go to command prompt on the server IP config that looks good.
Can we ping PC 1? Yes, we can.
PC 2, PC 3, so that looks great.
So as one last test, can PC 1 ping the server?
Yes, it can.
Can PC 2 ping the server?
Yes, it can. Can PC 3 ping the server?
Yes, it can.
So we've successfully configured this network and verified connectivity.
We should as an example save our device configurations.
So in each switch, I'll simply save the config to make sure that it's being done.
Okay so how did you do?
Were you able to configure this network?
Were you able to get everything working? Quite a bit
had to be done on this network to get things working.