How to Configuring EIGRP Static Neighbors

If you completed the previous labs 8-1 – Configure EIGRP, you'll notice the EIGRP does not form a neighbor relationship between R1 and R4. This is because it is a map between two devices that allow broadcasts. As a way to restrict ISP forbid the broadcast in a particular PVC program. Having said that, remember treat multicast broadcast through the frame relay network.

As a hotfix for this problem, you can define a static neighbor would force the EIGRP neighbor through unicast RIP like; same EIGRP routing processes, even if orders are communicated by it's neighbor x.x.x.x interface #/#x.x.x.x is equal to the IP address of the interface, and the interface #/# which adjacent relation in the peer interface.

Configure EIGRP static neighbor, neighbor's statements are needed in the same autonomous system in the operation of neighbor relationships at both ends of the EIGRP routing process. Also keep in mind that when you are in a specific interface, EIGRP, specify a static neighbourhood will be disabled when you process the multicast datagram for a specified EIGRP interface so that being said EIGRP EIGRP process will not be sent without receiving multicast traffic on the definition of a static neighbor EIGRP routing process interfaces.

In this lab you will on a hub and spoke frame relay network configuring static neighbors. (R1, R2, R3 to R1, and R1 to R4)

Will continue according to the laboratory this laboratory 8-1 and 8 other topology generation used in the lab.

• Frame relay hub and R1 and R4, R1 and R3, R1 and R2 for the branch network, configure a static neighbourhood.
• Validation on the R1 has been established on the relationship between neighbors.
• Validation and spoke between the spokes of the hub transmission.

Step 2: Talk to verify statements between communication routes between hubs and spokes.

All routes as shown below are advertised to frame relay network hub router (R1);

Now verify that the routes from the spoke routers R2 and R3 are in the R4′s routing table as shown below;

As you can see from the above, you can tell that route on R2 and R3 to R4 and therefore not to be released to R5 as well. What causes this and how to fix it?

This type of behavior is provided by the EIGRP IP split-horizon interface received them, carries no route created. This is a cycle of the precautionary approach, and in some cases must be disabled as a hub-and-spoke topology. You will learn more about split-horizon. Configure EIGRP did not split-horizon.