SLES 11 to SLES SP1 upgrade

SUSE Product Topics SLES Updates
1

Hello,

I am new to SLES, having a solaris and then redhat background.
I have a SLES 11 server to upgrade to sp1, and have found this document:
http://www.novell.com/support/documentLink.do?externalID=7005410

I am trying to use the zypper method.

The document implies I should add the appropriate sp1 repo(s).
I just want to make sure I add the correct one(s) before I begin.

Do I add the SP1-Pool?
Is that the only one, or do I add the update repository too?

thank you very much for your help

2

Hi
In your list of repositories, enable all the SP1’s listed and disable
the others.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 1 day 20:32, 2 users, load average: 0.00, 0.01, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

3

Hi, thanks for your answer.

Actually, that’s my question though…what repositories do I add? I do not have any SP1 repositories yet.
ftp2:~ # zypper lr

| Alias | Name | Enabled | Refresh

–±-------------------------------------------------------±-------------------------------------------------------±--------±-------
1 | OpenSuSE-proftpd | OpenSuSE-proftpd | Yes | Yes
2 | SLES11 | SLES11 | No | No
3 | SLES11SDK | SLES11SDK | No | No
4 | SUSE-Linux-Enterprise-Server-11 11-0 | SUSE-Linux-Enterprise-Server-11 11-0 | No | No
5 | SUSE-Linux-Enterprise-Software-Development-Kit-11_11-0 | SUSE-Linux-Enterprise-Software-Development-Kit-11 11-0 | No | No

4

Hi
You need to register the system to enable the respective repositories.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 1 day 21:27, 2 users, load average: 0.05, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

5

Thanks for your help. I must not be communicating, clearly, though.
My system is register; I just added the SP1-Pool repository.
I’m just trying to figure out if that is the correct repository to add, or if I should add more/different ones?
Should I add sp1-Updates instead, or with it?

thanks again for your response, it’s very much appreciated!
:~ # zypper ar https://nu.novell.com/repo/$RCE/SLES11-SP1-Pool/sle-11-x86_64?credentials=NCCcredentials SLES11-SP1-Pool
Adding repository ‘SLES11-SP1-Pool’ [done]
Repository ‘SLES11-SP1-Pool’ successfully added
Enabled: Yes
Autorefresh: No
URI: https://nu.novell.com/repo//SLES11-SP1-Pool/sle-11-x86_64?credentials=NCCcredentials

zypper lr

| Alias | Name | Enabled | Refresh

–±-------------------------------------------------------±-------------------------------------------------------±--------±-------
1 | OpenSuSE-proftpd | OpenSuSE-proftpd | Yes | Yes
2 | SLES11 | SLES11 | No | No
3 | SLES11-SP1-Pool | SLES11-SP1-Pool | Yes | No
4 | SLES11SDK | SLES11SDK | No | No
5 | SUSE-Linux-Enterprise-Server-11 11-0 | SUSE-Linux-Enterprise-Server-11 11-0 | No | No
6 | SUSE-Linux-Enterprise-Software-Development-Kit-11_11-0 | SUSE-Linux-Enterprise-Software-Development-Kit-11 11-0 | No | No

6

Hi
Re reading the TID so you ran;

run ‘suse_register -d 2 -L /root/.suse_register.log’ to register the
products in order to get the corresponding SP1-Pool repositories.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 3:49, 2 users, load average: 0.01, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

7

Ok, taken from the TID, and commented with what I did.

  1. Update by using zypper

    Open a root shell.
    Run ‘zypper ref -s’ to refresh all services and repositories.
    Run ‘zypper up -t patch’ to install package management updates.
    Run ‘zypper up -t patch’ again to install all available updates for SLES/SLED 11.

#did the above, but there was no info aobut the ditsro upgrades, as expected, because I only had repositories for the base install.
#I ran suse_register - obviously, now reading your reply, not the right thing to do.
#I then added the pool repository manually, with zypper ar

#then after, reading your reply, I deleted the SP1-pool repository and ran suse_register -d 2 -L /root/.suse_register.log, which had an exit status of 16 and ‘cannot contact the registration server’
#If i run suse_register, I get an exit status of 0. I don’t know what the -d is in suse_register … I will go look that up now

#My guess is that What i should do is re-add teh sp1_pool repo with zypper, and run the suse_register -d 2 -L /root/.suse_register.log, and then start from the zypper up -t patch? Or should I be adding different/add’l reos?

Thank you!

(----rest of the TID instructions follow---------)

Now the installed products contain information about distribution upgrades and which migration products should be installed to perform the migration. Read the migration product informations from /etc/products.d/*.prod and install them. You can use the following command:
grep '<product>' /etc/products.d/*.prod
A sample output could be as follows:

sle-sdk-SP1-migration
SUSE_SLES-SP1-migration

Install these migration products (example):
    zypper in -t product sle-sdk-SP1-migration SUSE_SLES-SP1-migration
run 'suse_register -d 2 -L /root/.suse_register.log' to register the products in order to get the corresponding SP1-Pool repositories.
Run 'zypper ref -s' to refresh services and repositores.
Check the repositories using 'zypper lr'. If needed, disable repositories for the old GA Products manually and enable the new SP1-Pool repositories:
    zypper mr --disable <repo-alias>
    zypper mr --enable <repo-alias>
Then perform a dist upgrade by using the following command:
    zypper dup 
zypper will report that it will delete the migration product and update the main products. Confirm the message to continue updating the rpm packages.
After the upgrade is finished, register the new products again. It will remove the SLE 11 GA update repositories and add the new SP1-Update repositories. The SP1-Pool repositories will stay untouched.
suse_register -d 2 -L /root/.suse_register.log
Reboot the system
8

Hi
Possibly a glitch in contacting the server (it can be an issue at
different times), so I would try re-running the register command again.

I used wagon via ssh -X to update my server from my desktop, any
thoughts about trying that?

ssh -X user@server
gnomesu /usr/sbin/wagon

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 19:25, 2 users, load average: 0.14, 0.06, 0.06
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU