Creating MCR Connections to SAP HANA Enterprise Cloud
Megaport makes it easy to provision fast, secure, and private connections between a cloud service provider and the SAP HANA Enterprise Cloud with a Megaport Cloud Router (MCR).
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
With SAP Cloud Peering through Megaport, you can connect to the SAP HANA Enterprise Cloud.
With an interconnection, you can use Megaport to reach additional cloud providers, including Amazon Web Services, Microsoft Azure, Google Cloud Platform, and others.
How the 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 centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and SAP are established on SAP HEC WAN routers (a minimum of two). These physical connections are maintained between SAP and Megaport.
Connecting from a Cloud Service Provider to the SAP Cloud Peering Service follows these general steps through the Megaport portal:
Order Megaport Cloud Routers in locations of your choice.
Two MCRs are required for resilience.
Order VXCs to SAP in increments of 100 Mbps up to 2 Gbps.
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. Speeds greater than 2 Gbps are available on request.
Provision a VXC from each MCR to your chosen Cloud Service Provider. Detailed instructions for each CSP are in Cloud Connectivity > MCR.
SAP Cloud Peering is available in these locations:
- Sydney, Australia Equinix SY3
- Frankfurt, Germany Equinix FR5
Ashburn, US Digital Realty ASH1
Sterling, US Cyxtera DC 1/2/3
Santa Clara, US vXchange
You can connect to multiple regions from a single interconnection point (which lets you leverage multi-region redundancy at a fraction of the cost).
For more details, see Availability of SAP Cloud Peering per location.
Setting up the SAP cloud peering service
Setting up SAP cloud peering requires two stages: first, open a ticket with SAP to set up your SAP cloud peering service and configuration, and second, create a connection from Megaport to SAP.
To set up SAP cloud peering with SAP
- Contact your SAP account manager or cloud advisory architect and establish an HEC agreement that covers SAP Cloud Peering services.
- Open an SPC ticket and provide the following configuration details.
|Customer||HEC customer name and CID|
|Location||Sydney, Frankfurt, Sterling, Ashburn, or Santa Clara|
|Bandwidth||100 Mbps up to 2 Gbps|
|Customer contact||Contact details|
|2 x BGP peering networks||10.11.12.0/30, 10.11.12.4/30, or similar|
|Customer side IP1 & SAP side IP1||10.11.12.1/30 & 10.11.12.2/30, or similar|
|Customer side IP2 & SAP side IP2||10.11.12.5/30 & 10.11.12.6/30, or similar|
|MD5 secret for BGP||< md5-hash-key >|
|ASN of customer BGP side||For example, 65200 is HEC01|
|Customer side peering ASN||Public or private ASN|
|SAP side peering ASN||Public or private ASN|
When configured, SAP provides a unique Megaport service key for both cloud peering location interfaces: one key for the primary and one key for the secondary.
To set up SAP Cloud Peering with Megaport
- Log into the Megaport Portal. If you don’t already have an MCR, create one following the procedures in Creating an MCR. Two MCRs are required for resilience.
- Add a VXC connection for the MCR.
If this is the first connection for the port or MCR, click the SAP tile. The tile is a shortcut to the configuration page. Alternatively, click +Connection, click Cloud, and click SAP as the provider.
Enter the service key provided by SAP and click Next.
Specify these connection details:
Connection Name – The name of your VXC to be shown in the Megaport Portal.
Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.
Partner managed accounts can apply a Partner Deal to a service. For details, see Applying a Deal to a Service.
Rate Limit – This number populates automatically based on the rate defined with the service key.
The MCR Connection Detail page appears, where you can set up the peering session between the MCR and the SAP HEC WAN router based on the configuration details in the SPC ticket.
Enter your local IP address.
Click Add BGP Connection.
Specify these connection details:
Local IP – Select the IP address assigned to the MCR from the drop-down list.
Peer IP – Select the second available IP address assigned by the customer.
Peer ASN – Enter the peer autonomous system number (ASN) assigned by SAP. For example, 65200 is HEC01.
BGP Password – Optionally, specify a shared key to authenticate the BGP peer. You will need to use this key when you configure your BGP peer group in the SAP Console. The shared key length is from 1 to 25 characters. The key can include any of these characters:
a-z A-Z 0-9 ! @ # ? . $ % ^ & * + = -
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
Description – Optionally, enter a description for the connection.
BGP State – Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not impact existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.
- Proceed through the ordering process.
- Repeat these steps to provision your secondary SAP Cloud Peering interface on a second MCR. The second MCR must be in a different location from the primary MCR.
Resiliency to SAP
By default, SAP provides a primary and secondary interface. For maximum resiliency, we recommend provisioning two Megaport MCRs in separate data centers. VXCs from Megaport correspond to the two SAP WAN router connections.
Updating the service bandwidth
You define your VXC speeds at the time of signing your agreement with SAP. If you need to change the speed, work with your SAP account manager to define your new speed and then update the VXC configuration in the Megaport Portal with the new speed.
Speed changes require approval from SAP. SAP accepts or rejects incoming speed change requests based on the contracted agreement. Speed changes do not affect network traffic.
SAP Frequently Asked Questions (FAQs)
Does SAP HANA Enterprise Cloud offer BYOIP?
Yes, SAP HANA Enterprise Cloud lets you bring your own IP address.
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 establish a VXC to the closest SAP location of your choice. Each VXC is carried across the Megaport redundant network to SAP.
Are my bandwidth speeds set?
Yes, you set your speeds when you sign your agreement with SAP. Speeds are set to 100 Mbps, in increments of 100 Mbps up to 2 Gbps (and speeds greater than 2 Gbps are available on request).
Does SAP support public or private ASNs?
SAP supports both private and public ASNs.