VCA agent cannot contact VCRM via cluster name

[Mikael Rönnbäck]

We are in the process of setting up a clustered SIM solution, we have previously used this on a single server but now are required to set up a redundant solution.

Following the "Install SIM on a MSCS cluster" whitepaper installation goes smoothly, provided you read the requirements on which user accounts can be in domain and which must be local on the server.

When selecting the shared disk for installing SIM, it will also by default cluster the other solutions, including VMMS and VCRM.
So far everythings is working fine :-)

Now we come to the agents, and here the problem starts, the VC Agent (7.30) just will not accept connecting to the cluster name, but will happily connect to any of the node names. The problem is that you cannot from what I see specify two names for the VC Agent, and specifying only one of the nodes will result in no Version control at all if the other node currently owns the cluster.

I have had some help from our local HP support contact in trying to find the cause for this but he cannot find any information on this problem or any information saying it shouldn't work, so I am unsure where to start looking for additional information.

[Rich Purvis]

Does this thread:

http://forums2.itrc.hp.com/service/forums/questionanswer.do?threadId=879231

have any useful information on this? Does the cluster have a shared IP address at all? If so you could use the IP address instead of the name of the node to configure the VCA's.

-Rich

[Mikael Rönnbäck]

Thanks for the link, but unfortunately it does not seem to help. Yes the cluster has a shared IP adress and no it won't work either just as the dns name pointing to it does not work.