Thursday, March 20, 2014

Using vsftpd under Veritas VCS Application agent


Add a group

haconf -makerw
hagrp -add vsftpd_grp
hagrp -modify vsftpd_grp SystemList Node01 0 Node02 1
hagrp -autoenable vsftpd_grp -sys Node01
hagrp -autoenable vsftpd_grp -sys Node02
hagrp -modify vsftpd_grp OnlineRetryLimit 3
# start group on both nodes
hagrp -modify vsftpd_grp AutoFailOver 0
hagrp -modify vsftpd_grp Parallel 1

Add Resource

hares -add vsftpd_res Application vsftpd_grp
hares -modify vsftpd_res StartProgram "/etc/init.d/vsftpd start"
hares -modify vsftpd_res StopProgram  "/etc/init.d/vsftpd stop"
# if you want to run as root - ignore this line
hares -modify vsftpd_res User a_user_name
# command will be executed as su - a_user_name
hares -modify vsftpd_res UseSUDash 1                  
# Monitor process - whole string as appears in ps -ef output
hares -modify vsftpd_res MonitorProcesses \ 
   "/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf"
# not tested
hares -modify vsftpd_res MonitorProgram "/etc/init.d/vsftpd status"
# does not write a pid file - ignore it
hares -modify vsftpd_res PidFiles "/var/run/vsftpd.pid"         
hares -modify vsftpd_res Enabled 1
# Make group dependendt on cluster filesystem (or any other group you wish)
hagrp -link vsftpd_grp CFS_Group online local firm
haconf -dump -makero

Bring vsftpd online

hagrp -online vsftpd_grp -sys Node01
hagrp -online vsftpd_grp -sys Node02

Snip from config file

group mq_group (
        SystemList = { Node01 = 0, Node02 = 1 }
        AutoFailOver = 0
        Parallel = 1
        AutoStartList = { Node01, Node02 }
        OnlineRetryLimit = 3
        )

        Application activemq (
                StartProgram = "/etc/init.d/vsftpd start"
                MonitorProcesses = { "/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf" }
                StopProgram = "/etc/init.d/vsftpd stop"
                )

        requires group CFS_Group online local firm

Thursday, March 6, 2014

Using bond interface for Veritas VCS LLT link

If you need to use bonded interface (say bond0) in Veritas VCS on linux, you may be getting jeopardy entries in gabconfig -a.


# gabconfig -a  ( on a three node cluster)
GAB Port Memberships
===============================================================
Port a gen   5afa01 membership 01
Port a gen   5afa01   jeopardy ;1
Port b gen   5afa04 membership 01
Port b gen   5afa04   jeopardy ;1
Port d gen   5afa07 membership 01
Port d gen   5afa07   jeopardy ;1
Port f gen   5afa13 membership 01
Port f gen   5afa13   jeopardy ;1
Port h gen   5afa09 membership 01
Port h gen   5afa09   jeopardy ;1
Port u gen   5afa11 membership 01
Port u gen   5afa11   jeopardy ;1
Port v gen   5afa0c membership 01
Port v gen   5afa0c   jeopardy ;1
Port w gen   5afa0e membership 01
Port w gen   5afa0e   jeopardy ;1
Port y gen   5afa0b membership 01
Port y gen   5afa0b   jeopardy ;1

You need to change llttab like bellow ( see set-dbg-minlinks 2) and it will go off !

# cat /etc/llttab
set-node
set-cluster 59195
link bond0 bond0 - ether - -
set-verbose 1

set-dbg-minlinks 2

A good working gabconfig will loook like:

# gabconfig -a
GAB Port Memberships
===============================================================
Port a gen   495401 membership 012
Port b gen   495405 membership 012
Port d gen   495408 membership 012
Port f gen   495417 membership 012
Port h gen   49540c membership 012
Port u gen   495414 membership 012
Port v gen   49540f membership 012
Port w gen   495411 membership 012
Port y gen   49540e membership 012