Interpreting Iperf results
|Article:HOWTO64303|||||Created: 2011-12-29|||||Updated: 2012-01-12|||||Article URL http://www.symantec.com/docs/HOWTO64303|
Because of these influencing factors, you should run Iperf a number of times across the day to get a feel for what is normally achievable bandwidth and to know if there are any periods where bandwidth is higher or lower than normal.
You should always test the available bandwidth in both directions between the nodes to ensure that the available bandwidth is comparable depending on which node is used as the server. Otherwise, you can experience significant changes in Veritas Volume Replicator (VVR) throughput if the direction of replication is reversed after migration or fail over between sites. Likewise, you should test the available bandwidth on the same ports that is used by VVR with comparable options, such as protocol and packet size. This ensures that Iperf-generated traffic is subject to the same compression and other factors as the VVR traffic.
When using the TCP protocol, data is sent on the VVR heartbeat port, which is port 4145 by default, whereas when using the UDP protocol, data is sent on anonymous UDP ports by default. This makes it very difficult to determine the exact port numbers that are in use for data transmission. If VVR throughput is very poor, but Iperf shows significantly improved data throughput on a named UDP port or range of ports, you should configure VVR to use the same ports as a test to see if VVR shows an increase in throughput.
Article URL http://www.symantec.com/docs/HOWTO64303