When the Scenario Heartbeat interval was set after Prepare() was executed on
an Endpoint, the new Scenario Heartbeat interval value was not propagated to the Endpoint.
The MeetingPoint could mark an Endpoint as "unavailable" when a test longer
than 1 minute was running.
This could lead to the ByteBlower GUI stopping a scenario while the test was
(rightfully) still running
- The server now provides latency histograms over time when using the latency distribution trigger. This allows to have latency histograms per configured measurement interval.
This feature is useful when measuring the QeD performance of a specific flow.
- The TPID (EtherType) of a VLAN tag can now be configured through the API.
- Faster filtering for traffic containing multiple VLAN tags.
- The ByteBlower 2100 and ByteBlower 4100 server series did not support 4 stacked VLAN tags as the other series did. Now all systems have the same limit.
- The MeetingPoint will now automatically query the ByteBlower Endpoint for the test results when the Endpoint returns after a test.
- The MeetingPoint needed up to 5 seconds for initial registration of an Endpoint. The MeetingPoint now temporarily lowers the communication interval so this procedure finishes earlier.
- The MeetingPoint tagged unverified ByteBlower Endpoint platforms as “Unsupported”. The tag is renamed to “Unverified”, which means Excentis did not have tested this platform.
- The MeetingPoint stopped accepting API calls when an “Unavailable” ByteBlower Endpoint was addressed. This did not only influence the calling test, but also effected other tests and users with “Available” Endpoints. The only remedy for this was restarting the ByteBlower MeetingPoint service on the ByteBlower server.