You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Denis Kandrov (JIRA)" <ji...@apache.org> on 2012/06/01 09:21:22 UTC
[jira] [Created] (OPENMEETINGS-306) Initial network quality test
Denis Kandrov created OPENMEETINGS-306:
------------------------------------------
Summary: Initial network quality test
Key: OPENMEETINGS-306
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
Project: Openmeetings
Issue Type: Task
Environment: Linux
Reporter: Denis Kandrov
Priority: Minor
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
{{ $ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested> }}
After this you will see the following report:
{{Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-306) Initial network quality test
Posted by "Denis Kandrov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Kandrov updated OPENMEETINGS-306:
---------------------------------------
Description:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
After this you will see the following report:
Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test
was:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
{noformat}$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>{noformat}
After this you will see the following report:
Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test
> Initial network quality test
> ----------------------------
>
> Key: OPENMEETINGS-306
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
> Project: Openmeetings
> Issue Type: Task
> Environment: Linux
> Reporter: Denis Kandrov
> Priority: Minor
> Attachments: network_test.sh
>
>
> I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
> If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
> And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
> To solve this problem, I wrote a small script on bash.
> The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
> For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
> Then you run the script on the reference server:
> $ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
> After this you will see the following report:
> Start testing latency and jitter
> ========================================
> Jitter = 8 for 100 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 10000 bites (ping)
> Max latency is 20
> Jitter = 100 % from 8 ms
> Start testing opened ports
> ========================================
> Port 5080 available
> Port 1935 available
> Port 8088 available
> Start testing bandwidth of server
> ========================================
> Start outbound test
> [SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
> [SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
> [SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
> Stop server
> End outbound test
> Start inbound test
> [SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
> [SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
> [SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
> Stop server
> End inbound test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-306) Initial network quality test
Posted by "Denis Kandrov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Kandrov updated OPENMEETINGS-306:
---------------------------------------
Description:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
{noformat}$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>{noformat}
After this you will see the following report:
Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test
was:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
After this you will see the following report:
Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test
> Initial network quality test
> ----------------------------
>
> Key: OPENMEETINGS-306
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
> Project: Openmeetings
> Issue Type: Task
> Environment: Linux
> Reporter: Denis Kandrov
> Priority: Minor
> Attachments: network_test.sh
>
>
> I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
> If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
> And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
> To solve this problem, I wrote a small script on bash.
> The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
> For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
> Then you run the script on the reference server:
> {noformat}$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>{noformat}
> After this you will see the following report:
> Start testing latency and jitter
> ========================================
> Jitter = 8 for 100 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 10000 bites (ping)
> Max latency is 20
> Jitter = 100 % from 8 ms
> Start testing opened ports
> ========================================
> Port 5080 available
> Port 1935 available
> Port 8088 available
> Start testing bandwidth of server
> ========================================
> Start outbound test
> [SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
> [SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
> [SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
> Stop server
> End outbound test
> Start inbound test
> [SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
> [SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
> [SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
> Stop server
> End inbound test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-306) Initial network quality test
Posted by "Denis Kandrov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Kandrov updated OPENMEETINGS-306:
---------------------------------------
Description:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
<code>$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested></code>
After this you will see the following report:
{{Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test}}
was:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
{{ $ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested> }}
After this you will see the following report:
{{Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test}}
> Initial network quality test
> ----------------------------
>
> Key: OPENMEETINGS-306
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
> Project: Openmeetings
> Issue Type: Task
> Environment: Linux
> Reporter: Denis Kandrov
> Priority: Minor
>
> I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
> If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
> And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
> To solve this problem, I wrote a small script on bash.
> The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
> For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
> Then you run the script on the reference server:
> <code>$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested></code>
> After this you will see the following report:
> {{Start testing latency and jitter
> ========================================
> Jitter = 8 for 100 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 10000 bites (ping)
> Max latency is 20
> Jitter = 100 % from 8 ms
> Start testing opened ports
> ========================================
> Port 5080 available
> Port 1935 available
> Port 8088 available
> Start testing bandwidth of server
> ========================================
> Start outbound test
> [SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
> [SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
> [SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
> Stop server
> End outbound test
> Start inbound test
> [SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
> [SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
> [SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
> Stop server
> End inbound test}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-306) Initial network quality test
Posted by "Denis Kandrov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Kandrov updated OPENMEETINGS-306:
---------------------------------------
Attachment: network_test.sh
> Initial network quality test
> ----------------------------
>
> Key: OPENMEETINGS-306
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
> Project: Openmeetings
> Issue Type: Task
> Environment: Linux
> Reporter: Denis Kandrov
> Priority: Minor
> Attachments: network_test.sh
>
>
> I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
> If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
> And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
> To solve this problem, I wrote a small script on bash.
> The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
> For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
> Then you run the script on the reference server:
> $ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
> After this you will see the following report:
> Start testing latency and jitter
> ========================================
> Jitter = 8 for 100 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 10000 bites (ping)
> Max latency is 20
> Jitter = 100 % from 8 ms
> Start testing opened ports
> ========================================
> Port 5080 available
> Port 1935 available
> Port 8088 available
> Start testing bandwidth of server
> ========================================
> Start outbound test
> [SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
> [SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
> [SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
> Stop server
> End outbound test
> Start inbound test
> [SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
> [SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
> [SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
> Stop server
> End inbound test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-306) Initial network quality test
Posted by "Denis Kandrov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Kandrov updated OPENMEETINGS-306:
---------------------------------------
Description:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
After this you will see the following report:
Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test
was:
I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
To solve this problem, I wrote a small script on bash.
The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
Then you run the script on the reference server:
<code>$ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested></code>
After this you will see the following report:
{{Start testing latency and jitter
========================================
Jitter = 8 for 100 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 1000 bites (ping)
Max latency is 8
Jitter = 8 for 1000 packets with size 10000 bites (ping)
Max latency is 20
Jitter = 100 % from 8 ms
Start testing opened ports
========================================
Port 5080 available
Port 1935 available
Port 8088 available
Start testing bandwidth of server
========================================
Start outbound test
[SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
[SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
.....
[SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
[SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
Stop server
End outbound test
Start inbound test
[SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
[SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
.....
[SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
[SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
Stop server
End inbound test}}
> Initial network quality test
> ----------------------------
>
> Key: OPENMEETINGS-306
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-306
> Project: Openmeetings
> Issue Type: Task
> Environment: Linux
> Reporter: Denis Kandrov
> Priority: Minor
> Attachments: network_test.sh
>
>
> I regularly install OpenMeetings on different servers, and before installation I am asked whether the work OM.
> If the parameters of server hardware, I can quickly check, to verify the quality of the network connection is not so easy.
> And you do not want to waste time re-installing OM on another server, if it turns out that the server connection is bad.
> To solve this problem, I wrote a small script on bash.
> The solution consists of the following, I have a server with good network connection and guaranteed bandwidth - a reference server.
> For using of the script requires that iperf was installed and ssh with authorization through a certificate was configured.
> Then you run the script on the reference server:
> $ ./network_test.sh <ip of the reference server> <ssh login of the server being tested> <ip address of the server being tested>
> After this you will see the following report:
> Start testing latency and jitter
> ========================================
> Jitter = 8 for 100 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 1000 bites (ping)
> Max latency is 8
> Jitter = 8 for 1000 packets with size 10000 bites (ping)
> Max latency is 20
> Jitter = 100 % from 8 ms
> Start testing opened ports
> ========================================
> Port 5080 available
> Port 1935 available
> Port 8088 available
> Start testing bandwidth of server
> ========================================
> Start outbound test
> [SUM] 0.0- 5.0 sec 5.87 MBytes 9.84 Mbits/sec
> [SUM] 5.0-10.0 sec 5.70 MBytes 9.57 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 5.63 MBytes 9.45 Mbits/sec
> [SUM] 0.0-30.2 sec 34.3 MBytes 9.53 Mbits/sec
> Stop server
> End outbound test
> Start inbound test
> [SUM] 0.0- 5.0 sec 7.47 MBytes 12.5 Mbits/sec
> [SUM] 5.0-10.0 sec 9.28 MBytes 15.6 Mbits/sec
> .....
> [SUM] 25.0-30.0 sec 8.38 MBytes 14.1 Mbits/sec
> [SUM] 0.0-43.2 sec 55.9 MBytes 10.9 Mbits/sec
> Stop server
> End inbound test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira