10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear All,
Can any one help me for this request?
There is a case. I have 20 files which I need to FTP to 5 servers. I want to know if there is any possibility to make a load balancer which transfers files in round robin manner to 5 servers.
As per theoretical algorithm, what I think, flow can... (9 Replies)
Discussion started by: Zaib
9 Replies
2. UNIX for Advanced & Expert Users
Hi,
I am working on development project where I have to migrate many jobs from Tidal to Autosys R11.
During this project we came across the following requirements.
1. There are 3 real machines. There could be many jobs activated simultaneously, but only one job should execute at a time and... (0 Replies)
Discussion started by: sujeetp
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
Currently we have 3 old and 3 new servers catering to Live traffic. As my component move from legacy interfaces to MQ one, we want to have load balancing of old interfaces available on MQ interface as well.
For this, we want to send only 30% of all MQ traffic on 3 OLD Live servers, and want... (1 Reply)
Discussion started by: senkerth
1 Replies
4. IP Networking
Hello everybody
How can i Load Balance two slow ppp(gprs) connections with iptables . (4 Replies)
Discussion started by: rink
4 Replies
5. Linux
Hi,
We have 2 pools of servers. Lets call them A and B and they would contain 2 servers each. Pool A will be hosting www.example.com/app/v1 and pool B will be hosting www.example.com/app/v2. Clients will be requesting right url (/v1 or /v2) but will be hitting just one IP.
I'd like to:
1)... (3 Replies)
Discussion started by: chrisfb
3 Replies
6. UNIX for Advanced & Expert Users
Hi folks,
(Sorry I don't know what its technology is termed exactly. High Availability OR load balancing)
What I'm going to explore is as follows:-
For example, on Physical Servers;
Server-1 - LAMP, a working server
Server-2 - LAMP, for redundancy
While Server-1 is working all... (3 Replies)
Discussion started by: satimis
3 Replies
7. Web Development
Hi All,
I have one webserver which has an application for a set of internal users can be accessed by _http://server1.com
I am planning to load balance this application. For that I have cloned this server and build a new one which can be accessed using _http://server2.com]Server2.com. Also i... (2 Replies)
Discussion started by: Tuxidow
2 Replies
8. Solaris
Is it possible to do a load balancing ( incoming and outgoing )with with IPMP in solaris 10 like sun trunking ? If yes what are the steps involved in it , i know how to do the failover IPMP both link based and probe based but i 'm looking for possible load balancing (3 Replies)
Discussion started by: fugitive
3 Replies
9. Ubuntu
Hi guys, I wonder if someone would be able to assist with my problem. I have just set up a load balancer for a company I am working for. HTTP redirection is working fine, however they also want to load balance SSH and FTP too.
At the moment the perlbal config looks like;
CREATE POOL webhttp
... (1 Reply)
Discussion started by: JayC89
1 Replies
10. UNIX for Dummies Questions & Answers
If you have two or more servers load balancing, are the servers mirroring one another? If images, etc., are uploaded, will they be stored on all the servers so that if one server goes down, the images will be served up by another server? (1 Reply)
Discussion started by: wvmlt
1 Replies
OCF_HEARTBEAT_ISCSIT(7) OCF resource agents OCF_HEARTBEAT_ISCSIT(7)
NAME
ocf_heartbeat_iSCSITarget - iSCSI target export agent
SYNOPSIS
iSCSITarget [start | stop | monitor | meta-data | validate-all]
DESCRIPTION
Manages iSCSI targets. An iSCSI target is a collection of SCSI Logical Units (LUs) exported via a daemon that speaks the iSCSI protocol.
SUPPORTED PARAMETERS
implementation
The iSCSI target daemon implementation. Must be one of "iet", "tgt", or "lio". If unspecified, an implementation is selected based on
the availability of management utilities, with "iet" being tried first, then "tgt", then "lio". (optional, string, no default)
iqn
The target iSCSI Qualified Name (IQN). Should follow the conventional "iqn.yyyy-mm.<reversed domain name>[:identifier]" syntax.
(unique, required, string, no default)
tid
The iSCSI target ID. Required for tgt. (unique, optional, integer, no default)
portals
iSCSI network portal addresses. Not supported by all implementations. If unset, the default is to create one portal that listens on .
(optional, string, default 0.0.0.0:3260)
allowed_initiators
Allowed initiators. A space-separated list of initiators allowed to connect to this target. Initiators may be listed in any syntax the
target implementation allows. If this parameter is empty or not set, access to this target will be allowed from any initiator.
(optional, string, no default)
incoming_username
A username used for incoming initiator authentication. If unspecified, allowed initiators will be able to log in without
authentication. This is a unique parameter, as it not allowed to re-use a single username across multiple target instances. (unique,
optional, string, no default)
incoming_password
A password used for incoming initiator authentication. (optional, string, no default)
additional_parameters
Additional target parameters. A space-separated list of "name=value" pairs which will be passed through to the iSCSI daemon's
management interface. The supported parameters are implementation dependent. Neither the name nor the value may contain whitespace.
(optional, string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 10.
stop
Stops the resource. Suggested minimum timeout: 10.
status
Suggested minimum timeout: 10. Suggested interval: 10.
monitor
Performs a detailed status check. Suggested minimum timeout: 10. Suggested interval: 10.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 10.
EXAMPLE
The following is an example configuration for a iSCSITarget resource using the crm(8) shell:
primitive p_iSCSITarget ocf:heartbeat:iSCSITarget
params
iqn=string
op monitor timeout="10" interval="10" depth="0"
SEE ALSO
http://www.linux-ha.org/wiki/iSCSITarget_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_ISCSIT(7)