saptune 3 Is on the Horizon
For quite some time we haven’t released a new version of saptune. That didn’t mean that development has stopped. Far from it! The last months have been busy to finalize the upcoming version 3, which brings new features customers and partners requested.
It is currently in our QA and will be available in a few weeks.
For which releases saptune 3 will be available?
As always each release of “SLES for SAP Applications” still under support will get the new saptune:
- SUSE Linux Enterprise Server for SAP Applications 12 SP3
- SUSE Linux Enterprise Server for SAP Applications 12 SP4
- SUSE Linux Enterprise Server for SAP Applications 12 SP5
- SUSE Linux Enterprise Server for SAP Applications 15
- SUSE Linux Enterprise Server for SAP Applications 15 SP1
- SUSE Linux Enterprise Server for SAP Applications 15 SP2
- SUSE Linux Enterprise Server for SAP Applications 15 SP3
What is new?
Additional SAP Notes
- 1656250 – SAP on AWS: Support prerequisites – only Linux Operating System IO Recommendations
- 2993054 – Recommended settings for SAP systems on Linux running in Azure virtual machines
- 3024346 – Linux Kernel Settings for NetApp NFS
- 900929 – Linux: STORAGE_PARAMETERS_WRONG_SET and ‘mmap() failed’
The new Cloud SAP Notes 1656250 and 2993054 are part of all Solutions (except BOBJ).
Due to the new tagging feature (see below), they only get applied on a system that is a cloud instance of the appropriate vendor.
This allows you always to use the same Solutions, no matter if you run on hardware or in the cloud. Simply choose the one designed for your SAP product!
The new SAP Note 900929 is part of NETWEAVER and S4HANA-APPSERVER Solutions.
Detection of sysctl conflicts
Most support cases are about conflicting saptune settings with entries in e.g.
Saptune 3 will now check, if sysctl parameters set by an applied SAP Note are also present in sysctl files. This should help to detect possible dormant misconfiguration issues.
Here an example:
SAPNote, Version | Parameter | Expected | Override | Actual | Compliant --------------------+-------------------------------+-----------+-----------+---------+----------- 1410736, 6 | net.ipv4.tcp_keepalive_intvl | 75 | | 75 | yes  1410736, 6 | net.ipv4.tcp_keepalive_probes | 9 | | 9 | yes  1410736, 6 | net.ipv4.tcp_keepalive_time | 300 | | 300 | yes  (no change)  parameter is additional defined in sysctl config file /usr/lib/sysctl.d/99-sysctl.conf(100)  parameter is additional defined in sysctl config file /usr/lib/sysctl.d/99-sysctl.conf(10)  parameter is additional defined in sysctl config file /usr/lib/sysctl.d/99-sysctl.conf(300)
Check script to verify setup
The second most cause for support cases has been an incorrect setup of saptune: forgetting to enable services, mixups with sapconf, wrong tuned profiles, something like that.
Now saptune comes with a check script to verify the correct setup:
# saptune_check This is saptune_check v0.2.1. It verifies if saptune is set up correctly. Please keep in mind: - This tool does not check, if the tuning itself works correctly. - Follow the hints from top to down to minimize side effects. Checking saptune ================ [NOTE] saptune package has version 3.0.0 [ OK ] System is in status "running" [ OK ] configured saptune version is 3 [ OK ] sapconf.service is inactive [ OK ] sapconf.service is disabled [ OK ] saptune.service is active [ OK ] saptune.service is enabled [NOTE] tuned profile is 'virtual-guest' [ OK ] tuned.service is inactive [ OK ] tuned.service is disabled Saptune is set up correctly.
Best run it always after you have changed your saptune setup.
Do you want your own version of a e.g. HANA Solution tailored to your needs? Do you want your own custom Notes be part of such a Solution?
No problem. With saptune 3 allows you create your own Solutions.
# saptune solution list All solutions (* denotes enabled solution, O denotes override file exists for solution, C denotes custom solutions, D denotes deprecated solutions): ... S4HANA-DBSERVER - 941735 1771258 1980196 2578899 2684254 2382421 2534844 2993054 1656250 SAP-ASE - 941735 1410736 1680803 1771258 2578899 2993054 1656250 * C myHANA - 941735 1771258 1980196 2578899 2684254 2382421 2534844 DC1
Tagging of configuration sections (architecture, storage vendors, etc.)
Saptune 3 supports so-called tags to apply configuration sections only if certain conditions are met.
The newly added SAP Notes for AWS and Azure are making use of it. The settings get only applied if the system is a cloud instance:
# saptune note show 2993054 ... [sysctl:csp=azure] net.ipv4.tcp_keepalive_time = 300 ...
- OS version
- System vendor and model (everything in
- Cloud vendor
- Block device details
Of cause tags can also be used in custom Notes as well as in overrides.
Saptune packages can come with binary changes (bug fixes, new features) as well as with configuration changes (new or changed SAP Notes and Solutions). This can cause challenges for customers.
On one hand they want to install a needed fix, but on the other hand they don’t want or can introduce configuration changes due to internal change management processes.
To address this, saptune 3 introduces staging.
Staging decouples binary changes from SAP Note and Solution changes.
If staging has been enabled, SAP Note or Solution changes are placed into a staging area during a package upgrade. Later you can review the changes and apply them partially or full when ever you want. This has the advantage that you can install bug fixes, but must not worry about changes in your system configuration.
What has changed?
Saptune 3 doesn’t use
tuned anymore! It now comes with it’s own systemd service.
This has implications for setting up saptune!
With saptune 2 it was necessary to enable and start
tuned.service and set the saptune profile.
The recommended way was to use
saptune daemon start, which took not only care of that, but also disabled sapconf, if it was in use.
With saptune 3 this command still does it’s job. It now enables and starts
saptune.service and disables sapconf and also
tuned. So, if you use this command already in your scripts or deployments everything will keep working.
If you configure
tuned directly, than you have to adapt your method!
saptune v1 has been removed
I really hope nobody is using v1 anymore. The configuration is hopelessly outdated and does not reflect current SAP recommendations. Saptune 2 kept it to allow customers to take their time to switch to version 2, but it was marked as deprecated.
saptune version returns
current active saptune version is '1', you have to act now! Details about how to migrate can be found in the man page saptune-migrate(7).
Updated SAP Notes
The following SAP Notes have received updates:
- 1680803 – Sybase – SAP Adaptive Server Enterprise
- 1771258 – Linux: User and system resource limits
- 2382421 – Optimizing the Network Configuration on HANA- and OS-Level
- 2578899 – SUSE LINUX Enterprise Server 15: Installation notes
- 1984787 – SUSE LINUX Enterprise Server 12: Installation notes
- 2684254 – SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications 15
- 2205917 – SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12
- 2382421 – Optimizing the Network Configuration on HANA- and OS-Level
New saptune commands
We have further enhanced saptune’s commands. Saptune 3 brings among others:
- New commands to handle the saptune systemd service:
saptune service start|status|stop|restart|takeover|enable|disable|enablestart|disablestop
- You can now edit custom Notes easily.
saptune note edit NoteID
- The new feature of custom Solutions brings a list of new commands:
saptune solution customise|create|edit|revert|show|delete SolutionName
saptune solution rename SolutionName newSolutionName
- The new staging feature also introduces a whole bunch of new commands.
saptune staging status|enable|disable|is-enabled|list|diff|analysis|release
saptune staging analysis|diff NoteID...|SolutionID...|all
saptune staging release [--force|--dry-run] NoteID...|SolutionID...|all
- You can now get a much more detailed overview about saptune’s status.
Can I just upgrade or do I have to make preparations ?
You can just upgrade the package.
Keep in mind, that we ship updated and new SAP Notes and Solutions, so you should run a
saptune note verify after upgrading to check if all recommendations are still met!
I use deployment and configuration scripts. Do I have to take care of something?
This depends, how you have implemented the saptune setup.
If you use
saptune daemon start everything is fine.
If you configure
tuned directly, then this will not work anymore!
See `No tuned!` above!
With the release the SLES for SAP Guides (https://documentation.suse.com/) will be updated as well as SAP Note ‘1275776 – Linux: Preparing SLES for SAP environments‘.
Additionally I’ll start a video series on our SUSE Products channel on YouTube soon to explain some aspects of saptune in detail.
we have recently updated a host from SLES 12 to SLES 15 and that automatically updated SAPTUNE from version 1 to version 3.
Now, when we run saptune_check we face errors. There is not yet a sapnote to handle this case. Should we raise a sap incident for support in this case?
I guess it looks like this:
With version 1 having recommendations out of date for 2 years, the support in saptune3 has been removed.
A migration is described in the man page "saptune-migrate", but such a migration needs to be done before an update to saptune3.
Easiest way would be a fresh start. Remove the saptune package and install version 3 it again. The deinstallation removes all legacy files. After the installation you have to configure saptune, meaning applying a Solution and/or Notes and enable it by running "saptune service takeover".
If you run into further problems, you can rise a SAP incident for the component BC-OP-LNX-SUSE.