Configuring Virtual Server in Active-Standby (or failover) mode

I want all traffic going to server A, and server B being configured as backup unit should server A fails.

have you checked priority group activation configuration? is it what you are looking for?

Thanks for guiding me through this. I found this article on F5 site: http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-concepts-11-3-0/ltm_pools.html?sr=37506658 There is a paragraph at about 2/3 of the article as follow: *** Quote *** Priority group number The Priority Group feature assigns a priority number to the pool member. Within the pool, traffic is then load balanced according to the priority number assigned to the pool member. For example, pool members assigned to group 3, instead of pool members in group 2 or group 1, normally receive all traffic. Thus, members that are assigned a high priority receive all traffic until the load reaches a certain level or some number of members in the group become unavailable. If either of these events occurs, some of the traffic goes to members assigned to the next higher priority group. This setting is used in tandem with the pool feature known as Priority Group Activation. You use the Priority Group Activation feature to configure the minimum number of members that must be available before Local Traffic Manager begins directing traffic to members in a lower priority group. *** Unquote ***

Will this guarantee that all traffic goes to server A until it fails before going to server B?

Regards, Alain

Will this guarantee that all traffic goes to server A until it fails before going to server B?

yes

you have 1 active node and 1 standby node, haven't you?

when previous active node (e.g. A) comes back up, existing connection still goes to new active node (e.g. B) but new connection will go to the previous one (A).

Thank you very much for your advice. This is exactly what I need.

Best regards, Alain

I have a similar situation and have previously configured the Active/Standby and it works properly except for one issue. I've got two LDAP servers, not using the iApp for LDAP, but a simple VS and monitor checking port 389.

My problem is that the primary server, if the LDAP service is disabled, takes too long to mark the server down before the Standby server becomes active. It's obviously the monitor taking too long to mark the server down. I don't want to set the timeout too low and get false positive failovers.

We have a similar setup on our ACE which we are migrating from and it works perfectly there using the same timeout settings. My end user has a script that is doing repeated LDAP queries where he ran it against the ACE and there was no interruption and then on the F5 where he clearly lost connection until the standby server comes up.

Any advice would be appreciated.

Steve