Load-balancing TNS redirect message to include IP instead hostname?

Is it possible to configure somehow (via Oracle or OS settings) that on a TNS redirect message (as resulting from server-side load balancing), the embedded connection string contains the target instance address as an IP address instead of a hostname? Thanks!

Ron wrote:
Is it possible to configure somehow (via Oracle or OS settings) that on a TNS redirect message (as resulting from server-side load balancing), the embedded connection string contains the target instance address as an IP address instead of a hostname? Thanks!My guess is that this is dependent on how the Listener was instructed to listen on a port. I posted about in message {message:id=9120517} - how specifying an IP address as a listener end point changes the behaviour when specifying a hostname as end point instead.
If instructed to use a specific IP address as listening end point, then it cannot really pass a hostname to the client as that hostname may resolve to another IP used by the server.
It should be relatively simple to set up a test case for this - what Oracle (4 digit) version are you using?

Similar Messages

Load Balancing Error Message

We have two ASA 5550's, ver. 8.0.4. We just recently set them up for Load Balancing. Every time the user logins to Cisco VPN client (5.0.03.0560), we got two email notifications for the below message. We got the error messages every time every user logins to the Cisco VPN client
163>%ASA-3-713128: Connection attempt to VCPIP redirected to VCA peer 192.168.110.18 via load balancing
163>%ASA-3-713902: Group = office, IP = XX.XXX.XXX.XXX, Removing peer from peer table failed, no match!
The user was able to access the internal resources. The two ASA's have the exact configurations. Do you have any suggestions how to fix the problem?
Thanks.
Debra

Error Message - %PIX|ASA-3-713128: Connection attempt to VCPIP redirected to VCA peer IP_address via load balancing
Explanation - This message appears when a connection attempt has been made to the VCPIP and has been redirected to a less loaded peer using load balancing.
Recommended Action - None required.
Error Message - %PIX|ASA-3-713902 descriptive_event_string
Explanation - This system log message could have several possible text strings describing an error. This may be the result of a configuration error either on the headend or remote access client.
Recommended Action - It might be necessary to troubleshoot the configuration to determine the cause of the error. Check the ISAKMP and crypto map configuration on both peers.

Oracle Portal Load Balancing question

Our customer wishes to have multiple Oracle Application Servers running Oracle Portal, with load balancing. They would like to have Web Cache collocated with one of these Portal servers, operating as a load balancer for the Portal servers (including the one collocated with Web Cache). Our understanding is that this is not supported, since Web Cache must use the same port number as the destination server it is load balancing, and this is a problem with collocation. The alternative of using mod_oc4j load balancing by OHS is we understand not supported for Portal. The customer does not wish to use external, hardware load balancers, or operating system load balancing. We understand that the solution is to use Web Cache on a dedicated separate server, to load balance the Portal servers. Can you please confirm that, or is collocation possible to avoid the cost of the dedicated Web Cache server.
thanks,
Message was edited by:
user582458

<<
We understand that the solution is to use Web Cache on a dedicated separate server, to load balance the Portal servers. Can you please confirm that, or is collocation possible to avoid the cost of the dedicated Web Cache server
>>
You are right .. if the client does not want use load balancer you have no other choice.

FRM-92102 when accessing a form using a Load Balancer

Greetings.
We have two oracle application servers version 10.1.2.0.2 on windows 2003 running forms and reports. When just one a server is running everithing works fine, but when I start the second server the clients receive the message "FRM-92102 : A network error has occurred.The Forms Client has attempted to re-establish its connection to the Server 5 times without success.Please check the network connection and try again later" when the first form is called. In our coniguration the F5 Load Balancer is redirecting requests to the Apache ports in both Oas Machines, we are not using the webcache port. I read the note "FRM-92102 When Using A Software Load Balancer With Forms [ID 465583.1]" but this note applies when webcache is used. Our LBR is set using "insert cookie" persitent mechanism.
I have the following questions:
What configuration is needed in OAS files in order to use a LBR and avoid the FRM-92102 error?
How can I debug or trace FRM-92102 issues?
Thanks!
Ramiro Ortiz.

FRM-92102 is the result of the client not getting a response from the server (mid tier). This generally means only one of a couple of things:
1. The mid tier which parented the Forms session is not responding. This could be because it is overloaded, the web server (OHS or WebCache) is failing, or something else is preventing the client from getting a response.
2. Client requests are being routed to the wrong mid-tier server. This is usually the result of improper load balancer configuration or an LB failure. However, generally in this case FRM-92101 would result. If you are using an unpatch 10.1.2 installation, as I believe you are (10.1.2.0) then seeing either error may be possible.
Regarding the note that discusses using Oracle WebCache for load balancing, regardless of whether you are using an Oracle product or hardware or whatever for loadbalancing, the same concept will apply. The load balancer must have session binding enabled. Understanding whether or not this is the problem should be fairly easy to determine. Simply shutdown one server. If everything works correctly, restart the second server. If the problem now occurs, you can likely assume you have a session binding issue and should likely refer to the load balancer's documentation or their Support group.
Also, important to understand is that if the load balancer is designed to alter the header information in any way, the likelihood of failing Forms sessions is high. Forms is expecting very specific information in the header exchange. Some intermediate servers (load balancers, ssl accelerators, firewalls, etc) have been known to intentionally or unintentionally alter the header. Again, contact the vendor.
If you are seeing that the client console is reporting 5 retry attempts, yet you have not set "networkRetries" in formsweb.cfg, this often suggests a critical tcp/ip failure. Often, but maybe not always, the result of a damaged header or other misconfiguration or failure outside of Forms.

Logon load balance in EDMS

Hi Experts,
We configured Easy document management system (EDMS). We are able to login into the system. But we have three dialogue instances and one application instance. We need to configure logon load balance in EDMS. we already configured logon load balance in our message server. Please help me which connection parameter we need to select and what is the value we have to provide in EDMS.
Please help me this is very urgent.
Regards,
Patan Thavaheer

Dear Experts,
Problem resolved.
Thanks&Regards,
Patan Thavaheer.

Data Centre Interconnection - firewall and load balancer deployment

Hi all,
I've read lots of Cisco docs/white papers on DCI - Layer 2 extension between DCs, but as yet I cannot find any decent information on how best to deploy firewalls and load balancers in such a design. I've seen refs to FHRP isolation on Nexus 7k (and possible 6k if you use DCI block) but nothing on the services elements.
The services element seems to be a complete minefield here:
- active/standby across sites, or deploy resilient pairs in each site?
- how to align optimal traffic flows inbound and ooutbound (RHI, SNAT, etc.)
- best practice suggestions ideally.
Cisco DCI docs seem to always gloss over the fact that most customers would have to deal with firewalls and load balancers here, and simply refer to 'coming soon' for that info.
If anyone has any good suggestions/links to docs explaining detailed implementation info would be much appreciate
Thanks
Phil

You might want to check out this new product called ITD.
Simple and faster solution:
ITD provides :
ASIC based multi-terabit/s L3/L4 load-balancing at line-rate
No service module or external L3/L4 load-balancer needed. Every N7k port can be used as load-balancer.
Redirect line-rate traffic to any devices, for example web cache engines, Web Accelerator Engines (WAE), video-caches, etc.
Capability to create clusters of devices, for example, Firewalls, Intrusion Prevention System (IPS), or Web Application Firewall (WAF), Hadoop cluster
IP-stickiness
Resilient (like resilient ECMP)
VIP based L4 load-balancing
NAT (available for EFT/PoC). Allows non-DSR deployments.
Weighted load-balancing
Load-balances to large number of devices/servers
ACL along with redirection and load balancing simultaneously.
Bi-directional flow-coherency. Traffic from A-->B and B-->A goes to same node.
Order of magnitude OPEX savings : reduction in configuration, and ease of deployment
Order of magnitude CAPEX savings : Wiring, Power, Rackspace and Cost savings
The servers/appliances don’t have to be directly connected to N7k
Monitoring the health of servers/appliances.
N + M redundancy.
Automatic failure handling of servers/appliances.
VRF support, vPC support, VDC support
Supported on both Nexus 7000 and Nexus 7700 series.
Supports both IPv4 and IPv6
N5k / N6k support : coming soon
Blog
At a glance
ITD config guide
Email Query or feedback:[email protected]

Best Load Balancing solution for NMS 4.15

What is the best load balancing solution for Messaging Server with 250 users?

What are you trying to achieve? I do not understand from your question what it is you are trying to accomplish. What component(s) of NMS are you trying to load balance?

TOMCAT SERVER CONNECTED TO LOAD BALANCER

Hi ,
scenario:
Tomcat server addedd to the load balancer for performance .
Q&A:
We have added tomcat(new server) to load balancer,now all the services are up and running,but i want to know the validation of how the new server added to the cluster will have the connections via load balancer to this server. is there any simple way where by we can go by looking at some logs, or load, or connection statistics for the Tomcat server whilst users connect.
please gurus can you help,
1.HOW TO VALIDATE THE LB IS WORKING FINE .
2.TOMCAT SERVICES VIA LB (CONNECTION)
3.OTHER VALIDATION TO BE CONSIDERED.
Regards,

SAP Business Objects really cannot verify if your load balancer is working fine, you should take that up with your load balancer manufacturer or IT folks that manage it.
When using a load balancer with business objects deployment on tomcat you should enable session persistance (this is mandatory in XIR2) and may be needed in some circumstances in XI 3.x.
A little trick I've seen customers do is to change an image file in the deployment to have a #1 or 2 or 3 or... depending on the tomcat server, this way they could tell which server the load balancer was redirecting to. To do this right click the image when accessing tomcat (to get it's location in the deployment) and simply edit with MS paint or favorite image editor (back up the original 1st just in case...)
Regards,
Tim

Use message server as load balancing instead of web dispacher for XI in HA

Hi all!
    We are currently upgrading a cluster XI installation from 3.0 to 7.0.
    The idea is:
          Now:    1 node (central instance)
                     1 node (database)
          Future: 1 node (central instance)
                     1 node (database + application instance)
     So we need some king of load balancing between the two instances.
     We already know web dispatcher and all configuration required. However we
were trying not to use it but use the abap/java message server who can also do
the redirect.
     However, once the Exchange Profile has been updated, it does not work.
     If we change "com.sap.aii.connect.repository.httpport" to "8101". Cache refresh stop working with a "Authorization Error". This is really strange because if I try the very same URL in the explorer and I enter the logon data, I have no problem.
     Do you have any experience with this? I mean, is it possible to avoid installing web dispatcher?
     Thanks and kind regards,
           Encinas.

Hi David,
the message server does only a redirect and some XI applications (JAVA and ABAP side) cannot handle the redirect URL.
Therefore in the XI environment you have to use a "real" dispatcher (keeping the session and forwarding the session, instead of redirect) - for example you can use the SAP WebDispatcher here.
Best regards,
Silvia

Flex Load Balancer Environment URL Redirect

Hi,
Our Flex application is running on a load balancer environment, where SSL is terminated. From the browser to load balancer, the connection is using https and from the load balancer to the server, it is http. What we are noticing is, when the https url is invoked on the browser, it immediately redirects the url from https to http. This breaks the connection and an error message unable to connect is shown on the browser. We traced the network traffic using the Live HTTP headers, it showed the same redirect in the url with the message HTTP/1.1 302 Moved Temporarily.
Please let me know, how i can resolve this issue. Also let me know, if you need any other information from me.
Thanks for your help.
Murugan.

I'm kind of a newbie on the netscaler. What od you mean by stick? We keep persistence by a cookie insert.
I did find out what the issue was, our E1 installation sits on port 8086, so from the netscaler we would reroute the port 80 calls from jdesso.xxx.local to the E1 server, but for some reason when the handoff came back from OID to E1 the load balancer somehow realized the app server was running from port 8086 and it mixed the whole process up (instead of keeping all traffic to and from the client on port 80). To workaround this I created a new virtual server to listen on port 8086, then I redirected the port 80 calls to new 8086 VS, and then from the 8086VS to the app server and it worked correctly.

Message load balancing in PI 7.0

Hi Experts,
We have the below requirement. Please suggest a way to make it feasible.
There would be a threshold limit for the count of messages that are processed by a communication channel.
The messages being processed by a communication channel have to be counted for a day and if the limit is crossed, the channel has to stop processing the messages for that day.
We have only File and JMS communication channels in our landscape.
This activity is being done for load balancing on the system per interface.
Please suggest if there is any possible way to achieve this.
If this is not possible, please suggest any other possible way to achieve the load balancing.
Thank you.
Regards,
Subbu

Hi Subbu,
You can try this below solution,
Maintain table in SAP PI (ABAP Stack),evry time when interface executes enter count value in table, next time exeuction read old count value and update new on in Table.
once coutn reaches max value then you can kill message in mapping level.
But this is not good desisgn..just idea thats it.
Regards,
Raj

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

HTTP Redirect with Global Load Balancing

I've seen a lot of documentation about redirects and what I am trying to do seems simple enough yet I can't get it to work. Here is a summary:
We have two CSSs in different data centers with load balancing in a roundrobin fashion.
User types www.test.com:9086/test.html
User hits one of the CSSes configured to respond to www.test.com, CSS1 and CSS2.
If CSS1 gets the request, it should redirect request to server1:9086/test.html
If CSS2 gets the request, it should redirect request to server2:9086/test.html
Here is a sample of one of the CSSes:
content vTEST
dnsbalance roundrobin
add dns www.test.com
url "/*"
protocol tcp
port 9086
vip address 192.168.3.135
add service rTEST
active
service rTEST
protocol tcp
port 9086
type redirect
keepalive type none
ip address 2.2.2.2
redirect-string "server1:9086/test.html"
active
I've seen a lot of example of using HTTP Redirects, but none of them touch on using global load balancing as we are trying to accomplish.
Now, if I type in a browser:
http://www.test.com:9086/test.html
it fails. Why? because the CSS returns back an IP of 2.2.2.2 for www.test.com, which isn't a real IP address (this is by design). If I type:
http://192.168.3.135:9086/test.html
it works because it successfully redirects to:
http://server1:9086/test.html
because it is going directly against the VIP and redirecting as it should.
So the redirect function we know is working on the CSS as expected. However, the problem is this:
When I ping www.test.com I should get back the VIP address of the content rule (192.168.3.135) and I do UNTIL I ADD THE REDIRECT TYPE to the service. Once I do that if I ping www.test.com I will get back 2.2.2.2. Somehow once the redirect is added the IP address of the service (2.2.2.2) is returned instead of the content VIP (192.168.3.135). That shouldn't happen.
I hope this makes sense and any help would be greatly appreciated!!!

I think what you want to do is explained at :
http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a0080094068.shtml
For your information, you should also look at this solution :
http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a00801dcd75.shtml
Regards,
Gilles.

Load balancing error 88: Cannot connect to message server (rc=9)

Hi,
We are facing a problem in the system object.
initially we created a system object with loadbalancing template ,and everything worked fine, but after couple of months we found a error "Load balancing error 88: Cannot connect to message server (rc=9)", so we have created a Dedicated application server object which resolved our issue.
My question is why has this problem occured, and since my client side has lot number of users and we wish to keep the system back to load balancing object.
How can i make my system object work back, what might be the causes?
Thanks
Srivastsa Kondapally

Load balancing only works if the message server is available and the logon group specified exists as well. If one of those changes, then it will break until you get the values set correctly.

WLS 5.1 JMS and Message load balancing

Would I be right in thinking that WLS 5.1 offers no out of the box component that distributes incoming messages over a series of JMS Destinations? (much like a distributed destination would do in WLS 8.1?)
          Is it BEA's recommendation then that any JMS Client sending to these JMS destinations pick's up the responsibility for carrying out load balancing?
          regards
          Barry

Would I be right in thinking that WLS 5.1 offers no          > out of the box component that distributes incoming
          > messages over a series of JMS Destinations? (much
          > like a distributed destination would do in WLS 8.1?)
          Yes.
          >
          >
          > Is it BEA's recommendation then that any JMS Client
          > sending to these JMS destinations pick's up the
          > responsibility for carrying out load balancing?
          Application dependent.
          For example, you could set up an EJB that enqueues to the local queue - where the local queue's name is inferred from the server the EJB is running on.
          Load balancing (and fail-over) would then be accomplished by invoking the EJB and depending on standard EJB features...
          >
          > regards
          > Barry

Load-balancing TNS redirect message to include IP instead hostname?

Similar Messages

Maybe you are looking for