Solaris Cluster 3.3 on VMware ESX 4.1

Question

Hi there,
I am trying to setup Solaris Cluster 3.3 on Vmware ESX 4.1
My first question is: Is there anyone out there setted up Solaris Cluster on vmware accross boxes?
My tools:
Solaris 10 U9 x64
Solaris Cluster 3.3
Vmware ESX 4.1
HP DL 380 G7
HP P2000 Fibre Channel Storage
When I try to setup cluster, just next next next, it completes successfully. It reboots the second node first and then the itself.
After second node comes up on login screen, ping stops after 5 sec. Same either nodes!
I am trying to understand why it does that? I did every possibility to complete this job. Setted up quorum as RDM from VMware. Solaris has direct access to quorum disk now.
I am new to Solaris and I am having the errors below. If someone would like to help me it will be much appreciated!
Please explain me in more details i am new bee in solaris :) Thanks!
I need help especially on error: /proc fails to mount periodically during reboots.
Here is the error messages. Is there any one out there setted up Solaris Cluster on ESX 4.1 ?
* cluster check (ver 1.0)
Report Date: 2011.02.28 at 16.04.46 EET
2011.02.28 at 14.04.46 GMT
Command run on host:
39bc6e2d- sun1
Checks run on nodes:
sun1
Unique Checks: 5
===========================================================================
* Summary of Single Node Check Results for sun1
===========================================================================
Checks Considered: 5
Results by Status
Violated : 0
Insufficient Data : 0
Execution Error : 0
Unknown Status : 0
Information Only : 0
Not Applicable : 2
Passed : 3
Violations by Severity
Critical : 0
High : 0
Moderate : 0
Low : 0
* Details for 2 Not Applicable Checks on sun1
* Check ID: S6708606 ***
* Severity: Moderate
* Problem Statement: Multiple network interfaces on a single subnet have the same MAC address.
* Applicability: Scan output of '/usr/sbin/ifconfig -a' for more than one interface with an 'ether' line. Check does not apply if zero or only one ether line.
* Check ID: S6708496 ***
* Severity: Moderate
* Problem Statement: Cluster node (3.1 or later) OpenBoot Prom (OBP) has local-mac-address? variable set to 'false'.
* Applicability: Applicable to SPARC architecture only.
* Details for 3 Passed Checks on sun1
* Check ID: S6708605 ***
* Severity: Critical
* Problem Statement: The /dev/rmt directory is missing.
* Check ID: S6708638 ***
* Severity: Moderate
* Problem Statement: Node has insufficient physical memory.
* Check ID: S6708642 ***
* Severity: Critical
* Problem Statement: /proc fails to mount periodically during reboots.
===========================================================================
* End of Report 2011.02.28 at 16.04.46 EET
===========================================================================
Edited by: user13603929 on 28-Feb-2011 22:22
Edited by: user13603929 on 28-Feb-2011 22:24
Note: Please ignore memory error I have installed 5GB memory and it says it requires min 1 GB! i think it is a bug!
Edited by: user13603929 on 28-Feb-2011 22:25

Answer 1

@TimRead
Hi, thanks for reply,
I have already followed the steps also on your links but no joy on this.
What i noticed here is cluster seems to be buggy. Because i have tried to install cluster 3.3 on physical hardware and it gave me excat same error messages! interesting isnt it?
Please see errors below that I got from on top of VMware and also on Solaris Physical hardware installation:
ERROR1:
Comment: I have installed different memories all the time. It keeps sayying that silly error.
problem_statement : *Node has insufficient physical memory.
<analysis>5120 MB of memory is installed on this node.The current release of Solaris Cluster requires a minimum of 1024 MB of physical memory in each node. Additional memory required for various Data Services.</analysis>
<recommendations>Add enough memory to this node to bring its physical memory up to the minimum required level.
ERROR2
Comment: Despite rmt directory is there I gor error below on cluster check
<problem_statement>The /dev/rmt directory is missing.
<analysis>The /dev/rmt directory is missing on this Solaris Cluster node. The current implementation of scdidadm(1M) relies on the existence of /dev/rmt to successfully execute 'scdidadm -r'. The /dev/rmt directory is created by Solaris regardless of the existence of the actual nderlying devices. The expectation is that the user will never delete this directory. During a reconfiguration reboot to add new disk devices, if /dev/rmt is missing scdidadm will not create the new devices and will exit with the following error: 'ERR in discover_paths : Cannot walk /dev/rmt' The absence of /dev/rmt might prevent a failover to this node and result in a cluster outage. See BugIDs 4368956 and 4783135 for more details.</analysis>
ERROR3
Comment: All Nics have different MAC address though, also I have done what it suggests me. No joy here as well!
<problem_statement>Cluster node (3.1 or later) OpenBoot Prom (OBP) has local-mac-address? variable set to 'false'.
<analysis>The local-mac-address? variable must be set to 'true.' Proper operation of the public networks depends on each interface having a different MAC address.</analysis>
<recommendations>Change the local-mac-address? variable to true: 1) From the OBP (ok> prompt): ok> setenv local-mac-address? true ok> reset 2) Or as root: # /usr/sbin/eeprom local-mac-address?=true # init 0 ok> reset</recommendations>
ERROR4
Comment: No comment on this, i have done what it says no joy...
<problem_statement>/proc fails to mount periodically during reboots.
<analysis>Something is trying to access /proc before it is normally mounted during the boot process. This can cause /proc not to mount. If /proc isn't mounted, some Solaris Cluster daemons might fail on startup, which can cause the node to panic. The following lines were found:</analysis>
Thanks!