Forum Discussion
Dayesh_263997
Nimbostratus
NimbostratusClient 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 as there is no mechanism in the DB server to monitor failure of the active server.
The requirement is to direct all the traffic from web server towards the active DB server (always) through LTM unless Active server fails and standby server takes over.
It reminds of me of using a persistence profile. The only worry is that traffic will continue to be directed towards the active server even after its failure.
Could anyone suggest any better approach to achieve this?
Thanks,
Dayesh
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.
RyannnnnnnnnAltocumulus
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.
Dayesh_263997Hi Ryan,
Thanks for your input.
I will take care of it. Do you recommend any specific approach to achieve the objective of sending the client request to the active server?
Thanks,
Dayesh
- Ryannnnnnnnn
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.
- Dayesh_263997
Thanks Ryan,
I will get back in case of any further queries.
Thanks,
Dayesh
Ryan_80361Cirrostratus
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.
- Dayesh_263997
Hi Ryan,
Thanks for your input.
I will take care of it. Do you recommend any specific approach to achieve the objective of sending the client request to the active server?
Thanks,
Dayesh
- Ryan_80361
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.
- Dayesh_263997
Thanks Ryan,
I will get back in case of any further queries.
Thanks,
Dayesh