Forum Discussion

Dayesh_263997's avatar
Dayesh_263997
Icon for Nimbostratus rankNimbostratus
Oct 24, 2018
Solved

Client request sent to Single server

Hi Team,   Traffic originated from the Web server (Client) towards the DB server (Backend server).   DB server is functioning in Active/Passive mode. Traffic from the Web server is through LTM ...
application delivery
LTM
  • Ryan_80361's avatar
    Ryan_80361
    Oct 24, 2018

    Are you only dealing with 2 servers (one active and one passive)? if so, you don't need to use a persistence profile. I'd also consider enabling manual resume on your primary server so that it doesn't come back online automatically after it's gone down in the pool. That way you can manage it back in without having a split brain situation.

     

Ryan_80361's avatar
Ryan_80361
Icon for Cirrostratus rankCirrostratus

Are you only dealing with 2 servers (one active and one passive)? if so, you don't need to use a persistence profile. I'd also consider enabling manual resume on your primary server so that it doesn't come back online automatically after it's gone down in the pool. That way you can manage it back in without having a split brain situation.

 

Ryan_80361's avatar
Ryan_80361
Icon for Cirrostratus rankCirrostratus
Oct 24, 2018

You can create priority groups, assign one priority group to each server (e.g. the primary server has a priority group of 100 and the standby server has a priority of 50) and set priority activation to be less than 1 available members. Traffic should only be sent to the higher priority group (with your primary server in it) until it fails and the second priority group takes over.