Cluster_Authorize question
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 08:37:05 -0400
OK, big problem here...
contents of cluster_authorize.dat is all 0s except for 4 bytes E48851CF
near the top.
MC SYSMAN CONFIG SET CLUSTER/PASSWORD=xxx/GROUP=yyy accesses the file,
but doesn't change the contents. (i.e. I changed the group number and
the only 4 nonzero bytes in the file didn't change).
Is this normal ? Are the contents stored in some deep down hidden
semantics ?
My new alpha can jon the cluster when booting as a satellite. But with
the same cluster_authorize.dat that is located on the boot_server's disk
, the alpha will not join the cluster when it boots on its own disk. No
error messages. And on the cluster, no messages about that node being visible.
The alpha is at 8.2 (alpha) the rest of the cluster is VAX at 7.2.
If it can join the cluster booting 8.2 as a satellite, how come it
couldn't when booting from its own disk ?
MC SYSMAN CONFIG SHOW CLUSTER reveals that group is the same , and so is
the broadcast address.
One item though, not sure if it is important: the alpha is on a switch
(unmanaged) while the rest of the cluster on a on hub (with a link
between the two).
The multicast address is AB-00-04-01-0A-01
(the 0A is the cluster's group).
Would switches know that this is a "broadcast" ethernet address ? If
not, the switch may get confused and not send it to all its ports ?
Would a node that boots via MOP bypass the multicast address mechanism
to establish cluster membership ?
.
- Follow-Ups:
- Re: Cluster_Authorize question
- From: jls
- Re: Cluster_Authorize question
- Prev by Date: Re: Stripeset member logging errors
- Next by Date: VMS 8.2 complaint: screen cleared at login.
- Previous by thread: hobbyist licensing site down / helping out
- Next by thread: Re: Cluster_Authorize question
- Index(es):
Relevant Pages
|