SAP NetWeaver on Linux Deployment Guide

This deployment guide shows you how to deploy and connect to a VM running SAP NetWeaver on Linux-based systems on Google Cloud Platform (GCP). To learn how to deploy a Windows-based implementation, see the Windows Deployment Guide.

These instructions give you the details for setting up an example 3-tier system, with all the SAP components running on one VM and the database server running on a second VM. During deployment, you also install Google's monitoring agent and can validate that it is sending metrics to SAP. This guide also includes considerations for migrating an existing system, setting up a 3-tier scale-out system, and setting up a 2-tier system.

For more details on planning your implementation, see the Planning Guide. For an overview of IT ops for your system, see the Operations Guide.

VM deployment options

You have two main options for deploying VMs for SAP NetWeaver on GCP:

  • Create a VM manually in the Google Cloud Platform Console or by using the gcloud command- line tool, and walk through the steps of creating a network, configuring your VM and disks, and setting up firewall rules.
  • Use Cloud Deployment Manager and a template created by Google to automate the deployment process.

For either option, you must first have a Google account to create a GCP project. Any Cloud Platform resources that you use, such as a network or a VM, must belong to a project.

Creating a project

To create a project:

  1. Sign in to your Google Account.

    If you don't already have one, sign up for a new account.

  2. Select or create a GCP project.

    Go to the Manage resources page

  3. Make sure that billing is enabled for your project.

    Learn how to enable billing

Deploying manually

The following instructions show you how to deploy an example 3-tier SAP system running Linux and either SAP HANA, SAP ASE, or IBM Db2 for Linux, UNIX and Windows (IBM Db2) as the database. The database components run on one VM, and the other SAP components, including the SAP central services, run on a second VM.

For general considerations for a scale-out system, see Deploying a 3-tier scale-out system.

Installing and configuring the gcloud command-line tool (optional)

The instructions in this guide use Cloud Shell.

We recommend that you install the gcloud command-line tool, which is a part of Google Cloud SDK. Cloud SDK includes features like statement autocompletion, in-place updating, and human-readable and machine-parsable output formats. The gcloud command-line tool allows you to run the commands in this guide from your local machine, instead of in Cloud Shell, if you prefer.

  1. Optionally, install the gcloud command-line tool.

  2. Make sure you are using the correct configuration for your VMs, which you set when you run gcloud init. Configurations are collections of key-value pairs that influence the behavior of the gcloud commands.

    To check your current gcloud configuration, run:

    gcloud config list

    To switch between configurations, run:

    gcloud config configurations activate [CONFIGURATION_NAME]


    • [CONFIGURATION_NAME] is the name of the configuration
  3. If you need to set the default region for the gcloud tool, run:

    gcloud config set compute/region [REGION]


  4. If you need to set the default zone for the gcloud tool, run:

    gcloud config set compute/zone [ZONE]


Creating a network

When you create a project, a default network is created for your project. However, for security purposes, you should create a new network and specify firewall rules to control who has access.

  1. Go to Cloud Shell.


  2. To create a new network in the custom subnetworks mode, run:

    gcloud compute networks create [YOUR_NETWORK_NAME] --subnet-mode custom


    • [YOUR_NETWORK_NAME] is the name of the new network. The network name can contain only lowercase characters, digits, and the dash character (-).

    Make sure to specify the custom flag instead of using an automatic subnetwork. An automatic subnetwork always has the same assigned IP address range, which can cause issues if you have multiple subnetworks and want to use VPN.

  3. Create a subnetwork, and specify the region and IP range:

    gcloud compute networks subnets create [YOUR_SUBNETWORK_NAME]
    --network [YOUR_NETWORK_NAME] --region [YOUR_REGION] --range [YOUR_RANGE]


    • [YOUR_SUBNETWORK_NAME] is the new subnetwork.
    • [YOUR_NETWORK_NAME] is the name of the network you created in the previous step.
    • [REGION] is the region where you want the subnetwork. Use a region that is supported for SAP NetWeaver.
    • [YOUR_RANGE] is the IP address range, specified in CIDR format, such as If you plan to add more than one subnetwork, assign non-overlapping CIDR IP ranges for each subnetwork in the network. Note that each subnetwork and its internal IP ranges are mapped to a single region.
  4. Optionally, repeat the previous step and add additional subnetworks.

  5. Optionally, create a NAT gateway. If you intend to create a VM without a public IP address, you must create a NAT gateway so that your VM can access the Internet to download Google's monitoring agent. If you intend to assign an external public IP address to your VM, you can skip this step.

    1. To create a VM to act as the NAT gateway in the subnet you just created, run the following command:

      gcloud compute instances create [YOUR_VM_NAME] --can-ip-forward
      --zone [YOUR_ZONE]  --image-family [YOUR_IMAGE_FAMILY]
      --image-project [YOUR_IMAGE_PROJECT]
      --machine-type=[YOUR_MACHINE_TYPE] --subnet [YOUR_SUBNETWORK_NAME]
      --metadata startup-script="sysctl -w net.ipv4.ip_forward=1; iptables
      -t nat -A POSTROUTING -o eth0 -j MASQUERADE" --tags [YOUR_VM_TAG]


      • [YOUR_VM_NAME] is the name of the VM you are creating that want to use for the NAT gateway.
      • [YOUR_ZONE] is the zone where you want the VM.
      • [YOUR_IMAGE_FAMILY] and [YOUR_IMAGE_PROJECT] specify the image you want to use for the NAT gateway VM. If you are using SUSE Linux Enterprise Server (SLES) for your SAP NetWeaver components, you must specify a SLES VM for your gateway as well. However, if you are using Red Hat Enterprise Linux (RHEL), then you don't have to select a premium image for your gateway. For example, to select the latest version of Debian, specify --image-family debian and --image-project debian-cloud.
      • [YOUR_MACHINE_TYPE] is any supported machine type. If you expect high network traffic, choose a machine type with that has at least 8 virtual CPUs.
      • [YOUR_SUBNETWORK_NAME] is the name of the subnetwork where you want the VM.
      • [YOUR_VM_TAG] is the tag that is applied to the VM you are creating. If you use this VM as a bastion host, this tag is used to apply the firewall rule only to this VM.
    2. To create a route that is tagged so that traffic passes through the NAT VM instead of the default Internet gateway, run the following command:

      gcloud compute routes create [YOUR_ROUTE_NAME]
      --network [YOUR_NETWORK_NAME] --destination-range
      --next-hop-instance [YOUR_VM_NAME] --next-hop-instance-zone
      [YOUR_ZONE] --tags [YOUR_TAG_NAME] --priority 800


      • [YOUR_ROUTE_NAME] is the name of the route you are creating.
      • [YOUR_NETWORK_NAME] is the network you created.
      • [YOUR_VM_NAME] is the VM you are using for your NAT gateway.
      • [YOUR_ZONE] is the zone where the VM is located.
      • [YOUR_TAG_NAME] is the tag on the route that directs traffic through the NAT VM.
    3. If you also want to use the NAT Gateway VM as a bastion host, run the following command to allow inbound SSH access to this instance from the Internet:

      gcloud compute firewall-rules create allow-ssh --network [YOUR_NETWORK_NAME] --allow tcp:22 --source-ranges --target-tags "[YOUR_VM_TAG]"


      • [YOUR_NETWORK_NAME] is the network you created.
      • [YOUR_VM_TAG] is the tag you specified when you created the NAT gateway VM. This tag is used so this firewall rule applies only to the VM that hosts the NAT gateway, and not to all VMs in the network.

Creating and setting up a VM

When you create a VM, you can specify several options, including the operating system, region, machine type, and persistent disks. You must also specify a start-up script to install Google's monitoring agent on the VM.

To create a VM:

  1. Go to the Images page in Compute Engine:

    Go to the Images page

  2. To use a public image, choose an image from one of the following image families:

    • For RHEL, select an image that begins with rhel-.
    • For SLES, select an image that begins with sles-. This option includes SLES for SAP images if you use SAP HANA as your database.
  3. Click the Create instance button.

  4. Enter a name for the VM.

    Limit your name to 13 characters, as this is the maximum supported by SAP. For more information, see SAP Note 611361: Hostnames of SAP servers.

  5. Select the zone for your VM based on the location of your internal resources and users, and the CPU platform you want to use.

    For more details on the zones supported for SAP NetWeaver, see the following guides and SAP Notes:

  6. Change the machine type to one of the supported high-memory machine types that begins with n1-highmem.

    To compare the supported machine types and their persistent-disk limitations, see the Planning Guide.

  7. Optionally, in the Boot disk section, click Change to configure your boot disk. You can customize the size of the boot disk. For Linux systems, ensure that the boot disk is at least 16 GB.

    If desired, you can change the boot disk from a standard persistent disk to an SSD persistent disk. Be sure to deselect the Delete boot disk when instance is deleted checkbox for the VM instance in the GCP Console.

  8. Under Access Scope, for the Compute Engine default service account, select Set access for each API.

    To ensure that the monitoring agent functions correctly, enable the following APIs for the service account:

    API Access
    Cloud Source Repositories Read Write
    Compute Engine Read
    Service Control Enabled
    Service Management Read Only
    Stackdriver Logging API Full
    Stackdriver Monitoring API Full
    Stackdriver Trace Write Only
    Storage Full

  9. Expand the Management, disks, networking, SSH keys section.

  10. If you are using a NAT gateway, in the Networking tab, under Network tags, add the tag that you specified as [YOUR_TAG_NAME] when you set up the route directing traffic through the gateway.

  11. Specify the start-up script to install the monitoring agent, which sends data to the SAP monitoring system to streamline system metrics for support.

    You must have the monitoring agent installed and running to get support from SAP. For an overview of how the monitoring agent functions, see the Operations Guide.

    In the Management tab, under Automation > Startup script, specify the following script:

    curl -s | bash

    The startup script creates two cron jobs that monitor the agent and update it if necessary.

  12. In the Management tab, under Availability policy, ensure that you leave the following default settings:

    • To ensure availability of your SAP systems, keep the Preemptibility setting Off (recommended).
    • To ensure that your VM can restart if there's a maintenance or failure event, keep the Automatic restart setting On (recommended) .
    • To ensure that your VM is migrated to other hardware during infrastructure maintenance, keep the On host maintenance setting on Migrate VM instance (recommended).
  13. In the Disks tab, under Additional disks, click Add item to add persistent disks for storage.

  14. Under the Name, select Create disk.

  15. In the Create a disk window, under Disk Type select the following:

    • For SAP NetWeaver binaries, add a standard persistent disk (HDD) or an SSD disk.
    • For the swap disk, add an SSD disk.
  16. Under Source type, select None (blank disk).

  17. Specify the size of your disk.

    • For the swap disk, size the SSD according to your needs. Disk throughput is a function of disk size. For this tutorial, you can use a size of 50 GB. For a production system, you can use a much larger disk.

    • You can add more disks if needed. For more information, see SAP Note 1597355 - Swap-space recommendation for Linux.

  18. Click Create to create the disk.

  19. Repeat steps 13-18 to create all the disks you need for your system.

  20. In the Networking tab, choose the network that you created.

  21. In the SSH Keys tab, select Block project-wide SSH keys.

  22. Click Create to create and start the instance.

Adding firewall rules

By default, incoming traffic from outside your GCP network is blocked. To allow incoming traffic, set up a firewall rule for your VM. Firewall rules regulate only incoming traffic to a VM. When a connection is established with a VM, traffic is permitted in both directions over that connection.

Create firewall rules to allow access for:

  • The default ports used by SAP NetWeaver, as documented in TCP/IP of All SAP Products.
  • Connections from your computer or your corporate network environment to your Compute Engine VM instance. Use an IP address such as the one displayed at, or talk to your company's network administrator.
  • SSH from the browser. Allow access in the new GCP network you created through port 22.
  • Connection to your VM by using a third-party tool in Linux. Create a rule to allow access for the tool through your firewall.
  • Communication between two VMs. If you are deploying a system using SAP HANA, recall that you will have 2 VMs in your subnetwork: the VM you just created for SAP NetWeaver, and another VM that you will create for SAP HANA. To enable communication between the two VMs, you must create a firewall rule to allow traffic that originates from the subnetwork.

To create a firewall rule:

  1. In the GCP Console, go to the Firewall Rules page.


  2. At the top of the page, click Create firewall rule.

  3. You can create a firewall rule to allow access to specified ports, or to allow access between VMs on the same subnetwork.

    • In the Network field, select the network where your VM is located.
    • In the Targets field, select All instances in the network.
    • In the Source filter field, select the range of IPs that you want to allow access on this port.
    • In the Allowed protocols and ports section, specify tcp:[PORT_NUMBER];.
  4. For SAP HANA, to specify the details for a firewall rule to allow access between VMs on the same subnetwork:

    • In the Network field, select the network where your VM is located.
    • In the Targets field, select All instances in the network.
    • In the Source filter field, select Subnetworks.
    • In the Subnetworks field, select the subnetwork you are using.
  5. Click Create to create your firewall rule.

To learn more about how to add additional firewall rules to your instance, see the Networking documentation.

Connecting to your VM

You can connect to a Linux VM using common SSH tools. The easiest way to connect to a Linux VM is to connect from your browser through the GCP Console or using the gcloud command-line tool.

Alternatively, you can generate a new key-pair for your Linux VM and apply it to your project, which allows you to connect using third-party tools, such as PuTTY on Windows workstations. For more details, see Creating a new SSH key pair.

You can also connect to your VM using other configurations. For a list of supported environments and known issues, see SSH from the Browser.


To SSH directly from your web browser in the Google Cloud Platform Console:

  1. In the GCP Console, go to the VM Instances page.

    Go to the VM Instances page

  2. In the list of virtual machine instances, click SSH in the row of the instance that you want to connect to.


The gcloud command-line tool manages your SSH keys for you by generating and applying new project-wide SSH keys when you need them. To connect through the gcloud tool:

Connect to your instance by running:

gcloud compute ssh [VM_NAME]

where [VM_NAME] is the name of your VM.

You can now use the terminal to run commands on your Linux VM. When you are done, use the exit command to disconnect from the VM.

Formatting and mounting disk drives

After you connect to your VM, format and mount your disk drive:

  1. In the terminal where you are connected to your VM, use the mkdir command to create a directory where you can mount the device:

    sudo mkdir -p /mnt/disks/[MNT_DIR]

    where [MNT_DIR] is the directory where you want to mount your disk.

  2. In the terminal, use the ls command to identify the disk that you want to mount.

    ls /dev/disk/by-id/
    google-example-instance       scsi-0Google_PersistentDisk_example-instance
    Google-example-instance-part1 scsi-0Google_PersistentDisk_example-instance-part1

    The disk ID usually includes the name of the disk with a google- prefix or a scsi-0Google_ prefix. This example uses the google- ID.

  3. Format the disk.

    For example, for the swap disk, you can use the following command:

    sudo mkswap /dev/disk/by-id/google-example-instance

    For other persistent disks, you can use the following command to format the entire disk with a single xfs file system and no partition table:

    sudo mkfs.xfs -F /dev/disk/by-id/`google-example-instance`
  4. Mount the disk to the VM:

    sudo mount -o discard,defaults /dev/disk/by-id/google-example-instance /mnt/disks/[MNT_DIR]
  5. Configure read and write access to the device. For this example, grant write access to the device for all users:

    sudo chmod a+w /mnt/disks/[MNT_DIR]
  6. Optionally, you can add the persistent disks to the /etc/fstab file so that the device automatically mounts again when the VM restarts.

    When you specify the entry /etc/fstab file, be sure to include the nofail option so that the instance can continue to boot even if the disk is not present. For example, if you take a snapshot of the boot disk and create a new instance without any persistent disks attached, the instance can continue through the startup process and not pause indefinitely.

  7. Create the /etc/fstab entry. Use the blkid command to find the UUID for the file system on the device and edit the /etc/fstab file to include that UUID with the mount options. You can complete this step with a single command.

    For example, for the swap disk:

    echo UUID=`sudo blkid -s UUID -o value /dev/disk/by-id/google-example-instance` none swap sw 0 0 | sudo tee -a /etc/fstab

    For example, for other persistent disks:

    echo UUID=`sudo blkid -s UUID -o value /dev/disk/by-id/google-example-instance`
    /mnt/disks/[MNT_DIR] xfs discard,defaults,[NOFAIL] 0 2 | sudo tee -a /etc/fstab


    • [MNT_DIR] is the directory where you mounted your persistent disk.
    • [NOFAIL] is the option that specifies what the system should do if it is unable to mount this disk.
  8. Use the cat command to verify that your /etc/fstab entries are correct:

    cat /etc/fstab

    If you detach this persistent disk or create a snapshot from the boot disk for this instance, edit the /etc/fstab file and remove the entry for this persistent disk. Even with the nofail option in place, keep the /etc/fstab file in sync with the devices that are attached to your instance and remove these entries before you create your boot disk snapshot.

  9. For the swap disk, activate it by running the following command:

    swapon -a

Preparing the operating system

After you have created your VM, consult the relevant SAP notes on installation and ensure that your system includes the software components specified:

Setting up the database

You can use the following databases with SAP NetWeaver on Linux:

  • IBM Db2


For instructions on how to install SAP HANA as your database, including instructions on how to download and extract SAP HANA to a Cloud Storage bucket, see the SAP HANA Deployment Guide. Following these instructions, you will create another VM with SAP HANA installed.

For more information on SAP HANA, consult the following SAP guides and notes:


For instructions on how to install SAP ASE as your database, including instructions on how to download and extract SAP ASE to a Cloud Storage bucket, see the SAP ASE Deployment Guide.

For more information about using SAP ASE, see the SAP Help Portal.

Using IBM Db2

For instructions on how to install IBM Db2 as your database, see the IBM Db2 Deployment Guide for SAP NetWeaver.

For more information about using IBM Db2 with SAP, see the IBM Db2 Deployment Guide for SAP NetWeaver.

Installing the Stackdriver logging agent

The Stackdriver Logging agent provides you with a solution for GCP system-activity logging. This is an optional but recommended component. See the SAP NetWeaver on GCP Operations Guide for more information about GCP logging.

To install the Stackdriver logging agent, see these instructions.

Deploying a VM automatically with Deployment Manager

As an alternative to manually creating your VM, you can use Deployment Manager and a template provided by Google to streamline your setup.

The template completes the following tasks:

  • Creates a VM using a RHEL 7 or SLES 12.2 image (100 GB with a standard PD). Note that the template also supports certain Windows versions.

  • Adds a persistent disk for SAP binaries (100 GB).

  • Adds a persistent SSD for configuring swap (100 GB).
  • Creates a swap file (4 GB) and enables swap.
  • Enables the correct APIs for Google's monitoring agent.
  • Installs and starts Google's monitoring agent.
  • Runs the sapinit commands and starts up the VM that will host SAP NetWeaver.

To learn more about Deployment Manager, see Deployment Manager Fundamentals.

Before you begin

Create a VM with an SAP HANA, SAP ASE, or IBM Db2 database.

For instructions for SAP HANA, see the SAP HANA Deployment Guide.

For instructions for SAP ASE, see the SAP ASE Deployment Guide.

For instructions for IBM Db2, see the IBM Db2 Deployment Guide for SAP NetWeaver.

Using the Deployment Manager template

To deploy a VM using the provided Deployment Manager template:

  1. Go to Cloud Shell.


  2. Click the Activate Google Cloud Shell button at the top of the console window.

    Activate Google Cloud Shell

  3. A Cloud Shell session opens inside a new frame at the bottom of the GCP Console and displays a command-line prompt. It can take a few seconds for Cloud Shell session to be initialized.

    Cloud Shell session

    Your Cloud Shell session is ready to use.

  4. Run the following commands to use the template:

    curl -s
    >; chmod +x; ./
  5. At the prompts, specify the following for your deployment:

    • Deployment name. The deployment name will be the name of the VM and the OS host name. The name should be unique. If you reuse a name, Deployment Manager fails. Limit your name to 13 characters, as this is the maximum supported by SAP NetWeaver. For more information, see SAP Note 611361: Hostnames of SAP servers.
    • Machine Type. Enter a supported high-memory machine type. The default is n1-highmem-2.
    • Zone. The zone to deploy your VM. The default is us-central1-c.
    • Operating system. Choose RHEL (rhel) or SLES (suse).
  6. Optionally, if you need a swap file larger than the default 4 GB size, add more disks as needed. See SAP Note 1597355 - Swap-space recommendation for Linux.

  7. The template creates two cron jobs that monitor the agent and update it if necessary.

  8. Confirm your VM deployment on the Deployment Manager page.


  9. Click on the deployment to see more details. For example:

    Deployment details

Installing SAP NetWeaver

For instructions on installing SAP NetWeaver, see the SAP help portal and the SAP NetWeaver Master Guide.

After you install SAP NetWeaver, update the SAP kernel to the minimum supported patch level. For details on the supported SAP kernel patch levels, see the SAP Note 2446441 - Linux on Google Cloud Platform (IaaS): Adaptation of your SAP License.

Ensure that the following support package requirements for SAP NetWeaver are met: SAP Note 1102124 - SAPOSCOL on Linux: Enhanced function.

Installing the SAP Host Agent

The SAP Host Agent has been enhanced for running on GCP. Ensure that you run at least the minimum SAP Host Agent version required for the GCP environment.

For details, refer to the following SAP Notes:

Migrating an existing system

For migrations, SAP recommends following their best practices for copying components from your source system to a newly created target system. Use homogeneous system copy when the source and target systems use the same OS and database system. Use heterogeneous system copy when the source and target systems use different OS or database systems. The basic steps are:

  1. Create your GCP VMs, network, and other infrastructure, as described in Deploying manually.
  2. Shut down the SAP NetWeaver system.
  3. Use SWPM to export the source system.
  4. Copy the data from the system and database export to your Cloud Storage bucket. Depending on the size of the exported objects and the bandwidth you have available to connect to GCP, you might want to choose from different methods of sending the objects to Cloud Storage.

Use SWPM to create a new, target system and to import the artifacts that you exported from the source system. You can mount the Cloud Storage bucket as a file system for use by the target system.

Validating your installation of the monitoring agent

After you have deployed a VM and installed SAP NetWeaver, validate that Google's monitoring agent is functioning properly with SAP's enhanced monitoring.

Verifying that Google's monitoring agent is running

You can check whether the monitoring agent is running by polling for a health check from the server. Follow these steps:

  1. In the GCP Console, open Cloud Shell.


  2. Connect to the VM instance you want to monitor. For details on how to connect, see Connecting to your VM.

  3. At the command prompt, enter the following command:

    curl http://localhost:18181/health

If the monitoring agent is functioning properly, the value for status should be UP. For example:


If the monitoring agent isn't running, see the Operations Guide section about restarting Google's monitoring agent.

Verifying that SAP NetWeaver is receiving metrics

To check whether the connection between Google's monitoring agent and SAP NetWeaver works as intended, enter transaction ST06 in your SAP NetWeaver ABAP system. In the overview pane, check the availability and content of the following fields for the correct end-to-end setup of the SAP and Google monitoring infrastructure:

  • Cloud Provider: Google Cloud Platform
  • Enhanced Monitoring Access: TRUE
  • Enhanced Monitoring Details: ACTIVE

Deploying a 3-tier scale-out system

The steps to deploy each VM in a 3-tier system are very similar to the steps for deploying the example system. In a 3-tier scale-out system, you deploy several VMs:

  • A primary VM that runs the SAP NetWeaver application server (AS) and ABAP central services. This VM also hosts a shared file-system that contains the shared profile and must be accessible from each VM that runs SAP NetWeaver in the system.
  • Some number of additional VMs that run the AS, for scaling purposes.
  • A VM that is dedicated to the central database.
  • Everything needs to run in the same zone.

The high-level steps are as follows:

  1. Create the VM that hosts the database and then install the database.

  2. Create the primary instance.

    • Run SWPM on the first VM that you want to run SAP NetWeaver.
    • Install central services.
    • Install the AS.
    • Point to the existing database.
  3. Create additional instances.

    • Run SWPM on each additional VM that you want to run SAP NetWeaver.
    • Install the AS.
    • Point to the existing database.
    • Point to the network share that contains the profiles and is managed by the primary instance.

Deploying a 2-tier system

The steps to deploy SAP NetWeaver in a 2-tier configuration on Linux are very similar to the steps for setting up a 3-tier configuration. In a 2-tier configuration, you:

  • Deploy a single VM that hosts both SAP NetWeaver and the central database.
  • Size the VM to support running both SAP NetWeaver and the central database, together. For example, SAP HANA requires far more memory resources than SAP NetWeaver, so you would need to size the system to support at least the minimum requirements for SAP HANA.
  • Install the central database before you install SAP NetWeaver.
  • For SAP HANA-based systems, use a different SAP system ID (SID) for the SAP NetWeaver ABAP system than for the SAP HANA system.

For SAP HANA-based systems, see SAP Note 1953429 - SAP HANA and SAP NetWeaver AS ABAP on One Server. An installation guide is attached to the note.


This section contains information about how to correct common issues.

Troubleshooting firewalls for an SAP HANA installation

If you are setting up a 3-tier SAP system and having connection issues between your VMs, ensure that you have created a firewall rule to allow traffic between VMs on your subnetwork.

Troubleshooting connecting to your VM

If you are having issues connecting to your VM through SSH, ensure that you have created a firewall rule to open port 22 on the GCP network you are using.

For other possible issues, see Known issues for SSH from the browser.

Troubleshooting Google's monitoring agent

To troubleshoot the monitoring agent, see the Operations Guide.

Was this page helpful? Let us know how we did:

Send feedback about...