Solution : https://service.sap.com/sap/support/notes/21151 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues encountered in multi-homed SAP system installations, where multiple network interfaces cause communication problems among various server components like Application Servers, Message Servers, and Database Servers. Key functions such as transaction SM51 may not perform as expected, and the activation of SAPHTTP or SAPFTP could fail on the frontend. The primary cause of these issues stems from improper TCP/IP configuration across these network adapters. The solution recommended by SAP includes ensuring all Application and Database Servers are reachable through a correctly assigned network interface and hostname, adhering strictly to defined IP configurations, restricting hostname assignments, and using static IP routes for dedicated server networks. Proper implementation of these solutions as per the attached Network Integration document is crucial.
Key words :
solution sap strongly recommends, seperate fast server network, server-internal network traffic, tcp/ip network configuration, high availability configurations, profile parameter saplocalhost, static routes inside, static route points, tcp/ip settings, multiple network adapters
Related Notes :
| 1135491 | RSSTAT98 - Inconsistent host name when setting up SAPWLSERV |
| 611361 | Hostnames of SAP servers |
| 364552 | Loadbalancing does not find application server |
| 126498 | startsap/stopsap hangs for netstat -i |
| 75226 | Questionnaire: addressing in switchover environment |
| 10548 | CCMS: BRBACKUP start fails, hostname > 8 |
| 10456 | Error establishing connection to R/3 servers (SM51) |