Solution : https://service.sap.com/sap/support/notes/129997 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with incorrect hostname displays in SM51 and other system components, where servers may appear under different names or workload data shows under erroneous hostnames. The root cause is linked to TCP/IP communications within the R/3 system, involving both internal and external connections. Correct hostname and IP address resolution are paramount, requiring that each server's hostname resolves to an IP and vice versa, consistently across all R/3 system servers. Solutions include ensuring proper entries in the /etc/hosts file or DNS configurations, with specific attention to "A" and "PTR" records in DNS. The SAP tool "niping" is recommended for verifying hostname resolutions.
Key words :
/3 server- workload data appears, reverse lookup zone file, resolution hostname -> ip address -> back, correct zone file, profile parameter saplocalhost, symptom - wrong hostnames, tcp/ip externally, correct hostname resolution, newest niping version, external communication partner
Related Notes :
| 1624061 | Use of virtual TCP/IP host names |
| 1342666 | Trace entries: NiHsLGetNodeAddr: to get |
| 1282975 | Use of virtual TCP/IP host names in Windows |
| 1135491 | RSSTAT98 - Inconsistent host name when setting up SAPWLSERV |
| 962955 | Use of virtual TCP/IP host names |
| 611361 | Hostnames of SAP servers |
| 530633 | NWCHECK error when resolving names for 'localhost' |
| 124562 | Hostname resolution problems (DNS timeouts) |