cluster node hangs when another node shutdown

[albert000]

Dear:

Both HWNOD1 and HWNOD2 can access the quorum disk directly.     

When I boot only HWNOD1 from SAN storage system, then it will enter the following status:

     %PEA0,cluster communication enabled on IP interface, WE0

     %PEA0,successfully initialized with TCP/IP services

     %PEA0,setting socket option failed.

It will always hang on this step until I boot the other node:HWNOD2, then it can enter the system.

I use TCP/IP for these two node to communicate with each other.

Is it wrong?

Looking forward to your reply.

BR

TONG

[Steven Schweda]

> It will always hang on this step until I boot the other node:HWNOD2,
> then it can enter the system.

   That suggests (to me) that the quorum disk is not doing its job.
Previous questions about your quorum disk remain unanswered.

> %PEA0,setting socket option failed.

> I use TCP/IP for these two node to communicate with each other.
>
> Is it wrong?

   I've never used IP for the cluster interconnect, so I know nothing,
but...

   I don't like the "setting socket option failed" message, but if the
cluster works with both nodes up, then the cluster interconnect would
seem to be working properly.

[Steven Schweda]

> > It will always hang on this step until I boot the other node:HWNOD2,
> > then it can enter the system.
>
> That suggests (to me) that the quorum disk is not doing its job.

   I can't remember if I ever used a quorum disk in a cluster, so I know
nothing, but...

   The documentation suggests that "the quorum disk must be mounted by
all disk watchers".  The system (boot) disk is mounted by the boot
procedure, but if the quorum disk is mounted by the normal start-up
scripts (like SYSTARTUP_VMS.COM), then it won't be available until the
system is (mostly) up (_after_ forming or joining the cluster).

   If that's true, then the quorum disk would be useless in _forming_
the cluster; its only value would be in maintaining the quorum when one
of the cluster members _leaves_ the cluster.

   So, the question would be this: After both nodes have been booted
(and are cluster members, and have mounted the quorum disk with its
QUORUM.DAT file), if you shut down one of the cluster members, does the
other cluster member continue to work, or does the cluster lose its
quorum, and freeze the remaining cluster member?

[albert000]

Dear:

     I re-install the 2-nodes with votes=3.

     Then I mount the quorum disk with command: mount /noassist /cluster devname vol_label. The cluster info is as follows;

    +-------------------------------------------------------------------------------
| CLUSTER
+--------+-----------+----------+---------+------------+-------------------+----
| CL_EXP | CL_QUORUM | CL_VOTES | QF_VOTE | CL_MEMBERS | FORMED | LA
+--------+-----------+----------+---------+------------+-------------------+----
| 3       | 2        | 3        | YES     |          2 | 22-SEP-2016 11:40 | 22-
+--------+-----------+----------+---------+------------+-------------------+----

Now I restart any node, the other node can still work well.

Thanks for your help.

BR

TONG

[Steven Schweda]

> I re-install the 2-nodes with votes=3.

   "with votes=3"?  Does that mean one vote (VOTES = 1) for each node,
plus one vote for the cluster disk (QDSKVOTES = 1), so EXPECTED_VOTES =
3?  If not, then what does it mean?

[Volker Halle]

It should be noted, that you don't need to have the QUORUM disk mounted, once the quorum file ([000000]QUORUM.DAT) has been successfully created, but to CREATE the quorum file after the initial cluster configuration, the quorum disk MUST be mounted system-wide on one of the quorum disk watcher nodes at least once (with the cluster up and running without the quorum disk votes, i.e. QF_VOTE=NO)

Volker.