From: Jongsoo.Kim@Intelsat.com
Date: Tue Mar 01 2005 - 19:30:17 GMT-3
I think you can't use backup-peer command because the ip address you have to
use at below is R2's local peer ID.( so all three ip addresses end up being
same)
I think you have to point R2's loopback interface address and rely on
routing protocol to choose active path between 2 links.
Depending on routing protocol and topology, you can use all sort of options
coming with ISDN, such as snapshot routing, OSPF demand, Rip trigger, dialer
watch, backup interface...
Regards
Jongsoo
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Tuesday, 01 March, 2005 5:08 PM
To: Group Study
Subject: dlsw and backup
Hi guys,
Here's a simple dlsw scenario that I'm not sure how to configure. Any
ideas?
R1 <--> R2 have 2 links between them: 1 f/r and 1 isdn
I want R1 to use the isdn link if the f/r link goes down.
Both R1 and R2 need to pass dlsw traffic from their single LAN interface
across the ip cloud.
Here are the ip addresses being used:
R1:
lo0 = 1.1.1.1
E0 = 11.1.1.1
R2:
Lo0 = 2.2.2.2
E0 = 22.2.2.2
f/r = 12.0.0.0
isdn = 21.0.0.0
My problem is that I can't figure out what addresses I should use with which
commands.
Assume a single routing protocol and both routers know how to reach all ip
addresses when the f/r is up.
And, assume that only dlsw traffic is defined as interesting. If possible,
also assume that R2 is configured as promiscuous.
I know I need to use the following commands on R1:
dlsw remote-peer 0 tcp <pri ip addr of R2>
dlsw remote-peer 0 tcp <bkup ip addr of R2> backup-peer < pri ip addr of R2>
But, I'm not sure what addresses I should use.
Also, note that once the primary f/r link goes down, both R1 and R2 won't
know what networks are reachable on the other side of the isdn link until
the isdn link comes up and the routing protocol reconverges. (As usual,
static routes aren't allowed.)
Any suggestions?
TIA, Tim
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:38 GMT-3