Netsh advfirewall firewall add rule program=\ntttcp.exe name="ntttcp" protocol=any dir=in action=allow enable=yes profile=ANYįor example, if you copied ntttcp.exe to the "c:\tools" folder, this would be the command:
Bandwidth test windows#
Name rather than to allow specific TCP ports inbound.Īllow ntttcp through the Windows Firewall like this: It's easiest to allow the entire NTTTCP program by On the RECEIVER, create an Allow rule on the Windows Firewall to allow the Testing VMs running WINDOWS: Get NTTTCP onto the VMs.Ĭonsider putting NTTTCP in separate folder, like c:\tools Allow NTTTCP through the Windows firewall Valid examples of testing are covered later in this document. The preceding sample should only be used to confirm your configuration. Once the tool is working as expected, extend the test period to 300 seconds for the most accurate results. Tip: When setting up this test for the first time, you might try a shorter test period to get feedback sooner. Run the NTTTCP test for 300 seconds (or 5 minutes) on the sender VM and receiver VM. Make a note of the number of cores on the VM. Make a note of the RECEIVER's IP address. It is possible to test with the VIP but this kind of testing is outside the scope of this document. Deploying VMs for testingįor the purposes of this test, the two VMs should be in either the same Proximity Placement Group or the same Availability Set so that we can use their internal IPs and exclude the Load Balancers from the test. One VM functions as SENDERĪnd the other as RECEIVER. NTTTCP is recommended.Ĭopy the tool to two Azure VMs of the same size. When testing network throughput performance in Azure, it's best to use a tool that targets the network for testing and minimizes the use of other resources that could impact performance.
0 kommentar(er)
