- Joined
- Jan 11, 2016
- Messages
- 13,304
Cool following up for you.Nope
![]()
Cool following up for you.Nope
![]()
How can I then ensure a low contention on last mile on Vuma?Contention isnt as relative as it used to be as it was more around the last mile. Which should now be uncontended, but that isn't realistic either. PON networks more specifically due to the sharing and splitting. At the ISP level you just really need to manage access capacity which we never saturate. If we need more bandwidth we buy more it's as simple as that.
This morning they ask me for the things serial number.
Vuma trenched last mile is gigabit copper to an aggregation switch. There may be contention on the back haul from that switch to their backbone but I doubt it's a thing.How can I then ensure a low contention on last mile on Vuma?
Yet the cheapest Vuma bundle "Firestream" advertises UNCONTENDED.For sure, but there's 'transparency'. And conversely if you want 1:1 contention ratios you can have it but expect to pay bombs...
Between how many people?Vuma trenched last mile is gigabit copper to an aggregation switch. There may be contention on the back haul from that switch to their backbone but I doubt it's a thing.
Change 160M to 100M
Why? I got a 200Mbps account...Change 160M to 100M
Oh my bad. Speed test looked like 100Why? I got a 200Mbps account...
You would assume Vuma would do these tests onsite before they leave.
What would be the correct iperf settings for 20M line?
My install is coming up and will make sure I hold him hostage (got 5 rottweilers) until I see a pass test.
What does a pass look like?
I would guess 18 - 20.
This is accepted as a pass.
c:\iperf>iperf3.exe -R -u -b 180M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.88.252 port 54418 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 21.7 MBytes 182 Mbits/sec 0.070 ms 73/2845 (2.6%)
[ 4] 1.00-2.00 sec 21.4 MBytes 180 Mbits/sec 0.122 ms 0/2745 (0%)
[ 4] 2.00-3.00 sec 21.5 MBytes 180 Mbits/sec 0.113 ms 0/2748 (0%)
[ 4] 3.00-4.00 sec 21.5 MBytes 180 Mbits/sec 0.056 ms 0/2746 (0%)
[ 4] 4.00-5.00 sec 21.5 MBytes 180 Mbits/sec 0.107 ms 1/2747 (0.036%)
[ 4] 5.00-6.00 sec 21.5 MBytes 180 Mbits/sec 0.051 ms 0/2746 (0%)
[ 4] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec 0.053 ms 1/2747 (0.036%)
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 0.107 ms 0/2747 (0%)
[ 4] 8.00-9.00 sec 21.4 MBytes 180 Mbits/sec 0.070 ms 0/2744 (0%)
[ 4] 9.00-10.00 sec 21.5 MBytes 180 Mbits/sec 0.055 ms 0/2749 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 218 MBytes 183 Mbits/sec 0.067 ms 75/27961 (0.27%)
[ 4] Sent 27961 datagrams
iperf Done.
200/200
Which? The last mile?Between how many people?
The ont was swapped out but wasn't provisioned yet or configured or whatever it is they do. So wasn't syncing.You would assume Vuma would do these tests onsite before they leave.
Yes, between me and vuma.Which? The last mile?