Have you ever been in a situation when you wanted to troubleshoot a network-related issue in a fairly complex OCI deployment and you were spending a good amount of time understanding how a Virtual Cloud Network (VCN) is connected via a Local Peering Gateway (LPG)?
I am excited about OCI newly launched Network Visualizer.
I am a network engineer and I am tasked to identify the root cause of an issue. The OCI environment has several VCNs which are peering via LPG. Since I am not familiar with the deployment, I am trying to open one VCN and check how it is connected.
In the LPG section of the VCN, you can see which routes are leaned, but you do not have a direct way to navigate to the peered LPG
The only way to do it was by searching the OCID of the peered LPG. First, you need to copy the OCID of the peered LPG:
And search it:
In my example, the scenario was a basic one. Imagine that you have more than 10 VCNs.
With the Network Visualizer, you can see at the compartment level a network drawing. I will use the same example as before. The tool is creating the network map every time it is invoked.
This tool has two views: a Regional view where all the VCNs from a compartment are shown and a VCN view where information about a VCN is displayed.
You can easily see that I have three VCNs and “vcn1” and “vcn2” peer together. You can also observe that the Dynamic Routing Gateway (DRG) from “vcn1” has a Remote peering Connection (RPC).
Whenever you click on a resource from the map you will have additional information about the resource. Bellow, you can see the information about “vcn1”,
and for the RPC:
Each element can be moved on the canvas, so it will allow you to create a visual representation of the environment that can be easily screen-shooted.
Notice the “Open Additional Details” button from the VCN details page. It will give you the subnet details on the VCN.
If we consider the original scenario, we can troubleshoot the issue by selecting the LPG. You will be able to identify the routing tables attached and also the received routed.
If we move from the Regional view to the VCN view for “vcn1”, we can see the following:
Notice that you can quickly identify the routes for a specific subnet where it points to.
Network troubleshooting has never been so easy in OCI. In a few clicks, you can identify how VCNs are connected and which are the routes on a specific subnet