Network Plane Planning

The network information needs to be planned based on application scenarios and SAP NetWeaver planning.

The network segments and IP addresses are for reference only. You can configure it based on site requirements.

Network plane planning in the standard deployment scenario where the SAP NetWeaver system is accessed using the NAT server with an EIP bound

In this scenario, an SAP NetWeaver instance node uses only one NIC for network communication between servers and clients. Figure 1 shows the network planning in the standard deployment mode.

Figure 1 Network planning in the standard deployment mode

Table 1 shows the planned network information.

**Table 1** Network planning in the single-node scenario where HA is not required and an EIP is used to access the NAT server
Parameter	Description	Example Value
IP address of the server/client plane	Specifies the IP address of the primary NIC plane. The central instance communicates with the SAP HANA database or the SAP GUI client using this IP address.	Central instance: 10.0.3.2 NAT server: 10.0.3.202 Database server: 10.0.3.3
EIP	A public IP address, which allows you to access the NAT server	Automatically allocated by the public cloud

Network plane planning (using a VPN to access the SAP NetWeaver system in the distributed deployment scenario)

In this scenario, an SAP NetWeaver instance node uses only one NIC for network communication between servers and clients. Figure 2 shows the network plane planning in distributed deployment mode where SAP NetWeaver is accessed using a VPN.

Figure 2 Network planning in distributed deployment mode

Table 2 shows the network information in distributed deployment mode.

**Table 2** Network information planning (distributed VPN deployment mode)
Parameter	Description	Example Value
IP address of the server/client plane	Specifies the IP address of the primary NIC plane. The ASCS instance communicates with the SAP HANA database or the SAP GUI client using this IP address.	ASCS instance: 10.0.3.2 Database server: 10.0.3.3 SAP application server: 10.0.3.4

Network plane planning

In this scenario, the ASCS node uses two NICs for the server/client network communication plane and internal communication plane, respectively.

The IP addresses of the server/client plane and internal heartbeat communication plane must belong to different subnets.

Figure 3 shows the network planning in distributed HA deployment mode where SAP NetWeaver is accessed using a VPN.

Figure 3 Network planning in distributed HA deployment mode

**Table 3** Network information planning (distributed and HA EIP deployment mode)
Parameter	Description	Example Value
IP address of the server/client plane	Specifies the IP address of the primary NIC plane. The active and standby ASCS nodes communicate with the SAP GUI and SAP HANA databases using this IP address.	ASCS active node: 10.0.3.2 ASCS standby node: 10.0.3.13 SAP GUI: 10.0.3.4 PAS & HANA: 10.0.3.5 AAS & HANA: 10.0.3.6
IP address of the internal heartbeat communication plane	The active and standby ASCS nodes use this network plane to communicate with each other. The active and standby SAP HANA databases use this network plane to communicate with each other.	ASCS active node: 10.0.4.2 ASCS standby node: 10.0.4.3 SAP HANA database server active node: 10.0.4.6 SAP HANA database server standby node: 10.0.4.7