From: Mike O (mikeeo@msn.com)
Date: Wed Jun 14 2006 - 15:35:26 ART
You are right I had to go with non-broadcast on the ptp like and used
neighbor from the hub. So I guess the answer is if you can't get the ospf
types to match go with the neighbor statements and make it non-broadcast.
>From: "Plank, Jason" <JPlank@concordefs.com>
>Reply-To: "Plank, Jason" <JPlank@concordefs.com>
>To: Mike O <mikeeo@msn.com>, midatlanticnet@gmail.com
>CC: ccielab@groupstudy.com
>Subject: RE: interfaces w/ OSPF network types
>Date: Wed, 14 Jun 2006 14:18:48 -0400
>
>They won't pass routes. Partially because when you mix/match network types
>the "DR" selection process must match. If one side was non-broadcast (DR)
>and one side was of a point-to-point link (NO DR) I would think that the
>results you got would be normal. Which IE lab was this? If you can't change
>the network type of R6, it sounds like you'd need to use non-broadcast
>which
>means the only network type you'd be able to mix/match would be broadcast.
>
>-------------------
>J. Marshall Plank
>Network Engineer
>101 Bellevue Parkway
>Wilmington, DE 19809
>E-mail: JPlank@concordefs.com
>Phone: 302-793-5913
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>Mike
>O
>Sent: Wednesday, June 14, 2006 2:12 PM
>To: midatlanticnet@gmail.com
>Cc: ccielab@groupstudy.com
>Subject: Re: interfaces w/ OSPF network types
>
>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
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>-----------------------------------------
>The information in this message may be proprietary and/or
>confidential, and protected from disclosure. If the reader of this
>message is not the intended recipient, or an employee or agent
>responsible for delivering this message to the intended recipient,
>you are hereby notified that any dissemination, distribution or
>copying of this communication is strictly prohibited. If you have
>received this communication in error, please notify First Data
>immediately by replying to this message and deleting it from your
>computer.
>
>_______________________________________________________________________
>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