07-06-2021 08:40 PM - last edited on 07-06-2021 09:45 PM by RogersZia
I switched over to Ignite many months ago and have the Rogers 500u plan. I have my main computers (2) connected by ethernet and other devices (laptops etc) via WiFi including many smart home bulbs and hubs etc. When I set up the system I checked the WiFi signal strength all over my house and it was VERY strong, so much so that I removed my ASUS router and used the Ignite Modem in Gateway mode.
The system has been functioning very well for months and months.
Until a few weeks ago when we started noticing freeze-ups in my TV. in some recent incidents, the picture would freeze for a few seconds and that was followed by the TV going totally black for a few seconds (10-15 seconds) then all would resume. Alternately, the TV would just go black all of a sudden and then resume in 10-15 seconds (i.e. no picture freeze per se.
I started to wonder if it might actually be my TV (unlikely - it is high end and relatively new) but now we are seeing interruptions in Internet service as well. Zooms and other connections are also now failing for short times at intermittent intervals. The disruptions are getting more frequent and more annoying, and sooner or later it is going to crash some really important meeting and I can not abide that.
Not sure if I should be calling a tech person (I know how futile that can usually be) or if there is some fairly straightforward troubleshooting I can do on my own.
I am paying for a premium package that has worked very well, but it is now routinely failing me on too many occasions throughout the day. And it all started a few weeks ago, yet really there have been no changes at my end re: connections, equipment, setup etc.
Ideas?
***Edited Labels***
09-23-2021 01:25 AM
I was getting daily disconnections after Ignite was installed and the next tech that came fully disconnected all the unused jacks in my condo and checked the signal strength to the modem, then said the signal was too high and installed a 3dB attenuator on the modem. These are the current stats wth the attenuator connected.
Are these good levels or should they be between 36-40db for optimal performance?
IndexLock StatusFrequencySNRPower LevelModulation
Downstream | Channel Bonding Value | ||||||||||||||||||||||||||||||||
23 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
693 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350 MHz | 275600000 |
40.4 dB | 40.7 dB | 40.9 dB | 40.9 dB | 41.0 dB | 41.4 dB | 41.4 dB | 41.2 dB | 41.3 dB | 41.0 dB | 41.1 dB | 41.1 dB | 41.5 dB | 41.5 dB | 41.4 dB | 41.3 dB | 41.2 dB | 41.1 dB | 41.1 dB | 40.9 dB | 40.7 dB | 40.9 dB | 40.6 dB | 40.6 dB | 40.7 dB | 40.7 dB | 40.6 dB | 40.8 dB | 41.5 dB | 41.2 dB | 41.2 dB | 41.1 dB | 40.5 dB | NA |
4.8 dBmV | 0.2 dBmV | 7.3 dBmV | 7.3 dBmV | 7.1 dBmV | 4.5 dBmV | 4.6 dBmV | 4.6 dBmV | 4.6 dBmV | 4.6 dBmV | 4.7 dBmV | 4.7 dBmV | 5.1 dBmV | 5.1 dBmV | 4.9 dBmV | 4.9 dBmV | 5.0 dBmV | 4.9 dBmV | 4.9 dBmV | 5.0 dBmV | 5.0 dBmV | 4.9 dBmV | 4.7 dBmV | 4.7 dBmV | 4.8 dBmV | 4.8 dBmV | 4.9 dBmV | 4.9 dBmV | 7.6 dBmV | 7.7 dBmV | 7.6 dBmV | 7.4 dBmV | 1.5 dBmV | NA |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM | OFDM |
Upstream | Channel Bonding Value | ||
1 | 2 | 3 | 4 |
Locked | Locked | Locked | Locked |
21 MHz | 25 MHz | 32 MHz | 38 MHz |
2560 | 5120 | 5120 | 5120 |
42.3 dBmV | 43.3 dBmV | 43.5 dBmV | 43.3 dBmV |
QAM | QAM | QAM | QAM |
TDMA_AND_ATDMA | ATDMA | ATDMA | ATDMA |
09-23-2021 01:46 AM - edited 09-23-2021 01:47 AM
@mascf1 Those signal levels are good, and disconnecting the unused coax outlets was also the right thing to do.
09-23-2021 09:40 AM
09-23-2021 10:57 AM - edited 09-23-2021 11:00 AM
@mascf1 wrote:
Sadly this hasn’t fixed the issue and the modem is still losing connection and rebooting itself. This has been happening every day this week and I’m fed up with Rogers!
You currently have strong (but not too strong) Downstream power levels and good SNR stats, and normal upstream power levels.
Are you currently using your own router, with Bridge Mode enabled on your Ignite gateway? (Totally fine if you are. In this this config, there are fewer things running on the Ignite gateway that could trigger a reboot.)
I would also plug the Ignite gateway directly into wall power, not into a power bar, to see of that improves stability. (Unless you have really noisy/unclean wall power, which could also cause all sorts of weird issues.)
Otherwise, I don't think that there is much more that you can do. Even with good signal levels to your modem, there are still things at the DOCSIS level that could trigger a DOCSIS WAN reset or cause the modem to reboot. Sure, the Ignite gateways can be twitchy, but in the 2+ years that I have been an Ignite TV customer, my XB6's Internet connection has always been solid.
09-30-2021 12:34 PM - last edited on 09-30-2021 02:06 PM by RogersMoin
My Ignite Internet connection has been unstable since Sunday. It has been dropping several times an hour. The Tech team has been out (Monday) once and verified there were no signal noise issues in the house. Modem Replaced on Monday with no change to the service drops. My tech appointment today was between 10 AM and noon and as of 12:30 they are a no show and no call. On hold with call in support now for 30 minutes. This is beyond frustrating. We were pushed from the Legacy internet service several months ago for this exact issue. Service dropping . Ignite has not solved the issues and in fact have made it worse as with no Internet No TV, at least before the TV and Internet were separate. Any ideas??
09-30-2021 01:50 PM - last edited on 09-30-2021 02:06 PM by RogersMoin
@mdallen Ignite Internet is the same as Rogers legacy Internet, just with a different modem. Switching to Ignite Internet will not make existing, long-term problems go away.
I don't know why your Internet service is constantly dropping. If you post your modem's signal levels and error stats (log into your Ignite gateway and go to Gateway > Connection > Rogers Network) we can confirm whether or not they are withing spec, but Rogers is also fully capable of confirming that as well, and more. If it is a signal-related issue, problems with DOCSIS channels dropping, or some interoperability issue between the modem and CMTS, only Rogers can troubleshoot and fix that.
You can also send a private message to @CommunityHelps and ask them for a second opinion. They are a great group of people and have helped many with getting the right teams within Rogers engaged to investigate and resolve complex issues.
09-30-2021 02:49 PM
What is the best way to copy the logs so you can see them?
09-30-2021 02:58 PM - edited 09-30-2021 02:58 PM
@mdallen wrote:
What is the best way to copy the logs so you can see them?
https://communityforums.rogers.com/t5/Community-Lounge/posting-data-from-modem-how/m-p/485734
09-30-2021 03:03 PM
Downstream | Channel Bonding Value | |||||||||||||||||||||||||||||||
17 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
657 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 693 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350000000 |
40.6 dB | 42.3 dB | 41.0 dB | 41.1 dB | 41.8 dB | 42.2 dB | 42.3 dB | 42.3 dB | 42.1 dB | 42.0 dB | 42.1 dB | 41.8 dB | 41.5 dB | 41.3 dB | 41.3 dB | 41.2 dB | 41.0 dB | 40.2 dB | 40.1 dB | 39.7 dB | 40.0 dB | 40.0 dB | 39.8 dB | 39.9 dB | 40.0 dB | 39.8 dB | 39.0 dB | 38.7 dB | 41.3 dB | 41.1 dB | 41.4 dB | 41.1 dB | 42.5 dB |
-5.2 dBmV | 0.5 dBmV | -4.0 dBmV | -3.8 dBmV | -2.6 dBmV | -2.5 dBmV | -2.3 dBmV | -2.0 dBmV | -2.3 dBmV | -2.6 dBmV | -2.7 dBmV | -2.9 dBmV | -3.7 dBmV | -3.9 dBmV | -4.0 dBmV | -4.0 dBmV | -4.5 dBmV | -5.9 dBmV | -5.9 dBmV | -6.1 dBmV | -6.2 dBmV | -6.2 dBmV | -6.3 dBmV | -6.3 dBmV | -6.2 dBmV | -6.4 dBmV | -7.2 dBmV | -7.5 dBmV | -3.3 dBmV | -3.7 dBmV | -3.5 dBmV | -3.7 dBmV | 1.0 dBmV |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM |
Upstream | Channel Bonding Value | |||
1 | 2 | 3 | 4 | 5 |
Locked | Locked | Locked | Locked | Locked |
21 MHz | 25 MHz | 32 MHz | 38 MHz | 4 MHz |
2560 | 5120 | 5120 | 5120 | 0 |
39.0 dBmV | 39.5 dBmV | 40.5 dBmV | 41.5 dBmV | 435000.0 dBmV |
QAM | QAM | QAM | QAM | OFDMA |
TDMA_AND_ATDMA | ATDMA | ATDMA | ATDMA | TDMA |
C |
09-30-2021 03:04 PM - edited 09-30-2021 03:06 PM
@mdallen can you copy and post the error stats as well.
09-30-2021 03:28 PM
@mdallen Your Downstream power levels are on the low side on some channels but they are still technically within the allowable range, at least as far as Rogers is concerned. If you are getting a ton of Uncorrectable Codewords errors, especially on the downstream OFDM channel, then that is not good, and Rogers would need to send a senior tech (and possibly a maintenance crew) to investigate further.
09-30-2021 03:37 PM
Like these:
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
662379428 | 833493859 | 833730474 | 833857604 | 833995217 | 834117533 | 834260584 | 834402900 | 834538134 | 834680382 | 834892840 | 834932988 | 835003081 | 835225590 | 835370635 | 835515842 | 835651924 | 835801230 | 835953327 | 836097759 | 837242415 | 837388733 | 837533881 | 837667560 | 837809703 | 837951466 | 838123031 | 838284296 | 838450369 | 870151419 | 870389289 | 870373815 | 662379428 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
445626122 | 53723 | 6590 | 6639 | 6132 | 12889 | 12408 | 11510 | 11132 | 10670 | 10416 | 9590 | 9390 | 8910 | 8450 | 8361 | 7987 | 8117 | 8292 | 8073 | 7993 | 8092 | 7942 | 8416 | 8141 | 8089 | 8773 | 8907 | 7409 | 9323 | 8594 | 8916 | 445626122 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
| 45620 | 2443 | 2120 | 2311 |
09-30-2021 03:40 PM
@mdallen Yeah, that's bad. Very bad. Your connection is definitely not healthy. I would definitely contact @CommunityHelps for assistance.
09-30-2021 03:54 PM
09-30-2021 03:55 PM
Thanks I will let them know. Will this help when the next tech arrives?
09-30-2021 04:07 PM - edited 09-30-2021 04:09 PM
@mdallen Further to what @Datalink said, it could be a noise issue. It could also be due to something as simple as a bad coax patch cable. It could also be a problem with the Rogers line going into your home. Regardless, if those error counts continue to increase, that's not good.
Before rebooting your Ignite gateway, I would also give Rogers an opportunity to troubleshoot and look at your modem's logs.
When you do reboot your gateway, I would power cycle it. If you have your gateway plugged into a power bar, when you unplug it, I would plug it back in directly into a wall outlet, and unplug that power bar completely. (If the power bar has gone bad, it could leak noise and cause all sorts of problems.
09-30-2021 04:59 PM
So the Tech just left. - There was a Noise filer on the Line at the Cable Box for the neighborhood. Tech felt that was not the correct place. When the filter was removed service level went too hi in the house so a filter was laced at the Modem. Fingers crossed. One other issue that came up was the techs are not updating their logs for all service calls as there was no entry for the work done here on Monday. Bizarre way to diagnose issues! For now the Uncorrectable Codewords are back to Zero from the large numbers that existed. I will keep an eye on that. Thanks for the insights. I may have learnt more about Rogers today than I really wanted but I guess we are on our own.