Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello, We have a CSS 11501 unit connected to several servers for load balancing which has been running fine for over 12 months. Lately however we had been recieving complaints that our web pages have been loading slowly, sometimes 2-3 minutes to load...
Hello, I am using a CSS11501 for load balancing and have setup http keepalive services for both servers. At the moment I am running one web server. The sh keepalive-summary is showing that server1 is up, but the http keepalive for it is down. When us...
hello, I've setup a CSS115001 for load balancing two web servers. I am using just the basic L3 rule for load balancing and noticed that every so often I get this error:-"MAR 17 10:00:56 1/1 29 IPV4-4: Duplicate IP address detected for vip: 65.214.xx....
Hello, I have two servers setup on ip addresses 10.10.0.1/10.10.0.2 and want to setup a layer 3 balance using VIP of 192.168.0.100, is this possible or do the server ip's and vip have to be on the same subnet?? (The 192.168.0.100 is only for interna...
Hi, I've setup a CSS to load balance between 2 servers using layer3 balancing, but I discovered that when requesting a dns lookup (the two servers are acting as primary dns servers), I get the following response from a terminal nslookup:-';; reply fr...
The only problem with using "balance leastconn' is that we use session files on our web servers so wouldn't that confuse the client if suddenly the CSS moved that client's requests to a different server within the same session?Also I'm concerned abou...
Okay, I did what you suggested about re-configuring the keepalive uri using "/keep.html" and that fixed the problem. I think what was happening was that the the webserver would return a "forbidden" error to the CSS. Thanks.. - Trevor
But what about the config that I have for layer3 load balance? That should not have caused a crash either? We have about 180-200requests a second to the web servers so I presume the CSS would not have a problem with that? - Trevor
Okay I believe I've fixed the duplicate ip message. We have a Pix Firewall connected to a port on the CSS and the global config ip range overlapped the VIP ip address used on the CSS itself. Now this is fixed, would this have caused the CSS to crash?...
