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 ;; *) ;; esacSolved937Views4likes1CommentNeed 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.5KViews4likes14Commentsreallocate the /etc/vx/cbr/bk , vg config backup file without any service restart ...
1. Create the directory to copy the vg config backup file . # mkdir -p /tech/vgconfigbackup/bk ( please must create the "bk" directory ) 2. Take the backup of scripts " /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh " # cp /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh_bkp<date> 3. Made the required change care fully in below script . # vi /usr/lib/vxvm/voladm.d/lib/vxcbrlib comment the existing line "CF_BKUP_BASE_PATH" and change CF_BKUP_BASE_PATH to point to a new location. 4. Delete the all old vg configuration file backup from default location . 5. Take the new vg configuration backup and test 6. Check the new vg configuration file backup in new location .1.4KViews4likes3CommentsSome VCS plexes disabled after power outage
Hi all, I'm running the Veritas Storage Foundation Standard HA 5.0MP3 under Suse Linux Enterprise Server 11 on two Oracle X6270 servers. There was a power outage, causing an immediate brutal shutdown of both servers. After power was restored, the server on which the Oracle service group was active ("db1-hasc") could not boot at all (mainboard failure). The other server ("db2-hasc") booted, but reported during boot that cluster cannot start, and that manual reseeding might be needed to start it, so I started the cluster from the working server db2-hasc using command gabconfig -x (found it after some googling). In the meantime, the failed server db1-hasc was fixed and cluster is now working (all service groups online, but on the db2-hasc, the one which started successfully after power outage). No attempt has been made yet to try to switchover any of the service groups (except network service groups which are online) to the db1-hasc server. However, I have noticed some problems with several volumes in disk group "oracledg": db2-hasc# vxprint -g oracledg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg oracledg oracledg - - - - - - dm oracled01 - - - - NODEVICE - - dm oracled02 sdb - 335462144 - - - - v archvol fsgen ENABLED 62914560 - ACTIVE - - pl archvol-01 archvol DISABLED 62914560 - NODEVICE - - sd oracled01-02 archvol-01 DISABLED 62914560 0 NODEVICE - - pl archvol-02 archvol ENABLED 62914560 - ACTIVE - - sd oracled02-02 archvol-02 ENABLED 62914560 0 - - - v backupvol fsgen ENABLED 167772160 - ACTIVE - - pl backupvol-01 backupvol DISABLED 167772160 - NODEVICE - - sd oracled01-03 backupvol-01 DISABLED 167772160 0 NODEVICE - - pl backupvol-02 backupvol ENABLED 167772160 - ACTIVE - - sd oracled02-03 backupvol-02 ENABLED 167772160 0 - - - v dbovol fsgen ENABLED 62914560 - ACTIVE - - pl dbovol-01 dbovol DISABLED 62914560 - NODEVICE - - sd oracled01-01 dbovol-01 DISABLED 62914560 0 NODEVICE - - pl dbovol-02 dbovol ENABLED 62914560 - ACTIVE - - sd oracled02-01 dbovol-02 ENABLED 62914560 0 - - - db2-hasc# vxprint -htg oracledg DG NAME NCONFIG NLOG MINORS GROUP-ID ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK CO NAME CACHEVOL KSTATE STATE VT NAME RVG KSTATE STATE NVOLUME V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO EX NAME ASSOC VC PERMS MODE STATE SR NAME KSTATE dg oracledg default default 0 1265259474.12.db1-HASc dm oracled01 - - - - NODEVICE dm oracled02 sdb auto 65536 335462144 - v archvol - ENABLED ACTIVE 62914560 SELECT - fsgen pl archvol-01 archvol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-02 archvol-01 oracled01 62914560 62914560 0 - NDEV pl archvol-02 archvol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-02 archvol-02 oracled02 62914560 62914560 0 sdb ENA v backupvol - ENABLED ACTIVE 167772160 SELECT - fsgen pl backupvol-01 backupvol DISABLED NODEVICE 167772160 CONCAT - WO sd oracled01-03 backupvol-01 oracled01 125829120 167772160 0 - NDEV pl backupvol-02 backupvol ENABLED ACTIVE 167772160 CONCAT - RW sd oracled02-03 backupvol-02 oracled02 125829120 167772160 0 sdb ENA v dbovol - ENABLED ACTIVE 62914560 SELECT - fsgen pl dbovol-01 dbovol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-01 dbovol-01 oracled01 0 62914560 0 - NDEV pl dbovol-02 dbovol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-01 dbovol-02 oracled02 0 62914560 0 sdb ENA Does anyone have some ideas on how to recover the disabled plexes/subdisks? Or which other commands to run to ascertain the current state of the cluster, in order to have a clear(er) picture what is wrong and which steps to take to remedy the problem? If so, I would appreciate if you can share any tips/suggestions. The physical disks seem fine (no errors reported in ILOM diagnostics). Thanks, /HrvojeSolved2.2KViews4likes9CommentsVeritas InfoScale 7.0: Licensing Veritas InfoScale 7.0
You require a license to install and use Veritas InfoScale products. There are two ways you can register the Veritas InfoScale product license keys: Use key-based licensing When you purchase a Veritas InfoScale product, you receive a License Key certificate. The certificate specifies the product keys and the number of product licenses purchased. Use keyless licensing The license is registered based on the product you install. Within 60 days of choosing this option, you must install a valid license key corresponding to the license level, or continue with keyless licensing by managing the systems with Veritas InfoScale Operations Manager. You can register the product license keys either manually or by using the installer. You can use the vxlicinstupgrade utility, if you want to: Upgrade to another Veritas InfoScale product Upgrade a temporary license to a permanent license Manage co-existence of multiple licenses For more information on licensing Veritas InfoScale products, see: About Veritas InfoScale product licensing Registering Veritas InfoScale using product license keys Registering Veritas InfoScale product using keyless licensing Updating your product licenses Using the vxlicinstupgrade utility Veritas InfoScale documentation can be found on the SORT website.1.6KViews3likes0CommentsDisk 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.Solved772Views3likes2Comments