The first thing I'm going to do is configure the switches with their names and configure the interfaces
as trunks or access ports.
That means we need to configure the VLANs on the switches as well as configure the HTTP mode.
This is the console for switch one.
So in other words, eos v WL two, hyphen one as you can see here on the console.
I'm going to type enable to go to privilege mode top T to go to global configuration mode and then type
hostname.
And I can specify the name of the switch.
I'm going to configure it as one do, allows me to see show commands in global config mode as an example.
So I'm going to use the command do show IP interface brief.
To view interfaces on the switch so I can see various interfaces such as gigabit zero zero, gigabit
zero one and so forth, which have a status of up up at the moment.
In this topology, I'm only using gigabit 002 gigabit zero three as well as gigabit 1/0.
So these are the interfaces that I'm using.
As a best practice.
I'm going to shut down any other interfaces on the switch.
So I'm going to shut down gigabit 1/1.
Two, three.
My interfaces have gone down, so do show.
IP interface brief shows me that those interfaces are currently down.
I should also shut down to slash zero.
Two, three.
As well as three 0 to 3.
So do show IP interface brief.
Shows me that those interfaces are shut down.
Now you probably want to script this kind of configuration.
So on the other switches, I'll do most of the configuration through notepad and then simply paste it
into the switch consoles to speed things up.
But what we've done at this point is shut down unused interfaces and we've named the switch.
The Range Command is really useful when doing configurations on multiple interfaces.
By default we have a VLAN one configured as well as a legacy VLANs such as 1002, three, four and five,
which were used in the past for FDI in token ring.
VLAN one is the only VLAN used in an ethernet environment.
In this topology, however, I need to configure VLAN ten as well as VLAN 20.
Now before I configure the VLANs, I'm going to change the HTTP mode to transparent so that every switch
uses its own local database of VLANs.
By default, the HTTP mode is set to server and we can see that by using the command show.
HTTP status servers allow you to create a VLANs and they also synchronize with other switches in the
topology.
I don't want to do that, so I'm going to type HTTP mode.
Transparent so that my switch does not try and synchronize with other switches in the topology.
In a small environment like this, we don't really need VP and VP can cause a lot of problems in networks.
So for safety reasons, I'm going to disable HTTP and the command show HTTP status allows me to see
that the mode is now changed to transparent.
The number of existing VLANs is five.
The maximum number of VLAN supported in the switch is 1005.
We can see the current VLANs by tapping show VLANs once again and as you can see we have VLAN one 1000,
two, three, four and five as the five VLANs currently configured.
So VDP status shows me that the switch supports HTTP modes 1 to 3.
The current version running is http one.
The switch is not part of a HTTP domain.
We can also see that VP pruning and VTB trapped generations are disabled so show vlan brief.
Shows me that I have vlan one configured and all of these ports are in VLAN one.
VLAN one is the default ethernet vlan once again and all interfaces are by default in vlan one.
So conti vlan ten vlan 20 and show vlan brief.
Now you can see that.
VLAN ten and VLAN 20 have been created and added to the list of VLANs currently available on the switch.
For a port to be put into a VLAN, the VLAN needs to be added to the VLAN database.
So if I was going to put this MPM server into VLAN 30 as an example, I would need to configure VLAN
30 and then add that port to VLAN 30.
In this example, I want to configure VLAN ten and VLAN 20 because I'm going to create a Layer three
interfaces on the switch for those VLANs.
So I need to have configured the VLANs in the VLAN database first.