Re: ospf over async interface

From: Kenneth Vargas (kvargas@varteksolutions.com)
Date: Thu May 13 2004 - 14:35:43 GMT-3


Sorry for the interrupt but what about the "Async default routing" command?

http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_command_refe
rence_chapter09186a00800ca4b4.html#6857

Regards,

Kenny Vargas, SEC+,CCNA/DA, CCNP
Senior Network Analyst
Planetgov inc.
www.planetgov.com
kvargas@planetgov.com

----- Original Message -----
From: "Yash Bajpai" <ccieyash@yahoo.com>
To: "Church, Chuck" <cchurch@wamnetgov.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, May 13, 2004 1:19 PM
Subject: RE: ospf over async interface

> here is my config for the router on one side...
>
> R3#sh run
> Building configuration...
>
> Current configuration : 862 bytes
> !
> version 12.2
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname R3
> !
> logging buffered 10000 debugging
> !
> ip subnet-zero
> !
> !
> no ip domain-lookup
> !
> !
> !
> !
> interface FastEthernet0/0
> ip address 192.168.10.1 255.255.255.0
> duplex auto
> speed auto
> !
> interface Serial0/0
> no ip address
> shutdown
> !
> interface Async65
> ip address 192.168.1.2 255.255.255.252
> ip directed-broadcast
> encapsulation ppp
> async dynamic routing
> async mode dedicated
> cdp enable
> !
> router ospf 1
> log-adjacency-changes
> network 192.168.1.2 0.0.0.0 area 2
> network 192.168.10.0 0.0.0.255 area 2
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 172.27.65.1
> no ip http server
> !
> !
> line con 0
> line aux 0
> modem InOut
> transport input all
> speed 38400
> flowcontrol hardware
> line vty 0 4
> exec-timeout 0 0
> privilege level 15
> password cisco
> login
> !
> end
>
> R3#
> --- "Church, Chuck" <cchurch@wamnetgov.com> wrote:
> > Send your int async65 configs, router ospf x
> > configs, and the line aux0
> > configs. The cause has got to be in one of those.
> >
> >
> > 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: Thursday, May 13, 2004 12:46 PM
> > To: Church, Chuck
> > Cc: ccielab@groupstudy.com
> > Subject: RE: ospf over async interface
> >
> > no there are no passive default or passive interface
> > configuration at
> > all.
> >
> > just for the heck of it, i even enabled ip
> > directed-broadcast (somehow
> > it made sense to me that time, but of no avail)
> > --- "Church, Chuck" <cchurch@wamnetgov.com> wrote:
> > > That's certainly it. Do you have passive default
> > in the router
> > > config?
> > >
> > >
> > > 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 3:29 PM
> > > To: Church, Chuck
> > > Cc: ccielab@groupstudy.com
> > > Subject: RE: ospf over async interface
> > >
> > > yes both the routers have their async under ospf
> > process. this is what
> >
> > > i see on both routers
> > >
> > > R2#sh ip ospf int async 65
> > > Async65 is up, line protocol is up
> > > Internet Address 192.168.1.1/30, Area 2
> > > Process ID 1, Router ID 192.168.100.1, Network
> > Type POINT_TO_POINT,
> > > Cost: 1111
> > > 1
> > > Transmit Delay is 1 sec, State POINT_TO_POINT,
> > > Timer intervals configured, Hello 10, Dead 40,
> > Wait 40, Retransmit 5
> > > No Hellos (Passive interface)
> > > Neighbor Count is 0, Adjacent neighbor count is
> > 0
> > > Suppress hello for 0 neighbor(s)
> > >
> > >
> > > ****************
> > >
> > > R3#sh ip ospf int async 65
> > > Async65 is up, line protocol is up
> > > Internet Address 192.168.1.2/30, Area 2
> > > Process ID 1, Router ID 192.168.10.1, Network
> > Type POINT_TO_POINT,
> > > Cost: 2631
> > > Transmit Delay is 1 sec, State POINT_TO_POINT,
> > > Timer intervals configured, Hello 10, Dead 40,
> > Wait 40, Retransmit 5
> > > No Hellos (Passive interface)
> > > Index 1/1, flood queue length 0
> > > Next 0x0(0)/0x0(0)
> > > Last flood scan length is 0, maximum is 0
> > > Last flood scan time is 0 msec, maximum is 0
> > msec
> > > Neighbor Count is 0, Adjacent neighbor count is
> > 0
> > > Suppress hello for 0 neighbor(s)
> > >
> > > my biggest doubt it the no hellos (PASSIVE
> > INERFACE) line. that is the
> >
> > > issue, i think. but why??....
> > >
> > >
> > > --- "Church, Chuck" <cchurch@wamnetgov.com> wrote:
> > > > 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
> >
> === message truncated ===
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:11 GMT-3