RE: OSPF neighbor problem - fixed

From: Lab Candidate (labccie@xxxxxxxxx)
Date: Thu Jun 06 2002 - 23:43:12 GMT-3


   
Hi group,

Thanks to everyone who responded and offerred helpful advice.
Although after many hours of troubleshooting and tried out every piece of advic
e I received from
list members, the routers had decided to keep doing what they wanted and refuse
d to cooperate. All
of us think that the configs are correct and I just went ahead and got it worki
ng without knowing
why by doing a config-reg 0x42 and reboot. ever since, everything came back in
order.
I guess I just got one of those days and wasted a whole day of time on it. Than
ks again!

--- Stephen Austin <routepackets@earthlink.net> wrote:
> Two things you might want to check:
>
> (1) Turn OFF spanning tree on the connected ports on the switch.
>
> (2) Enable 'ip cef' on the routers.
>
> I have experienced a similar ping results in a WAN environment, and the
> above resolved the problem.
>
> Regards,
> Steve
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Mingzhou Nie
> Sent: Wednesday, June 05, 2002 10:12 PM
> To: Lab Candidate; Derekc@mad.scientist.com; ccielab@groupstudy.com
> Subject: RE: OSPF neighbor problem
>
> How many switches in between two routers? Is there a noncisco switch
> involved? Sounds like an IOS bug to me.
>
> --- Lab Candidate <labccie@yahoo.com> wrote:
> > Derek, rebooted the switch to no vail. and here's how it turned out
> > for extended ping with 100
> > packets of 1500 bytes. I am going to check the physical
> > cable/connections.
> > Also changed the ip ospf network to nonbroadcast and put in neighbors
> > on both r3 and r5, it's
> > stuck in init and sttempt states:
> >
> > r3#sh ip os n
> >
> > Neighbor ID Pri State Dead Time Address
> > Interface
> > 170.10.30.1 0 FULL/DROTHER 00:01:35 170.10.80.4
> > Serial0/1
> > 198.133.219.25 0 FULL/DROTHER 00:01:39 170.10.80.2
> > Serial0/1
> > N/A 0 ATTEMPT/DROTHER - 170.10.54.2
> > Ethernet0/0
> > r3#
> >
> > r5#sh ip os n
> >
> > Neighbor ID Pri State Dead Time Address
> > Interface
> > 170.10.50.1 1 INIT/DROTHER 00:01:05 170.10.54.1
> > FastEthernet0/0
> > r5#
> >
> >
> > r3#p
> > Protocol [ip]:
> > Target IP address: 170.10.54.2
> > Repeat count [5]: 100
> > Datagram size [100]: 1500
> > Timeout in seconds [2]:
> > Extended commands [n]:
> > Sweep range of sizes [n]:
> > Type escape sequence to abort.
> > Sending 100, 1500-byte ICMP Echos to 170.10.54.2, timeout is 2
> > seconds:
> >
> !!!!!!!!.!!.!!.!!!!.!!!!.!!.!!!!.!!!!.!!.!!!!.!!!!!.!.!!!!.!!!!!.!!!!!
> > !!.!.!!.!.!!!!!
> > 00:54:30: %OSPF-5-ADJCHG: Process 9, Nbr 170.10.40.1 on Ethernet0/0
> > from EXSTART
> > to DOWN, Neighbor Down: Too many retransmitions.!.!!!!!.!.!!.!
> > Success rate is 77 percent (77/100), round-trip min/avg/max =
> > 192/349/1943 ms
> > r3#
> >
> > --- "Derekc@mad.scientist.com" <derekc@mad.scientist.com> wrote:
> > > Everything you have shown so far seems fine. Here are two
> > suggestions you
> > > might want to try:
> > > Do an extended ping (100 large size packets) from one router to
> > another and
> > > see if your have any significant packet drops. If so, try to
> > change your
> > > CAT5 cable.
> > > If your CAT 5 cables are good, then try this. Change your Ethernet
> > and Fast
> > > Ethernet from OPSF network broadcast to OSPF network NMBA and then
> > specific
> > > each other as neighbor. If that fixed your problem (a big IF at
> > that),
> > > check your VLAN and port configuration. The VLAN (or port) might
> > have
> > > multicast turn off.
> > > If your switch is configured properly, try reloading the switch.
> > And then
> > > revert your router Ethernet and Fast E interface back to broadcast.
> > > I hope this help. Otherwise you really SOL
> > > Good luck,
> > > Derek
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
> > Of Lab
> > > Candidate
> > > Sent: Wednesday, June 05, 2002 1:48 PM
> > > To: Edward Monk; 'Bauer, Rick'; 'Michael Breen'
> > > Cc: ccielab@groupstudy.com
> > > Subject: RE: OSPF neighbor problem
> > >
> > > Thanks all for all the response and good advices. this is what i've
> > done:
> > > 1. the routers have been rebooted before i posted for help
> > > 2. they are up for over 10 hours now, and still doing the same
> > thing.
> > > 3. they can ping each other over the e0/0 and f0/0.
> > > 4. they are both using ios 12.2(7a), see below show version
> > > 5. both intf's are plugged in Cat3548's f0/4 and f0/7 and vlan'ed
> > in vlan8:
> > > #show cdp d
> > > r3 Fas 0/4 169 R 2612
> > Eth 0/0
> > > r5 Fas 0/7 124 R 2621
> > Fas 0/0
> > > #show vlan
> > > 8 VLAN0008 active Fa0/4, Fa0/6,
> > Fa0/7, Fa0/9
> > >
> > > 6. i don't think it's hardware problem, and routers, intf's,
> > cat3548 have
> > > been working fine.
> > > 7. as to Guy Lupi's advice, I used half-duplex before and changed
> > it to
> > > full, to no joy.
> > >
> > > now what? ;-)
> > >
> > > r3#sh ver
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(7a), RELEASE
> > SOFTWARE
> > > (fc
> > > 2)
> > > Copyright (c) 1986-2002 by cisco Systems, Inc.
> > > Compiled Thu 21-Feb-02 03:48 by pwade
> > > Image text-base: 0x80008088, data-base: 0x8153F5D0
> > >
> > > ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
> > >
> > > r3 uptime is 10 hours, 14 minutes
> > > System returned to ROM by reload
> > > System image file is "flash:c2600-jk9o3s-mz.122-7a.bin"
> > >
> > > cisco 2612 (MPC860) processor (revision 0x300) with 61440K/4096K
> > bytes of
> > > memory
> > > .
> > > Processor board ID JAD05500CQ6 (2044823788)
> > > M860 processor: part number 0, mask 49
> > > Bridging software.
> > > X.25 software, Version 3.0.0.
> > > SuperLAT software (copyright 1990 by Meridian Technology Corp).
> > > TN3270 Emulation software.
> > > Basic Rate ISDN software, Version 1.1.
> > > 1 Ethernet/IEEE 802.3 interface(s)
> > > 1 Token Ring/IEEE 802.5 interface(s)
> > > 2 Serial(sync/async) network interface(s)
> > > 1 ISDN Basic Rate interface(s)
> > > 32K bytes of non-volatile configuration memory.
> > > 16384K bytes of processor board System flash (Read/Write)
> > >
> > > Configuration register is 0x2102
> > >
> > > r3#
> > > 10:15:32: %OSPF-5-ADJCHG: Process 9, Nbr 5.5.5.5 on Ethernet0/0
> > from EXSTART
> > > to
> > > DOWN, Neighbor Down: Too many retransmitions
> > > r3#
> > > 10:16:32: %OSPF-5-ADJCHG: Process 9, Nbr 5.5.5.5 on Ethernet0/0
> > from DOWN to
> > > DOW
> > > N, Neighbor Down: Ignore timer expired
> > > r3#
> > > 10:17:52: %OSPF-5-ADJCHG: Process 9, Nbr 5.5.5.5 on Ethernet0/0
> > from EXSTART
> > > to
> > > DOWN, Neighbor Down: Too many retransmitions
> > > r3#
> > > 10:18:52: %OSPF-5-ADJCHG: Process 9, Nbr 5.5.5.5 on Ethernet0/0
> > from DOWN to
> > > DOW
> > > N, Neighbor Down: Ignore timer expired
> > > r3#
> > >
> > > r5#sh ver
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(7a), RELEASE
> > SOFTWARE
> > > (fc
> > > 2)
> > > Copyright (c) 1986-2002 by cisco Systems, Inc.
> > > Compiled Thu 21-Feb-02 03:48 by pwade
> > > Image text-base: 0x80008088, data-base: 0x8153F5D0
>
=== message truncated ===



This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:28 GMT-3