leblanc
asked on
eigrp neighbor not showing
I am trying to figure out why R2 does not see S2 as its eigrp nei (see diagram). R1 can see S1 and R2. The only difference is a L2 switch between R2 and S2.
R2#sh ip eigrp nei
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.200.2 Gig0/0 12 01:02:56 40 1000 0 11R1#sh ip eigrp nei
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.200.1 Gig0/0 12 01:03:19 40 1000 0 9
1 10.10.20.254 13 00:41:23 40 1000 0 10S1#sh ip eigrp nei
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.101.2 Gig0/2 13 00:43:10 40 1000 0 7
1 10.10.20.250 Vlan 11 00:42:57 40 1000 0 12S2#sh ip eigrp nei
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.101.1 Vlan 12 00:43:56 40 1000 0 9SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mitul Prajapati
Your problem will be sort out if you either replace Layer 2 S1 or S2 switch to Layer 3 switch as L2 switch doesn't support routing. Or to see EIGRP neighbors from R2 to S2 they should be in the same subnet but that make no sense.
ASKER
S1 and S2 are layer 3 switches.
Predrag,
I think you got it. "EIGRP neighbors that are not in the same IP address range will not established adjacency" I added an SVI 10 (which is in R2) in S2, I know have the S2 as eigrp neighbor from R2. Bascially, I need a L3 link so that eigrp can be advertised.
Now the strange thing is to reach 10.10.20.100, the preferred path is via R2 from S2 which is 2 hops away. I shutdown R2 and the traceroute shows that it is only 1 hop away from S2 to S1. Any idea why it takes the R2 S2 path instead of S2 S1. All the bandwidth are gigs.
Predrag,
I think you got it. "EIGRP neighbors that are not in the same IP address range will not established adjacency" I added an SVI 10 (which is in R2) in S2, I know have the S2 as eigrp neighbor from R2. Bascially, I need a L3 link so that eigrp can be advertised.
Now the strange thing is to reach 10.10.20.100, the preferred path is via R2 from S2 which is 2 hops away. I shutdown R2 and the traceroute shows that it is only 1 hop away from S2 to S1. Any idea why it takes the R2 S2 path instead of S2 S1. All the bandwidth are gigs.
S2#traceroute 10.10.20.100
Type escape sequence to abort.
Tracing the route to 10.10.20.100
1 10.10.10.250 42 msec 4 msec 1 msec
2 10.10.200.2 0 msec 0 msec 0 msec
3 * 0 msec 0 msec S2#traceroute 10.10.20.100
Type escape sequence to abort.
Tracing the route to 10.10.20.100
1 10.10.101.1 2 msec 0 msec 0 msec
2 10.10.20.100 0 msec 14 msec 0 msec
That would be too much to guess, it could be anything (including static route configured on S2 :) ).
Check routing table and EIGRP database on S2, it should give you some clue.
Check routing table and EIGRP database on S2, it should give you some clue.
Can you post vlan trunk configs and gig interface configs from switch2?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I rebuilt the lab. I think there is a bug in GNS3