Environment
Novell GroupWise 2012
Novell GroupWise 8
Novell eDirectory
Novell GroupWise 8
Novell eDirectory
Situation
Need to move Domain or Post Office to a new network with a different IP address or new subnet.
How to change OES IP address, how to manually migrate and reconfigure GroupWise agents.
How to change OES IP address, how to manually migrate and reconfigure GroupWise agents.
Resolution
Novell has provided a script and documentation for changing the ip address of an OES Server:
See Changing an OES 2 SP3 Server's IP Address.
Note: It does reference this migration as NW or Windows to Linux, but the steps and reconfiguration are very close to identical when migrating from one Linux server to another.
Novell has provided documentation for Manual Server Migrations:
See Manual Server Migration.
See Troubleshooting Post-Migration Problems for common issues.
Note: It does reference this migration as NW or Windows to Linux, but the steps and reconfiguration are very close to identical when migrating from one Linux server to another.
Novell has provided documentation for Manual Server Migrations:
See Manual Server Migration.
See Troubleshooting Post-Migration Problems for common issues.
Additional Information
This command will replace any old ip with the new ip for any files that ends in .conf or .xml:
sed -i "s|<oldIP>|<newIP>|g" `find / -name "*.conf" -or -name "*.xml"`
Note: It's possible that just this command will fix any eDirectory references to the old IP address, etc. The information provided below is for your reference.
You can use the following command to grep through your server and see if there are any other files with the old ip address still in there. Insert your ip address and the directories you want to search.
grep -R <oldIP> /etc/* | less
Below is a list of files which relate to the IP address of an OES2 server. If you want to ensure that all OES2 services still run properly after editing the IP address in YaST, do the following (the first sed command above should catch everything below except the novell-lum namconfig step):
Recreate default ssl certificates:
After completing all the tasks reboot the server.
sed -i "s|<oldIP>|<newIP>|g" `find / -name "*.conf" -or -name "*.xml"`
Note: It's possible that just this command will fix any eDirectory references to the old IP address, etc. The information provided below is for your reference.
You can use the following command to grep through your server and see if there are any other files with the old ip address still in there. Insert your ip address and the directories you want to search.
grep -R <oldIP> /etc/* | less
Below is a list of files which relate to the IP address of an OES2 server. If you want to ensure that all OES2 services still run properly after editing the IP address in YaST, do the following (the first sed command above should catch everything below except the novell-lum namconfig step):
- /etc/nam.conf (edit the file)
- /etc/opt/novell/eDirectory/conf/nds.conf (edit the file)
- /etc/sysconfig/novell/ldap_servers/<server ip address> (rename the file, edit the file)
- /etc/sysconfig/novell/lum (edit the file)
- /etc/sysconfig/novell/sms (edit the file)
- /var/lib/novell-lum/.<server ip address>.der ( run namconfig -k to recreate the file)
Recreate default ssl certificates:
- Use iManager to recreate the default ssl certs with the correct ip address.
iManager | Novell Certificate Server | Repair Default Certificates.
After completing all the tasks reboot the server.