Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Ace load balancing, inservice/no inservice serverfarms

I've started working with an ACE load balancer and came across  something that just didn't add up to me. I can pull and put servers in  and out of rotation without a problem however when working with a  serverfarm or a group of servers I have to pull each one individually  and can't find a way to remove say the entire serverfarm via one  command. Does anyone know of a way to put a serverfarm 'inservice' or  set it to 'no inservice' that would make it easier for large groups of  servers needing to be adjusted.

Sorry if this isn't the write forum for this kind of question. Please feel free to move it if needed.

  • Application Networking
Everyone's tags (3)
3 REPLIES
Bronze

Re: Ace load balancing, inservice/no inservice serverfarms

Hello Chris,

  There is no toggle to set every rserver under a serverfarm out of service.  You can only take a single rserver out of service at a global level, or under a serverfarm inividually.

  One thing to think about  - bringing down all of the servers would be the same as removing the serverfarm from under the policy map type loadbalance since it would effectively bring the vip down.

Regards,

Chris Higgins

New Member

Re: Ace load balancing, inservice/no inservice serverfarms

Guys , will the sessions be terminated if the server was pulled out form the SF group ??

Sent from Cisco Technical Support iPad App

Bronze

Re: Ace load balancing, inservice/no inservice serverfarms

No, ACE will no longer balance new connections to the server you removed, existing connections are untouched and are allowed to close off gracefully or timeout.

Regards,

Chris

1862
Views
3
Helpful
3
Replies
This widget could not be displayed.