Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
Troubleshooting / Re: Optimised traffic not passing
« Last post by JohnNicholas on October 18, 2018, 08:24:25 AM »
Hi Karl,

Yes, there was a similar issue that was resolved in v.4.2.3. It might be related if running < 4.2.3
32
Troubleshooting / Optimised traffic not passing
« Last post by karlfoley on October 18, 2018, 08:00:33 AM »
We have had an issue where WanOS stopping passing optimised traffic after a patch reboot.
We had to reboot the server again to get optimised traffic flowing.
Has anyone else seen this behaviour, and how to troubleshoot to prevent it happening again.
33
Troubleshooting / Re: TXP-X : How To Verify?
« Last post by JohnNicholas on September 13, 2018, 10:28:27 AM »
Yes, in bridge mode all the devices can actually be in the same subnet.

Quote
iPerf3 - optimized and accelerated I hit 103Mbps on the LAN Tx, optimized to 8.4Mbps on the WAN Tx.
That looks promising.

Any break through with the Dicom protocol?
34
Installation / Re: Free Express throughput
« Last post by JohnNicholas on September 13, 2018, 10:24:17 AM »
Hi Leeson,

"Are you already do this?"
This question is not clear.

To get a new key see Activate License
35
Installation / Re: Free Express throughput
« Last post by Leeson on September 13, 2018, 10:02:27 AM »
Are you already doing this? I'm interested in a trial key.
36
Troubleshooting / Re: TXP-X : How To Verify?
« Last post by mgagliardi on September 09, 2018, 11:13:07 PM »
I've got iPerf3 running on the test machines themselves, transiting the Wanos instances.  Tomorrow I will change the dedup level and see what that brings.  FWIW while I am running in bridge mode the entire setup is on a single subnet (two Wanos instances, each with two NICs, one NIC in the "local" LAN Segment with the test machine, one in the DMZ/WAN LAN Segment).  Traffic is most definitely transiting the Wanos instances as if I power either of them off the clients can't even ping each other.  I saw the warning in the docs about TCP-X and routing but I think I don't think my setup meets the conditions that were cautioned against.
37
Troubleshooting / Re: TXP-X : How To Verify?
« Last post by ahenning on September 09, 2018, 09:31:47 PM »
Is Iperf3 running on the test machines or directly on Wanos?

It is worth testing with deduplication set to level 0. This would eliminate some potential RAM and Disk IOPS or Disk latency bottlenecks.

The Optimized Iperf3 results looks as expected. Also perhaps test with TCP-X enabled, but please read the doc first has in bridge mode the network routes much be carefully configured on Wanos to ensure the TCP accelerator can reach all the source and destination subnets.
38
Troubleshooting / Re: TXP-X : How To Verify?
« Last post by mgagliardi on September 09, 2018, 02:22:45 PM »
Thanks for the suggested test, I did what you'd indicated and got 2.2MB/sec...roughly 17.6Mb/sec on a 20Mb/sec link.  That seems reasonable.  I also did a few other tests...
  • iPerf3 - optimized and accelerated I hit 103Mbps on the LAN Tx, optimized to 8.4Mbps on the WAN Tx.
  • iPerf3 - accelerated only (showing pass-through) I saw 19.9Mbps on the WAN Tx.
  • My application (DICOM) - optimized and accelerated I hit 8.6Mbps on LAN Tx, optimized to 2.2Mbps on WAN Tx.
  • My application (DICOM) - accelerated only (indicating pass-through) I saw 10.7Mbps WAN Tx.
I'm mystified here...curious about why the WAN link isn't being more fully utilized when optimization is in effect.  FWIW right now this lab is all in place on a single VMware host...no traffic is actually hitting the wire.  All VMs are over-provisioned (ex. the Wanos VMs are 4 vCPUs and 8GB RAM) and the host has plenty of unallocated resources, this isn't an issue of CPU, RAM or network contention.  Is it possible the protocol in use (DICOM) is not well-suited to optimization/acceleration?
39
Troubleshooting / Re: TXP-X : How To Verify?
« Last post by JohnNicholas on September 08, 2018, 06:47:48 PM »
In the UI look for the session in the Netstat page. If TCP-X is not enabled the session will not show up.

2.7Mbps over a 20Mbps link with 40ms does not sound right. Maybe testing over a bad WiFi link? It seems very low.
Also TCP-X is designed for higher latency, not sure what the result will be at 40ms, but 2.7Mbps is way too low for a 20Mbps link.

To test the performance between the two instances:

Appliance 1:
cd /tce/www/redirect/
dd if=/dev/zero of=speedtest.file bs=1M count=100


Appliance 2:
wget http://appliance-1-ip/speedtest.file


Usually this should at least be around 100Mbps over a 20Mbps 40ms.
40
Troubleshooting / TXP-X : How To Verify?
« Last post by mgagliardi on September 08, 2018, 06:35:28 PM »
Iím running a trial of 4.2.3 and I can see my traffic is being optimized (cool!). I have now enabled TCP-X (TCP Acceleration) and nothing appears to have changed/improved performance-wise. My link has ~40ms (20 Mbps link) latency and without acceleration Iím hitting ~2.7Mbps throughput. With acceleration enabled Iíve actually dropped a bit down to ~2.4Mbps. Is there any way to confirm that traffic is being accelerated? FWIW this is on a single subnet and the Wanos instances are in bridge mode. No routes added, the optimization rule (working) is set up for the subnet and I just have the default ďaccelerate everythingĒ rule in for TCP-X.

Thanks!
Pages: 1 2 3 [4] 5 6 ... 10