In this video, you will specifically look at private connectivity related troubleshooting, which could be either IPSec or FastConnect, etc. First of all, once you have established a VPN connection between your OCI, VCM, and the RG and the On-Premise network, you need to first of all, ensure when you are interconnecting two private networks, the two networks don't have any overlapping siders. Which means you should have planned for it even before deploying otherwise, you will have errors. Then are you having the configuration of your private networks correctly done is something you need to understand. Wherein the first thing you take here is check your siders and routing configuration, whether you have any stateful packet inspections that you are configuring in your IPSec connections that are there in your tunnels that you established for IPSec, and are two tunnels both up. This is the first round of testing you would do. Basically, when you use OCIs VPN servers, it gives you two public endpoints and two tunnels which you can configure. First, validate the connectivity and routing information is clear. If this is all in place, then you can go to Step 2 of your troubleshooting, which is to do ping test. From your On-Premise environment to the OCI compute environment or network devices that you have, as well as from your OCI to On-Prem do a ping. You must have heard the security list or network firewall implementation using security lists or network security group to allow this port protocol to communicate. Only then the network level communication will happen. You should have a consistent result from the pings that are happening. If not, you might want to check out whether there is any misconfiguration. You can work with Oracle Support to figure out is there any problem. You can use the Glance tool, for example, which are used by system administrators to get more information about your system administration monitoring. More than the top command or anything else you might have, Glance gives you interesting options to troubleshoot various resources including networking. Your Glance should show that the communication is going through fine. If there is any knotting you have configured, you might want to consider that also. Once all this is clear, then you know the configuration is all set and you might want to go to the next level of troubleshooting, which is to check whether there is any performance issues. You can use tools such as iPerf to configure a bandwidth latency check between two environments. For example, you might have a computer in your On-Premise and an OCI compute instance in which both you will install the IPerf tool and use the tool to generate a simulated network workload to figure out what is the throughput in terms of bandwidth and latency that is being experienced to identify is there any other configuration issues. Both ways, you need to run the command from the On-Premise to OCI and from OCI to On-Premise to validate everything is running fine. In case this is a problem, you can still work with Oracle to figure out, is there any configuration issues? Lastly, if all this still works out fine and you still have networking issues, you can do tcpdump to be configured and look into that. Sometimes what can happen is the OS compute environment in OCI might need some other settings to be taken care where you can raise a ticket to troubleshoot and get the problem resolved. These are various things you can do from an IPSec or VPN connectivity or FastConnect connectivity, both ways, similar configuration would be applicable. Then comes the ability to set up redundancy. Same configuration would be applicable when you use FastConnect. You would have one more provider in between to check the networking. You will have the provider, either the partner or a third party provider who is involved in setting up the connectivity. You need to take care of that. But once that is all taken care and network connectivity is in place, you need to ensure you have a redundant connection between your On-Premise environment and OCI. If I refer to this box over here as your On-Prem network, and this as your OCI environment, there are various ways of setting up redundancy. Generally, when your deployments in OCI are critical for your workload, first and foremost, recommendation is to have a FastConnect connection. Because with FastConnect, you have a reliable SLA based connectivity wherein Oracle ensures with the provider, they take care of redundancy within the FastConnect provider itself to ensure connectivity to OCI. Even if you're using a FastConnect provider, Oracle recommends you have a VPN connect also as a backup or redundancy setup so that in case for whatever reason the FastConnet lands up having a problem, you at least have a basic VPN connection available with OCI. In your On-Premise environment, you need to configure it in such a way, the routing is given priority with FastConnect and OCI also will take care in there. OCI end priority is given to the FastConnect to connect. Even better would be to have a redundant FastConnect connection itself. Some customers, when they find that their OCI deployments are very critical, might go with two providers and setup FastConnect connection so that both can be used in an active manner and in case one of the FastConnect connections goes down, you have redundant FastConnect with VPN as a third backup that is available. An even better way to do it is have a FastConnect with another region and implement remote pairing between the regions so that you don't have any problems. When you are using FastConnect or VPN, monitoring them is very important. Troubleshooting any connection issues is important. Similar to how you could troubleshoot your VPN environment, FastConnect troubleshooting is also available. You need to make sure one tunnel is used as primary and the other tunnel is backup so that in case one tunnel goes down, the other tunnel is activated when you are using a specific VPN connection. Separate, separate FastConnect with separate, separate network providers in two different FastConnect connections gives you a entirely resilient connection to OCI. These are all things one has to configure when you set up that tenancy or after setting up your tenancy in Oracle Cloud. This is some of the options you need to keep in mind. Every component, the IPSec, FastConnect connections that you use, all have monitoring metrics available which you will have to monitor and work with Oracle to figure out in case there are any problems. That's about private connectivity related troubleshooting.
