Network Plane Planning

The network information needs to be planned based on application scenarios and SAP S/4HANA planning. The network segments and IP addresses are for reference only. You can configure it based on site requirements.

In HA 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 1 shows the network planning in HA scenario.

Figure 1 Network planning in HA scenario

**Table 1** Network planning
Parameter	Description	Example Value
IP address of the server/client plane	Specifies the IP address of the primary NIC plane. The ASCS and ERS nodes communicate with NAT Server and SAP HANA using this IP address.	PAS & ASCS node: 10.0.3.12 AAS & ERS node: 10.0.3.13 NAT Server: 10.0.3.4 Active SAP HANA node: 10.0.3.5 Standby SAP HANA node: 10.0.3.6
IP address of the internal heartbeat communication plane	The ASCS and ERS 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.	PAS & ASCS node: 10.0.4.2 AAS & ERS node: 10.0.4.3 Active SAP HANA node: 10.0.4.6 Standby SAP HANA node: 10.0.4.7

VPC and Subnet Planning

The VPC and subnet planning is the same as that for SAP HANA. For details, see Single-Node Scenario Where HA Is Required.

Host Planning

SAP application system ID (SID): PRD

SAP HANA SID: HAP

Table 2 describes the SAP host planning.

**Table 2** SAP host planning
Host Name	IP Address	Active Heartbeat	Virtual IP Address	Type	Instance number	SID
hana01	10.0.3.5	10.0.4.6	10.0.3.7	DB Server 01	00	HAP
hana02	10.0.3.6	10.0.4.7	10.0.3.7	DB Server 02	00	HAP
S/4HANA-0001	10.0.3.12	10.0.4.2	10.0.3.14	ASCS Instance/PAS Instance	01	PRD
S/4HANA-0002	10.0.3.13	10.0.4.3	10.0.3.14	ERS Instance/AAS Instance	02	PRD