Hi Gurus, I have a question related to Veritas Cluster 5.0. I have configured HA setup using two nodes. I have installed my prodcut in both the nodes. Now I can access my product using the Virtual IP address. But the fact is my product runs based on the server hostname. So as like as Virtual IP address , if there is virtual hostname then i dont want to install product on both the nodes. Instead i can use a storage array in between and install prodcut on that storage array using virtual hostname which is created when configuring the cluster. Can anyone help me on this problem. With Regards, Sri

Hi Sri, what is the OS here ? In any case, as far my experience, in any case, product binaries need to be there on each host.... not sure but I am not very clear with your query.... Gaurav

Garuav, I have installed my product on the Storage array. Thro SAN technologies i have connected both servers to this array. Now using Cluster i am going to online one server so that only one of the server willl be pointed to the array at an instant. As you asked, as my binaries are going to be placed in the Storage array so no need for keepnig the binaries in both the servers. But my question is, Most of the files in my application are based on hostname, Hence when i install my product on storage array using primary server(in which the cluster is online) i can see the hostnames are poinitng to primary server hostname. hence after failover my application will not work, as secondary server hostname is different. Hence my idea is to have a hostname (virtual) which is common to both the servers(and it will be used by the server which is online). is this possible to acheive this virtual hostname concept along with virtual IP address assignation during the cluster configuration ? I want to do this in both windows and solaris . Regards, Sri

Hi Sri, For the Windows version, the Lanman resource is what you would configure to handle virtual names. I think the Solaris product also uses Lanman but I'm not sure. You can check the Bundled Agent's Guide for the Solaris product to see if it has a Lanman agent or not. Thanks, Wally

Hi Sri, OK I understand the query now.... firs thing, Lanman agent is not available for solaris.... One very simple issue I think why this wouldn't work with shared location of binaries is, using a cluster (if VCS), uses a mechanism of LLT. To configure LLT correctly, system name should be picked separately along with its node ids. Lets assume we created the files under /etc but how they would behave is unknown... above mentioned thing would not have been tested for solaris atleast.. Gaurav

Thanks Gaurav and Wally for their valuable inputs. As wally suggested let me try with Lanman resource for windows. For Gaurav`s question, let me explaing about my prodcut little more in brief. While installing my prodcut , it will take the hostname of the server from which installation is triggered. For example let us assume my server1 is assigned with hostname ServerA and server2 is with ServerB. So i am installing my prodcut using Server1 in storage array , so my product binaries will be incorporated with ServerA as hostname. So if a failover happens, my product binaries will not work from Server2 because Server2 hostname is ServerB which is not present in my prodcu binary files. THis is my problem. So as a solution , what i am trying to do is I am going to install my product using a hostname which will be common to both the server. Hence If i do a setup using virtual hostname and installing my product using the virtual hostname (it will be applicable for both the servers), even after failover that name will be allocated to Server2 also, hence my binaries will be working from server2 also. Hope you understood my problem now.. With Regards, Sri

Is virtual host name created in cluster

14 Replies

Sridhar_sri
Level 5
15 years ago
Thanks Wally for your wonderful support.

As you iterated already, there is no such lanmen resource for solaris environment. Just let me know if you have any idea for solaris also as like as windows.

Thanks,
Sri.
Gaurav_S
Moderator
15 years ago
I think you are unfortunate for Solaris.... :-(

Not sure how you will workaround this.. you won't have a supported or trusted solution here I believe....

Gaurav
Sridhar_sri
Level 5
15 years ago
Thanks Gaurav,
i will try to do some workaround in solaris. If i got any i will post the same in this forum.

Regards,
Sri
Roger_Zimmerman
Level 4
15 years ago
Hi, Sri,

which version of solaris you are working with? There are Solaris Virtual Machines called Container in Solaris 10 and per Patch also in Version 9.

With this you can do the following:
- make a Solaris Container, probably one that is owning only a few things (shared all zone) what is making an own environment, especially a hostname, take care for the switchable disks!
- make this zone switchable (only two files per node have to be changed / created)
- install your application into this zone, the most things are delivered by the global zone then and only the hostname by the local zone
- configure the Cluster environment, take especially care for the attribute "Container" for the few things delivered by this container
- be happy!!

Result of this will be an installation where volume manager, volumes, mount points, nics etc. comes from the global zone and hostname and ip adress from the local zone. Your service group spans both zones.

This is a very elegant method to provide not only a virtual server name through an ip adress but a really existing hostname for applications what are hostname aware, not logical interfaces aware.

Best regards
Roger

Forum Discussion

Is virtual host name created in cluster

14 Replies

Related Content

Unable to create a cluster user

Virtual Cluster backup using virtual media

Discovery of NetApp SVM from a new cluster (or established) on a newly created Collector.

Backup Exec cannot create a recovery checkpoint for the virtual machine

0xe00095b3 - Unable to create the virtual disk

Recent Discussions

Configure two Mount type resources of nfs FStype attribute using the same share

order

key registration and reservation

Verifying that primary and dr clusters replication is synced

vcs can create logical nic