How can I know if patch updates are available for a SUSE Linux Enterprise 10 device?
What is the difference between mandatory bundles and non-mandatory bundles?
What are the different statuses of a bundle on a managed device?
What are the different statuses of a package on a managed device?
Why does the ZMD show fewer installed packages than are shown by the rpm -qa command?
When can I use an NFS mounted directory as a ZMD cache directory?
Does the RPM command that I use to install packages reflect in the bundle status and package status?
How do I install a bundled PostgreSQL database to its own mounted NFS server?
How do I install a bundled PostgreSQL database to a local mounted hard disk?
How can I upgrade SLES 9 to SLES 11 with ZENworks 7.3 Linux Management installed?
How do I mirror software from an SMT repository to a ZENworks Linux Management Server?
How can I create a copy of a catalog on the ZENworks Linux Management Server?
How can I know the bundle size based on the payload content?
At the command prompt, enter the rug list-updates command to view the updates that are available for your device.
At the command prompt, enter the rug list-updates -t patch command to view the patch updates that are available for the SUSE Linux Enterprise 10 device.
If you are logged in to the GNOME desktop or KDE desktop, the globe icon on the panel changes to an orange exclamation mark if there are updates available for your device. Click the icon to view the list of updates.
A mandatory bundle is assigned directly to a managed device. You cannot uninstall a mandatory bundle from a device on which the complete ZENworks Linux Management is installed.
A non-mandatory bundle is assigned to a catalog, and the catalog is assigned to a device. These bundles are optional and are not automatically installed on the device. Non-mandatory bundles fulfil the dependencies required to install packages.
Refer to the following table to understand the different statuses of a bundle on a managed device:
Table 2-1 Bundle Status on a Managed Device
|
Status |
Description |
|---|---|
|
‘ ‘ |
Bundle is not installed on the device. |
|
i |
Bundle is installed on the device. |
|
* |
Bundle is partially installed on the device. |
|
v |
A different version of the bundle is installed on the device. |
Refer to the following table to understand the different statuses of a package on a managed device:
|
Status |
Description |
|---|---|
|
‘ ‘ |
Package is not installed on the device. |
|
i |
Package is installed on the device. |
|
s |
The package in the bundle is of a lower version than that installed on the device. |
|
v |
A different version of the package is installed on the device. |
The rpm -qa command shows the imported GPG keys (gpg-pubkey-xxxxxxx-xxxxxxx) that are not actual packages as installed packages. The ZMD filters the GPG keys from the list of installed packages, and therefore shows fewer installed packages than are shown by the rpm -qa command.
If you encounter an insufficient disk space error in the partition that has the ZMD cache directory, you can use an NFS mounted directory as a ZMD cache directory.
Yes. The ZMD monitors the rpm DB/var/lib/rpm/Packages directory for any changes in the RPM database, and updates the bundle status and package status appropriately.
If you have set the flag for some or all of the packages while installing a bundle, those packages are upgraded only if an earlier version of the package is already installed. If no earlier version of the package exists on the device, the packages in the bundle are not installed even though the bundle is installed. Therefore, the status of these packages is displayed as not installed when you run the rug bundle-packages command.
Mirror the SLE*10-SP1-Online Catalog and SLE*10-Updates Catalog from Novell Updates to your ZENworks Linux Management server by using zlmmirror.
This server requires authentication with your Novell Customer Center (NCC) account name and password.
(Optional) Assign the monolithic SLE*10-Updates-bundle from the Updates Catalog to the managed devices. After the bundle is installed, remove the assigned bundle from the device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Assign the SLE*10-SP1-Online bundle from the Online Catalog to the managed device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Install the bundle, then restart the managed device.
NOTE:If you want the existing kernel on the device to be updated by the new kernel, change the for all the kernel packages from in ZENworks Control Center in the bundles specified in Step 2 and Step 3.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
You can install these bundles by either directly assigning them from the ZENworks Linux Management server or manually installing them on the managed device by using the rug bin command. If the bundles are manually installed on the device, ensure that the assigned catalog contains either a single monolithic bundle or all patch bundles.
If the Catalog has only a monolithic bundle, it can be installed by using rug bin directly. If the Catalog has all the patch bundles, then you should run rug bin --entire-catalog to install all its bundles, excluding the monolithic bundle.
Mirror the SLE*10-SP2-Online Catalog and SLE*10-SP1-Updates Catalog from Novell Updates to your ZENworks Linux Management server by using zlmmirror.
This server requires authentication with your Novell Customer Center (NCC) account name and password.
(Optional) Assign the monolithic SLE*10-Updates-bundle from the Updates Catalog to the managed devices. After the bundle is installed, remove the assigned bundle from the device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Assign the SLE*10-SP2-Online bundle from the Online Catalog to the managed device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide
Install the bundle, then restart the managed device.
NOTE:If you want the existing kernel on the device to be updated by the new kernel, change the for all the kernel packages from in ZENworks Control Center in the bundles specified in Step 2 and Step 3.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
You can install these bundles by either directly assigning them from the ZENworks Linux Management server or manually installing them on the managed device by using the rug bin command. If the bundles are manually installed on the device, ensure that the assigned catalog contains either a single monolithic bundle or all patch bundles.
If the Catalog has only a monolithic bundle, it can be installed by using rug bin directly. If the Catalog has all the patch bundles, then you should run rug bin --entire-catalog to install all its bundles, excluding the monolithic bundle.
Mirror the SLE*10-SP3-Online Catalog and SLE*10-SP2-Updates Catalog from Novell Updates to your ZENworks Linux Management server by using zlmmirror.
This server requires authentication with your Novell Customer Center (NCC) account name and password.
(Optional) Assign the monolithic SLE*10-SP2-Updates-bundle from the Updates Catalog to the managed devices. After the bundle is installed, remove the assigned bundle from the device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide
Assign the SLE*10-SP3-Online bundle from the Online Catalog to the managed device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide
Install the bundle, then restart the managed device.
NOTE:If you want the existing kernel on the device to be updated by the new kernel, change the for all the kernel packages from in ZENworks Control Center in the bundles specified in Step 2 and Step 3.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
You can install these bundles by either directly assigning them from the ZENworks Linux Management server or manually installing them on the managed device by using the rug bin command. If the bundles are manually installed on the device, ensure that the assigned catalog contains either a single monolithic bundle or all patch bundles.
If the Catalog has only a monolithic bundle, it can be installed by using rug bin directly. If the Catalog has all the patch bundles, then you should run rug bin --entire-catalog to install all its bundles, excluding the monolithic bundle.
Mirror the SLE*10-SP4-Online Catalog and SLE*10-SP3-Updates Catalog from Novell Updates to your ZENworks Linux Management server by using zlmmirror.
This server requires authentication with your Novell Customer Center (NCC) account name and password.
(Optional) Assign the monolithic SLE*10-SP3-Updates-bundle from the Updates Catalog to the managed devices. After the bundle is installed, remove the assigned bundle from the device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide
Assign the SLE*10-SP4-Online bundle from the Online Catalog to the managed device.
For more information on how to assign the bundle, see Assigning Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide
Install the bundle, then restart the managed device.
NOTE:If you want the existing kernel on the device to be updated by the new kernel, change the for all the kernel packages from in ZENworks Control Center in the bundles specified in Step 2 and Step 3.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
You can install these bundles by either directly assigning them from the ZENworks Linux Management server or manually installing them on the managed device by using the rug bin command. If the bundles are manually installed on the device, ensure that the assigned catalog contains either a single monolithic bundle or all patch bundles.
If the Catalog has only a monolithic bundle, it can be installed by using rug bin directly. If the Catalog has all the patch bundles, then you should run rug bin --entire-catalog to install all its bundles, excluding the monolithic bundle.
Mirror the SLE*11-Updates, SLE*11-Pool and SLE*11-SP1-Pool Catalogs from Novell Update to your ZENworks 7.3 Linux Management Server with IR3. This server requires authentication with your Novell account name and password.
Remove either the monolithic bundle or the patch bundles from the SLE*11-Updates Catalog before assigning them to the managed devices, because this catalog has both the monolithic bundle and the patch bundles.
Assign the mirrored SLE*11-Pool Catalog to the managed devices . It acts as a source to resolve package dependencies for updates being installed.
Change the in ZENworks Control Center for all the kernel packages from to for the SLE*11-Updates-bundle and SLE*11-SP1-Pool-bundle to allow upgrade of the existing kernel package being installed.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Assign the mirrored catalog to the managed device that you want to upgrade.
For more information, see Assigning Catalogs
in the Novell ZENworks 7.3 Linux Management Administration Guide.
On the managed device, subscribe to the SLE*11-Updates Catalog, then run the rug bin SLE*11-Updates-bundle command to update the SUSE Linux Enterprise 11 packages. You should run rug bin --entire-catalog SLE*11-Updates-Catalog if the catalog contains the patch bundles.
When the packages are upgraded and the bundle is installed, log in to ZENworks Control Center and unassign the SLE*11-Updates and SLE*11-Pool Catalogs from the managed device.
Assign the SLE*11-SP1-Pool Catalog to the managed device to update the device packages to SLE11 SP1.
On the managed device, subscribe to the SLE*11-SP1-Pool Catalog, then install the SLE*11-SP1-Pool-bundle by using the following command to upgrade the existing packages to SUSE Linux Enterprise 11 SP1:
rug bin -r <SLE*11-SP1-Pool-bundle>
If you want to update KDE packages while upgrading a device to SLE*11-SP1 by using the existing pool bundle, then you can use the rug dup command. rug dup command is used to upgrade distribution.
NOTE:You can use ZENworks Control Center instead of executing the rug bin command to directly assign the bundles from SLE*11-Updates and SLE*11-SP1-Pool Catalogs to the managed device.
Mirror the SLE*11-SP1-Updates, SLE*11-SP1-Pool and SLE*11-SP2-Core Catalogs from Novell Update to your ZENworks 7.3 Linux Management Server with IR3. This server requires authentication with your Novell account name and password.
Remove either the monolithic bundle or the patch bundles from the SLE*11-SP1-Updates Catalog before assigning them to the managed devices, because this catalog has both the monolithic bundle and the patch bundles.
Assign the mirrored SLE*11-SP1-Pool Catalog to the managed devices. It acts as a source to resolve package dependencies for updates being installed.
Change the in ZENworks Control Center for all the kernel packages from to for the SLE*11-SP1-Updates-bundle and SLE*11-SP2-Core-bundle to allow upgrade of the existing kernel package being installed.
For more information, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Assign the mirrored SLE*11-SP1-Updates catalog to the managed device that you want to upgrade.
For more information, see Assigning Catalogs
in the Novell ZENworks 7.3 Linux Management Administration Guide.
On the managed device, subscribe to the SLE*11-SP1-Updates Catalog, then run the rug bin SLE*11-SP1-Updates-bundle command to update the SUSE Linux Enterprise 11 packages. You should run rug bin --entire-catalog SLE*11-SP1-Updates-Catalog if the catalog contains the patch bundles.
When the packages are upgraded and the bundle is installed, log in to ZENworks Control Center and unassign the SLE*11-SP1-Updates Catalogs from the managed device.
Assign the SLE*11-SP2-Core Catalog to the managed device to update the device packages to SLE11 SP1.
On the managed device, subscribe to the SLE*11-SP2-Core Catalog, then install the SLE*11-SP2-Core-bundle by using the following command to upgrade the existing packages to SUSE Linux Enterprise 11 SP2:
rug bin -r <SLE*11-SP2-Core-bundle>
If you want to update KDE packages while upgrading a device to SLE*11-SP2 by using the existing pool bundle, then you can use the rug dup command. rug dup command is used to upgrade distribution.
NOTE:You can use ZENworks Control Center instead of executing the rug bin command to directly assign the bundles from SLE*11-SP1-Updates and SLE*11-SP2-Core Catalogs to the managed device.
See Upgrading to OES 2 SP2 Through a ZENworks Linux Management Server in the OES 2 SP2 Installation Guide.
See Upgrading to OES 2 SP3 Through a ZENworks Linux Management Server in the OES 2 SP3 Installation Guide.
Stop the PostgreSQL server by using the following command:
/etc/init.d/postgresql stop
Mount the /var/lib/pgsql directory to a remote server that has the Write privilege by using the following command:
mount IPaddress_of_the_NFS_server:/data /local_mount_directory
Move the PostgreSQL database to the mounted NFS server by using the following command:
mv /var/lib/pgsql /local_mount_directory
Create a symbolic link by using the following command:
ln –s /local_mount_directory/pgsql /var/lib/
Change the ownership of the pgsql directory to postgres by using the following command:
chown –R postgres:postgres /var/lib/pgsql
Start the PostgreSQL server by using the following command:
/etc/init.d/postgresql start
Create a /local directory on the local hard disk.
Mount the new hard disk by using the following command:
mount /dev/new_hard_disk /local
The mounted hard disk must have the Write privilege.
Stop the PostgreSQL database by using the following command:
/etc/init.d/postgresql stop
Move the PostgreSQL data from the local hard disk to the mounted hard disk by using the following command:
mv /var/lib/pgsql /local
Create a symbolic link by using the following command:
ln –s /local/pgsql /var/lib/
Change the ownership of the pgsql directory by using the following command:
chown –R postgres:postgres /var/lib/pgsql
Start PostgreSQL server by using the following command:
/etc/init.d/postgresql start
An online upgrade from SLES 9 to SLES 11 is currently not supported by SUSE Linux Enterprise. Therefore, upgrading SLES 9 by using ZENworks 7.3 Linux Management to SLES 11 is also not supported. To upgrade SLES 9 that has ZENworks 7.3 Linux Management installed to SLES 11, see TID 7003597 at Novell Support.
An online upgrade from SLES 10 to SLES 11 or from SLED 10 to SLED 11 is currently not supported by SUSE Linux Enterprise. Therefore, upgrading SLES 10 or SLED 10 by using ZENworks 7.3 Linux Management to SLES 11 or SLED 11 is also not supported. To upgrade SLES 10 or SLED 10 that has ZENworks 7.3 Linux Management installed to SLES 11 or SLED 11, see TID 7002790 at Novell Support.
On the ZENworks Linux Management Server, create a Remote Execute policy with the following script:
touch /var/run/zmd/allow-upgrade-across-arch
For more information on how to create a Remote Execute policy, see Remote Execute Policy
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Assign the policy to the managed device on which you want to upgrade the packages.
Refresh the managed device by using the rug refresh command to successfully enforce the policy.
Ensure that the policy is successfully enforced on the managed device by using the following command:
ls /var/run/zmd/allow-upgrade-across-arch
Install the RPM bundle on the managed device.
Create a YUM subscription configuration file.
For more information on how to create a configuration file, see Configuring a Software Mirror
in the Novell ZENworks 7.3 Linux Management Administration Guide.
Edit the Remote Server section of the configuration file as follows:
Set the value of the <Base></Base> tag as the IP address of the SMT Server repository channel target.
For example, set the value as https://164.99.138.2/repo/$RCE/SLED10-SP1-Online/sled-10-i586 where SLED10-SP1-Online is the channel and sled-10-i586 is the target.
Set the value of the <Type></Type> tag to yum.
Set the value of the <Platform></Platform> tag as the operating system version that matches the supported device target of ZENworks Linux Management.
For example, if the operating system is SLED 10, the value of the tag should be sled-10.
NOTE:The remote server credentials and the target for the catalog are not required.
Mirror the catalog from a Primary ZENworks Linux Management Server to the same server under a different folder in ZENworks Control Center.
See the Novell Cool Solutions article Computing the Bundle Content Payload Size for ZENworks 7.x Linux Management“.
See the Novell Cool Solutions article Automated Orphaned Packages Deletion from ZLM Package Repository.
If the managed devices are distributed across remote geographical locations and have limited connectivity with the ZENworks Linux Management server, the patches or updates cannot be distributed directly by using bundles because the redundant data is transmitted over the network to all the managed devices. By using the File bundle, the downloaded updates can be distributed to each remote server device at a particular location. The remote server can be configured as a Web Server to publish the deployed packages in the Yum repository. All the agents can trigger update from this local Yum source by using the rug up command, by assigning a Remote Execute Policy from the ZENworks Linux Management Server.
Perform static mirroring of Pool and Updates Catalogs from the Novell Update Server(NU) to the ZENworks Linux Management server. You can also mirror the bundle packages to the local file system by using a static mirror.
Install the createrepo rpm on the ZENworks Linux Management server then run the createrepo command on the directories containing mirrored package updates for the given device targets. .
This creates Yum(rpm-md) repository for each target packages.
Create a File Bundle with the archived content of the packages directory, deploy the content to the remote server device, and extract it under a suitable location accessible to the locally managed devices via NFS or HTTP.
Create a Remote Execute Policy that adds this local Yum service to a published catalog, subscribes to the catalog, and performs rug up to update the device and report the status.
See the Novell Cool Solutions article Updating SLE10 SP3 product installed data after Online Migration from SP2 to SP3 using SLE10-SP3-Online-bundle in ZEnworks Linux Management.
Novell provides a Patch Notification Tool by Product to notify you about patches and updates.
When you subscribe to Novell/SUSE products, you can receive periodic e-mail notification messages regarding the new patches or updates released for a product. You can choose to perform replication by using zlmmirror to download these new published patches or updates for the specified product from the Novell Update Channel, then apply the equivalent mirrored bundles to update the corresponding ZENworks Linux Management Agents.
For more information, see Applying Red Hat Updates to RHEL Server Devices by Using SLES Expanded Support in the Novell ZENworks 7.3 Linux Management Administration Guide.
Mirror the RES 6 updates by following the procedure in Applying Red Hat Updates to RHEL Server Devices by Using SLES Expanded Supportin the Novell ZENworks 7.3 Linux Management Administration Guide.
After mirroring is complete, in the ZENworks Control Center, change the for all the kernel packages from to .
This allows the RES 6 bundle to upgrade the existing kernel packages. Also, delete the following:
Packages with names having abrt and report.
Python-mech RPM, if any.
You need not delete openoffice.org-report-builder package from the bundle.
Assign the mirrored catalog to the managed device that you want to upgrade.
Install the updates by running the rug up<RES_CATALOG_NAME> command on the device.
For more information, see Applying Red Hat Updates to RHEL Server Devices by Using SLES Expanded Support in the Novell ZENworks 7.3 Linux Management Administration Guide.