Upgrade OES2 to OES11 Cluster

Hi all,
we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
version running on OES11SP1. The cluster provides GroupWise, File and iPrint
Services and is connected via QLogic iSCSI HBA to our SAN.
What would you recommend how the Upgrade could be done without major
trouble?
Thanks in advance
Alex

On 16.02.2014 14:54, Alexander Lorenz wrote:
> Hi all,
>
> we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
> version running on OES11SP1. The cluster provides GroupWise, File and iPrint
> Services and is connected via QLogic iSCSI HBA to our SAN.
>
> What would you recommend how the Upgrade could be done without major
> trouble?
There should be no trouble at all. Move all ressources to one Node, then
update the free node to OES11 as documented, move ressources to the
upgraded server, test, then do the same with the other node. But I
suggest use SP2 instead of SP1. There's really not much special on a
cluster node vs a "normal" server.
One thing you may need to check into is iPrint. If it's fully clustered,
your weg data of iPrint will reside on a clustered volume, which however
will never be available on the node that's currently upgraded, so you
likely end up with the old iPrint stuff there. Yuo may want to re-run
the iprint cluster setup script again (or if you feel able to, copy the
local iPrint data over to the cluster volume).
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

Similar Messages

Rolling Cluster Upgrade (OES2 to OES11) - GPT partition

We've got an OES2 SP3 cluster that we'll be rolling cluster upgrading to OES11 SP2.
We are currently at max capacity for several of the NSS volumes (2 TB).
If I'm reading/interpreting the OES11 SP2 docs correctly:
AFTER the cluster upgrade is complete, the only way I can get to larger volumes will be to create new LUNs on the SAN and intialize those with GPT. Then I could do the NSS Pool Move feature to get the existing 2 TB volumes to the larger setup?
Is that correct?
Or is there a better way that doesnt' require massive downtime?

Originally Posted by konecnya
In article <[email protected]>, Kjhurni wrote:
> We are currently at max capacity for several of the NSS volumes (2 TB).
I was on the understanding that you could bind multiple partitions to
create NSS volumes up to 8TB. But I'd be hesitant to do that for a
clustered volume as well.
> I could do the NSS Pool Move feature to get the existing 2 TB
> volumes to the larger setup?
> Or is there a better way that doesnt' require massive downtime?
My first thought is the migration wizard so that the bulk of the copy can
be done while system is live but in the quieter times. Then the final
update with down time should be much faster.
But then do you really need down time for the Pool Move feature?
https://www.novell.com/documentation...a/bwtebhm.html
Certainly indicates it can be done live on a cluster with the move
process being cluster aware.
Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
Migration = pew pew (re-doing IP's/etc and copying 4 TB of data is ugly especially when it's lots of tiny stuff).
haha
Anyway, when I asked about a better way that doesn't require massive downtime what I meant was:
Is there a better way vs. Pool Move that doesn't require massive downtime (in other words, the "other way" having the massive downtime, not the Pool Move).
Choice A = Pool Move = No downtime
But let's say that's not a good option (for whatever reason) and someone says use Choice B. But Choice B ends up requiring downtime (like the data copy option).
I just didn't know if Pool Move required that you create the partition ahead of time (so you can choose GPT) or if it kinda did it all for you on the fly (I'll have to read up when I get to that point).
I'm not terribly keep on having multiple DOS partitions, although that technically would work. Just always scares me. It's just temporary for the next 8 months anyway while we migrate to NAS from OES, but I'm running out of space and am on an unsupported OS anyway.

Needing to migrate/upgrade NSM 3.02.76 from OES2 to OES11

Currently running on OES2 SP2a server. NSM version 3.0.2.76
Need to upgrade to new server. New server is OES11 SP1. Also would like to upgrade to latest NSM version.
Do I need to upgrade in place now and then move to new server? Can OES2 SP2a even run NSM 3.1?
Looked at documentation some, but don't see clear process on moving NSM to new server.
I didn't find any tips in the Discussion forum.
You've given me tips in the past and they have always worked great.
Can you point me to documentation and give best practices in making this upgrade and change.
Any assistance is greatly appreciated.
thanks,
Lin

For the benefit of others doing the same, I'd migrate then upgrade. Here's how I migrated Storage Manager Engine from OES2 to OES11:
1 - Unload old Engine and disable from starting on server boot.
2 - Install NSM Engine on new server, open firewall port 3009, and configure the engine using nsmengine-config, but don't start the engine.
3 - On the new server, rename /var/opt/novell/storagemanager/engine/data to data-original
4 - Copy /var/opt/novell/storagemanager/engine/data from old server to new server, then fire-up the new Engine
5 - Run NSMAdmin against the new server and next your way through the wizard. I had to create a new NSMProxy user, but you can use the existing NSMAdmins group.
6 - Reconfigure Event and Agent servers to point to the new Engine.
Regards,
Anthony

Best plan for this scenario (migrate oes2 to oes11)

Hi there!
I would like to ask you guys the best plan for migrate a few servers that I have
in oes2 to oes11.
I have four servers in oes2sp2/sp3, these servers have a few NSS
volumes over NCS. Also I have my iPrint service on two machines,
also using NCS. I have one cluster between two machines and
other cluster between the other two machines. For exmaple,
machine1 and machine2, three NSS volumes (every NSS volume is a cluster
resource) and other resource in the same cluster for iPrint. Cluster: CL1
machine3 and machine4, one NSS volume (for other people in the company)
in other cluster. Cluster: CL2. In this cluster only have a NSS volume/resource.
Machine1/3 are physical, machine2/4 are virtual (vmware)
My CA is in other server that I will migrate after a while. So, It seems that there is
no problem with the certificate. Machine1 and machine3 are a replica for the eDir in
my organization.
My plan: I have deployed two virtual machines and one physical with oes11sp1 and sles11sp2.
I think that the best plan is migrate with migration tool iPrint first, like a cluster resource,
and NSS volumes, and after that, make a transfer ID (like a different project)
For machine1/3, move NSS volumes and after, make a transfer ID.
Is this correct? I dont know If I have to delete the current clusters (cl1 and cl2) and
create new ones, after that, create every resource as It was on the old ones.
thank you so much !
Antonio.

Originally Posted by kjhurni
This is just my opinion, of course, but:
If you don't want to have to migrate your NSS data and keep the same server names/IP/s and cluster load scripts, then I believe a Rolling Cluster Upgrade is a good way to go.
If you look in my signature, there's a link to my OES2 guides. Somewhere there is one that I did for our Rolling Cluster Upgrade.
If all you have is NSS and iPrint, then you only need to use the miggui (migration utility) for iPrint--or so I think (I do have to followup on this one as I vaguely recall I asked this a while back and there may have been a way to do this without migrating stuff again).
But your NSS data will simply "re-mount" on the OES11 nodes and you'll be fine (so that's why I like the rolling cluster upgrades).
Let me double-check on the OES2 -> OES11 cluster option with iPrint.
--Kevin
Thank you Kevin for your answer.
Finally, I think Im going to proceed using transfer ID on my servers that Im only using NSS over NCS (I only have two machines with one NSS volume)
because it seems that its a good option. I would like to keep old IPs from all the servers, cluster and resources if possible. So, testing this
migration on my test environment it seems that it works fine:
- I use miggui for transfer id between all the machines: physical -> physical and virtual -> virtual. eDirectory assumes new hostname, IP, etc.
the only task "out of the box" is that I have to delete the cluster and regenerate (reconfigure NCS on the new servers) but its pretty easy. This way
I have the two old ips from the older machines and all the ips from the cluster and the cluster resources also. I think that its the best plan.
For the other two machines that has 4 nss volumes and iPrint I must think about a plan. But with those, Im going to proceed this way. I hope
I have chosen a good plan!
thank you so much all for your answers / advices

Manage OES11 Cluster Services

Hello to all!
I've just a "big" problem. I have to manage 3 OES-Cluster Nodes. 2 2-Node-Clusters on OES 2 SP3 and 1 4-Node-Cluster on OES 11. The master - where the iManager is installed - is an OES 2 SP3, too.
When I start the iManager, it's no problem to manage everything on the OES 2-Clusters. If I choose the OES 11-Cluster, I'll get errors and the iManager stops working (the frontend).
I've searched the internet for information; so I can say, it's not the TID with the sysctl-settings.
Does anyone have any idea?
Hans-Christian Wssner

Originally Posted by hwoess
Hello to all!
I've just a "big" problem. I have to manage 3 OES-Cluster Nodes. 2 2-Node-Clusters on OES 2 SP3 and 1 4-Node-Cluster on OES 11. The master - where the iManager is installed - is an OES 2 SP3, too.
When I start the iManager, it's no problem to manage everything on the OES 2-Clusters. If I choose the OES 11-Cluster, I'll get errors and the iManager stops working (the frontend).
I've searched the internet for information; so I can say, it's not the TID with the sysctl-settings.
Does anyone have any idea?
Hans-Christian Wssner
Use iManager on one of the OES11 servers to manage the OES11 cluster? (I'm just saying to try that).
I don't know off the top of my head if the OES11 iMan/cluster stuff can manage both cluster versions. I believe OES11 does not use cimom to manage clustering anymore (sfbcd or something like that now?)

Miggi tool, issue migrating OES2 to OES11

I have had this issue at three consecutive sites of late. All in the process of doing transfer id of OES2sp3 to OES11sp1. Each server also has been a DNS/DHCP server as well. I am basically shutting down those services beforehand, and doing the transfer id. All prerequisites have been done beforehand, and the pre checks and health checks pass fine. The process hangs all three times on the last part on the LUM transfer. It simplys hangs on the process and want finish. I actually opened an SR on one of the boxes the first time and Novell had me kill the process to let it finish. Problem is that is fouls up the LDAP and SSL certs and all of it has to be done manually afterwards. If this was one site I would let it ride, but since I have had three separate customers who I ran into this issue on each one makes me feel something else is going on. Now, this is the first times I have done transfer id going to OES11sp1. I have done many going from NetWare and OES2 to OES11, so not sure if issue in OES11sp1?? Anyway, just thought I would see if anyone else had run into this issue. I have more to do this year so would like to know what is causing this issue.

Looks like from the SR, it has multiple issues. First the server has issues with certificates and post recreation it went through and next is the nam commands were failing.
My suggestion is verify the nam preferred-server on the target server before TransferID is accessible or not and if not point to a proper ldap server in the tree.
Also make sure that you have patched the server to the latest and the certificates of the server and as well as tree are valid.
If by any chance TransferID UI is closed for any reason, you can execute the remaining TransferID steps using command-lines documented in the guide.
-Ramesh
>>> jlewter<[email protected]> 08/12/2013 08:06 PM >>>
SR was 10847842383
Here is the migration log:
2013-07-30 15:21:50,495 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 15:21:50,495 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 15:21:50,496 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 15:21:50,599 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 15:21:50,600 INFO - ServerIDSwap:ndscheck:
2013-07-30 15:21:50,600 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 15:21:50,600 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 15:21:50,603 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:50:37,147 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:56:46,871 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:namconfig:/etc/nam.conf
file exists. Moving it to /etc/nam.conf.migsave
2013-07-30 16:56:46,887 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:57:39,239 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:57:56,595 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Starting to
execute NDSRepair command
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndsrepair -U
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:No log messages willbe updated during the execution
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:04:34,314 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:04:34,447 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:04:34,448 INFO - ServerIDSwap:ndsconfig:Executing
Command: /opt/novell/eDirectory/bin/ndsconfig add -m sas -a
"admin.chatham" -w env:ADM_PASSWD --config-file
/etc/opt/novell/eDirectory/conf/nds.conf
2013-07-30 17:04:55,463 INFO - ServerIDSwap:LUM Repair:ndsconfig add
-m sas returned...
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:11:06,175 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:11:06,315 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
CN=utility.chathamhall.org, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
OU=Organizational CA, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 17:11:07,519 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 17:11:07,616 INFO - ServerIDSwap:ndscheck:
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:ExecutingCommand: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 17:17:25,527 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
Here is part from serverswap log:
2013-07-30 15:21:50,495 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 15:21:50,495 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 15:21:50,496 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 15:21:50,599 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 15:21:50,600 INFO - ServerIDSwap:ndscheck:
2013-07-30 15:21:50,600 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 15:21:50,600 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 15:21:50,603 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:50:37,147 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:56:46,871 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:namconfig:/etc/nam.conf
file exists. Moving it to /etc/nam.conf.migsave
2013-07-30 16:56:46,887 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:57:39,239 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:57:56,595 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Starting to
execute NDSRepair command
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndsrepair -U
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:04:34,314 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:04:34,447 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:04:34,448 INFO - ServerIDSwap:ndsconfig:Executing
Command: /opt/novell/eDirectory/bin/ndsconfig add -m sas -a
"admin.chatham" -w env:ADM_PASSWD --config-file
/etc/opt/novell/eDirectory/conf/nds.conf
2013-07-30 17:04:55,463 INFO - ServerIDSwap:LUM Repair:ndsconfig add
-m sas returned...
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:11:06,175 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:11:06,315 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
CN=utility.chathamhall.org, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
OU=Organizational CA, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 17:11:07,519 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 17:11:07,616 INFO - ServerIDSwap:ndscheck:
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 17:17:25,527 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
jlewter
jlewter's Profile: https://forums.novell.com/member.php?userid=14321
View this thread: https://forums.novell.com/showthread.php?t=468831

DST issues? For OES2 to OES11 upgrade?

Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php?userid=75037
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

Originally Posted by konecnya
Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
View Profile: konecnya - Novell Forums
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
We just went through a round of upgrades from OES2 SP3 (physical) with and without DST to OES11/SP1 on VMware
Now, given your particular setup, I'd think you could be fine with moving the disks. In our case, we needed to do ID transfers, and that could still be done. Setup your target OES11 SP1 VM, do your iPrint, DHCP, etc. migrate them (just not the file services). Do the ID transfer. Power off source VM. "move" the NSS disks (I'm ASSUMING the NSS disks are separate VMware virtual hard disks) to the new OES11 box and voila.
The only gotcha that I can think of:
I BELIEVE that if you stored the disks with the virtual machine (default I believe), you have to be VERY VERY careful to NOT "delete from disk" when you remove the OES2 Guest, as I think it'll delete the entire underlying directory which is now where your disks are
In other words, if you SCP or something to the ESXi host and look at the directory/file structure it'll be something like:
\OES2-Guest\bunch of .vmdk files
\OES11-Gust\bunch of .vmdk files
When you "move" the virtual disks from OES2-Guest to OES11-Guest, it's just pointing to the:
\OES2-Guest\nssdisk.vmdk files
You could manually move them around I believe if you want to maintain the proper directory structure.
Personally that would probably be the biggest time saver for you.
Otherwise you COULD migrate the file systems with DST but there's some scenarios/caveats involved with that.
Let me know if you choose the route to actually migrate the DST file systems and I'll explain further.
But, if it were me, and I had them on VMware, I'd just "move" the disks around.

OES2 to OES11 (upgrade or migrate?)

GW 2012 happily working on OES 2 SP3
Obviously there is a need to upgrade to OES 11
What is easier, upgrade with bootable media or migration?
If migration how does one move GW stuff to new server?
Seb

Originally Posted by Jose
Starting from an OES2 and GW2012 server in VMWare, is it better to
upgrade to GW2012 SP1 before or after the upgrade to OES11?
No, no update to the GW SP1 code is needed, you are already running 2012 code. So there are no upgrade steps here for GroupWise, just a move.
Originally Posted by Jose
For the migration to the new server, it seems you install OES11 and GW
and then bring that OS disk into the "old" OES2 server, is that correct?
Yes, that's about it.... but also, in my setups the OES2 OS disk is a separate disk from the data disk.
After first removing the original OES2 from the tree, the OES11 disk gets attached and set as first boot disk, if the OES2 OS disk is seperate... I leave it out of the new configuration.
Then start the OES11 server - which has all the needed elements but has not been configured yet (in other words: has not been added to the tree), set server name and ip equal to the one used for the OES2 server and configure eDir and NSS services. (I always first configure eDir and NSS services... make sure that's working, and then add any other OES services... *if needed*).
As the GroupWise install stuff and agents are already in there, all that is needed is to copy the GroupWise data to a new volume (or reuse the original volume, which saves the time needed to copy over the files), reconfigure the agents as needed and start them up.
Path changes on the Linux server (like when moving the GroupWise data from an ext3 mounted partition to an NSS volume, which by default has it's mount in /media/nss/..), that can easily be handled by using a symlink (symbolic link) to have the old "path" point to the new one on the NSS volume (e.g. #ln -a [/oldpath] [/media/nss/[NSS volume]/newpath]).
This is usually not needed, as you will be supplying the new agent dib paths during configuration of them anyway. It can ease things though when old paths are causing issues with some bits.
Hope that clarifies a little more.
Cheers,
Willem

DHCP on OES11 Cluster

Hello,
I have some problems to get DHCP Service running in a Cluster Evironment (OES11 SP1, NSS Volume). The Ressource is up and running, but the DHCP Service wont load.
LDAPS session successfully enabled to 10.0.181.36:636
Error: Cannot find LDAP entry matching (&(objectClass=dhcpServer)(cn=DHCP_CLUSTER-DNSDHCP-SERVER))
Configuration file errors encountered -- exiting
The standard command rcnovell-dhcp start did work. So it looks like the rights or seomthing else is missing on the cluster volume /media/nssDHCP...
Maybe I am misunderstanding the doc as well. It states in the DHCP Linux Guide:
8.3.3. hot wo use a different user - it states that it would use the dhcpd user , but no such user was created. Do I need to create it manually?
Thanks for your help!
Regards Jrgen

Hi,
If I recall correctly from my setup, I had to create a user and LUM enable it, and match the UID to the local account.
See here: http://www.novell.com/documentation/...a/bbe81cc.html
Let us know how it goes.
Cheers,

Easy way to upgrade a one-node cluster?

Hi all...
I have a one-node cluster running SQL Server. I would like to upgrade the O/S from W2008R2 to W2012R2. Unfortunately, the Compatibility report tells me that it won't upgrade because it is a member of a cluster.
I understand that if it is a member of a two+ node cluster that it won't upgrade, but I don't understand why I can't do it on a single-node cluster.
Is there a work-around for this? I don't want to start redirecting clients to a different cluster name / ip address.
Thanks!

Why even have a one-node cluster for anything but testing purposes?
Why not create another server with the name of your cluster and set it up to serve out the SQL database. Or, if you want to do it properly, get two nodes and make the cluster and keep the cluster name the same. Those are two work arounds.
There is no upgrade in place for what you want to do.
. : | : . : | : . tim

Upgrade to 11R2 Win Cluster Only?

Hi,
i have seen with new version 11R2 the approch of the installation have change. Now the cluster is part of the Grid upgrade package.
My rac installation is a clusteware 1.1.0.7 and my rdbms is a 10.2.0.3 under Window 2003 sp2.
I there a way i can upgrade my cluster in these step (like in older version)
1- Upgrade cluster only (or cluster and asm)
2- Upgrade Database and ASM
3- Upgrade GRID at the end (because i would like to upgrade all my GRID agents and server at the same time).
I have check the installation doc. and i did not fine a way to do these step in the order i specify.
Thanks

download the document you indicate me in the answer.
Great document, but i still have my question unanswered after i bass thru.
Every time i try to upgrade my cluster the OUI force me to upgrade my GRID (or new installation) before i can upgrade my cluster, ASM and RDBMS.
When i do the step in the OUI, at one point the SCAN ask me for a 'TCP/IP host name lookup', message INS-40718.
Is there a way i can bypass this GRID upgrade (or installation) and go directly to the cluster and ASM upgrade?
If no and i understand the installation documentation, i will have to create 1 new adress for my 3 nodes in the DNS (one alias adress in DNS round robin for the 3 vip adress of my 3 nodes) and added to my HOST file, so the installation can solve it? (at this ponit i'm not shure if the 3 ip adress have to be the 3 vip or 3 new ip adress)
Can you indicate me a example what should i put in my host file for the scan client adress
example:
# public
host1 10.200.0.11
host2 10.200.0.12
host3 10.200.0.13
#vip
host1-vip 10.200.0.21
host2-vip 10.200.0.22
host3-vip 10.200.0.23
#vip
host1-priv 10.200.0.31
host2-priv 10.200.0.32
host3-priv 10.200.0.33
# scna client
host_scan ????????
Thanks
Edited by: Ron_B on 2010-04-13 13:35
Edited by: Ron_B on 2010-04-14 05:46

Upgraded OES2 SP1 to SP2 no GW Webaccess

We just upgraded an OES2 Sp1 server to OES2 Sp2 and things seemed to be fine from the upgrade point of view, but GW webaccess does not work. Apache and Tomcat both are loaded, as are the GW components and we are getting emails, but no web access, using the same link that we did before. I was thinking that something might have changed with apache and how it works with OES2 SP2, instead of how it did with OES2 SP1, any ideas where to look next?

Originally Posted by jmarton
On Tue, 04 May 2010 15:16:03 +0000, dschaldemcs wrote:
> It is GW 7.0.3 or 4 I cannot remember which at this point. All I
> remember was that there was a TID that explained how OES2 SP2 handled
> things with apache. The title was "GW Webaccess and OES2" I will look
> for it as well.
This one?
Installing WebAccess Application on OES2/SLES10SP1+OES2 Add-on
Yes that was the one, it worked for us, and GW Webaccess is working once more. Thank you
Joe Marton
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Can anyone point direction to Upgrade Guides with Veritas Cluster solution?

Hello,
I would like to know if there's specific information about upgrading an R/3 system to ERP 6 which uses veritas cluster solution for high availability on Solaris 10
Are there any guides or considerations I should take into account before starting the upgrade process?
Thank you!
Maria

Hi,
You can check SAP Note 1012486- Important Information on upgrading SAP Systems in HA-Setups.
Thanks
Sunny

I need kernal upgrade on hp unix cluster ECC6 process step to step

Hello,
I need kernal upgrade procedure on hp unix cluster ECC6 in step to step
Please help me .
Regards
Mahesh

Hi,
If its a cluster or single instance, the procedure is the same.
As a thumb rule always execute the program RSPARAM from se38 and find the directory structure of the parameter DIR_CT_RUN.
The default value is generally /usr/sap/SID/SYS/exe/run
Download the SAPEXE<NO>.SAR and SAPEXEDB<no>.SAR and extract i in the above directory.
Before you do it make sure thats:
Stop the SAP R/3 resource in the cluster. Leave the SAP disk online.
Replace the Kernel
Start the instance
Replicate executables in the c:windowssapcluster or c:winntsapcluster (on both nodes)
You are done
Thanks Nirmal

Mac 10.8.4 - OES11 Cluster volume migration

I am posting this question as we are trying to implement the 'same' features we are used to with Windows.
The kanaka client 2.8 & server are configured and have the clustering resources set to the same vol-name as in the documentation
Now some questions:
1) when a cluster resource moves - the kanaka client loses connectivity - is there a way to have it auto reconnect as windows clients do?
2) When Word is open and editing a document on a network volume - The network volume is migrated - Word crashes and loses the contents
Is there a timeout for reconnecting? I see a timeout for logging in and the default is 60 seconds.
what are some of the best solutions for what I am asking ?
Thanks in advance
Joe

Some further info
In our testing without cluster migration we have noticed that volumes have been dropped.
When the Macs went to sleep (for about 15 minutes) - all the volumes were present.
When they were asleep for longer - some volumes dropped but not all ?

Upgrade OES2 to OES11 Cluster

Similar Messages

Maybe you are looking for