IP-EIGRP(Default-IP-Routing-Table:1):

Answered Question
Jan 11th, 2012

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?

I have this problem too.
0 votes
Correct Answer by rizwanr74 about 2 years 3 months ago

Check the EIGRP peering neighbor whether are the on the same subnet.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
rizwanr74 Wed, 01/11/2012 - 06:20

What is that you are trying to accomplish, default-route failover ?

Tramp_Sergey Wed, 01/11/2012 - 06:24

ip route 0.0.0.0 0.0.0.0 10.1.3.1

Everything works. But there is always a message.

Peter Paluch Wed, 01/11/2012 - 06:29

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

Tramp_Sergey Wed, 01/11/2012 - 06:35

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?

Peter Paluch Wed, 01/11/2012 - 06:42

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

Correct Answer
rizwanr74 Wed, 01/11/2012 - 06:32

Check the EIGRP peering neighbor whether are the on the same subnet.

Tramp_Sergey Wed, 01/11/2012 - 06:45

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.

Actions

Login or Register to take actions

This Discussion

Posted January 11, 2012 at 6:12 AM
Stats:
Replies:7 Avg. Rating:5
Views:2095 Votes:0
Shares:0
Tags: eigrp, not, subnet, common
+

Related Content

Discussions Leaderboard

Rank Username Points
1 15,007
2 8,150
3 7,730
4 7,083
5 6,742
Rank Username Points
155
77
70
69
45