MCR – Connecting to SAP HANA Enterprise Cloud with Megaport

Megaport supports two connectivity models for SAP. This article is for connecting from a Cloud Service Provider via a Megaport Cloud Router to SAP. If Connecting from a Megaport Data Centre Port to SAP please see this article.

Megaport makes it easy to provision fast, secure, and private connections between your data centre and SAP HANA Enterprise Cloud portfolio. We provide dedicated connectivity to SAP Cloud peering, via our global Software Defined Network (SDN) from 300+ locations worldwide, in just a few clicks. 

Through private connectivity that bypasses the public internet, enterprises benefit from:

  • Higher network performance, consistency, and predictability
  • Streamlined and accelerated workloads and data migration
  • Improved data and operational security

Megaport and SAP provide a powerful solution for enterprises to expand their reach, drive innovation, and access SAP Solutions across a mixture of public cloud, on-premise and SAP Cloud direct. Enterprises have the control and ability to enable multiple Virtual Cross Connections (VXCs) to SAP from a single location, providing the scalability and agility required in response to evolving business needs.

With SAP Cloud Peering via Megaport you can connect to SAP HANA® Enterprise Cloud.


SAP and Megaport plan to make available SAP SuccessFactors®, SAP Hybris®, SAP Ariba®solutions in the near future.

Once your interconnection is set up, you can use Megaport to reach additional cloud providers, including Amazon Web Services, Microsoft Azure, Google Cloud Platform, and others.

google-cloud, AWS & Azure connectivity diagram to SAP

How SAP Cloud Peering Service works

SAP consists of a physical network connection at a number of SAP Points of Presence (PoPs) around the world. These PoPs reside within facilities operated by co-located data centres where Megaport is enabled. 

Physical fibre connections (NNIs) at each location between Megaport and SAP are established on (minimum of two) SAP HEC WAN routers. These physical connections are maintained between SAP and Megaport. 

Step 1: When connecting from a Cloud Service Provider to SAP Cloud Peering Service you must order a Megaport Cloud Routers in locations of your choice. Two MCRs are required for resilience.

Step 2: Through the Megaport portal, VXCs may be ordered to SAP in increments of 100 Mbps up to 2 Gbps – and speeds greater than 2 Gbps are available upon request. VXCs to SAP Cloud Peering are established as a Layer 3 service between SAP and the MCR. One VXC from each MCR is required for resilience.

Step 3: Through the Megaport portal you may provision a VXC from each MCR to your chosen Cloud Service Provider. The detailed instructions of how to provision, a VXC, from the MCR to your CSP may be found here.


Asia Pacific 

  • Sydney, Australia Equinix SY3


  • Frankfurt, Germany Equinix FR5


  • Ashburn, US Digital Realty ASH1
  • Sterling, US  Cyxtera DC 1/2/3
  • Santa Clara, US vXchange

Connect to multiple regions from a single interconnection point. This means you can leverage multi-region redundancy at a fraction of the cost.


How to order SAP Cloud Peering Service 

You must first contact your cloud advisory architect from SAP to discuss requirements and check prerequisites as you prepare to design your interconnectivity framework. During this process you will discuss cloud peering options and establish an HEC agreement which covers SAP Cloud Peering services. To allow SAP HEC to start service configuration and open a SPC ticket the following information is required. This should be provided by the customer.

Information required

Example format

Customer HEC customer name and CID
Provider In this case Megaport
Location Frankfurt, Sterling, …
Solution HEC
Bandwidth 100/200/300/…2000 MBit/s
Customer Contact name/phone/mail
2 x BGP peering networks,, or similar
  – Customer side IP1 & SAP side IP1 &, or similar
  – Customer side IP2 & SAP side IP2 &, or similar
MD5 secret for BGP verysecret#$*&^%, or similar
ASN of customer BGP side 65200 is HEC01 as an example
  – Customer side peering ASN xxxxx
  – SAP side peering ASN yyyyy (It is used for Customer side BGP configurations)


1. SAP will provide a unique Megaport Service Key per cloud peering location interface: one for the Primary and one for the Secondary cloud peering location interface. When you consume the Service Key created by SAP you will pay for the VXC charges.

2. Log into the Megaport Portal: 

3. Establish an MCR in the selected location if you are not already enabled on the Megaport Network.

4.  Select ‘+ Connection’ and select ‘Enter Service Key’. Paste in the Megaport, 8 characters, Service Key provided by SAP.


sap-portal-15. On the next screen name the Virtual Cross Connect with the Label provided by SAP (Example format CID-1234567890). Set the rate limit to match the Service Key maximum.

6. The next screen, MCR Connection Detail, allows you to enter details to set up the peering session between the selected MCR and the SAP HEC WAN Router using the customer provided information similar to the table above. IP addresses – enter your local IP address and click +Add.

7. Next select + Add BGP Connection to add BGP connection details.

8. Complete the BGP Connection details

  • Local IP – Click on the drop-down to select the local IP address
  • Peer IP – IP address assigned by the customer
  • Peer ASN – assigned by SAP, 65200 is HEC01 as an example
  • Complete the BGP Connection details
  • BGP Authorization: This is not a mandatory field
  • Override MCR ASN: MCR ASN 133937 will be automatically populated. You can choose to override the MCR ASN.

9. Select Add and then proceed to order the VXC.

10. Repeat steps 3 to 9 to provision your Secondary SAP Cloud Peering interface on a second MCR located in a different location to the first MCR.

Resiliency to SAP 

Maximum Resiliency to SAP

By default, SAP provides a Primary and Secondary interface as outlined below. For maximum resiliency, it is recommended that two MCRs are provisioned in two separate Data Centres. VXCs from Megaport correspond to the two SAP WAN routers connections.

Updating the Service Bandwidth

Customers should agree on a data rate with SAP and then increase or decrease your bandwidth between 100 Mbps and 2 Gbps, in increments of 100 Mbps. Speed changes require approval from SAP. 

SAP will accept or reject incoming speed change requests based on what a customer has contracted. Speed changes are non-traffic affecting.



Does SAP HANA Enterprise Cloud offer BYOIP?
Yes, SAP HANA Enterprise Cloud offers BYOIP.

What if I’m not located within an SAP Cloud Peering enabled facility? You don’t have to be located within the same facility as SAP; you can simply establish a VXC to the closest SAP location of your choice. Each VXC is carried across our redundant network to SAP. 

Are my bandwidth speeds set?
Yes. You nominate your speeds at the time of signing your agreement with SAP. Speeds are set to 100 Mbps, in increments of 100 Mbps up to 2 Gbps

Does SAP support public or private ASNs?
SAP supports both private and public ASNs 

Can I use SAP Cloud Peering to connect to SAP HEC running on other cloud platforms? No, SAP Cloud Peering is only for SAP Direct solutions. When SAP HEC is running on other cloud platforms use their private connectivity option via Megaport. For example for SAP HEC on AWS use Direct Connect, for Azure use ExpressRoute and for GCP use Partner Interconnect.


Further readings

©2020 Megaport. Megaport, Virtual Cross Connect, VXC and MegaIX are registered trademarks of Megaport (Services) Pty Ltd ACN 607 432 646.

Log in with your credentials

Forgot your details?