Transcript Test of Ipanematech equipment

QoSmart
• ip|engine is deployed at WAN egress point
at each site
• Each ip|engine sees all traffic entering or
leaving site
• ip|agent software on each ip|engine
timestamps all traffic to and from other sites
• ip|boss collects all data
Oct 18th, 2003
TF-NGN, Ipanematech
1
Topology
ip|engine
ip|engine
ip|engine
ip|boss
Oct 18th, 2003
TF-NGN, Ipanematech
2
ip|boss
• ip|boss runs on one central management
station
• Collects and records all data from ip|engines
• Metrics available on any unidirectional flow
between two sites: OWD, ipdv, throughput
and packet loss.
• Configurable sampling for longer term
graphs
Oct 18th, 2003
TF-NGN, Ipanematech
3
OWD
Oct 18th, 2003
TF-NGN, Ipanematech
4
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 ip|engine with GPS provides ITP based
time data to other ip|engines.
• Like NTP, ITP becomes unstable over
asymmetric paths.
Oct 18th, 2003
TF-NGN, Ipanematech
5
Synchronization problems
Oct 18th, 2003
TF-NGN, Ipanematech
6
Testing results
• When using ITP over asymmetric paths, the
time offset becomes the average of the
OWD’s of both directions
• ip|engines (10, 100, 1000 Mbit/s) have
throughput limits; when exceeded, system is
not able to measure.
Oct 18th, 2003
TF-NGN, Ipanematech
7