You can view network throughput, packet rates, protocol latency, and external network errors within the Network Performance report.
For this example, you are researching into network latency to determine the cause.
Click the
Performance Reporting tab.
On the
Live Performance Reporting page, click the
Cluster drop down and select the cluster that you want to monitor.
Click the
Report Type drop down and select
Network Performance.
In the
Date Range fields, select a range to display, then click
View Report.
The date range should include the entire period of time when the cluster was behaving unexpectedly. The default setting is to view the last hour of data.
The modules in the report are now populated with data for the cluster and date range you selected.
In the
External Network Throughput Rate module, check the throughput rate during the time in question.
NOTE High throughput values indicate times when the cluster's network was under heavy load.
In the
External Network Throughput Rate module, click the
Client breakout.
To learn more about breakouts, refer to the
Breakouts topic.
To remove focus on a breakout, click the
None breakout.
On the left side of the module, you can now see a list of all clients that were using the cluster's network throughput during the timeframe you specified. The client at the top of the list was using the highest percentage of network throughput.
Click to select the client that was using the most throughput during the date range.
To remove focus on a client, click the client filter button at the top of the module.
All applicable modules in the report are now showing information that is focused on the client you selected, and data from all other clients are removed from the module.
In the
Protocol Operations Average Latency module, click the
Protocol breakout.
On the left side of the module, you can now see a list of all protocols in use during the date range you specified, with the protocol at the top experiencing the most latency.
With the information you gathered, you can determine which client and protocol might be causing network latency issues on the cluster.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\