《网络规划与设计课程设计》指导书参照下面网络图与指定的练习内容进行。
EXERCISE 1 Using IOS FeaturesChoose 3620-1.1. Access User EXEC mode on your router.Hit the ENTER key. You should see the EXEC prompt: Router>.2. Pull up the list of commands available at this mode.Use the ?.3. Go to Privilege EXEC mode.Use the enable command and your prompt should look like this: Router#.4. Type the show interfaces and show running-config commands on two separatecommand lines.On one command line, type: show interfaces. Hit the ENTER key. On the nextcommand-line type: show running-config.5. Use the CLI editing features of your router by changing the show running-configcommand to show startup-config and execute this.Use the command recall (UP ARROW) to recall the show running-config command.Edit this command and replace “running” with “startup.” You need to LEFT ARROW over to the “-” and BACKSPACE to delete the word “running.” Then type startup. UseCTRL-E to go to the end of the line and hit the ENTER key to execute the command.6. Log out of the router switch.Use the exit command.EXERCISE 2 Set Up a Basic Configuration1. Starting with the 3620-1 router, go to Privilege EXEC mode and then enter Configuration mode.On 3620-1 router, access User EXEC mode and use enable to go to Privilege EXEC mode and then configure terminal to access Configuration mode.2. Assign a hostname of 3620-1.Use the hostname 3620-1 command and examine the prompt.3. Set a User EXEC password of cisco for telnet access.Enter the line vty 0 4 command and follow it with the login and password cisco commands.4. Exit this subcommand mode: exit.5. Assign an encrypted Privilege EXEC password of cisco.Enter enable secret cisco.6. Check whether or not the serial 1/0 interface is DTE or DCE.If it is DCE, assign a clock rate of 64000. Check the controller: show controller serial 1/0.7.if it’s the DCE, e nter the interface with configure terminal and interface serial 1/0. Configure the clock rate: clock rate 64000.8.Enable the fastethernet 0/0 interface: interface fastethernet 0/0,no shutdown, and exit.9.Enable the Serial 1/0 interface: interface Serial 1/0,no shutdown, and exit.10. Use a command to display all of the interfaces, their IP addresses, and their statuses on one screen and then show the details of fastethernet0 and serial 1/0 separately.Use the show interfaces command followed by show interface Fa0/0 and show interface s1/1.11. Save your configuration to NVRAM and view the active configuration.Save it with copy running-config startup-config and view it with showrunning-config.12.Configure the 3620-2 router.13. Assign a hostname of e the hostname 3620-2.Enter the line vty 0 4 command and follow it with the login and password cisco commands. Exit the subcommand mode: exit.14. Enter enable secret cisco.15. Enable the fastethernet 0/0 interface: interface fastethernet 0/0,no shutdown, and end. Check the serial 1/1 controller: show controller serial 1/1. if it’s the DCE, e nter the interface with configure terminal and interface serial 1/1. Configure the clock rate: clock rate 64000.ing: show interface. Make sure fa0/0 and s1/1 are “up and up”.17.Save your configuration to NVRAM and view the active configuration.Save it with copy running-config startup-config and view it with showrunning-config.18. Go to Configuration mode on your 2950-1 switch.Access User EXEC mode. Use enable to go to Privilege EXEC mode and then configure terminal to access Configuration mode. Assign a hostname of 2950 to the switch of e the hostname2950-1 command and examine the prompt. Enter the line vty 0 4 command and follow it with the login and password cisco commands.. Enter enable secret cisco. Exit the subcommand mode: end.19.View the switch’s interface status by using the show interface commands.20. Save your configuration to NVRAM and view the active configuration.Save it with copy running-config startup-config.21.Repeat this process(step 18 to 20)for the 2950-2 switch (with a hostname of 2950-2) and the 2950-3 switch (with a hostname of 2950-3).EXERCISE 3 Configuring the Switches1. Go to Configuration mode on your 2950-1 switch.2. Assign an IP address of 192.168.1.2/24 to the 2950-1 in VLAN 1, with a default gateway of 192.168.1.1.3.Enter the VLAN interface with interface vlan1. Next, enter the addressing information: ip address192.168.1.2 255.255.255.0.Enabled the interface: no shutdown. Exit the interface with the exit command and configure the default gateway: ip default-gateway 192.168.1.1.5. Save your configuration to NVRAM and view the configuration in NVRAM.Return to Privilege EXEC mode with the end command. Save it with copyrunning-config startup-config and view it with show startup-config.Host-1. On the CLI, type ipconfig /ip 192.168.1.10 255.255.255.0. Then, typeipconfig/dg 192.168.1.1(or winipcfg).Host-2. On the CLI, type ipconfig /ip 192.168.1.11 255.255.255.0. Then, typeipconfig/dg 192.168.1.1(or winipcfg).Test connectivity to Host-1: ping192.168.1.10. The ping should be successful6.Test connectivity to Host-2: ping192.168.1.11. The ping should be successful.7. Like above step, configure the 2950-2 switch ,parameter shows as topology .enter: enable, configure terminal, interface vlan1,ip address192.168.1.3255.255.255.0, no shutdown, exit, ip default-gateway192.168.1.1, end, copy running-config startup-config, and show startup-config. Make sure you configured the right hostname and IP address.8. Configure the 2950-3 switch ,parameter shows as topology .9. Test connectivity by pinging the Host-3 and Host-4 PCs: ping 192.168.3.10 and ping 192.168.3.11.The pings should be successful.EXERCISE 4 Configuring Trunks on Your Switches1. On the 2950-1 switch, set the trunk mode to on for the connection between the two 2950 switches and examine the status. Does the trunk come up?Choose 2950-1. Access Configuration mode: enable and configure terminal. Go into the interface: interface fa0/1. Set the trunk mode to trunk: switchport mode trunk. Exit configuration mode: end. Use the show interfaces trunk command to verify the status.You might have to wait a few seconds, but the trunk should come up. If one side is set to on, or desirable, and the other is set to on, desirable, or auto (default), then the trunk should come up.2. Save your configuration to NVRAM:copy running-config startup-config.3. On the 2950-2 switch, set the trunk mode to on for the connection between the two 2950 switches and verify the trunking status of the interface.Choose 2950-2. Access Configuration mode: enable and configure terminal. Go into the interface: interface fa0/1. Set the trunk mode to trunk: switchport mode trunk. Exit configuration mode: end. Use the show interfaces trunk command to verify the status.4. Save your configuration to NVRAM:copy running-config startup-config.EXERCISE 5 Configuring VLANs on Your Switches1. From the 2950-1, verify that you can ping Host-1 connected to fa0/3. Also ping Host-2 connected to 2950-1’s fa0/4 interface.Choose 2950-1. Access the CLI of the 2950-1. Execute ping 192.168.1.10and ping 192.168.1.11. Both should be successful.2. On the 2950-1, create VLAN 2. Then assign fa0/3 to VLAN 2 as an access-link port.Examine your VLANs.Access Configuration mode: enable and configure terminal. Use the vlan2 command to create your VLAN. Go into the interface: interface fa0/3. Assign the VLAN: switchport mode access, switchport access vlan2. Exit out of Configuration mode: exit and exit.3.View your VLANs on the 2950-1:show vlan. Make sure that all interfaces are inVLAN 1 except for fa0/3, which should be in VLAN 2.4. From Host-1, ping Host -2 (192.168.1.11) connected to the 2950-1 switch. Is theping successful?Choose Host-1. Execute ping192.168.1.11. The ping should fail, since the Host-2 is in VLAN 1, while Host-1 is in VLAN 2.5. On the 2950-1 switch, move Host-2 to VLAN 2 and verify your configuration.Choose 2950-1.: configure terminal and interface fa0/4. Assign the VLAN: switchport mode access, switchport access vlan2. Exit and Exit.6. View your VLANs: show vlan. Make sure that fa0/3 and fa0/4 are in VLAN 2..7. From Host-1, ping Host-2 (192.168.1.11), which is connected to the 2950-1 switch.Is the ping successful? Can Host-1 ping either the 2950-1 or the 2950-2 switch?Choose Host-1. Execute ping192.168.1.11. The ping should be successful, since all connections from Host-1 to Host-2 are in VLAN 2.Execute ping192.168.1.2and ping 192.168.1.3. Both should fail, since both of these switches, by default, are in VLAN 1 and the hosts are in VLAN 2.EXERCISE 6 Manipulating Your Ro uter’s Configuration Files1. Access the 2600 router’s Privilege EXEC mode and save your router’s activeconfiguration to NVRAM. Verify the copy.Access Privilege EXEC mode: enable. Use the copy running-config startup-configcommand. Verify the copy: show startup-config.2. Change the hostname on the router to different and then reload the savedconfiguration from the NVRAM into RAM. What is the hostname?Access Configuration mode (configure terminal) and use the hostname differentcommand to change the rou ter’s name to different. Exit Configuration mode: end. Restore your configuration with copy startup-config running-config. Your prompt shouldchange back to the previous name of the router (you might have to wait a few seconds forthis to complete).3. Era se your router’s configuration in NVRAM. Examine the configuration file inNVRAM. Save the active configuration file to NVRAM. Examine the configuration file in NVRAM.Use the erase startup-config command to erase your configuration in NVRAM. Use the show startup-config command to verify the configuration file was deleted. Use the copy running-config startup-config command to save your configuration to NVRAM. Use the show startup-config command to verify that your router’s configuration was backed up from RAM to NVRAM.EXERCISE 7 Using the Router’s Troubleshooting Tools1. Access the 3620-1 router in the simulator. See what neighbors are directly connected to the router. What is the IP address of the 3620-2 router?Choose 3620-1. Use show cdp neighbors command to view the 3620-1’sneighbors—you may have to wait 60 seconds to see neighbors from this interface. You should see one of the 2950 switches and the 3620-2 router. Use the show cdp neighbors detail command to view the 3620-2’s address: it is 192.168.2.2.2. Access the 2950-2 switch in the simulator. See what neighbors are directly connected to the router. Which neighbors do you see? What are their IP addresses?At the top of the simulator in the menu bar, click on the eSwitches icon and choose 2950-2.Use the show cdp neighbors command to view your neighbors. You should see the 2950-1 switch and 3620-1 router. Add the detail parameter to the preceding command to see their IP addresses.EXERCISE 8 Static Route Configuration1. On the 3620-1, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up. Examine the IP addresses configured on the 3620-1.Use the show interfaces command to verify your configuration. If fa0/0 and s1/1 are not up, go into the interfaces (fa0/0 and s1/1) and enable them: no shutdown. Use the show interfaces command to verify that the IP addresses you configured are still there.2.Examine the routing table on the 3620-1.Use the show ip route command. You should have two connected networks: 192.168.1.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.3. On the 3620-2, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up. Examine the IP addresses configured on the 3620-2 and look at its routing table.Use the show interfaces command to verify your configuration. If fa0/0 and s1/1 are not up, go into the interfaces (fa0/0 and s1/1) and enable them: no shutdown. Use the show interfaces command to verify that the IP addresses you configured are still there.4.Examine the routing table on the 3620-2.Use the show ip route command. You should have two connected networks: 192.168.3.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.3. Test connectivity between Host-1 and the 3620-1.From Host-1,ping the 3620-1:ping192.168.1.1. The ping should be successful.If it is not, then you may have used the configuration from the VLAN lab and have a VLANconfiguration problem.4. Test connectivity between Host-3 and the 3620-2.From Host-3,ping the 3620-2:ping192.168.3.1. The ping should be successful.5. Test connectivity between Host-3 and the Host-1.From Host-3,ping the Host-1:ping192.168.1.10. The ping should fail: there is no route from the 3620-2 to this destination.6.Look at the 3620-2’s routing table: show ip route. I t doesn’t list 192.168.1.0/24.7. On the 3620-2, configure a static route to 192.168.1.0/24, which is connected to the 3620-1.Choose 3620-2. Configure the static route:ip route 192.168.1.0 255.255.255.0 192.168.2.1. View the static route: show ip route. Make sure that 192.168.1.0/24 shows up in the routing table as a static route (S).8. On the 3620-1, configure a static route to 192.168.3.0/24, which is connected to the 3620-2. View the routing table.Choose 3620-1. Configure the static route:ip route 192.168.3.0 255.255.255.0 192.168.2.2 and end.View the static route: show ip route. Make sure that 192.168.3.0/24 shows up in the routing table as a static route (S).9. From Host-3, ping the fa0/0 interface of the 3620-1.Choose Host-3. Access Host-3 and ping the fa0/0 interface of the 3620-1 router:ping 192.168.1.1. The ping should be successful. Ping Host-1 ping 192.168.1.10. The ping should be successful.10. From Host-3, ping Host-1.Choose Host-3: ping 192.168.1.10. The ping should be successful.EXERCISE 9 Basic IP and Routing Troubleshooting1. Test connectivity from Host-1 to Host-3.On Host-1, ping Host-3: ping 192.168.3.10. Note that the ping fails.2. Examine the IP configuration on Host-1.Execute winipcfg. Make sure the IP addressing information is correct: IP address of 192.168.1.10,subnet mask of 255.255.255.0, and default gateway address of 192.168.1.1. 3. Test connectivity from Host-1 to its default gateway.Ping the default gateway address: ping192.168.1.1. The ping should be successful, indicating that at least layer 3 is functioning between Host-1 and the 2600.4. Verify Host-3’s IP configuration.Execute winipcfg. Make sure the IP addressing information is correct: IP address of 192.168.3.10,subnet mask of 255.255.255.0, and default gateway address of 192.168.3.1. 5. Test connectivity from Host-3 to its default gateway.At the Host-3. ping192.168.3.1. The ping should still fail, indicating that there is a problem between Host-3 and the 3620-2. In this sample, assume layer 2 is functioning correctly; therefore, it must be a problem with the 3620-2.6. Check the 3620-2’s IP configuration.From the 3620-2,ping Host-3: ping192.168.3.10. The ping should still fail. Examine the interface on the 3620-2:show interface fa0/0.The interface is disabled, but it has the correct IP address: 192.168.3.1.7.Access Host-1 and retry pinging Host-3.From the Host-1,ping Host-3: ping192.168.3.10. The ping should still fail. So far,there is connectivity within 192.168.1.0 and 192.168.3.0,but there is still a problem between these two networks.8. Check the interface statuses on the 3620-1 and verify connectivity to the 3620-2. On 3620-1:show ip interface brief. Notice that the fa0/0 and s1/1 are both up.Try pinging the 3620-2’s s1/1 interface: ping192.168.2.2. The ping fails. Examine CDP information that the 3620-1 has learned about the 3620-2:show cdp entry 3620-2.Notice that the 3620-2 has no IP address.9. Fix the IP addressing problem on the 3620-2 and retest connectivity across the serial connection.At 3620-2. Fix the IP address: configure terminal, interface serial 1/1, ip address 192.168.2.2 255.255.255.0, end. Retest the connection to the 3620-1: ping192.168.2.1. The ping should be successful.10. Examine the routing table on the 3620-2 and verify that 192.1681.0/24 shows up as a static route.Examine the routing table: show ip route. As you can see, 192.168.1.0 shows up as a static route and points to 192.168.2.1.11. Access Host-3 and try connectivity between its default gateway and the 3620-1 router.At the Host-3. Test the connection to the 3620-2: ping192.168.3.1.The ping should be successful, considering that we already tested it.Test connectivity to the 3620-1: ping 192.168.2.1. The ping should fail. This presents an interesting problem. Host-1 can ping the 3620-1. The 3620-1 can ping the 3620-2. Host-3 can ping the 3620-2.So, on a hop-by-hop basis, you have IP connectivity. The 3620-2 can even ping Host-1, indicating that some routing functioning is working.12. Access the 3620-1 router and examine its routing table. Fix the problem.Choose 3620-1. Examine the routing table: show ip route. Does the 3620-1 know how to reach 192.168.3.0/24?It does not. The 3620-2 router could ping Host-1 since the 3620-1 router is directly connected to these segments; but any traffic from the 3620-1 to 192.168.3.0/24 will fail since the router doesn’t have a path. Add a static route to 192.168.3.0/24: ip route192.168.3.0 255.255.255.0192.168.2.2. Test connectivity to Host-3: ping 192.168.3.10. The ping should be successful.13. Now test connectivity between Host-1 and Host-3.At Host-1. Test connectivity to Host-3: ping192.168.3.10. The ping should be successful.EXERCISE 13 Configuring RIP1. On the 3620-1, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up. Examine the IP addresses configured on the 3620-1 and look at its routing table.At the 3620-1, use the show interfaces command to verify your configuration. If fa0/0 and s1/1 are not up, go into the interfaces (fa0/0 and s1/1) and enable them: configure terminal, interface type [slot_#/]port_#, no shutdown, and end.2. Use the show ip interfaces brief command to verify that the IP addresses you configured are still there.3. Use the show ip route command. You should have two connected networks: 192.168.1.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.4. On the 3620-2, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up.5. Examine the IP addresses configured on the 3620-2. Use the show ip interfaces brief command to verify that the IP addresses you configured before are still there.6. On the 3620-2, use the show ip route command. You should have two connected networks: 192.168.3.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.7. Test connectivity between Host-1 and the 3620-1.From Host-1, ping the 3620-1 router (the default gateway): ping 192.168.1.1. The ping should be successful.8. Test connectivity between Host-3 and the 3620-2. Test connectivity between Host-3 and Host-1.From the Host-3,ping the 3620-2 router (the default gateway): ping192.168.3.1. The ping should be successful.9. From the Host-3, ping Host-1: ping192.168.1.10.The ping should fail. Why? there is no route from the 3620-2 to this destination.(Look at the 3620-2’s routing table: it doesn’t list 192.168.1.0/24.)10. Access the 3620-2 and examine the routing table to see why the ping failed.At the 3620-2. Examine the routing table: show ip route. Notice that it doesn’t list 192.168.1.0/24, which explains why Host-3 can’t reach Host-1.11. Enable RIPv1 on the 3620-1 router.On the 3620-1, execute the following: router rip, network192.168.1.0, and network 192.168.2.0.12. Enable RIPv1 on the 3620-2 router.On the 3620-2, execute the following: router rip, network192.168.2.0, and network 192.168.3.0.13. On the 3620-1, verify the operation of RIP.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1. Use the show ip protocols command to make sure that RIP is configured—check for the neighbo ring router’s IP address. Use the show ip route command and look for the remote LAN network number as a RIP (R) entry in the routing table. On the 3620-1, you should see 192.168.3.0, which was learned from the 3620-2.14. On the 3620-2, verify the operation of RIP.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-2. Use the show ip protocols command to make sure that RIP is configured—check for the neighboring router’s IP address. Use the show ip route command and look for the remote LAN network number as a RIP (R) entry in the routing table. On the 3620-2, you should see 192.168.1.0, which was learned from the 3620-1.15. On Host-1, test connectivity to Host-3.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-1. On Host-1, test connectivity: ping192.168.3.10. The ping should be successful.EXERCISE 14 Basic RIP Troubleshooting1. Test connectivity from Host-1 to Host-3 with ping as well as from Host-1 to its default gateway.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-1.On Host-1, ping Host-3: ping192.168.3.10. Note that the ping fails.2. Examine the IP configuration on Host-1 by executing: winipcfg.Make sure the IP addressing information is correct: IP address of 192.168.1.10,subnet mask of 255.255.255.0, and default gateway address of 192.168.1.1.3. On Host-1, ping the default gateway address: ping192.168.1.1. The ping should fail, indicating that at least layer-3 is not functioning between Host-1 and the 3620-1.4. Check the 3620-1’s IP configuration.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1.From the 3620-1, ping Host-1: ping192.168.1.10. The ping should fail. Examine the interface on the 3620-1: show inte r face fa0/0.The interface is enabled, but has an incorrect IP address: 192.168.11.1. Fix the IP address: configure terminal, interface fa0/0, ip address192.168.1.1255.255.255.0, end. Verify the IP address: show interface fa0/0.5. Retry the ping test: ping192.168.1.10. The ping should be successful. Save the configuration on the router: copy running-config startup-config.6. Test connectivity from Host-1 to Host-3 with ping.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-1.On Host-1, ping Host-3: ping192.168.3.2. Note that the ping still fails.7. Examine Host-3’s IP configration.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-3.Examine the IP configuration on Host-3 by executing: winipcfg. Make sure the IP addressing information is correct: IP address of 192.168.3.10,subnet mask of 255.255.255.0, and default gateway address of 192.168.3.1.8. On Host-3 ping the default gateway address: ping192.168.3.1. The ping should be fail, indicating that there is a problem between Host-3 and the 3620-2. In this example, assume layer-2 is functioning correctly; therefore, it must be a problem with the 3620-2.9. Check the interface statuses and IP configuration on the 3620-2 and verify connectivity to the 3620-1. Also verify RIP’s configuration.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-2.Check the status of the interfaces: show interfaces. Notice that the fa0/0 is disabled, but s1/0 is enabled (up and up). Go into fa0/0 and enable it: configure terminal, interface fa0/0, no shutdown, end. Verify the status of the fa0/0 interface: show interface fa0/0.10. Test connectivity from 3620-2 to 3620-1 with ping.Try pinging Host-3:ping192.168.3.10. The ping should succeed. Try pinging the 3620-1’sserial 1/1 interface: ping192.168.2.1. The ping succeeds.11. Verify RIP’s configuration on 3620-2.Examine the 3620-2’s RIP configuration: show ip protocol. You should see RIP as the routing protocol and networks 192.168.2.0 and 192.168.3.0 included. From this output, it looks like RIP is configured correctly on the 3620-2. Save the configuration on the router: copy running-config startup-config.12. Test connectivity from the 3620-2 to Host-1. Examine the routing table.Test the connection to Host-1: ping192.168.1.10. The ping should fail. This indicates a layer-3 problem between the 3620-2 and Host-1.13. Examine the 3620-2’s routing table: show ip route. Notice that there are only two connected routes (192.168.2.0/24 and 192.168.1.0/24), but no RIP routes.14. Access the 3620-1 router and examine RIP’s configuration.Choose 3620-1, examine the routing table: show ip protocol. What networks are advertised by the 3620-1? You should see 192.168.1.0 and 192.168.11.0. Obviously, serial 1/1’s interface isn’t included since 192.168.2.0 is not configured.15. Fix the problem with the 3620-1’s RIP configuration.Fix this configuration problem:: configure terminal, router rip, no network 192.168.11.0, network192.168.1.0, end. examine the routing table: show ip protocol.16. Test connectivity to Host-3: ping192.168.3.10.The ping should be successful. Save the configuration on the router: copy running-config startup-config.17. Now test connectivity between Host-1 and Host-3.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-1.Test connectivity to Host-3: ping192.168.3.10. The ping should be successful.EXERCISE 15 Configuring OSPF1. On the 3620-1, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up. Examine the IP addresses configured on the 3620-1 and look at its routing table.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1.On the 3620-1, use the show interfaces command to verify your configuration. If fa0/0 and s1/1 are not up, go into the interfaces (fa0/0 and s1/1) and enable them: configure terminal, interface type port, no shutdown, end, show interfaces. Use the show ip route command. You should have two connected networks: 192.168.1.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.2. On the 3620-2, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up. Examine the IP addresses configured on the 3620-2 and look at its routing table.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-2. On the 3620-2, verify that the fa0/0 and s1/1 interfaces are up. If not, bring them up: configure terminal, interface type port, no shutdown, end, show interfaces. Use the show interfaces command to verify that the IP addresses you configured are still there. Use the show ip route command. You should have two connected networks: 192.168.3.0 connected to fa0/0 and 192.168.2.0 connected to s1/1.3. Test connectivity between Host-1 and the 3620-1.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-1. From Host-1, ping the 3620-1: ping192.168.1.1. The ping should be successful.4. Test connectivity between Host-3 and the 3620-2.At the top of the simulator in the menu bar, click on the eStations icon and choose Host-3. From Host-3, ping the 3620-2 router: ping192.168.3.1. The ping should be successful. 5. From Host-3, ping Host 1:ping192.168.1.10. The ping should fail: there is no route from the 3620-2 to this destination (look at the 3620-2’s routing table: it doesn’t list 192.168.1.0/24).6. Enable OSPF on the 3620-1 and 3620-2 routers, using a process ID of 1, and put all interfaces in area 0.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1. On the 3620-1 router, configure the following: configure terminal, router ospf1, network0.0.0.0 255.255.255.255 area 0, end. At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1.7.On the 3620-2 router, configure the following: configure terminal, router ospf 1,network 0.0.0.0 255.255.255.255 area 0, end.8. On the 3620-2, verify the operation of OSPF. Is either router a DR or BDR on the WAN link?At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-2. Use the show ip protocols command to make sure that OSPF is configured—check for the neighboring router’s update. Use the show ip route command and look for the remote LAN network number as a RIP (O) entry in the routing table. Use the show ip ospf neighbor command to view your neighboring router. Neither should be a DR or BDR on the serial link, since point-to-point connectio ns don’t use DRs and BDRs.9. On the 3620-1, verify the operation of OSPF.At the top of the simulator in the menu bar, click on the eRouters icon and choose 3620-1. Use the show ip protocols command to make sure that OSPF is configured—check for the neig hboring router’s update. Use the show ip route command and look for the remote。
