From: Mike O (mikeeo@msn.com)
Date: Wed Jun 14 2006 - 15:12:19 ART
One issue I ran into forced a ptp link on R4 and connected to R1 which was
not allowed to have sub interfaces or network type. While adjusting the
hello timer would allow OSPF to form an adjacency it would NOT pass routes.
>From: "Chris Broadway" <midatlanticnet@gmail.com>
>To: "Mike O" <mikeeo@msn.com>
>CC: ccielab@groupstudy.com
>Subject: Re: interfaces w/ OSPF network types
>Date: Wed, 14 Jun 2006 14:05:22 -0400
>
>If my understanding of the question is correct, I would look at the default
>network type on R6 and then make sure R1, R4, and R5 are the same by using
>the "ip ospf network type" (if needed that is). And yes, depending on the
>default OSPF type on R6, you might need neighbor statements.
>
>-Broadway
>
>
>On 6/14/06, Mike O <mikeeo@msn.com> wrote:
>>
>>I have a question that I thought I would throw out.
>>
>>If you have a situation where some of your frame-relay interfaces are
>>allowed to have the ospf network type defined and then some not. Whats the
>>best way to configure that? For example say you have a hub and spoke with
>>R1
>>as the hub as R4,5 and 6 as the spoke. R6 cannot use "ip ospf network" but
>>everyone else can. Do you just use neighbor? or better yet say you must
>>use
>>network type on R4.
>>
>>Is it always better to fall back and use the neighbor command when you
>>can't
>>get anything else to work? considering you are allowed to use the neighbor
>>command in the given section.
>>
>>_______________________________________________________________________
>>Subscription information may be found at:
>>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:32 ART