21151 - Multiple Network Adapters in SAP Servers
2
SAP Note Header Data Symptom l Installation of a new SAP system on computers with more than one network interface. l Communication problems between the SAP servers (Application Servers, Message Server, database server). l Some functions showing the status of the SAP installation do not work properly (e.g. transaction SM51). l Activation of SAPHTTP or SAPFTP on the frontend may fail. l The SAP message server will distribute hostnames that are not accessible by the clients (e.g. saplogon and SAP Web Dispatcher) Other Terms Network, Interface, Adapter, TCP/IP, Routing, Route, Installation, Application Server, Message Server, Database Server, Multihomed Reason and Prerequisites If your SAP servers are equipped with multiple network adapters it is important to configure the TCP/IP settings according to the requirements imposed by the SAP system. Otherwise some functions of the SAP system may fail. Solution SAP strongly recommends that you configure the SAP server computers according to the following rules: 1. Every SAP server must have a network interface that can be reached by all Application Servers of the same SAP system and by all frontend computers and other communication partners. This can always be achieved by appropriate IP configuration. 2. The hostname of an SAP Application Server (i.e. the output of the command "hostname") must be assigned to the IP address of the network interface in item 1). Restrictions on the hostname, mechanisms for the assignement between hostnames and IP addresses (e.g. hosts file, DNS) and exceptions that apply to high availability configurations are discussed in the "Network Guide" described below and in related notes. The profile parameter SAPLOCALHOST may be used to make the SAP system believe it runs on a different hostname. 3. The SAP system and all frontend access and communication interfaces have to be configured using only the hostnames of item 2) or the IP address of item 1). No other IP name or IP address of an SAP server may appear in any table or configuration file of the SAP system. This rule ensures that every communication partner can actually reach the IP address that the hostname resolves into. 4. If the SAP servers are connected via a seperate fast server network, static IP routes have to be used to route the server-internal network traffic over this network. Attention: Do not use static routes inside a Microsoft Cluster (MSCS). It may happen that after a failover a static route points to local devices, this configuration leads to connection problems on Windows. 5. The Document "Network Integration of SAP Servers" describes the TCP/IP network configuration for SAP Servers in detail. Please find this document attached to this note. 21151 - Multiple Network adapters in SAP Servers Version 32 Validity: 10.11.2008 - active Language English (Master) Released On 11.11.2008 13:56:35 Release Status Released for Customer Component BC-NET Network Infrastructure BC-CST-NI Network Interface Priority Recommendations / Additional Info Category Consulting Other Components
-
Upload
suwatchai-manchansa -
Category
Documents
-
view
227 -
download
0
description
21151 - Multiple Network Adapters in SAP Servers
Transcript of 21151 - Multiple Network Adapters in SAP Servers
-
SAP Note
Header Data
Symptom
l Installation of a new SAP system on computers with more than one network interface.
l Communication problems between the SAP servers (Application Servers, Message Server, database server).
l Some functions showing the status of the SAP installation do not work properly (e.g. transaction SM51).
l Activation of SAPHTTP or SAPFTP on the frontend may fail.
l The SAP message server will distribute hostnames that are not accessible by the clients (e.g. saplogon and SAP Web Dispatcher)
Other Terms
Network, Interface, Adapter, TCP/IP, Routing, Route, Installation, Application Server, Message Server, Database Server, Multihomed
Reason and Prerequisites
If your SAP servers are equipped with multiple network adapters it is important to configure the TCP/IP settings according to the requirements imposed by the SAP system. Otherwise some functions of the SAP system may fail.
Solution
SAP strongly recommends that you configure the SAP server computers according to the following rules:
1. Every SAP server must have a network interface that can be reached by all Application Servers of the same SAP system and by all frontend computers and other communication partners. This can always be achieved by appropriate IP configuration.
2. The hostname of an SAP Application Server (i.e. the output ofthe command "hostname") must be assigned to the IP address of the network interface in item 1). Restrictions on the hostname, mechanisms for the assignement between hostnames and IP addresses (e.g. hosts file, DNS) and exceptions that apply to high availability configurations are discussed in the "Network Guide" described below and in related notes. The profile parameter SAPLOCALHOST may be used to make the SAP system believe it runs on a different hostname.
3. The SAP system and all frontend access and communication interfaces have to be configured using only the hostnames of item 2) or the IP address of item 1). No other IP name or IP address of an SAP server may appear in any table or configuration file of the SAP system. This rule ensures that every communication partner can actually reach the IP address that the hostname resolves into.
4. If the SAP servers are connected via a seperate fast server network, static IP routes have to be used to route the server-internal network traffic over this network. Attention: Do not use static routes inside a Microsoft Cluster (MSCS). It may happen that after a failover a static route points to local devices, this configuration leads to connection problems on Windows.
5. The Document "Network Integration of SAP Servers" describes the TCP/IP network configuration for SAP Servers in detail. Please find this document attached to this note.
21151 - Multiple Network adapters in SAP Servers
Version 32 Validity: 10.11.2008 - active Language English (Master)
Released On 11.11.2008 13:56:35 Release Status Released for Customer Component BC-NET Network Infrastructure
BC-CST-NI Network Interface
Priority Recommendations / Additional Info Category Consulting
Other Components
-
Validity
This document is not restricted to a software component or software component version
References
This document refers to:
SAP Notes
This document is referenced by:
SAP Notes (11)
Attachments
1135491 RSSTAT98 - Inconsistent host name when setting up SAPWLSERV 1033987 Remote login using NAT or SAP router fails
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)
126498 startsap/stopsap hangs for netstat -i 10548 CCMS: BRBACKUP start fails, hostname > 8 10456 Error establishing connection to R/3 servers (SM51) 364552 Loadbalancing does not find application server 75226 Questionnaire: addressing in switchover environment 1135491 RSSTAT98 - Inconsistent host name when setting up SAPWLSERV 954717 Error in NiMyAddrVerify 1033987 Remote login using NAT or SAP router fails 1054467 Local host name refers to loopback address 611361 Hostnames of SAP servers 581509 Reasons for "timeout during allocate"
File Name File Size (KB) Mime Type
Network_Integration.zip 765 application/x-zip-compressed
SAPGUI_INFRA.zip 323 application/x-zip-compressed
