![]() |
Painful Brighton !
|
Re: Painful Brighton !
noooooooooooooooooooo, I thought we went though this last year :doh:
|
Re: Painful Brighton !
Yes we did and it was ok but of late it has deteriorated again, why is this ?
https://www.cableforum.co.uk/images/local/2016/02/7.png |
Re: Painful Brighton !
have you had a look at your power levels etc?
|
Re: Painful Brighton !
Oů est-Horsemanl lorsque vous avez besoin de lui, mon General?
|
Re: Painful Brighton !
you are killing me dude, ich hasse Französisch. That being said, I haven't seen Horse in ages. If they did some relief work and capacity upgrades last year though I would assume they did enough to get rid of the problem altogether and that db's problem might be more symptomatic of a local fault. Either that or all the students are pounding the internet again, but I would have thought VM would have made a provision for that when they were planning the upgrade work as they can see how bad the utilisation was.
|
Re: Painful Brighton !
Ich hasse Es auch - und mein Deutsch ist besser als Französisch. Aber wenn Mann es braucht ...
For the OP's benefit, though, her's only shown us a TBB graph. The OP has said nothing about what was being done on his own connection at the time of the original snapshot. FGrom the live graph we can see iut's building up again. Also the modem stats will tell us whether or not he is on two upstream channels. |
Re: Painful Brighton !
Quote:
That said I can't offer much, but coincidentally I was randomly checking a few other IP's on my subnet and discovered these two examples of potential imbalance on Brig15 CMTS which I've been monitoring for last few weeks: Share Live Graph1 Share Live Graph2 Of course I don't know the nodes/post code or individual CM/Hub stats for these two radically different Brig15 comparisons but circumstantially considering the significant difference in minimum latency and "brick wall gaps" in one I suspect load balancing across linecards and/or backhaul core upstream port issues even? As stated unless it is a local issue then it would seem likely Networks are already monitoring/aware of that issue? I'd have to monitor the other 6-12 lines on my subnet responding to ICMP echo's to see how prevalent this is but without knowing their other specific details it's very speculative anyway. Our DB133 friend doesn't seem to have posted on VM H&S under his usual handle since March 2012 when he was on Brig1 legacy chassis so it would be useful if he checked what CMTS/uBR he's now on as well as the SHub stats (I'm assuming he did eventually upgrade to DOCSIS3)? Clearly he'd need to post on VM Forum or ring in anyway ultimately. Clearly the more "visibility" and the earlier, then the more likely he/we can attract similar (nil or otherwise) reports and engage Level2 accordingly with appropriate priority?. |
Re: Painful Brighton !
Quote:
No I haven't and I don't know how to, I've had a quick look on Google but as yet I haven't found out how to look at them. It looks complicated for the lay person. In any event kind regards https://www.cableforum.co.uk/images/local/2016/02/7.png Gave VM a ring went through the usual and its been rebooted/reset adjusted ! I am to call back in 24 hours if it has not been resolved. Very nice lady although I had to keep repeating that it does work but not very well at times. |
Re: Painful Brighton !
|
Re: Painful Brighton !
ya, I think their should be two tables, one for your upstream stats and one for downstream. Do a screen dump and post the whole lot in here.
|
Re: Painful Brighton !
Looks like a bit of an improvement at about 16:45, hard to say for sure if it's fixed though. Going to bet "no".
|
Re: Painful Brighton !
All seems to return to normal after a reboot and then will probably start to f up again after a while.
|
Re: Painful Brighton !
well spotted. Maybe the reboot caused him to lock onto different channels which have given the impression the fault has been resolved
|
Re: Painful Brighton !
aye, looks like the DilDoe is vibrating quite a lot
|
Re: Painful Brighton !
Quote:
Locked 56 322750000 Hz QAM256 2.8 dBmV 40.7 dB 45746 10 Locked 49 266750000 Hz QAM256 3.8 dBmV 43.2 dB 345 0 Locked 50 274750000 Hz QAM256 3.6 dBmV 42.5 dB 259 0 Locked 51 282750000 Hz QAM256 3.2 dBmV 42.0 dB 370 0 Locked 52 290750000 Hz QAM256 2.4 dBmV 41.5 dB 4383 0 Locked 53 298750000 Hz QAM256 3.9 dBmV 42.6 dB 495 0 Locked 54 306750000 Hz QAM256 3.7 dBmV 42.2 dB 284 0 Locked 55 314750000 Hz QAM256 3.5 dBmV 41.4 dB 1812 0 Upstream Channels Lock Status Channel ID Frequency Modulation Tx Power Mode Channel Bandwidth Symbol Rate Locked 4 45800000 Hz ATDMA 37.0 dBmV 16QAM 6400000 20480 Kbits/sec Locked 5 35800000 Hz ATDMA 37.0 dBmV 16QAM 6400000 20480 Kbits/sec Unlocked 0 0 Hz Unknown 0.0 dBmV Unknown Unknown 0 Kbits/sec Unlocked 0 0 Hz Unknown 0.0 dBmV Unknown Unknown 0 Kbits/sec Graph show improvement after my call. Regards https://www.cableforum.co.uk/images/local/2016/02/7.png |
Re: Painful Brighton !
They are pretty well spot on. Pity we didn't see them from before the improvement. It would have been interesting to see the channel changes. However, on the SH1 there is a tendency in certain cases (this is being investigated) for latency to creep up until the SH1 is rebooted. If you stay in touch, we'll see.
|
Re: Painful Brighton !
Quote:
|
Re: Painful Brighton !
IMPO, a reboot is necessary only if you see instability creeping in on the TBB graph. That said, the SH1 always benefits from an occasional hard reboot.
|
Re: Painful Brighton !
i can't remember the last time I rebooted either my vmng300 or my Linksys router. Goes to prove a nice point I always make when we recommend different routers to other forum users because I always say it is hassel free and just sits there in the background not causing any agro.
|
Re: Painful Brighton !
Same with my SH2/Airport Extreme. And just for the record, same with the SH1 in modem mode for the 18 months it was in use. Oh and also the VMNG300 before that with a Draytek router.
|
Re: Painful Brighton !
My VMNG300 needed rebooting 2-3x times a day sometimes, all boils down to the network conditions in your area.
|
Re: Painful Brighton !
Never had to reboot my Ambit 300 and so far I think I've rebooted my SH2 a grand total of about 5 times, mostly due to me switching cables around and knocking off the power.
I think qas has made a valid point about network conditions. |
Re: Painful Brighton !
I had a spell of bad connectivity with very low power levels (they swapped out the VMNG300 for a SH at the time). Anyway, I don't recall rebooting the VMNG300 during that 2 month period of circuit instability apart from the odd experiment or two. It would reset according to whatever network events were screwing the circuit up.
|
Re: Painful Brighton !
Quote:
|
Re: Painful Brighton !
by the way the graph looks ok now :)
should have posted a snapshot not live graph. |
Re: Painful Brighton !
Quote:
|
Re: Painful Brighton !
Quote:
|
Re: Painful Brighton !
http://www.thinkbroadband.com/ping/s...26-10-2013.png
Thanks for the tip. Off Topic I know !! I use an interface for my music it all works ok but for some crackles every so often. I have tried turning off the internet Wi fi and most of it stops say 98% but not all. Any info will be most appreciated. I don't like to disconnect the Wi-Fi because I have to restart to pick a signal up again. I don't understand why there are several wireless connections to choose from including my one when I am connected but when I disconnect (to stop the crackles as mentioned above ) and try to reconnect there are no signals to pick up ! So I restart and I am reconnected with several to choose from. Any input will be most appreciated; Kind regards to all. |
Re: Painful Brighton !
Sounds like a driver or resource conflict, though can't be more specific without knowing the details of the computer.
|
Re: Painful Brighton !
Quote:
Read this for more info on why it happens and to download LatencyMon: http://www.resplendence.com/latencymon Running DPC Latency Checker may help to see when there are problems even though you don't hear any crackles all the time: http://www.thesycon.de/deu/latency_check.shtml If you have the same problem, to fix you could disable the LAN driver in Device Manager and leave the Wifi driver on instead to avoid the clash, or replace the wifi card with a different model/brand. I had an Atheros before and upgraded to an Intel Centrino card. Using DPC Latency Checker can help you identify if you're still having the issue after you've disabled a driver. Test with headphones to see if it's an audio problem that only occurs with internal speakers or with headphones too. If it's just internal speakers it could well be that your computer has one of Intel's dodgy transistors controlling the headphone jack. So external speakers would be a way around it. |
All times are GMT +1. The time now is 22:28. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum