Pro Domain 3: Network Connectivity

You have two routers connected as shown in the network diagram. All networks shown in the diagram are part of the subnetted 172.19.0.0 network. You want to use OSPF for routing on the network. However, you do not want information about the networks connected to the Fa0/0 interfaces to be shared using OSPF. In this lab, your task is to: Use the show ip interface command to identify the IP address and mask for each interface before configuring OSPF. Configure RouterA to share information about the networks connected to the Fa0/1 and Fa0/1/0 interfaces using OSPF area 0. Configure RouterB to share information about the networks connected to the Fa0/1 and Fa0/1/0 interfaces using OSPF area 0. Neither router should share information about the network connected to its Fa0/0 interface.

Configure RouterA. Select RouterA. Press Enter to get started. At the RouterA> prompt, type enable and press Enter. At the RouterA# prompt, type config t and press Enter. At the RouterA(config)# prompt, type router ospf 100 and press Enter. At the RouterA(config-router)# prompt, type network 172.19.0.208 0.0.0.15 area 0 and press Enter. At the RouterA(config-router)# prompt, type network 172.19.0.0 0.0.0.127 area 0 and press Enter. Press Ctrl + Z. At the RouterA# prompt, type copy run start and press Enter. Press Enter to begin building the configuration. Configure RouterB. Select RouterB. Press Enter to get started. At the RouterB> prompt, type enable and press Enter. At the RouterB# prompt, type config t and press Enter. At the RouterB(config)# prompt, type router ospf 100 and press Enter. At the RouterB(config-router)# prompt, type network 172.19.0.160 0.0.0.31 area 0 and press Enter. At the RouterB(config-router)# prompt, type network 172.19.0.0 0.0.0.127 area 0 and press Enter. Press Ctrl + Z. At the RouterB# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

Your branch office is expanding, and you have added a new subnet. The new subnet currently has a single switch, Branch4. The switch connects through its FastEthernet0/24 interface to the FastEthernet0/1 interface on the router. The new subnet uses 192.168.12.0 as the subnet address for its default subnet mask. In this lab, your task is to complete the configuration of both new devices as follows: On the SFO router:Configure the FastEthernet0/1 interface with the last available IP address on the subnet.Bring the interface up.Add the description Link to Branch4 to the FastEthernet0/1 interface.Save your changes. On the Branch4 switch:Assign the switch the fourth available IP address on the subnet.Configure the Branch4 switch as the default gateway.Add a description Link to SFO to the FastEthernet0/24 interface.Save your changes.

Configure the SFO FastEthernet0/1 interface. Select SFO. Press Enter to get started. At the SFO> prompt, type enable and press Enter. At the SFO# prompt, type configure terminal and press Enter. At the SFO(config)# prompt, type interface FastEthernet0/1 and press Enter. At the SFO(config-if)# prompt, type ip address 192.168.12.254 255.255.255.0 and press Enter. At the SFO(config-if)# prompt, type no shutdown and press Enter. At the SFO(config-if)# prompt, type description Link to Branch4 and press Enter. At the SFO(config-if)# prompt, type exit and press Enter. At the SFO(config)# prompt, type exit and press Enter. At the SFO# prompt, type copy run start and press Enter. Press Enter to begin building the configuration. Configure the Branch4 switch. Select Branch4. Press Enter to get started. At the Branch4> prompt, type enable and press Enter. At the Branch4# prompt, type configure terminal and press Enter. At the Branch4(config)# prompt, type interface Vlan1 and press Enter. At the Branch4(config-if)# prompt, type ip address 192.168.12.4 255.255.255.0 and press Enter. At the Branch4(config-if)# prompt, type interface FastEthernet0/24 and press Enter. At the Branch4(config-if)# prompt, type description Link to SFO and press Enter. At the Branch4(config-if) prompt, type exit and press Enter. At the Branch4(config)# prompt, type ip default-gateway 192.168.12.254 and press Enter. At the Branch4(config)# prompt, type exit and press Enter. At the Branch4# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You are configuring the IP addresses on the SFO router FastEthernet interfaces. Subnet 1 is connected to FastEthernet0/0 and has 1,178 hosts. Subnet 2 is connected to FastEthernet0/1 and has 508 hosts. To determine which subnet mask will work for the 172.16.0.0 network, look at the number of hosts required for each subnet. Subnet1 (connected to FastEthernet0/0) has 1,178 hosts. To support 1,178 hosts, a subnet mask of /21 is required (11 host bits in the 2n - 2 formula will afford 2,046 host addresses in the subnet). Subnet2 (connected to FastEthernet0/1) has 508 hosts. To support 508 hosts, a subnet mask of /23 is required (9 host bits in the 2n - 2 formula will afford 510 host addresses in the subnet). In this lab, your task is to subnet the 172.16.0.0 network to provide sufficient host addresses for both subnets while minimizing wasted IP addresses. Choose one subnet mask for each subnet. The masks should provide enough host addresses without wasting IP addresses. Assign IP addresses and correct subnet masks to the SFO interfaces connected to the switches in this order:For FastEthernet0/0, use the second possible subnet and the last address on the subnet.The second possible subnet: 172.16.8.0/21 (172.16.0.0/21 is the first possible subnet, 172.16.8.0/21 is the second possible subnet, and 172.16.16.0/21 is the third possible subnet.)The last possible IP address in the subnet: 172.16.15.254255.255.248.0 is the decimal version of a 21-bit mask.For FastEthernet0/1, use the next available subnet that does not overlap and the last address on the subnet.The next available subnet that does not overlap: 172.16.16.0/23 (172.16.14.0/23 is the eighth possible subnet, and 172.16.16.0/23 is the ninth possible subnet.)The last possible IP address in the subnet: 172.16.17.254255.255.254.0 is the decimal version of a 23-bit mask. Enable both interfaces. Save your changes to the startup-config file.

Find the DCE interface. Select RouterA. Press Enter to get started. At the RouterA> prompt, type show controllers s0/0/0 and press Enter. Select RouterB. Press Enter to get started. At the RouterB> prompt, type show controllers s0/0/1 and press Enter. RouterB has the DCE interface. Configure RouterB. At the RouterB> prompt, type enable and press Enter. At the RouterB# prompt, type config t and press Enter. At the RouterB(config)# prompt, type interface s0/0/1 and press Enter. At the RouterB(config-if)# prompt, type ip address 192.168.2.26 255.255.255.252 and press Enter. At the RouterB(config-if)# prompt, type clock rate 9600 and press Enter. At the RouterB(config-if)# prompt, type no shutdown and press Enter. Press Ctrl + Z. At the RouterB# prompt, type copy run start and press Enter. Press Enter to begin building the configuration. Configure RouterA. At the RouterA> prompt, type enable and press Enter. At the RouterA# prompt, type config t and press Enter. At the RouterA(config)# prompt, type interface s0/0/0 and press Enter. At the RouterA(config-if)# prompt, type ip address 192.168.2.25 255.255.255.252 and press Enter. At the RouterA(config-if)# prompt, type no shutdown and press Enter. Press Ctrl + Z. At the RouterA# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You have just connected two routers through their serial ports in a back-to-back configuration. You've already configured IP addresses on the Fa0/0 and Fa0/1 interfaces for both routers and have configured a static route on each router for the networks accessible through the other router. You need to complete the configuration by configuring the serial link between the two routers. Remember that a 30-bit mask has a magic number of 4. Valid subnets are 192.168.2.0, 192.168.2.4, 192.168.2.8, etc. The seventh subnet is 192.168.2.24. The first valid address on that subnet is 192.168.2.25. The last valid address on that subnet is 192.168.2.26. A 30-bit mask uses a mask value of 255.255.255.252. In this lab, your task is to: Assign an IP address to each serial interface. Use the seventh subnet on network 192.168.2.0 using a 30-bit mask:For S0/0/0 on RouterA, assign the first address on the subnet.For S0/0/1 on RouterB, assign the last address on the subnet. Use the show controllers command to identify the DCE device. On the DCE interface, configure a clock rate of 9600 using the clock rate command. Bring both interfaces up. Save the changes on both routers.

Find the DCE interface. Select RouterA. Press Enter to get started. At the RouterA> prompt, type show controllers s0/0/0 and press Enter. Select RouterB. Press Enter to get started. At the RouterB> prompt, type show controllers s0/0/1 and press Enter. RouterB has the DCE interface. Configure RouterB. At the RouterB> prompt, type enable and press Enter. At the RouterB# prompt, type config t and press Enter. At the RouterB(config)# prompt, type interface s0/0/1 and press Enter. At the RouterB(config-if)# prompt, type ip address 192.168.2.26 255.255.255.252 and press Enter. At the RouterB(config-if)# prompt, type clock rate 9600 and press Enter. At the RouterB(config-if)# prompt, type no shutdown and press Enter. Press Ctrl + Z. At the RouterB# prompt, type copy run start and press Enter. Press Enter to begin building the configuration. Configure RouterA. At the RouterA> prompt, type enable and press Enter. At the RouterA# prompt, type config t and press Enter. At the RouterA(config)# prompt, type interface s0/0/0 and press Enter. At the RouterA(config-if)# prompt, type ip address 192.168.2.25 255.255.255.252 and press Enter. At the RouterA(config-if)# prompt, type no shutdown and press Enter. Press Ctrl + Z. At the RouterA# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You have two routers connected as shown in the network diagram. The Jujuy router is already configured to share route information using OSPF on Area 0. When configuring OSPF, routers do not need to use the same process ID, but networks must be defined in the same area. When adding network statements, include the wildcard mask and the area number (in this case, area 0). All interfaces have been configured and enabled. In this lab, your task is to: Configure the Salta router to share routing information using OSPF with the Jujuy router. When you are finished, save your changes.

Select Salta. Press Enter to get started. At the Salta> prompt, type enable and press Enter. At the Salta# prompt, type config t and press Enter. At the Salta(config)# prompt, type router ospf 100 and press Enter. At the Salta(config-router)# prompt, type network 192.168.1.0 0.0.0.255 area 0 and press Enter. At the Salta(config-router)# prompt, type network 192.168.2.0 0.0.0.255 area 0 and press Enter. At the Salta(config-router)# prompt, type network 172.17.150.140 0.0.0.3 area 0 and press Enter. Press Ctrl + Z. At the Salta# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You have a single Cisco router named Atlanta that connects to two subnets, as shown in the network diagram. Determine which subnet mask will work for the 172.30.0.0 network by looking at the number of hosts required for each subnet: FastEthernet0/0 has 10 hosts. For 10 hosts, a subnet mask of /28 is required (4 host bits in the 2n - 2 formula will afford 14 host addresses in the subnet). FastEthernet0/1 has 31 hosts. For 31 hosts, a subnet mask of /26 is required (6 host bits in the 2n - 2 formula will afford 62 host addresses in the subnet). In this lab, your task is to subnet the 172.30.0.0/24 network to provide sufficient host addresses for both subnets while minimizing wasted IP addresses. Use a 26-bit subnet mask on both subnets. Although there will be wasted bits for the subnet connected to FastEthernet0/0, /26 is the smallest subnet mask that will work for both subnets. Configure the IP address on the two router interfaces as follows:For FastEthernet0/0, use the first possible subnet and the last address on the subnet.The first possible subnet: 172.30.0.0/26The last address on the subnet: 172.30.0.62 (172.30.0.63 is the broadcast address for the subnet.)For FastEthernet0/1, use the fourth possible subnet and the last address on the subnet.The fourth possible subnet: 172.30.0.192/26The last address on the subnet: 172.30.0.254 (172.30.0.255 is the broadcast address for the subnet.) Enable both interfaces. Save your changes to the startup-config file.

Select ATLANTA. Press Enter to get started. At the ATLANTA> prompt, type enable and press Enter. At the ATLANTA# prompt, type configure terminal and press Enter. At the ATLANTA(config)# prompt, type interface FastEthernet0/0 and press Enter. At the ATLANTA(config-if)# prompt, type ip address 172.30.0.62 255.255.255.192 and press Enter. At the ATLANTA(config-if)# prompt, type no shutdown and press Enter. At the ATLANTA(config-if)# prompt, type interface FastEthernet0/1 and press Enter. At the ATLANTA(config-if)# prompt, type ip address 172.30.0.254 255.255.255.192 and press Enter. At the ATLANTA(config-if)# prompt, type no shutdown and press Enter. At the ATLANTA(config-if)# prompt, type exit and press Enter. At the ATLANTA(config)# prompt, type exit and press Enter. Save your changes to the startup-config file.At the ATLANTA# prompt, type copy run start and press Enter.Press Enter to begin building the configuration.

You are in the process of configuring the Branch1 switch. Use the show cdp neighbors detail command to find the IP address assigned to the FastEthernet0/0 interface on router SFO. In this lab, your task is to: Configure the switch with the following parameters:IP address: 192.168.11.250Subnet mask: 255.255.255.0 Configure the switch to use the FastEthernet0/0 interface on the SFO router as the default gateway. Save your changes to the startup-config file.

Select Branch1. Press Enter to get started. At the Branch1 > prompt, type enable and press Enter. At the Branch1# prompt, type show cdp neighbors detail and press Enter. Find the IP address for the SFO router. At the Branch1# prompt, type config t and press Enter. At the Branch1(config)# prompt, type interface vlan1 and press Enter. At the Branch1(config-if)# prompt, type ip address 192.168.11.250 255.255.255.0 and press Enter. At the Branch1(config-if)# prompt, type exit and press Enter. At the Branch1(config)# prompt, type ip default-gateway 192.168.11.254 and press Enter. At the Branch1(config)# prompt, type exit and press Enter. At the Branch1# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You manage the network shown in the diagram. Users on the networks connected to the R1 router report that they are unable to contact computers connected to the R3 router. Documentation for the network configuration is as follows: Subnets are assigned addresses as follows: For DCE devices, the clock rate is set to 56000. All routers use OSPF with area 0 to share information about all connected networks. No static routes are allowed. In this lab, your task is to: Troubleshoot and correct the problem. Take only the necessary actions to correct the problem you find. Use the information above to identify misconfigurations and to correct problems.

Select R1. Press Enter to get started. At the R1> prompt, type enable and press Enter. At the R1# prompt, type ping 192.168.3.30 or ping 192.168.3.158 and press Enter. At the R1# prompt, type show ip route and press Enter.Notice that R1 knows about some of the networks connected to R2, but it does not know about network 172.18.0.64/30, nor has it learned any routes from R3. This means the problem is on either R2 or R3, possibly on the serial link between the two routers. Select R2. Press Enter to get started. At the R2> prompt, type enable and press Enter. At the R2# prompt, type show ip route and press Enter.Because network 172.18.0.64/30 shows as a directly connected route in the routing table, you know that the interface is up and has been configured with a correct IP address. At the R2# prompt, type show ip protocols and press Enter. Verify the following values of the OSPF configuration:OSPF is running.Network statements include the 172.18.0.64/30Network statements use the correct area number.Notice that there is a network statement for network 172.18.0.0/30. However, this statement will not enable OSPF on the 172.18.0.64/30 network. On R2, modify the network statement to use the correct IP address and wildcard mask so that OSPF is enabled on the Serial0/1/1 interface.At the R2# prompt, type conf t and press Enter.At the R2(config)# prompt, type router ospf 200 and press Enter.At the R2(config-router)# prompt, type no network 172.18.0.0 0.0.0.3 area 0 and press Enter.At the R2(config-router)# prompt, type network 172.18.0.64 0.0.0.3 area 0 and press Enter.Press Ctrl + Z. At the R1# prompt, type show ip route and press Enter to verify the fix. At the R2# prompt, type show ip route and press Enter to verify the fix. At the R3# prompt, typpe show ip route and press Enter to verify the fix. At the R1# prompt, type ping 192.168.3.30 or ping 192.168.3.158 and press Enter to verify connectivity.

Your branch office is connected to the main office and the internet through the SFO router. Both serial interfaces connecting the SFO router to the main office and the internet have been configured and are up. You need to configure static routes on the SFO router for each destination. Use the next hop address when assigning the static routes. Your ISP's address is 160.12.99.1. Use the show cdp neighbors detail command to discover the next hop address for the 10.0.0.0 network. In this lab, your task is to: Configure a static route to 10.0.0.0/8 network. Configure a default route to the internet. Save your changes to the startup-config file.

Select SFO. Press Enter to get started. At the SFO> prompt, type enable and press Enter. At the SFO# prompt, type configure terminal and press Enter. At the SFO(config)# prompt, type ip route 10.0.0.0 255.0.0.0 172.17.12.98 and press Enter. At the SFO(config)# prompt, type ip route 0.0.0.0 0.0.0.0 160.12.99.1 and press Enter. At the SFO(config)# prompt, type exit and press Enter. At the SFO# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

You are working with an SFO router that is connected to two other routers through serial interfaces. In this lab, your task is to: Use the show ip route command. Answer the questions.

Select SFO. Press Enter to get started. At the SFO> prompt, type enable and press Enter. At the SFO# prompt, type show ip route and press Enter.

You just installed a new switch, and you want to manage the switch from a remote location. In this lab, your task is to set up remote management for the switch as follows: Configure the VLAN 1 interface with the following:IP address: 192.168.11.250Subnet mask: 255.255.255.0 Configure the switch to use 192.168.11.254 as the default gateway. Verify the configurations using the show run command. Save your changes to the startup-config file.

Select Switch. Configure the IP address for the switch. Press Enter to get started. At the Switch> prompt, type enable and press Enter. At the Switch# prompt, type configure terminal and press Enter. At the Switch(config)# prompt, type interface Vlan1 and press Enter. At the Switch(config-if)# prompt, type ip address 192.168.11.250 255.255.255.0 and press Enter. At the Switch(config)# prompt, type ip default-gateway 192.168.11.254 and press Enter to configure the default gateway address. At the prompt, type exit and press Enter. At the prompt, type show run and press Enter to verify the configuration. Save your changes. At the Switch# prompt, type copy run start and press Enter. Press Enter to begin building the configuration.

In this lab, you'll explore how ping, traceroute, and the default gateway affect device communication. Devices on this network use the following IP addresses: Select Wrk1. At the command prompt, type ping 192.168.11.2 and press Enter to verify that you can ping Wrk2. The ping succeeds. At the command prompt, type tracert 192.168.11.2 and press Enter and trace the route to Wrk2. Notice that the switch does not show in the path because the switch is a Layer 2 device and uses the MAC address to pass frames between ports. Ping is a Layer 3 tool that uses IP addresses. Select Branch1. Press Enter to get started. At the Branch1> prompt, type enable and press Enter. At the Branch1# prompt, type show ip interface brief and press Enter. Notice that the Branch1 switch does not have an assigned IP address. The VLAN 1 interface shows unassigned in the IP-Address column. At the Branch1# prompt, type ping 192.168.11.1 and press Enter. The ping fails because the switch does not have an IP address. Configure Vlan1 on the Branch1 switch with the following IP address: 192.168.1.1 with a mask of 255.255.255.0. At the Branch1# prompt, type conf t and press Enter. At the Branch1(config)# prompt, type int vlan 1 and press Enter. At the Branch1(config-if)# prompt, type ip address 192.168.1.1 255.255.255.0 and press Enter. Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.11.1 and press Enter to ping Wrk1. The ping fails because the IP address assigned to the switch is not on the same subnet as the IP address assigned to the workstation. Even though they are on the same network segment, the IP addresses are not on the same subnet. At the Wrk1 prompt, type ping 192.168.11.2 and press Enter to ping Wrk2. The ping succeeds. Switching takes place regardless of the IP address configured on a switch. Change the IP address on Branch1 to the correct IP address. At the Branch1# prompt, type conf t and press Enter. At the Branch1(config)# prompt, type int vlan 1 and press Enter. At the Branch1(config-if)# prompt, type ip address 192.168.11.250 255.255.255.0 and press Enter. Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.11.1 and press Enter to ping Wrk1. The ping succeeds because the switch now has an IP address on the same subnet as the workstations. On Wrk1, at the command prompt, type tracert 192.168.11.2 and press Enter and trace the path between Wrk1 and Wrk2. Setting an IP address on the switch does not affect the trace route output because the switch is operating at Layer 2. On Branch1, at the Branch1# prompt, type ping 192.168.11.254 and press Enter to ping the SFO Fa0/0 interface. The ping fails. At the Branch1# prompt, type show ip interface brief and press Enter. Select SFO. Press Enter to get started. At the SFO> prompt, type enable and press Enter. At the SFO# prompt, type show ip interface brief and press Enter. Notice that Fa0/0 on the router is administratively down. The ping fails because the connected device is not up. Bring up the SFO Fa0/0 interface on the router. At the SFO# prompt, type conf t and press Enter. At the SFO(config)# prompt, type int fa0/0 and press Enter. At the SFO(config-if)# prompt, type no shutdown and press Enter. Press Ctrl + Z. On Branch1, at the Branch1# prompt, type ping 192.168.11.254 and press Enter to ping the SFO Fa0/0 interface. After fixing the problem, bringing the interface up makes the ping succeed. At the Wrk1 prompt, type ping 192.168.12.1 and press Enter to ping Wrk12. Wrk1 can ping Wrk12. The ping goes from the workstation to the router to the destination workstation on the other subnet. At the Branch1# prompt, type ping 192.168.12.1 and press Enter to ping Wrk12. The ping from the switch fails because the destination is not on the same subnet and the switch is not configured with a default gateway address. On Branch1, configure 192.168.11.254 as the default gateway. At the Branch1# prompt, type conf t and press Enter. At the Branch1(config)# prompt, type int vlan 1 and press Enter. At the Branch1(config-if)# prompt, type ip default-gateway 192.168.11.254 and press Enter. Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.12.1 and press Enter to ping Wrk12. The ping succeeds because the packet addressed to the other subnet is sent to the router. On Wrk1, at the command prompt, type tracert 192.168.12.1 and press Enter and trace the path between Wrk1 and Wrk12. Layer 2 switches do not alter the IP addresses in a packet, so they do not show up in the trace route path.

Select Wrk1. At the command prompt, type ping 192.168.11.2 and press Enter to verify that you can ping Wrk2.The ping succeeds. At the command prompt, type tracert 192.168.11.2 and press Enter and trace the route to Wrk2.Notice that the switch does not show in the path because the switch is a Layer 2 device and uses the MAC address to pass frames between ports. Ping is a Layer 3 tool that uses IP addresses. Select Branch1. Press Enter to get started. At the Branch1> prompt, type enable and press Enter. At the Branch1# prompt, type show ip interface brief and press Enter.Notice that the Branch1 switch does not have an assigned IP address. The VLAN 1 interface shows unassigned in the IP-Address column. At the Branch1# prompt, type ping 192.168.11.1 and press Enter.The ping fails because the switch does not have an IP address. Configure Vlan1 on the Branch1 switch with the following IP address: 192.168.1.1 with a mask of 255.255.255.0.At the Branch1# prompt, type conf t and press Enter.At the Branch1(config)# prompt, type int vlan 1 and press Enter.At the Branch1(config-if)# prompt, type ip address 192.168.1.1 255.255.255.0 and press Enter.Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.11.1 and press Enter to ping Wrk1.The ping fails because the IP address assigned to the switch is not on the same subnet as the IP address assigned to the workstation. Even though they are on the same network segment, the IP addresses are not on the same subnet. At the Wrk1 prompt, type ping 192.168.11.2 and press Enter to ping Wrk2.The ping succeeds. Switching takes place regardless of the IP address configured on a switch. Change the IP address on Branch1 to the correct IP address.At the Branch1# prompt, type conf t and press Enter.At the Branch1(config)# prompt, type int vlan 1 and press Enter.At the Branch1(config-if)# prompt, type ip address 192.168.11.250 255.255.255.0 and press Enter.Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.11.1 and press Enter to ping Wrk1.The ping succeeds because the switch now has an IP address on the same subnet as the workstations. On Wrk1, at the command prompt, type tracert 192.168.11.2 and press Enter and trace the path between Wrk1 and Wrk2.Setting an IP address on the switch does not affect the trace route output because the switch is operating at Layer 2. On Branch1, at the Branch1# prompt, type ping 192.168.11.254 and press Enter to ping the SFO Fa0/0 interface.The ping fails. At the Branch1# prompt, type show ip interface brief and press Enter. Select SFO. Press Enter to get started. At the SFO> prompt, type enable and press Enter. At the SFO# prompt, type show ip interface brief and press Enter.Notice that Fa0/0 on the router is administratively down. The ping fails because the connected device is not up. Bring up the SFO Fa0/0 interface on the router.At the SFO# prompt, type conf t and press Enter.At the SFO(config)# prompt, type int fa0/0 and press Enter.At the SFO(config-if)# prompt, type no shutdown and press Enter.Press Ctrl + Z. On Branch1, at the Branch1# prompt, type ping 192.168.11.254 and press Enter to ping the SFO Fa0/0 interface.After fixing the problem, bringing the interface up makes the ping succeed. At the Wrk1 prompt, type ping 192.168.12.1 and press Enter to ping Wrk12.Wrk1 can ping Wrk12. The ping goes from the workstation to the router to the destination workstation on the other subnet. At the Branch1# prompt, type ping 192.168.12.1 and press Enter to ping Wrk12.The ping from the switch fails because the destination is not on the same subnet and because the switch is not configured with a default gateway address. On Branch1, configure 192.168.11.254 as the default gateway.At the Branch1# prompt, type conf t and press Enter.At the Branch1(config)# prompt, type int vlan 1 and press Enter.At the Branch1(config-if)# prompt, type ip default-gateway 192.168.11.254 and press Enter.Press Ctrl + Z. At the Branch1# prompt, type ping 192.168.12.1 and press Enter to ping Wrk12.The ping succeeds because the packet addressed to the other subnet is sent to the router. On Wrk1, at the command prompt, type tracert 192.168.12.1 and press Enter and trace the path between Wrk1 and Wrk12.Layer 2 switches do not alter the IP addresses in a packet, so they do not show up in the trace route path.