top of page

App Service in network mode

Updated: Jul 10

When to use network mode for App Service?


Bumblebee Global Private Link builds connectivity without the need for routing, this works perfectly for B2B networking for on-prem to on-prem, cross region and multi-cloud. But there are situations where dynamic network routing is preferred. For example, a print server is located in head quarter and printers are in branch offices. Print server initiated traffic needs to reach many printers and many branches. If using private link technique, one will need to build many app services. For such scenarios, network node is a better solution.


In network mode, traffic can be initiated from both app service side and endpoint side, the solution is still cloud scale. To have the ability of dynamic fail over, BGP routing should be enabled on both endpoint and app service run BGP sessions to exchange routes. This BGP routing enables dynamic failover if one app service or endpoint fails.


Global Private Link network
Global Private Link network mode

In the diagram above, a branch office deploys 2 Endpoint nodes and in the head office 3 App Service nodes are deployed. Print servers in the head office can initiate print commands to the printers located in the branch offices.


The key features


  • Both Endpoint side of the network and App Service side of the network can initiate traffic.

  • App Service nodes and Endpoint nodes have no public IP address associated with them. No inbound firewall ports need to be opened.

  • Support static routing and dynamic routing using BGP.

  • Support network address translation for overlapping network address ranges between the endpoint network side and app service side and between endpoints themselves.

  • Support scale out deployment where clusters of Endpoint nodes and App Service nodes can be deployed to increase network throughput.

  • Support dynamic failover of multiple endpoint nodes and app service nodes.


Configuration setup

  1. Log in to the platform console

  2. At the left navigation bar, click App Services

  3. Click + Create App Service

  4. Enter the App Service name (you can change it later)

  5. For Location, select Network

  6. For the Real subnet CIDRs, enter the network address range of the network where App Service is deployed. Example, 192.168.1.0/24

  7. Select Enable address translation if there are any overlapping network CIDRs in the network.

    1. if Enable address translation is selected, a virtual address range is popped up, this is the default range recommended by Bumblebee platform. You can overwrite if you wish to customize.

  8. Select Enable BGP if App Service advertise routes to the router connects to the Service nodes.

  9. If Enable BGP is selected

    1. Enter what you wish the Bumblebee side ASN number be, for example 65001

    2. Enter what your router ASN number be, for example 65002

    3. Enter your router side BGP peer IP address (Bumblebee side peer IP address will be displayed at the App Service Details page as the field BGP local IP)

  10. Select a Service Node group in the drop menu. If there is no Service Node gorup, follow the instructions list here, to create one and then return to the current page and select a Service Node Group in the drop down menu.

  11. Click Create.

  12. Once the App Service is created, an App Service ID is generated. The App Service ID is what your partners or customers use to make a request to connect to your application. Note all Endpoints must all be in Network mode.

  13. For a complete end-to-end configuration workflow, check out Tutorial: end-to-end-configuration.  



47 views0 comments

Comments


bottom of page