EIGRP error not on common subnet

Unanswered Question
Oct 9th, 2008

Oct 10 05:44:41 GMT: IP-EIGRP(Default-IP-Routing-Table:100): Neighbor 172.19.242

.74 not on common subnet for GigabitEthernet0/1.6

please discuss why this arises and how to overcome.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Thu, 10/09/2008 - 22:49

Hello Abhay,

this means there is a router with an interface or subinterface in the L2 vlan associated with local router int g0/1.6 that is sending EIGRP hellos with right parameters (AS number k values) but using a source address that is not part of IP subnet on local router interface g0/1.6.

This check is performed by EIGRP to verify that the neighbor can be safely used as an ip next-hop.

ip 172.19.242.74 is out of local subnet.

If you want to build EIGRP adjacency: modify remote router ip address to fit or change the network mask on local router to be able to accept ip 172.19.242.74

Hope to help

Giuseppe

csco10716389 Thu, 10/09/2008 - 23:21

Giuseppe

thanks for replying but the subnet is not the issue here , as mentioned by u (source address is not a part of ip subnet on local router)i have verified it is contained in the same subnet,main interface g0/1 doesnot have any ip adress it is a trunk port and the sub interface G0/1.6 is connected to Layer3 switch and the port on which it is connected it has been assingned a vlan.now i think it is clear and now explain what could be the issue

Actions

This Discussion