From: steven.j.nelson@xxxxxx
Date: Thu Mar 28 2002 - 09:00:58 GMT-3
Thanks Bob,
I'll give it a shot.
-----Original Message-----
From: Bob Sinclair [mailto:bsin@erols.com]
Sent: 28 March 2002 11:58
To: Nelson,SJ,Steven,IVNH25 C
Cc: ccielab
Subject: Re: Dialer Watch
Steven,
>From what I have seen, you may want to make IP uninteresting in the dialer
list. This would include OSPF. When I test it, I make only icmp
interesting for testing purposes. Let dialer watch control link
initiation.
-Bob
----- Original Message -----
From: <steven.j.nelson@bt.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, March 28, 2002 6:31 AM
Subject: Dialer Watch
> All,
>
> I have been experimenting with Dialer Watch as a backup medium to frame
> relay and using ospf as the routing protocol.
>
> CCO says this should work
> www.cisco.com/warp/public/access_dial/bri_isdn_11048.html
>
> However when using this config ospf packets multicasted to the 224.0.0.5
> address keep the isdn link active, I have tried every combination to get
> this working, i.e :-
>
> No peer neighbor routes
> ISDN Point to Point network types
> etc etc
>
> obv an access list solves this, but then ospf dies.
>
> And I have come to the conclusion that to use dialer watch as a backup
> medium in conjunction with ospf you need to have demand circuit enabled as
> well as dialer watch, as demand circuit kills the hellos etc ect and
dialer
> watch looks after the watched routes.
>
> Has anyone else come across this scenario ?
>
> Thanks
>
> Steve
>
> Steve Nelson
> Customer Engineer
> BT Ignite- National Solutions
> T: +44 (0)1422 338881 M: +44 (0)7811 944172
> e-mail: steven.j.nelson@bt.com
> pp HW A170, PO Box 200(HOM-NZ), London, N18 1ZF
> > British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ
> > Registered in England no. 1800000.
> > This electronic message contains information from British
> Telecommunications plc which may be privileged or confidential. The
> information is intended to be for the use of the individual(s) or entity
> named above. If you are not the intended recipient be aware that any
> disclosure, copying, distribution or use of the contents of this
information
> is prohibited. If you have received this electronic message in error,
please
> notify us by telephone or email (to the numbers or address above)
> immediately.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:24 GMT-3