Skip to main content

What a Cluster... VCS 5.1 on ESX (vSphere)

I had originally planned on this being a lengthy post, detailing my experience with building a 2-node Veritas Cluster Server environment using VMware vSphere 4.1 hosting Red Hat 5.7 and VCS 5.1 SP1GA.

Once I had the cluster up and running, it seemed to be somewhat flaky and I decided to focus on more important things.  I might get back to this someday.

I guess my greatest surprise is that fencing appears to be working (even though the "hardware test" failed --
Output:
Preempt and abort key KeyA using key KeyB on node vcs02 ................ Failed
An even greater surprise is why fencing does not work in more environments...

Regardless, here it is...
[root@vcs01 rhel5_x86_64]# hastatus -sum

-- SYSTEM STATE
-- System State Frozen

A vcs01 RUNNING 0
A vcs02 RUNNING 0

-- GROUP STATE
-- Group System Probed AutoDisabled State

B ClusterService vcs01 Y N ONLINE
B ClusterService vcs02 Y N OFFLINE
B cvm vcs01 Y N ONLINE
B cvm vcs02 Y N ONLINE
[root@vcs01 rhel5_x86_64]# gabconfig -a
GAB Port Memberships
===============================================================
Port a gen 5dfc01 membership 01
Port b gen 5dfc15 membership 01
Port d gen 5dfc08 membership 01
Port f gen 5dfc21 membership 01
Port h gen 5dfc18 membership 01
Port u gen 5dfc1e membership 01
Port v gen 5dfc1a membership 01
Port w gen 5dfc1c membership 01

I believe I will be able to test the fencing by removing a disk or two from a node and letting it run it's course.

And.. here is the key:
create a directory on a datastore visible to the ESX server
# mkdir /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/
Then... run the following commands to create the volumes.
#!/bin/sh
vmkfstools -c 512m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/quorum-1.vmdk
vmkfstools -c 512m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/quorum-2.vmdk
vmkfstools -c 512m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/quorum-3.vmdk
vmkfstools -c 2048m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/sharedDB-1.vmdk
vmkfstools -c 2048m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/sharedDB-2.vmdk
vmkfstools -c 2048m -a lsilogic -d eagerzeroedthick /vmfs/volumes/datastore1/SharedDisk-VCS01-VCS02/sharedDB-3.vmdk

Attach them to your 2 VCS-VMs.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...
Post a Comment
Read more