@DigTV99 wrote:
My internet just disconnected 5 minutes ago and the modem was flashing green. I'm now back online but I'm wondering why my modem stats still show this: System Uptime: 4 days 1h: 19m: 29s
Why doesn't it register the disconnection?
Think of the Ignite Gateway as a small computer. The System Uptime indicates how long it has been since the Gateway got power-cycled or rebooted... and also represents how long the error counts in the stats have been accumulating.
What you just saw was the Ignite Gateway losing its connection to the Rogers network. The modem will immediately try to reconnect, and the flashing green and amber status is the modem going through its registration process.
@DigTV99 wrote:
@-G-I forgot to mention that I was told the node in my neighbourhood was updated a few weeks ago. The upload upgrade was not done but improvements were made.
Okay... but that just begs to ask more questions, such as:
Why are you provisioned with only 4 upstream (DOCSIS 3.0) QAM channels and no OFDMA channel? (Is there some really old legacy gear installed in your neighbourhood that would make this channel configuration unstable or problematic? Is more maintenance work required to enable your area to be upgraded to support mid-split?)
Why are you getting so many uncorrectable errors? Is this problem isolated to your line? Are your neighbours affected as well? With a DAA / R-PHY node, the RF signal path to/from your modem is terminated at your node, not in the headend. If the errors are caused by noise ingress or other RF impairments, it should be localized and easily remediated.
Why is your modem losing registration so frequently? Is it due to serious issues with the cable plant in your area? Is it due to hardware/software stability issues with your new fibre node?
Did your current stability issues coincide with your node getting upgraded?
Yup, everything that @-G- said .......
I'm not as concerned about the uncorrectable codewords as their a small component of the overall codewords.
Looking at your signal stats, there's nothing to indicate an issue, and apparently the moderators have indicated that the OFDM channel stats are within acceptable parameters. As @-G- is asking, what the heck is going on, and that's being polite about this.
Ok, so, this is where it would be an idea to run a long term ping test to the CMTS. If you're going to do this, run it on your main pc, even it its connected via wifi. You might see occasional missed packets over wifi, which we won't be too concerned about, but, in the case of a complete disconnect, you'll see a series of timeouts until the modem reconnects. Using the Powershell approach, you will have timestamps to go along with the time outs. You can copy that timeout data, with timestamps and sent that to the moderators via message to @CommunityHelps. What the moderators will do with that data is a good question, but, looking at the CMTS logs for the disconnected times, should show if you're the only one with this problem or if there are other customers on your neighbourhood node who also have this problem.
You indicated that you have a Windows 7 pc that you could use. Don't do that. Windows 7 on the internet is a security hazard looking for someone to hack into it. If you're not using it at all, and there's nothing on the hard drive that you want to keep, consider loading Ubuntu onto it, which is kept up to date. Only caveat is that you have to ensure that you enable the firewall after the load. If you're curious about linux and its offshoots, loading Ubuntu is an easy first step for learning purposes.
Yup, thats what we're looking for. Now, its on the moderators or network engineering staff to look at the CMTS and neighbourhood node records to see what was going on at that time.
I've never seen a "PING: transmit failed. General failure". Interesting .....
Did the connection just drop, or were there any high time pings that occurred just before the drop? Just wondering if there's anything evident leading up to the drop?
It shouldn't drop at all. The question is, are you the only one seeing this or is it restricted to you and your neighbourbours or is it a wider problem? Someone will have to dig into the records to see just how many customers are affected, which includes Rogers and other TPIA customers.
I would keep that test running. Let it run for days if you're willing to do that. Every once in a while you can copy the text file using File Manager and paste it into the same directory, it will paste in as a "Copy of ....." or paste it into a different folder. You don't have to stop the test to copy the file. When that's parked somewhere, you can use Word (??) or Notepadd++ to peruse the file. It would be work searching thru the file, looking for overnight disconnects.
I'm getting a lot of packet loss & jitter when pinging CMTS but not when pinging 10.0.0.1. What does this indicate?
CMTS
10.0.01
-
6366 views
-
15 Likes
-
-
