INFORMATION TEC2

Lab - Building a Simple Network Topology Addressing Table Device Interface IP Address Subnet Mask PC-A NIC 192.168.1.10 255.255.255.0 PC-B NIC 192.168.1.11 255.255.255.0 Objectives Part 1: Set Up the Network Topology (Ethernet only) Part 2: Configure PC Hosts Part 3: Configure and Verify Basic Switch Settings Background / Scenario Networks are constructed of three major components: hosts, switches, and routers. In this lab, you will build a simple network with two hosts and two switches. You will also configure basic settings including hostname, local passwords, and login banner. Use show commands to display the running configuration, IOS version, and interface status. Use the copy command to save device configurations. You will apply IP addressing for this lab to the PCs to enable communication between these two devices. Use the ping utility to verify connectivity. Required Resources 2 Switches (Cisco 2960) 2 PCs Console cables to configure the Cisco IOS devices via the console ports Ethernet cables as shown in the topology

Part 1: Set Up the Network Topology (Ethernet only) In Part 1, you will cable the devices together according to the network topology. Step 1: Connect the two switches. Connect one end of an Ethernet cable to F0/1 on S1 and the other end of the cable to F0/1 on S2. You should see the lights for F0/1 on both switches turn amber and then green. This indicates that the switches have been connected correctly. Step 2: Connect the PCs to their respective switches. a. Connect one end of the second Ethernet cable to the NIC port on PC-A. Connect the other end of the cable to F0/6 on S1. After connecting the PC to the switch, you should see the light for F0/6 turn amber and then green, indicating that PC-A has been connected correctly. b. Connect one end of the last Ethernet cable to the NIC port on PC-B. Connect the other end of the cable to F0/18 on S2. After connecting the PC to the switch, you should see the light for F0/18 turn amber and then green, indicating that the PC-B has been connected correctly. Part 2: Configure PC Hosts Step 1: Configure static IP address information on the PCs. a. Use the following IP address to manually enter an IP address for PC-A and a subnet mask. IP address 192.168.1.10 Subnet Mask 255.255.255.0 b. Use the following IP address to manually enter an IP address for PC-A and a subnet mask. IP address 192.168.1.11 Subnet Mask 255.255.255.0 Step 2: Verify PC settings and connectivity. Use the command prompt (cmd.exe) window to verify the PC settings and connectivity. a. On PC-A go to the Command Prompt on the Desktop and verify your PC settings by using the ipconfig /all command. This command displays the PC hostname and the IPv4 address information.

b. Type ping 192.168.1.11 and press Enter. Were the ping results successful? ______________________

Part 3: Configure and Verify Basic Switch Settings

Step 1: Console into the switch. Establish a console connection to the switch from PC-A. Step 2: Enter privileged EXEC mode. You can access all switch commands in privileged EXEC mode. The privileged EXEC command set includes those commands contained in user EXEC mode, as well as the configure command through which access to the remaining command modes are gained. Enter privileged EXEC mode by entering the enable command. Switch> enable Switch# The prompt changed from Switch> to Switch# which indicates privileged EXEC mode.

Step 3: Enter configuration mode. Use the configuration terminal command to enter configuration mode. Switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# The prompt changed to reflect global configuration mode.

Step 4: Give the switch a name. Use the hostname command to change the switch name to S1. Switch(config)# hostname S1 S1(config)# Step 5: Prevent unwanted DNS lookups. To prevent the switch from attempting to translate incorrectly entered commands as though they were hostnames, disable the Domain Name System (DNS) lookup. S1(config)# no ip domain-lookup S1(config)# Step 6: Enter local passwords. To prevent unauthorized access to the switch, passwords must be configured. S1(config)# enable secret class S1(config)# line con 0 S1(config-line)# password cisco S1(config-line)# login S1(config-line)# exit S1(config)# Step 7: Enter a login MOTD banner. A login banner, known as the message of the day (MOTD) banner, should be configured to warn anyone accessing the switch that unauthorized access will not be tolerated. The banner motd command requires the use of delimiters to identify the content of the banner message. The delimiting character can be any character as long as it does not occur in the message. For this reason, symbols, such as the #, are often used.

S1(config)# banner motd # Enter TEXT message. End with the character '#'. Unauthorized access is strictly prohibited and prosecuted to the full extent of the law. # S1(config)# exit S1# Step 8: Save the configuration. Use the copy command to save the running configuration to the startup file on non-volatile random access memory (NVRAM). S1# copy running-config startup-config Destination filename [startup-config]? [Enter] Building configuration... [OK] S1# Step 9: Display the current configuration. The show running-config command displays the entire running configuration, one page at a time. Use the spacebar to advance paging. The commands configured in Steps 1 – 8 are highlighted below. S1# show running-config Building configuration... Current configuration : 1409 bytes ! ! Last configuration change at 03:49:17 UTC Mon Mar 1 1993 ! version 15.0 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname S1 ! boot-start-marker boot-end-marker ! enable secret 4 06YFDUHH61wAE/kLkDq9BGho1QM5EnRtoyr8cHAUg.2 ! no aaa new-model system mtu routing 1500 ! ! no ip domain-lookup ! <output omitted>

! banner motd ^C Unauthorized access is strictly prohibited and prosecuted to the full extent of the law. ^C ! line con 0 password cisco login line vty 0 4 login line vty 5 15 login ! end S1# Step 10: Display the IOS version and other useful switch information. Use the show version command to display the IOS version that the switch is running, along with other useful information. Again, you will need to use the spacebar to advance through the displayed information. S1# show version Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 15.0(2)SE, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2012 by Cisco Systems, Inc. Compiled Sat 28-Jul-12 00:29 by prod_rel_team ROM: Bootstrap program is C2960 boot loader BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(53r)SEY3, RELEASE SOFTWARE (fc1) S1 uptime is 1 hour, 38 minutes System returned to ROM by power-on System image file is "flash:/c2960-lanbasek9-mz.150-2.SE.bin" This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

Switch Ports Model SW Version SW Image ------ ----- ----- ---------- ---------- * 1 26 WS-C2960-24TT-L 15.0(2)SE C2960-LANBASEK9-M Configuration register is 0xF S1#

Step 11: Display the status of the connected interfaces on the switch.

To check the status of the connected interfaces, use the show ip interface brief command. Press the spacebar to advance to the end of the list. S1# show ip interface brief Interface IP-Address OK? Method Status Protocol Vlan1 unassigned YES unset up up FastEthernet0/1 unassigned YES unset up up FastEthernet0/2 unassigned YES unset down down FastEthernet0/3 unassigned YES unset down down FastEthernet0/4 unassigned YES unset down down FastEthernet0/5 unassigned YES unset down down FastEthernet0/6 unassigned YES unset up up FastEthernet0/7 unassigned YES unset down down FastEthernet0/8 unassigned YES unset down down FastEthernet0/9 unassigned YES unset down down FastEthernet0/10 unassigned YES unset down down FastEthernet0/11 unassigned YES unset down down FastEthernet0/12 unassigned YES unset down down FastEthernet0/13 unassigned YES unset down down FastEthernet0/14 unassigned YES unset down down FastEthernet0/15 unassigned YES unset down down FastEthernet0/16 unassigned YES unset down down FastEthernet0/17 unassigned YES unset down down FastEthernet0/18 unassigned YES unset down down FastEthernet0/19 unassigned YES unset down down FastEthernet0/20 unassigned YES unset down down FastEthernet0/21 unassigned YES unset down down FastEthernet0/22 unassigned YES unset down down FastEthernet0/23 unassigned YES unset down down FastEthernet0/24 unassigned YES unset down down GigabitEthernet0/1 unassigned YES unset down down GigabitEthernet0/2 unassigned YES unset down down S1#

Step 12: Repeat Steps 1 to 12 to configure switch S2. The only difference for this step is to change the hostname to S2. Step 13: Record the interface status for the following interfaces. S1 S2 Interface Status Protocol Status Protocol F0/1 F0/6 F0/18 VLAN 1 Why are some FastEthernet ports on the switches are up and others are down? ________________________________________________________________________________ ________________________________________________________________________________ Reflection

What could prevent a ping from being sent between the PCs?