From: Wu, Jiang (wujiang@xxxxxxxxx)
Date: Sun Dec 17 2000 - 23:41:28 GMT-3
Not quite understand your second question. For the first one, ethernet redundan
cy feature is not for backup, it provides redundancy and load balancing. If R4
is hub, I think it is a good practice. A way for backup is to use backup peer.
But in your topology, it seems no router can become backup when R5 fails...
----- Original Message -----
From: Ronnie Royston <RonnieR@globaldatasys.com>
To: <ccielab@groupstudy.com>
Sent: Monday, December 18, 2000 3:18 AM
Subject: DLSw + SRTrans Compatibility?
> I have: R3,2,and 5 share a switched e-net, R2,5,4 share frame, R5 is
> hub.
>
> R3-----------R5
> \ / \
> \ / \
> R2 R4
> | |
> token1 token2
>
> I am asked to config DLSw between To1 and To2 and between R5 and R4 (this
> peering allows hosts on the e-net to connect to To2). R3 is to act as DLSw
> backup for R5 to To2.
>
> I used the ethernet (switched) redundancy feature to provide the backup. Is
> this the best/only way to accomplish the objective?
>
> Leter, the lab asked me to accomodate an low latency application (UDP 6500)
> between To1 and the e-net by configuring the e-net interface on R2. I
> wanted to set up ip policy routing to set the IP precedence to critical for
> UDP 6500 for traffic to the IP address of my DLSw peer that connects to the
> e-net. But the lab says to accomplish the objective by configuring R2's
> e-net interface ( and it seems dumb to go across the network and back when
> you could just SRTranslate to the e-net ). How can I configure this?
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:04 GMT-3