> Hi Tundra, > > it's good to hear that you have solved the problem, > but ... > > > I don't know if this is related or not, but the > iSCSI initiator keeps spitting out 'unable to connect > to target' notices. There are two iSCSI targets > defined, each with two paths, so I get a set of 4 > iSCSI notices at a time. I have noticed that all the > nodes get these messages early in the process, but > once each node joins the cluster the notices stop - I > presume this is because the iSCSI starts talking > BEFORE clustering starts, and since iSCSI is talking > over the cluster interconnect paths which don't exist > until clustering startup creates the interconnects, > iSCSI can't reach the targets until later on. Since > each node has a local mirrored zpool as it's rpool to > boot from, I'd prefer if I could tell iSCSI not to > bother looking until later in the process, as it > seems that would both remove the errors and boot > faster, but if that's not causing my problem I'm not > too worried. > > ... could it be that, at the time, you were using the > same initiator node name > (iqn) on the fourth node and one other node? This is > likely to happen if nodes > are cloned.
While it is possible that I had the same IQN in error, it wouldn't be because the nodes were cloned (because they weren't cloned) > > Nils > _______________________________________________ > ha-clusters-discuss mailing list > ha-clusters-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ha-cluste > rs-discuss -- This message posted from opensolaris.org
