CompNtwk : Lab 7.1.6 Analyzing a Test Plan and Performing a Test

Task 1: Analyze the Test Plan

Analyze the test plan shown above and answer the following questions:

a. What are the four main sections of the test plan?

1) Introduction,

2) Equipment,

3) Design / Topology Diagram,

4) Test Descriptions and related testing information. (Test procedure, success criteria, and conclusions subsections repeat for each test within the test plan.)

How many tests are defined within the test plan in this lab?

2

In which testing subsection would you find the types of commands or analysis tools used to determine

if the test was successful?

Procedures

d. In which main test plan section would you find a description the devices and cabling used to build the

prototype for the test plan?

Equipment

e. In which main testing section would an overall description of the tests to be performed and the

reasons why they are being specified in the test plan?

Introduction

Task 2: Configure the PCs and switch VLANs and perform Test 1

Step 1: Connect devices and configure PC IP addresses

Connect the switch to the router as shown in the Test Plan topology diagram.

Connect the PC1 and PC2 hosts to the switch using the ports indicated in the Test Plan topology table.

Using the IP address information from the Test Plan table, configure PC1 and PC2.

Step 2: Prepare the switch for configuration

Connect a PC with a console cable to the switch to perform configurations using a terminal emulation

program. Confirm that the switch is ready for lab configuration by ensuring that all existing VLAN and general configurations are removed. Remove the switch startup configuration file from NVRAM.

Switch#erase startup-config

Erasing the nvram filesystem will remove all files! Continue? [confirm]

Press Enter to confirm. The response should be:

Erase of nvram: complete

If the switch has previously been configured with VLANs, it will necessary to delete the VLAN

database information file. From the privileged EXEC mode, issue the following commands:

Switch#delete vlan.dat

Delete filename [vlan.dat]?[Enter]

Delete flash:/vlan.dat? [confirm] [Enter]

If there was no VLAN file, this message is displayed.

%Error deleting flash:/vlan.dat (No such file or directory)

It is recommended that the delete command not be issued as: delete flash:vlan.dat.

Accidentally omitting vlan.dat from this command could lead to the complete IOS being deleted

from flash memory. Issuing the reload command to restart the switch may not always clear the previous VLAN configuration; for that reason, the power cycle (hardware restart) step is recommended.

Step 3: Configure VLANs on switch S1

Configure switch S1 with a hostname and passwords.

Switch(config)#hostname FC-ASW-1

FC-ASW-1(config)#enable password cisco

FC-ASW-1(config)#enable secret class

FC-ASW-1(config)#line console 0

FC-ASW-1(config-line)#password cisco

FC-ASW-1(config-line)#login

FC-ASW-1(config-line)#line vty 0 15

FC-ASW-1(config-line)#password cisco

FC-ASW-1(config-line)#login

FC-ASW-1(config-line)#exit

FC-ASW-1(config)#

Configure switch S1 with the VLAN 1 IP address of 10.0.1.2/24.

FC-ASW-1(config)#interface vlan1

FC-ASW-1(config-if)#ip address 10.0.1.2 255.255.255.0

FC-ASW-1(config-if)#no shutdown

FC-ASW-1(config-if)#exit

FC-ASW-1(config)#

Configure switch S1 with the default gateway address of 10.0.1.1.

FC-ASW-1(config)#ip default-gateway 10.0.1.1

FC-ASW-1(config)#

Create VLAN 10 named main-net and VLAN 20 named voice.

FC-ASW-1(config)#vlan 10

FC-ASW-1(config-vlan)#name main-net

FC-ASW-1(config-vlan)#exit

FC-ASW-1(config-vlan)#vlan 20

FC-ASW-1(config-vlan)#name voice

FC-ASW-1(config-vlan)#exit

FC-ASW-1(config)#

Assign interface range Fa0/2 through Fa0/12 to VLAN 10.

FC-ASW-1(config)#interface range fa0/2 – 12

FC-ASW-1(config-if-range)#switchport mode access

FC-ASW-1(config-if-range)#switchport access vlan 10

FC-ASW-1(config-if-range)#exit

FC-ASW-1(config)#

Assign interface range Fa0/13 through Fa0/24 to VLAN 20.

FC-ASW-1(config)#interface range fa0/13 – 24

FC-ASW-1(config-if-range)#switchport mode access

FC-ASW-1(config-if-range)#switchport access vlan 20

FC-ASW-1(config-if-range)#end

FC-ASW-1#

Step 4: Perform Test 1 to determine if the hosts can communicate between VLANs

a. Issue the show running-config commands from the switch and verify all basic configuration

settings. See output at end of lab.

b. Issue the show vlan brief command on the switch to verify what ports are in which VLANs.

Which switch ports are in VLAN 1?

Fa0/1 Gi0/1, Gi0/2

Which switch ports are in VLAN 10?

Fa0/2 – Fa0/12

Which switch ports are in VLAN 20?

Fa0/13 – Fa0/24

FC-ASW-1#show vlan brief

VLAN Name Status Ports

1 default active Fa0/1, Gi0/1, Gi0/2

10 main-net active Fa0/2, Fa0/3, Fa0/4, Fa0/5

Fa0/6, Fa0/7, Fa0/8, Fa0/9

Fa0/10, Fa0/11, Fa0/12

20 voice active Fa0/13, Fa0/14, Fa0/15, Fa0/16

Fa0/17, Fa0/18, Fa0/19, Fa0/20

Fa0/21, Fa0/22, Fa0/23, Fa0/24

<*** output omitted ***>

c. With PC1 connected to switch port 4 and PC2 attached to port 14, attempt to ping from PC1 to PC2.

Would you expect the ping to be successful?

Tidak

Why or why not?

PC IP addresses are on different networks (PC1 is on net 10.0.10.0/24 and PC2 is on net 10.0.20.0/24 and in different VLANs.

d. Change the IP address of PC2 to 10.0.10.5 so that the two PCs are on the same network and ping again. Would you expect the ping to be successful?

Tidak

Why or why not?

Alamat IP PC punya alamat jaringan yang sama tapi masih di VLAN yang berbeda

e. Move the cable for PC2 to a port that is in the VLAN 10 range (Fa0/2 to Fa0/12) and ping again.

Would you expect the ping to be successful?

Ya

Why or why not?

Alamat IP PC berada pada jaringan dan VLAN yang sama

f. Change the IP address for PC2 back to 10.0.20.2 and move the cable back to Fa0/14 in VLAN 20.

This test demonstrated that the PCs from the main-net cannot communicate with the PCs on the voice net without assistance from a Layer 3 device.

Task 3: Configure the switch and router for VLAN routing and perform Test 2

Step 1: Configure VLAN trunking on switch S1

Configure trunking between switch S1 and the router with 802.1 encapsulation on both devices.

FC-ASW-1#int fa0/1

FC-ASW-1(config-if)#switchport mode trunk

FC-ASW-1(config-if)#end

Step 2: Perform basic configuration of the router.

Connect a PC to the console port of the router to perform configurations using a terminal emulation

program. Configure router R1 with a hostname and console, Telnet, and privileged passwords according to the table diagram.

Router(config)#hostname FC-CPE-1

FC-CPE-1(config)#line con 0

FC-CPE-1(config-line)#password cisco

FC-CPE-1(config-line)#login

FC-CPE-1(config-line)#line vty 0 4

FC-CPE-1(config-line)#password cisco

FC-CPE-1(config-line)#login

FC-CPE-1(config-line)#exit

FC-CPE-1(config)#enable password cisco

FC-CPE-1(config)#enable secret class

FC-CPE-1(config)#no ip domain lookup

Step 3: Configure VLAN Trunking on the Router

Configure router R1 Fa0/0 interface to trunk for VLAN 1, VLAN 10, and VLAN 20 with 802.1Q

encapsulation.

FC-CPE-1(config)#interface fa0/0

FC-CPE-1(config-if)#no shutdown

FC-CPE-1(config-if)#interface fa0/0.1

FC-CPE-1(config-subif)#encapsulation dot1Q 1

FC-CPE-1(config-subif)#ip address 10.0.1.1 255.255.255.0

FC-CPE-1(config-subif)#exit

FC-CPE-1(config)#interface fa0/0.10

FC-CPE-1(config-subif)#encapsulation dot1Q 10

FC-CPE-1(config-subif)#ip address 10.0.10.1 255.255.255.0

FC-CPE-1(config-subif)#exit

FC-CPE-1(config)#interface fa0/0.20

FC-CPE-1(config-subif)#encapsulation dot1Q 20

FC-CPE-1(config-subif)#ip address 10.0.20.1 255.255.255.0

FC-CPE-1(config-subif)#end

FC-CPE-1#

On the router, issue the command show vlans.

What information is displayed?

The 802.1Q trunk subinterfaces, the address configured and the number of packet transmitted and received

FC-CPE-1#show vlans

Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interface: FastEthernet0/0.1

This is configured as native Vlan for the following interface(s) :

FastEthernet0/0

Protocols Configured: Address: Received: Transmitted:

IP 10.0.1.1 21 43

Other 0 138

396 packets, 67954 bytes input

181 packets, 51149 bytes output

Virtual LAN ID: 10 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interface: FastEthernet0/0.10

Protocols Configured: Address: Received: Transmitted:

IP 10.0.10.1 94 25

Other 0 12

94 packets, 15324 bytes input

37 packets, 3414 bytes output

Virtual LAN ID: 20 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interface: FastEthernet0/0.20

Protocols Configured: Address: Received:

Transmitted:

IP 10.0.20.1 9781 113

Other 0 14

9781 packets, 939660 bytes input

127 packets, 9617 bytes output

From switch S1, issue the command show interfaces trunk.

What interface on switch S1 is in trunking mode?

Fa0/1

Which VLANs are allowed and active in the management domain?

1, 10, 20

FC-ASW-1#show interfaces trunk

Port Mode Encapsulation Status Native vlan

Fa0/1 on 802.1q trunking 1

Port Vlans allowed on trunk

Fa0/1 1-4094

c.

Port Vlans allowed and active in management domain

Fa0/1 1,10,20

Port Vlans in spanning tree forwarding state and not pruned

Fa0/1 1,10,20

Step 4: Perform Test 2 to determine if the hosts can communicate between VLANs through the use of inter-vlan routing provide by a router

a. Issue the show running-config commands from the switch and verify all basic configuration

settings. See output at end of lab.

b. Ping from the switch to the router default gateway for VLAN 1.

Was the ping successful?

Ya

c. Telnet from the switch to the router.

Where you successful?

Ya

d. With PC1 connected to switch port 4 and PC2 attached to port 14, attempt to ping from PC1 to PC2.

Would you expect the ping to be successful?

Ya

Why or why not?

PC IP addresses are on different networks (PC1 is on net 10.0.10.0/24 and PC2 is on net 10.0.20.0/24 and in different VLANs but the router is routing packet between the two independent subnets.

e. Telnet from PC1 to the switch and the router.

Would you expect the Telnet to be successful?

Ya

Why or why not?

Physical and IP connectivity has been previously verified. As long as there are no VTY restrictions or ACLs in place, each PC should be able to telnet to either the switch using the VLAN1 IP address or to the router using any of the router subinterface addresses.

f. Issue the show ip route command on the router to display the routing table. How many subnet

routes are there?

3 – All directly connected to the subinterfaces defined for Fa0/0.

(10.0.1.0, 10.0.10.0 and 10.0.20.0)

FC-CPE-1#show ip route

Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP

D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area

N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2

E1 – OSPF external type 1, E2 – OSPF external type 2

i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS

level-2

ia – IS-IS inter area, * – candidate default, U – per-user

static route

o – ODR, P – periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 3 subnets

C 10.0.10.0 is directly connected, FastEthernet0/0.10

C 10.0.1.0 is directly connected, FastEthernet0/0.1

C 10.0.20.0 is directly connected, FastEthernet0/0.20

Task 4: Reflection

Why is it important to develop a test plan and prototype network behavior?

Sebuah rencana uji menyediakan dokumen terstruktur digunakan untuk menguji dan membutuhkan tester untuk berpikir dengan hati-hati tentang bagaimana fungsi jaringan untuk diuji dan dievaluasi. Ini membantu untuk membuktikan bahwa hasil yang diharapkan adalah nyata dan bahwa jaringan akan tampil seperti yang diharapkan. Ini berfungsi untuk mendokumentasikan hasil dari upaya pengujian.

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: