![]() |
Poor VM Connection, strange TBB quality monitor etc..
This thread is really for thenry after asking some questions about my tbb graph!
At the moment my internet SEEMS fine, when it comes to downloading, my speed/ping tests also seem spot on, but something is most definitely wrong with my think broadband graph! Live graph: https://www.cableforum.co.uk/images/local/2012/11/4.png Connection stats: https://www.cableforum.co.uk/images/local/2012/11/7.png https://www.cableforum.co.uk/images/local/2012/11/8.png Can you, or anyone else, shed some light on what's wrong with my connection that's showing such heavy downstream load on the tbb graph? Thanks in advance :) http://www.pingtest.net/result/73030705.png https://www.cableforum.co.uk/images/local/2012/11/9.png |
Re: Poor VM Connection, strange TBB quality monitor etc..
just for me :blush:
as mentioned the doubles ETA for the area you live in is around May 2013. you'll probably be sent a senior tech by the CEOs office if you havent already had 1 out. The tech wont be able to cure it. Power levels are fine but there wouldnt be harm in asking the tech to move you at the cab to lower the upstream levels. He'll then have to probably stick an FP attenuator on or change it for higher attenuation. I think I remember you said infinity wasn't available but I'm sure its enabled in Stockton-on-Tees, that is where you live? ---------- Post added at 19:52 ---------- Previous post was at 19:50 ---------- have you doubled checked the ping monitor IP is correct? ---------- Post added at 19:56 ---------- Previous post was at 19:52 ---------- post up actual day results not just the live graph in a thread of your own on the VM community forum marking each generated day link with dates. as well as all the other stats. staff members on there might be able to get networks on it. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Well, the TBB graph isn't showing heavy downstream activity at all. You can't easily distinguish between DS and US activity on the TBB graph unless it's showing packet loss (red). Then it's either updtream congestion or upstream noise.
What background process on your equipment could be punting anything over the internet? Or are your systems entirely quiet over night? The yellow doesn't matter as much as the blue. I recommend you download and use Jack Dinn's speed test (JDAST). It'll kick in every hour (or whatever interval you set), keeps records and makes a very useful comparison for correlation against TBB. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
I'll mention moving me at the cab when he's back, if this makes any difference? We've had so many issues lately with VM and our connection that they've tried all sorts. It's only been like this since August though when our connection randomly went off for 10 days and no one could tell me what was wrong, ever since then we've had issues with lag and high downstream power levels along with downstream channels dropping and leaving me with only one. My friend suggested asking to be moved onto another docsis to see if this alleviates any issues, is this as you suggested, moving me at the cab, or is this different altogether? I'm still concerned about the large yellow part, however as it doesn't appear to be affecting my internet, should I really be concerned, or just ignore the graph for now? |
Re: Poor VM Connection, strange TBB quality monitor etc..
Seph will be able to assist you better.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
Our systems are entirely quiet over night. Myself and my boyfriend are out during the day and the internet is only really used from 6pm - 11pm then everything (apart from the router) is shut off. I will definitely download JDAST, I'll put this on the other half's laptop as his is constantly wired and mine is not. Weirdly though, whenever we get an engineer visit, it's fine after they leave (see below), then the yellow starts to increase (see second image) 26th - Engineer left my house at 6.30pm [img]Download Failed (1)[/img] 27th [img]Download Failed (1)[/img] ---------- Post added at 20:09 ---------- Previous post was at 20:08 ---------- Quote:
|
Re: Poor VM Connection, strange TBB quality monitor etc..
the moving at the cab and docsis move are unrelated. if you was to be moved to docsis 1.1 then youll be downgraded to 10 or 20 meg.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Ooh er. The other half wouldn't be so happy about that. He's the only reason we're still with VM, the thought of switching to anything other than 60mb brings him out in a cold sweat ;)
|
Re: Poor VM Connection, strange TBB quality monitor etc..
TH might be giving me too much credit!
The yellow means the maximum ping time recorded. It can be just one ping in an hour, but it'll show like that. However, if the blue bit, the average ping, follows the yellow, then the yellow is regular as a high. Into the mix comes the peak time added activity in your network segment. This will produce increased blue and yellow. The high yellow is abnormal though. What did the engineer say he'd done? Did he actually think he'd fixed it? If everything's off except the SH, what could the SH be putting out or doing? Have you tried turning the Firewall off for a while and using Windows firewall in your PCs? Incidentally the reason why you can get these strange graphs but download speed seems unaffected is that the pings are at low priority as compared with TCP or UDP network traffic that you'd be generating/receiving. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
This is about trying to explain the TBB graphs. There appears to be no detriment to the OP's VM service. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
We didn't have an internet connection for 10 days, there was a fault in my area but it shouldn't have kicked me off completely, no one could tell me what was wrong though or when i'd be back online which is why I emailed 3 directors in the hope that it would get sorted. They sent an engineer out, he said there was no problems with my house sending a 'signal' to the cab across the road (its opposite my house) it was the return path that had the issue. He upped my power levels really high and put an attenuator (spelling??) on my box which brought the power levels down inside the house. This worked and we were back online, but had mega issues with speed, not being able to load web pages etc. This is my connection straight after they got us back online, not a problem in sight really: [img]Download Failed (1)[/img] Everything was ok until the middle of October, when my graphs started to look like this. Terrible internet again, slow speeds, loads of lag on fifa, web pages not loading etc: [img]Download Failed (1)[/img] Another engineer came out, said he couldn't see anything that was wrong but swapped the superhub over. The internet was fine for a day: [img]Download Failed (1)[/img] Then it stayed like this for a couple of weeks, really terrible internet connection, slow speeds, loads of lag on FIFA again. [img]Download Failed (1)[/img] A principal technician (awesome chap!) came out and said that our power levels were stupidly high, he dropped these and took off the attenuator that the original engineer fitted. He spent a lot of time at the cab and called another engineer to come out. I didn't fully understand what he said, but he said that he believes theres an issue at the cab and has escalated this. He's on holiday until the 3rd December though so I can't get him to come out again and take another look... After he left the connection was fine, you can see 6pm when he left. [img]Download Failed (1)[/img] Then a few days later it was all over the place again, then we had really bad packet loss every day and only had one downstream channel, which they managed to sort from their end, they said the superhub had been configured incorrectly from their end. They still sent out an engineer who confirmed everything was fine. it IS working fine in terms of speed and pingtests (although we can't test FIFA till payday as my other halfs gold account on the xbox has expired :dunce:), but I firmly believe from my think broadband graph that there's an underlying issue here that's causing these bizarre graphs. This graph is up to date: https://www.cableforum.co.uk/images/local/2012/11/4.png This is a BBmax speed test result from a second ago: Download Speed: 58696 kbps (7337 KB/sec ) Upload Speed: 2892 kbps (361.5 KB/sec ) This is a speedtest.net speed test result from a second ago: https://www.cableforum.co.uk/images/local/2012/11/5.png This is the internal VM speedtest result: Download Speed: 61144 kbps (7643 KB/sec transfer rate) Upload Speed: 2872 kbps (359 KB/sec transfer rate) Latency: 24 ms Thu Nov 29 2012 10:27:38 GMT+0000 (GMT Standard Time) So as you can see... no problems, just a really odd graph! :) |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
Quote:
Quote:
When he is back on Monday i'll give him a call and explain what you've discussed. Quote:
Quote:
----------- Now a question... Say this is an upstream issue and it relates to the cab (as the PT thought), is this something that is going to be fixed soonish once it's been brought to the attention of someone from VM, or is it likely to go on and on forever until enough people report a problem? I'm a bit of a battleaxe and I'm pretty sure that I'm the only person on my road who's actively trying to find out what the issue is so it's probably not high on their priority list right now :p: |
Re: Poor VM Connection, strange TBB quality monitor etc..
When I had discrepant stats some months ago, the PT arranged for the cabinet amplifier to be replaced. They are supposed to be "sloped" so as to provide correct downstream power for the frequency range (attenuation is greater per metre for higher frequencies). The upstream power requirement is set by the remote CMTS based on what it needs to set in order to make sense of the data received. In dire circumstances, power rises to the maximum (58 dBmv) and the TBB would then show considerable packet loss. The upstream impairment can be anywhere between you and the first active node (the optical node). Most non-interference upstream impairments in the bit between the home and the cabinet have downstream consequences to (like low power and sometimes poor SNR). You don't have that. So it's likely to be between your tap point and the optical node. But, as I've said before, your neighbours would have that problem too.
You should, if you can, research your neighbours' experience. The fact that you have a PT's attention should be siufficient to get this cleared up. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
As for the graphs, I've never seen anything like it. Looks more like a problem at the CMTS end - either channelization or routing. You don't get those giant and sudden jumps in the green part of the graph from bad signal by any means... |
Re: Poor VM Connection, strange TBB quality monitor etc..
Yeah - I suppose that distinction is valid.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I'm not working from home today so I can't measure just how good my connection is, but...
[img]Download Failed (1)[/img] It looks to have stabalised in terms of where the blue bit stops, although I'm still concerned. I'm debating emailing the director of transmission operations again, whos been dealing with my issues since September, but because i'm having no issues that show up on a speed-test, I don't know what exactly to tell him, or how to get VM to sort it out! qasdfdsaq - what's the CMTS end?? |
Re: Poor VM Connection, strange TBB quality monitor etc..
The CMTS end is the VM end of the operatio. It's the massive server that puts out to and receives from several thoudand broadband users as well as sending out the TV stuff.
The graph you've posted can now be classified as BAD. You should take advantage of your handle on the TOD. When the average goes up like that then somethings spooking in the circuit. I would now expect you to see an effect on performance. |
Re: Poor VM Connection, strange TBB quality monitor etc..
I've dropped him an email. He's usually really good at responding within a few hours so I'll let you know what he comes back with.
Sorry for all the questions I keep asking. I like to have a good idea of what's going on before I fire off emails. If I have a vague idea of what I'm talking about they might take notice, rather than just saying "my graph looks bad". Ha. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Do a proper ping test - ping -n 100 www.bbc.co.uk or something like that. I'd like to see if the graph is actually representative of most paths or just TBB's network
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Pinging www.bbc.net.uk [212.58.246.90] with 32 bytes of data:
Reply from 212.58.246.90: bytes=32 time=28ms TTL=53 Reply from 212.58.246.90: bytes=32 time=29ms TTL=53 Reply from 212.58.246.90: bytes=32 time=33ms TTL=53 Reply from 212.58.246.90: bytes=32 time=42ms TTL=53 Reply from 212.58.246.90: bytes=32 time=61ms TTL=53 Reply from 212.58.246.90: bytes=32 time=28ms TTL=53 Reply from 212.58.246.90: bytes=32 time=26ms TTL=53 Reply from 212.58.246.90: bytes=32 time=22ms TTL=53 Reply from 212.58.246.90: bytes=32 time=51ms TTL=53 Reply from 212.58.246.90: bytes=32 time=24ms TTL=53 Reply from 212.58.246.90: bytes=32 time=24ms TTL=53 Reply from 212.58.246.90: bytes=32 time=193ms TTL=53 Reply from 212.58.246.90: bytes=32 time=562ms TTL=53 Reply from 212.58.246.90: bytes=32 time=155ms TTL=53 Reply from 212.58.246.90: bytes=32 time=280ms TTL=53 Reply from 212.58.246.90: bytes=32 time=385ms TTL=53 Reply from 212.58.246.90: bytes=32 time=562ms TTL=53 Reply from 212.58.246.90: bytes=32 time=110ms TTL=53 Reply from 212.58.246.90: bytes=32 time=132ms TTL=53 Reply from 212.58.246.90: bytes=32 time=24ms TTL=53 Reply from 212.58.246.90: bytes=32 time=102ms TTL=53 Reply from 212.58.246.90: bytes=32 time=25ms TTL=53 Reply from 212.58.246.90: bytes=32 time=114ms TTL=53 Reply from 212.58.246.90: bytes=32 time=29ms TTL=53 Reply from 212.58.246.90: bytes=32 time=138ms TTL=53 Reply from 212.58.246.90: bytes=32 time=22ms TTL=53 Reply from 212.58.246.90: bytes=32 time=98ms TTL=53 Reply from 212.58.246.90: bytes=32 time=51ms TTL=53 Reply from 212.58.246.90: bytes=32 time=97ms TTL=53 Reply from 212.58.246.90: bytes=32 time=25ms TTL=53 Reply from 212.58.246.90: bytes=32 time=96ms TTL=53 Reply from 212.58.246.90: bytes=32 time=27ms TTL=53 Reply from 212.58.246.90: bytes=32 time=77ms TTL=53 Reply from 212.58.246.90: bytes=32 time=38ms TTL=53 Reply from 212.58.246.90: bytes=32 time=61ms TTL=53 Reply from 212.58.246.90: bytes=32 time=60ms TTL=53 Reply from 212.58.246.90: bytes=32 time=60ms TTL=53 Reply from 212.58.246.90: bytes=32 time=28ms TTL=53 Reply from 212.58.246.90: bytes=32 time=646ms TTL=53 Reply from 212.58.246.90: bytes=32 time=292ms TTL=53 Reply from 212.58.246.90: bytes=32 time=314ms TTL=53 Reply from 212.58.246.90: bytes=32 time=499ms TTL=53 Reply from 212.58.246.90: bytes=32 time=161ms TTL=53 Reply from 212.58.246.90: bytes=32 time=321ms TTL=53 Reply from 212.58.246.90: bytes=32 time=83ms TTL=53 Reply from 212.58.246.90: bytes=32 time=34ms TTL=53 Reply from 212.58.246.90: bytes=32 time=85ms TTL=53 Reply from 212.58.246.90: bytes=32 time=28ms TTL=53 Reply from 212.58.246.90: bytes=32 time=193ms TTL=53 Reply from 212.58.246.90: bytes=32 time=41ms TTL=53 Reply from 212.58.246.90: bytes=32 time=122ms TTL=53 Reply from 212.58.246.90: bytes=32 time=26ms TTL=53 Reply from 212.58.246.90: bytes=32 time=64ms TTL=53 Reply from 212.58.246.90: bytes=32 time=51ms TTL=53 Reply from 212.58.246.90: bytes=32 time=83ms TTL=53 Reply from 212.58.246.90: bytes=32 time=37ms TTL=53 Reply from 212.58.246.90: bytes=32 time=156ms TTL=53 Reply from 212.58.246.90: bytes=32 time=29ms TTL=53 Reply from 212.58.246.90: bytes=32 time=96ms TTL=53 Reply from 212.58.246.90: bytes=32 time=32ms TTL=53 Reply from 212.58.246.90: bytes=32 time=94ms TTL=53 Reply from 212.58.246.90: bytes=32 time=46ms TTL=53 Reply from 212.58.246.90: bytes=32 time=63ms TTL=53 Reply from 212.58.246.90: bytes=32 time=24ms TTL=53 Reply from 212.58.246.90: bytes=32 time=907ms TTL=53 Reply from 212.58.246.90: bytes=32 time=179ms TTL=53 Reply from 212.58.246.90: bytes=32 time=245ms TTL=53 Reply from 212.58.246.90: bytes=32 time=348ms TTL=53 Reply from 212.58.246.90: bytes=32 time=58ms TTL=53 Reply from 212.58.246.90: bytes=32 time=285ms TTL=53 Reply from 212.58.246.90: bytes=32 time=432ms TTL=53 Reply from 212.58.246.90: bytes=32 time=28ms TTL=53 Reply from 212.58.246.90: bytes=32 time=57ms TTL=53 Reply from 212.58.246.90: bytes=32 time=25ms TTL=53 Reply from 212.58.246.90: bytes=32 time=58ms TTL=53 Reply from 212.58.246.90: bytes=32 time=30ms TTL=53 Reply from 212.58.246.90: bytes=32 time=97ms TTL=53 Reply from 212.58.246.90: bytes=32 time=23ms TTL=53 Reply from 212.58.246.90: bytes=32 time=52ms TTL=53 Reply from 212.58.246.90: bytes=32 time=23ms TTL=53 Reply from 212.58.246.90: bytes=32 time=55ms TTL=53 Reply from 212.58.246.90: bytes=32 time=25ms TTL=53 Reply from 212.58.246.90: bytes=32 time=60ms TTL=53 Reply from 212.58.246.90: bytes=32 time=23ms TTL=53 Reply from 212.58.246.90: bytes=32 time=71ms TTL=53 Reply from 212.58.246.90: bytes=32 time=26ms TTL=53 Reply from 212.58.246.90: bytes=32 time=55ms TTL=53 Reply from 212.58.246.90: bytes=32 time=37ms TTL=53 Reply from 212.58.246.90: bytes=32 time=56ms TTL=53 Reply from 212.58.246.90: bytes=32 time=22ms TTL=53 Reply from 212.58.246.90: bytes=32 time=84ms TTL=53 Reply from 212.58.246.90: bytes=32 time=165ms TTL=53 Reply from 212.58.246.90: bytes=32 time=334ms TTL=53 Reply from 212.58.246.90: bytes=32 time=532ms TTL=53 Reply from 212.58.246.90: bytes=32 time=195ms TTL=53 Reply from 212.58.246.90: bytes=32 time=34ms TTL=53 Reply from 212.58.246.90: bytes=32 time=233ms TTL=53 Reply from 212.58.246.90: bytes=32 time=407ms TTL=53 Reply from 212.58.246.90: bytes=32 time=59ms TTL=53 Reply from 212.58.246.90: bytes=32 time=22ms TTL=53 Ping statistics for 212.58.246.90: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 907ms, Average = 128ms ---------- Post added at 22:15 ---------- Previous post was at 22:15 ---------- I did type in bbc.co.uk.... Not sure why it came up with .net.uk! |
Re: Poor VM Connection, strange TBB quality monitor etc..
.net.uk is right dont worry about that. no loss which is good.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
That's fairly consistent with the TBB graph. Good call by Qasi to ask for that.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
My vm contact didn't actually reply, no out of office either... Shocking. I sent a text to the PT. he's back on Monday, hopefully he'll pop out to my house to see what the fuss is all about
---------- Post added at 22:53 ---------- Previous post was at 22:30 ---------- Question: should I present that ping test to the Director of transmission operations. |
Re: Poor VM Connection, strange TBB quality monitor etc..
I've had a reply :)
Long story short, he's got people looking at it. Can see the issues I'm having, no other customers on the same network as me is having these issues and so he's arranging a specialist to visit my house to take a look. What a carry on. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Jumping from 24ms to 900ms in one second, though no packet loss. Crazy.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I used to be angry... now I just think it's amusing, especially as my graphs/results seem to baffle everyone. As long as they keep whacking out the credits while it's not working and fix it at some point soon for good it's not bothering me.
I rarely use the internet at the moment for anything other than downloading mixes and the occasional browsing... its my other half that's taken the hit as he plays fifa, or rather he used to before this started happening a few month ago! I'll let you know what my guy comes back with! ---------- Post added at 13:18 ---------- Previous post was at 12:21 ---------- Ashleigh Please do not apologise, I am personally and proifessionally embarrassed that your service is still not as you need. I have been working this morning to arrange the necessary people for you The work we did last night has given us hopefully the answers towards rectifying your issues We will need to look at your home setup and settings also though It will be a combination of possibly Graham on site and a remote specialist who did a lot of analysis last night Will advise soonest on a date / time to suit you Regards Hugh. --- Looks like we're getting somewhere :) |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
Your upstream is so poor that: 1/ JDAST can't get in to perform the upload speed test 2/ You're getting packet loss. I get zero packet loss 100% of the time and so should you. It could be discards due to utilisation or it could be noise on the upstream (which is what I suspect). Your contact at VM really needs to look at the upstream, IMO. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Well... I got a text from the PT who said he would be coming through tomorrow evening.
Me and my other half have moved the router because we've put the christmas tree up... It was unplugged for a short while, and now it's back on the graph's looking, well... Normal?! http://www.thinkbroadband.com/ping/s...02-12-2012.png No doubt it will rise again, but at the minute, I'm having no issues. Just done another ping test too. Now I'm worried that they will come out and say everythings fine. Something must not be if it's causing issues like I've had all weekend. Pinging www.bbc.net.uk [212.58.244.69] with 32 bytes of data: Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=45ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=41ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=30ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=19ms TTL=53 Reply from 212.58.244.69: bytes=32 time=28ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=29ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=38ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=29ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=27ms TTL=53 Reply from 212.58.244.69: bytes=32 time=45ms TTL=53 Reply from 212.58.244.69: bytes=32 time=36ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=25ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=31ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=29ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=28ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=34ms TTL=53 Reply from 212.58.244.69: bytes=32 time=25ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=30ms TTL=53 Reply from 212.58.244.69: bytes=32 time=42ms TTL=53 Reply from 212.58.244.69: bytes=32 time=31ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=40ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=26ms TTL=53 Reply from 212.58.244.69: bytes=32 time=35ms TTL=53 Reply from 212.58.244.69: bytes=32 time=37ms TTL=53 Reply from 212.58.244.69: bytes=32 time=33ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=31ms TTL=53 Reply from 212.58.244.69: bytes=32 time=29ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=60ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=24ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=27ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=44ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=31ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=53ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=28ms TTL=53 Reply from 212.58.244.69: bytes=32 time=20ms TTL=53 Reply from 212.58.244.69: bytes=32 time=22ms TTL=53 Reply from 212.58.244.69: bytes=32 time=21ms TTL=53 Reply from 212.58.244.69: bytes=32 time=57ms TTL=53 Reply from 212.58.244.69: bytes=32 time=23ms TTL=53 Ping statistics for 212.58.244.69: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 60ms, Average = 26ms |
Re: Poor VM Connection, strange TBB quality monitor etc..
:LOL: all that and all was needed was a simple reboot for a better upstream channel :LOL: fail.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I'm still worried that there's an underlying issue that needs to be addressed though, or I'm going to keep having the same issue again in a couple of days.
It's always fine after a reset, then after 24 hours it starts to creep up again, see the last reset last week: http://www.thinkbroadband.com/ping/s...26-11-2012.png |
Re: Poor VM Connection, strange TBB quality monitor etc..
Although an acid test might be to move the thing back to where it was, if there is something else wrong, it'll happen again.
If it doesn't happen again, then if it wasn't something resolved externally, it would likely have been noise ingress internally. You're there and I'm not so I can't picture what might have been near the modem in the original location. So what could that have been? (electrical) |
Re: Poor VM Connection, strange TBB quality monitor etc..
I can take a photo of its location if that helps?
It was moved from its original location about 2 weeks ago, which could have caused some electrical interference now you mention this. Basically, in that area is a laptop, two CDJs, a mixer, telephone (not a cordless), I can't think of anything else that is electrical that's plugged in in that location though. It's only around 4ft from its old location though. Is that enough distance to cause issues? I feel so stupid now it's all working correctly, like ive caused a fuss over nothing. Ooops! :) |
Re: Poor VM Connection, strange TBB quality monitor etc..
Analogue telephone? Nearby telephone jack with the orange & white wires connected?
Noise ingress comes from fridges, analogue devices etc. Basiclly RF that gets into the upstream signal. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Yes it's an analogue telephone.
Hmm... I guess only time will tell with its current location if the telephone was the issue. I'll move it back in a week to see if it interferes again. |
Re: Poor VM Connection, strange TBB quality monitor etc..
speakers?
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Nope, no speakers thenry. Unless laptop speakers would cause the issues too?
|
Re: Poor VM Connection, strange TBB quality monitor etc..
yes rip them out lol only joking. whos the DJ?
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Me... I'm a super star DJ ;-)
My mate moved back home and needed somewhere to keep his CDJs etc. We've got them here but they've never been used. In fact, I don't even think they could be causing the issues because they weren't switched on! |
Re: Poor VM Connection, strange TBB quality monitor etc..
switch them on
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I can't. We have no spare plugs for them anymore... The Christmas lights are taking up the spare sockets :)
|
Re: Poor VM Connection, strange TBB quality monitor etc..
you better get a gang extension cable for the Christmas party
|
Re: Poor VM Connection, strange TBB quality monitor etc..
The Xmas lights switching on and off ........
|
Re: Poor VM Connection, strange TBB quality monitor etc..
there needed for the party
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I'm confused :'( haha.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
your having a party and we're coming.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Oh really? I love a good excuse for a party! My house isn't too big mind... How many of yous are there?!
|
Re: Poor VM Connection, strange TBB quality monitor etc..
all CF members: 85,606.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
If it's always fine after a restart and gradually gets worse then it's almost certainly a fault with the Superhub.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Possibly! Our Superhub was changed over a few weeks back though.
I'll see what the PT says when he comes over tonight. Graph's still looking stable, apart from the weird packet loss this morning: [img]Download Failed (1)[/img] |
Re: Poor VM Connection, strange TBB quality monitor etc..
Packet loss usually/often means noise on the upstream
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Oh I do love my connection :)
It better be alright tonight though, I've got an online tutorial at 8pm for Uni, could be interesting if the PT is still messing. I still feel like it was all my fault about the location of the SH and that I caused the issue... I'm hoping its not like, last thing I want is to have wasted a director's time :angel: |
Re: Poor VM Connection, strange TBB quality monitor etc..
Right... The PT has been round and has been talking on the phone to his national specialist. Aparently he's come into work today after being off for 10 days to hundereds of emails from a few directors/senior people relating to my VM connection... Oops!
He's adamant there's something in my house that's causing the bizarre connection/upstream issue... But he doesn't think it's the phone as we all thought. It's currently working really well... In fact its the best it's been for months! We've decided to give it a couple of days, if there's no issues with the connection, we're moving the superhub back to where it was when we had issues. This should give us a good idea of if its indoors. If it IS something indoors. He's having one of his other engineers bring an RF tester to hopefully find the source of the weird RF leak. So... It's now just a waiting game :) |
Re: Poor VM Connection, strange TBB quality monitor etc..
[img]Download Failed (1)[/img]
Possibly panicking over nothing here like... But that rising yellow bit is looking suspiciously like it did before my upstream had a mental breakdown :) |
Re: Poor VM Connection, strange TBB quality monitor etc..
A lot of people got that blip last night (including me). It's likely yo be an overload on one or more of VM's peering pints (you can Google that term).
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I think the OP means 6am onwards Seph
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Gotch, TH.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Yes I meant the 6am onwards part :)
Comparing it against the 27th November... (below) (same time, 6am onwards) http://www.thinkbroadband.com/ping/s...27-11-2012.png |
Re: Poor VM Connection, strange TBB quality monitor etc..
Sorry if I keep updating this! it might come in handy if anyone else finds they have bizarre graphs like me :)
Graham, the principal technician phoned me just now, he wants to pop round as the network specialist just phoned him and they can see from their end that it's going crazy again! I'd love to know what's causing this!! |
Re: Poor VM Connection, strange TBB quality monitor etc..
That's what we're here for! Keep posting and above all, write the answers down!!
|
Re: Poor VM Connection, strange TBB quality monitor etc..
OK... Nothing major to report. PT came round, talked on the phone to the specialist a bit, added a second SH to run along side to test (i've set up a TBB graph on this one too to compare)... Now, he didn't do anything specifically to my SH... But it's just gone back to normal on the graph (can see slight dip right at the very end):
http://www.thinkbroadband.com/ping/s...04-12-2012.png Very odd indeed... |
Re: Poor VM Connection, strange TBB quality monitor etc..
Me too
|
Re: Poor VM Connection, strange TBB quality monitor etc..
So havve you got 2 SHs running (i.e. he split your line and connected to an engineering circuit)?
|
Re: Poor VM Connection, strange TBB quality monitor etc..
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
Spoiler:
He said he'd be back tomorrow once it's had 24 hours running both SH's together to see if one is faulty and one is OK... or if both are showing weirdness etc. |
Re: Poor VM Connection, strange TBB quality monitor etc..
on the 2nd you powered down and up which settled the connection, may be new upstream, may be SH glitch. it then started showing signs of going back to how it was today the 4th. just saying a 24hr test may not be long enough.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
So - yoou've got 2 SHs running - one with your kit on it. What's on the other SH? His or your PC?
I noticed 7.3 dB attenuation from the splitter. So your modem stats would be interesting. If it's your kit on the 2nd SH, TBB and stats would also be interesting. Otherwise what data is being collected over the other SH? |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
It'll probably have the same loss on the upstream too. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Ah. Well compared to the previous 3-way splitter he'll only have an additional ~3.2 dB attenuation, not the full 7.3
|
Re: Poor VM Connection, strange TBB quality monitor etc..
I'm not at home now until Thursday afternoon, by then the second SH will have probably been taken away. So I won't be able to post any stats I'm afraid, my boyfriend probably won't know where to look to show me them to post to you guys.
Both connections are looking pretty stable at the minute actually...so I'm still baffled as to what the problem is! Mine: http://www.thinkbroadband.com/ping/s...05-12-2012.png Second: http://www.thinkbroadband.com/ping/s...05-12-2012.png |
Re: Poor VM Connection, strange TBB quality monitor etc..
Can you post the stats for both please? Are they both in the ame SH mode?
It would be interesting to see if you're both in the same frwquency range up/down. |
Re: Poor VM Connection, strange TBB quality monitor etc..
I can't post stats... I've not got remote access to the SH I don't think. Unless someone can explain how?
I'm on a train though so if I CAN access it remotely, it might be difficult. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Nah - it can wait. But you can see why it might be interestting. So far, the TBBs correspond.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
interesting, good that you have a tech who is working hard to fix, I am very curious what the issue is if its found out.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Right gents... These are the stats for the SH's (PT hasn't been to take it away yet)
First are my own SH's stats: https://www.cableforum.co.uk/images/...2012/12/55.png https://www.cableforum.co.uk/images/...2012/12/56.png Now for the test SH stats: https://www.cableforum.co.uk/images/...2012/12/57.png https://www.cableforum.co.uk/images/...2012/12/58.png Power levels are a bit high because of the 4-way splitter, but they are stable... (My SH top, Test SH bottom) http://www.thinkbroadband.com/ping/s...06-12-2012.png [img]Download Failed (1)[/img] |
Re: Poor VM Connection, strange TBB quality monitor etc..
In a well performing environment, the PT would expect to see those results. They are mutually consistent.
I noticed that the upstream power has fallen by 4 dBmv (downstream has risen as expected). Maybe they've solved the original upstream impairment. If the problem returns, note the upstream power. I keep regular records of my power levels. |
Re: Poor VM Connection, strange TBB quality monitor etc..
I will keep a record Seph :) Anything to help figure out what the issue was/is.
Graham (PT) phoned last night and said that he would be coming round tonight to remove the test SuperHub and leave it to see what happens when it's all back to my normal setup. I can't wait mind, I'm sick of all the cables, the area where the superhubs are looks like spaghetti junction!! |
Re: Poor VM Connection, strange TBB quality monitor etc..
BTW, I noted that both SHs share all the same channels in your segment.
But I noticed this: You have SEVEN downstream channels. When you first posted, you had SIX. He has SIX. Ask him to find out what's going on, and to explain the drop in Upstream power. He might not be able to do thatyon the spot. But worth a serious question. |
Re: Poor VM Connection, strange TBB quality monitor etc..
Mark Wilkin has posted on the VM forums today:
Quote:
Probably coincidence. Would be typical for VM to find a major core routing problem and fix it 1 week before all my services are cut. |
Re: Poor VM Connection, strange TBB quality monitor etc..
^ fail. wrong thread. ^
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
He's swapped my old SH for a new one as he thinks that's what's been causing the issues. he's left the test SH in for the time being, and is either taking this out tomorrow, or leaving it in over the weekend to monitor it. But I'm hopeful that the issue has been sorted, although I'm still not sure what it ACTUALLY was! I'll ask him tomorrow if he found out the answer to the number of downstream channels, or Monday, depending on when he comes to take away the test SH. This new SH only has 6 channels: Locked 32 323000000 Hz QAM256 5.7 dBmV 39.9 dB 169 0 Locked 27 283000000 Hz QAM256 8.1 dBmV 42.2 dB 205 0 Locked 28 291000000 Hz QAM256 8.1 dBmV 42.1 dB 216 0 Locked 29 299000000 Hz QAM256 7.5 dBmV 41.5 dB 257 0 Locked 30 307000000 Hz QAM256 6.5 dBmV 41.3 dB 271 0 Locked 31 315000000 Hz QAM256 6.3 dBmV 40.4 dB 155 0 |
Re: Poor VM Connection, strange TBB quality monitor etc..
If the DS power is now +8 after an extra 3-4dB attenuation from the new splitter does that mean they were +11-12 before? That's way out of optimal range, and enough to stop some crappier modems working entirely.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
What Qasi says.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Back again!
It's a good job the PT did leave the test hub in the house... At the moment, we currently have nothing connected to the test hub, everything is connected to OUR superhub, which was brand new as of Thursday, but the yellow bit has started to rise again! So it's not the superhub... Could it possibly be something that's connected to the superhub that's causing this? My laptop has been on all night wirelessly connected to my Superhub, but that's it. Curious why it always happens at 6am though :-/ TEST HUB [img]Download Failed (1)[/img] MY HUB [img]Download Failed (1)[/img] |
Re: Poor VM Connection, strange TBB quality monitor etc..
Now - that's important. Ae both hubs still on the same channels as before (Modem stats)?
Are thry both plugged into the same mains block? Are they both more or less in the same place? |
Re: Poor VM Connection, strange TBB quality monitor etc..
Are they both plugged into the same mains block - yes
Are they both more or less in the same place - yes, haven't even been over in that direction, nor has anyone else. Are they both on the same channels as before... Lets have a look! ---------- Post added at 15:15 ---------- Previous post was at 15:09 ---------- Test SH downstream: Locked 30 307000000 Hz QAM256 5.4 dBmV 40.9 dB Locked 27 283000000 Hz QAM256 7.2 dBmV 42.5 dB Locked 28 291000000 Hz QAM256 7.0 dBmV 42.2 dB Locked 29 299000000 Hz QAM256 6.4 dBmV 41.9 dB Locked 31 315000000 Hz QAM256 5.7 dBmV 40.8 dB Locked 32 323000000 Hz QAM256 5.0 dBmV 39.9 dB Upstream: Locked 3 27400000 Hz ATDMA 47.3 dBmV 16QAM 6400000 20480 Kbits/sec The new (own) superhub is on the same channels as it was when I last posted... Downstream Locked 32 323000000 Hz QAM256 5.6 dBmV 39.9 dB Locked 27 283000000 Hz QAM256 7.9 dBmV 42.4 dB Locked 28 291000000 Hz QAM256 7.8 dBmV 42.2 dB Locked 29 299000000 Hz QAM256 7.3 dBmV 41.6 dB Locked 30 307000000 Hz QAM256 6.5 dBmV 41.4 dB Locked 31 315000000 Hz QAM256 6.3 dBmV 40.9 dB upstream... Locked 2 35800000 Hz ATDMA 47.3 dBmV 16QAM 6400000 20480 Kbits/sec ---------- Post added at 15:25 ---------- Previous post was at 15:15 ---------- P.S. - I hope this is giving everyone reading this as much amusement as it is me :-D It's like my little mini project now, trying to get my internet back to how it was before September! |
Re: Poor VM Connection, strange TBB quality monitor etc..
What time did you switch what on that is connected to own SH?
What's attached to the VM SH and when is that switched on/off? |
Re: Poor VM Connection, strange TBB quality monitor etc..
Quote:
Xbox (wired)- was on last night for 3 hours, off until 2.45pm, on for 45 mins 2x laptops (1x wired and 1x wireless) - Wired laptop was on standby all night, turned on around 12pm. Wireless laptop on from around 6pm, on all night and still on now, not running anything overnight (that I'm aware of :erm:) Network hard drive - on all the time, never been switched off but not used within this time I don't think. 2x phones (wireless) - On constantly. Not used from 1am - 12pm 1x Wireless iPad - not used hardly at all for a couple of days but on. Nothing is connected to the test superhub (it's not been turned off at all since thursday), except for my laptop now (wireless) in case it's my laptop that's causing the issues!:shocked: |
Re: Poor VM Connection, strange TBB quality monitor etc..
With my engineering sort of hat on, I'd look at the effect of the difference in what's connected.It's just before 08:00 that things diverge. If you switched them all off right for two hours (or rather took them off the network) now except for one laptop you're using, that would eleminate unknown traffic from those devices. If that proves right (which it prolly won't) we can take a look at the devices.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
My parent's came round, so I've only just seen this.
I'm going to remove everything connected to the superhub in a second, and turn my laptop off so it's not connected by wireless. The only thing then will be mine and my other half's phones that will be connected to it... I'll see how it looks in the morning then. it's still going wild :) http://www.thinkbroadband.com/ping/s...08-12-2012.png [img]Download Failed (1)[/img] |
Re: Poor VM Connection, strange TBB quality monitor etc..
Nah - nothing to be connected. You can't eleiminate the phones and background apps if you don't tuen wi-fi off on them.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
Fair point. I'll make sure we turn WiFi off both and see how things look in the morning!
How sad is it that I'm kind of excited to see what results I get?! ---------- Post added at 23:41 ---------- Previous post was at 23:40 ---------- Wait!!! Look at the graph. It's already changed!!! ---------- Post added at 23:44 ---------- Previous post was at 23:41 ---------- I've plugged the network drive back in... seeing if that's the culprit |
Re: Poor VM Connection, strange TBB quality monitor etc..
what was connected?
|
Re: Poor VM Connection, strange TBB quality monitor etc..
The Xbox which wasn't turned on.
Other halfs laptop which was on. Network drive which was on. I unplugged them all, the graph sorted itself out, I've just plugged the network drive back in and that's it to see if that's the culprit. |
Re: Poor VM Connection, strange TBB quality monitor etc..
looks like it is. torrents? virus scan it with malwarebytes, kaspersky or any other decent scanner.
|
Re: Poor VM Connection, strange TBB quality monitor etc..
We don't download from torrents! We probably download about 3x tv shows per week and we're pretty sure we don't have any viruses. I don't on my laptop anyway.
---------- Post added at 23:58 ---------- Previous post was at 23:55 ---------- Looks like plugging the network drive back in has caused it to go crazy again... why would it do this? Is this common for a network drive? Does it just not agree with the superhub? Confused... |
Re: Poor VM Connection, strange TBB quality monitor etc..
which external HDD have you got, make and model?
give it a virus scan. |
All times are GMT +1. The time now is 20:09. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum