He has the switch
sprouted up before I configure the switch on no shot interface f0/0 so that that interface comes up,
you can see it's come up on the switch.
Now you may want to do your configuration in a specific order.
It doesn't really matter if things don't work, shut down ports and re-enable them, for instance,
on the connections to the IP phones to ensure things work properly.
Once you finished your configuration.
Now interface gigabit 101 needs to be configured as a trunk port.
So switch port trunk.
Encapsulation dot one Q switch port mode.
Trunk.
That looks good.
I need to configure my vlans so vlan 100 can give it a name such as data.
You may want to be consistent with the names that you're using on your DHCP pools, but that doesn't
really matter.
So show VLAN brief here we've got.
Data VLAN and voice VLAN configured, but currently all ports on the switch are in VLAN one.
Before I configure the porch to the PCs and phones, I'll configure the switch with its management IP
address.
Management.
IP address needs to be ten 11253.
Default gateway needs to be the router.
No shut to that IP default gateway ten 11254 router needs to be configured so that my switch can get
to remote subnets.
Let's see if the switch camping the router.
Yes, it can.
So that's good.
Now, Cisco, IP phones use CDP or LDAP for communication with the switch.
The phones need to learn which VLAN they belong to.
So in other words, they need the switch to run CDP so that they can query the switch about which VLAN
they belong to.
So we need to enable CDP on the switch.
So that the switch can tell the phones which VLANs they belong to.
After the moment, we don't see any CDP neighbors.
That may take a while.
So while we're waiting for that, let's configure the ports on the switch.
So interface range one zero 2 to 4.
I'm going to configure this port, this port and this port at the same time.
Switchboard mode is access.
These are access ports, but we're going to configure both a data VLAN and a voice VLAN on those ports.
So show run on the switch.
We've got a trunk on this port to the router and then we've enabled.
The voice VLAN and the data VLAN on those ports.
Now, this is a bit of an interesting command on a Cisco switch.
It says it's an access port.
But if we look at that port by using the command show interface, interface number, switch port.
What you'll notice is this port is configured and is operational as a static access port, but it's
allowing both a untagged and tagged a VLAN across it.
So it's a special type.
Of Access port that also accepts tagged frames from phones.
So two VLANs are allowed across that port.
This is not like a standard access port.
Just a bit of history.
In the very, very old days, you used to configure ports to phones as trunk ports.
But it caused issues with broadcasts.
So Cisco changed the way that the trunk ports were configured.
And we have the special type of access port that's kind of an access port, but it's also kind of a
trunk port.
It's essentially a trunk port that's pruned to only allow those two VLANs.
VLAN 100 and VLAN 101.
So it's kind of like an access or a pruning trunk port, if that makes any sense.
Show CDP neighbor.
We can see IP phones connected.
To the ports.
On the switch show.
Power in line.
Just do that.
Come on again.
Show power in line.
Scrolling up.
There's a command.
These three phones are drawing ten watts of power.
So one of the questions we need to answer is verify phone power usage.
We can see that the phones are each drawing ten watts of power.
That's the power used on the switch.
But more is available.
Okay.
So we've configured the switch and the rudder.
With basic configuration.
Let's see if IP addresses are being released to clients.
At the moment we're not seeing any DHCP bindings.
Let's confirm that we've done things right.
I made a mistake in this command, so let's remove that command.
That should be.
IP DHCP excluded range 101 200 to 101 254.
So let's have a look at that again.
That looks better.
Show IP DHCP binding.
Still don't have any bindings or let's verify the other configuration on the router.
So that looks good.
That looks good.
Show CDP neighbor.
Well, enable CDP on the rota.
Hopefully we should learn about the switch.
Still not receiving any DHCP requests.
So lets go back onto the switch and what I'll do is shut the ports down and bring them up again to make
sure that the phones request IP addresses.
So interface range gigabit 10224.
Shut those ports down and no shut to them.
And while we're waiting for spending tree to converge, let's look at the pieces they need to be configured
for DHCP.
So hopefully they'll get IP addresses once spending tree has converged.
Set the pieces to use dhcp.
Do that here.
So on PC three, IP config, IP config.
And notice it got an IP address.
So it should hopefully be able to ping the router, which it can.
Under this PC, it still doesn't have an IP address.
So let's do a renew to force it to request an IP address from the DHCP server.
It's now been given one and it can ping the rotter.
What about this PC IP config?
No IP address for it to get an IP address using a renew.
It's got an IP address and can ping the router.
Back on the router.
Show IP DHCP bindings.
We can see that the PCs have requested IP addresses.
The phones haven't to this point.
So let's configure the telephony service while we wait.
And see if the phones request IP addresses.
Sometimes packet tracer doesn't work precisely like a real device.