Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
RHEL 7 sap-hana and sap-hana-vmware tuned profiles using eth0
Version-Release number of selected component (if applicable):
RHEL 7 sap-hana and sap-hana-vmware tuned profiles
How reproducible:
Steps to Reproduce:
1. Looking at script.sh for the profiles
Actual results:
start() {
ethtool -K eth0 lro off
return 0
}
stop() {
ethtool -K eth0 lro on
return 0
}
Expected results:
Instead of eth0 should be RHEL 7 NIC name
Additional info:
Comment 3Jaroslav Škarvada
2017-09-19 14:04:32 UTC
Comment 5Jaroslav Škarvada
2017-09-19 14:56:24 UTC
Upstream commit fixing the problem:
https://github.com/redhat-performance/tuned/pull/70/commits/b970238a3da96caa2b6e77ad2a56fa65fe3a9661
There is now sap-hana-vmware-variables.conf file with the variable 'sap_hana_vmware_nic', just set it to the client NIC (or NICs) if you want the tuning, e.g. for eth0:
sap_hana_vmware_nic=eth0
Or for eth0, eth1:
sap_hana_vmware_nic=eth0, eth1
Or for anything with the eth prefix:
sap_hana_vmware_nic=eth*
Or for anything else than eth1:
sap_hana_vmware_nic=!eth1
I.e. anything the Tuned syntax supports can be used.
=============================================
Verified in:
tuned-2.9.0-1.el7.noarch
tuned-profiles-sap-hana-2.9.0-1.el7.noarch
=============================================
>> Patch was applied. Source code corresponds to patches.
# ls /etc/tuned/
active_profile bootcmdline profile_mode recommend.d sap-hana-vmware-variables.conf tuned-main.conf
>> There is file sap-hana-vmware-variables.conf to specify interface.>> 1. TEST - no NIC will be applied
# cat /etc/tuned/sap-hana-vmware-variables.conf
sap_hana_vmware_nic=!*
# tuned-adm profile sap-hana-vmware
# cat /var/log/tuned/tuned.log | grep 'tuned.plugins.base' | grep 'instance net'
2018-01-18 05:42:01,888 WARNING tuned.plugins.base: instance net: no matching devices available
# ethtool -k eno1 |grep large-receive-offload
large-receive-offload: on
# ethtool -k eno2 |grep large-receive-offload
large-receive-offload: on
>> Profile sap-hana-vmware was applied. There was specified that no NIC would be set, so LRO was not set to 'off' value.>> 2. TEST - all NIC will be applied
# cat /etc/tuned/sap-hana-vmware-variables.conf
sap_hana_vmware_nic=*
# tuned-adm profile sap-hana-vmware
# cat /var/log/tuned/tuned.log | grep 'tuned.plugins.base' | grep 'instance net'
2018-01-18 06:05:37,621 INFO tuned.plugins.base: instance net: assigning devices eno1, eno2
# ethtool -k eno1 |grep large-receive-offload
large-receive-offload: off
# ethtool -k eno2 |grep large-receive-offload
large-receive-offload: off
>> Profile sap-hana-vmware was applied. There was specified that all NIC would be set, so LRO was disabled (set to 'off' value).
# tuned-adm profile balanced
# ethtool -k eno1 |grep large-receive-offload
large-receive-offload: on
# ethtool -k eno2 |grep large-receive-offload
large-receive-offload: on
>> When we applied another profile, LRO changed to 'on' values.>> 3. TEST - only one NIC will be applied
# cat /etc/tuned/sap-hana-vmware-variables.conf
sap_hana_vmware_nic=eno2
# tuned-adm profile sap-hana-vmware
# cat /var/log/tuned/tuned.log | grep 'tuned.plugins.base' | grep 'instance net'
2018-01-18 06:08:27,695 INFO tuned.plugins.base: instance net: assigning devices eno2
# ethtool -k eno1 |grep large-receive-offload
large-receive-offload: on
# ethtool -k eno2 |grep large-receive-offload
large-receive-offload: off
=============================================
Reproduced in:
tuned-2.8.0-5.el7.noarch
tuned-profiles-sap-hana-2.8.0-5.el7.noarch
=============================================
This bug is new feature. There isn't possible to disable LRO for specified NIC.
These variants of sap-hana-vmware-variables.conf were tested:
sap_hana_vmware_nic=!*
sap_hana_vmware_nic=*
sap_hana_vmware_nic=eno1, eno2
sap_hana_vmware_nic=eno2
sap_hana_vmware_nic=eno1, !eno2
sap_hana_vmware_nic=!eno1
Tereza, thanks for the verification and for clarifying how to correctly configure the sap-hana-vmware-variables.conf. I wasn't aware that the file is actually located in /etc/tuned/.
This should be documented in a kbase or something so that we can reference it in the SAP documentation.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0879
Comment 18Red Hat Bugzilla
2023-09-15 00:03:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Description of problem: RHEL 7 sap-hana and sap-hana-vmware tuned profiles using eth0 Version-Release number of selected component (if applicable): RHEL 7 sap-hana and sap-hana-vmware tuned profiles How reproducible: Steps to Reproduce: 1. Looking at script.sh for the profiles Actual results: start() { ethtool -K eth0 lro off return 0 } stop() { ethtool -K eth0 lro on return 0 } Expected results: Instead of eth0 should be RHEL 7 NIC name Additional info: