Can LLT heartbeats communicate between NICs with different device names?
One 2-node vcs cluster, the heartbeat NICs are eth2 and eth3 on each node, IF eth2 on node1 down, and eth3 on node2 down. Does this mean the 2 heartbeat Links both down, and the Cluster is in split brain situation? Can LLT heartbeats communicate between NIC eth2 and NIC eth3? Since the 《VCSInstallation Guide》requires the 2 heartbeat Links in different networks.We should put eth2 of both nodes in the VLAN (VLAN1), and put eth3 of both nodes in another vlan (VLAN2). So in this situation heartbeats cannot communicate between eth2 and eth3. But, in a production cluster system, we found out the 4 NICs--eth2 and eth3 of both nodes are all in a same VLAN. and this lead me to post the discussion thread to ask this question: IF eth2 on node1 down, and eth3 on node2 down, What will happen to the cluster (which isin active-standby mode)? Thanks!Solved1.6KViews5likes5CommentsFailed to execute postonline trigger
Postline trigger is getting failed to execute on onlining a resource. Getting a below error. 2015/02/27 01:25:47 VCS INFO V-16-6-15003 (dsacl2ip) hatrigger:Failed to execute /opt/VRTSvcs/bin/triggers/postonline dsacl2ip SG-APP-TM-003 2015/02/27 01:29:27 VCS INFO V-16-6-15003 (dsacl2ip) hatrigger:Failed to execute /opt/VRTSvcs/bin/triggers/postonline dsacl2ip SG-APP-TM-003 i manually executed the command hatrigger -postonline 0 dsacl2ip SG-APP-TM-003 but again same error. Please let me know what can be the issue. Below is my script ccmId="@(#)%name: postonline % %version: 5 %, %date_modified: Thu Feb 19 12:13:59 2015 %" ##################################################### # Configure required IP addresses for TM in this section ##################################################### export TMVIRTIP=10.225.230.57 export TMIPADDRS=" 10.15.14.139 10.15.15.137 10.215.17.0 " ##################################################### # Configure required IP addresses for APPin this section ##################################################### export RMVIRTIP=10.225.238.58 export RMIPADDRS=" 192.168.17.4 " ##################################################### # # DO NOT CHANGE ANYTHING BELOW THIS LINE # ##################################################### ##################################################### if [ -z "$VCS_HOME" ]; then VCS_HOME=/opt/VRTSvcs fi ##################################################### # Source VCS helper script if [ -r $VCS_HOME/bin/ag_i18n_inc.sh ]; then . $VCS_HOME/bin/ag_i18n_inc.sh else function VCSAG_LOG_MSG { msgtype=$1 msgtxt="$2" category="$3" case $msgtype in E) msgtype="ERROR:";; W) msgtype="WARNING:";; I) msgtype="INFO:";; esac echo "`date +'%m/%d %T'`: $msgtype $msgtxt ($category)" } fi ##################################################### # Check if relevant arguments were provided system=$1 group=$2 if [ -z "$system" ]; then VCSAG_LOG_MSG "W" "Failed to continue; undefined system name" 15028 exit elif [ -z "$group" ]; then VCSAG_LOG_MSG "W" "Failed to continue; undefined group name" 15031 exit fi ##################################################### # Determine the interface that the APP virtual IP is bound to function getInterface { /bin/netstat -ie | grep -B1 "$1" | sed -ne "s/\(^$2.*\) *Link.*/\1/p" } ##################################################### function addRoutes { typeset device=$1 typeset gwAddr=$2 shift 2 typeset maskAddr for ipAddr in $*; do if [ "${ipAddr##*.}" = "0" ];then maskAddr=255.255.255.0 else maskAddr=255.255.255.255 fi echo /sbin/route add -net $ipAddr netmask $maskAddr gw $gwAddr dev $device done } ##################################################### case $group in SG-APP-TM-003) virtInterface=$(getInterface $TMVIRTIP bond) if [ -z "$virtInterface" ]; then VCSAG_LOG_MSG "E" "Could not determine interface for virtual IP" 15032 else VCSAG_LOG_MSG "I" "Adding routes for interface $virtInterface" 15032 addRoutes $virtInterface 10.225.238.2 $TMIPADDRS fi ;; SG-APP-DS_RM-004) virtInterface=$(getInterface $RMVIRTIP bond) if [ -z "$virtInterface" ]; then VCSAG_LOG_MSG "E" "Could not determine interface for virtual IP" 15032 else VCSAG_LOG_MSG "I" "Adding routes for interface $virtInterface" 15032 addRoutes $virtInterface 10.225.238.5 $RMIPADDRS fi ;; *) ;; esacSolved930Views4likes1CommentNeed inputs on configuring alerts to send email upon faults
I am planning to setup alerts for my application to notify users upon faults. I understand that i need to configure a NotifierMngr resourse under ClusterService. Please answer following questions that i have for my understanding. 1) Should I configure a new ClusterService group or use the existing one. Currently I have following resources in my existing ClusterService group. # hagrp -resources ClusterService webip csgnic Wouldnt be a risk if Notifier resource is configured in this group itself? If i need to configure a seperate a ClusterService, could you please guide me how do i do that using command line. 2)How to do give multiple severity to a single recipient. What i mean is that if i want error, severe error and warning alerts to reach my email ID, how do i configure? is below command fine hares -modify ntfr SmtpRecipients parakh.agarwal@abc.com Error Warning SevereError 3) How to i give multiple email ID with their respective severity labels. Do i need to modify main.cf file and give email IDs semi colon seperated or is it possible through command line as well? 4) Are below commands to add Notifier resource OK? haconf -makerw hares -add ntfr NotifierMngr ClusterService hares -modify ntfr SmtpServer mailhost hares -modify ntfr SmtpRecipients parakh.agarwal@abc.com Error Warning hares -modify ntfr Enabled 1 haconf -dump -makero 5) is there anything that needs to be done apart from this.Solved1.5KViews4likes14CommentsDisk groups stoping
Hi I installed veritas 6.1 on redhat 6.4 64bit and vom 6.0 and created disk groups and volumes and then service groups failover and mounted the volumes in the service groups. When i restarted node1 the service groups failover good to node2 and when i restarted node2 the failover working good and failover but if i tray to do that mounal switch some service groups failover and others not failover and the state for diskgroups in host stoping and the volume too . Please help RegardsSolved3.1KViews3likes10CommentsGateway problem with MultiNICA (VCS)
Hello We have 2 node cluster on SUSE. The route configuration is done at linux level not the MultiNICA resource. We have upgrade the SFHA6.0.1 to SFHA 6.0.5 & SUSE11SP2 to SUSE11SP3. After upgrade the default route are missing when the server booted up. I am not sure that I must configure the default GW at multinica? Please advice me. Thank you.Solved762Views3likes2CommentsNFS share doesn't failover due to being busy
Hello! We are trying to implement a failover cluster, which hosts database and files on clustered NFS share. Files are used by the clustered application itself, and by several other hosts. The problem is, that when active node fails (I mean an ungraceful server shutdown or some clustered service stop), the other hosts still continue to use files on our cluster-hosted NFS share. That leads to an NFS-share "hanging", when it doesn't work on the first node, and still cannot be brought online of the second node. Other hosts also experience hanging of requests to that NFS share. Later, I will attach logs, where problem can be observed. The only possible corrective action found by us is total shutdown and sequential start of all cluster nodes and other hosts. Please recommend us a best-practice actions, required for using NFS share on veritas cluster server (maybe, some start/stop/clean scripts being included as a cluster resource, or additional cluster configuration options). Thank you, in advance! Best regards, Maxim Semenov.Solved4.4KViews3likes13CommentsCan't locate object method "QEMU" Error During Upgrade to 6.0.x
Hi all, I have a two node VCS cluster running on two KVM Virtual Machines RHEL 5.5. VCS version is currently 5.1 SP1 RP2 and I'm trying to upgrade it to version 6.0.1. Right after I run the installer script I get the following error: [root@Hostname rhel5_x86_64]# pwd /shared_data/VCS/dvd1-redhatlinux/rhel5_x86_64 [root@Hostname rhel5_x86_64]# ./installer Can't locate object method "QEMU" via package "Padv::RHEL5x8664" at /shared_data/VCS/dvd1-redhatlinux/rhel5_x86_64/scripts/EDR/Padv/Linux.pm line 1061. [root@Hostname rhel5_x86_64]# Has anyone encountered such an error before? I've contacted support and so far they have only instructed me to approach RedHat and open a ticket with them. Any help will be much appreciated. Thanks, YairSolved625Views3likes4CommentsIntegration between Veritas Cluster and JDBC driver
Dear Sir, Currently our application uses Oracle RAC for DB failover management and pool the connection at application end. In case of DB failover at one node, application receives the FAN events. Application determine the DB failover based on failover error code (FCF error code) and take certain action. Now we are planning to move HA structure. Sorry, I don't have much knowledge aboutVeritas Cluster. But we are planning to use Veritas Cluster for failover management. To take this option we are currently executing some impact analysis from application point of view. Can you please share your view for following queries- How Veritas Cluster and JDBC driver communicate each other? In case of DB failover at primary node, does the Veritas Cluster generates any failover events (i.e. similar to FCF error code)? As I have mentioned that we maintain the connection at application end. In case of DB failover, Veritas Cluster will refresh the connection pool i.e. remove the stale connection from the pool? If VeritasCluster will not refresh the connection pool in case of DB failover then how application will detect DB failover? Does the application receive any FCF error code while use the stale connection? Please note that currently we using oracle 11gR1 enterprise editions and planning to upgrade the oracle version to 11gR2 or 12c enterprise editions. Regards, KrishnenduSolved2KViews2likes4CommentsWhen can 'hasys -nodeid' fail?
Dear All, We are running VCS Engine version 6.1.0.000 and need to use 'hasys -nodeid' to get info about the node. So in what scenario can this command fail ? Also in VCS 6.1 . , the man page info for this command states that it will display the nodeid value for the corresponding system if the nodeid is supplied whereas in older versions it states that itwill set the supplied nodeid . Can anyone confirm the behaviour when the nodeid is supplied as well please ? Thanks in advance.Solved839Views2likes1Comment