PACKET TRACER LABS DOWNLOAD SERIAL

Both IP addresses actually belong to R3-one over the frame-relay network and the other is the direct link to R1. We will start with R1 and view the EIGRP neighbors using the show ip eigrp neighbors command: LetвЂ™s now move on to EIGRP troubleshooting. Looking at the configuration on that interface, we can see why:ДЇor frame-relay to work, that interface must be configured with the encapsulation frame-relay command as follows: interface Serial0/1/0Д®ven without pinging, we see that the EIGRP neighbor adjacency has formed between R1 and R3:Д¬ool, so we have IP connectivity.

PACKET TRACER LABS DOWNLOAD SERIAL

So letвЂ™s go over to R3 to check what is happening on that routerвЂ™s frame-relay interface:ДЄs you can see from the output of the show interface command above, the serial interface is using the default encapsulation of HDLC. It seems R1 does not have a DLCI associated with R3. Since inverse ARP is turned on by default, we can use the show frame-relay map command to make sure DLCIs are correctly learned and associated: R1 can ping R2 over the frame-relay network but not R3.

Now letвЂ™s go check the IP connectivity from the routers themselves. Note: Go ahead and confirm the DLCIs are correct e.g., R1R2 is 102 while R2R1 is 201. Therefore, we need to make sure that the frame-relay device (cloud) is correctly configured: The first place to start in this type of scenario is to confirm that there is underlying L1/L2 connectivity between the routers. Trblsht_wan_eigrp_final.pkt: This Packet Tracer file contains the lab with the issues resolved.

Packet tracer labs download