You can use Megaport to implement an ExpressRoute Layer 2 connection between your on-premises or colocation-based infrastructure and your SAP on Azure instance. You can also use ExpressRoute to connect to a cloud-only instance of SAP on Azure.
Before you begin, ensure that you have created a Megaport connection, or Megaport. After you create a Megaport, you will connect a Virtual Cross Connect (VXC) from the Megaport to the virtual gateway associated with the Azure VNet infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Megaport) and a B-End (in this case, your SAP on Azure instance).
If you aren’t a Megaport customer, you can create a 1 Gbps or 10 Gbps Megaport in one of our global data centers/points of presence. If your company isn’t located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. Contact Megaport for more information.
Note: If you require a Megaport in a different location to physically separate this solution from other existing traffic traversing your Megaports, we recommend that you create a new one before proceeding.
This high-level figure shows Megaport connectivity into an SAP Netweaver on Azure solution:
You can achieve redundancy for the connectivity portion of this solution by deploying additional VXCs to the Azure environment. This figure shows how you can achieve additional physical redundancy if the VXCs are implemented on separate Megaports:
Before you begin, you must have the following:
- A Megaport connection, or Megaport – If you haven’t already created a Megaport, see Creating a Megaport. You will deploy a connection from the Megaport to the SAP on Azure instance using a Virtual Cross Connect (VXC).
- An ExpressRoute Service Key – Create a service key from your Azure portal by following the steps in the Azure documentation. Ensure that you choose Megaport as the Provider in the Create ExpressRoute Circuit window (Step 2 in the Azure documentation).
To integrate Megaport with SAP on Azure
- In the Megaport portal, go to the Services page and select the Megaport you want to use.
- Add an Azure connection for the Megaport.
If this is the first connection for the Megaport, click the Microsoft Azure tile. The tile is a shortcut to the configuration page. Alternatively, click +Connection, click Cloud, and then click Azure ExpressRoute as the Provider.
- Locate the ExpressRoute Service Key that you created in your Azure Console and paste it into the Microsoft Azure Service Key field.
The Megaport Portal verifies the Service Key, and displays Primary and Secondary Azure on-ramps. For details on adding a redundant connection, see Redundancy.
- Choose the Primary option and click Next.
- Specify these connection details:
- Name your connection – The name of your VXC to be shown in the Megaport Portal.
- Invoice Reference – This is an optional field. It can be any text, such as a PO number or billing reference number.
- Rate Limit – The speed of your connection in Mbps. This value will be auto-populated with information from the Service Key.
- Preferred A-End VLAN – Specify an unused VLAN ID for this connection. This is the S-Tag, or outer tag, associated with the Megaport that transparently carries the inner C-Tags for ExpressRoute. This VLAN ID must be a unique ID on this Megaport and can range from 2 to 4090. If you specify a VLAN ID that is already in use, Megaport will assign the next closest available value. If you don’t specify a value, Megaport will assign one.
Important: Megaport delivers ExpressRoute services to Microsoft ports using Q-in-Q. For network devices that do not support Q-in-Q, you can Untag the A-End VLAN. Untagging removes the VLAN tag for the outer connection (S-Tag), and delivers the three inner tags (C-Tags) natively as 802.1Q VLANs. Be aware that using an untagged VLAN limits that VXC to one port. Because you can’t deploy any other VXCs on the Port, such as a secondary ExpressRoute VXC, we don’t recommend this workaround as a long-term solution.
- Click Next.
- Review the details and click Add VXC.
- Click Order.
- Review the Global Services Agreement and click Order Now.
You have now created a Layer 2 connection into your Azure infrastructure.
- Connect the new VXC to the SAP on Azure instance.
Log in to your Microsoft Azure portal. Specify the AS number, VLAN ID, and Primary and Secondary IP subnets for your Primary and Secondary BGP connections into your Azure infrastructure.
Note: Microsoft Azure requires that you use BGP to connect between your on-premises environment and your Azure infrastructure.
For details on setting up Microsoft Peering and Private Peering from your Azure console, see Create and modify peering for an ExpressRoute circuit.
You can repeat the steps to create a second VXC connection into your Azure infrastructure, which will qualify the setup for Microsoft Azure’s SLA. When you paste your Microsoft Azure Service Key into the appropriate field, choose the Secondary on-ramp location (the Primary on-ramp location will be greyed out and unavailable).
At this point, you will have created the second Layer 2 connection from your Megaport to your Azure infrastructure and your work in the Megaport portal is complete.
Planning for deployment of SAP on Azure
You can run SAP applications on Azure Virtual Machines (VMs) and bare metal instances as is the case with SAP Hana on Azure (large instance). SAP applications on VMs offer fast deployment of compute and storage instead of the relatively long process of procuring and installing equipment for premise-based installations. This can be a cloud-only or a hybrid cloud/on-premises solution (note that dividing the same SAP system between on-premises and cloud infrastructures is not supported).
SAP on Azure Virtual Machines
SAP services such as NetWeaver, Business One, and HANA can run on Azure VMs, storage, and network. To use these services efficiently, it’s important to understand the sizes and capacities of the VMs in terms of vCPU, memory, and associated network and storage bandwidth. You will need adequate resources to ensure the performance of the SAP applications you are using.
There are two storage types associated with Azure VMs: non-persistent (volatile) and persistent. Microsoft Azure offers Standard and Premium Storage tiers; the Premium Storage tier delivers better I/O latency, better throughput, and less variability in I/O latency. For more information on Premium Storage, see Azure Premium Storage, now generally available.
SAP HANA (large instance)
SAP HANA (large instance) is a special solution for large enterprise customers that allows for the implementation of SAP HANA on bare metal servers that are dedicated to you. This solution removes any potential performance issues that may be associated with a shared multi-tenant environment. You have options ranging from 36 Intel CPU cores with 768 GB of memory to 480 Intel CPU cores with 24 TB of memory. Note that the bare metal servers are only designated to run the SAP HANA, while the workload middle layer will still operate on VMs.
The isolation of customer resources for the networking, storage, and servers are met through tenants. The bare metal solution of SAP on Azure is Tailored Datacenter Integration (TDI) certified.
SAP Solutions on Azure – How to migrate, implement, configure, and operate SAP solutions on Azure
SAP on Azure: Planning and Implementation Guide – Additional planning and implementation guides for SAP NetWeaver on Azure VMs
SAP Business One on Azure Virtual Machines – Guides for SAP Business One on Azure VMs
What is SAP HANA on Azure (Large Instances)? – More information on the large instance solution