SUSE Conversations


Open Enterprise Server 2 SP1 Migration Guide – Vol. 2, OES1

mfaris01

By: mfaris01

March 3, 2009 9:04 am

Reads:73

Comments:0

Rating:0

Even though the majority of Novell users are concerned with migrating NetWare to Open Enterprise Server 2 Linux, there are those users who migrated their NetWare servers to OES 1 Linux. This guide was written to help those OES 1 Linux migrate their servers to OES 2 SP1 Linux.

Migrating OES1 to OES2 SP1 is a much more involved process than changing OS platforms all together. If you’re planning of migrating to a new server altogether, the process is simpler. Upgrading an existing OES 1 Linux server is more tedious and lengthy. Now depending whether you are upgrading hardware or same server upgrade is your decision. We’ll take a look at each, so as to cover a broader audience.

Why upgrade OES 1 to OES 2 Linux? eDirectory, ZENworks, GroupWise, iFolder, etc.. Work on both? True, but there are major enhancements. OES 1 is based on SuSE Linux Enterprise Server 9. OES 2 SP1 is based on SLES 10 SP2. SLES 10 SP2, in itself is a much more enhanced. Novell Storage Services is considerably more stable and easier to install and maintain.

This guide is separated into two sections:

Part I – Migrating an OES 1 SP2 Linux server to a new OES 2 SP1 Linux server
Part II – Upgrading an existing OES 1 SP2 Linux server to OES 2 SP1 Linux

A few notes and prerequisites.

  1. OES 1 Linux must be running SP2 prior to beginning.
  2. SLES and OES must be upgraded together.
  3. Any third party application, even other Novell products (GroupWise) that are not native to OES or SLES will be deleted during the upgrade process.
  4. According to the documentation, on-line upgrading through the support channel is not supported. I don’t know why you would really want to anyway.
  5. You must have an active support subscription for updates. There are post-installation updates that are critical to eDirectory and other services.

Part I – Migrating an OES 1 SP2 Linux Server to a New OES 2 SP1 Linux Server

The steps to perform the migration are listed here:

  1. Prepare your environment
  2. Install your new server
  3. Migrate file system
  4. Migrate services
  5. Testing
  6. Decommission OES 1 Server

Unlike NetWare to OES 2 migrations, not all services can be migrated. Here is a list of what CAN be migrated using the migration gui. The services that cannot can be manually migrated to the new OES 2 SP1 server.

iFolder v2 and v3.2
iPrint
NSS – File Systems
NCP

That’s it? This list doesn’t mean the other services, like DHCP can’t be migrated, we’ll just have to use a different method.

Our example will have the following services migrated from the source to the target.

File System
iPrint
DHCP

I’m including DHCP so we can see one way of manually migrating a service.

Preparing your Environment

Even though we are migrating the services and data to a completely new server, good backups of the server should be included in your daily routine.

Ensure that your OES 1 Linux server is SP2 and has the latest patches.
Ensure that both the source and target servers have complete DNS entries to include reverse lookup.

Have, either the eDirectory admin password or have an admin equivalent account.

Install the New Server

The installation process of both SLES 10 SP1 and OES 2 SP1 have been covered exhaustively in numerous formats and media. I’ve written it up myself for various entities and know it by heart. I’m not going to type it up again. Refer to Novell’s documentation for more information.

Make sure when you install SLES and OES 2, that you choose the same functional packages that the source server has, otherwise, you have to do so before migration can begin.

Ensure the new server is registered and has all the latest updates.

If the new server is to be in the same eDirectory tree, that it is placed respectively in a location that is accessible (tree wise) from the source server. i.e., Same Organizational Unit.

Migrate the File System

I’m going to configure the file system migration separate from any other service, because I feel it’s one of the most important aspects of the server-to-server migration scenario.

From New server, Target, make sure the X Window gui is loaded and running, (startx). If you’re using runlevel 5, you’re already there.

Run YaST or miggui (from the command line)

This is the main screen. Click on the Source Server.

Fill out the fields according to your organization. Also, ensure you enter the source server’s root password. Click Ok.

Do the same for the Target server.

Choose Migration Type – Consolidate.

Click on Add to add services to migrate.

You will see File System and iPrint, select both and click Ok.

We have our services for migration, now we have to configure them.

Highlight File System and click the Configure button.

Select the directories you wish to migrate and drag them over to the target server. If you mess up the placement, just click Cancel and try again.

Click the File Option tab.

Make your selections and click on Trustee Options tab.

If you click on Custom Mapping, the Match User Options tab will become active.

When you are done, click Ok.

Migrate Services

Select iPrint from the list and click the Configure button.

Browse to both the source and target Print Managers. Add any printers you with to migrate and then click the Other Options tab.

Browse to your current Driver Store and choose your printer driver and profile options.

When you are done, click Ok.

Click Start to begin the migration process. If there are any problems, the log tab will help you identify where the problem is. Remember that LDAP is used for authentication, and could be a source of failures. Check that too.

When the migration is complete, you will see a screen similar to this.

But the migration is not really complete, we still have to manually migrate DHCP.

Even though Novell stores DHCP configuration data in eDirectory, Linux DHCP likes it stored in a file on the server. When configured for a particular server, eDirectory writes the configured scopes and settings to the server in the form of a text file and then starts the dhcpd daemon and it reads the configuration from disk, not eDirectory.

Login to iManager and select DHCP (Linux). Create a new DHCP Server and designate the new OES 2 SP1 server.

Assign the scopes to be serviced by the new OES 2 SP1 server and save the config. Make sure you restart the dhcpd daemon on the target server.

When you’re done with everything… If you need to add replicas, etc.., do that now.

Testing

Testing involves ensuring the services you migrated are working. Simple. Check your file system and if trustees are assigned, as in user home directories, check them and see if they have the correct trustee, if any. If not, you can go back and re-run the migration utility and migrate the trustees. Then test again to make sure before you release the server to production.

Decommission the OES 1 Linux Server

There isn’t a lot to do when decommissioning an OES server, aside from removing any replicas from the server with iManager or ConsoleOne. Remove eDirectory by running the following:

/opt/novell/eDirectory/bin/ndsconfig rm [-a <admin FDN>] [-w <admin password>] [-c] [-b <port to bind>] [--config-file <configuration file>]

This will remove the server from the tree. You will still need to login to iManager and remove any remaining objects related to the server.

After that, simply shutdown the server and turn it off.

Part II – Upgrading an existing OES 1 SP2 Linux server to OES 2 SP1 Linux

The steps to perform the upgrade are listed here:

  1. Preparing your environment
  2. Upgrade of SLES 10 SP2 with OES 2 SP1 as an add-on
  3. Upgrading eDirectory
  4. Configuring LDAP
  5. Configuring OES Services
  6. Testing

Seems straight forward, and it is, but there are many little things you need to do in each of the steps.

Preparing your Environment

As with any upgrade, ensure you have a good full backup of all partitions on your server. This upgrade modifies not only root (/) but also /boot. Make note as to which partition is root. You can do this by cat’ing the /etc/fstab or by running df.

Again, Non-OES 2 applications, applications not included with OES 2, will be DELETED during installation. These include Identity Manager, GroupWise and ZENworks. iFolder 3 will NOT be deleted as it is included, iFolder 2 will be deleted. Refer to Novell documentation for those applications.

Ensure your OES 1 server has a valid DNS entry. Validate it by pinging it by name, from another machine.

Create a Common Server Certificate and export it for use later.

Do the following to accomplish this.

  1. Run YaST.
  2. Click Security and Users | CA Management.
  3. If no CAs are listed, create one by clicking Create Root CA.
  4. If there is one listed, you can use it by selecting it and clicking Enter CA. Provide the password (usually root’s password).
  5. Click Certificates | Add.
  6. Enter the information needed and complete the creation of the cert.
  7. You will see it listed. Select the cert you just created.
  8. Click the Export button, then select Export as Common Server Certificate.

Upgrade of SLES 10 SP2 with OES 2 SP1

EVMS, NSS and the system

If you have ignored all recommendations and put EVMS and NSS on the same device as the system partitions, root, swap, etc, then this next part applies to you. Otherwise, skip to Installation of SLES 10 SP2.

Run YaST

Select System | System Services (Runlevel)

Choose Expert Mode

Scroll down and enable boot.lvm and boot.md

Click Finish and Yes.

Run “parted” to determine which partition is the NSS volume.

Depending on what your disk device is called, you would enter something similar:

parted /dev/sda

Using /dev/sda
(parted)

Type print at the prompt. Your output will be similar.

Disk geometry for /dev/sda:  0kB – 146GB
Disk label type: msdos
Number   Start     End      Size      Type     File system   Flags
1        64kB      301MB    301MB     primary  ext3          boot, type=83
2        301MB     22GB     21GB      primary                lvm, type=8e
3        22GB      146GB    124GB     primary                type=65
(parted)

NSS volumes are of type=65. Make note the “number” for each partition that is of Type=65.

Now type quit to exit.

We want to “hide” the NSS partitions from EVMS, we’ll change the type from 65 to 6b, temporarily. When the upgrade is complete, we’ll change them back.

Back at the terminal prompt, type the following parted command for each NSS partition you find in the above list. Type=6b and the Number is 3 for my example.

parted /dev/sda set 3 type 0x6b

Later you will notice that NSS partitions are missing. Don’t worry, they’re still there, EVMS won’t recognize them. We’ll fix that later after the upgrade.

Installation of SLES 10 SP2

Installation sources other than CD/DVD are beyond the scope of this article. Please refer to Novell documentation for more information on remote installation sources.

Place the SLES 10 SP2 CD 1 or DVD 1 into the server and reboot the server.

Select Installation.

Select your Language and then agree to the EULA and click Next.

On the Installation Mode screen, ensure that Update and Add-On Product boxes are checked. Click Next.

You will be prompted to specify where the media is located for the Add-On product. Click CD or DVD, depending on what you have, and follow the prompts to add it.

If YaST cannot determine which partition /boot is located, you will be prompted to specify which partition you wish to upgrade.

For those of you with EVMS on your system device, you should get a pop up stating that YaST could not mount the partition.

If you get this, click Select Mount Options.

Delete /evms from the device field and click Ok.

Once the device is mounted, you will see a warning screen telling you that applications not included with SLES and OES will be removed.

Once you’ve read this and decided whether you want to continue, click Ok.

YaST will present you with a summary of what will be upgraded. This is similar to the Options screen for a standard SLES installation. Modifications can be made at this point, i.e., additional packages added.

Select Update Options to determine how your existing packages are upgraded.

If you just want to update the existing packages only, check Only Update Installed Packages.

If you want to add additional packages, such as Novell DNS, you can check Update Installation with New… and click the Select Patterns button. You will be presented with the following screen.

The packages to be updated have the lightening or ‘Z’ symbol. It is not recommended that use this process to uninstall packages. That process should be performed in a post upgrade setting.

Once you are satisfied with your selections, click Accept. If there are any conflicts, you will be presented with them at this time. If you mess up, click Cancel and then Select Patterns again. This will reset the selections.

Click Accept on the Update Options screen, and Next on the Installation screen.

Click Start Update on the confirmation screen and the upgrade will commence.

After the server reboots, you will be asked to Test Internet Connection. If you have multiple network interfaces, ensure that the correct interface is listed, otherwise choose the correct interface and select Yes and Next.

You can skip the test, but it will also skip updates and registration. This is not recommended.

I’m going to assume that you’ve already tested, registered and are ready to update online.

One thing I have found with these initial updates is to allow Novell to determine which packages to update. There are some sequential type updates that have dependencies. I simply accept the updates presented and allow it to progress. You will notice that the update process runs several times because of these dependencies. Just Accept each one and eventually it will complete.

Upgrading eDirectory

When the process continues, OES services will begin their configuration. If you initially installed eDirectory to it’s default location, you will get the following message.

Click Upgrade and enter the Admin password to update the DIBs.

Enter the information for LDAP in accordance with your organization.

Click Next

Configuring OES Services

This is the OES configuration summary screen. Review all of the options to ensure that all of the OES services are configured to your organization’s protocol. Some you may have to configure, especially if you added them at the update. When you have completed these configurations, click Next.

Now the configuration will begin and you will see iManager, eDirectory, etc..

When it’s complete, you will be presented with the ReadMe screen. Click Next.

On the Installation Completed screen. Uncheck Clone this System for AutoYaST, and click Finish.

The server will then proceed to either a login prompt (Runlevel 3) or a GUI login prompt (Runlevel 5).

Login as root.

For those who have EVMS on the system device, open the /etc/fstab file and check the root (/), /boot and swap and make sure that the mount paths are correct.

/dev/evms/boot, not /dev/anything_else/. When you are done, save the file and run the following command to make sure that initrd is updated correctly:

mkinitrd -f evms

Now we need to “unhide” the NSS volumes. From a terminal prompt enter the following command to change the NSS partitions back to Type=65.

parted /dev/sda set 3 type 0x65

Now we have to activate the NSS partition for EVMS. Enter the command,

evms_activate

Now we’ll need to reboot the server.

Testing

When the server is back up, open a browser and enter the URL to access the server’s welcome page:

http://servername.your_domain.org

Check your logs and OES services to ensure they are operating properly. We can’t show them here because of the wide variety.

Conclusion

There are several options and paths to migrating your various systems, be it NetWare or OES 1 Linux to OES 2 SP1 Linux. And because you’re working and learning Linux, you will probably find another ten different ways of producing the same result. These are just examples of what you can do, as provided by Novell. Keep up the fight and have fun.

Enjoy!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags:
Categories: Open Enterprise Server on SLES, Technical Solutions

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

Comment

RSS