> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Creating MCR Connections to SAP HANA Enterprise Cloud
> This help topic describes how to create connections between a Megaport Cloud Router and SAP HANA Enterprise Cloud.
export const Image = ({src, alt = '', caption, width, height, shadow}) => {
const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
if (typeof src !== 'string') {
src = String(src);
}
if (!src || src === 'undefined') {
console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
return <>;
}
const img = ;
return caption ?
{img}
{caption} : img;
};
export const Link = ({href, children}) => {
const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Link -';
if (typeof href !== 'string') {
href = String(href);
}
if (!href || href === 'undefined') {
console.error(`${errorPrefix} the \`href\` property is required — rendering an empty string instead`);
return <>;
}
if (href.includes('{') || href.toUpperCase().includes('%7B')) {
console.error(`${errorPrefix} could not resolve a variable in href "${href}" — rendering an empty string instead`);
return <>;
}
const isExternal = (/^https?:\/\//).test(href);
return
{children ?? href}
{isExternal && (opens in a new tab)}
;
};
Megaport makes it easy to provision fast, secure, and private connections between a Cloud Service Provider (CSP) 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 several 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:
1. Order Megaport Cloud Routers in locations of your choice.\
Two MCRs are required for resilience.
2. Order VXCs to SAP in increments of 100 Mbps, typically up to 2 Gbps. Speeds greater than 2 Gbps are available on 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.
3. Provision a VXC from each MCR to your chosen Cloud Service Provider.\
Detailed instructions for each CSP are in [Cloud Connectivity > MCR](/cloud/mcr).
## Availability
SAP Cloud Peering is available in these locations:
* Asia Pacific
* Sydney, Australia Equinix SY3
* Europe
* Frankfurt, Germany Equinix FR5
* North America
* 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 use multi-region redundancy at a fraction of the cost).
For more information, see the [provisioning guide in the SAP Help Portal](https://help.sap.com/doc/36c625027bd245818ac46998669c639f/ALL/en-US/SAP_Cloud_Peering_Customer_Guide.pdf).
## 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**
1. Contact your SAP Account Manager or cloud advisory architect and
establish an HEC agreement that covers SAP Cloud Peering services.
2. Open an SPC ticket and provide the following configuration details.
| **Required Information** | **Details** |
| :----------------------------------- | :--------------------------------------------------- |
| Customer | HEC customer name and CID |
| Provider | Megaport |
| Location | Sydney, Frankfurt, Sterling, Ashburn, or Santa Clara |
| Solution | HEC |
| Bandwidth | 100 Mbps up to 2 Gbps or above |
| 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**
1. Log in to the Megaport Portal.\
If you don’t already have an MCR, create one following the procedures in [Creating an MCR](/mcr/creating-mcr). Two MCRs are required for resilience.
2. 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**, then click **SAP**.
3. Enter the service key provided by SAP and click **Next**.
4. Specify the 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 your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This number populates automatically based on the rate defined with the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- string maximum length 128. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- string maximum length 256. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
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, and add IPsec tunnels if you want them.\
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc).
6. Enter your local IP address.
7. If the MCR has IPsec enabled, you can add IPsec tunnels.
Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
8. Click **Add BGP Connection**.
9. Specify the 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** (optional) -- 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** (optional) -- 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 affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.
10. Click **Add VXC**.
11. 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.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
14. Click **Order Now**.
## 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.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## 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.