When you describe this as a partial mesh, am I correct in assuming that R2 has 2 PVCs (one to each remote router) and that R5 and R6 have a single PVC (to R2)? If so that is the reason why EIGRP is building the neighbor relationships this way. R5 receives a hello from R2, sends a hello and they become neighbors. Similarly R6 receives a hello from R2, sends a hello and they become neighbors. The hello sent from R5 gets to R2 but does not get to R6 so R5 and R6 do not become neighbors.
Perhaps what is a bit confusing to the issue is what it means when your frame relay map includes broadcast. This means that the router will send broadcasts (by making a copy for each PVC) but it does not mean that a router will forward broadcasts (or multicasts).
Perhaps another way of looking at it is that R5 can see directly only R2. R5 has access to R6 (via the frame relay map) but its access is indirect (using R2 as a relay). EIGRP only forms neighbor relationships on direct connections and not on indirect connections.
Yes it is true that a FR router with "broadcast" configured in its mappings won't forward a received broadcast packet to another FR neighbor, even if that neighbor is in the same subnet. The broadcast parameter in the map is about how the router handles its own traffic. It does not enable forwarding of received broadcasts.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...