Lab: RIP v2 with VLSM

Transcription

1 Lab: RIP v2 with VLSM Topology Diagram Addressing Table Device Interface IP Address Subnet Mask Default Gateway BRANCH HQ ISP PC1 PC2 PC3 PC4 PC5 Lo1 S0/0/0 Lo1 S0/0/0 S0/0/1 S/0/0/1

2 Learning Objectives Upon completion of this lab, you will be able to: Subnet an address space given requirements. Assign appropriate addresses to interfaces and document. Cable a network according to the Topology Diagram. Erase the startup configuration and reload a router to the default state. Perform basic configuration tasks on a router. Configure and activate Serial and Ethernet interfaces. Determine appropriate static, summary, and default routes. Test and verify configurations. Reflect upon and document the network implementation. Scenario In this lab activity, you will be given a network address that must be subnetted to complete the addressing of the network shown in the Topology Diagram. Static routes will also need to be configured so that hosts on networks that are not directly connected will be able to communicate with each other. Task 1: Subnet the Address Space. Step 1: Examine the network requirements. NOTE: {PN} means your Pod Number assignment. You have been given the 10.{PN}.0.0/16 address space to complete the network design. Subnet this network to provide enough IP addresses to support the host requirements for each LAN. Remember that Point-to-Point links require 2 valid host addresses. Step 2: Complete the following Subnet Chart based on the following: 1.HQ LAN 1 requires 1000 Hosts. 2.HQ LAN 2 requires 2000 Hosts. 3.Branch LAN 1 requires 290 Hosts. 4.Branch LAN 2 requires 85 Hosts. Device Network Network ID Subnet Mask LAN 1 BRANCH HQ ISP LAN 2 WAN LAN 1 LAN 2 WAN (ISP) 209.{PN} WAN (Branch) LAN 209.{PN} WAN 209.{PN}

3 Task 2: Determine Interface Addresses. Step 1: Assign appropriate addresses on Branch. 1. Assign the first valid host address in Branch LAN 1 to PC1 2. Assign the last valid host address to the Branch LAN 1 interface (). 3. Assign the first valid host address in Branch LAN 2 to PC2 4. Assign the last valid host address to the Branch LAN 2 interface (Lo1). 5. Assign the first valid host address on the WAN interface on Branch. Step 2: Assign appropriate addresses on HQ. 1. Assign the first valid host address in HQ LAN 1 to PC3 2. Assign the last valid host address to the HQ LAN 1 interface (). 3. Assign the first valid host address in HQ LAN 2 to PC4 4. Assign the last valid host address to the HQ LAN 2 interface (Lo1). 5. Assign the second valid host address on the WAN interface to Branch. 6. Assign the second available address on the WAN interface to ISP. Step 3: Assign appropriate addresses on ISP. 1. Assign the first available address on the WAN interface to HQ. 2. Assign the first valid host address in ISP LAN to PC5. 3. Assign the last valid host address to the ISP LAN interface (). Step 4: Document the addresses to be used in the table provided under the Topology Diagram. NOTE: We will not be assigning the PC interface addresses on the equipment, it is simply for addressing purposes. Use the LAN addresses for the loopback address on each router. Task 3: Prepare the Network. Step 1: Clear any existing configurations on the routers. Task 4: Perform Basic Router Configurations. Perform basic configuration of the BRANCH, HQ, and ISP routers according to the following guidelines: 1. Configure the router hostname. 2. Disable DNS lookup. 3. Configure an EXEC mode password. {cisco} 4. Configure a message-of-the-day banner. 5. Configure a password for console connections. {class} 6. Configure a password for VTY connections. {class} 7. Synchronize unsolicited messages and debug output with solicited output and prompts for the console and virtual terminal lines. 8. Configure an EXEC timeout of 15 minutes.

4 Task 5: Configure and Activate Serial and Ethernet Addresses. Step 1: Configure the interfaces on the BRANCH, HQ, and ISP routers. Configure the interfaces on the BRANCH, HQ, and ISP routers with the IP addresses from the table provided under the Topology Diagram. When you have finished, be sure to save the running configuration to the NVRAM of the router. Step 2: Configure the Ethernet interfaces. Since we do not have actual hosts connected to our devices, we are using Loopback addresses to simulate a LAN. The Loopback addresses should be assigned to the LAN interface. Task 6: Verify Connectivity to Next-Hop Device. You should not have connectivity between end devices yet. Step 1: Verify BRANCH and HQ connectivity. Verify that BRANCH can ping across the WAN link to HQ. Step 2: Verify HQ and ISP connectivity. Verify that HQ can ping across the WAN link to ISP. Task 7: Configure RIP Routing. Do not advertise RIP routes out any of the LAN interfaces. Step 1: Configure RIP v2 on Branch. Step 2: Configure RIP v2 on HQ. Step 3: Configure RIP v2 on ISP. Do not allow the LAN interface on ISP to participate in the RIP routing process. ISP should have a default static route out Fa0/0 (Lo) and advertise it to the rest of the network. Task 8: Verify the Configurations. Note: We must use the extended functions of PING to test from the PC's. Use the address as the source address. The Highlighted commands are NOT defaults, all others simply press enter. Router#ping Protocol [ip]: Target IP address: {Destination IP} Repeat count [5]: Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Source address or interface: {Source IP} Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: Data pattern [0xABCD]: Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]:

5 Answer the following questions to verify that the network is operating as expected: From PC2, is it possible to ping PC1? From PC2, is it possible to ping PC3? From PC2, is it possible to ping PC5? The answer to these questions should be yes. If any of the above pings failed, check your physical connections and configurations. For a review of basic troubleshooting techniques, see Lab 1.5.1, Cabling a Network and Basic Router Configuration. Task 9: Document the Router Configurations On each router, capture the following command output to a text (.txt) file and save for future reference. Running configuration (Router#sh run) Routing table (Router#sh ip route) Interface summarization (Router#sh ip int brief)