From: Church, Chuck (cchurch@wamnetgov.com)
Date: Wed May 12 2004 - 15:53:06 GMT-3
Did you do a debug on OSPF - 'deb ip ospf hello' to see what going on?
Are both interfaces in the OSPF process?
Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Wam!Net Government Services - Design & Implementation Team
13665 Dulles Technology Dr. Ste 250
Herndon, VA 20171
Office: 703-480-2569
Cell: 703-819-3495
cchurch@wamnetgov.com
PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.
com
-----Original Message-----
From: Yash Bajpai [mailto:ccieyash@yahoo.com]
Sent: Wednesday, May 12, 2004 12:23 PM
To: Church, Chuck
Cc: ccielab@groupstudy.com
Subject: RE: ospf over async interface
thanks for replying Chuck!
The links are UP and stable. a thousand 1500 bytes PING packet goes
without dropping over the async link.
i have enabled CDP too and that works like a charm too.
But running OSPF or even RIP for that matter over this link is driving
me nuts. the processes just dont seem to wanna talk to to the neighbor.
i even tried manually configuring the neigbor for OSPF, but no luck!
--- "Church, Chuck" <cchurch@wamnetgov.com> wrote:
> Yash,
>
> You skipped some steps in troubleshooting the problem. Can IP
> (ping) get across the link, or CDP for that matter?
> If you do a show
> interface, is IPCP and/or CDPCP being negotiated?
> If no IPCP, the OSPF
> will never work. Are the interfaces staying up, or are they bouncing?
> Oh, and you are using a standard cisco console cable, right? Ethernet
> cables won't work.
>
>
> Chuck Church
> Lead Design Engineer
> CCIE #8776, MCNE, MCSE
> Wam!Net Government Services - Design & Implementation Team
> 13665 Dulles Technology Dr. Ste 250
> Herndon, VA 20171
> Office: 703-480-2569
> Cell: 703-819-3495
> cchurch@wamnetgov.com
> PGP key:
>
http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.
> com
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of Carlos G Mendioroz
> Sent: Wednesday, May 12, 2004 7:15 AM
> To: Yash Bajpai
> Cc: ccielab@groupstudy.com
> Subject: Re: ospf over async interface
>
> async default routing ?
> modem inout in the line ?
>
> I've never found a taxative explanation of the differences between
> async dynamic routing and async default routing, but both seem to be
> needed...
>
> BTW, do not be intimidated, we are all humans after all :-) Also,
> there's a lot of info in the archives. Archive searching is a great
> tool.
>
>
> Yash Bajpai wrote:
>
> > hello,
> >
> > this is my first email and i admit iam highly intimidated by the
> > complexity of some of the
> questions
> > posted.
> >
> > in any case, i have a seemingly simple issue with
> me.
> > i have two 2600 routers connected back to back
> using
> > the aux ports. i have the following configured on
> both
> > ends on the async.
> >
> > interface Async65
> > ip address 192.168.1.1 255.255.255.252 ip directed-broadcast
> > encapsulation ppp async dynamic routing async mode dedicated
> >
> > But no matter what i do, i cannot seem to get the
> ospf
> > adjaceny UP with its async neighbor. the "sh ip
> ospf
> > int" says the interface is passive. ofcourse, i
> have
> > not configured any interface as passive on either router.
> >
> > anyone has any clues on what i might be missing
> here?
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Win a $20,000 Career Makeover at Yahoo! HotJobs
> >
> http://hotjobs.sweepstakes.yahoo.com/careermakeover
> >
> >
>
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:10 GMT-3