Was anyone aware if you put in the http://192.168.100.1:8080 for Arris SB8200 enter admin/password the modem has spectrum analyzer. Sorry if this is already posted or old information
↧
SB8200
↧
SB8200 quit working.
Bought it brand new in February. Has been rock solid up until 2 days ago then it quit. All of the lights are on, mediacom can see it on their end but it wont respond to any of their reprovisioning commands.
Had a tech come out this morning tested his modem and an older 6121 i had. Both worked fine. I called arris and they had me perform a factory reset after which they had me call mediacom and have them reprovisioning it. But no luck. Any ideas? I guess its warranty replacement time.
↧
↧
SB6190 High Corrected
Does anyone see issues with my stats? Seems to always have issues on channel 17 with corrected numbers in the millions. How can I track this down and optimize or fix the error?
↧
Arris SB6190 32x8 cable modem
For those curious, this is the product page for the SB6190. It's a 32x8 DOCSIS 3.0 modem. http://www.surfboard.com/products/sb6190-surfboard-cable-modem/
And here is the support page http://arris.force.com/consumers/ConsumerProductDetail?p=a0ha000000REMs8AAH&c=SURFboard%20Modems%20and%20Gateways which has the spec sheet and user guide and stuff.
--
I'm always up for a good chat and helping with tech problems.
↧
SB8200 Webpage problems
Hello All,
I just got my SB8200 today and it is working great on mediacom. They are coming out in a week to setup my 1gbit connection but right now I have their 200down and 30up connection which I am getting 270down and 50up. My issue is, I am not able to view the SB8200 status page. I get a purple page that says 404 Not Found, File Not Found. I am going to 192.168.100.1 just like my old SB6190.
What might the issue be?
I will say this. The modem is fast. Like what I have seen others say, websites seem to load a lot faster for me. I didn't really feel like I had problems with my SB6190 maybe I was lucky from what I have seen.
↧
↧
SB8200 - Questions
Hi Everyone,
I recently ordered Comcast gig inet and they said I need a DOCSIS 3.1 modem.
I'm currently using the Arris Surfboard 6190. I believe they told me that this won't work.
I came across the SB8200 and had a couple questions. What's with two gig ports? Are these used as WAN or 1 LAN + 1 WAN?
I prefer to run the modem in bridged mode and I'm curious if that second port will prevent me from doing so.
Thanks
Lefty
↧
6183 mgmt web GUI unreachable
For past 2 months, my 6183 has been unreachable via the web GUI. Modem works fine otherwise. I occasionally can hit it for a short time immediately after a reboot until it syncs with the provider, but as soon as it syncs, Im back to it being unreachable.
I noticed this weekend it rebooted and for some oddity was reachable for about a day and a half, but now its back to not wanting to talk to me.
Provider if it makes a difference is legacy TWC now Spectrum.
↧
Arris SB6183 My test results
Hi All,
How is everyone doing? I am posting on here some of the basic tests I have done with my Modem Arris SB6183 connected directly to PC via Ethernet cable. I am hoping to learn what the tests mean or don't mean and I hope to educate myself at least with some of the more common knowledge when it comes to Modems, router, latency etc. I have attached ping tests, spectrum analysis, puma 6 test and I have also attached a picture of my channel downstream and upstream signal to noise ratio. Additionally I've attached a picture of my log as well. I am brand new to this community, if I break any rules or anything please let me know so that I may learn from it. I hope to hear what everyone or anyone has to say and thinks. I understand that most of these tests you know what they are but I've labeled them just in case when saving the pictures.
Thank You
Modem LOG:
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 05 16:53:59 2017 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:6c:bc:b9:a2:ad;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Clear Log
[Mod edit - CM-MAC addresses removed. Not a good idea to post them on in a public board.]
↧
Specifying downstream frequency on SB6183
I am noticing some correctable and uncorrectable errors on a small band showing up on three channels from 135 to 147 MHz. Because of this, I'm wanting to try to pick a different range to use. I see that the SB6183 has a place to change the downstream frequency on the configuration page, but it's grayed out for me. Does anyone know if this actually works or if I'm wasting my time here?
↧
↧
SB8200 issues after re-provisioning by Comcast. Losing connectivity
I am very frustrated.
The good:
Since this morning my cable modem now suddenly shows the blue downstream light indicating D3.1 is enabled (light was always green till today).
As of this morning I now also have 29 downstream channels (28 of them are QAM256 and 1 is labeled 'Other') instead of 16 channels last night.
My upstream power is also somehow better (no change on my end) and now well within spec.
The bad:
When the tech was here the other day, removing my amp (since they seem to have boosted power coming into the tap screwing up my downstream power), they had issues with my SB8200 modem and decided to re-provision it (this was a few days ago); they noticed it was not officially supported (correct me if I am wrong but it has been supported for months now after we all initially had to wait).
They entered the MAC ID and manually force provisioned it since it was not supported).
The worst part:
I am not sure what is causing it but I have lost internet connectivity twice already this morning and had to reboot my modem twice already today!!!
This started today (after seeing the blue light and 29 channels etc.)
I removed the router from the equation but the access issue persisted. Seems some signal is knocking out my internet.
The strange thing is that during the issues some sites appeared to work and it still said 'internet' on my connection in Windows and the cable modem lights remained on. (puzzling).
The other odd thing is that my IPv6 is not working ('No network access') on wifi, as opposed to 'internet'.
Any ideas?
Really frustrating as I am working remotely today and need my access.
Edited to add that my SB8200 has been running very hot (today not so much so, maybe since upstream signal levels are better and it has less work to do). Not sure that is a factor since it was already in spec, although close to the general consensus limit despite the higher limit tech gave me).
If I can't find a solution SOON, may go back to a CM1000, or try a new Motorola MB8600 (have not been keeping up on D3.1 modems but just found this new MB8600 model when searching - will research reviews) and see what happens.
↧
SB8200 Questionable Performance and Statistics
Hello, first time posting here. I've been following the SB8200 discussion on here for several months around when my previous modem decided to be bad. I got the SB8200 three months ago or so and it's been working, but I don't think mine is working as well as everyone else's. As I'm writing this, the PUMA 6 test is mostly green with two reds and one orange square, but I have seen it in the past where half or more of the squares were a mix of yellow, orange, and red.
What concerns me the most though is the signal readings. Right now it's locked on 24 channels, though I believe I've seen it lock on all 32 before. All of the locked channels have greater than 0 correctables and uncorrectables. I believe the 8 channels that are not locked had even more than the locked ones, going past 10k+. I installed the same modem in my office two weeks ago, and it has 0 correcables and unccorectables.
I'm in Phoenix, AZ and have the Premier package, which says it's up to 150d/10u, and the up is ok, but the down is 30-80 depending on the speed test. Not sure if it matters, but I figure I might as well put it out there if its indicative of something.
It is hardware version 4 and running firmware D31CM-PEREGRINE-1.0.1.0-GA-04-NOSH. I have an ASUS RT-AC66U running DDWRT behind it, if it matters.
I'm curious if anyone knows if this is how the modem should be operating or if there's something I should do to improve it? To be honest I'm not feeling the greatness of the SB8200 so far over my previous SB6183. Thank you in advance for any help or suggestions!
↧
DG2460A QoS help?
Hello, I have this dual band router (TOUCHSTONE® DG2460 CABLE GATEWAY) and I am trying to figure out how to set up the QoS to my computer. I am not able to find it in any of the pages in the admin page. please help. Thank you!
↧
SB6183 event log question
Is there a reason why the SB6183 event log overwrites an error?
EX: Mon Jul 24 22:40:19 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
I know I saw the same error listed in the event log on 7/22 or 7/23 (earlier dates too). That error is no where to be found now.
I did not "clear log."
↧
↧
SB6183 refurbs at Staples $30
http://www.staples.com/Arris-SURFboard-SB6183-Refurbished-Cable-Modem/product_2719381
↧
SB6183 High Operating Temperature
Yesterday I installed an SB6183 modem which is working fine but it's running 110F. Is this within norms? It's in an air conditioned room where temperature is set at 79F and a ceiling fan on medium speed.
Modem is ls located in an enclosure with two legs to help air movement.
↧
SB6183 vs. SB6121
I just signed up for cable service that promised up to 100 Mbps. I've read conflicting information about whether I will notice the difference between the two modems?
Thoughts?
Thanks.
↧
SB8200: High Downstream Power Levels
I had seen a post that Cox was moving to DOCSIS 3.1 in the Las Vegas area, so I put my SB8200 back on line. Yep. I've now got 3.1. But, my downstream power levels are all over the place. With my SB6183 (after Cox had done all kinds of maintenance on their lines) my downstream power levels had been (finally) stable around 5 dBmV (all the channels). With the SB8200, I'm seeing power levels that start at about 5 dBmV and go all the way up to almost 12 dBmV. I'm getting "Dynamic Range Window violation" warnings in the Event Log which I assume are because of those power levels. Cox had already changed all my splitters and the line to the tap, worked on the tap, itself, and, apparently, done some kind of repair at the node while I was on the SB6183. Should there be differences like this between the SB6183/SB8200 and DOCSIS 3.0/3.1? Should I assume the SB8200 is bad and try getting it repaired?
↧
↧
Cable modem speed dropped in half
I plugged a laptop into the cable modem directly. My speed dropped from 70+ to 32 about a week ago. No changes or anything added.
Specs:
Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.1-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Cable Modem status page doesn't say Failed on anything.
The Status page:
Downstream Bonding Channel Value
Channel ID 111
Frequency 717000000 Hz
Signal to Noise Ratio 38 dB
Downstream Modulation QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
2 dBmV
Upstream Bonding Channel Value
Channel ID 4
Frequency 36800000 Hz
Ranging Service ID 23
Symbol Rate 5.120 Msym/sec
Power Level 55 dBmV
Upstream Modulation [1] QPSK
[3] 16QAM
[2] 64QAM
Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 111
Total Unerrored Codewords 113694794
Total Correctable Codewords 0
Total Uncorrectable Codewords 1409
I don't know what any of the above means. :)
Can the cable modem go partially bad?
Any troubleshooting ideas?
The modem is getting old, I can upgrade to gig now through my provider but will need a docsis 3.1 modem.
Thanks!
↧
SB8200 Constant Reboots
Hi everyone,
New to this forum so bear with me here as I get familiar with posting. I have had the SB8200 since late May with Comcast residential in central NJ (Toms River area). Several times a day, it will completely drop the connection and reboot, usually taking several minutes to come back online. There seems to be no pattern to it. I've been reading up on the threads here about the device's problems, but the few people that are having severe issues and constant drops aren't following up or nobody is replying, so I figure I'd make this thread to try and get some help.
My signals levels look OK, but I am not sure about the uncorrectable errors. I remember reading that some are expected during a startup, but I am not sure how true that is. I was a bit concerned about upstream power, but apparently, that is still within their specs. Comcast has been here several times and basically replaced everything from the splitters in the house to the equipment on the pole across the street.
Utility power is being conditioned through a Dell Rackmount UPS running other networking and server gear just fine so the power is not dirty. Additionally, the power levels of the cable signal are steady and don't change much.
I've put screenshots of my signal level, event log, and external monitoring service as attachments. I'd appreciate any advice, I am really hoping someone has some insight before I go office space on it and just buy something else.
↧
Broadcom Chip Spectrum Analyzer
https://www.dslreports.com/forum/r31563033-Broadcom-Chip-Spectrum-Analyzer
↧