Best Practices from Oracle Development's A‑Team

A Simple Guide to Verify Fusion SaaS Network Latency


In this Blog I am writing about how the network latency can be tested for Fusion SaaS Application console and services from the customer side. When customer experience slowness while accessing Fusion Application Services including the Web console, the first level of troubleshooting need to be done by the customer to rule out whether any network level latency is causing the overall slowness.

Fusion SaaS Application supports the following network connectivity models:

1) Public Internet
2) IPSec VPN
3) FastConnect

For any of the Fusion SaaS connectivity models mentioned above, the following checkpoints can be verified and tested by the customer to identify and troubleshoot the network latency before reaching out to the Oracle Support.

Before you begin

Pre-Checks before executing the network latency tests.

A) Browser Recommendations

1) Ensure that the latest version of the Firefox browser (Default Browser: For best performance of Oracle Fusion Applications, use the latest ESR version of Mozilla Firefox).
2) Dedicate the Firefox exclusively for use with Fusion Applications.
3) Ensure browser best practice settings are followed for Fusion Applications as per "Best Practices for the Browser Settings and Performance on Fusion Applications (Doc ID 1385107.1)".

B) Check for Any VPN Enabled on Client Machine

If any client VPN is enabled while accessing the Fusion SaaS Application (For Example: Cisco AnyConnect), the assigned Client DNS IP Address may be located at considerable distance from the Client IP which then results in sub-optimal routing and increased round trip times.

This scenario will impact the network performance while accessing Fusion SaaS Applications will Akamai CDN Enabled over Public Network.

For Example, when the assigned Client DNS IP Address is in a different country from the Client IP address, the Client is incorrectly assigned a distant Akamai Edge Server, rather than a local Akamai Edge Server. So by not using a VPN, this will minimize the round trip time between the Client and the local Akamai Edge Server.

C) Verify the network connectivity on the client machine

One of the common scenario observed during the network latency troubleshooting is slow network connectivity on the client/customer machine. This may be due to poor WIFI connection or Low Bandwidth connection over Wired Network at times which may end in slowness while accessing Fusion SaaS services. To avoid such situations, its always recommended to test the network bandwidth over local network access points for adequate bandwidth to access Fusion SaaS Services.

D) If Federated SSO is configured using 3rd Identity Provider.

If an identity Provider outside Oracle Cloud (3rd Party Identity Provider) is used for identity federation to enable Single Sign On (SSO), slow or unreliable network connectivity connecting the 3rd Party Identity Provider and Oracle SaaS/Oracle Identity Cloud Service can impact the overall performance of Fusion SaaS Application/Services.

While troubleshooting the Fusion SaaS Application slowness, it will be a good idea to check the network latency between the 3rd Party Identity Provider and Oracle SaaS/Oracle Identity Cloud Service specifically if more occurrences of slow Logins and Logouts are reported by Users. 

Testing Network Throughput

For testing the network throughput from the customer site to the Oracle Data Centre where the Fusion SaaS Application is hosted, we will be using the "MTR" network diagnostic tool. Generating the "MTR" report will enable the customer to check for any network latency between any network hops till the Final Hop ie Oracle Data Centre.

Based on this report, the customer can identify which network team to be involved to troubleshooting the network latency, ie Customer Network Team, Oracle Network Team/FastConnect Provider in case of IPSec VPN/ FastConnect.

MTR is a simple, cross-platform command-line network diagnostic tool that combines the functionality of commonly used traceroute and ping programs into a single tool. In a similar fashion as traceroute, "MTR" prints information about the route that packets takes from the host on which "MTR" is run to a user specified destination host. 

MTR tool is available on Linux and Windows Platform.

Following MTR command can be used to check the network latency to Fusion Application host via Public Internet.

Hostname used is the FQDN available in the Fusion SaaS URL:

$ mtr -r <podname>-test.fa.em2.oraclecloud.com



Getting the network latency report is the very first phase of the troubleshooting exercise to inspect or analyze the slowness in accessing the Fusion SaaS services. Customer need to work with the Customer Network Team, ISP Provider, Oracle Support to further troubleshoot in case any network level issues are identified.


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha