</P><P>I am having difficulty with an OSPF demand circuit running over an async interface.
</P><P>The line comes up as desired with a dialer watch-group, however, when the line goes down again, OSPF shows the LSAs updating and re-dials. This continues every 120 seconds (idle-timeout) forever.
</P><P>As far as I can see, the links are configured properly (ip ospf demand-circuit, ip ospf network point-to-point).
</P><P>There are no other relevant factors (not redistributions or other unstable links).
</P><P>My network is configured roughly in a square.(This is the Hello Computers Security Lab 2 core network, for those of you with access. No other routers are configured right now so as to eliminate the possibility of interaction).
</P><P>Router 1 and 5 share an ethernet LAN that is area 0.
Router 5 is connected to router 2 via frame.
Router 2 is connected to router 4 via frame.
Router 4 is connected to router 5 via the DDR async.
All frame/DDR networks are area 1.
[R5] --/DDR/-- [R4]
[R1] -/Frame/- [R2]
<P>I have reviewed, investigated, and attempted all the applicable fixes listed at the following URL:
I was looking to your configs and I found somethings I don't understand...
First, the following ACL:
access-list 9 deny 220.127.116.11 18.104.22.168
access-list 9 deny any
access-list 9 permit any
doesn't make much sense to me, because on the second statement you deny everything and then you permit everything... If you are using "ip ospf demand-circuit" you don't need to define OSPF as uninteresting traffic,which I think you were trying to do with the first statement on the ACL 9. You are denying a multicast source address (22.214.171.124) which never happens! If you want to deny OSPF you should use an extended ACL denying OSPF.
On router 5 you are using dialer-watch and OSPF demand-circuit. I've never tried to use both at the same time. If you use dialer watch you should define OSPF as uninteresting traffic... Maybe the dialer-watch feature overrides the demand-circuit feature, and as you didn't define OSPF as uninteresting traffic on router R5 the link is kept up.
Yeah, ignore that ACL... I put that in there because I was having problems where both sides would initiate a call at the same time and it would result in endless busy signals. It's in there for troubleshooting only, not to effect the operation of the demand circuit.
As for the dialer watch stuff, it works the same even if it is gone. I put that in there for troubleshooting because the routers would not initiate a call on boot-up and thus never learn the route to begin with (I suspect that this is related to the original problem).
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.