Solution : https://service.sap.com/sap/support/notes/1624061 (SAP Service marketplace login required)
Summary :
To facilitate seamless transitions across hardware in an SAP environment, configuring virtual host names enables the decoupling of SAP server software from their physical network identities. This best practice, essential for settings like failover clusters, requires setting up a new IP and host name that are not bound to physical server assets, ensuring flexibility in server moves. Detailed steps include adding a new TCP/IP interface and registering it in DNS or through configuration tools. Additionally, SAP instance modification via start and instance profiles ensures SAP processes recognize the virtual network identity, enhancing adaptive infrastructure and minimizing downtime. Caution is advised in avoiding TCP alias names to prevent resolution conflicts.
Key words :
> saplocalhostfull = < full qualified virtual host, ip addresses <-> tcp/ip host, tcp/ip host table entries, ip address -> tcp/ip host, decouple end-user communication, resolutions tcp/ip host, corp physhost <ip2> virthost1, virtualize physical host names, tcp network alias names, sap netweaver versions lower
Related Notes :
| 1282975 | Use of virtual TCP/IP host names in Windows |
| 962955 | Use of virtual TCP/IP host names |
| 773830 | FQHN determination in ICM |
| 611361 | Hostnames of SAP servers |
| 129997 | Hostname and IP address lookup |