12.5.13 Packet Tracer - Troubleshoot Enterprise Networks (Answers)

12.5.13 Packet Tracer - Troubleshoot Enterprise Networks Answers

Topology

12.5.13 Packet Tracer - Troubleshoot Enterprise Networks

Objectives

Part 1: Verify Switching Technologies
Part 2: Verify DHCP
Part 3: Verify Routing
Part 4: Verify WAN Technologies
Part 5: Verify Connectivity

Scenario

This activity uses a variety of technologies that you have encountered during your CCNA studies, including IPv4 routing, IPv6 routing, port security, EtherChannel, DHCP, and NAT. Your task is to review the requirements, isolate and resolve any problems, and then document the steps you took to verify the requirements.

The company replaced routers R1 and R3 to accommodate a fiber connection between the locations. Configurations from the previous routers with serial connections were modified and applied as a starting configuration. IPv6 is being tested on a small portion of the network and needs to be verified.

Note: Passwords have been removed for ease of troubleshooting in this exercise. The typical password protections should be reapplied; however, the activity will not grade those items.

Addressing Table

Device	Interface	IP Address / Prefix	Default Gateway
R1	G0/0/1	192.168.10.1 /24	N/A
	S0/1/0	10.1.1.1 /30	N/A
	G0/0/0	10.3.3.1 /30	N/A
R2	G0/0	209.165.200.225 /30	N/A
	G0/0	2001:db8:b:209::1/64	N/A
	G0/1	192.168.20.1 /24	N/A
	G0/1	2001:db8:b:20::1/64	N/A
	S0/0/0	10.1.1.2 /30	N/A
	G0/1/0	10.2.2.1 /30	N/A
	G0/1/0	2001:db8:b:10:2::1/64	N/A
R3	G0/1.30	192.168.30.1 /24	N/A
	G0/1.40	192.168.40.1 /24	N/A
	G0/1.50	192.168.50.1 /24	N/A
	G0/1.50	2001:db8:b:50::1/64	N/A
	G0/1.99	N/A	N/A
	G0/1/0	10.3.3.2 /30	N/A
	G0/2/0	10.2.2.2 /30	N/A
	G0/2/0	2001:db8:b:10:2::2/64	N/A
S1	VLAN10	192.168.10.2 /24	192.168.10.1
S2	VLAN99	192.168.99.2 /24	N/A
S3	VLAN99	192.168.99.3 /24	N/A
S4	VLAN99	192.168.99.4 /24	N/A
PC1	NIC	IPv4 DHCP assigned	IPv4 DHCP assigned
PC2	NIC	IPv4 DHCP assigned	IPv4 DHCP assigned
PC3	NIC	IPv4 DHCP assigned	IPv4 DHCP assigned
PC4	NIC	IPv4 DHCP assigned	IPv4 DHCP assigned
PC4	NIC	2001:db8:b:50::10/64	fe80::3
TFTP Server	NIC	192.168.20.254 /24	192.168.20.1
TFTP Server	NIC	2001:db8:b:20::254/64	fe80::2

Instructions

Part 1: Verify Switching Technologies

a. Port security is configured to only allow PC1 to access S1's F0/3 interface. All violations should disable the interface.

Issue the command on S1 to display the current port security status.

S1# show port-security
S1#

b. Enter interface configuration mode for interface F0/3 and set up port security.

S1(config)# interface fastethernet 0/3
S1(config-if)# switchport port-security
S1(config-if)# switchport port-security mac-address sticky

c. Devices in the LAN on S1 should be in VLAN 10. Display the current state of VLAN configuration.

S1# show vlan

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/2, Fa0/5, Fa0/6
                                                Fa0/7, Fa0/8, Fa0/9, Fa0/10
                                                Fa0/11, Fa0/12, Fa0/13, Fa0/14
                                                Fa0/15, Fa0/16, Fa0/17, Fa0/18
                                                Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                Fa0/23, Fa0/24, Gig0/1, Gig0/2
10   V10                              active    Fa0/3, Fa0/4
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active

What ports are currently assigned to VLAN 10?

F0/3, F0/4

d. PC1 should be receiving an IP address from the router R1.

Does the PC currently have an IP address assigned?

No, it only has an APIPA address

e. Notice the G0/1 interface on R1 is not in the same VLAN as PC1. Change the G0/1 interface to be a member of VLAN 10 and set portfast on the interface.

S1(config)# interface gigabitethernet 0/1
S1(config-if)# switchport access vlan 10
S1(config-if)# spanning-tree portfast

f. Reset the interface address on PC1 from the GUI or by using the command prompt and the ipconfig /renew command.

C:\> ipconfig /renew

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::202:17FF:FE87:AB7D
   IPv6 Address....................: ::
   IPv4 Address....................: 192.168.10.10
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     192.168.10.1

Does PC1 have an address?

Yes, IP is 192.168.10.10

If not, recheck your steps. Test connectivity to the TFTP Server. The ping should be successful.

C:\> ping 192.168.20.254

Pinging 192.168.20.254 with 32 bytes of data:

Request timed out.
Reply from 192.168.20.254: bytes=32 time=81ms TTL=126
Reply from 192.168.20.254: bytes=32 time=2ms TTL=126
Reply from 192.168.20.254: bytes=32 time=1ms TTL=126

Ping statistics for 192.168.20.254:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 81ms, Average = 28ms

g. The LAN connected to R3 had an additional switch added to the topology. Link aggregation using EtherChannel is configured on S2, S3, and S4. The EtherChannel links should be set to trunk. The EtherChannel links should be set to form a channel without using a negotiation protocol. Issue the command on each switch to determine if the channel is working correctly.
S2:

S2# show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SU)           -      Fa0/1(P) Fa0/2(P)
2      Po2(SU)           -      Fa0/3(P) Fa0/4(P)

S3:

S3# show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SD)           -
3      Po3(SU)           -      Fa0/3(P) Fa0/4(P)

S4:

S4# show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

2      Po2(SU)           -      Fa0/1(P) Fa0/2(P)
3      Po3(SU)           -      Fa0/3(P) Fa0/4(P)

Were there any problems with EtherChannel?

S3 shows Po1 as down (SD)

h. Modify S3 to include ports F0/1 and F0/2 as port channel 1.

S3(config)# interface range fastethernet 0/1 - 2
S3(config-if-range)# channel-group 1 mode on

Check the status of the EtherChannel on S3. It should be stable now. If it is not, check the previous steps.

S3# show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SU)           -      Fa0/1(P) Fa0/2(P)
3      Po3(SU)           -      Fa0/3(P) Fa0/4(P)

i. Verify the trunk status on all switches.
S2:

S2# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Po1         on           802.1q         trunking      99
Po2         on           802.1q         trunking      99
Gig0/1      on           802.1q         trunking      1

Port        Vlans allowed on trunk
Po1         1-1005
Po2         1-1005
Gig0/1      1-1005

Port        Vlans allowed and active in management domain
Po1         1,30,40,50,99
Po2         1,30,40,50,99
Gig0/1      1,30,40,50,99

Port        Vlans in spanning tree forwarding state and not pruned
Po1         1,30,40,50,99
Po2         1,30,40,50,99
Gig0/1      1,30,40,50,99

S3:

S3# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Po1         on           802.1q         trunking      99
Po3         on           802.1q         trunking      99

Port        Vlans allowed on trunk
Po1         1-1005
Po3         1-1005

Port        Vlans allowed and active in management domain
Po1         1,11,30,40,50,99
Po3         1,11,30,40,50,99

Port        Vlans in spanning tree forwarding state and not pruned
Po1         11
Po3         1,11,30,40,50,99

S4:

S4# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Po2         on           802.1q         trunking      99
Po3         on           802.1q         trunking      99

Port        Vlans allowed on trunk
Po2         1-1005
Po3         1-1005

Port        Vlans allowed and active in management domain
Po2         1,30,40,50,99
Po3         1,30,40,50,99

Port        Vlans in spanning tree forwarding state and not pruned
Po2         1,30,40,50,99
Po3         1,30,40,50,99

Were there any issues with trunking?

S2 is using VLAN 1 as the Native VLAN on the link G0/1 interface.

j. Correct the trunk issues on S2.

S2(config)# interface gigabitethernet 0/1
S2(config-if)# switchport trunk native vlan 99

k. Spanning Tree should be set to PVST+ on S2, S3, and S4. S2 should be configured to be the root bridge for all VLANs. Issue the command to display the spanning-tree status on S2.

S2# show spanning-tree summary totals
Switch is in pvst mode
Root bridge for:

l. The command output shows that S2 is not the root bridge for any VLANs. Correct the spanning-tree status on S2.

S2(config)# spanning-tree vlan 1-1005 root primary

m. Check the spanning-tree status on S2 to verify the changes.

S2# show spanning-tree summary totals
Switch is in pvst mode
Root bridge for: default V30 V40 V50 Native

Part 2: Verify DHCP

R1 is the DHCP server for the R1 LAN.
R3 is the DHCP server for all 3 LANs attached to R3.

a. Check the addressing of the PCs.
PC2:

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::201:96FF:FED2:8316
   IPv6 Address....................: ::
   IPv4 Address....................: 192.168.30.55
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     192.168.30.1

PC3:

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2D0:BCFF:FE60:4100
   IPv6 Address....................: ::
   IPv4 Address....................: 192.168.40.24
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     192.168.30.1

PC4:

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::203:E4FF:FE97:A607
   IPv6 Address....................: 2001:DB8:B:50::10
   IPv4 Address....................: 192.168.50.12
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::3
                                     192.168.30.1

Do they all have correct addressing?

No, PC3 and PC4 have incorrect gateways

b. Check the DHCP settings on R3. Filter the output from the show running-config command to start with the DHCP configuration.

R3# show running-config | begin dhcp
ip dhcp excluded-address 192.168.30.1 192.168.30.9
ip dhcp excluded-address 192.168.40.1 192.168.40.9
ip dhcp excluded-address 192.168.50.1 192.168.50.9
!
ip dhcp pool LAN30
 network 192.168.30.0 255.255.255.0
 default-router 192.168.30.1
ip dhcp pool LAN40
 network 192.168.40.0 255.255.255.0
 default-router 192.168.30.1
ip dhcp pool LAN50
 network 192.168.50.0 255.255.255.0
 default-router 192.168.30.1

Are there any issues with the DHCP configurations?

The default-router setting is incorrect on LAN40 and LAN50.

c. Make any necessary corrections and reset the IP addresses on the PCs. Check connectivity to all devices.

R3(config)# ip dhcp pool LAN40
R3(dhcp-config)# network 192.168.40.0 255.255.255.0
R3(dhcp-config)# default-router 192.168.40.1
R3(dhcp-config)# ip dhcp pool LAN50
R3(dhcp-config)# network 192.168.50.0 255.255.255.0
R3(dhcp-config)# default-router 192.168.50.1

Reset the interface address on PC3, PC4 from the GUI or by using the command prompt and the ipconfig /renew command.

PC3:

C:\> ipconfig /renew

   IP Address......................: 192.168.40.24
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: 192.168.40.1
   DNS Server......................: 0.0.0.0

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2D0:BCFF:FE60:4100
   IPv6 Address....................: ::
   IPv4 Address....................: 192.168.40.24
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     192.168.40.1

PC4:

C:\> ipconfig /renew

   IP Address......................: 192.168.50.12
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: 192.168.50.1
   DNS Server......................: 0.0.0.0

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::203:E4FF:FE97:A607
   IPv6 Address....................: 2001:DB8:B:50::10
   IPv4 Address....................: 192.168.50.12
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::3
                                     192.168.50.1

Were you able to ping all IPv4 addresses?

PC1, PC2, PC3 & PC4 should have full connectivity for IPv4 internally. The hosts are not able to ping outside. This problem will be addressed in Part 3.

Part 3: Verify Routing

Verify that the following requirements have been met. If not, complete the configurations.

All routers are configured with OSPF process ID 1 and no routing updates should be sent across interfaces that do not have routers connected.
R3:

R3(config)# router ospf 1
R3(config-router)# passive-interface gigabitethernet 0/1.30
R3(config-router)# passive-interface gigabitethernet 0/1.40
R3(config-router)# passive-interface gigabitethernet 0/1.50

R2:

R2(config)# router ospf 1
R2(config-router)# passive-interface gigabitethernet 0/1

R2 is configured with an IPv4 default route pointing to the ISP and redistributes the default route in the OSPFv2 domain.
R2 is configured with a default IPv6 fully qualified default route pointing to the ISP and redistributes the default route in the OSPFv3 domain.
NAT is configured on R2 and no untranslated addresses are permitted to cross the internet.

a. Check the routing tables on all routers.
R1:

R1# show ip route ospf
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O       10.2.2.0 [110/649] via 10.1.1.2, 00:33:13, Serial0/1/0
                 [110/649] via 10.3.3.2, 00:33:13, GigabitEthernet0/0/0
O    192.168.20.0 [110/649] via 10.1.1.2, 00:33:53, Serial0/1/0
O    192.168.30.0 [110/658] via 10.3.3.2, 00:33:23, GigabitEthernet0/0/0
O    192.168.40.0 [110/658] via 10.3.3.2, 00:33:23, GigabitEthernet0/0/0
O    192.168.50.0 [110/658] via 10.3.3.2, 00:33:23, GigabitEthernet0/0/0

R2:

R2# show ip route ospf
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O       10.3.3.0 [110/649] via 10.2.2.2, 00:33:15, GigabitEthernet0/1/0
O    192.168.10.0 [110/649] via 10.1.1.1, 00:34:00, Serial0/0/0
O    192.168.30.0 [110/11] via 10.2.2.2, 00:33:15, GigabitEthernet0/1/0
O    192.168.40.0 [110/11] via 10.2.2.2, 00:33:15, GigabitEthernet0/1/0
O    192.168.50.0 [110/11] via 10.2.2.2, 00:33:15, GigabitEthernet0/1/0

R3:

R3# show ip route ospf
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O       10.1.1.0 [110/649] via 10.2.2.1, 00:33:26, GigabitEthernet0/2/0
O    192.168.10.0 [110/649] via 10.3.3.1, 00:33:36, GigabitEthernet0/1/0
O    192.168.20.0 [110/2] via 10.2.2.1, 00:33:26, GigabitEthernet0/2/0

Do all of the networks appear on all routers?

All of the networks are in the routing tables. However, the default route is not propagating to R1 and R3, so there is only connectivity to the outside from R2.

b. Ping the Outside Host from R2.

R2# ping 64.100.100.10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.100.100.10, timeout is 2 seconds:
..!!!
Success rate is 60 percent (3/5), round-trip min/avg/max = 0/1/2 ms

Was the ping successful?

Yes. R2 is able to ping the Outside Host (64.100.100.10).

c. Correct the default route propagation.

R2(config)# router ospf 1
R2(config-router)# default-information originate

d. Check the routing tables on R1 and R3 to make certain the default route is present.
R1:

R1# show ip route ospf
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O       10.2.2.0 [110/649] via 10.1.1.2, 00:38:32, Serial0/1/0
                 [110/649] via 10.3.3.2, 00:38:32, GigabitEthernet0/0/0
O    192.168.20.0 [110/649] via 10.1.1.2, 00:39:12, Serial0/1/0
O    192.168.30.0 [110/658] via 10.3.3.2, 00:38:42, GigabitEthernet0/0/0
O    192.168.40.0 [110/658] via 10.3.3.2, 00:38:42, GigabitEthernet0/0/0
O    192.168.50.0 [110/658] via 10.3.3.2, 00:38:42, GigabitEthernet0/0/0
O*E2 0.0.0.0/0 [110/1] via 10.1.1.2, 00:03:47, Serial0/1/0

R3:

R3# show ip route ospf
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O       10.1.1.0 [110/649] via 10.2.2.1, 00:38:43, GigabitEthernet0/2/0
O    192.168.10.0 [110/649] via 10.3.3.1, 00:38:53, GigabitEthernet0/1/0
O    192.168.20.0 [110/2] via 10.2.2.1, 00:38:43, GigabitEthernet0/2/0
O*E2 0.0.0.0/0 [110/1] via 10.2.2.1, 00:03:58, GigabitEthernet0/2/0

e. Test IPv6 connectivity from R2 to Outside Host and TFTP Server. The pings should be successful. Troubleshoot if they are not.

R2# ping 2001:DB8:B:64::10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:B:64::10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

R2# ping 2001:DB8:B:20::254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:B:20::254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

f. Test IPv6 connectivity from R2 to PC4. If the ping fails be sure to check that the IPv6 addressing matches the Addressing Table.

R2# ping 2001:DB8:B:50::10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:B:50::10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

g. Test IPv6 connectivity from R3 to Outside Host. If the ping fails, check the IPv6 routes on R3. Be sure to validate the default route originating from R2. If the route does not appear, modify the IPv6 OSPF configuration on R2.

R3# ping 2001:DB8:B:64::10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:B:64::10, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

R2(config)# ipv6 router ospf 1
R2(config-rtr)# default-information originate

R3# ping 2001:DB8:B:64::10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:B:64::10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

h. Check connectivity from R2 to Outside Host. The ping should be successful.

Part 4: Verify WAN Technologies

The serial link between R1 and R2 is used as a backup link in case of failure and should only carry traffic if the fiber link is unavailable.
The Ethernet link between R2 and R3 is a fiber connection.
The Ethernet link between R1 and R3 is a fiber connection and should be used to forward traffic from R1.

a. Take a close look at the routing table on R1.

Are there any routes using the serial link?

Yes. Traffic for the 192.168.20.0 network and the default route are using S0/1/0 as opposed to G0/0/0.

Use the traceroute command to verify any suspicious paths.

R1# traceroute 192.168.20.254
Type escape sequence to abort.
Tracing the route to 192.168.20.254

  1   10.1.1.2        1 msec    1 msec    1 msec
  2   192.168.20.254  1 msec    9 msec    0 msec

Notice the traffic is being sent via the S0/1/0 interface as opposed to the G0/0/0 interface.

b. The original configurations that came from the previous serial WAN connections were transferred to the new devices. Compare the G0/0/0 interface and Serial0/1/0 interface settings. Notice they both have an OSPF cost value set. Remove the OSPF cost setting from the G0/0/0 interface. It will also be necessary to remove the setting on the link on R3 that connects to R1.
R1:

R1(config)# interface gigabitethernet 0/0/0
R1(config-if)# no ip ospf cost 648

R3:

R3(config)# interface gigabitethernet 0/1/0
R3(config-if)# no ip ospf cost 648

c. Reissue the traceroute command from R1 to verify that the path has changed.

R1# traceroute 192.168.20.254
Type escape sequence to abort.
Tracing the route to 192.168.20.254

  1   10.3.3.2        0 msec    0 msec    0 msec
  2   10.2.2.1        0 msec    0 msec    0 msec
  3   192.168.20.254  0 msec    0 msec    0 msec

d. The change has been made to direct traffic over the faster link, however the backup route needs to be tested. Shut down the G0/2/0 interface on R3 and test connectivity to the TFTP Server and Outside Host.

R3(config)# interface gigabitethernet 0/2/0
R3(config-if)# shutdown

R1# ping 192.168.20.254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.20.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/8/25 ms

R1# ping 64.100.100.10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.100.100.10, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

Were the pings successful?

TFTP Server can be reached; however, Outside Host cannot be reached. Students should think about other causes for the lack of connectivity. In this case, it is a problem with NAT not being set as inside on the Serial interface on R2.

e. R2 is required to perform NAT for all internal networks. Check the NAT translations on R2.

R2# show ip nat translations
R2#

f. Notice that the list is empty if you have only attempted to ping from R1. Attempt a ping from R3 to Outside Host and recheck the NAT translations on R2. Issue the command to display the current NAT statistics which will also provide the interfaces involved in NAT.

R2# show ip nat statistics
Total translations: 0 (0 static, 0 dynamic, 0 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: GigabitEthernet0/1 , GigabitEthernet0/1/0
Hits: 0  Misses: 0
Expired translations: 0
Dynamic mappings:

g. Set the Serial 0/0/0 interface as an inside interface to translate addresses.

R2(config)# interface serial 0/0/0
R2(config-if)# ip nat inside

h. Test connectivity to Outside Host from R1. The ping should now be successful. Re-enable the G0/2/0 interface on R3.

R1# ping 64.100.100.10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.100.100.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/12 ms

R2# show ip nat statistics
Total translations: 5 (0 static, 5 dynamic, 5 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: GigabitEthernet0/1 , Serial0/0/0 , GigabitEthernet0/1/0
Hits: 5  Misses: 13
Expired translations: 0
Dynamic mappings:

R3(config)# interface gigabitethernet 0/2/0
R3(config-if)# no shutdown

Part 5: Verify Connectivity

Devices should be configured according to the Addressing Table.
Every device should be able to ping every other device internally. The internal PCs should be able to ping the Outside Host.
PC4 should be able to ping the TFTP Server and the Outside Host using IPv6.

Device Configs - Final

ROUTER R1

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR ROUTER R1
!--- Usage: open the R1 CLI tab and paste this whole file at the R1> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 4: Verify WAN Technologies
! --------------------------------------------------------------

!--- b. Remove the OSPF cost left over from the old serial link on G0/0/0 (fiber link to R3).
interface gigabitethernet 0/0/0
 no ip ospf cost 648
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   traceroute 192.168.20.254   -> first hop 10.3.3.2 (R3) instead of 10.1.1.2 (R2)
! ==============================================================

ROUTER R2

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR ROUTER R2
!--- Usage: open the R2 CLI tab and paste this whole file at the R2> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 3: Verify Routing
! --------------------------------------------------------------

!--- No OSPF updates on the LAN interface G0/1 (no routers there).
!--- c. Propagate the IPv4 default route into OSPFv2.
router ospf 1
 passive-interface gigabitethernet 0/1
 default-information originate
 exit

!--- g. Propagate the IPv6 default route into OSPFv3.
ipv6 router ospf 1
 default-information originate
 exit

! --------------------------------------------------------------
!--- Part 4: Verify WAN Technologies
! --------------------------------------------------------------

!--- g. S0/0/0 (backup link to R1) must also be a NAT inside interface.
interface serial 0/0/0
 ip nat inside
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show ip protocols         -> Passive Interface(s): GigabitEthernet0/1
!---   show ip nat statistics    -> Inside Interfaces include Serial0/0/0
! ==============================================================

ROUTER R3

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR ROUTER R3
!--- Usage: open the R3 CLI tab and paste this whole file at the R3> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 2: Verify DHCP
! --------------------------------------------------------------

!--- c. Correct the default gateway of the LAN40 and LAN50 pools.
ip dhcp pool LAN40
 network 192.168.40.0 255.255.255.0
 default-router 192.168.40.1
 exit
ip dhcp pool LAN50
 network 192.168.50.0 255.255.255.0
 default-router 192.168.50.1
 exit

! --------------------------------------------------------------
!--- Part 3: Verify Routing
! --------------------------------------------------------------

!--- No OSPF updates on the LAN subinterfaces (no routers there).
router ospf 1
 passive-interface gigabitethernet 0/1.30
 passive-interface gigabitethernet 0/1.40
 passive-interface gigabitethernet 0/1.50
 exit

! --------------------------------------------------------------
!--- Part 4: Verify WAN Technologies
! --------------------------------------------------------------

!--- b. Remove the OSPF cost left over from the old serial link on G0/1/0 (fiber link to R1).
interface gigabitethernet 0/1/0
 no ip ospf cost 648
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show ip route ospf   -> O*E2 0.0.0.0/0 default route learned from R2
!---   PC3, PC4: ipconfig /renew   -> gateways 192.168.40.1 and 192.168.50.1
! ==============================================================

SWITCH S1

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR SWITCH S1
!--- Usage: open the S1 CLI tab and paste this whole file at the S1> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1: Verify Switching Technologies
! --------------------------------------------------------------

!--- b. Port security on F0/3 (PC1); sticky learns the MAC of PC1. The default violation mode is shutdown.
interface fastethernet 0/3
 switchport port-security
 switchport port-security mac-address sticky
 exit

!--- e. G0/1 (link to R1) into VLAN 10, with PortFast.
interface gigabitethernet 0/1
 switchport access vlan 10
 spanning-tree portfast
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show port-security   -> Fa0/3 secure port
!---   show vlan            -> Fa0/3, Fa0/4 and Gig0/1 in VLAN 10
! ==============================================================

SWITCH S2

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR SWITCH S2
!--- Usage: open the S2 CLI tab and paste this whole file at the S2> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1: Verify Switching Technologies
! --------------------------------------------------------------

!--- j. Native VLAN 99 on the trunk G0/1.
interface gigabitethernet 0/1
 switchport trunk native vlan 99
 exit

!--- l. S2 is the root bridge for all VLANs.
spanning-tree vlan 1-1005 root primary

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces trunk                -> Gig0/1 native VLAN 99
!---   show spanning-tree summary totals    -> Root bridge for: default V30 V40 V50 Native
! ==============================================================

SWITCH S3

! ==============================================================
!--- 12.5.13 Packet Tracer - Troubleshoot Enterprise Networks
!--- ANSWER SCRIPT FOR SWITCH S3
!--- Usage: open the S3 CLI tab and paste this whole file at the S3> prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1: Verify Switching Technologies
! --------------------------------------------------------------

!--- h. F0/1 and F0/2 into port channel 1 without a negotiation protocol (mode on).
interface range fastethernet 0/1 - 2
 channel-group 1 mode on
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show etherchannel summary   -> Po1(SU) with Fa0/1(P) and Fa0/2(P)
! ==============================================================

Download Packet Tracer (.pka) file:

12.5.13 Packet Tracer - Troubleshoot Enterprise Networks.pka 777.80 KB 8230 downloads

...

Download

Previous Lab
11.5.1 Packet Tracer – Compare Layer 2 and Layer 3 Devices

Next Lab
12.6.1 Packet Tracer – Troubleshooting Challenge – Document the Network

12.5.13 Packet Tracer - Troubleshoot Enterprise Networks (Answers)