08-24-2012 05:34 PM - edited 03-07-2019 08:31 AM
Hi everyone,
Having some issues with load balancing two webservers using two CSS11501 content service switches (VIP/interface redundancy, Active/Backup, and Active Session Redundancy setup).
I've set up both CSSs to load balance the web servers behind it, and it works with Active/Backup setup. When I configure it with Active Session Redundancy though for stateful failover, I start to have issues. For example, as a test, I'm downloading a file through the load balancers from the web server. Mid-download, when I do a reboot on the master CSS, the download just suddenly stops (meaning, my ASR stateful config didn't work.. duhh). the funny thing is this: after the CSS finishes rebooting, and both are up again, I can't access the web servers through vip address at all (times out on my web browser). To get it up and running again, I would first need to unplug the ethernet cables from the master CSs, wait awhile, then re-attach.
I've tried many variations on fixing this issue, but have been unsuccessful. Any help is appreciated. I've attached the running config on both CSSs for your reference (i've chnaged the IPs around, of course, but you get the idea):
CSS 1:
!*************************** GLOBAL ***************************
global-portmap base-port 3000 range 30000
!************************* INTERFACE *************************
interface e2
bridge vlan 2
interface e7
isc-port-one
!************************** CIRCUIT **************************
circuit VLAN1
ip address 172.41.2.2 255.255.255.0
ip virtual-router 1
ip redundant-interface 1 172.41.2.254
circuit VLAN2
ip address 215.215.186.10 255.255.255.0
ip virtual-router 2
ip redundant-interface 2 215.215.186.254
ip redundant-vip 2 215.215.186.5
ip redundant-vip 2 215.215.186.3
!************************** SERVICE **************************
service ws1-80
ip address 172.41.2.10
keepalive type http
keepalive port 80
protocol tcp
redundant-index 1
active
service ws2-80
ip address 172.41.2.11
keepalive type http
keepalive port 80
protocol tcp
redundant-index 2
active
!*************************** OWNER ***************************
owner company1
content ws80-newvip
vip address 215.215.186.5
protocol tcp
port 80
add service ws1-80
add service ws2-80
redundant-index 102
active
content ws80-oldvip
protocol tcp
vip address 215.215.186.3
port 80
add service ws1-80
add service ws2-80
redundant-index 101
active
CSS2:
sh run
!*************************** GLOBAL ***************************
global-portmap base-port 33100 range 30000
!************************* INTERFACE *************************
interface e2
bridge vlan 2
interface e7
isc-port-one
!************************** CIRCUIT **************************
circuit VLAN1
ip address 172.41.2.3 255.255.255.0
ip virtual-router 1
ip redundant-interface 1 172.41.2.254
circuit VLAN2
ip address 215.215.186.11 255.255.255.0
ip virtual-router 2
ip redundant-interface 2 215.215.186.254
ip redundant-vip 2 215.215.186.5
ip redundant-vip 2 215.215.186.3
!************************** SERVICE **************************
service ws1-80
ip address 172.41.2.10
keepalive type http
keepalive port 80
protocol tcp
redundant-index 1
active
service ws2-80
ip address 172.41.2.11
keepalive type http
keepalive port 80
protocol tcp
redundant-index 2
active
!*************************** OWNER ***************************
owner company1
content ws80-newvip
vip address 215.215.186.5
port 80
protocol tcp
add service ws1-80
add service ws2-80
redundant-index 102
active
content ws80-oldvip
vip address 215.215.186.3
protocol tcp
port 80
add service ws1-80
add service ws2-80
redundant-index 101
active
08-27-2012 10:09 AM
just to add to the previous post, i didn't configure any critical services - but I don't believe this should be an issue. You can see in the configuration. As well, I don't have any issues with both CSSs failing over when I have both up and running, and I manually power down / or simply unplug one CSS... it fails over well from master to backup and vice versa.
I only have an issue when i reboot one CSS - it never seems to recover when I reboot, even after the one CSS comes back up.
Thanks again,
Harriet
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide