Hi Tirthankar et al,
actually there is no need to touch an internal interface like the
infrastructure file to get this information (I would discourage to
directly touch this file unless absolutely necessary).
The information about the used scsi protocol is available via
# clq show -v
And I think one of the messages he cited is indicating that scsi2 is
currently used.
Btw. if this is an issue for a production system, then while we are
happy to help out - if it is critical and influences business decisions,
I would recommend to David to open an official Case with Sun Service
(provided a service contract exists).
Greets
Thorsten
Tirthankar wrote:
> Check in the /etc/cluster/ccr/infrastructure file what
> version of the scsi protocol is being used for that QD
>
> If you see that its scsi2 and now that you need scs1 3
> I would suggest removed the quorum device. Boot up
> all the 3 nodes and then add the quorum device again
>
> Thanks
> Tirthankar
>
>
>
> On Dec 14, 2007 3:22 PM, ALLEN, David <David.ALLEN at eur.crowncork.com
> <mailto:David.ALLEN at eur.crowncork.com>> wrote:
>
> Further to my last email, some more info for you.
>
> We set up the cluster initially with two machines, each with a single
> fibre card to connect to the disc pack. We then have tried to add the
> third machine, with has a duel fibre card set up for multipathing. Could
> this somehow be the cause of the problems? i.e the intital culster set
> it self up with scsi 2, but the duel fibre card setup needs scsi 3?
>
> Thanks in advance.
>
> David
>
> -----Original Message-----
> From: ha-clusters-discuss-bounces at opensolaris.org
> <mailto:ha-clusters-discuss-bounces at opensolaris.org>
> [mailto:ha-clusters-discuss-bounces at opensolaris.org
> <mailto:ha-clusters-discuss-bounces at opensolaris.org>] On Behalf Of
> Tirthankar
> Sent: 13 December 2007 18:12
> To: ha-clusters-discuss at opensolaris.org
> <mailto:ha-clusters-discuss at opensolaris.org>
> Subject: Re: [ha-clusters-discuss] Establising quorums?
>
> Seems like you are hitting a null pointer dereference in the orb
> invocation code path
>
> I would recommend you do a "scconf -cq reset" as Zoram mentioned.
>
> i.e.
> 1. Boot up the 2 nodes that do not give a problem 2. Run the command
> "scconf -cq reset"
> 3. The boot up the 3rd node that is giving a problem.
>
> See if the node joins without panicking.
>
> If it does, then please send the stack trace ( $C ) output and $<msgbuf
> output
> --
>
> This message posted from opensolaris.org <http://opensolaris.org>
>
> _______________________________________________
> ha-clusters-discuss mailing list
> ha-clusters-discuss at opensolaris.org
> <mailto:ha-clusters-discuss at opensolaris.org>
> http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss
>
> CONFIDENTIALITY NOTICE The information contained in this
> e-mail is intended only for the confidential use of the above
> named recipient. If you are not the intended recipient or person
> responsible for delivering it to the intended recipient, you have
> received this communication in error and must not distribute or
> copy it. Please accept the sender's apologies, notify the sender
> immediately by return e-mail and delete this communication.
> Thank you.
>
>
>
>
> --
>
> Tirthankar
> http://insanityrulz.blogspot.com/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ha-clusters-discuss mailing list
> ha-clusters-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht M?nchen: HRB 161028
Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer
Vorsitzender des Aufsichtsrates: Martin H?ring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy
all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
