Sometimes there may be issues relating to the performance of the service, rather than a service interruption. If a Corente Services Gateway is functional and active on the Corente Services network, the monitoring tools in Gateway Viewer and App Net Manager enable you to diagnose and resolve performance issues.
Performance issues are most often caused by a routing device that is not functioning properly between the customer site and the hub site (also known as a hop between sites). Several tests and features in Gateway Viewer and App Net Manager can help determine what hop might be causing latency or loss issues for application traffic. App Net Manager can also help determine whether a gateway is using too much or too little bandwidth.
First, identify whether or not there are any active alerts on the Corente Services Gateway by right-clicking the Corente Services Gateway icon in the App Net Manager and highlighting Alarms in the displayed menu. Select an alarm number to view the details of that active alarm. This indicates what sort of problem the Corente Services Gateway is experiencing. When there is a performance issue, this alarm will often indicate whether the issue is due to latency, loss, or bandwidth shortage.
If there is an issue with slow performance, the issue is most likely a latency problem.
In the Gateway Viewer, on the Test page, perform a ping test from the customer's Corente Services Gateway to the hub site. This gives a basic measure of latency. Do the following:
In the Partner section, click the Ping button beside the name of the hub site.
The results of this test will display the approximate round trip time of test packets.
If this test indicates that there is latency on the connection to the hub site, the user should next perform a traceroute test to determine what part of the network is experiencing the latency.
In the Partner section, click the Traceroute button beside the name of the hub site.
The results of this test display the amount of time it takes for a packet to reach each hop on the way to the hub site.
If the results of the traceroute indicate that the latency is caused at some point on the Internet, contact the ISP to determine the cause of the latency. If the test indicates that the latency is caused by a device at the hub site or on the customer LAN, this issue should be escalated to Oracle Support.
If a Corente Services Gateway is generating a loss alert, access the Test page of Gateway Viewer.
On the Test page, perform a ping test from the customer's Corente Services Gateway to the hub site. This gives a basic measure of packet loss.
In the Partner section, click the Ping button beside the name of the hub site.
The results of this test display the percentage of loss on packets between the customer site and the hub site. Ideally there should be no loss, and a loss rate exceeding 5% is poor.
If this test indicates that there is an unacceptable amount of packet loss on the connection to the hub site, you should next perform a traceroute test to determine what part of the network is experiencing the latency.
In the Partner section, click the Traceroute button beside the name of the hub site.
The results of this test show an asterisk in place of a dropped packet. This can help indicate the point in the route to the hub site at which a packet loss occurs or begins to occur.
If the results of the traceroute indicate that the loss is caused at some point on the Internet, contact the ISP to determine the cause of the loss. If the test indicates that the loss is caused by a device at the hub site or on the customer LAN, this issue should be escalated to Oracle Support.
If the gateway is generating a bandwidth alert or the previous tests have proved inconclusive, you can examine the bandwidth reports for a Corente Services Gateway in App Net Manager.
To access bandwidth reports in App Net Manager, do the following:
Double-click the Reports category in the domain directory.
In the subcategories that are displayed under Reports, double-click the Graphs subcategory. All of the Corente Services Gateways in the domain are listed under the Graphs subcategory.
Double click the Corente Services Gateway name.
Select Bandwidth Report to view the bandwidth report.
If the report is displaying a consistent excess of bandwidth usage, this could be causing poor application performance. A device on the customer site LAN might be consuming too much bandwidth, causing the application to be slow.
To identify the top bandwidth users on the customer site LAN, access Gateway Viewer and log in and then click the Monitoring button and then click Top Talkers.
The top ten bandwidth users on the user’s LAN are displayed. You can use this information to identify the cause of the problem.
An application could be suffering from poor performance due to incorrect QoS (Quality of Service) configuration. If there are multiple applications being used over the Corente Services network, you must make sure that the highest priority applications have the highest QoS priority, and the lowest priority have the lowest.
QoS settings are enabled on the customer side in tubes, which divide each site-to-site connection into specific sets of rules that apply to specific User Groups and applications.
Access the Location form for the customer's Corente Services Gateway by right-clicking on the Corente Services Gateway icon in the map and selecting Edit. The Location form is displayed in a new window.
On the Location form, click the Partners tab. This tab is used to choose the partners of this Corente Services Gateway.
The main Partners tab presents a table of all partners of the Corente Services Gateway. Select the hub site gateway and click the Edit button. The Edit Partner screen will be displayed.
On this screen, select a tube that is defined for this connection and click Edit. The Edit Tube screen is displayed.
Ensure that any Inbound or Outbound QoS settings for this particular User Group to application partnership are the correct priority levels. Change as necessary.
Repeat for any additional tubes.
When you are finished, click OK. Click OK again to store your changes to the customer to hub site partnership, and click OK once more to store your changes to the Location form.
Click the Save button on the App Net Manager tool bar to save your changes.
Wait a few minutes until the changes have been distributed to the customer's Corente Services Gateway.
Check that the application performance is improved.