Ken, first of all, thanks, it helps.
Let me se if I understand you
portals of the same portal group (sharing same tag) can be
for multiple connections in session.
Portals of different portal groups can be used for multiple
sessions - and
used by the initiator anyway it likes, e.g. in your example
below, open two
sessions, use one actively, and if it fails, use the other
It does make sense,
Router 1 SendTargets response:
Router 2 SendTargets response:
The initiator puts 2 and 2 together (ok, 1 and 2, but you
see what I mean), and comes up with:
it knows three things:
The name of the target
(2) That it can be reached via two
(3) Connections on those portals cannot
be spanned into the one session
can choose to login via either or both portals whenever it likes. There
is no need for the routers to do any IP failover.
On Oct 3, 2006, at 4:04 AM, Dan Bar Dov wrote:
It is true that you cannot run two active connections
same session when going through two
However, is it not possible to
have a single active connection,
and fail-over to a new (or a
standby) connection ?
The problem is that putting both routers in the same Target Portal
Group (TPG) means exactly that the initiator CAN have two active
connections, in the same session, through the two portals.
So why do you want them in the same portal group? Why not just give
each router a different TPG and be done with it?
each target is in a different TPG, how do I achieve fail-over between
(other than maintaining some heart-beat between them, and moving the router IP address