Hmm... off the top of my head the only reason for that behavior that I can
think of is a passive-interface statement in your eigrp config, which you'd
probably notice. g Perhaps posting the configs is a good idea.
John
Hey again,
I've run into a wall here trying to configure a
Okey dokey :)
3 routers:
eo1 Cisco 2516 2 Serials s0 and s1, 1 ethernet (hub).
e0: 172.16.1.40/16
s0: 10.10.10.10/24 (creative huh?) s0.1
s1: 10.10.30.1/24 s1.1
eo2 Cisco 1602r 2 Serials (56K 4 wire dsu), 1 ethernet
e0: 192.168.1.1/24
s0: 10.10.30.2/24 s0.1
s1: 10.10.20.2/24 s1.1
eo3 Cisco
In EIGRP, the network statement specifies which interfaces are going to
participate in the routing process. So, for every separate major network on
the router, you need a different network statement.
For example, on Router eo1 the only interface that will run EIGRP is e0. To
have EIGRP run on
Ya know, that fixed it right up. For some reason I was thinking it would
cause troubles if I advertised the same network out but now that I read into
it, thats not the context at all. Strange.. now for ospf :)
Look to the south for a large mushroom cloud in the sky.
Thanks again,
Dave
On
Luckily, the network command works similarly for both EIGRP and OSPF: they
specify which interfaces are participating in the routing process. However,
with OSPF I've noticed that if there is an interface that I don't want to
run OSPF on, I still have to have a network statement for it or other
5 matches
Mail list logo
