Solaris

ipmp: did you use link or probe based? i'm using link based on internal networks. four adapters - e1000g0 to g3.

did you have to configure the network on the vbox host itself?

what instructions did you follow?

i've done probe based ipmp. same adapters for me. e1000g0-3. and i use a "internal only" network for public and clusterinterconnect. so no traffic to the outside world.

what instructions do you mean?

I wonder if it's because i am using link based?

Can you show me your /etc/hostname.e1000g0 and g1 files please (assuming they are your two network ips)?

In the cluster set up; do you say you use switches or (like) crossover for e1000g2 and g3 (assuming they are your cluster transport private network adapters)?


wondered if you followed any specific set up e.g. online guide or whatever. I havent been on a cluster course, i've had to read all about it using google etc. didnt happen to write any notes on it did you?

I have two nodes; global0 and global1. I run the scinstall from global1. I dont understand why, after global0 reboots it just sits there saying "waiting for global0 to reboot..."

I do hope you dont mind me picking your brains and maybe asking newbie questions about clustering but i'm going to go mad if i cant get two nodes to cluster.

Solaris Cluster on a laptop using VirtualBox, iSCSI and a quorum server : JET Stream should help you .. but its straight fwd once you understand and figure out which interface to select for cluster interconnects.

yeah i've been reading that one, amongst other.

i think though it might be because i am using link based ipmp not probe, as all the other guides say they use probe.

i could still use:

/etc/hosts
/etc/hostname.e1000g*
anyother network files that might be relivant.

did you change the address of the virtualbox host itself? is it necessary to have it on the same subnet as the two virtual servers?

Saying all that, there is nothing wrong with the comms during the initial part of the scinstall. It would appear that the VM that gets rebooted first, simply doesnt contact the scinstall server when it comes back up.

I am wondering, perhaps i dont have the iscsi set up correctly? although i can do a format on it from the remote server. does the remote server (the first to reboot) rely on there being a quorum available?

damn i am stuck.

yes, you need a quorum!

my setup is:
- one admin node (also solaris)
- two cluster nodes

on the admin node is clustersoftware installed (cluster console and quorum server).

i'm just setting up an admin node now.

did you make the admin node zfs? or ufs and then create a zpool from files? what did you do?