Server Migration

Question

I'm having a problem setfing up migration on my Managed Servers on Welbogic 9.2 mp2. First, My problem.
When I try to manually migrate ManagedServer1 from MachineA to MachineB:
Nodemanger shutdowns ManagedServer1
Nodemanager removes the interface with the floating IP (so far so good)
(here is where the problem starts)
Nodemanager brings up the interface back on MachineA
Nodemanager starts ManagesServer1 on MachineA (all this is suppose to happen on MachineB).
This doesn't help me if it migrates it to the same machine!!!
I quick overview of how things are set up.
1) I have two machines, MachineA and MachineB running Solaris 10
2) I have the admin server running on MachineA listening on the static ip of 139 and ManagedServer1 listening on the floating IP of 169 (fyi, don't want give out IP, so I made a number up)
3) I have ManagedServer2 running on MachineB with the floating IP of 170.
4) I created a weblogic user that has ssh trust config between the two machines and has the proper authority to create and bring down an interface.
5) Created 2 Unix machines, Type SSH with the shell command ssh -l legalint -o PasswordAuthentication=no -p %P %H /opt/bea/weblogic92/common/bin/wlscontrol.sh -d %D -n /legalint/mtdom/ndmgr -c -f startManagedWebLogic.sh -s %S %C
6) Network Time Protocal Config is set
7) Lease database schema is created with corresponding data source and has two tables ACTIVE and ACTIVE_MT
8) Server migration progerties configured: cluster datasource is set (In my directions it tells me to leave the Canidate machines blank). Managed servers auto migration set to true and primary and back-up machine set and auto-restart set to true.
Any help is appreciated.
Tom.

Answer 1

The best way to deal with certificates and FQDN's in ZESM is to use commercial issued certificates or from the company's internal CA. Don't use the built-in product self-signed certificates under any reason for production deployments. The reason behind that, is that the internal ZESM certificate has its private key marked as non-exportable. So you'll not be able to export it from one server and move to another.
For the server FQDN, create an A or Alias record in DNS to something like: "zesm.company.com", and point it to the actual ZESM server, that way, once you need to move all users from server, all that you need to do is to import the commercial certificate and point the DNS record to the new server IP Address.
I did a couple of deployments in that way, with no issues.
Hope this helps.
>>>
From: mauro vaccari<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 1/19/2010 7:36 AM
Subject: Server Migration
Hi,
planning the upgrade to the imminent release of ZESM 4.1 we would like
to reinstall the server because it has undergone many installations.
For security reason and for don't stop production we want to install
ZESM 4.1 in a new server with the same ip and name of the actual then we
want try It in a test VLAN.
My question is:
when we want to pass the new server in production or before ZESM
instalation could we migrate the IIS certificate from the old server to
new one? so the client should not be involved.
Thank you for help
mauro_vaccari
mauro_vaccari's Profile: http://forums.novell.com/member.php?userid=16902
View this thread: http://forums.novell.com/showthread.php?t=398639