340
edits
Analyze connections between remote sites: Difference between revisions
Jump to navigation
Jump to search
Analyze connections between remote sites (view source)
Revision as of 15:26, 9 April 2020
, 9 April 2020no edit summary
m (Martin.fesser moved page 6- Investigating network problems on remote sites to Investigating network problems on remote sites) |
No edit summary |
||
| Line 1: | Line 1: | ||
== | == Problem == | ||
Often multiple locations (offices) are connected through a dedicated | Often multiple locations (offices) are connected through a dedicated | ||
line. Sometimes network problems are reported which cannot be easily | line. Sometimes network problems are reported which cannot be easily | ||
| Line 8: | Line 8: | ||
measure the packet loss and network latency between a local | measure the packet loss and network latency between a local | ||
installation and a remote site. | installation and a remote site. | ||
{| | {| | ||
|[[File:Ap-mm-path-measurement-3.png|600px|thumb|right]] | |[[File:Ap-mm-path-measurement-3.png|600px|thumb|right]] | ||
| Line 15: | Line 16: | ||
internet. | internet. | ||
== Requirements == | |||
== | |||
1. You need two Allegro Network Multimeter of any type. | 1. You need two Allegro Network Multimeter of any type. | ||
| Line 22: | Line 22: | ||
2. One Multimeter (the master device) will get traffic information from the remote Multimeter via a regular SSL connection. This means the master device must be able to connect to the remote device. If a firewall is in place between both devices, an additional rule might be necessary to connect the remote device on port 443. | 2. One Multimeter (the master device) will get traffic information from the remote Multimeter via a regular SSL connection. This means the master device must be able to connect to the remote device. If a firewall is in place between both devices, an additional rule might be necessary to connect the remote device on port 443. | ||
== Device installation == | |||
== | |||
1. Install the master device somewhere in your network where it can see the traffic sent to the remote site and received from the remote site. The multimeter can be installed on a mirror port on a switch which sees all the traffic, or inline between the local network and uplink to the remote site. | 1. Install the master device somewhere in your network where it can see the traffic sent to the remote site and received from the remote site. The multimeter can be installed on a mirror port on a switch which sees all the traffic, or inline between the local network and uplink to the remote site. | ||
| Line 29: | Line 28: | ||
2. Install the remote device on the remote site at a network position where it sees all traffic from and to the local network. Again, this can be a mirror port on a switch on the remote site, or inline between the remote network and the link to the local network. | 2. Install the remote device on the remote site at a network position where it sees all traffic from and to the local network. Again, this can be a mirror port on a switch on the remote site, or inline between the remote network and the link to the local network. | ||
== Configuration == | |||
== | |||
{| | {| | ||
| Line 40: | Line 37: | ||
* The IP address of the management port. | * The IP address of the management port. | ||
* The TCP port under which the web site of the Multimeter is accessible (defaults to 443). | * The TCP port under which the web site of the Multimeter is accessible (defaults to 443). | ||
* The username and password of the admin user (or any other user with admin role). | * The username and password of the admin user (or any other user with admin role). | ||
| Line 69: | Line 64: | ||
'''(k)''' The "Remote client status" should say "connected". If not, a button appears which can be clicked to reconnect to the remote device. Any error will be printed in a info box. | '''(k)''' The "Remote client status" should say "connected". If not, a button appears which can be clicked to reconnect to the remote device. Any error will be printed in a info box. | ||
== Evaluation == | |||
== | |||
{| | {| | ||
| Line 84: | Line 77: | ||
devices, but excludes the traffic that is only seen on one device. | devices, but excludes the traffic that is only seen on one device. | ||
=== Checking packet loss === | |||
To identify packet loss during a time interval, first select the | To identify packet loss during a time interval, first select the | ||
| Line 105: | Line 97: | ||
17:45:29. | 17:45:29. | ||
=== Checking latency === | |||
The "Two-way latency" graph shows the minimum, maximum and average | The "Two-way latency" graph shows the minimum, maximum and average | ||
| Line 124: | Line 115: | ||
experience worse quality due to high latency. | experience worse quality due to high latency. | ||
=== How to identify traffic happening during packet loss or high latency === | |||
First select the interesting time window when the packet loss or high | First select the interesting time window when the packet loss or high | ||