From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Sat Jan 11 2003 - 11:07:27 GMT-3
When you declare the local peer, use a loopback address. Let the routing protocol takes care of the
backup link between the two router.
example
R1
========================
int lo0
ip addr 1.1.1.1 255.255.255.0
dlsw local-peer peer-id 1.1.1.1
dlsw remote-peer 0 tcp 2.2.2.2
R2
========================
int lo0
ip addr 2.2.2.2 255.255.255.0
dlsw local-peer peer-id 2.2.2.2
dlsw remote-peer 0 tcp 1.1.1.1
By this way if the Frame is down, the remote peer address would be learned through the ISDN line.
But that is taken care off by the underlying IGP protocol.
Cheers,
Donny
Sage Vadi
<sagevadi@yahoo.c To: ccielab@groupstudy.com
o.uk> cc:
Sent by: Subject: DLSW: backup-peer
nobody@groupstudy
.com
11-01-2003 21:20
Please respond to
Sage Vadi
Hi all,
R1--------R4
R1 & R4 are connected via Frame "AND" ISDN. R1 is the
DLSW master (for want of a better word). The DLSW TCP
circuit is alive and well between them.
Requirement:
When the Frame circuit goes down, the DLSW circuit has
to be established though the ISDN.
Problem:
I cannot configure this on R4 as R1 has only got one
DLSW local peer-id?!?! Any ideas? All examples from
CCO show a backup-peer to another router, in my
situation the backup-peer is the same router hence my
dillema.
Cheers,
Sage
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3