Deploying your infrastructure

Use the following information to deploy and set up SAP HANA and SAP NetWeaver on IBM Cloud® Virtual Servers for Virtual Private Cloud.

Setting up a Virtual Private Cloud (VPC) and subnet

Before you can create a virtual server, you must create a VPC.

The following steps summarize the setup of VPC and subnets, which is detailed further in the Create an IBM Cloud VPC.

Click Menu icon > VPC Infrastructure > Network > VPCs
Click Create.
Enter a unique Name for the VPC.
Select a Resource group. Use resource groups to organize your account resources for access control and billing purposes. For more information, see Best practices for organizing resources in a resource group and What makes a good resource group strategy?.
Optional: Enter tags to help you organize and find your resources. You can add more tags later. For more information, see Working with tags.
Select whether the Default security group allows inbound SSH and ping traffic to virtual server instances in this VPC. We'll configure more rules for the default security group later.
Optional: Classic access. Select whether you want to enable your VPC to access classic infrastructure resources. For more information, see Setting up access to classic infrastructure.

You can only enable a VPC for classic access when it is created. You cannot update a VPC to add or remove classic access. In addition, you can have only one classic access VPC in your account at any time.
Optional: Default address prefixes. Disable this option if you don't want to assign default subnet address prefixes to each zone in your VPC. After you create your VPC, you can go to its details page and set your own subnet address prefixes. If you do disable this option, the New subnet for VPC section will be hidden, and will require manual definition after the VPC is created. Leave the value default.

New subnet for VPC

Enter a unique Name for the VPC subnet.
Select a Resource group for the subnet.
Select a Location for the subnet. The location consists of a region and a zone.

The region that you select is used as the region of the VPC. All additional resources that you create in this VPC are created in the selected region.
Enter an Address prefix, Number of addresses, and an IP range for the subnet. The IP range is entered in CIDR notation, for example: 10.240.0.0/24. In most cases, you can use the default IP range. If you want to specify a custom IP range, you can use the IP range calculator to select a different address prefix or change the number of addresses.

A subnet cannot be resized after it has been created.
Attach a public gateway to the subnet if you want to allow all attached resources to communicate with the public internet.

You can also attach the public gateway after you create the subnet.
Click Create virtual private cloud.

Manually defining your subnets

If you disabled Default address prefixes, which hid the New subnet for VPC section on the VPC ordering page, you need to manually define your subnets before provisioning your Virtual Servers for VPC. Use the following steps to set up your subnets if you didn't do so when you set up your VPC.

Click Menu icon > VPC Infrastructure > Subnets > New Subnet.
Enter a unique Name and select the Virtual private cloud that it's to be associated with.
Select a Resource group.
Select Location. The location consists of a region and zone. If you're manually creating the initial subnet, versus creating it when you created your VPC, the region (location) that you select is used as the region of the VPC. All additional resources that you in this VPC are created in the selected region.

If you created a subnet when you created your VPC, more subnets must be created in the same region. You can create multiple subnets within VPC zones.
Click Create subnet.

Provisioning your Intel virtual server

Before you can create a virtual server, you must create the VPC and you must create an SSH key that you add to the server instance during its creation - see more details on SSH keys with virtual servers.

Use the following steps to order your virtual server and necessary components. For more information about creating a virtual server, see Creating virtual server instances by using the IBM Cloud console.

Log in to the IBM Cloud console with your unique credentials.
Click Menu icon > VPC Infrastructure > Virtual server instances.
Click Create.
Enter a unique Name for the virtual server, which becomes the hostname. SAP hostnames must consist of a maximum of 13 alpha-numeric characters. For more information about SAP hostnames, see SAP Notes 611361 and 129997.
Choose a Resource group.

The resource group can't be changed after the virtual server is created.
Optional: Enter tags to help you organize and find your resources. You can add more tags later. For more information, see Working with tags.
Select the same Location in which you created your VPC and subnets. The location consists of a region and zone.
Select your preferred Operating System from either Windows Server, Red Hat Linux or SUSE Linux to run SAP Netweaver, or from Red Hat or SUSE to run SAP HANA; you find the Linux versions in the tile Catalog image > ...-sap-hana-... as the OS images for SAP HANA, or Catalog image > ...-sap-applications-... as the OS images for SAP NetWeaver.
Select a Profile based on the guidance detailed in Intel Virtual Server certified profiles for SAP HANA or Intel Virtual Server certified profiles for SAP NetWeaver, which lists the profiles that are certified for SAP HANA and SAP NetWeaver.
Select the SSH key you want to add to the virtual server. For this step, you can create a new SSH key.
Click New volume for Data volumes. Data volumes are required.
- For SAP HANA, these volumes must meet special KPI needs that are defined by SAP and are mandatory. See Storage specifications - Intel Virtual Server (Gen2) certified profiles for SAP HANA or Storage design considerations to learn these special needs and how you should configure the data volumes.
- For SAP NetWeaver, these volumes are based on the requirements of the installed SAP NetWeaver instance. The standard tiered options are 3K, 5K, and 10K IOPS, and custom IOPS. These options can be used to attune to the specific requirements.
You can enable Auto Delete to automatically delete the data volume if the virtual server is deleted. This option is not recommended.
Attach the appropriate data volumes to your virtual server.
Under Networking, select the Virtual private cloud in which to attach the virtual server.
Under Network interfaces, the first virtual network interface is shown attached to the default subnet of the VPC. This can be amended as required.
Click Create virtual server instance. After the Virtual Servers for VPC is provisioned and ready for SSH logon, you can begin installing SAP HAAN or SAP NetWeaver applications.

Table 1 is a summary of the fields and values that are used to provision Virtual Servers for VPC.

Table 1. Instance provisioning selections
Field	Value
Name	Unique name for your virtual server.
Virtual private cloud	Specify the VPC where you want to create your virtual server.
Resource group	Use resource groups to organize your account resources for access control and billing purposes.
Location	Locations are composed of regions (specific geographic areas) and zones (fault tolerant data centers within a region). Select the location where you want to create your virtual server.
Operating System	Linux distribution for SAP HANA workloads, select Catalog image > `...-sap-hana-...` Linux distribution for SAP HANA workloads, select Catalog image > `...-sap-applications...` Windows Server for SAP NetWeaver workloads, select Windows Server . Choose an operating system version that is supported by SAP as documented in SAP Note 2927211
Profile	Select one of the profiles outlined in Intel Virtual Server certified profiles for SAP HANA or Intel Virtual Server certified profiles for SAP NetWeaver.
SSH Key	You must select an existing SSH key or upload a new SSH key before you can create the instance. SSH keys are used to securely connect to a running instance.
	Note: Alpha-numeric combinations are limited to 100 characters. For more information, see SSH keys.
User data	You can add user data to automatically complete common configuration tasks or run scripts. For more information, see User data.
Boot volume	The default boot volume size for all profiles is 100 GB. You can edit the boot volume by clicking the pencil icon.
Data volume	You can add one or more secondary data volumes when you provision the instance. To add volumes, click New volume. For more information about provisioning the volume, see Create and attach a block storage volume when you create a new instance. Attach data volumes to your virtual server depending on your SAP HANA or SAP NetWeaver virtual server profile.
Network interfaces	Assign networking options to connect into the IBM Cloud VPC. You can create and assign up to five network interfaces to each instance - see below.

Adding Network Block Storage for VPC

Log in to the IBM Cloud console with your unique credentials.
Click Menu icon > VPC Infrastructure > Block storage volumes > New Volume.
Enter a unique Name.
Choose a Resource group.

The resource group can't be changed after you create the virtual server.
Select the same Location in which you created your Virtual Servers for VPC. The location consists of a region and zone.
Select either IOPS tiers or Custom. As described in Storage design considerations, the IOPS per GB depends on the workload anticipated.
Click Create volume.

By default all block storage for VPC volumes use IBM-managed encryption. However, new capabilities are available for customer-managed encryption.
Click Menu icon > VPC Infrastructure > Virtual server instances.
Select the virtual server to which you want the new block storage to be attached.
Click Attach volume.
Select the new block storage volume and click Attach.
Log in to the virtual server over SSH, and perform the necessary activities for the block storage, such as add file system partitions, file systems, and mount points.

See here more information about using attached block storage.

Creating the network interface

For each network interface (vNIC) added, define the following:

Network interface name (defaults to eth0 and so on, but this name is not what appears on the OS when it is running ip link)
Subnet to assign to this network interface into

During virtual server provisioning, each virtual server requires a Primary network interface. If you are using a Floating IP, by default it is attached to the primary network interface.

By default during provisioning of a virtual server, the primary network interface is already added with the default Security Group. After a virtual server is created, the network interface is assigned its own Private IP from the selected Subnet range.

Throughput of network interfaces

Every virtual server profile has a maximum network bandwidth of 2 Gbps per vCPU, with a cap of 80 Gbps. Network bandwidth is distributed evenly across network interfaces. Each network interface has a cap of 16 Gbps that might limit the overall performance. You might need to attach multiple network interfaces to your virtual server instance to optimize network performance.

For example, if you choose a profile with 16 vCPU, the network cap for the profile is 32 Gbps. If you have just one network interface, the maximum network performance is 16 Gbps due to the network interface cap. You need to attach two network interfaces (16 Gbps each) to reach the profile cap of 32 Gbps.

For more information, see VPC - Network performance notes for profiles.

Multiple network interfaces

You can add up to 5 network interfaces (vNIC) to your virtual server instance, each is assigned with a single unique IP address from the selected Subnet range, which provides multiple IP addresses for your virtual server instance.

Each of the multiple networks interfaces attached to the virtual server are able to use the same Subnet or different Subnets. However, these subnets must be within the same Zone of the VPC.

You can create a new network interface during provisioning or after the virtual server is running.

After a new network interface is created, it is immediately available to the OS shown by using ip link.

If your virtual server instance is running when you complete the following steps to add the network interface, then it remains in DOWN mode and you must configure the network interface for the instance. You can either stop and then restart the instance, which puts the interface into UP mode and append to the route table, or you can manually configure the interface in the guest operating system (for example, on a Linux-based operating system, you can use ip link set dev <interface> up).

To add a new network interface to your virtual server instance, complete the following steps:

In the Network interfaces section of the Instance details page, click New interface.
On the New network interface page, the interface name defaults to an incremented number. If this is the first new interface after your primary interface, the default name is eth1. You can change the name if you want.
Select a subnet from the subnets that are assigned to your existing network interfaces.
Select the security group that you want to associate with the network interface.
Click Create.

More information is shown on VPC Infrastructure - Managing network interfaces.

Readying your Operating System

Bring your own OS product license

When you have your own operating system license, you can install it on your virtual server based on the vendor's instructions. For more information about custom images, see Importing and managing custom images.

Please consider, the OS chosen must be certified for SAP and have access to the necessary OS Packages for SAP.