01-11-2012 06:12 AM - edited 03-07-2019 04:17 AM
I have cisco 6509. Gateways vlan 1 10.1.1.1 and vlan 2 10.1.2.1 are configured two here. In addition to these there are vlan and others, and with them everything is OK. Everything works, but that's falling out such messages.
IP-EIGRP(Default-IP-Routing-Table:1): Neighbor 10.1.2.1 not on common subnet for Vlan1
IP-EIGRP(Default-IP-Routing-Table:1): Neighbor 10.1.1.1 not on common subnet for Vlan2
Read here http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a0080093f09.html to no avail.
what to do?
Solved! Go to Solution.
01-11-2012 06:32 AM
Check the EIGRP peering neighbor whether are the on the same subnet.
01-11-2012 06:20 AM
What is that you are trying to accomplish, default-route failover ?
01-11-2012 06:24 AM
ip route 0.0.0.0 0.0.0.0 10.1.3.1
Everything works. But there is always a message.
01-11-2012 06:29 AM
Sergey,
The router is telling you that it is receiving EIGRP Hello packets from routers that do not belong to the same IP subnet as the interface on which the Hello packets were received. This is always a sign of a misconfiguration.
Would you mind posting the configuration of your interfaces Vlan1 and Vlan2?
Best regards,
Peter
01-11-2012 06:35 AM
interface Vlan1
ip address 10.0.3.1 255.255.255.0 secondary
ip address 10.1.1.1 255.255.255.0
ip helper-address 10.1.10.2
ip helper-address 10.1.10.3
no ip redirects
ip flow ingress
interface Vlan2
ip address 10.0.2.1 255.255.255.0 secondary
ip address 10.1.2.1 255.255.255.0
ip helper-address 10.1.10.2
ip helper-address 10.1.10.3
no ip redirects
no ip unreachables
ip flow ingress
I understand that the switch to the wrong address swears in packages, but I can not understand how to take these wrong packets?
01-11-2012 06:42 AM
Sergey,
Thank you. As you can see, the complaints are absolutely logical: your Vlan1 is in 10.1.1.0/24 while the EIGRP peer is addressed with 10.1.2.1, and your Vlan2 is in 10.1.2.0/24 while the EIGRP peer is addressed with 10.1.1.1.
Either the two offending EIGRP routers are connected to wrong VLANs (they should be exchanged), or they are misconfigured and their IP addresses are erroneously reversed.
Best regards,
Peter
01-11-2012 06:32 AM
Check the EIGRP peering neighbor whether are the on the same subnet.
01-11-2012 06:45 AM
I've found - from the network 10.1.2.0/24 had two connections and one of the ports was in vlan 1. Thanks for your help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide