VLAN, Trunk and 802.1q Router Configuration Objectives  Initial Configuration  VLAN Trunking Configuration  802.1q Router/Switch trunking Topology  You can click the Show Lab Content button to download the lab or you can download the l ab from [email protected] in Content. VLAN, Trunk and 802.1q Router Configuration Step 1: Initial Switch Configuration  Configure hostnames on the switches  Configure enable secret, console and vty (Telnet) passwords as uwstout  Configure VLANs 10, 20 and 30 on StoutSW1 and StoutSW2  Configure the ports the PCs are connected to in the proper vlans  Shutdown the fa0/4 interfaces on each switch  Configure an IEEE 802.1Q trunk between StoutSW1 and StoutSW2 using the fa0/1 interfaces  Configure the IP addresses and subnet masks on PC1a, PC1b and PC2 according to the topology diagram  Verify your configuration before moving on to Step 2 If you need help remembering the commands for the initial configuration steps, try using ? or refer to the previous labs. Before moving to Step 2 verify your trunk and VLAN configuration, PC IP addresses and that the switchports for the PCs are in the correct vlans. Use “show” commands and ipconfig to verify the initial configuration. VLAN, Trunk and 802.1q Router Configuration Step 2: Configure 802.1 trunk between Menomonie and StoutSW1 Data from one vlan cannot cross into another vlan without the help of a router to route the data. Currently the PCs cannot successfully send to each other because they are on different VLANs. In this step you will configure a trunk between the Menomonie router and the StoutSW1 switch. (This type of configuration is referred to as “Router-on-a-Stick”) so the router can be used to route traffic between the VLANs. The physical interface on the router that is connected to StoutSW1 is fastethernet0/1 so you will configure the trunked sub-interfaces on the fastethernet0/1 interface. Then configure fastethernet0/8 on StoutSW1 to trunk. Configure the Router: Configure the hostname on the router to Menomonie:  In global configuration mode type, hostname Menomonie Configure the first sub-interface on Menomonie to route vlan 10  In global configuration mode type, interface fastethernet0/1.10  In interface configuration mode for fa0/1.10 type, encapsulation dot1q 10 Configure the second sub-interface on Menomonie to route vlan 20  In global configuration mode type, interface fastethernet0/1.20  In interface configuration mode for fa0/1.20 type, encapsulation dot1q 20 Configure the third sub-interface on Menomonie to route vlan 30  In global configuration mode type, interface fastethernet0/1.30  In interface configuration mode for fa0/1.30 type, encapsulation dot1q 30 Now that the virtual trunked interfaces have been configured you can assign an IP address to the interfaces. The addresses for each inter ...

1. VLAN, Trunk and 802.1q Router Configuration
Objectives
Topology
lab or you can download the l ab from
[email protected] in Content.
VLAN, Trunk and 802.1q Router Configuration
Step 1: Initial Switch Configuration

2. ches
as uwstout
vlans
StoutSW2 using the fa0/1 interfaces
and PC2 according to the topology
diagram
If you need help remembering the commands for the initial
configuration steps, try using ? or refer to the
previous labs.
Before moving to Step 2 verify your trunk and VLAN
configuration, PC IP addresses and that the switchports
for the PCs are in the correct vlans. Use “show” commands and
ipconfig to verify the initial configuration.

3. VLAN, Trunk and 802.1q Router Configuration
Step 2: Configure 802.1 trunk between Menomonie and
StoutSW1
Data from one vlan cannot cross into another vlan without the
help of a router to route the data. Currently
the PCs cannot successfully send to each other because they are
on different VLANs. In this step you will
configure a trunk between the Menomonie router and the
StoutSW1 switch. (This type of configuration is
referred to as “Router-on-a-Stick”) so the router can be used to
route traffic between the VLANs. The
physical interface on the router that is connected to StoutSW1 is
fastethernet0/1 so you will configure the
trunked sub-interfaces on the fastethernet0/1 interface. Then
configure fastethernet0/8 on StoutSW1 to trunk.
Configure the Router:
Configure the hostname on the router to Menomonie:

4. Configure the first sub-interface on Menomonie to route vlan 10
fastethernet0/1.10
encapsulation dot1q 10
Configure the second sub-interface on Menomonie to route vlan
20
fastethernet0/1.20
encapsulation dot1q 20
Configure the third sub-interface on Menomonie to route vlan
30
pe, interface
fastethernet0/1.30
encapsulation dot1q 30
Now that the virtual trunked interfaces have been configured
you can assign an IP address to the

5. interfaces. The addresses for each interface will be as follows,
with default subnet masks:
Fastethernet 0/1.10 : 192.168.10.1
Fastethernet 0/1.20 : 192.168.20.1
Fastethernet 0/1.30 : 192.168.30.1
on mode for fa0/1.10 type, ip
address 192.168.10.1 255.255.255.0
address 192.168.20.1 255.255.255.0
address 192.168.30.1 255.255.255.0
Configure StoutSW1:
VLAN, Trunk and 802.1q Router Configuration
The router is configured to trunk on the fastethernet0/1, now the
StoutSW1 port it connects to needs to be
configured to trunk in order to complete the link. Configure
fastethernet0/8 to trunk:

6. StoutSW1 type, switchport mode trunk
Step 3: Configure the Default Gateway on the PCs
In the initial configuration we are not using any routers to route
traffic on the network. In that configuration
the PCs are unable to communicate with each other because they
are in different VLANs and subnets. At
this point you have configured the router and switch so traffic
can pass to the router to be routed to the
other VLANs. The router is the default gateway, it is what is
being used when traffic needs to leave the
network from which it was sent. In this step you will configure
the PCs to use the router’s sub-interface IP
address as its default gateway, then verify you have
connectivity in the network.
Configure each PC with the proper default gateway.
PC1a default gateway 192.168.10.1
PC1b default gateway 192.168.20.1

7. PC2 default gateway 192.168.30.1
Verify network connectivity:
At this point your network is complete and you should be able
to communicate/ping to all PCs.
address, the pings should be successful.
VLAN, Trunk and 802.1q Router Configuration
Verify the router is being used to forward traffic between the
VLANs. You can use the tracert command on
the PCs to see the path the traffic is taking to get to its
destination. Review the path traffic is taking to get
from PC1a to PC1b, notice the first hop is the router sub-
interface and then it is forwarded to the PC.

8. Step 4: Saving the Configuration file to NVRAM
Now you need to save your configuration from RAM to
NVRAM using the command copy running-config
startup-config in Privileged Mode.
Now you need to save your configuration from RAM to
NVRAM. The configuration in RAM is called the running -
config,
the configuration in NVRAM is called startup-config. In order
to save our device configuration you need to copy from
RAM to NVRAM. Use the command: copy running-config
startup-config in Privileged Mode.
***Before completing a lab you must always issue this
command on each network device (router or switch) you have
configured. When you do that it saves the configuration you
did. When you issue the command once you have
completed the lab, that is the file I see as your final file
submitted. This is the configuration I will grade you on. You ca
n
issue the copy running-config startup-config command multiple
times while doing your lab (which is a good idea in
case you lose your internet connection or power), just be sure to

9. issue it one more time right before you have
completed the lab.
Static Routing
Objectives:
Topology
Enter Lab you will see the following:
to move around the topology.
lab or you can download the lab from
[email protected] in Content.

10. you will be configuring all of the
equipment in the topology
Static Routing
Step 1: Initial Router Configuration
Perform the initial router configurations on all routers. If you
have trouble recalling how to do each step
refer to the previous lab.
tnames according to the topology
all of the passwords to uwstout
according to the topology
CE interfaces to 128000
interfaces

11. Verify you have done the initial configuration correctly:
Before proceeding to the next step check that your interfaces
are up, once you have completed the initial
configuration on all routers all interfaces should be up. You
will use the show ip interfaces brief command
to see if your interfaces are up.
In user or privileged mode, type show ip interfaces brief and
press enter.
(It is okay that the BRI interfaces are down, we didn’t configure
them)

12. Notice that all of the interfaces configured show a status as up
and the protocol is up. At this point you are
ready to move to the next step. If your interfaces are not up you
will need to troubleshoot:
o Verify that you enabled the interfaces (no shutdown)
o Verify the IP address/subnet masks are correct—typos are
common
o Verify the clockrate and bandwidth on the DCE
o Make sure you configured the correct interfaces.
Static Routing
Step 2: Configuring the Static Routes
Now that you have completed the initial configuration you can
begin to configure routing. If you are not
using a Routing protocol to route the traffic you will use
administratively configure static routes to route
the traffic in your network. We will be configuring static routes
to route traffic in our network. When you
configure a static route you are simply writing a command that
says “if you want to send traffic to the
xxx.xxx.xxx.xxx network send it to the yyy.yyy.yyy.yyy
address” where yyy.yyy.yyy.yyy represents the
next hop address. You can also configure an outgoing interface
rather than a next hop address. Next
hop address is the prefer method for our use because it is a more

13. definite route—I can predict exactly
where my traffic will be going assuming that interface is up.
Configure the static routes on RemoteAZ:
Configure the static routes on RemoteAZ so traffic can get to
RemoteWI and Menomonie. Static routes
are only configured for networks that the router isn’t directly
connected to. Directly connect routes do not
need any routing, they are already in the routing table.
The form of the command is: ip route <destination prefix>
<prefix mask> <forwarding router’s address>
Remote AZ needs to get to the 10.10.2.0 and 192.168.2.0
networks on Menomonie and the
10.10.3.0 network on RemoteWI so we will configure a static
route to complete this task.
10.10.2.0 255.255.255.0 192.168.1.2 and
press enter.
10.10.3.0 255.255.255.0 192.168.3.1 and
press enter.
192.168.2.0 255.255.255.0 192.168.1.2
and press enter.
configuration using copy running-config

14. startup-config command.
Configure the static routes on Menomonie:
10.10.1.0 255.255.255.0 192.168.1.1 and
press enter.
10.10.3.0 255.255.255.0 192.168.2.2 and
press enter.
192.168.3.0 255.255.255.0 192.168.2.2
and press enter.
configuration using copy running-config
startup-config command.
Static Routing
Configure static routes on RemoteWI:
Configure the static routes on RemoteWI so traffic can get to
the Menomonie and RemoteAZ networks.

15. 10.10.1.0 255.255.255.0 192.168.3.2 and
press enter.
10.10.2.0 255.255.255.0 192.168.2.1 and
press enter.
192.168.1.0 255.255.255.0 192.168.3.2
and press enter.
configuration using copy running-config
startup-config command.
Step 3: Verifying Connectivity
Use the command show ip route to review the routing table of
each router. If everything was done
correctly you will see routes to all networks in the topology in
the routing table, some will be
Connected and some will be Static. There are six networks in
the topology
In all routers:
to
view the routing table.

16. Static Routing
Next, use ping to verify the connectivity between all the routers
and hosts. To ping from the routers you will
go into privileged mode and type ping ip address, where ip
address is the IP address you are wanting to
ping, you are wanting to see if you have connectivity to. If your
ping is successful then you have
connectivity to that network and you have done the lab correctly
once you have ensured you have
connectivity to all networks.
l interfaces (ip addresses) from all routers
Example:
On RemoteAZ I pinged to the IP addresses on Menomonie that I
wasn’t directly connected to and it was
successful.
If you are unable to ping an interface or computer, verify your
configurations to make sure you entered
everything correctly.