topic Re: Monitor Cluster command in Operating System - OpenVMS

Monitor Cluster command

Robert Jacobs — Mon, 19 Sep 2005 12:34:33 GMT

Can you / how can I use the $monitor cluster command if there is no decnet running. I have a two not cluster and get the no connect error message. I am running just TCP/IP services.

I know very little about this VPM Software.
Error message below

%MONITOR-I-ESTABCON, establishing connection to remote node(s)...
GS160A Sep 19 10:43:46 2005 <| %VPM-W-NOCONNECT, Unable to connect to remote node GS160B
GS160A Sep 19 10:43:47 2005 <| -MONITOR-W-NODEINIERR, error during node initialization
GS160A Sep 19 10:43:48 2005 <| %MONITOR-I-CONT, continuing....

Thank you

Robert J.

Re: Monitor Cluster command

Jan van den Ende — Mon, 19 Sep 2005 12:37:44 GMT

Robert,

What version of VMS?

Proost.

Have one on me.

jpe

Re: Monitor Cluster command

Veli Körkkö — Mon, 19 Sep 2005 12:55:34 GMT

$ sear sys$startup:systartup_vms.template vpm/win=(3,0)

$!
$! Uncomment the following command to have Monitor run with TCP/IP.
$!
$!$ @SYS$STARTUP:VPM$STARTUP.COM

so, there it is. Just run the needed startup procedure. And uncomment it in your SYSTARTUP_VMS.COM

_veli

Re: Monitor Cluster command

Robert Jacobs — Mon, 19 Sep 2005 15:49:44 GMT

I am running OpenVMS 7.3-2 I have started the VPM s.w. on both nodes and still get the error The VPM server process is running and show up at the end of the show system command below is the error shown from a console works log files

********************************************
%MONITOR-I-ESTABCON, establishing connection to remote node(s)...
CONSOL Sep 19 13:56:58 2005 <| %VPM-W-NOCONNECT, Unable to connect to remote node GS160A
CONSOL Sep 19 13:56:58 2005 <| -MONITOR-W-NODEINIERR, error during node initialization
CONSOL Sep 19 13:56:59 2005 <| %MONITOR-I-CONT, continuing....

********************************************
$ monitor cluster
GS160A Sep 19 14:00:34 2005 <|
GS160A Sep 19 14:00:34 2005 <| %MONITOR-I-ESTABCON, establishing connection to remote node(s)...
GS160A Sep 19 14:00:34 2005 <| %VPM-W-NOCONNECT, Unable to connect to remote node GS160B
GS160A Sep 19 14:00:34 2005 <| -MONITOR-W-NODEINIERR, error during node initialization
GS160A Sep 19 14:00:35 2005 <| %MONITOR-I-CONT, continuing

********************************************
Any clues here?

Thank You

Re: Monitor Cluster command

John Gillings — Mon, 19 Sep 2005 22:22:26 GMT

Robert,

You need to make sure the host names and addresses are correct. What does:

$ TCPIP SHOW HOST GS160B

return? You'll need to have aliases matching the SCSNODE name for each node in the cluster.

Re: Monitor Cluster command

Colin Butcher — Tue, 20 Sep 2005 03:04:41 GMT

Looks as if you need to set up the proxy accounts for access to the other node. Regrettably MONITOR uses DECnet or TCPIP rather than a lower-level protocol, so it's task to task communication - and that needs a proxy entry to establish the connection.

For example:

UAF> ADD/PROXY :: [/DEFAULT]

I've never used the TCPIP only method, but I would expect you to have to set up TCPIP proxies in a similar manner within the separate TCPIP proxy database.