ACE at production site, CSS at DR

Unanswered Question
Jul 14th, 2008
User Badges:

Hi


We have ACE modules at our primary production site in an active/standby config - and have been working fine for some time.

eg.


context ace1

description context1

allocate-interface vlan 10

allocate-interface vlan 11

context ace2

description context2

allocate-interface vlan 20

allocate-interface vlan 21


There is a bridge group in each context and the ip range for context1 is 10.1.1.x and context2 is 10.2.2.x.


Rservers and VIPs in context1 are therefore in the 10.1.1.x range; in context2 they are in the 10.2.2.x range.


For a DR site, we want to use a CSS11506 to act as the load balancer in case of a disaster at the production site.


Is it possible for the CSS11506 to be configured to act the same as the ACE in case of a DR scenario? ie. Can a CSS be configured to so the same job as the ACE, maintaining the IP addresses assigned to the rservers/vips/vlans?


We need to have the IP addressing at DR to be the same the production site (vlans can be created at DR as required and are independent of the production site) - however the DR site is only 'active' when the production site is destroyed (or in testing obviously).


What would a sample config on the CSS11506 look like given the above ACE configuration?

(It's my first attempt at configuring a CSS!)


Cheers guys

Cameron

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
diro Thu, 07/17/2008 - 09:55
User Badges:
  • Bronze, 100 points or more

hi,


It is possible to have a css to do the same functionality. The context principle does not exist but you have the similar interface/vip redundancy see:


http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20_v8.10/configuration/redundancy/guide/redundgd.html


Bridging can also be done see:


http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20/configuration/routing/guide/rtbrgdgd.html


Keep in mind that the policies are replaced by owner & content rules, serverfarms do not exist, real servers are called services and predictors are callled loadbalancing systems:


http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20/configuration/content_lb/guide/cntlbgd.html




Actions

This Discussion