No default route after boot with Hitachi / SLES for SAP system

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

Environment

SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 3

Situation

System is running SLES for SAP 12 SP3 on a Hitachi Advanced Server DS7000. A default route has been set in YaST and appears correctly in /etc/sysconfig/network/routes. However, after boot, no default route is in effect. The system cannot communicate beyond it's own subnet.

Restarting the network service adds the default route in, but the same issue happens at the next reboot.

Resolution

In this case, the administrator had installed some additional packages from Hitachi, known as "hitachi-provisioning-tools" and "hitachi-sap-hana-tunings". One of the things provided by those is a service known as "hitachi-sap-hana-network.service".

It was found that after disabling that service (i.e. the command: systemctl disable hitachi-sap-hana-network.service) the system would correctly have a default route after boot.

The administrator worked with Hitachi support to resolve his Hitachi configuration. SUSE does not know the full details of the Hitachi solution, but is publishing this information to help put troubleshooters of similar cases on the right track.

Cause

3rd party (Hitachi) tuning / configuration.

Disclaimer

This Support Knowledgebase provides a valuable tool for 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.