Load balancing http server

Hi There,
I want to implement a load balancer (linux virtual server) into our htmldb configuration. We currently run the http server on the same machine running oracle/htmldb. I want to split this out and use 2 seperate machines running http server behind the load balancer, both these http servers will be pointing to the same oracle database.
The load balancer will not be using persistent sessions, therefore client requests will be sent evenly to each http server. My main question is, will I have problems with user sessions, or (as I imagine) is all the session information written to the database ?
Thanks in advance.
Tom

Bill,
There are a few things you need to consider
1: Availability of http server. ie how many are you going to have. How are you going to access them. Load balancer, DNS round robin. These should be on different servers to the database.
2: How are the http servers going to connect. For RAC you'll need to specify TNS connections. I'd also recommend that you look at using application partitioning using services in the RAC cluster. That way you can have Apex using a subset of nodes in the cluster .
3: If you are going down the RAC path then I'd assume availability is a priority. You''ll need to think of standby configuration. Again this is possible with TNS configuration.
You can do it all with Apex. RAC and Standby but it will take planning and testing.

Similar Messages

Load Balancing HTTP requests to ABAP App Servers options?

Looking at SAP Documentations, SAP recommends to use the Web Dispatcher to load balance HTTP requests to multiply ABAP App servers.
My question is that the only solution? or can we use hardware such as the F5 BigIP to perform the same job?
Any thoughts?

In collaboration with SAP and SAP customers, F5 Networks has created a solution that delivers security, high availability, and improved performance for SAP web and portal technologies.
By deploying F5 Networks solutions with SAP NetWeaver, enterprises extend their control over their Network and Application traffic, and ensure the fast and secure delivery of their applications.
Benefits of F5 for SAP NetWeaver and Enterprise SOA
u2022 Cuts SAP Enterprise Portal login time by more than half for WAN users
u2022 Speeds document downloads
u2022 Reduces SAP server CPU utilization by 44%
u2022 Provides a 20x reduction in the number of SAP server-side connections
Further details, case studies and deployment guides on;
http://www.f5.com/solutions/applications/sap/netweaver/
F5 certification information on SAP Website
http://www.sap.com/partners/directories/SoftwareISVSolutions.epx?context=21B87D61C0F646A22B2A6DB254A010CA8C9C141B7529F029910FE6FF9EEEC5A701BF20EED61AC07159D98BAA068EBE1B8C5C7665EA2226374E942CF1D2A49D20AB1BFDFA1E0B68EC41E3058F04A85F105D5002CF1A11383C905D9FE5DDB951251A4B574B0BBE58309F67667A3B95877FEF85F1EF8B2C1A9F6FBA3BF5066D9534%7c01518B8BD6BF02F55A5A72E5947F2C45
Hope this helps. Thanks

Load balancing HTTP requests for an OC4J instance w/multiple JVMs

Hello everyone,
I am using OAS 10.1.3.1 and wish to load balance HTTP requests across an OC4J group of one or more OC4J instances, where each like named OC4J instance may have multiple JVMs or it may just have one JVM.
My mod_oc4j.conf file would contain the following directives :
Oc4jSelectMethod roundrobin:local
Oc4jRoutingMode Static
Oc4JMount /xyz/* xyz
In the degenerate case, I would like to have an OC4J group with a cluster size of one, and have that one OC4J instance have two or more JVMs. I would like to be able to receive a request within my web application, determine that the JVM that has been sent the request is the wrong JVM to process the request, and then call HttpServletResponse.sendRedirect("/xyz"). Then, when the browser receives the HTTP 302 response and issues the subsequent HTTP request, have that request sent to a different JVM than the previous JVM that issued the sendRedirect().
What I have seen is that the subsequent request is sent back to the same JVM that issued the sendRedirect(). I also call invalidate() against the HttpSession prior to calling sendRedirect(), but that does not seem to affect the behavior that I see.
In the full blown case, I would have an OC4J group with a cluster size > 1, and each of those OC4J instances would have at least one JVM. In that case, I wish the sendRedirect() call to allow the subsequent request to be sent to any one of the OC4J instances in the group, and any one of those JVMs within all of those OC4J instances.
Can anyone verify that my mod_oc4j mount directive is appropriate given the select method and routing mode? What else might I need to do to have a chance to have a different JVM respond to the request that results from a sendRedirect()?
Thank you,
Doug

I should clarify that in the full blown environment, the OC4J instances that form a group will each be housed within a separate OAS instance that resides on its own machine.
So ideally, a request could be inbound to say OAS instance 1 on machine A, OC4J instance AA, JVM 2, and I need to force a redirect so that the request can actually be serviced by OAS instance 3 on machine C, OC4J instance AA, JVM 1, and I need to be able to call sendRedirect() against an HttpServletResponse from within a JVM until the subsequent request from the browser, Internet Explorer in my case, is serviced by that JVM.
Thanks,
Doug

Using ACE to load balance HTTP/S traffic between client & proxy server using tcp 8080

Folks,
I have a scenario where ACE is in load balancing connections to a bunch of Websense servers in a one-armed topology. ACE presents a single VIP to web browser clients and each client's browser proxy configuration is populated with the VIP DNS name. Traffic then gets load balanced between the Websense servers. The problem arises due to Websense requiring the 'X-Forwarded-For' HTTP header in order to obtain the source IP of the client.
ACE inserts this header into the standard HTTP 'proxied' traffic but doing this for HTTPS traffic has required the configuration of the ACE SSL proxy client server.
So the problem I have is this:
How to configure ACE to load balance both HTTP & HTTPS applications using a single VIP and tcp port number ie tcp 8080
The ACE hardware being used is ACE20-MOD-K9 - MODULE
I have attempted to use a L7 class map to match all ciphers and attach this to a L7 Policy-Map but the documentation highlights the fact the 'match cipher' configuration is only available on the ACE appliance.
I believe I am on the correct track. The HTTPS traffic must be identified and used to match against PolicyA and HTTP traffic matched against PolicyB
I'm looking for ideas! I'm hopeful someone must have solved this problem previously!!
Regards,
Simon

Hi Simon,
The classification has to work on different ports. Whether client types http or https doesn't matter to client. His request will reach VIP which will classify the traffic based on port, protocol first and then it can look into further detail to send the traffic to appropriate serverfarm.
You can class-map match-any xxxxx
2 match virtual-address x.x.x.x tcp any
and then you configure further classification on the basis of L7 like url, header etc.
But again, you will still need SSL termination on ACE.
Regards,
Kanwal
Note: Please mark answers if they are helpful.

CSS11503 load balancing virtual server IP's

Hi CSS experts,
We have a Cisco Content Services Switch 11503 Load Balancer which seems to require Real Server NICs to be plugged in. When I plug a cable from our Cisco 3560 switch into the Cisco Load Balancer, it can't see the 2 web server IP's that I'm trying to load balance for HTTP/HTTPS. The virtual IP does not display the webpage of either web servers.
On the otherhand, when I use two physically separate 1U web servers and physically plug 2 cables (1 for each server) into the CSS 8 port switch, the virtual IP is able to redirect the traffic to both web servers.
How do I configure the CSS to load balance and actually see 2 IP's on the network which isn't plugged in physically per server into the CSS 8 port switch.
Internet->CSS->1 cable plugged into Cisco switch which host 2 web servers.
Thanks,
Mike
Configuration:
circuit VLAN1
ip address 192.168.1.10 255.255.255.0
service Websrv1
ip address 192.168.1.104
protocol tcp
port 80
keepalive type http non-persistent
active
service Websrv1SSL
ip address 192.168.1.104
protocol tcp
port 443
keepalive type ssl
active
service Websrv2
ip address 192.168.1.101
protocol tcp
port 80
keepalive type http non-persistent
active
service Websrv2SSL
ip address 192.168.1.101
protocol tcp
port 443
keepalive type ssl
active
owner Web
content NG
add service Websrv1
add service Websrv2
vip address 192.168.1.7
port 80
protocol tcp
advanced-balance arrowpoint-cookie
url "/*"
active
content NGSSL
add service Websrv1SSL
add service Websrv2SSL
vip address 192.168.1.7
port 443
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 60
active

I checked the connectivity to the servers form the CSS and it was good. I was able to ping, and the connection status in sh service summary incremented by 1 each time I tried to connect. From the server, I was able to ping back to the IP of the CSS and the VIP address as well. I have tried using only 1 server for 1 VIP. I have tried changing the default gateway on the server to the IP of the CSS and the VIP IP as well. It still doesn't seem to help. Anymore suggestions for me to try?
Thanks
Mike

Load Balancing Reports Server

I am supporting an app server for a Forms & Reports application that uses run_report_object to run reports on a Reports Server. This is on 10gR2 (10.1.2.0.2) on Solaris & Linux.
Currently running multiple standalone Reports Servers on a single server (for 3 different projects). Need to prevent one project from affecting another as much as possible (yes, I know they are on the same box....).
I have a requirement to ensure that a hanging Reports Server doesn't prevent other jobs from running. I see that Reports Server clustering is no longer an option. The Reports documentation about how to implement HA basically say just read the AS docs and figure it out. The problem is that using the AS J2EE HA means that you'd HAVE to use the Reports Servlet. Additionally, I don't see how the reports servlet could be called so that more than one Reports server would be used.
I keep hearing about an impending doc about implementing HA on Reports. When is it coming?
Future environments will be multiple AS installs on separate boxes accessing a RAC DB.
So, what's the scoop? How can I implement this?
So, here are my questions:
1. (Two Servers) I believe I could do this on two servers if I had the same Reports Server name on each. If so, could I have two OC4J containers on each server both with the same mount point for the rwservlet application? What else would I need to do to tell OHS to load balance between both since they have the same name.
2. (Two Servers) If 1 above is okay, would it be possible to have two OC4J containers point to two different standalone Reports Servers?
3. (One Server) Can I start up multiple Reports Servers on same box with the same name (I'm pretty sure this is no :-) )
4. (One Server) Like 2 above except on a single server. Two independent OC4J containers accessing two different servlets. Each has a default Reports Server setup. URL would look the same from each.
I'm kind of graping for straws here on how to move ahead. I'm surprised the Reports Server clustering was taken away, but I suspect it is because the underlying Visibroker architecture was changed and there weren't the resources required to redo this. I'm not sure that is a good thing.
Any help would be appreciated.
:-) Steve

Say you have two servers where you configured Reports, i.e. either in full Enterprise Edition or in AS10g Forms&Reports standalone.
For example:
ServerA.oracle.com with port 7777
ServerB.oracle.com with port 7777
Without using a load balancer you would call a Report with:
http://ServerA.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
http://ServerB.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
Now you put a load balancer in front of them and assign it the virtual name:
reports.oracle.comNow you can call Reports with this URL:
http://reports.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
To make it more interesting you create a specific Reports Server on ServerA called repserver_a and on ServerB: repserver_b. You add them into Enterprise Manager with:
$OH/bin/addNewServerTarget.sh repserver_a (on ServerA and with repserver_b on ServerB). You might need to reload opmnctl and emctl with:
opmnctl reload
emctl reloadIn $OH/reports/conf you add this line at the end (use server=repserver_b on ServerB) :
reporting: userid=scott/tiger@orcl destype=cache desformat=htmlcss server=repserver_a %* You'll call your Reports with this URL:
http://reports.oracle.com:7777/reports/rwservlet?reporting&report=test.rdf
Good luck!
Martin

Load Balance https based on url

I am trying to configure ACE 4710 to load balance base on the URL, If it matches the specific URL ( /456/ ), the traffic will be sent to server farm 456 else the traffic will be sent to server farm 123.
I attached an image of the topology.
Ace Config:
rserver host SRV01_123
ip address 192.168.1.101
inservice
rserver host SRV02_123
ip address 192.168.1.102
inservice
rserver host SRV01_456
ip address 192.168.1.111
inservice
serverfarm host farm_123
rserver SRV01_123
    inservice
rserver SRV02_123
    inservice
serverfarm host farm_456
rserver SRV01_456
    inservice
class-map match-all VIP_Application
2 match virtual-address 192.168.1.10 tcp eq https
class-map type http loadbalance match-all L7_server_456
2 match http url /456/
policy-map type loadbalance http first-match LB_Application
class L7_server_456
    serverfarm farm_456
class class-default
    serverfarm farm_123
policy-map multi-match ServerGroup1_PM
class VIP_Application
    loadbalance vip inservice
    loadbalance policy LB_Application
    loadbalance vip icmp-reply
interface vlan 70
bridge-group 1
no shutdown
interface vlan 700
bridge-group 1
service-policy input ServerGroup1_PM
no shutdown
Thanks

Hi John,
If you want to do the offload in the ACE also called SSL termination, it is a two step process:
1- You need to upload your certificate and key to the ACE using FTP or one of the available methods.
2- Create the the SSL proxy service where you add these two files and finally add this service under the policy-multimatch for the VIP in question.
You also need to decide whether you want to keep your server listening in the encrypted port (that would be a two way encryption process called End-to-End SSL) or you can change the port to 80 and leave all the decyption process to the ACE (this would be transparent to the client, the site will show up as HTTPS all the time).
Here you can take a look at the SSL termination process (using clear text port in the backend servers).
Oficial Configuration Example
http://www.cisco.com/en/US/partner/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA4_1_0/configuration/ssl/guide/terminat.html
Cisco Wiki Example
http://docwiki.cisco.com/wiki/SSL_Termination_on_the_Cisco_Application_Control_Engine_Without_an_Existing_Chained_Certificate_and_Key_in_Routed_Mode_Configuration_Example
HTH
Pablo

Load Balance HTTPS servers with redirection

Hello,
I have been tasked with ACE configuration at work as the prior go-to guy for load balancing is no longer available. Trouble is, I have little idea what I’m doing when it comes to the ACE. So, forgive me if the question I have is super basic. After doing some research I put together a LB config, but its not working.
I was trying to load balance 10 servers, split into groups of 2 using 5 VIPS (1 VIP for each group of 2 servers). The servers serve an ssl web app.
Below is my configuration. What am I doing wrong? Does the config have any glaring errors? I've been staring at this thing on and off for a week and searching these forums trying to figure it out.
Any help provided will greatly appreciated.
probe tcp probe_443
port 443
interval 30
passdetect interval 5
probe https probe_https_test
interval 30
passdetect interval 5
ssl version all
request method get url /test.html
expect status 200 200
rserver host QA-1.1
ip address 10.200.162.126
inservice
rserver host QA-1.2
ip address 10.200.162.127
inservice
rserver redirect QA-group_1_redirect_rserver
webhost-redirection https://10.37.5.73/ 302
inservice
rserver host QA-2.1
ip address 10.200.162.22
inservice
rserver host QA-2.2
ip address 10.200.162.240
inservice
rserver redirect QA-group_2_redirect_rserver
webhost-redirection https://10.37.5.74/ 302
inservice
rserver host QA-3.1
ip address 10.200.162.181
inservice
rserver host QA-3.2
ip address 10.200.162.50
inservice
rserver redirect QA-group_3_redirect_rserver
webhost-redirection https://10.37.5.75/ 302
inservice
rserver host QA-4.1
ip address 10.200.162.23
inservice
rserver host QA-4.2
ip address 10.200.162.241
inservice
rserver redirect QA-group_4_redirect_rserver
webhost-redirection https://10.37.5.76/ 302
inservice
rserver host QA-5.1
ip address 10.200.162.182
inservice
rserver host QA-5.2
ip address 10.200.162.51
inservice
rserver redirect QA-group_5_redirect_rserver
webhost-redirection https://10.37.5.77/ 302
inservice
serverfarm host SF_QA-group_1_HTTPS
failaction reassign
predictor leastconns
probe probe_443
probe probe_https_test
rserver QA-1.1 443
inservice
rserver QA-1. 2 443
inservice
serverfarm host SF_QA-group_2_HTTPS
failaction reassign
predictor leastconns
probe probe_443
probe probe_https_test
rserver QA-2.1 443
inservice
rserver QA-2. 2 443
inservice
serverfarm host SF_QA-group_3_HTTPS
failaction reassign
predictor leastconns
probe probe_443
probe probe_https_test
rserver QA-3.1 443
inservice
rserver QA-3. 2 443
inservice
serverfarm host SF_QA-group_4_HTTPS
failaction reassign
predictor leastconns
probe probe_443
probe probe_https_test
rserver QA-4.1 443
inservice
rserver QA-4. 2 443
inservice
serverfarm host SF_QA-group_5_HTTPS
failaction reassign
predictor leastconns
probe probe_443
probe probe_https_test
rserver QA-5.1 443
inservice
rserver QA-5. 2 443
inservice
serverfarm redirect SF_ QA-group_1_REDIRECT
rserver QA-group_1_redirect_rserver
inservice
serverfarm redirect SF_ QA-group_2_REDIRECT
rserver QA-group_2_redirect_rserver
inservice
serverfarm redirect SF_ QA-group_3_REDIRECT
rserver QA-group_3_redirect_rserver
inservice
serverfarm redirect SF_ QA-group_4_REDIRECT
rserver QA-group_4_redirect_rserver
inservice
serverfarm redirect SF_ QA-group_5_REDIRECT
rserver QA-group_5_redirect_rserver
inservice
sticky ip-netmask 255.255.255.255 address source SRC_ QA-group_1_STICKY
serverfarm SF_ QA-group_1_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_ QA-group_2_STICKY
serverfarm SF_ QA-group_2_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_ QA-group_3_STICKY
serverfarm SF_ QA-group_3_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_ QA-group_4_STICKY
serverfarm SF_ QA-group_4_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_ QA-group_5_STICKY
serverfarm SF_ QA-group_5_HTTPS
timeout 30
replicate sticky
class-map match-all QA-group_1_HTTP
3 match virtual-address 10.37.5.73 tcp eq www
class-map match-all QA-group_1_HTTPS
3 match virtual-address 10.37.5.73 tcp eq https
class-map match-all QA-group_2_HTTP
3 match virtual-address 10.37.5.74 tcp eq www
class-map match-all QA-group_2_HTTPS
3 match virtual-address 10.37.5.74 tcp eq https
class-map match-all QA-group_3_HTTP
3 match virtual-address 10.37.5.75 tcp eq www
class-map match-all QA-group_3_HTTPS
3 match virtual-address 10.37.5.75 tcp eq https
class-map match-all QA-group_4_HTTP
3 match virtual-address 10.37.5.76 tcp eq www
class-map match-all QA-group_4_HTTPS
3 match virtual-address 10.37.5.76 tcp eq https
class-map match-all QA-group_5_HTTPS
3 match virtual-address 10.37.5.77 tcp eq www
class-map match-all QA-group_5_HTTPS
3 match virtual-address 10.37.5.77 tcp eq https
class-map type management match-any remote-management
2 match protocol http any
3 match protocol https any
4 match protocol icmp any
5 match protocol snmp any
6 match protocol ssh any
policy-map type management first-match remote-access
class remote-management
permit
policy-map type loadbalance first-match QA-group_1_REDIRECT
class class-default
serverfarm SF_ QA-group_1_REDIRECT
policy-map type loadbalance first-match QA-group_2_REDIRECT
class class-default
serverfarm SF_ QA-group_2_REDIRECT
policy-map type loadbalance first-match QA-group_3_REDIRECT
class class-default
serverfarm SF_ QA-group_3_REDIRECT
policy-map type loadbalance first-match QA-group_4_REDIRECT
class class-default
serverfarm SF_ QA-group_4_REDIRECT
policy-map type loadbalance first-match QA-group_5_REDIRECT
class class-default
serverfarm SF_ QA-group_5_REDIRECT
policy-map multi-match SERVICE_VIPS
class QA-group_1_HTTPS
    loadbalance vip inservice
    loadbalance policy HTTPS_ QA-group_1_HTTPS _L7_BALANCED
    loadbalance vip icmp-reply
    nat dynamic 1 vlan 25
class QA-group_1_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_1_REDIRECT
class QA-group_2_HTTPS
    loadbalance vip inservice
    loadbalance policy HTTPS_ QA-group_2_HTTPS _L7_BALANCED
    loadbalance vip icmp-reply
    nat dynamic 1 vlan 25
class QA-group_2_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_2_REDIRECT
class QA-group_3_HTTPS
    loadbalance vip inservice
    loadbalance policy HTTPS_ QA-group_3_HTTPS _L7_BALANCED
    loadbalance vip icmp-reply
    nat dynamic 1 vlan 25
class QA-group_3_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_3_REDIRECT
class QA-group_4_HTTPS
    loadbalance vip inservice
    loadbalance policy HTTPS_ QA-group_4_HTTPS _L7_BALANCED
    loadbalance vip icmp-reply
    nat dynamic 1 vlan 25
class QA-group_4_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_4_REDIRECT
class QA-group_5_HTTPS
    loadbalance vip inservice
    loadbalance policy HTTPS_ QA-group_4_HTTPS _L7_BALANCED
    loadbalance vip icmp-reply
    nat dynamic 1 vlan 25
class QA-group_5_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_4_REDIRECT
interface vlan 25
ip address 10.37.5.72 255.255.255.0
    access-group input everyone
service-policy input remote-access
service-policy input SERVICE_VIPS
no shutdown
ip route 0.0.0.0 0.0.0.0 10.37.5.1

Fnu,
Thank you so much for your reply.
At this point I can get to the real server IP's via ping and https in a browser from my PC. I can also ping the gateway and all the real server IP's from the ACE context i'm working on. However, the VIPS are not working. When I attempt to use one of the VIPS in the browser, the request times out. When I issue the command ":show service-policy" I see a hit count (which increments every time I try and reach the VIP via the browser) but the dropped counter is equal to the hit counter. I will paste the running config from the context I’m working in along with the output from the show service-policy command.
Any suggestions on how I can get this working would be greatly appreciated.
csc# show run
Generating configuration....
access-list Servers line 3 extended permit tcp any any eq https
access-list Servers line 5 extended permit tcp any any eq www
access-list everyone line 1 extended permit ip any any
access-list everyone line 2 extended permit icmp any any
probe tcp probe_443
port 443
interval 30
passdetect interval 5
rserver host QA-1.1
ip address 10.37.5.111
inservice
rserver host QA-1.2
ip address 10.37.5.88
inservice
rserver host QA-2.1
ip address 10.37.5.84
inservice
rserver host QA-2.2
ip address 10.37.5.89
inservice
rserver host QA-3.1
ip address 10.37.5.85
inservice
rserver host QA-3.2
ip address 10.37.5.90
inservice
rserver host QA-4.1
ip address 10.37.5.86
inservice
rserver host QA-4.2
ip address 10.37.5.81
inservice
rserver host QA-5.1
ip address 10.37.5.87
inservice
rserver host QA-5.2
ip address 10.37.5.92
inservice
rserver redirect QA-group_1_redirect_rserver
webhost-redirection https://10.37.5.93/ 302
inservice
rserver redirect QA-group_2_redirect_rserver
webhost-redirection https://10.37.5.94/ 302
inservice
rserver redirect QA-group_3_redirect_rserver
webhost-redirection https://10.37.5.95/ 302
inservice
rserver redirect QA-group_4_redirect_rserver
webhost-redirection https://10.37.5.96/ 302
inservice
rserver redirect QA-group_5_redirect_rserver
webhost-redirection https://10.37.5.97/ 302
inservice
serverfarm host SF_QA-group_1_HTTPS
failaction reassign
predictor leastconns
probe probe_443
rserver QA-1.1 443
    inservice
rserver QA-1.2 443
    inservice
serverfarm redirect SF_QA-group_1_REDIRECT
rserver QA-group_1_redirect_rserver
    inservice
serverfarm host SF_QA-group_2_HTTPS
failaction reassign
predictor leastconns
probe probe_443
rserver QA-2.1 443
    inservice
rserver QA-2.2 443
    inservice
serverfarm redirect SF_QA-group_2_REDIRECT
rserver QA-group_2_redirect_rserver
    inservice
serverfarm host SF_QA-group_3_HTTPS
failaction reassign
predictor leastconns
probe probe_443
rserver QA-3.1 443
    inservice
rserver QA-3.2 443
    inservice
serverfarm redirect SF_QA-group_3_REDIRECT
rserver QA-group_3_redirect_rserver
    inservice
serverfarm host SF_QA-group_4_HTTPS
failaction reassign
predictor leastconns
probe probe_443
rserver QA-4.1 443
    inservice
rserver QA-4.2 443
    inservice
serverfarm redirect SF_QA-group_4_REDIRECT
rserver QA-group_4_redirect_rserver
    inservice
serverfarm host SF_QA-group_5_HTTPS
failaction reassign
predictor leastconns
probe probe_443
rserver QA-5.1 443
    inservice
rserver QA-5.2 443
    inservice
serverfarm redirect SF_QA-group_5_REDIRECT
rserver QA-group_5_redirect_rserver
    inservice
serverfarm host SF_QA-group_HTTPS
serverfarm host SF_QA-group__HTTPS
sticky ip-netmask 255.255.255.255 address source SRC_QA-group_1_STICKY
serverfarm SF_QA-group_1_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_QA-group_2_STICKY
serverfarm SF_QA-group_2_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_QA-group_3_STICKY
serverfarm SF_QA-group_3_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_QA-group_4_STICKY
serverfarm SF_QA-group_4_HTTPS
timeout 30
replicate sticky
sticky ip-netmask 255.255.255.255 address source SRC_QA-group_5_STICKY
serverfarm SF_QA-group_5_HTTPS
timeout 30
replicate sticky
class-map match-all QA-group_1_HTTP
3 match virtual-address 10.37.5.93 tcp eq www
class-map match-all QA-group_1_HTTPS
3 match virtual-address 10.37.5.93 tcp eq https
class-map match-all QA-group_2_HTTP
3 match virtual-address 10.37.5.94 tcp eq www
class-map match-all QA-group_2_HTTPS
3 match virtual-address 10.37.5.94 tcp eq https
class-map match-all QA-group_3_HTTP
3 match virtual-address 10.37.5.95 tcp eq www
class-map match-all QA-group_3_HTTPS
3 match virtual-address 10.37.5.95 tcp eq https
class-map match-all QA-group_4_HTTP
3 match virtual-address 10.37.5.96 tcp eq www
class-map match-all QA-group_4_HTTPS
3 match virtual-address 10.37.5.76 tcp eq https
class-map match-all QA-group_5_HTTP
3 match virtual-address 10.37.5.97 tcp eq www
class-map match-all QA-group_5_HTTPS
3 match virtual-address 10.37.5.97 tcp eq https
class-map type management match-any remote-management
2 match protocol http any
3 match protocol https any
4 match protocol icmp any
5 match protocol snmp any
6 match protocol ssh any
policy-map type management first-match remote-access
class remote-management
    permit
policy-map type loadbalance first-match QA-group_1_REDIRECT
class class-default
policy-map type loadbalance first-match QA-group_2_REDIRECT
class class-default
    serverfarm SF_QA-group_2_REDIRECT
policy-map type loadbalance first-match QA-group_3_REDIRECT
class class-default
    serverfarm SF_QA-group_3_REDIRECT
policy-map type loadbalance first-match QA-group_4_REDIRECT
class class-default
    serverfarm SF_QA-group_4_REDIRECT
policy-map type loadbalance first-match QA-group_5_REDIRECT
class class-default
    serverfarm SF_QA-group_5_REDIRECT
policy-map multi-match SERVICE_VIPS
class QA-group_1_HTTPS
    loadbalance vip inservice
    loadbalance policy QA-group_1_REDIRECT
    loadbalance vip icmp-reply
class QA-group_1_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_1_REDIRECT
class QA-group_2_HTTPS
    loadbalance vip inservice
    loadbalance policy QA-group_2_REDIRECT
    loadbalance vip icmp-reply
class QA-group_2_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_2_REDIRECT
class QA-group_3_HTTPS
    loadbalance vip inservice
    loadbalance policy QA-group_3_REDIRECT
    loadbalance vip icmp-reply
class QA-group_3_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_3_REDIRECT
class QA-group_4_HTTPS
    loadbalance vip inservice
    loadbalance policy QA-group_4_REDIRECT
    loadbalance vip icmp-reply
class QA-group_4_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_4_REDIRECT
class QA-group_5_HTTPS
    loadbalance vip inservice
    loadbalance policy QA-group_5_REDIRECT
    loadbalance vip icmp-reply
class QA-group_5_HTTP
    loadbalance vip inservice
    loadbalance policy QA-group_5_REDIRECT
interface vlan 25
ip address 10.37.5.98 255.255.255.0
access-group input everyone
service-policy input remote-access
service-policy input SERVICE_VIPS
no shutdown
ip route 0.0.0.0 0.0.0.0 10.37.5.1
csc# show service-policy SERVICE_VIPS
Status     : ACTIVE
Interface: vlan 25
service-policy: SERVICE_VIPS
    class: QA-group_1_HTTPS
      loadbalance:
        L7 loadbalance policy: QA-group_1_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : ENABLED
        VIP state: OUTOFSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: DISABLED
        curr conns       : 0         , hit count        : 122
        dropped conns    : 122
        conns per second    : 0
        client pkt count : 122       , client byte count: 6164
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_1_HTTP
      loadbalance:
        L7 loadbalance policy: QA-group_1_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : DISABLED
        VIP state: OUTOFSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: DISABLED
        curr conns       : 0         , hit count        : 58
        dropped conns    : 58
        conns per second    : 0
        client pkt count : 58        , client byte count: 3628
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_2_HTTPS
      loadbalance:
        L7 loadbalance policy: QA-group_2_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : ENABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 13
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 74        , client byte count: 7648
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_2_HTTP
      loadbalance:
        L7 loadbalance policy: QA-group_2_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : DISABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 3
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 12        , client byte count: 1398
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_3_HTTPS
      loadbalance:
        L7 loadbalance policy: QA-group_3_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : ENABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 34
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 201       , client byte count: 23495
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_3_HTTP
      loadbalance:
        L7 loadbalance policy: QA-group_3_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : DISABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 5
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 20        , client byte count: 1907
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_4_HTTPS
      loadbalance:
        L7 loadbalance policy: QA-group_4_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : ENABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 0
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 0         , client byte count: 0
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_4_HTTP
      loadbalance:
        L7 loadbalance policy: QA-group_4_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : DISABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 2
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 8         , client byte count: 697
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_5_HTTPS
      loadbalance:
        L7 loadbalance policy: QA-group_5_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : ENABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 0
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 0         , client byte count: 0
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0
    class: QA-group_5_HTTP
      loadbalance:
        L7 loadbalance policy: QA-group_5_REDIRECT
        VIP Route Metric     : 77
        VIP Route Advertise : DISABLED
        VIP ICMP Reply       : DISABLED
        VIP State: INSERVICE
        VIP DWS state: DWS_DISABLED
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 0
        dropped conns    : 0
        conns per second    : 0
        client pkt count : 0         , client byte count: 0
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
      compression:
        bytes_in : 0                          bytes_out : 0
        Compression ratio : 0.00%
                Gzip: 0               Deflate: 0
      compression errors:
        User-Agent : 0               Accept-Encoding    : 0
        Content size: 0               Content type       : 0
        Not HTTP 1.1: 0               HTTP response error: 0
        Others      : 0

Network Load balancing for Server 2003 and Server 2012

Our environment currently has 2 web servers running Windows Server 2003 with Network Load Balancing. We are looking to update the servers to Windows Server 2012. Is it possible to add Windows Server 2012 into the Windows Server 2003 Network Load
balancing cluster? This way we could bring up 2 new servers add them into the network load balancing and then take out the 2003 servers without disrupting our production.
Any thoughts or suggestions on how to make this work properly?

Hi,
You can upgrade an existing Network Load Balancing (NLB) cluster to Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 by taking the entire cluster offline
and upgrading all the hosts, or you can leave the NLB cluster online and perform a rolling upgrade. A rolling upgrade entails taking individual cluster hosts offline one at a time, upgrading each host, and returning the host to the cluster. You continue upgrading
individual cluster hosts until the entire cluster is upgraded. A rolling upgrade allows the cluster to continue running during the upgrade.
The related KB:
Upgrading an Existing Network Load Balancing Cluster
http://technet.microsoft.com/en-us/library/cc731691(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Help: AM Agent working with load balancing AM Server

Hi,
We are trying to set up the policy agent to work with two AM Servers behind a load balancer.
The agent deployment document said that in the AMAgent.properties we must set
com.sun.am.loadBalancer_enable=true
According to the AM deployment guide(http://docs.sun.com/source/817-7644/appE_loadbalancerconfig.html),
we also set in the AMConfig.properties something like
com.iplanet.am.lbcookie.name=server1
com.iplanet.am.lbcookie.value=server1
The loading balancing just does not work. Can anyone explain how AM agent works under such an deployment
environment? Some people say the agent can find the real server using the naming service, but the not
much explanation can be found.
More info on our two machines:
The two AM servers are named server1.domain and server2.domain. The virtual LB name is server.domain.
The two AM servers were installed using the host name server.domain. We added the servers' real name
in the AM's fqdnMap. At the agent config file, the name service is pointing to the LB.
Really appreciated any advices.
Regards,
Henry

Thanks for your reply.
We figured it out lately thanks to help from Bernhard.
1) use each machine's name to install the AM servers using the same LDAP server.
2) In AmAgent.propeties, set com.sun.am.loadBalancer_enable=true
3) In AM server platform, add in all machine's names
4) In Organization alias, add in two machines' name
5) In fqdnMap, add in load balancer's name
6) In LB, set cookie stickiness based on cookie JSESSIONID

Timesheet Update Issue-- After Load Balancing of server

Hi Recently we have applied Load balancing to our production and development server, but we are getting error while trying to save and submit timesheet for resource . The jobs are failing and blocking the Queue
This is the error message
General
Queue:
GeneralQueueJobFailed (26000) - TimesheetUpdate.UpdateTimesheetMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='187a8888-6c29-4c92-a39e-4b9999096259' JobUID='6c18188f-c49f-4e10-9f18-00e393ac4820' ComputerName='MUCPMOF1'
GroupType='TimesheetUpdate' MessageType='UpdateTimesheetMessage' MessageId='1' Stage=''. For more details, check the ULS logs on machine " XXXXXXXXXX " for entries with JobUID
6c18188f-c49f-4e10-9f18-00e393ac4820.
This is due to Load balancing , as when we undo the load balancing there are no issue with timesheet updates .anyone has any idea ????Regards

Hi Priyanshu,
Did you solved the load balancing issue ? We are interested by your answer, we are on the verge to implement Project Server (2013) on a load balancing SharePoint Farm, and we wonder if it is supported (we found no document to prove it, esp for reporting
or timesheet). We have heard rumours that says it does not work on reporting.
Regards
www.e-labor.net
Didier Maignan | http://didiermaignan.unblog.fr

Client side load balancing and server side load balancing

Hello Team,
I need to know how to set up client and server side load balancing in oracle rac. What all things to be implemented like creating a service, tnsnames.ora settings etc.
And also if i used SCAN ip instead of VIP. how the settings will change.
Regards,

Hi,
please find here an Whitepaper with the information
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11gr2-client-failover-173305.pdf
kind regards

Network load balancing SQL Server 2012

Hi all,
Out of pure curiosity, would the following scenario to load balance work:
* Create an NLB of 2 nodes
* On each node, install sql server, in my case 2012 std
* Create a merge replication which manages identity columns between the 2 servers. One node is the publisher the other one the subscriber
If I were to implement this, what would be the risks ?
Thanks
Olivier

SQL Server does not support load balancing.
Yes you can do what you describe. You need to use "sticky sessions" to make sure users always get the same server, which kind of defeats the purpose of load balancing.
I would suggest looking into an AlwaysOn availably group cluster instead. Not the same thing, but built in and you can redirect read only users to use a replica.
https://msdn.microsoft.com/en-us/library/ff877884.aspx

Load balancing Application Server

Hi
I am new to peoplesoft dba
It would be great if somebody could point me to the steps required for setting up loadbalancing for Peoplesoft application server (not web server)
In particular i wanted to know where to look for information on 'directing certain loads' to particular server.
Thanks a lot
Cyril

Are you talking about load balancing from Webserver to multiple appserver in 4tier mode ? See here the configuration.properties conf :
http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tsvt/book.htm?File=tsvt/htm/tsvt14.htm#H4003
Or are you talking about load balancing for 3tier mode ? See TUXEDO Connect String* in the profile (configuration manager) :
http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tsvt/book.htm?File=tsvt/htm/tsvt11.htm#H4032
Nicolas.

Load balancing Http/https requests of SRM

Hi all,
we are on SRM 5.0 with CI and one DI , we don't have any web dispatcher for routing http/https requests.
Currently CI is flooded with all requests and DI is sitting idle no routing is going on.... and users are experiencing Time out expceptions ...
we have configured SMLG and services in SICF have group assigned...
we have BI portal where users log in and access all SRM web applications like shopping cart, invoice....
Please suggest how to handle the load balancing of http/https requests with message server...
Thanks,
Subhash.G

Thanks

Load balancing http server

Similar Messages

Maybe you are looking for