Problem with Multinet cluster service names.

[Malcolm Dunnett]

I can’t get multinet cluster service names to work reliably. It worked
just fine for years in older versions of multinet, but with multinet 5.2
the domain nameserver doesn’t seem to be able to reliably see it. It was
working for a while today but then it quit, eg:

MALVM9> mu nslook vmscluster.mala.bc.ca localhost
Server: LOCALHOST
Address: 127.0.0.1

*** LOCALHOST can't find VMSCLUSTER.MALA.BC.CA: Non-existent host/domain
MALVM9> mu netcon domain show
Connected to NETCONTROL server on "LOCALHOST"
< malvm9.mala.bc.ca Network Control V5.2(10) at Thu 10-Apr-2008 8:49PM-PDT
< Service VMSCLUSTER.MALA.BC.CA:
< Nodename Address Rating
< -------- --------------- ------
< MALVM3 142.25.103.73 169
< MALVM9 142.25.103.71 169
< End of line

The nameserver does not show the translation of vmscluster even though
the mu netcon domain show displays that the two hosts are both
contributing entries.

The servers are Alphaservers running VMS 8.3

Anyone else seen this problem. Anyone successfully using Multinet
cluster service names with Multinet 5.2?

[Jim]

I can't get multinet cluster service names to work reliably. It worked
just fine for years in older versions of multinet, but with multinet 5.2
the domain nameserver doesn't seem to be able to reliably see it. It was
MALVM9> mu nslook vmscluster.mala.bc.ca localhost
Server: LOCALHOST
Address: 127.0.0.1
*** LOCALHOST can't find VMSCLUSTER.MALA.BC.CA: Non-existent host/domain
MALVM9> mu netcon domain show
Connected to NETCONTROL server on "LOCALHOST"
< malvm9.mala.bc.ca Network Control V5.2(10) at Thu 10-Apr-2008 8:49PM-PDT
< Nodename Address Rating
< -------- --------------- ------
< MALVM3 142.25.103.73 169
< MALVM9 142.25.103.71 169
< End of line
The nameserver does not show the translation of vmscluster even though
the mu netcon domain show displays that the two hosts are both
contributing entries.
The servers are Alphaservers running VMS 8.3
Anyone else seen this problem. Anyone successfully using Multinet
cluster service names with Multinet 5.2?

I have just now set up an VMS 8.3 I64 cluster to use DNS load
balancing with the cluster service name and experience the same issue
that you do.

[Malcolm Dunnett]

Post by Jim

Post by Malcolm Dunnett
Anyone else seen this problem. Anyone successfully using Multinet
cluster service names with Multinet 5.2?

I have just now set up an VMS 8.3 I64 cluster to use DNS load
balancing with the cluster service name and experience the same issue
that you do.

Process Software has confirmed this is a bug. They've opened a defect
report (DE 10509).