<html>
<body>
But this is the so called "SYM-active" mode and therefore not
at all related to hot-standby which seems to be what Chris is using at
the moment. <br><br>
@Chris,<br><br>
I guess this is a config problem. The last paragraph of your email below
sounds like a conf sync problem now and not like a failover problem
anymore. Search for "config-sync" in the latest documentation
and you are going to find the stuff to synchronize the
configuration.<br>
Attach the configs or cut&paste them to the mail in case you are
talking about a failover problem at the network level (L2 or
L3).<br><br>
R, Oliver<br><br>
<br>
At 06:39 04.02.2008, Joseph Jackson wrote:<br>
<blockquote type=cite class=cite cite="">Here ya go. <br><br>
This is from the "active" SI<br><br>
server virtual <a href="http://www.website.com">www.website.com</a>
<a href="http://192.168.1.1">192.168.1.1</a><br>
sym-priority 10<br>
port http<br>
port ssl sticky concurrent<br>
bind http server1 http server2 http<br>
bind ssl server1 ssl server2 ssl<br><br>
From the "standby" SI<br><br>
server virtual <a href="http://www.website.com">www.website.com</a>
<a href="http://192.168.1.1">192.168.1.1</a><br>
sym-priority 20<br>
port http<br>
port ssl sticky concurrent<br>
bind http server1 http server2 http<br>
bind ssl server1 ssl server2 ssl<br><br>
Whatever virtual server has the lower sym-priority will be the SI that
traffic flows through it. In this way you can have groups of
servers being load balanced on each other so that your SI's can be both
active at the same time. <br><br>
HTH<br><br>
Joseph<br><br>
<br>
On 2/1/08, <b>Chris Price</b>
<<a href="mailto:cprice@its.to">cprice@its.to</a>> wrote:<br>
<dl>
<dd>Oliver Adam wrote:<br>
<dd>> The virtual server failover is bound to the switch failover in
a<br>
<dd>> hot-standby setup. There is no need for the real servers to fail
over.<br>
<dd>> They do see the same MAC before and after the failover and I do
not<br>
<dd>> know what you mean with a real server failover.<br>
<dd>><br>
<dd> I am obviously missing something easy here.
I'll try and illustrate<br>
<dd>my simple setup that I am using for learning purposes with the
SI's;<br><br>
<dd> I have two SI's: lb1 and lb2 configured in a
hot-standby ha pair. I<br>
<dd>defined a 'server source-ip-standby <ip> <mask>
<gateway>' on lb1 and<br>
<dd>lb2 to provide a failover gateway ip for systems being load balanced.
I<br>
<dd>have tested the failover gateway ip functionality and it works as
expected.<br><br>
<dd> Lets assume that lb1 is my current active node and lb2
is the standby<br>
<dd>node in my hot-standby ha pair.<br><br>
<dd> I defined two real servers (realA and realB) and a
virtual server<br>
<dd>(virtA) on lb1. I bound realA and realB http port to virtA. Http<br>
<dd>requests to virtA's ip sees traffic being distributed to both realA
and<br>
<dd>realB in a round-robin fashion. This is all expected for my
basic<br>
<dd>configuration.<br><br>
<dd>THE PROBLEM:<br><br>
<dd>When I force a 'reload' on lb1, and the hot-standby HA
configuration<br>
<dd>fails over to lb2 (ie: lb2 becomes the active node), my real servers
and<br>
<dd>virtual server config are not 'failed' over.<br><br>
<dd>My experience with Cisco Arrowpoint and F5 is that there is some sort
of<br>
<dd>sync to peer config that must be run to sync config changes on
the<br>
<dd>active node to the backup node. For the life of me I cannot find
any<br>
<dd>information in the Foundry docs (slb guide, hardware install guide,
etc)<br>
<dd>on how to propagate changes from the active node to the backup
node.<br><br>
<dd>Does that make sense?<br><br>
<br><br>
<br><br>
<dd>_______________________________________________<br>
<dd>foundry-nsp mailing list<br>
<dd><a href="mailto:foundry-nsp@puck.nether.net">
foundry-nsp@puck.nether.net</a><br>
<dd>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" eudora="autourl">
http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br><br>
</dl><br>
_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" eudora="autourl">
http://puck.nether.net/mailman/listinfo/foundry-nsp</a></blockquote>
<x-sigsep><p></x-sigsep>
Oliver Adam<br>
<font face="Times New Roman, Times" size=2>Foundry Networks<br>
Systems Engineer L4/L7 Central Europe<br>
</font></body>
</html>