Hello!
We plan to use QoS Round Trip Sensor to make a measure of internet channels quality between our offices. Every remote office and our main office has it's own Probe. But when we creating this sensor it does't work (Timeout, No packets recieved, 50000 port is in use), whatever what settings we change. So i think i don't understand how it work. So, just to be shure:
1) On what device must we create QoS sensor? Only on Local or Remote Probes or it this sensor i can create on any device in device tree? 2) If we want to meauser quality from both sides, must we create QoS sensor Round Trip on both Probes or one must be QoS Round Trip and other QoS One Way?
Article Comments
Ok! But if i create several QoS Round Trip sensors (by one on every Remote Probe) and for all of them i set one remote point - Local Probe on Core Server no any problem will be with this scheme? Will all sensors work correctly?
Apr, 2019 - Permalink
Hi Vasiliy,
This scheme has no issues. Please note, however, that each QoS Round Trip sensor needs its own Port if all have the Local Probe as target, as it causes issues when multiple requests try to connect to the same port.
Best Regards,
Moritz Heller
Paessler Support Team
Apr, 2019 - Permalink
Is there any limitations for Scanning Interval? As i see in sensor Setting it sending 1000 packets per interval, can i set 60 second interval, or i need something more rare? 10 min, for example?
Apr, 2019 - Permalink
Hi Vasiliy,
There are no limitations for the scanning interval of this Sensor. All limitations or special requirements are listed below the point "Remarks" in the corresponding manual
However, we recommend to use the default value to prevent any issues.
Best Regards,
Moritz Heller
Paessler Support Team
Apr, 2019 - Permalink
Hi Vasiliy,
Thank you for your post.
I will be happy to answer your questions:
With regard to your error, please make sure that no firewall in between blocks the traffic from this Sensor.
For more detailed information, please follow these links:
Best Regards,
Moritz Heller
Paessler Support Team
Apr, 2019 - Permalink