The first thing you should know about EIGRP is that EIGRP uses multicast hello packets to communicate to other EIGRP neighbors and when it receives an EIGRP hello packet sourced from an IP address on a subnet that is not configured on its receiving interface as a primary address will generates “not on common subnet” error message. Also may generates this error based on following issues:
Misconfiguration of the interfaces or switch ports or cabling problem.
Mismatch of primary/secondary IP addresses on the neighbor interface.
A switch/hub is leaking multicast packets to other ports.
If using a LAN switch, the vlans may have joined routers together.
Another router uses EIGRP advertising on the same subnet/vlan as this router and is misconfigured with an incorrect AS number.
To troubleshoot this issue, check these items:
- Double check the interface configuration for misconfigured IP address on local and neighboring routers
- Verify the primary address of the interface is in the same subnet as the primary address of the neighbor
Another way to disable this error message is using the following command under the EIGRP process that is not recommended by Cisco but you can use this command to disable the error message in both sides but both sides never make neighbor relationship if you use different subnets:
no eigrp log-neighbor-warnings
please note that: you can use this command if you run IOS release 11.3, 12.0 or later.
Today I am having trouble with redistributing EIGRP to RIP
R4 is using RIP and other routers are running EIGRP, R4 routes do not show up on any of the EIGRP router and Vise Versa. I have also used the "No Auto-Summary" command. I don`t undersand what could be the problem.
I have attached the Running Config of all the routers
Open a new discussion for this. Just looking at the configuration you attached here, you have not configure RIP on R2 yet you redistributed it under EIGRP.
Same thing with R4, you redistributed EGRIP when you never configure one. I think you are practicing redistribution. You want R4 to get EIGRP routes. so removed the redistribute command under RIP. Like DelVonte already mention, configure atleast R2 link to R4, as a rip Link, then redistribute command on R2 will make sense to the router.
To avoid some network issues, you can make put each link into a separate subnet. For example
R1 - R2 = 192.168.1.0/30
R1 - R3 = 192.168.2.0/30
R2 - R4 = 192.168.3.0/30 and so on
I have made some configuration changes and got your redistribution working!
See Attached text file for all 4 routers config files - Study them. There are other ways to get it going too.
Have a good weekend!!
Good-luck on your studies.
Running Config - Redistribution.txt.zip 841 bytes
You have saved me once again... I did have to break my head once again... What I did was, I configured RIP in R2 and redistributed it
But till I was not able to ping 192.168.1.5 and 192.168.1.6 from R4 and Ping failed from R1 to 192.168.1.22
Then I configured RIP on R3 as well and redistributed it and now the entire network is working fine, I understand that If I have to make the network reachabe I have to configure all the neighbours of R4 to redistribute, Am I correct ?
And next time I will definitely open up a new discussion, Sorry about that.
Thanks to Glory too