Release notes, June 29, 2015

Important notice: 

Netrounds customer base is growing. As a result of this done some changes was required to our server environment. We have changed/added IP addresses used by Probes and Agents to connect to the server, as well as for the snmp trap source. If you have stringent firewall rules for the Probes and Agents to be able to connect to login.netrounds.com over TCP port 443, or for receiving snmp traps, you need to add firewall rules to allow new IP addresses.

login.netrounds.com (probes)

54.72.155.135

52.17.235.179

Outgoing connection over TCP port 443.

agent.netrounds.com (agents)

54.154.189.18

52.17.148.60

Outgoing connection over TCP port 443.

app.netrounds.com (snmp trap source)

52.16.180.206

52.16.81.4

Incoming traps over UDP port 161.

Note: If all your Probes and Agents went offline during the upgrade, you need to make sure that your firewall is not blocking these new IP addresses.

After the upgrade, you can remove the firewall openings for the current IP addresses, that are:

Probes - 54.247.187.157

Agents - 54.247.95.88

SNMP-trap - 176.34.97.238

The server upgrade will improve the performance, scalability, and response times of Netrounds.

New features

Support for RFC 6349 - Framework for TCP Throughput Testing

This framework describes a practical methodology for measuring end-to-end TCP Throughput in an IP network. The goal iof the RFC was to provide a better indication in regard to user experience. Read more about RFC 6349 in this blog post

Possibility for customers to trigger Probe upgrades

Instead of Netrounds always triggering Probe upgrades automatically, it will now be possible for you as a customer to trigger the upgrade at a time that suits you. A notification will be shown in the Netrounds GUI when new upgrades are available.

Improvements

See what login server the Probes are connected to 

It will be shown in the GUI if a Probe is connected directly to login.netrounds.com or via a Proxy.

Minor improvements to Y.1731

Changed name on Multi-TCP QoS test script and some improvements

The script will now be called "QoS profiling", and some improvements have been made to the reports from the test. The QoS profiling test is a quick and simple validation that the network QoS settings are correct, in terms of how much bandwidth that is allocated for each QoS class.

Time synchronization requirement loosened up

In order to maintain high accuracy on delay sensitive tests, the time synchronization requirement has earlier been 4 ms in order to start such tests. We have now modified this requirement to a warning if not below 4 ms, and to not start the test if over 100 ms. This since many customers prefers a warning, before having to wait until the time sync is good enough.

Support for multiple interfaces on Agents

The Agent application is a lightweight measurement app that can be installed on Windows, MAC and Linux operating systems, and that can do both network performance measurements (TCP/UDP) and IPTV quality measurements. 

When using Agents for IPTV, it is sometimes necessary to use two interfaces - one with Internet connectivity for management, and one for IPTV measurements on an isolated IPTV network.

From now on, the Agents support multiple interfaces for this use-case.

DNS and routes are shown in the probe interface tabs
This so that you can quickly understand how your Probes perceive these important network settings.

Last login is shown for offline probes
If the Probe is offline, it will be easier for you to understand why it went offline, since you can correlate with known actions and events.

Possibility to clone a monitoring group
Simplifies the work of setting up many similar monitorings in large scale deployments.

Have more questions? Submit a request

Comments

Powered by Zendesk