From: Piotr (usaccie@gmail.com)
Date: Wed Dec 03 2008 - 00:08:53 ARST
I saw this a few times in my dynamips labs. It's usually a MTU problem but
your debug does not indicate that.
if it were an MTU issue then possible solutions would be:
1. Change the system MTU on the switch. - (3560 system mtu(requires a
reboot)
or system mtu routing (no reboot))
2. Configure ip ospf mtu-ignore. (this is needed only on one side)
3. configure a MTU on the VLAN interface with the "IP MTU" command.
(on a 3550)
Maybe you have a layer 2 issue since the connection never worked, check your
switch(s), ports, trunks, vlans etc...
On Tue, Dec 2, 2008 at 6:53 PM, omar parihuana <omar.parihuana@gmail.com>wrote:
> Hi,
>
> Both routers are connected directly via FastEthernet Interfaces (R2 and R4)
>
> R2#sh run int f0/0
> Building configuration...
>
> Current configuration : 114 bytes
> !
> interface FastEthernet0/0
> ip address 150.1.24.2 255.255.255.0
> ip pim dense-mode
> duplex auto
> speed auto
> end
>
> R2#
>
>
> R4#sh run int f0/0
> Building configuration...
>
> Current configuration : 114 bytes
> !
> interface FastEthernet0/0
> ip address 150.1.24.4 255.255.255.0
> ip pim dense-mode
> duplex auto
> speed auto
> end
>
> R4#
>
>
> Suddenly:
>
> R4#
> *Mar 1 20:12:10.778: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.2.2 on
> FastEthernet0/0 from DOWN to DOWN, Neighbor Down: Ignore timer expired
> R4#
> R4#
>
> *Mar 1 20:14:20.842: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.2.2 on
> FastEthernet0/0 from EXSTART to DOWN, Neighbor Down: Too many
> retransmissions
>
> R4#debug ip ospf adj
> OSPF adjacency events debugging is on
> R4#
> R4#
> R4#
> *Mar 1 20:15:03.146: OSPF: Nbr 150.1.2.2 150.1.24.2 FastEthernet0/0 is
> currently ignored
> R4#
> R4#
> R4#
> *Mar 1 20:15:20.846: OSPF: 150.1.2.2 address 150.1.24.2 on
> FastEthernet0/0
> is dead
> *Mar 1 20:15:20.850: OSPF: 150.1.2.2 address 150.1.24.2 on
> FastEthernet0/0
> is dead, state DOWN
> *Mar 1 20:15:20.850: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.2.2 on
> FastEthernet0/0 from DOWN to DOWN, Neighbor Down: Ignore timer expired
> *Mar 1 20:15:20.854: OSPF: Neighbor change Event on interface
> FastEthernet0/0
> *Mar 1 20:15:20.858: OSPF: DR/BDR election on FastEthernet0/0
> *Mar 1 20:15:20.858: OSPF: Elect BDR 0.0.0.0
> *Mar 1 20:15:20.862: OSPF: Elect DR 150.1.4.4
> *Mar 1 20:15:20.862: DR: 150.1.4.4 (Id) BDR: none
> *Mar 1 20:15:30.838: OSPF: 2 Way Communication to 150.1.2.2 on
> FastEthernet0/0, state 2WAY
> *Mar 1 20:15:30.842: OSPF: Neighbor change Event on interface
> FastEthernet0/0
> *Mar 1 20:15:30.842: OSPF: DR/BDR election on FastEthernet0/0
> *Mar 1 20:15:30.846: OSPF: Elect BDR 0.0.0.0
> *Mar 1 20:15:30.846: OSPF: Elect DR 150.1.4.4
> *Mar 1 20:15:30.846: DR: 150.1.4.4 (Id) BDR: none
> *Mar 1 20:15:30.850: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:30.854: OSPF: Neighbor change Event on interface
> FastEthernet0/0
> *Mar 1 20:15:30.858: OSPF: DR/BDR election on FastEthernet0/0
> *Mar 1 20:15:30.858: OSPF: Elect BDR 0.0.0.0
> *Mar 1 20:15:30.862: OSPF: Elect DR 150.1.4.4
> *Mar 1 20:15:30.862: DR: 150.1.4.4 (Id) BDR: none
> *Mar 1 20:15:30.874: OSPF: Neighbor change Event on interface
> FastEthernet0/0
> *Mar 1 20:15:30.878: OSPF: DR/BDR election on FastEthernet0/0
> *Mar 1 20:15:30.882: OSPF: Elect BDR 150.1.2.2
> *Mar 1 20:15:30.882: OSPF: Elect DR 150.1.4.4
> *Mar 1 20:15:30.882: DR: 150.1.4.4 (Id) BDR: 150.1.2.2 (Id)
> *Mar 1 20:15:30.886: OSPF: Neighbor change Event on interface
> FastEthernet0/0
> *Mar 1 20:15:30.890: OSPF: DR/BDR election on FastEthernet0/0
> *Mar 1 20:15:30.890: OSPF: Elect BDR 150.1.2.2
> *Mar 1 20:15:30.890: OSPF: Elect DR 150.1.4.4
> *Mar 1 20:15:30.890: DR: 150.1.4.4 (Id) BDR: 150.1.2.2 (Id)
> *Mar 1 20:15:35.854: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:35.858: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [1]
> *Mar 1 20:15:40.858: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:40.862: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [2]
> *Mar 1 20:15:45.862: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:45.866: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [3]
> *Mar 1 20:15:50.866: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:50.870: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [4]
> *Mar 1 20:15:55.870: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:15:55.874: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [5]
> *Mar 1 20:16:00.874: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:00.874: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [6]
> *Mar 1 20:16:05.874: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:05.878: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [7]
> *Mar 1 20:16:10.878: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:10.882: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [8]
> *Mar 1 20:16:15.882: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:15.886: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [9]
> *Mar 1 20:16:20.886: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:20.890: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [10]
> *Mar 1 20:16:25.890: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:25.890: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [11]
> *Mar 1 20:16:30.890: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
> *Mar 1 20:16:30.890: OSPF: Retransmitting DBD to 150.1.2.2 on
> FastEthernet0/0 [12]
> *Mar 1 20:16:35.890: OSPF: Send DBD to 150.1.2.2 on FastEthernet0/0 seq
> 0x236D opt 0x52 flag 0x7 len 32
>
> the connection never worked, after shut/no shut the adjacency come back UP
> again..
>
> Rgds.
>
> On Tue, Dec 2, 2008 at 6:47 PM, Marko Milivojevic <markom@markom.info
> >wrote:
>
> > On Tue, Dec 2, 2008 at 23:41, omar parihuana <omar.parihuana@gmail.com>
> > wrote:
> > > Hi Guys,
> > >
> > > Today I faced exactly the same problem, and tried to ip ospf mtu-ignore
> > in
> > > both interfaces and nothing, checked duplex mode the same. I had to
> > shut/no
> > > shut and after that adjacency is formed... anyway after read the thread
> I
> > > didn't find out other solution. Somebody got a solution.. ?
> >
> > How about the actual MTU on the transmission path? Can it carry the
> > largest packet transmitted by either side?
> >
> > --
> > Marko
> > CCIE #18427 (SP)
> > My network blog: http://cisco.markom.info/
> >
>
>
>
> --
> Omar E.P.T
> -----------------
> Certified Networking Professionals make better Connections!
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:07 ARST