From: Mike Gutknecht (mgutknec@xxxxxxxxx)
Date: Tue Feb 20 2001 - 16:48:36 GMT-3
Not quite. The "ospf network point-to-multipoint" command on R1 inserted
/32 s for every host on the NBMA cloud and they got distributed either via
OSPF or EIGRP.
I don't think the "next-hop-self" command really needs to be there. I ended
up with full connectivity without it.
-Mike Gutknecht
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Lachlan Kidd
Sent: Monday, February 19, 2001 3:50 PM
To: Scott Schneidewind; ccielab@groupstudy.com
Subject: RE: cciebootcamp #2, #4 - Next hop self
Hi Scott,
The reason for this is that R1 is an the same AS as R2 and R5. Without
next-hop-self, R3 will see routes from R5 and R2 with a next hop of R5/R2's
IP address. Due to the frame/ospf setup, I'm pretty sure that R5/R2's s0 IP
address is unreachable and hence the route will not be published in the
routing table. By setting next-hop-self, the routes will appear with a next
hop of R1 which is directly connected to R3 and hence reachable....at least
I think that's how it goes <grin>
Regards,
Lachlan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Scott Schneidewind
Sent: Tuesday, 20 February 2001 6:23:AM
To: ccielab@groupstudy.com
Subject: cciebootcamp #2, #4 - Next hop self
Hello All.
Taking a look at the cciebootcamp labs #2 and #4, router 1 has the
neighbor <router 3> next-hop-self
Could somebody please explain why this router needs the command and no other
routers do?
Thanks,
Scott
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:54 GMT-3