Performing a Channel Upgrade from OES 11 to OES 11 SP1 running SLES11 for VMware.

  • 7010764
  • 11-Sep-2012
  • 24-Oct-2012

Environment

Novell Open Enterprise Server 11 (OES 11) Linux
SUSE Linux Enterprise Server 11 SP1 for VMware (SLES11-SP1-VMware)

Situation

With the release of Novell Open Enterprise Server 11 SP1 (OES11SP1), we offer the opportunity to upgrade from Novell Open Enterprise Server 11 (OES11) using either the physical media or the update channels.

In both cases, when the OES11 was installed on SUSE Linux Enterprise Server 11 for VMware (SLES11 for VMware) it is required to use the SLES11 for VMware SP2 media or channel when upgrading.
Failing to do so may render the server in an unsupportable state and may have to be reinstalled.

Be aware that SLES11 for VMware is supported by VMware, inc.

Resolution

If SLES-11-SP1-for-VMware-DVD-x86_64-DVD1.iso was used for the initial installation of Novell Open Enterprise Server 11, when using physical media to upgrade the server, make sure to use these media:
- SLES-11-SP2-for-VMware-DVD-x86_64-DVD1.iso
- OES11-SP1-addon-x86_64-CD1.iso

When performing a Channel Upgrade from OES11 to OES11SP1, the procedure is the same as documented for a OES11 server installed on top of SLES11SP1, though the update channels that should be used are these:
- SLES-SP2-VMware-Core
- SLES-SP2-VMWare-Updates
The regular OES11SP1 channels can and should be used.


The regular documentation can be followed, with these considerations:

When registering the server running OES11 on top of SLES11SP1 for VMware, make sure to use the SLESforVMware Activation key.

So the 1st step in both the "Channel Upgrade from OES 11 to OES 11 SP1 Via Wagon" and "Channel Upgrade from OES 11 to OES 11 SP1 Using zypper" should look like:
suse_register -a email=<Email-Address> -a regcode-sles=<SLESforVMware-activation-key> -a regcode-oes=<OES-activation-key> -L /root/.suse_register.log
All in 1 command line.

The 2nd step in these scenarios should be used to ensure the OES11-Pool, OES11-Updates, SLES-SP1-VMware-Pool and SLES11-SP1-VMware Updates catalogs are subscribed and enabled.

The migration product that should be used along with Open_Enterprise_Server-SP1-migration, is the SLES-for-VMware-SP2-migration.

When using zypper to upgrade the server, the command for step 11 should look like:
zypper dup --from OES11-SP1-Pool --from OES11-SP1-Updates -- from SLES11-SP2-VMware-Core --from SLES11-SP2-VMware-Updates
All in one command line.


When "Upgrading OES 11 to OES11 SP1 Using SMT" the channels that should be mirrored in step 2 should be:
  • OES11                              -  OES11-Pool and OES11-Updates channels.
  • OES11SP1                        -  OES11-SP1-Pool and OES11-SP1-Updates channels.
  • SLES11SP1-for-VMware - SLES11-SP1-VMware-Core and SLES11-SP1-VMware-Updates channels.
  • SLES11SP2-for-VMware - SLES11-SP2-VMware-Core and SLES11-SP2-VMware-Updates channels.


At all times, on a server running SLES11 for VMWare, keep the regular SLES channels disabled.

Cause

Even though SUSE Linux Enterprise Server 11 for VMware is basically the same core OS as a regular SUSE Linux Enterprise server 11, there are essential differences. For instance SLES11 for VMware is stripped from all XEN related packages. Therefor it is possible to install OES11 on top op SLES11 for VMware.
For the reason that the SLES11 for VMware has a different package selection along with the fact that SLES11 for VMware is supported by VMware, inc. and the regular SLES11 is supported by SUSE Technical Services, mixing both distributions may render the server in a unsupportable state.

Additional Information

This document only is for Novell Open Enterprise Servers 11 installed on top of SUSE Linux Enterprise Server 11 for VMware. When the regular SUSE Linux Enterprise Server 11 SP1 was used, the regular documentation can be used without any alteration.
Using OES11-SP1-addon_with_SLES11-SP2-x86_64-DVD.iso is impossible when the Novell Open Enterprise Server was installed on top of SLES11SP1 for VMware.