QoSmart

1
QoSmart

• ipengine is deployed at WAN egress point at each
  site
• Each ipengine sees all traffic entering or
  leaving site
• ipagent software on each ipengine timestamps
  all traffic to and from other sites
• ipboss collects all data

2
Topology
ipengine
ipengine
ipengine
ipboss
3
ipboss

• ipboss runs on one central management station
• Collects and records all data from ipengines
• Metrics available on any unidirectional flow
  between two sites OWD, ipdv, throughput and
  packet loss.
• Configurable sampling for longer term graphs

4
OWD
5
Time synchronisation

• Comes with GPS reciever, which provides PPS to
  correct the system time
• Alternatively (but not prefered) ITP a NTP
  derived network time protocol
• One ipengine with GPS provides ITP based time
  data to other ipengines.
• Like NTP, ITP becomes unstable over asymmetric
  paths.

6
Synchronization problems
7
Testing results

• When using ITP over asymmetric paths, the time
  offset becomes the average of the OWDs of both
  directions
• ipengines (10, 100, 1000 Mbit/s) have throughput
  limits when exceeded, system is not able to
  measure.