Ashutosh Tripathi pisze: > So that seem to work find. Sure.. the status of the adapters > is faulted: > >>>> node1:xnf2 node2:xnf2 faulted >>>> node1:xnf1 node2:xnf1 faulted > > Which tells me that while the heartbeats are flowing, > perhaps the TCP traffic is having trouble getting across, we > can look at that, but perhaps your basic problem is: > >>> Btw, I can ping node2 via interconnects from node1. >>> I can't login to node2 neither from console nor via sshd. > > But then you have this output... Perhaps that is not from node2? > >>>> # uname -srvi >>>> SunOS 5.11 snv_104 i86xpv >>>> >>>> # dladm show-link >>>> LINK CLASS MTU STATE OVER It comes from xVM dom0 (this is where 'node2' lives). Sorry for the confusion.
> I am gonna assume that the problem you refer to is that node2 never > gets to the console login prompt and is stuck "somewhere". Right. > Typically, if i see a cluster related hang, it is typically the > cluster nodes waiting for quorum. Here, there is no quorum (node1 > is 1 vote, node2 0 and both are part of the cluster already). > So, it is quite possible that the hang on the node2 is not > directly related to the cluster (indirectly, perhaps it is). > > You might have to dive in a bit deep here, unfortunately. Fortunately ;) > Can you gather kernel buffers for the following components: Sure, but first from 'node1'. Btw, thanks for help. -- Regards, Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: mail_ohac_xvm URL: <http://mail.opensolaris.org/pipermail/ha-clusters-discuss/attachments/20090112/40b758bf/attachment.ksh>
