From: Scott Morris (smorris@internetworkexpert.com)
Date: Sun Feb 15 2009 - 22:32:33 ARST
Actually good highlight... It's what I get for not reading the onfigs. :)
There's been a behavior change in IOS which includes OSPFv2. It used to be
that P2P and P2MP could talk to each other just fine. But there are
differences and discrepancies in how he database functionality works, so
caused a few issues along the way if not properly monitored.
Newer versions of IOS seem to not allow this to happen. I remember running
into this back when I was at another company where one of the labs that used
to work perfectly fine stopped working for people as advertised following
some upgrades. All the entertainment. Aparantly this carries for OSPFv3
as well.
Scott
-----Original Message-----
From: Hobbs [mailto:deadheadblues@gmail.com]
Sent: Sunday, February 15, 2009 11:58 AM
To: Ramanpreet Singh
Cc: Ryan DeBerry; smorris@internetworkexpert.com; Cisco certification
Subject: Re: OSPF v3- neighbors bouncing
On a P2P link you can only have one neighbor. So maybe by having the
full mesh, the adjacency that is trying to form between to the P2P
network types is screwing the other one with hub.
On Sun, Feb 15, 2009 at 8:59 AM, Ramanpreet Singh
<sikandar.raman@gmail.com> wrote:
> actually I tried deleting frame-relay map ipv6 (Link-state) from R3 to
> R4 and R4 to R3, neighbors came up but I don't know why?
>
> On Sun, Feb 15, 2009 at 9:41 AM, Ryan DeBerry <rdeberry@gmail.com> wrote:
>
>> So could you just ignore it?
>>
>> ip ospf mtu-ignore
>>
>>
>> On Sun, Feb 15, 2009 at 10:31 AM, Ramanpreet Singh <
>> sikandar.raman@gmail.com> wrote:
>>
>>> I agree with scott.. I was thinking about MTU issues but MTU is 1500
for
>>> all the three router interfaces..
>>>
>>>
>>> On Sun, Feb 15, 2009 at 9:27 AM, Scott Morris <
>>> smorris@internetworkexpert.com> wrote:
>>>
>>>> Timers won't make an adjacency to begin with. I'd look at MTU issues
>>>> although that's not common on router-to-router unless you have
>>>> manipulated
>>>> something along the way!
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>>>> Ryan
>>>> DeBerry
>>>> Sent: Sunday, February 15, 2009 10:21 AM
>>>> To: Ramanpreet Singh
>>>> Cc: Cisco certification
>>>> Subject: Re: OSPF v3- neighbors bouncing
>>>>
>>>> Sounds like your timers dont match.
>>>>
>>>> Show ip ospf int s0/0/0.346
>>>>
>>>>
>>>> On Sun, Feb 15, 2009 at 10:13 AM, Ramanpreet Singh <
>>>> sikandar.raman@gmail.com
>>>> > wrote:
>>>>
>>>> > I have configured point to multipoint ipv6 frame-relay for OSPF v3
>>>> between
>>>> > R3, R4 and R6. I am unable to form "Full" state neighbor
relationship.
>>>> >
>>>> > For some reason, neighbor relationship is bouncing between init and
>>>> > Exstart.
>>>> > As soon as it reaches full state, it bounces back to init. Kindly
help.
>>>> >
>>>> > Here sre the configs.
>>>> >
>>>> >
>>>> > *R6*
>>>> > interface Serial0/0/0.346 multipoint
>>>> > ip address 110.1.0.6 255.255.255.0
>>>> > ip ospf network point-to-multipoint
>>>> > ip ospf hello-interval 10
>>>> > ipv6 address 2001:0:0:346::/64 eui-64
>>>> > ipv6 ospf network point-to-multipoint
>>>> > ipv6 ospf hello-interval 10
>>>> > ipv6 ospf 1 area 0
>>>> > frame-relay map ipv6 FE80::216:9DFF:FE43:FDE0 604 broadcast
>>>> > frame-relay map ipv6 2001::346:215:C6FF:FEF2:64D0 603
>>>> > frame-relay map ip 110.1.0.3 603 broadcast
>>>> > frame-relay map ip 110.1.0.4 604 broadcast
>>>> > frame-relay map ipv6 2001::346:216:9DFF:FE43:FDE0 604
>>>> > frame-relay map ipv6 FE80::215:C6FF:FEF2:64D0 603 broadcast
>>>> >
>>>> > *R3*
>>>> > interface Serial0/0/0
>>>> > ip address 110.1.0.3 255.255.255.0
>>>> > encapsulation frame-relay
>>>> > ip ospf network point-to-point
>>>> > ipv6 address 2001:0:0:346::/64 eui-64
>>>> > ipv6 ospf network point-to-point
>>>> > ipv6 ospf 1 area 0
>>>> > frame-relay map ipv6 FE80::216:9DFF:FE43:FDE0 304 broadcast
>>>> > frame-relay map ipv6 2001::346:216:9DFF:FE43:64A0 306
>>>> > frame-relay map ip 110.1.0.6 306 broadcast
>>>> > frame-relay map ipv6 FE80::216:9DFF:FE43:64A0 306 broadcast
>>>> > frame-relay map ipv6 2001::346:216:9DFF:FE43:FDE0 304
>>>> > no frame-relay inverse-arp
>>>> > frame-relay lmi-type ansi
>>>> >
>>>> > *R4*
>>>> > !
>>>> > interface Serial0/0/0
>>>> > ip address 110.1.0.4 255.255.255.0
>>>> > encapsulation frame-relay
>>>> > ip ospf network point-to-point
>>>> > ipv6 address 2001:0:0:346::/64 eui-64
>>>> > ipv6 ospf network point-to-point
>>>> > ipv6 ospf 1 area 0
>>>> > frame-relay map ipv6 2001::346:216:9DFF:FE43:64A0 406
>>>> > frame-relay map ipv6 2001::346:215:C6FF:FEF2:64D0 403
>>>> > frame-relay map ip 110.1.0.6 406 broadcast
>>>> > frame-relay map ipv6 FE80::216:9DFF:FE43:64A0 406 broadcast
>>>> > frame-relay map ipv6 FE80::215:C6FF:FEF2:64D0 403 broadcast
>>>> > no frame-relay inverse-arp
>>>> > frame-relay lmi-type ansi
>>>> > end
>>>> >
>>>> > **
>>>> > **
>>>> >
>>>> >
>>>> > Blogs and organic groups at http://www.ccie.net
>>>> >
>>>> >
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:11 ARST