OD Configuration in an Active/Passive Cluster

Stange

I have a two part question...both related to our OD configuration/usage in a Veritas Cluster environment on Solaris.

Here are our vitals:
TS 6.7.1
OD 6.1.1
Test and PROD environments are both 2 node active/passive Veritas cluster environments. For TeamSite, only one node is active at a time. The content store is on a floating mount point that is managed by the cluster and is only mounted to the active TeamSite node. OpenDeploy runs constantly on all nodes.

Part 1 - Is it possible to create deployment configuration files that are localNode Host independent? We would like to manage our deployment configuration files using TeamSite and store them in the content store. We have a workflow created that deploys the config files to the two nodes in the cluster. It defeats the purpose if we have to then go in and change the localNode host value on one of the nodes to reflect that nodes host name. Any ideas? Is what we are trying to do even possible?

Part 2 - We would like to deploy content from our TEST content store to our PROD content store. To do so, we want to use the cluster VIP, which points to the active TeamSite node which is mounted to the floating content store. The problem is...it appears that OD can't resolve the connection to the VIP over port 20014. We have the localNode Host in our odbase.xml file set to the local host name. The ect/hosts file has the entry to allow that host name to resolve to the local IP. the lsof command shows the following:

POWERBROKER-iwovxtapp1# lsof -i TCP:20014
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 21844 root 19u IPv4 0x301d9add840 0t0 TCP iwovxtapp1:20014 (LISTEN)

Any help is greatly appreciated.

Thanks,

Jim

Adam Stoller

Part 1 - Is it possible to create deployment configuration files that are localNode Host independent? We would like to manage our deployment configuration files using TeamSite and store them in the content store. We have a workflow created that deploys the config files to the two nodes in the cluster. It defeats the purpose if we have to then go in and change the localNode host value on one of the nodes to reflect that nodes host name. Any ideas? Is what we are trying to do even possible?

I don't have any ideas about your second question, but with regard to the above - yes.

You basically want to make sure that the Receivers have strictPartnerChecking enabled within the listenerProperties element of your odrcvr.xml - and then you can define the localNode setting in the deployment configuration files to whatever you want (e.g.: "TeamSite") and as long as you have the actual host or IP address configured as an allowedHost (in the same odrcvr.xml previously mentioned) - OD will not attempt to do a string match against the localNode of the sender against the allowedHosts on the receiver.

Theoretically you should be able to do this without enabling the strictPartnerChecking (by default, I believe it's supposed to be the 2nd or 3rd match tested when a connection is made - see page 85 of your OD Reference manual for more information) - but I think it's cleaner to be explicit about what you're doing there.