This video I'm going to discuss of raftered ports on ethernet switches in this ingenious Threet apology.
I have to Iowas V layer two switches and an Iowas of the router.
The devices have no configuration.
So they've just booted up and bypassed the initial configuration dialog on the router.
And let's start by configuring host names on the switches
and I'll configure a hostname on the router so no configuration has been done on these devices at all.
They're using the default configuration and I've simply changed the hostname.
So show CGP neighbors on switch one shows me that switch to is available on the gigabit 00 interface
CD was advertising switch to with the name switch until I changed it on switched to shoyu CTP neighbor.
We can see switch one connected to Gigabit 00.
We don't see the router on gigabit to 0 1 because a rod as interfaces are shut down by default show
interface gigabit 00 switch port.
Here's the command.
We can see that the interface is enabled as a switch port.
It's using dynamic orda DTP mode or dynamic trunking protocol mode the villain that the port belongs
to is villaine one because it wasn't able to negotiate trunking with switch to.
There are no trunk's configured on the switch.
So show interface kickabout to 0 0 such port we can see that it's a static access port negotiation of
trunking is enabled but it hasn't negotiated trunking with the other side.
The interface belongs to the land one on switch two.
We would see something similar.
So show interface gigabit 00 switch port.
The interface is enabled as a switch port using dynamic Warda mode.
So when we look at the villans at the moment only the land one and the other default villans are configured
on the switches.
We're not going to worry about FDDI and Token Ring in these videos.
What I could do is create a switch to a virtual interface is vi you do that by using the interface movieland
command we can see that the interface has gone down.
But what I could do is configure an IP address on this interface and then shut it.
I could then also do something similar create an ace VI or switch to a virtual interface for a villain
one
and give the switch an IP address and no shut the VI interfaces come up on both sides.
So we should be able to ping switch to from switch one there's the ping again and we should be able
to ping switch one from switch to.
So the physical interface is a layer to interface gigabit to 00 is enabled as a switch port interface.
It's a layer to interface it supports protocols such as spanning tree.
Notice this port is the root port on switch 2 and it's forwarding show spending tree here shows that
gigabit 00 is the designated port on the switch and it's also forwarding protocols such as DTP and spending
tree run across switch ports all lead to ports.
But what I could do as an example on switch to is make the port a routed port by using the command no
switch port interfaces come up and now when we tap the show interface gigabit 00 switch port.
Notice we told that the switch port has disabled Whereas on this side it's still enabled as a switch
port and we can see the access feelin that the port belongs to.
We'll also be able to see whether it becomes a trunk.
But that's not true on the rodded port.
Another difference between a rodded port and a switch port is you can configure an IP address directly
on the interface.
Do show run interface gigabit 00.
Notice it's disabled as a switch port and an IP address has been configured directly on the interface.
Whereas if I tried that here and try and configure an IP address it's not recognized.
So at this point all just change that IP address to make it consistent.
Because this is switch to.
But notice the IP address command is not available on this side because it's currently a switch port.
But if I type a no switch port and then IP address notice I can configure the IP address on the interface
to show interface gigabit 00 or switch port it is disabled as a switch port.
But I can pain switch to through that interface.
So shows spending tree notice spending tree is not enabled on gigabit 00 previously gigabit 00 was a
designated port.
But now it's not shown in the output because spending tree and dynamic trunk protocol do not run on
rodded ports.
Gigabit 00 does also not appear on the side show run interface but 00.
Shows us that an IP address is configured on the interface.
If I enable this port is a switch port and look at the running config of that interface again.
Notice the IP address has been removed and spending tree is running on that interface.
Once again its interface but 00 no switch port IP address 10 1 to 2
shows spending tree spending tree is not running on gigabit 00 I should be able to ping switch one.
So show IP interface brief shows us that the interface has an IP address configured on it whereas this
interface is a layer to interface and the FBI will switch to a virtual interface is used as the layer
3 interface so Chauvelin brief notice can give it a 00 is not in the list of interfaces that belonged
to villaine one this interface.
Gigabit 0 1 is a layer to interface and belongs to the land one and has as it's a layer 3 IP address.
So basically when you type no switch port you're turning that interface into a routed interface so it
acts like a router.
So gigabit is 0 1 now.
Just configure it as a routed interface and on a router we would do something very similar.
No shut the interface and configure an IP address directly on the interface and we should be able to
ping switch to true that routed interface which we can.
We could also enable a writing protocol.
So Ali Nabl your job on all interfaces could do the same here router here job p 1 and enable your job
pian all interfaces show IP your job interfaces its enabled and all interfaces and the neighbor relationship
has been established.
Show IP your GOP neighbor the neighbor relationship is established on the gigabit 01 interface not on
the VI but once again if we changed gigabit 00 to a switch port and then enabled your GOP on this side.
Notice the difference in the neighbor relationships.
So show IPY GOP neighbor no neighbor relationship is established because I need to make this a switch
port to put them back in the same subnet.
So let's check Ping's can wrote it to ping Rotto one at the moment it Koncz and that's probably because
of spending tree.
Notice that port is learning.
So we've got to wait for spending tree to converge before the GOP can form a neighbor relationship.
Rodded ports however don't use spending tree so they will converge quicker than a spending tree portable.
So the convergence has just taken place.
Your GOP neighbor relationship is established.
So show me your job.
He never noticed the difference.
The snakebit which is switch 1 has been learnt on line 1 whereas the router has been learnt on the gigabit
zero or one interface to show run interface gigabit to 0 0 and 0 1.
Notice the difference switch port is enabled on gigabit 00 no switch port has been configured on gigabit.
0 1 when be paying from switch to switch one.
We using the VI interface but when we paying from switch to two Rotto one way using the physical interface.
So router ports are typically used between switches and routers for example where a router connects
you to the Internet switched of virtual interfaces and switch port interfaces are typically used in
a campus environment where you need to tag multiple villans across an interface a routed port doesn't
have the concept of villans they are no villans you don't run spending tree and you don't run DTP or
Dometic trunk protocol.
The port is a routed port in the same way that you configure a routed port on a router.
So again show IP your GOP neighbor.
Notice the difference in how the neighbor relationships are formed.
I hope you found this video useful if it's been of benefit to you.
Please like it please subscribe to my YouTube channel.
I wish you all the very best.