CSM for enabling hot spare instead of load balancing

We have a server at a remote site that we want the remote clients to use. We only want them to use the central server if the remote one fails. Is there a way I can use "weight" or some other method to accomplish this. Thanks.

what device are you talking about ?
There is a solution but it is different depending of the machine you are using.
Gilles.

Similar Messages

Cisco CSM: Duplication of udp packets possible instead of load balancing?

Hi all,
Does anybody know if it's possible to use the csm (WS-X6066-SLB-APC, OS 4.3.1) to duplicate udp packets to several real servers instead of balancing them.
In our special case we want to test duplicating snmp traps to several network management systems whereas on the snmp clients only one target address (the vserver address) is configured.
Many thanks in advance,
Thorsten

Hi Thorsten,
I'm afraid this is not possible. With the CSM you can only load-balance.
Regards
Daniel

Hot to do Failover/Load balance on CORBA C++ Client

I have a corba C++ client using Bea/Tuxedo 8.0 ORB talking to stateless session beans
on Weblogic Server 6.1/sp2.
Question:
If the wls server(s) is a cluster, how do I use this feature in my C++ client to
provide the failover/load balance?
Will the rmic generate idl which is cluster-aware if the EJBs are clustered?
Any help is appreciated.
Thanks,
steve

"steve" <[email protected]> writes:
I have a corba C++ client using Bea/Tuxedo 8.0 ORB talking to stateless session beans
on Weblogic Server 6.1/sp2.
Question:
If the wls server(s) is a cluster, how do I use this feature in my C++ client to
provide the failover/load balance?Currently, although the information is available to the client it does
not use it. This will probably change in a future release of Tuxedo,
but you should talk to your sales rep for details.
For now you can get some degree of failover by catching the
COMM_FAILURE exception and re-looking up CosNaming and your bean.
Will the rmic generate idl which is cluster-aware if the EJBs are clustered?The information is provided dynamically at runtime, so its independent
of the IDL.
andy

CSM Load Balancer Help

Hey,
Just a quick question....
Does anyone know a) if it's possible and b) how to have two servers off the CSM but instead of load-balancing between them make them a failover pair i.e. if server A goes down server B will take over - done using the same VIP?? It's needed because the application on the servers can't do load-balancing yet but can work in a failover way.
I'm reading the book trying to work it out but if someone has done this before that would be great!
Thanks
Anthony

Thanks for the responses.
I'm using CSM 4.6(6) and have given what you suggested a go but have run into problems.
When I disconnect the primary server I see that go out of service but that also knocks out the VIP and it never fails over to the second server. Am I missing something? I've attached the relevant parts of the config and would be greatful for any advice.
serverfarm FARM1
nat server
nat client WEB
real 10.2.250.10
inservice
probe HTTP
serverfarm FARM2
nat server
nat client WEB
real 10.2.250.11
inservice
probe HTTP
vserver WEBTRAFFIC
virtual 10.2.250.100 tcp www
vlan 250
serverfarm FARM1 backup FARM2
persistent rebalance
inservice
I also had a go at creating that variable but it wouldn't let me...just said variable not configurable - but I'll play with that and see if I can work it out...I'm not so bothered as long as the backup part works.
Thanks guys...
Anthony

Apache HTTP proxying for load balancing only to a group of non-clustered WL servers

          Hi,
          We're running WL Server 6.1 SP 2 on Solaris 2.8.
          For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf option,
          do the WL servers you want to load balance across have to be part of a WebLogic
          cluster (if you are prepared to do without failover, as I know it would need to be
          a proper WL cluster to replicate session info for failover). Can you load balance
          across a group of non-clustered WL servers, and maintain the user session to the
          one WL server so that it doesn't switch between servers on alternate requests for
          the same user session, or must the servers be configured as a WebLogic cluster?
          Paul
          We find that if you have a collection of WL servers that are not configured as a
          cluster, that it will load balance alternate requests to each server, but it will
          not pin a user to a single machine according to their session so for 2 servers, 2
          differetn sessions get created, one on each machine.
          Is this because it doesn't normally do this, but sends the user alternately to a
          primary then secondary which works in a cluster because the session is replicated.
          I thought the secondary was only used when the primary failed.


We're running WL Server 6.1 SP 2 on Solaris 2.8.          >
          > For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf
          option,
          > do the WL servers you want to load balance across have to be part of a
          WebLogic
          > cluster (if you are prepared to do without failover, as I know it would
          need to be
          > a proper WL cluster to replicate session info for failover). Can you load
          balance
          > across a group of non-clustered WL servers, and maintain the user session
          to the
          > one WL server so that it doesn't switch between servers on alternate
          requests for
          > the same user session, or must the servers be configured as a WebLogic
          cluster?
          You don't have to use the clustering option. To get failover, you'll have to
          use the JDBC persistence option of WL.
          > We find that if you have a collection of WL servers that are not
          configured as a
          > cluster, that it will load balance alternate requests to each server, but
          it will
          > not pin a user to a single machine according to their session so for 2
          servers, 2
          > differetn sessions get created, one on each machine.
          >
          > Is this because it doesn't normally do this, but sends the user
          alternately to a
          > primary then secondary which works in a cluster because the session is
          replicated.
          > I thought the secondary was only used when the primary failed.
          The primary/secondary stuff requires clustering. If Apache continues to
          "load balance" after the first request, you need to either use JDBC session
          persistence or use a different load balancer (like mod_jk for Apache or a
          h/w load balancer with support for sticky).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Paul Hammond" <[email protected]> wrote in message
          news:[email protected]...
          >

Load Balancer URL is not working properly

Hi
I have an issue when I am trying to use my load balancer URI for my web services.
I am trying to open the webservice URI in the browser which is on the following location
https://soa.xyz.com/soa-infra/services/default/Order!1.0*soa_c37f07ab-e0f5-4267-bc9c-5dde677efe9f/order_client_ep?WSDL
when I open it I notice that the abstract wsdl tag has http connection and not https. And also it shows my node1 uri instead of load balancer uri.
<abstractWSDL>http://node1.xyz.com:8001/soa-infra/services/default/Order!1.0/Order.wsdl</abstractWSDL>
When I try importing this WSLD onto jDev I get the following error
Exception:
WSDLException: faultCode=PARSE_ERROR: Failed to read wsdl file at <load-balancer wsdl uri>
caused by: javax.net.ssl.SSLHandshakeException :
javax.net.ssl.SSLHandshakeException : sun.security.validator.ValidatorException: No trust certificate found.
- This is a two node cluster with a loadbalancer
-- On both nodes, http, WebLogic and SOA installed
-- WL Admin server was setup on node1
-- On loadbalancer a self signed SSL certificate was installed and this cerificate was imported on both nodes.
-- All services are up
Can anyone tell me if I have missed something during configuration or something else? Any help would be appreciated.
Thanks.

Hi,
Enable the SSL debug to see what's happening... Have a look at this...
https://blogs.oracle.com/WebLogicServer/entry/ssl_troubleshooting_and_debugg
Cheers,
Vlad

Load balancing 10g forms - Connection from new browser window not supported

Load balancing 10g forms - Connection from new browser window not supported
We're experimenting with using webcache to load balance between multiple applications servers running OC4J forms processes.
We currently have one machine with infrastructure and mid-tier (BI & Forms) installed, which is being used for the webcache functionality, this is load balancing between 2 other servers each of which just have the mid-tier (BI & Forms) installation
In order to get this to work, I had to follow the instructions in the Forms deployment guide : http://download-uk.oracle.com/docs/cd/B14099_11/web.1012/b14032/tuning.htm#sthref707
The main gist of this is that you need to set the following in the orion-web.xml file in order that the sessions are maintained:
<session-tracking
cookies="enabled">
</session-tracking>
This all works fine in most cases.
The problem I am having is if I do one of the following on the client machine:
1) From IE6 / IE7 run a copy of a forms application. Then open a new window using the "New Window" menu option, and attempt to run another forms application.
2) In IE7 or Firefox 2.0 open a copy of the forms application, and then open a new tab and try and open another forms application.
If I try either of these I get a FRM-92101 error, and the following is displayed in the java console:
oracle.forms.net.ConnectionException: Connection from new browser window not supported
From trawling various forums (including metalink and otn) it looks like a problem with the way coockies are handled.
Unfortunately the usual workaround is to ensure that the session tracking option in the orion-web.xml file is disabled.
The problem is that I need this enabled in order for the load balancing to work.
Does anyone know of any other workarounds or patches that might help resolve this?
We're using Application server 10.1.2.0.2 running on windows 2003 servers.

You were right. Carriage returns were stopping it from working (the document is laid out over separate lines, so I assumed it would make no difference...).
I've now managed to get it so the forms at least run, but they are all being run in the forms OC4J instance on the same machine as the OHS.
Has anyone actually managed to get this to work, or am I doing something wrong?
I did wonder if using an OHS instance on a machine with no forms installation would make any difference?
I had raised a support call via metalink on this subject, but they eventually came to the conclusion that the only way to do this is with a hardware load balancer (Despite several documents suggesting that webcache is the way to go (including the forms deployment manual)).
I'm at the point now of giving up and writing some custom scripts to do the job instead...

Load Balancing - Wireless

Hi
If I'm reading correctly Load Balancing is not advisable if using voice of wifi.
On a conroler with 70.220 - Wireless - Advanced - Load balancing
Load balancing - client windows is default 5, max denial 3
But on the wlan, the load balancing isn't enabled..
Which one is the master setting?
We're boardcasting several SSIDs, one of them is a guest SSID, which is open, so we get the Apple devices autmaticaly associating to them.
So if we dont set the load balancing on each wlan, this means there is a msximum of 5 devices to 1 AP, doesn't matter which wlan it's on?
Is there a best practice guide for load balancing?
Clarrifaction would be great
Cheers
Craig

Craig,
Do not use load balancing for latency-sensitive WLANs, especially voice WLANs. Rejecting voice clients extends their roaming delay and can drop calls.
The setting on the WLAN Advanced tab determines whether or not clients associating to that WLAN will be denied if the load balancing algorithm determines the AP to which the client wants to associate is too loaded (determined by the global LB settings). If you have the box unchecked, then LB is not in effect for that WLAN and clients on that WLAN will never be rejected.
The load balancing algorithm is run against clients for an AP. The count of clients is cumulative for all WLANs, i.e., the load balancing numbers are not set and comared on a per-WLAN basis. This wouldn't make a lot of sense as the LB algorithm is attempting to keep clients physically spread across infrastructure radio resources, regardless of whether you have 1 WLAN or 5 WLANs active on the radio.
I don't know of a best practices guidefor load balancing other than don't use it on WLANs that have low-latency applications such as voice or live-streaming (unbuffered) video. The controller configuration guide is a good place to start and does a pretty good job of explaining how it works.
One other thing I would recommend is to make the algorithm less aggressive. I think max 3 denials is too high and would drop to 1 or 2. I'd also open up the LB window size to about 8 or 10 instead of the default 5.
I think some folks on the forums here have found some issues with LB, although I haven't run into too many so far. I think the AP sends a message type 17 and some clients have trouble processing it (or something like that). You might want to search the forums here and check the bug toolkit to see if there's anything that comes up.
Justin

Multiple dgraph clustering (load balancing) OOTB available?

Hello,
We have 2 dgraphs running in parallel having the same data to share the load of the clients.
I would like to know if there is any OOTB solution provided by Endeca where in these two dgraphs can share the load. OR I need to use an external load balancer for the same?
If there is any document that explains the configuration for OOTB Endeca solution, please let me know
Thanks!

Hi,
yes I know...
i tried to check if they were still available...but found none,
that's why I said if you want me to send them email me ...(I downloaded them from Eden ) and the files aren't too big
regards
Saleh
29/11/12 : copy of the document called Simple MDEX Load Balancing with Apache HTTP Server (Endeca)
Endeca Solution Article Simple MDEX Load Balancing with Apache HTTP Server
Endeca Solution Article
Simple MDEX Load Balancing with Apache HTTP Server
By Robert Dennis
Last Updated: December 2010
Endeca Product Versions: 5.0+
This document describes how to set up a simple load balancing and failover solution using Apache HTTP server. This provides a cost effective mechanism leveraging widely available open source technologies to address simple infrastructure needs. This document includes the following sections:
 Introduction
 Configuration Steps
 References
Endeca Solution Article Simple MDEX Load Balancing with Apache HTTP Server
Endeca Confidential 2 of 5
Introduction
Load balancers are the preferred solution for providing scalability, redundancy, and fail-over for MDEX Engine queries. Typically, load balancing and failover are accomplished with the use of dedicated load balancing hardware. For some Endeca implementations, however, a robust mechanism for load balancing may not be available or required by the customer. For more information on the basics of load balancing an Endeca application, see the “Endeca Load Balancing Best Practices” Solution Article available on EDeN.
This document describes the configuration steps involved in leveraging Apache’s default load balancing mechanisms to provide a simple load balancing solution for an Endeca application. In this scenario, Apache will sit between the Endeca presentation API housed in a web application and redundant MDEX engines. Apache performs the duties of a simple load balancer and failover broker, managing query requests from the application tier to specific MDEX engines.
Configuration Steps
The described configuration leverages Apache 2.2 HTTP Server as the load balancing mechanism between two identical MDEX engines all residing on a single server. The sample configuration expects the Apache HTTP server to be listening on port 5555 and the MDEX engines to be listening on ports 8000 and 8001. These can be changed as appropriate for a given environment.
1. In the Apache httpd.conf, enable the server for listening on port 5555.
Endeca Solution Article Simple MDEX Load Balancing with Apache HTTP Server
Endeca Confidential 3 of 5
2. Enable the following modules by un-commenting the appropriate loadmodule statements in the httpd.conf file. These modules include: mod_proxy, mod_proxy_balancer, mod_proxy_connect, mod_proxy_http, mod_negotiation.
3. Include the httpd-vhosts.conf file by un-commenting the appropriate line in the httpd.conf file.
4. Save the httpd.conf file and open the httpd-vhosts.conf file. Append the below information and save the file.
Endeca Solution Article Simple MDEX Load Balancing with Apache HTTP Server
Endeca Confidential 4 of 5
NameVirtualHost *:5555 <VirtualHost *:5555> ServerName localhost ProxyPass / balancer://dgraphs/ ProxyPassReverse / balancer://dgraphs/ <Proxy balancer://dgraphs> BalancerMember http://localhost:8000 loadfactor=1 retry=0 BalancerMember http://localhost:8001 loadfactor=1 retry=0 </Proxy> </VirtualHost> <Location /balancer-manager> SetHandler balancer-manager </Location>
The “retry” parameter associated with Balance Members disables the period of inactivity for a particular worker after Apache determines it is offline. The default is 60 seconds. It is recommended that this is set to a low number such as 0.
In environments where particular MDEX engines are targeted for additional load, the “loadfactor” parameter associated with Balance Members can be adjusted. Higher values ensure that the load balancing algorithm that is used will route the traffic load accordingly to specific Balance Members.
5. Restart Apache.
6. Within the UI application, configure the host and port of the HttpENEConnection to the host and port of the load balancer (e.g. localhost:5555).
Endeca Solution Article Simple MDEX Load Balancing with Apache HTTP Server
Endeca Confidential 5 of 5
Apache HTTP Server is now properly configured to serve as a load balancer for the MDEX Engines.
References
“Endeca Load Balancing Best Practices” Solution Article (EDeN)
Apache Module mod_proxy
Apache Module mod_proxy_balancer
Apache Module mod_proxy_connect
Apache Module mod_proxy_http
Apache Module mod_negotiation
Edited by: sabdelhalim on Nov 28, 2012 5:46 PM

Load-balancing with OCI connections

Gurus,
Oracle Identity Federation (OIF) can leverage an Oracle database as its transient data store in which case it uses JDBC-OCI connections to connect. However, there is no provision in OIF of defining multiple databases for load-balancing purposes.
Is this achievable using some load-balancer in front of multiple database instances and using a virtual hostname/IP in tnsnames.ora which OIF refers to?
-Vinod

I would say that using two seperate databases (with replication)
as the backend would mean that one database, at any time,
might be lagging the other, depending on which tables are updated
and how replication is implemented.
Connect Time Failover, rather than Load Balancing, might be an
implementation -- to handle Instance Failure (eg node / site has gone down).
Instead of Load Balancing.
Load Balancng between two seperate databases would be usable
if you are sure that either of
a. The underlying data doesn't change
OR
b. The application and users are aware that they might see different data
if there ARE changes to the data, not yet synchronised between the two DBs.

Anyconnect client problem, load balancing fqdn changes after update client?

Hi,
We use two asa's in loadbalancing. Users use the loadbalancing fqdn name to connect. This works fine until we push new client anyconnect software, that the connect to field changes from the fqdn to the appliance ip address where the client downloaded the software. So loadbalancing will not work anymore. Is there a solution for this?
Thx,
Marc

This sounds like CSCsz39019:
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz39019
Symptom:
Anyconnect client preserves the FQDN name of the ASA its connecting to instead
of load-balancing cluster FQDN.
Workaround:
When the cluster member appears in the host list, user can select the correct
host by clicking the drop down. The next time user starts the client, the
cluster member will no longer be visible. It will have been replaced with the cluster name last selected.
This should be fixed in 2.3(2028)
2.4(192) and 2.5(53) or any higher release. Keep an eye out for the next release with this fix.

Default WAN in RV042 Load Balancing

If I choose the RV042 mode as load balancer and bind some protocol to specific WANs, what will happen to the protocols that I didn't bind to any specific WAN? will they go to WAN1 by default?
Thanks

Hi,
When Load Balance is enabled, RV042 will dispatch (using weighted Round Robin) incoming sessions to WAN1 and WAN2 according to the ratio of the WAN bandwidth. A session is defined by a TCP connection or a UDP stream with certain timeout.
I found this in the users guide.
* Dual WAN. There are two functions provided for users – Smart Link Backup and Load Balance..
* If Smart Link Backup is selected, you only need to choose which WAN port is the primary and then the other will be the backup. See Figure 6-22.
* If Load Balance is selected, there will be two main choices:
•    By Traffic – Intelligent Balancer (Auto) and user defined. See Figure 6-23. First, choose the Max. Bandwidth of Upstream (64K/128K/256K/384K/512K/1024K/1.5M/2M/2.5M or above) and Downstream (512K/1024K/1.5M/2M/2.5M or above) for WAN1 and WAN2, as provided by your ISP.
•    Intelligent Balancer (Auto): When choosing Intelligent Balancer, it will automatically compute the maximum bandwidth of WAN1 and WAN2 by using Weighted Round Robin to balance the loading. If (upstream / downstream / upstream or downstream) bandwidth is excessive (30%, 40%, 50%, 60%, 70%, 80%, 90%), bring up the second link. When there is an inactivity time-out (None/10min/20min/30min/40min/50min/60min), the second link will be terminated.
Adding to this is the operation of Network Service Detection (NSD), which allows RV042 to ping the liveliness of the default gateway of the WAN port or a specified Host. The retry timeout and retry count will affect how long RV042 determines the WAN is down. By default the detection time is
(Retry timeout) + (Retry count) * (5 sec) // the 5 sec is hard coded (which is about 1 minute)

Aggressive Load Balancing = unstable network

Last week we upgraded 26 WLCs 4400 controllers from version 5.2.178 to version 6.0.188.0/6.0.196.0.
Two days after the upgrade, IT-administrators had reported problems with 15 of the WLCs.
The symptoms was:
- Problems conntecting to SSIDs
- Unstable network when connected
- Clients didnt get a IP-adress
- Unstable signal strength
After some troubleshooting, it turned out "Aggressive load-balancing" was enabled on the WLCs having these problems.
Output from one WLC:
(Cisco Controller) >show load-balancing
Aggressive Load Balancing........................ Enabled
Aggressive Load Balancing Window................. 0 clients
Aggressive Load Balancing Denial Count........... 3
Statistics
Total Denied Count............................... 5873 clients
Total Denial Sent................................ 14067 messages
Exceeded Denial Max Limit Count.................. 2924 times
None 5G Candidate Count.......................... 8215 times
None 2.4G Candidate Count........................ 2331 times
Yesterday we ran this command on these WLCs:
config load-balancing aggressive disable
..and the problems now seem to have dissappeared.
Aggressive load-balancing is disabled as default in the newest versions of WLC software, but we have upgraded since version 4.0.155.5 (where I think this was enabled as default), and I guess this setting was enabled because of that.
Some info from cisco.com about aggressive load balancing:
Aggressive load-balancing works at the association phase. If enabled and the conditions to load-balance are met, when a wireless client attempts to associate to a LAP, association response frames are sent to the client with an 802.11 response packet that includes status code 17. This code indicates that the AP is too busy to accept any more associations.
It is the responsibility of the client to honor, process or discard that association response frame with reason code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it tries. Many clients do not do this and send the association request again. The client in question is allowed on to the wireless network upon subsequent attempts to associate.
Just wanted to post this in case others are experiencing problems like we did

Tweak your RF. You need to adjust the TX power and the data rates. The reason you have one AP with 9 clients is probably because that AP has the lowest TX power setting like 7-8. Make each AP the same TX power level, depending on how many AP's and how big the room is. You will need to play around with this and the data rates to achieve what you want.
Here is a guide to look at too
http://www.cisco.com/web/strategy/docs/education/cisco_wlan_design_guide.pdf
Sent from Cisco Technical Support iPhone App

Client load-balancing

Hi all,
a short question.
Is there a feature in Cisco WLC like load-balancing based on bandwidth utilization?
What I mean is, one AP (channel6) has a channel utilization of 40%, the neighbor AP (channel 11) has a channel utilization of 10%.
So I would like push new clients automatically to the AP in channel 11.
many thanks
Martin

It doesnt work worth a crap anyway ... Most clients don't adhere to code 17 so what's the point ...
Aggressive load-balancing works at the association phase. If enabled and the conditions to load-balance are met, when a wireless client attempts to associate to a LAP, association response frames are sent to the client with an 802.11 response packet that includes status code 17. This code indicates that the AP is too busy to accept any more associations.
It is the responsibility of the client to honor, process or discard that association response frame with reason code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it tries. Many clients do not do this and send the association request again. The client in question is allowed on to the wireless network upon subsequent attempts to associate.

CISCO Load Balancer with SAP on Unix and Oracle

Hello Experts,
Explain me the steps How CISCO Load balancing Mechanism works with SAP Enterprise Portal?
If anyone implemented and achieved the same,please explain me the steps to follow from Initial Stage to end of implementation.
Or If you have any documentation on this just share with me or point me to the particular link.
I have seen the below SAP help which is somewhat helpful.
http://help.sap.com/saphelp_nw04s/helpdata/en/d3/e12840d89d185de10000000a1550b0/frameset.htm
I would like to know how CISCO will connect to M/essage Server /Java Dispatcher.
And explain me the steps to follow to implement External Facing Portal using Cisco Loadbalancer.
This should be achieved in Unix environment.
Any help would be greatly appreciated.
Regards,
Karthick Eswaran
*Points will be rewarded for helpful suggestions

We use F5 for loadbalancing, but all hardware loadbalancing solutions should similar. They offer multiple algorithms, we use simple round robin (SAP's webdispatcher has better options for load balancing). You create virtual IP to your CISCO loadbalancer. You then configure Cisco to route traffic to each portal application server. If you have CI + 2 appservers, you configure the loadbalancer to send traffic to cihost:port, appserver1:port, appserver2:port. You also create a DNS alias to the virtual IP of the loadbalancer. End users will use the DNS alias to connect your portal. Typically you use standard ports (80 & 443) on Cisco, so that end user URL does not contain any ports (so http traffic goes to port 80, https goes to port 443). You also need to enable cookie persistence on the load balancer for session persistence.
For external facing portal, you need to have your loadbalancer in DMZ and you want to use SSL. You also need to setup firewall rules for your portal and backend servers.
-RK

CSM for enabling hot spare instead of load balancing

Similar Messages

Maybe you are looking for