Pages

Showing posts with label idc protocol. Show all posts
Showing posts with label idc protocol. Show all posts

Tuesday, February 2, 2016

How to create High Availability Port with idc protocol ?

How to create High Availability Port with  idc protocol ?




Purpose : Using balance software , HA port is created with idc protocol . So this will help to load balance idc port in clustered domain .



Steps :
1.Install balance
2.run balance command


Detailed Steps :

1. Download balance from : https://www.inlab.de/balance.html




2. Make and Install it

cd balance-3.56
[root@LB balance-3.56]# make

gcc -O2 -Wall -Wstrict-prototypes -Wuninitialized -I. -c balance.c
balance.c: In function ‘stream’:
balance.c:910: warning: pointer targets in passing argument 1 of ‘hash_fold’ differ in signedness
./balance.h:133: note: expected ‘char *’ but argument is of type ‘unsigned char *’
balance.c: In function ‘main’:
balance.c:1813: warning: pointer targets in passing argument 1 of ‘hash_fold’ differ in signedness
./balance.h:133: note: expected ‘char *’ but argument is of type ‘unsigned char *’
gcc -O2 -Wall -Wstrict-prototypes -Wuninitialized -I. -c butils.c
gcc -O2 -Wall -Wstrict-prototypes -Wuninitialized -I. -o balance balance.o butils.o

[root@LB balance-3.56]# make install


install -o root -g root -m 755 balance \
/usr/sbin/balance
install -o root -g root -m 755 balance.1 \
/usr/sbin/../man/man1
install: cannot create regular file `/usr/sbin/../man/man1': No such file or directory


3.Verify by running balance commad

[root@myserver ~]balance
_ _
| |__ __ _| | __ _ _ __ ___ ___
| '_ \ / _` | |/ _` | '_ \ / __/ _ \
| |_) | (_| | | (_| | | | | (_| __/
|_.__/ \__,_|_|\__,_|_| |_|\___\___|
this is balance 3.56
Copyright (c) 2000-2009,2010
by Inlab Software GmbH, Gruenwald, Germany.
All rights reserved.



4.Run the balance command with idc server

Example : balance -b ::ffff:<LB> -B <LBHOSTNAME> <LBPORT> <IP1:POR1> <IP2:PORT2>

[root@myserver ~]# netstat -anp | grep 4444

[root@LB ]# balance -b ::ffff:10.111.11.111 -B LBHOST 4444 10.111.11.121:4453 10.111.11.122:4997
[root@LB ]# netstat -anp | grep 4444
tcp 0 0 ::ffff:10.111.11.111:4444 :::* LISTEN 23705/balance


6. Verify it

Here for testing purpose I am connecting two different WCC servers , which is having different autoprefix and running CHECKIN_UNIVERSAL . Make sure that admin server should be up and running while connecting via idc protocol

url= 10.111.11.111:4444
[sterin@sterinlap test]$ java TestRIDCCheckin
dDocName is SOURCEFF001052
[sterin@sterinlap test]$ java TestRIDCCheckin
dDocName is STJACOBPC1IDCO001205

So It will connect in round robin fashion . If one server is down, then automatically connect to other one