sapinst for CAL system - prerequisite check - could not evaluate hostname

[DavidK1]

Hi,

I have a question regarding "Unable to determine parameter "DNS domain name"" error when we call sapinst during part 2 "Install SAP S4/HANA", step 6 "Rename SAP system", following the guide "S/4HANA 1909 FPS1 Fully-Activated Appliance standard installation" to install the latest 2021 appliance.

https://blogs.sap.com/2020/06/30/s-4hana-1909-fps1-fully-activated-appliance-standard-installation/

The prerequisite checker also shows the following:

"Could not evaluate hostname check"

(Also see screenshots in comment below)

Can we ignore the "domain not determined" message, and "could not evaluate hostname check", and just install anyway?

Or should we create maybe a internal DNS server with some resolutions records? (its an Azure SUSE Linux VM with nameserver pointing to Azure nameserver 168.63.129.16 if I understand it correctly)

We have maintained the /etc/hostname and /etc/hosts according to the guide. (Part 2 step 1 Prepare system)

Thanks in advance,

David

[DavidK1]

Screenshots of the issue mentioned in the post:

[former_member369029]

Hello, Will you please try the following as suggested in the https://launchpad.support.sap.com/#/notes/0002575377

Localhost should not resolve into hostname but rather resolve into loopback (127.0.0.1).

1. a) Run niping -v -H localhost, it should resolve back to 127.0.0.1. or
   b) Run niping -v -H 127.0.0.1, it should resolve to 'localhost'.

   Also check Note: 1054467 - Local host name refers to loopback address

   If issue still exists with the hostname, you can check with your network team

Thanks, Ram.

[DavidK1]

Looks like niping test is ok, see terminal output below. I ended ignoring the host name check warning and just continued with the SAP system rename process (sapinst), and it worked fine. Don't know if its because "nslookup vhcals4hci" gives NXDOMAIN error, maybe due to the nameserver pointed to is the Azure VM general nameserver that can't resolve this address.
The system runs fine though...

But, thanks for the help!

Best regards,
David

NIPING TEST OUTPUT:

sid-hdb-s4h:s4hadm 3> niping -v -H localhost

Wed Apr 6 10:50:21 2022

*** WARNING => NiIInit: max number of open files per process (1024) < max number of NI handles (2048) [nixxi.cpp 8085]

Hostname/Nodeaddr verification:

===============================

Hostname of local computer: sid-hdb-s4h (NiMyHostName)

FQHN of local computer: localhost (NiGetOwnFQDN)

Lookup of hostname: sid-hdb-s4h (NiHostToAddr)

--> IP-Addr.: 127.0.0.1

Lookup of IP-Addr.: 127.0.0.1 (NiAddrToHost)

--> Hostname: localhost

Lookup of hostname: localhost (NiHostToAddr)

--> IP-Addr.: 127.0.0.1

Lookup of IP-Addr.: 127.0.0.1 (NiAddrToHost)

--> Hostname: localhost

sid-hdb-s4h:s4hadm 4> niping -v -H 127.0.0.1

Wed Apr 6 10:51:20 2022

*** WARNING => NiIInit: max number of open files per process (1024) < max number of NI handles (2048) [nixxi.cpp 8085]

Hostname/Nodeaddr verification:

===============================

Hostname of local computer: sid-hdb-s4h (NiMyHostName)

FQHN of local computer: localhost (NiGetOwnFQDN)

Lookup of hostname: sid-hdb-s4h (NiHostToAddr)

--> IP-Addr.: 127.0.0.1

Lookup of IP-Addr.: 127.0.0.1 (NiAddrToHost)

--> Hostname: localhost

Lookup of hostname: 127.0.0.1 (NiHostToAddr)

--> IP-Addr.: 127.0.0.1

Lookup of IP-Addr.: 127.0.0.1 (NiAddrToHost)

--> Hostname: localhost