Another my reference.

Scenario : OES Linux running on ESX vm need to join existing tree

• Install SLES + OES
• Pointing ESX Time Server to Master DS
• Make sure edir database, sync & report status OK
• Run $ntpq -p on new sles
• setup slp if possible
• Configure eDir and time server pointing to Master DS
• Configure SLP or scp from existing OES linux server
• Add new server to replica i.e RW
• Verify database, timesync, replica status OK

Note: Failed to point ESX time server to Master DS can caused time drift on OES vm.

Just for my reference :

Scenario : One of OES linux server need to be remove from eDir

• Check Time Sync report $ndsrepair -T
• Check Replica Status $ndsrepair -E
• Everything fine, remove the server from replica $ndsrepair -P -Ad
• Remove Server from edir & uninstall edir $ndsconfig -rm -a admin.novell
• Clean up server object in ConsoleOne
• Server-to-server sync with $ndstrace
• Replica sync status with $ndstrace
• Schema Sync with $ndstrace

Just want to share this two issues while installing ESX 4.0 onto M2 server :
1- Successfully installed ESX 4.0 but unable to boot it when there is external storage attached to HBA

Workaround -> Add legacy boot

2- ESX installed unable to detect M2 with ServerRAID SAS/SATA M5014 controller

Workaround -> Buy another supported RAID card

So, need extra carefull with this new hardware when you plan to install ESX on it.

Suppose to start with 2x ESX + 1x vCenter installation this morning but end up, I have to wait till evening because hardware vendor forgot to get dvd/cdrom for my customer’s IBM x3650 M2. What I suppose to do now? damn boring..