RE: OSPF Error " EXSTART to DOWN "

If the MTU was 1504 as part of your initial config, I'd vote to not change
it. Presumably your OSPF is new.

HTH,

Scott

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Paul
Adams
Sent: Saturday, April 11, 2009 3:41 AM
To: Salah ElShekeil
Cc: Cisco certification
Subject: Re: OSPF Error " EXSTART to DOWN "

Hi,

As of now I have applied the command sh ip ospf mtu-ignor, I believe it
should be ok ( but isnt ).

As per the question < do not change any inital configuration > ; due to this
I am, not chainging the system mtu size of Switch

On Sat, Apr 11, 2009 at 9:57 AM, Salah ElShekeil
<salah.elshekeil_at_gmail.com>wrote:

> chang the mtu to be the same as the router in the switch 1500byte
>
> but you have to reload the switch after applying the command
>
> HTH
>
> Salah
>
> On Sat, Apr 11, 2009 at 9:52 AM, Paul Adams <ccie.paul_at_gmail.com> wrote:
>
>> Thanks.
>>
>> I already have ip ospf mtu-ignore.
>>
>> So what could be the other possibility
>>
>> On Sat, Apr 11, 2009 at 9:35 AM, Salah ElShekeil <
>> salah.elshekeil_at_gmail.com> wrote:
>>
>>> check out system mtu !!
>>>
>>>
>>> use ip ospf mtu ign interface level command
>>> On Sat, Apr 11, 2009 at 9:26 AM, Paul Adams
<ccie.paul_at_gmail.com>wrote:
>>>
>>>> Hello GS,
>>>>
>>>> Time to Time I start getting the notification
>>>>
>>>> *2d22h: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.3.3 on Vlan12 from EXSTART
to
>>>> DOWN, Neighbor Down: Too many retransmissions
>>>> 2d22h: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.3.3 on Vlan12 from DOWN to
>>>> DOWN,
>>>> Neighbor Down: Ignore timer expired
>>>> *
>>>> and I start losing routes when I see " SH IP ROUTE "
>>>>
>>>>
>>>> SW1#sh ip ospf
>>>> neighbor
>>>>
>>>>
>>>>
>>>> Neighbor ID Pri State Dead Time Address
>>>> Interface
>>>> 4.4.3.3 1 FULL/BDR 00:00:32 4.4.12.3
>>>> Vlan12
>>>>
>>>> SW1#sh system
>>>> mtu
>>>>
>>>> System MTU size is 1504 bytes
>>>> R3#sh ip ospf
>>>> neighbor
>>>>
>>>>
>>>>
>>>> Neighbor ID Pri State Dead Time Address
>>>> Interface
>>>> 4.4.7.7 1 FULL/DR 00:00:30 4.4.12.7
>>>> FastEthernet0/0
>>>>
>>>> R3#sh int fastEthernet
>>>> 0/0
>>>>
>>>> FastEthernet0/0 is up, line protocol is
>>>> up
>>>>
>>>> Hardware is MV96340 Ethernet, address is 001d.46f3.b838 (bia
>>>> 001d.46f3.b838)
>>>> Internet address is 4.4.12.3/24
>>>>
>>>> MTU 1500 bytes, BW 100000 Kbit, DLY 100
>>>> usec,
>>>>
>>>> reliability 255/255, txload 1/255, rxload
>>>> 1/255
>>>>
>>>> Encapsulation ARPA, loopback not
>>>> set
>>>>
>>>> Keepalive set (10
>>>> sec)
>>>>
>>>> Full-duplex, 100Mb/s,
>>>> 100BaseTX/FX
>>>>
>>>> ARP type: ARPA, ARP Timeout
>>>> 04:00:00
>>>>
>>>> Last input 00:00:03, output 00:00:01, output hang
>>>> never
>>>>
>>>> Last clearing of "show interface" counters
>>>> never
>>>>
>>>> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:
>>>> 0
>>>> Queueing strategy:
>>>> fifo
>>>>
>>>> Output queue: 0/40
>>>> (size/max)
>>>>
>>>> 5 minute input rate 0 bits/sec, 0
>>>> packets/sec
>>>>
>>>> 5 minute output rate 0 bits/sec, 0
>>>> packets/sec
>>>>
>>>> 1151 packets input, 378891
>>>> bytes
>>>>
>>>> Received 1107 broadcasts, 0 runts, 0 giants, 0
>>>> throttles
>>>>
>>>> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0
>>>> ignored
>>>>
>>>> 0
>>>> watchdog
>>>>
>>>> 0 input packets with dribble condition
>>>> detected
>>>>
>>>> 9141 packets output, 882911 bytes, 0
>>>> underruns
>>>>
>>>> 0 output errors, 0 collisions, 0 interface
>>>> resets
>>>>
>>>> 0 unknown protocol
>>>> drops
>>>>
>>>> 0 babbles, 0 late collision, 0
>>>> deferred
>>>>
>>>> 0 lost carrier, 0 no
>>>> carrier
>>>>
>>>> 0 output buffer failures, 0 output buffers swapped out
>>>>
>>>>
>>>> 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
Received on Sat Apr 11 2009 - 05:09:01 ART