{"id":1168,"date":"2019-06-21T14:54:39","date_gmt":"2019-06-21T11:54:39","guid":{"rendered":"https:\/\/blog.3kgroup.ee:443\/?p=1168"},"modified":"2020-05-12T15:00:02","modified_gmt":"2020-05-12T12:00:02","slug":"mesh-vorgu-testid","status":"publish","type":"post","link":"https:\/\/blog.3kgroup.ee:443\/?p=1168","title":{"rendered":"802.11ac MESH v\u00f5rgu testid"},"content":{"rendered":"\n<p>Viisime l\u00e4bi oma kontoris l\u00e4bi katsed <a href=\"https:\/\/blog.3kgroup.ee:443\/mesh-juhtmevaba-ap-de-uhenduse-tehnoloogia\/\">MESH<\/a> v\u00f5rgu suutlikuse hindamiseks. Selleks valisime kaks Ruckus R610 AP'd, mis on meil tavaliselt kasutusel erinevatel \u00fcritustel WiFi v\u00f5rgu loomiseks. Selle AP kohta v\u00f5ib l\u00e4hemalt lugeda siit:  <br><a href=\"https:\/\/blog.3kgroup.ee:443\/ruckus-r610-ac-wave-2-3x33\/\">https:\/\/blog.3kgroup.ee:443\/ruckus-r610-ac-wave-2-3x33\/<\/a>. <\/p>\n\n\n\n<p>Meshi v\u00f5imekus on k\u00f5igil Ruckuse AP'del, v\u00e4lja arvatud 300 seeria AP'd.<\/p>\n\n\n\n<p>Testi tarbeks l\u00f5ime kahe R610 vahel Mesh v\u00f5rgu, \u00fchendasime kaks Linuxiga t\u00f6\u00f6tavat 1GbE pordiga arvutit otse AP LAN pordi k\u00fclge ning k\u00e4ivitasime iperf testi. Iperf testi seadistasime nii, et korraga saadetakse andmeid mitut voogu pidi, kasutades TCP protokolli ning test oli full-duplex. AP'd asetasime erinevatesse ruumidesse, otsen\u00e4htavus AP'de vahel puudus. Kuna meie kontor asub Tallinna piirkonnas, kus on korraga \u00f5hus v\u00e4ga palju andmeside liiklust, siis t\u00f5en\u00e4oliselt ei ole paremas asukohas keeruline saada paremaid tulemusi.<\/p>\n\n\n\n<p>Selle lihtsa testi tulemusena saime andmesidekiiruseks kahe arvuti vahel v\u00e4hemalt 300\/300 Mbit\/s, kui AP'd asusid \u00fcksteise suhtes \"seljaga\", st AP \u00fclemised osad vaatasid \u00fcksteise poole ning 400\/500 Mbit\/s kui AP'd olid \u00fcksteise poole k\u00fcljega, ehk rohkem samal tasandil.<\/p>\n\n\n\n<p>Seljaga \u00fcksteise suhtes asetus imiteerib olukorda, kus AP'd asuvad erinevatel korrustel, kuid pakuvad kasutajatele samal korrusel paremat levi. K\u00fcljega asetus olukorda, kus AP'd asuvad samal tasapinnal, kuid mingil p\u00f5hjusel ei ole v\u00f5imalik ruumide vahel kaablit vedada.<\/p>\n\n\n\n<p>Ruckuse MESH lahendus on v\u00e4ga erinev teiste tootjate lahendustest, sest MESH AP-d suhtlevad omavahel kahesuunalise <a href=\"https:\/\/blog.3kgroup.ee:443\/mis-on-ruckus-beamflex-nutiantenn\/\">BeamFlex juhitava suundatenniga,<\/a>  See on v\u00e4ga erinev lahendus<em> Beamforming<\/em>  tavalahendusest, kus p\u00fc\u00fctakse leida ainult kahe signaali faaside liitumispunkti signaalitugevuse parandamiseks. Beamflex v\u00f5imaldab signaale suunata ja antenni polarisatsiooni muuta, tulemuseks on tihedam ruumiline sageduste uuestikasutus.  Samuti on AP-de andmeedastuskiirus tavaliselt suurem, antud juhul siis half duplex TCP\/IP 600Mb\/s, mis tavaliselt kliendi ja AP vahel ei realiseeru. Esiteks on kliendid tavaliselt 2x2 MIMO ja teiseks pole nende klientide levitingimused kuigi head. Kui arvutada kargelt kogu s\u00fcsteemi l\u00e4bilaskvust, siis suure t\u00f5en\u00e4osusega on kliendi liiklus kahe raadio peale TCP\/IP liiklusena 300 Mb\/s ja teine 300 Mb\/s l\u00e4heb MESH liiklusele. <\/p>\n\n\n\n<p>Kuna Wi-Fi protokoll baseerub tegelikult ikkagi ALOHA protokollil, mis on jagatud ajaslottideks, ja samuti on tarvis k\u00f5iki pakette kviteerida, veenduda, et \u00f5hk oleks enne saatmist vaba, jne, l\u00e4heb v\u00e4ga suur osa 1300 Mb\/s teoreetilisest maksimumkiirusest s\u00fcsteemi enda halduseks. Alles <a href=\"https:\/\/blog.3kgroup.ee:443\/mis-on-802-11ax-6g-wi-fi-standard\/\">802.11ax standard<\/a> pakub siin leevendust OFDMA kahesuunalise multipleksimise kaudu.  Seega kui praeguse tehnikaga valida <a href=\"https:\/\/blog.3kgroup.ee:443\/ruckus-r730-6g-11ax-tugijaam\/\">R730 AP-d<\/a> (8x8 MIMO) ja panna MESH v\u00f5rku 10 AP-d, saame v\u00e4ga t\u00f5husa MESH v\u00f5rgu, kus AP-de omavaheline liiklus toimub paraleelselt OFDMA multipleksimisega. Suure t\u00f5en\u00e4osusega r\u00e4\u00e4givad veel enamus kliendiseadmeid veel 11n ja 11ac standardiga, aga selles 11ax 6G Wi-Fi lahenduses pudelikael tekkida ei saa, sest sarnaselt meie<a href=\"https:\/\/blog.3kgroup.ee:443\/ruckus-r610-ac-wave-2-3x33\/\"> R610 testiga<\/a>&nbsp;on AP-de omavaheline suhtluskanal kordades t\u00f5husam kui AP-de ja kliendi vaheline suhtluskanal.  Lisaks on <a href=\"https:\/\/blog.3kgroup.ee:443\/6-ghz-wi-fi-ka-eruroopas-tulekul\/\">tulevikus 500 MHz lisaspektrit<\/a>, et 802.11ax standardi seadmetega MESH v\u00f5rke luua.<br><\/p>\n\n\n\n<p>Testi tulemused on n\u00e4ha allpool.<\/p>\n\n\n\n<p>\"Seljad koos\" asetus:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Martins-MacBook-Pro:iperf-2.0.5-macos-x86_64 martin$ .\/iperf -c 192.168.3.76 -d -P 4 -w 128K<br> Server listening on TCP port 5001<br> TCP window size:  128 KByte<br> <br> Client connecting to 192.168.3.76, TCP port 5001<br> TCP window size:  129 KByte (WARNING: requested  128 KByte)<br> [  8] local 192.168.3.23 port 52242 connected with 192.168.3.76 port 5001<br> [  5] local 192.168.3.23 port 52239 connected with 192.168.3.76 port 5001<br> [  7] local 192.168.3.23 port 52241 connected with 192.168.3.76 port 5001<br> [  6] local 192.168.3.23 port 52240 connected with 192.168.3.76 port 5001<br> [ 10] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39720<br> [  9] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39718<br> [ 11] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39722<br> [ 12] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39724<br> [ ID] Interval       Transfer     Bandwidth<br> [  8]  0.0-10.0 sec  85.2 MBytes  71.5 Mbits\/sec<br> [  6]  0.0-10.0 sec  87.4 MBytes  73.3 Mbits\/sec<br> [  7]  0.0-10.0 sec  72.5 MBytes  60.7 Mbits\/sec<br> [  5]  0.0-10.0 sec  87.1 MBytes  73.0 Mbits\/sec<br><strong> [SUM]  0.0-10.0 sec   332 MBytes   278 Mbits\/sec<\/strong><br> [ 11]  0.0-10.0 sec  95.6 MBytes  79.9 Mbits\/sec<br> [ 10]  0.0-10.1 sec  95.5 MBytes  79.7 Mbits\/sec<br> [  9]  0.0-10.1 sec  97.6 MBytes  81.5 Mbits\/sec<br> [ 12]  0.0-10.1 sec  95.0 MBytes  79.3 Mbits\/sec<br> <strong>[SUM]  0.0-10.1 sec   384 MBytes   320 Mbits\/sec<\/strong><br><br>Martins-MacBook-Pro:iperf-2.0.5-macos-x86_64 martin$ .\/iperf -c 192.168.3.76 -d -P 8 -w 128K<br> Server listening on TCP port 5001<br> TCP window size:  128 KByte<br> <br> Client connecting to 192.168.3.76, TCP port 5001<br> TCP window size:  129 KByte (WARNING: requested  128 KByte)<br> [ 13] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39726<br> [  6] local 192.168.3.23 port 52254 connected with 192.168.3.76 port 5001<br> [ 12] local 192.168.3.23 port 52260 connected with 192.168.3.76 port 5001<br> [  9] local 192.168.3.23 port 52257 connected with 192.168.3.76 port 5001<br> [  5] local 192.168.3.23 port 52253 connected with 192.168.3.76 port 5001<br> [ 11] local 192.168.3.23 port 52259 connected with 192.168.3.76 port 5001<br> [ 10] local 192.168.3.23 port 52258 connected with 192.168.3.76 port 5001<br> [  7] local 192.168.3.23 port 52255 connected with 192.168.3.76 port 5001<br> [  8] local 192.168.3.23 port 52256 connected with 192.168.3.76 port 5001<br> [ 14] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39732<br> [ 15] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39734<br> [ 16] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39736<br> [ 17] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39738<br> [ 18] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39740<br> Waiting for server threads to complete. Interrupt again to force quit.<br> [ ID] Interval       Transfer     Bandwidth<br> [ 12]  0.0-10.0 sec  59.5 MBytes  49.9 Mbits\/sec<br> [  9]  0.0-10.0 sec  55.9 MBytes  46.8 Mbits\/sec<br> [  5]  0.0-10.0 sec  60.4 MBytes  50.5 Mbits\/sec<br> [ 11]  0.0-10.0 sec  59.4 MBytes  49.7 Mbits\/sec<br> [  7]  0.0-10.0 sec  57.1 MBytes  47.8 Mbits\/sec<br> [ 10]  0.0-10.1 sec  41.8 MBytes  34.8 Mbits\/sec<br> [ 15]  0.0-10.2 sec  66.5 MBytes  54.6 Mbits\/sec<br> [ 18]  0.0-10.2 sec  67.5 MBytes  55.4 Mbits\/sec<br> [ 13]  0.0-10.2 sec  70.4 MBytes  57.8 Mbits\/sec<br> [ 14]  0.0-10.2 sec  66.9 MBytes  54.9 Mbits\/sec<br> [ 16]  0.0-10.2 sec  68.1 MBytes  55.9 Mbits\/sec<br> [ 17]  0.0-10.2 sec  66.8 MBytes  54.8 Mbits\/sec<br> <strong>[SUM]  0.0-10.2 sec   406 MBytes   333 Mbits\/sec<\/strong><br> [  6]  0.0-10.2 sec  1.75 MBytes  1.44 Mbits\/sec<br> [  8]  0.0-10.2 sec  1.75 MBytes  1.44 Mbits\/sec<br> <strong>[SUM]  0.0-10.2 sec   338 MBytes   277 Mbits\/sec<\/strong><\/pre>\n\n\n\n<p>P\u00e4rast samale tasapinnale asetust olid tulemused tunduvalt paremad, kuna AP antennid on omavahel soodsamalt asetatud:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Martins-MacBook-Pro:iperf-2.0.5-macos-x86_64 martin$ .\/iperf -c 192.168.3.76 -d -P 8 -w 128K<br> Server listening on TCP port 5001<br> TCP window size:  128 KByte<br> <br> Client connecting to 192.168.3.76, TCP port 5001<br> TCP window size:  129 KByte (WARNING: requested  128 KByte)<br> [ 13] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39726<br> [  6] local 192.168.3.23 port 52254 connected with 192.168.3.76 port 5001<br> [ 12] local 192.168.3.23 port 52260 connected with 192.168.3.76 port 5001<br> [  9] local 192.168.3.23 port 52257 connected with 192.168.3.76 port 5001<br> [  5] local 192.168.3.23 port 52253 connected with 192.168.3.76 port 5001<br> [ 11] local 192.168.3.23 port 52259 connected with 192.168.3.76 port 5001<br> [ 10] local 192.168.3.23 port 52258 connected with 192.168.3.76 port 5001<br> [  7] local 192.168.3.23 port 52255 connected with 192.168.3.76 port 5001<br> [  8] local 192.168.3.23 port 52256 connected with 192.168.3.76 port 5001<br> [ 14] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39732<br> [ 15] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39734<br> [ 16] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39736<br> [ 17] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39738<br> [ 18] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39740<br> Waiting for server threads to complete. Interrupt again to force quit.<br> [ ID] Interval       Transfer     Bandwidth<br> [ 12]  0.0-10.0 sec  59.5 MBytes  49.9 Mbits\/sec<br> [  9]  0.0-10.0 sec  55.9 MBytes  46.8 Mbits\/sec<br> [  5]  0.0-10.0 sec  60.4 MBytes  50.5 Mbits\/sec<br> [ 11]  0.0-10.0 sec  59.4 MBytes  49.7 Mbits\/sec<br> [  7]  0.0-10.0 sec  57.1 MBytes  47.8 Mbits\/sec<br> [ 10]  0.0-10.1 sec  41.8 MBytes  34.8 Mbits\/sec<br> [ 15]  0.0-10.2 sec  66.5 MBytes  54.6 Mbits\/sec<br> [ 18]  0.0-10.2 sec  67.5 MBytes  55.4 Mbits\/sec<br> [ 13]  0.0-10.2 sec  70.4 MBytes  57.8 Mbits\/sec<br> [ 14]  0.0-10.2 sec  66.9 MBytes  54.9 Mbits\/sec<br> [ 16]  0.0-10.2 sec  68.1 MBytes  55.9 Mbits\/sec<br> [ 17]  0.0-10.2 sec  66.8 MBytes  54.8 Mbits\/sec<br> <strong>[SUM]  0.0-10.2 sec   406 MBytes   333 Mbits\/sec<\/strong><br> [  6]  0.0-10.2 sec  1.75 MBytes  1.44 Mbits\/sec<br> [  8]  0.0-10.2 sec  1.75 MBytes  1.44 Mbits\/sec<br> <strong>[SUM]  0.0-10.2 sec   338 MBytes   277 Mbits\/sec<\/strong><br><br>Martins-MacBook-Pro:iperf-2.0.5-macos-x86_64 martin$ .\/iperf -c 192.168.3.76 -d -P 8 -w 128K<br> Server listening on TCP port 5001<br> TCP window size:  128 KByte<br> <br> Client connecting to 192.168.3.76, TCP port 5001<br> TCP window size:  129 KByte (WARNING: requested  128 KByte)<br> [ 13] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39774<br> [  7] local 192.168.3.23 port 52288 connected with 192.168.3.76 port 5001<br> [ 12] local 192.168.3.23 port 52293 connected with 192.168.3.76 port 5001<br> [  6] local 192.168.3.23 port 52287 connected with 192.168.3.76 port 5001<br> [  5] local 192.168.3.23 port 52286 connected with 192.168.3.76 port 5001<br> [  9] local 192.168.3.23 port 52290 connected with 192.168.3.76 port 5001<br> [  8] local 192.168.3.23 port 52289 connected with 192.168.3.76 port 5001<br> [ 11] local 192.168.3.23 port 52292 connected with 192.168.3.76 port 5001<br> [ 10] local 192.168.3.23 port 52291 connected with 192.168.3.76 port 5001<br> [ 15] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39780<br> [ 14] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39788<br> [ 16] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39782<br> [ 17] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39784<br> [ 18] local 192.168.3.23 port 5001 connected with 192.168.3.76 port 39786<br> Waiting for server threads to complete. Interrupt again to force quit.<br> [ ID] Interval       Transfer     Bandwidth<br> [ 12]  0.0-10.0 sec  50.1 MBytes  42.0 Mbits\/sec<br> [  6]  0.0-10.0 sec  68.4 MBytes  57.3 Mbits\/sec<br> [  5]  0.0-10.0 sec  64.4 MBytes  53.9 Mbits\/sec<br> [  8]  0.0-10.0 sec  68.6 MBytes  57.4 Mbits\/sec<br> [ 17]  0.0-10.1 sec  87.0 MBytes  72.2 Mbits\/sec<br> [  9]  0.0-10.0 sec  71.5 MBytes  59.7 Mbits\/sec<br> [ 15]  0.0-10.1 sec  86.9 MBytes  72.1 Mbits\/sec<br> [ 14]  0.0-10.1 sec  88.2 MBytes  73.2 Mbits\/sec<br> [ 18]  0.0-10.1 sec  86.4 MBytes  71.6 Mbits\/sec<br> [ 13]  0.0-10.1 sec  90.8 MBytes  75.1 Mbits\/sec<br> [ 16]  0.0-10.1 sec  87.1 MBytes  72.1 Mbits\/sec<br> <strong>[SUM]  0.0-10.1 sec   526 MBytes   436 Mbits\/sec<\/strong><br> [  7]  0.0-10.1 sec  2.25 MBytes  1.87 Mbits\/sec<br> [ 10]  0.0-10.1 sec  2.25 MBytes  1.87 Mbits\/sec<br> [ 11]  0.0-10.2 sec  69.9 MBytes  57.7 Mbits\/sec<br> <strong>[SUM]  0.0-10.2 sec   397 MBytes   328 Mbits\/sec<\/strong><\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Viisime l\u00e4bi oma kontoris l\u00e4bi katsed MESH v\u00f5rgu suutlikuse hindamiseks. Selleks valisime kaks Ruckus R610 AP'd, mis on meil tavaliselt kasutusel erinevatel \u00fcritustel WiFi v\u00f5rgu loomiseks. Selle AP kohta v\u00f5ib [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[29],"tags":[75,68,24],"class_list":["post-1168","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-3k-support-teenused","tag-juuni","tag-mesh","tag-ruckus"],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/posts\/1168","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1168"}],"version-history":[{"count":8,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/posts\/1168\/revisions"}],"predecessor-version":[{"id":2787,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/posts\/1168\/revisions\/2787"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=\/wp\/v2\/media\/1169"}],"wp:attachment":[{"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1168"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1168"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.3kgroup.ee:443\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1168"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}