From: McCallum, Robert (Robert.McCallum@xxxxxxxxxxxxxxxxxx)
Date: Mon Jan 07 2002 - 10:34:20 GMT-3
surely the only way to so this is to stop using loopback addresses and start us
ing the token ring interfaces ip address. No?
-----Original Message-----
From: omar guarisco [mailto:oguarisco44@hotmail.com]
Sent: 07 January 2002 13:24
To: ccielab@groupstudy.com
Subject: DLSW+ circuit establishment loopback vs. TRing
Hi,
I was wondering something about DLSw+...
I've this situation: 2 Router - R1 and R2 - both are connected to ring 100
on TRing interfaces. R1 is connected via switch to CoreRouter1 (VLAN50) and
R2 via another switch to CoreRouter2 (VLAN 51).BTW CoreRouter1 is connected
to CoreRouter2.
R1 is primary DLSw+ peer for remote routers R10, R11, R12, R13...and backup
peer is configured to be R2 for all.
The DLSw circuit will be established between R1X loopback and loopback on R1
as primary and loopback R2 as secondary (Backup peer).
The DLSw circuit between R1X loopback and R1 loopback is established ...and
all is working fine...via TRing interface on R1
Think that Interface TRing on R1 goes down...DLSw circuit will stay up (as I
suppose) seeing that loopback is always up...but SNA traffic can't pass via
Interface TRing on ring 100 on Router R1...seeing that DLSW circuit is up on
R1, and the backup peer R2 is not used....
Could someone tell me if exists another way guaranteeing that when TRing
interface goes down on Primary peer, secondary will be used (DLSW circuit
establishment) also if the end of DLSW circuit is another Interface
Omar
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:18 GMT-3