Re: Change DNS on ESRS Appliance

SSH to your ESRS-VE appliance, and login as “root”

If you’re using PuTTY; run the following so the boxes display correctly: export TERM=linux

Run “yast”

Arrow down to “Network Devices”, Tab across and arrow down to “Network Settings” and hit Return

Tab around to Overview then right arrow to “Hostname/DNS”

Tab down to the DNS section, and make your changes

Tab around to “OK” and hit return, or press F10.

Hope that helps!

MarcT

Related:

7023374: After using yast2 keyboard module the keyboard mapping in GNOME is changed only until next login

This document (7023374) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12

SUSE Linux Enterprise Desktop 12

Situation

When starting the YaST2 keyboard module to change the keyboard, the GNOME keyboard settings are changed as well but only until the next login.

Resolution

The YaST2 keyboard module is not meant to be used to change the keyboard settings of a graphical desktop environment. In fact, it changes the settings for the system keyboard. As Linux was designed as multi-user environment by default, there are keyboard settings for users working on a local tty (configured by /etc/sysconfig/keyboard) as well as keyboard settings for the graphical desktop environment which can be configured differently for each user that exists on the system. These settings are typically stored in the user home directory while /etc/sysconfig/keyboard requires root access to make changes.
A user having experience with a single desktop environment, might find this confusing but it is working as designed. The correct way to adjust the keyboard mapping inside a graphical desktop environment is to use the respective configuration tools, not YaST2.

Cause

YaST2 uses the xkbset command to change the keyboard layout. This unfortunately has an effect on the active e.g. GNOME keyboard settings and overrides them. Hence a user might get the impression, using YaST2 is the right way to change the keyboard layout. In fact, YaST configures the system-wide keyboard and the change is written to /etc/sysconfig/keyboard.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7023120: Migrating a SLES 15 system to SLES for SAP Applications 15

Use an interactive script.

Download the following RPM file to the server running SUSE Linux Enterprise Server 15. It is not required that the system (the source system) be registered with SUSE Customer Center (SCC).

Install the RPM:

# zypper in migrate-sles-to-sles4sap-15-2.1.noarch.rpm

After installation run the interactive script and follow the on screen instructions:

NOTE: It is required to have your email address as well as a valid registration key for SUSE Linux Enterprise Server for SAP Applications (the target system) at hand.

# sudo /usr/sbin/Migrate_SLES_to_SLES-for-SAP.sh

NOTE: In case packages are installed that have dependencies against IBM Java, it may be needed to reinstall them at the end of the procedure.

A reboot of the system is not necessary unless packages which require a reboot are also installed from the newly added channels.

Related:

7014247: How to upgrade SLES for SAP Applications 11 SP2 to SP3

This document (7014247) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 for SAP Applications

Situation

A system running SLES for SAP Applications 11 Service Pack 2 should be upgraded to Service Pack 3.

Resolution

Important note: Aftercompleting any form of update, run the command “rcrpmconfigcheck”, then look at the contents of the file /var/adm/rpmconfigcheck.This file contains a list of configuration files that could not beupdated automatically. These files must be checked and theconfigurations adjusted manually.

Procedure for upgrading from SLES / SLED 11 SP2There are different supported ways for updating a SUSE LinuxEnterprise 11 system to SP3 level. Users can either update to SP3 byusing the online update tools to install the respective patches or update using the SP3 installation media.

For installing SP3 via the respective patches, the following toolsare supported:

  • 1) YaST (“yast2 wagon”)
  • 2) zypper

Alternatively, the full SP3 media (DVD ISOimage) can be downloaded and one of the following procedures can be used, especially in caseof environments without network access:

  • 3) by booting from SLES for SAP 11 SP3 media

Update to SP3 via patches

Attention: The update process has to be done completely frombeginning to reboot. There is only a limited chance to revert changes.Furthermore, the server has to be connected online during thewhole update process.

Prerequisites:
Users have to makesure to have the system registered. If this is not done already, it can either be registered by using the “Novell Customer CenterConfiguration” module in YaST or by using the suse_register commandlinetool. This will add update sources to the system.

1) Update by using YaST and/or Update Applet

  • Start the Online-Update module (YOU) from the YaST control center.
  • Check, if all available patches that are named “You update for Software update stack” are installed. If this is not the case, those patches will automatically be preselected. Press ‘Accept’ to apply those updates. Among others, this will install updates of libzypp, satsolver, yast2-wagon, yast2-pkgbindings, etc.After installing those, YOU will restart itself.
  • Now it is possible to install all other updates that are availablefor SLE for SAP 11 SP2. The system needs to be rebooted afterwards, because the kernel and/or other important system components are updated.
  • Thetray applications kupdateapplet or gnome-packagekit will display amessage that a distribution upgrade is available and start the YaST2module ‘wagon’ on request. If the gnome desktop is being used, but thegnome-packagekit applet is not started automatically on login, go aheadas follows:
    • Press ALT-F2 and run ‘gconf-editor’.
    • In here, select ‘apps’ -> ‘gnome-packagekit’ -> ‘force_get_update_login’.
    • Afterthe next login the gnome-packagekit will start automatically and openup a message that a distribution upgrade is available.
  • As an alternative to using the tray application open up a root shell and run ‘/usr/sbin/wagon &’.
  • to manually start yast wagon you can also open a root shell and execute ‘yast2 wagon’
  • yast2-wagon contains a workflow to upgrade the system to the next Service Pack level. On the welcome page press “Next”.
  • yast2-wagon will do an automatic self update if needed.
  • Inthefollowing dialogue select how to migrate. Select “CustomerCenter” if the update repositories should be used, or select “Custom URL”if you want to specify the update source manually (see the respectivesection below). In most cases “Customer Center” should be the rightchoice. If you want to review the repositories changes yourself,additionally select “Check Automatic Repository Changes”. Click “Next”.
  • Are-registration of the system against the Novell Customer Center will be done. During the registrationprocess the appropriate SP3 update catalogs (SLE11-SP3-SAP-Pool, SLE11-SP3-SAP-Updates, SLES11-SP3-Pool, etc.) will be added. TheSLES for SAP 11 SP1/SP2 catalogs will be removed. Click “Next”.
  • The successdialog-popup at the end informs about which repositories were added (clickon the “Details” Button). A detailed list of the repos can be found further down in this document in the “Update via zypper” section.
  • Ifyou have selected “Check Automatic Repository Changes”, the list ofrepositories will be displayed, providing the opportunity to manuallyenable/disable/add/delete repositories. Klick “Ok” when finished.
  • A proposal screen (named “Distribution Updrade Settings”) is now listed with the following sections:
    • Add-On Products: Third Party add-on products can be added here.
    • UpdateOptions: This shows what will happen with the product. Temporarymigration products (e.g. SUSE_SLES-SP3-migration) will be removed, realproducts (e.g. SUSE_SLES) will be upgraded. Further, it can be selected, if all packages should be downloaded before upgrading (this is the default) or if the packages should be downloaded and installed one by one.
    • Packages: shows some statistics about rpm packages to update, to install and to remove.
    • Backup: some backup options.
  • Please note: If you changed your mind and want to abort the upgrade to SP3,click “Back” then “Abort”. In this case a rollback is triggered tobring the system back to SLE 11 SP2 level. Further the migrationproducts are removed, a re-registration is performed and the newlyadded repositories are removed.
  • To continue the upgrade to SP3 press “Next” -> “Start Update”.
  • The following steps are executed:
    • The update of the rpm packages is performed.
    • SuSEconfig is executed.
    • A message to reboot the system is displayed (Press “Ok”).
    • Aregistration of the final SP3 product(s) takes place. Please note that only the SLE 11 SP3 catalogs need to stay enabled.
  • After a reboot the system is on SP3 level.
1.1) Using a “Custom URL” for updating with YaST
  • Start yast2 wagon as stated above.
  • In the “Update method” dialogue select “Custom URL”.
  • Alist of repositories will be displayed, providing the opportunity tomanually enable/disable/add/delete repositories. In here it is possible to manually adjust installation- and update repositories.
  • Add the SP3 update source(s). This can either be the SP3 installation media or the new SP3 repositories (SP3-Pool and SP3-Updates).
  • Klick “Ok” when finished and continue with the “Distribution Upgrade Settings” dialogue as stated above.

2) Update by using zypper

  • Open a root shell.
  • Run ‘zypper ref -s’ to refresh all services and repositories.
  • Run ‘zypper update -t patch’ to install package management updates (same as “zypper patch”)
  • Now it is possible to install all available updates for SLES for SAP 11 SP2: run ‘zypper update -t patch’ again.
(As a sidenote: if you want to use the above command in a script for an unattended upgrade, the command would be: “zypper –non-interactive patch –auto-agree-with-licenses –with-interactive”)
  • Now the installed products contain information about distribution upgradesand which migration products should be installed to perform themigration. Read the migration product informations from/etc/products.d/*.prod and install them. Use the followingcommand:
  • zypper se -t product | grep -h — “-migration” | cut -d| -f2
  • A sample output could be as follows:
SUSE_SLES_SAP-SP3-migration
  • Install these migration product:
    • zypper in -t product SUSE_SLES_SAP-SP3-migration
  • run ‘suse_register -d 2 -L /root/.suse_register.log’ to register theproducts in order to get the corresponding SP3 Update repositories.
  • Run ‘zypper ref -s’ to refresh services and repositores.
  • Check the repositories using ‘zypper lr’. Important: if needed, disable the SP1/SP2 Pool/Core/Updates repositories manually and enable the new SP3 repositories:
    • zypper mr –disable <repo-alias>
    • zypper mr –enable <repo-alias>
  • The following repositories should be made available (please note this list contains the HAE add-on product):

  • SLES4SAP:~ # zypper lr -E

    # | Alias | Name | Enabled | Refresh

    —+———————————————+————————————–+———+——–

    1 | SLES-for-SAP-Applications 11.2.2-1.5 | SLES-for-SAP-Applications 11.2.2-1.5 | No | No

    2 | nu_novell_com:SLE11-HAE-SP3-Pool | SLE11-HAE-SP3-Pool | Yes | Yes

    3 | nu_novell_com:SLE11-HAE-SP3-Updates | SLE11-HAE-SP3-Updates | Yes | Yes

    4 | nu_novell_com:SLE11-SP2-WebYaST-1.3-Pool | SLE11-SP2-WebYaST-1.3-Pool | Yes | Yes

    5 | nu_novell_com:SLE11-SP2-WebYaST-1.3-Updates | SLE11-SP2-WebYaST-1.3-Updates | Yes | Yes

    6 | nu_novell_com:SLE11-SP3-SAP-Pool | SLE11-SP3-SAP-Pool | Yes | Yes

    7 | nu_novell_com:SLE11-SP3-SAP-Updates | SLE11-SP3-SAP-Updates | Yes | Yes

    8 | nu_novell_com:SLES11-SP3-Pool | SLES11-SP3-Pool | Yes | Yes

    9 | nu_novell_com:SLES11-SP3-Updates | SLES11-SP3-Updates | Yes | Yes
  • Then perform a dist upgrade by using the following command (example including the HAE add-on product)
    • zypper dup –from SLE11-HAE-SP3-Pool –from SLE11-HAE-SP3-Updates –from SLE11-SP2-WebYaST-1.3-Pool –from SLE11-SP2-WebYaST-1.3-Updates –from SLE11-SP3-SAP-Pool –from SLE11-SP3-SAP-Updates –from SLES11-SP3-Pool –from SLES11-SP3-Updates

      #add more SP3 catalogs here if needed, e.g. in case other add-on products are installed
  • zypper will report that it will delete the migration product and update themain products. Confirm the message to continue updating the rpm packages.
  • After the upgrade is finished, register the newproducts again:
    • suse_register -d 2 -a email=user@site.com -a regcode-sles=insert_valid_regcode -L /root/.suse_register.log
  • Reboot the system

Update to SLES for SAP 11 SP3 via patches by using Subscription Management Tool for SUSE Linux Enterprise

As an alternative to downloading the updates for each singleclient system from the Novell update server, it is possible to useSubscription Management Tool for SUSE Linux Enterprise to mirror theupdates to a local server.

This tool acts as Novell CustomerCenter proxy both for client registrations and as software updaterepository. The SMT documentation at http://www.suse.com/documentation/smt11/ gives an overview of its features as well as instructions on how to implement it.

Update via using a SLES for SAP Applications 11 SP3 installation media

Please obtain the ISO images from http://download.suse.com.

3) Update by booting from a SLES for SAP Applications 11 SP3 media

To start the standard update via DVD, reboot thecomputer with this medium in it’s DVD drive. Perform a systemupdate instead of a fresh installation. To achive this, select”Installation” -> Select language and keyboard layout -> Agree tothe License -> Select “Update an Existing System” instead of “New Installation”.

3.1) Update by booting off a SP3 network installationsource

It is also possible to provide the installation media vianetwork. The SLES for SAP 11 Service-Pack 3 media contains a complete product. So it can beadded to an installation server in the same way as every other SUSELINUX Enterprise product. The procedure on how to setup an installationserver and on how to addthe service pack is described in the product documentation. For SLES 11 havea look into chapter 14.2 of the deployment guide. The document isavailable online under http://www.suse.com/documentation/sles11/.

To start the update, go ahead as follows:

  • A bootable medium is needed to initialize the process. Booting vianetwork/PXE is also possible. For PXE boot configuration examples seechapter 14.3 in the SLES 11 deployment guide (online available at http://www.suse.com/documentation/sles11/ ).
  • Boot the machine and choose “Installation”.
  • Changethe installation source via the “F4” key and enter the IP and path to the installation source or select “SLP” if this protocol is configuredon your installation server.
  • Select “System Update” instead of performing a “New Installation”.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7023285: Failed dependencies during initial PAM 3.5 install on sles 12 (lsb >= 3.0)

This document (7023285) is provided subject to the disclaimer at the end of this document.

Environment

Privileged Account Manager 3.5
SUSE Linux Enterprise Server 12

Situation

During a brand new install of PAM 3.5 on SLES 12, the following error occurs:

# rpm -ihv netiq-npam-manager-3.5.0-linux-2.6-x86_64.rpm

error: Failed dependencies:

lsb >= 3.0 is needed by netiq-npam-manager-3.5.0-linux-2.6-x86_64.rpm

Resolution

  1. Please resolve this dependency by upgrading lsb to >= 3.0.

    From a terminal window on the server, please enter the following command:

    zypper in lsb

  2. Verify lsb is >= 3.0:

    rpm -qa | grep lsb

  3. Then proceed with the PAM install again.

Cause

SLES 12 or other Linux server has a version of lsb < 3.0 where PAM requires >= 3.0.

Status

Reported to Engineering

Additional Information

The following will display the version of lsb installed on the OS:
# rpm -qa | grep lsb

lsb-release-2.0-28.1.noarch
The following steps detail the GUI approach to upgrading this dependency:
  1. Open YaST Software Management
  2. Search for ‘lsb’
  3. Select what is available >= 3.0, in this case: ‘lsb5 – Linux Standard Base’
  4. Click Accept to Install
  5. Click Continue (automatic dependency resolutions)
  6. Click Finish

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022883: Cannot convert Sentinel to FIPS mode due to an issue with Mozilla NSS

This document (7022883) is provided subject to the disclaimer at the end of this document.

Environment

Sentinel

Situation

If you try to convert Sentinel (Server, RCM or RCE) to FIPS mode either during installation or post installation, an issue with the Mozilla NSS packages that are provided by the SLES 12 operating system prevent the conversion from being completed successfully. The conversion stops at the prompt for the FIPS keystore database password even though the specified password meets the expected criteria.

Resolution

To convert Sentinel to FIPS mode, perform the following steps:

1. Log in to Sentinel Server, RCM, or RCE as the root user.

2. Launch YaST software manager by running the following command:

yast sw_single

3. Search for the following packages and install or upgrade to the latest version:

mozilla-nss-tools

libfreebl3-hmac

libsoftokn3-hmac

4. Clean up the artifacts from the previous FIPS conversion attempts by running the following commands:

rm -rf /etc/opt/novell/sentinel/3rdparty/nss


rm /etc/opt/novell/sentinel/3rdparty/newpwfile

5. Retry FIPS conversion.

Cause

This is caused by an issue with the NSS packages used for the FIPS implementation in Sentinel.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022728: yast, lsblk or hwinfo hang after updating to kernel 3.0.101-108.35 on VMware machines.

This document (7022728) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)

SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 11 SP3)

Situation

lsblk, hwinfo, yast2 disk (the partitioning module) or other disk accessing applications (e.g. parted) hang.

Using strace to debug the process shows it hangs while accessing the virtual CD-ROM drive:

[…]

3570 lseek(5, 0, SEEK_CUR) = 0

3570 read(5, “0n”, 4096) = 2

3570 close(5) = 0

3570 munmap(0x7efd4917d000, 4096) = 0

3570 open(“/dev/sr0”, O_RDONLY

Resolution

The following kernel releases contain the required fixes:

SLES 11 SP4: 3.0.101-108.38.1

SLES 12 SP2: 4.4.120-92.70.1

SLES 12 SP3: 4.4.120-94.17.1

Change log entry:

– ide-cd: workaround VMware ESXi cdrom emulation bug (bsc#1080813).

Cause

A problem in the emulation code for the virtual CD-ROM drive.

Additional Information

Available Workaround:

Run the following command :

echo options cdrom autoclose=0 >> /etc/modprobe.d/99-local.conf

to create a module options file, then unload and reload the cdrom module again:

rmmod cdrom

modprobe cdrom

In case the CD-ROM drive is in use, this might fail and only a reboot will solve this situation.

If unloading and loading of the module doesn’t help you can try to attach CD-ROM device to the virtual machine so that the lsblk command is succesful. This can be achieved for example if you pretend to install the VMware tools and as a consequence it is mounted within the VM.

strace debug command:

The following command may be used to trace the lsblk output:

strace -f -o /tmp/lsblk.out lsblk

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022856: Daemon uuidd not installed after upgrade from SLES11 to SLES12

This document (7022856) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12

SUSE Linux Enterprise Server 11

Situation

After upgrading SLES11 to SLES12 the “uuidd” daemon/service is no longer installed

Resolution

Install the sap_server pattern instead single packages:

zypper in -t pattern sap_server


Cause

The name of the package has changed from “uuid-runtime” to “uuidd

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022174: YaST lan module: Client call failed with ‘Augeas parsing/serializing error: Iterated lens matched less than it should.

This document (7022174) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)

Situation

Running ‘yast lan’ module fails with a popup message to report a bug.

Within /var/log/YaST/y2log a detailed error message shows :

Relevant snippet from the log file :



Details: Augeas parsing/serializing error: Iterated lens matched less than it should at /usr/share/augeas/lenses/dist/hosts.aug:23.12-.42:


Resolution

Add a line break at the end of /etc/hosts as below :

echo >> /etc/hosts

Cause

The last line in /etc/hosts does not have line termination “n”.

This can be verified by doing e.g. ‘cat /etc/hosts’, and not seeing the bash prompt on a new line as a result.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: