IBM Cloud Docs
Plan Network Connectivity Flows

Plan Network Connectivity Flows

Taking the time to understand and plan network flows is a key ingredient to successful deployment. As you review this section, consider the connectivity requirements you have today but may also need in the future.

Journey Map

Architecture

Overview

By using NSX logical switches with your own IP addresses (BYOIP) you gain the greatest flexibility to manage and secure your workload network in the IBM Cloud. However, with BYOIP comes the additional requirement of devising a strategy for connectivity from within your instance. There are four major areas of connectivity that need to be addressed:

  1. VM to VM connectivity. How your VMs will be able to communicate with each other over the NSX software defined network. Considerations here include routing and whether microsegmentation will be implemented.
  2. VM to public network (Internet) connectivity. Will your virtual machines connect to the Internet directly, utilize a gateway appliance such as FortiGate or vSRX, or utilize proxy servers deployed in the IBM Cloud network or on your own network accessed via VPN or Direct Link.
  3. VM to IBM Cloud Private connectivity. Will your virtual machines require connectivity to services such as Cloud Object Storage or IBM Databases as a Service, and will that connectivity be secured through a gateway appliance or leverage the network address capabilities of NSX-T.
  4. VM to on premise connectivity. Key to connectivity between your BYOIP NSX environment and on premise is the ability to perform route exchange between the two environments. Devising a solution to exchange routes using such technologies as BGP or GRE is essential to a complete working solution.

Detailed Flows

In this section, detailed network flows will be reviewed. The following network architecture will be broken down into five different flows:

Architecture

VM to VM traffic (overlay workload)

Architecture

VM to IBM Cloud Private (10.x & 161.x) networks

Architecture

VM to Internet

Architecture

Internet to VM

Architecture

VM to Client Campus Network over VPN

Architecture

Next Steps

The next step on the deployment journey is: