After the server has been registered in the Novell Customer Center, you can apply updates via packages and patches. The default GNOME desktop indicates when there are updates available to the server. You can update the server from any of the following interfaces.
You could also patch an OES server using the following methods: Section 7.8, GUI Based Patching, Section 7.9, Using SUSE Manager to Patch an OES Server, Section 7.7, Patching From Behind a Proxy Server, and so on.
After you have registered the server in the Novell Customer Center, you can update the server by using commands at the command line. The following procedure specifies steps for updating the server with all available patches for SLES 11 SP3 and OES 11 SP2.
Log in to the server as root or su to root.
At the command line, enter the following commands. The screen shots show example output.
Refresh all services:
zypper ref -s
See whether updates are available for SLES 11 SP3 and OES 11 SP2:
zypper patch-check --repo catalog1 --repo catalog2
zypper patch-check --repo SLES11-SP3-Updates --repo OES11-SP2-Updates
Update the server with all available SLES11 and OES 11 patches:
zypper up -t patch -r SLES11-SP3-Updates -r OES11-SP2-Updates
NOTE:When you install CIFS package using the command line (patch install, rpm upgrade, zypper updates and so on), you will get the 16024 Add method error. You can ignore this error as it does not cause disruption to any service. Cause: While installing a newer CIFS version, the setup might try to pull in few NMAS methods that are existing on your server. This would be seen only when the patches are updated from the command line interface. The NMAS methods present in the server are retained and are not overwritten.
If the patching requires a server reboot, do so when intimated by the system.
Rebooting the server activates the new kernel if it has been updated and ensures that OES services that need restarting after patching are restarted.
For more information on zypper, see SDB:Zypper usage 11.3.