[f-nsp] Getting started with ServerIron 4G

[Joseph Jackson]

opps sorry about that.  I forgot about the HA standby way.

On 2/4/08, Oliver Adam <oadam at madao.de> wrote:
>
> 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.
>
> @Chris,
>
> 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.
> 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).
>
> R, Oliver
>
>
> At 06:39 04.02.2008, Joseph Jackson wrote:
>
> Here ya go.
>
> This is from the "active" SI
>
> server virtual www.website.com 192.168.1.1
>  sym-priority 10
>  port http
>  port ssl sticky concurrent
>  bind http server1 http server2 http
>  bind ssl server1 ssl server2 ssl
>
> From the "standby" SI
>
> server virtual www.website.com 192.168.1.1
>  sym-priority 20
>  port http
>  port ssl sticky concurrent
>  bind http server1 http server2 http
>  bind ssl server1 ssl server2 ssl
>
> 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.
>
> HTH
>
> Joseph
>
>
> On 2/1/08, *Chris Price* <cprice at its.to> wrote:
>  Oliver Adam wrote:
> > The virtual server failover is bound to the switch failover in a
> > hot-standby setup. There is no need for the real servers to fail over.
> > They do see the same MAC before and after the failover and I do not
> > know what you mean with a real server failover.
> >
>      I am obviously missing something easy here. I'll try and illustrate
> my simple setup that I am using for learning purposes with the SI's;
>
>     I have two SI's: lb1 and lb2 configured in a hot-standby ha pair. I
> defined a 'server source-ip-standby <ip> <mask> <gateway>' on lb1 and
> lb2 to provide a failover gateway ip for systems being load balanced. I
> have tested the failover gateway ip functionality and it works as
> expected.
>
>    Lets assume that lb1 is my current active node and lb2 is the standby
> node in my hot-standby ha pair.
>
>    I defined two real servers (realA and realB) and a virtual server
> (virtA) on lb1. I bound realA and realB http port to virtA. Http
> requests to virtA's ip sees traffic being distributed to both realA and
> realB in a round-robin fashion. This is all expected for my basic
> configuration.
>
> THE PROBLEM:
>
> When I force a 'reload' on lb1, and the hot-standby HA configuration
> fails over to lb2 (ie: lb2 becomes the active node), my real servers and
> virtual server config are not 'failed' over.
>
> My experience with Cisco Arrowpoint and F5 is that there is some sort of
> sync to peer config that must be run to sync config changes on the
> active node to the backup node. For the life of me I cannot find any
> information in the Foundry docs (slb guide, hardware install guide, etc)
> on how to propagate changes from the active node to the backup node.
>
> Does that make sense?
>
>
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> Oliver Adam
> Foundry Networks
> Systems Engineer L4/L7 Central Europe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20080205/d10295d2/attachment.html>