From: Matt Holbert (mholbert@xxxxxxxxxxx)
Date: Fri Oct 06 2000 - 17:11:51 GMT-3
Tim,
I setup something like this in a lab:
R5 <-----BRI----->R6
R5 is a member of area 2. R6 is a member of area 1. The access-list for the
dialer-list permits only decnet packets, not decnet routing. I also have a
default route on each box that points to the bri interface.
It works like this: a packet with an unknown route is forwarded to the bri
interface for transport to the other side. The routing updates will travel
across the link during this time, but they will not reset the idle timer.
I hope this is what you are looking for. The configurations are below:
R6
decnet routing 1.6
decnet node-type area
interface BRI0
no ip address
no ip directed-broadcast
dialer string 8358661
dialer-group 1
decnet cost 1
isdn switch-type basic-5ess
isdn spid1 0835866201 8358662
dialer-list 1 protocol decnet permit
decnet route default bri 0
R5
decnet routing 2.5
decnet node-type area
interface BRI0
no ip address
no ip directed-broadcast
dialer string 8358662
dialer-group 1
decnet cost 1
isdn switch-type basic-5ess
isdn spid1 0835866101 8358661
dialer-list 1 protocol decnet permit
decnet route default bri 0
> -----Original Message-----
> From: Tim Haines [mailto:thaines@energis-eis.co.uk]
> Sent: Wednesday, October 04, 2000 9:10 AM
> To: ccielab@groupstudy.com
> Subject: DECnet Dilemma!
>
>
> Hi, All.
> I realise that this may be somewhat "off-tangent" from the
> core-study of the
> group, but I was wondering whether any of you had come across
> any scenarios
> involving DECnet (inter) area routing over ISDN. I have been
> trying to do
> this in our Lab (at the request of a customer) but I'm not
> convinced that it
> can be done.
> The idea is that the implementation uses ISDN as DDR (i.e.
> NOT a backup
> scenario), but the Hello packets required for the adjacencies
> keep bringing
> the link up every 15 seconds. Also, the fact that the DECnet address
> (area.node) is a property of the box creates an interesting "Catch22"
> situation in that how can you route traffic to unknown networks via a
> next-hop node that you don't even know about because there is
> no adjacency
> for it? I have thought about increasing the Hello interval, but my
> understanding is that this is not a reliable packet and will
> therefore be
> lost during the call set-up, so the adjacency will never be
> established.
>
> All the example configurations I have seen seem to imply that
> DECnet over
> DDR works for intra-area, not inter-area implementations. I
> have tried some
> of these configs myself, but still have the dilemma of the
> level-1 Hellos
> bringing up the link. Is there a way to suppress the Hellos or even
> configure a static adjacency?
>
> Any pointers greatly appreciated!
> Thanks,
> Tim.
>
> --------------------------------------------------------------
> ---------------------------------------------
>
> This email is confidential and intended solely for the use of
> the individual to
> whom it is addressed. Any views or opinions presented are
> solely those of the
> author and do not necessarily represent those of Energis
> Integration Services.
> If you are not the intended recipient, be advised that you
> have received this
> email in error and that any use, dissemination, forwarding,
> printing, or copying
> of this email is strictly prohibited.
>
> We have an anti-virus system installed on all our PC's and
> therefore any files
> leaving us via e-mail will have been checked for known viruses.
> Energis Integration Services accepts no responsibility once an e-mail
> and any attachments leave us.
>
> If you have received this email in error please notify
> Energis Integration Services Communications
> IT department on +44 (0) 1494 476222..
> --------------------------------------------------------------
> ---------------------------------------------
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:24 GMT-3