Jump to content
Welcome to our new Citrix community!

default lb should not take the hit, if state update is disabled.


Recommended Posts

We have Content switching vserver configured on ADC, which have lots of cs policies and each policy is binded to respective lb vserver. 

If State update is disabled on CS Vserver, and if there is one non-default lb which is down, traffic should not hit the default lb vserver. 

 

But in our case its still hitting the default lb vserver. what is the fix to drop the request if matching cs policy lb is down. 

 

-Thanks, At

Link to comment
Share on other sites

Which version of adc firmware are you on?

 

I think you are using state update for the wrong thing. If you want the cs vserver in a DOWN state with no valid destinations so the cs vserver's backup methods can kick in like its backup vserver or redirect URL then you need state update:enabled.  

If you want to rely on the default vserver's to handle the backup methods, then you need state update "disabled" and you will rely on the default lb vservver to have the backup vserver (method) or responder policies so it remains in an always up state (redirect url would not work, as the lb vserver would then be effectively down).

 

CS vserver:

State update "disabled", means the cs vserver ignores destination vserver status'.

State update "enabled" means the cs vserver will depend on destination services up/down status.  Unless a default vserver is specified, and then it wins.  See below.  If you need traffic to spillover, then you may need to construct your cs vserver so the default vserver isn't needed; or make its up/down state dependent on a monitor against the other vservers (would require a bit more work)

 

 

From Admin Guide:  https://docs.citrix.com/en-us/citrix-adc/current-release/content-switching/protecting-against-failure.html#configuring-the-state-update-option

When State Update is disabled:

The status of the content switching virtual server is marked as UP. It remains UP even if there is no bound load balancing virtual server that is UP.

When State Update is enabled:

When you add a content switching virtual server, initially, its status is shown as DOWN. When you bind a load balancing virtual server whose status is UP, the status of the content switching virtual server becomes UP.

If more than one load balancing virtual server is bound and if one of them is specified as the default, the status of the content switching virtual server reflects the status of the default load balancing virtual server.

If more than one load balancing virtual server is bound without any of them being specified as the default, the status of the content switching virtual server is marked UP only if all the bound load balancing virtual servers are UP.

 

So if you describe what you want to do, then we can probably help you figure out a way to do it.

Either use state-update enabled, and rely on default vserver to do the "failover" work.

Or use state-update disabled (with no default vserver) and use the cs vserver's backup vserver or redirect url feature to handle things instead.

Link to comment
Share on other sites

2 hours ago, Cisco Datacenter Team said:

But in our case its still hitting the default lb vserver. what is the fix to drop the request if matching cs policy lb is down. 

 

(Re-read your post)

Second part:

If you want regular traffic that would normally hit another vserver to be dropped when it goes to the default lb vserver. 

You would need to bind additional responder policies to the lb vserver you use as default and let it say if traffic is here and is traffic "x", drop this request. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...