Packet Tracer – Configure one-arm router for inter-VLAN routing

Packet Tracer – configure one-arm router inter-VLAN routing

Address Assignment Form

Device

Interface

IPv4 address

Subnet Mask

Default Gateway

R1

G0/0.10

172.17.10.1

255.255.255.0

not applicable

G0/0.30

172.17.30.1

255.255.255.0

not applicable

PC1

NICs

172.17.10.10

255.255.255.0

172.17.10.1

PC2

NICs

172.17.30.10

255.255.255.0

172.17.30.1

Topology Map

Goal

Part 1: Test connectivity without inter-VLAN routing

Part 2: Adding VLANs to the Switch

Part 3: Configuring Subinterfaces

Part 4: Testing connectivity when using inter-VLAN routing

Scene

In this exercise, you will check connectivity before implementing inter-VLAN routing. Then, configure VLANs and inter-VLAN routing. Finally, you will enable trunking and verify connectivity between the VLANs.

Part 1: Testing Connections Without Inter-VLAN Routing

Step 1: Ping between PC1 and PC3.

Wait for the switch to converge, or click speed up forwarding time a few times. When the link lights of PC1 and PC3 are green, on PC1 strong> and PC3. The ping fails because the two PCs are on different networks and R1 is not configured.

Step 2: Switch to simulation mode to monitor ping.

a. Switch to simulation mode by clicking the Simulation tab or pressing Shift + S.

b. Click Capture/Forward to view pings on PC1 and PC3 > Steps to take between . Notice how the ping never leaves PC1. Which process failed and why?

The ARP process failed because the ARP request was dropped by PC3. PC1 and PC3 are not on the same network, so PC1 will never learn PC3’s MAC address. Without a MAC address, PC1 cannot create an ICMP echo request.

Part 2: Adding VLANs to the Switch

Step 1: Create a VLAN on S1.

Return to Live mode and create VLAN 10 and VLAN 30 on S1.

S1(config)#vlan 10

S1(config-vlan)#vlan 30

Step 2: Assign VLANs to ports.

a. Configure interfaces F0/6 and F0/11 as access ports and assign VLANs.

· Assign PC1 to VLAN 10.

· Assign PC3 to VLAN 30.

S1(config)#int f0/11

S1(config-if)#switchport mode access

S1(config-if)#switchport access vlan 10

S1(config-if)#int f0/6

S1(config-if)#switchport mode access

S1(config-if)#switchport access vlan 30

b. Issue the show vlan brief command to verify the VLAN configuration.

S1#show vlan brief

VLAN Name Status Ports

—- ——————————– ——— —– ————————–

1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4

Fa0/5, Fa0/7, Fa0/8, Fa0/9

Fa0/10, Fa0/12, Fa0/13, Fa0/14

Fa0/15, Fa0/16, Fa0/17, Fa0/18

Fa0/19, Fa0/20, Fa0/21, Fa0/22

Fa0/23, Fa0/24, Gig0/1, Gig0/2

10 VLAN0010 active Fa0/11

30 VLAN0030 active Fa0/6

1002 fddi-default active

1003 token-ring-default active

1004 fddinet-default active

1005 trnet-default active

Step 3: Test the connection between PC1 and PC3.

Ping PC3 from PC1. Pings will still fail. Why is the ping unsuccessful?

Each VLAN is a separate network that requires a router or layer 3 switch to provide communication between them

Part 3: Configuring Subinterfaces

Step 1: Configure a subinterface on R1 using 802.1Q encapsulation.

a. Create subinterface G0/0.10.

· Set the encapsulation type to 802.1Q and assign VLAN 10 to the subinterface.

· Refer to the Address Table to assign the correct IP address to the subinterface.

b. Repeat for the G0/0.30 subinterface.

R1(config)#int g0/0.10

R1(config-subif)#encapsulation dot1Q 10

R1(config-subif)#ip add 172.17.10.1 255.255.255.0

R1(config-subif)#no sh

R1(config-subif)#int g0/0.30

R1(config-subif)#encapsulation dot1Q 30

R1(config-subif)#ip add 172.17.30.1 255.255.255.0

R1(config-subif)#no sh

Step 2: Verify the configuration.

a. Use the show ip interface brief command to verify the subinterface configuration. Both subinterfaces are down. A subinterface is a virtual interface associated with a physical interface. Therefore, in order to enable subinterfaces, you must enable the physical interfaces associated with them.

b. Enable the G0/0 interface. Verify that the subinterface is now active.

R1(config)#int g0/0

R1(config-if)#no sh

Part 4: Testing Connections Using Inter-VLAN Routing

Step 1: Ping between PC1 and PC3.

Ping PC3 from PC1. Pings will still fail.

Step 2: Enable Relay.

a. On S1, issue the show vlan command. To which VLAN is G0/1 assigned?

VLAN 1

b. Since the router is configured with multiple subinterfaces assigned to different VLANs, the switch port connected to the router must be configured as a trunk. Enable trunking on interface G0/1.

S1(config)#int g0/1

S1(config-if)#switchport mode trunk

c. How to use the show vlan command to determine that the interface is a trunk port?

The interface is no longer listed under VLAN 1

d. Issue the show interface trunk command to verify that the interface is configured as a trunk.

Step 3: Switch to simulation mode to monitor ping.

a. Switch to Simulation< strong>Simulation /strong> mode.

b. Click Capture/Forward to view pings on PC1 and PC3 > Steps to take between .

c. You should see ARP requests and replies between S1 and R1. Then there are ARP requests and replies between R1 and S3. PC1 can then encapsulate the correct data link layer information for the ICMP echo request and R1 will route the request to PC3.

Note: After the ARP process is complete, you may need to click “Reset Simulation” to see if the ICMP process is complete.

Experimental steps:

S1:

S1>enable

S1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

S1(config)#vlan 10

S1(config-vlan)#vlan 30

S1(config-vlan)#exit

S1(config)#int f0/11

S1(config-if)#switchport mode access

S1(config-if)#switchport access vlan 10

S1(config-if)#int f0/6

S1(config-if)#switchport mode access

S1(config-if)#switchport access vlan 30

S1(config-if)#

%LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

S1(config-if)#exit

S1(config)#int g0/1

S1(config-if)#switchport mode trunk

S1(config-if)#

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

S1(config-if)#

S1(config-if)#end

S1#

%SYS-5-CONFIG_I: Configured from console by console

S1#write

Building configuration…

[OK]

S1#

R1:

R1>ena

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#int g0/0.10

R1(config-subif)#encapsulation dot1Q 10

R1(config-subif)#ip add 172.17.10.1 255.255.255.0

R1(config-subif)#no sh

R1(config-subif)#int g0/0.30

R1(config-subif)#encapsulation dot1Q 30

R1(config-subif)#ip add 172.17.30.1 255.255.255.0

R1(config-subif)#no sh

R1(config-subif)#exit

R1(config)#int g0/0

R1(config-if)#no sh

R1(config-if)#

%LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up

%LINK-5-CHANGED: Interface GigabitEthernet0/0.10, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0.10, changed state to up

%LINK-5-CHANGED: Interface GigabitEthernet0/0.30, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0.30, changed state to up

R1(config-if)#end

R1#

%SYS-5-CONFIG_I: Configured from console by console

R1#we

R1#w

R1#write

Building configuration…

[OK]

R1#

Experiment script:

S1:

enable

conf t

vlan 10

vlan 30

exit

int f0/11

switchport mode access

switchport access vlan 10

int f0/6

switchport mode access

switchport access vlan 30

exit

int g0/1

switchport mode trunk

end

write

R1:

ena

conf t

int g0/0.10

encapsulation dot1Q 10

ip add 172.17.10.1 255.255.255.0

no sh

int g0/0.30

encapsulation dot1Q 30

ip add 172.17.30.1 255.255.255.0

no sh

exit

int g0/0

no sh

end

write

Experiment link: https://pan.baidu.com/s/1hmeeCFBayf-FMYRl6LJ0Og?pwd=6336

Extraction code: 6336

–Sharing from Baidu Netdisk super member V3

syntaxbug.com © 2021 All Rights Reserved.