When my GN3ACSMR loses its internet connection it will regain the connection but the lan port "turns off". The light on the front of the modem and on the lan port goes off and stays off. I have tried all 4 ports and still encounter this issue. Is it a problem with the modem? Any ideas or suggestions. The only way to resolve is to power cycle the modem. Thank you.
Solved! Solved! Go to Solution.
We are actively working on resolving the issue where LAN ports get disabled intermittently and we have received a new firmware that corrects this issue. Although we are not ready yet for a large scale deployment, we have decided to launch a new program that enables Rogers Community Forum users to participate in the testing of this firmware and to provide us valuable feedback.
In order to participate in this trial, visit this thread.
Does the modem reboot on its own, which would be a sign that there is a problem with the cable signal levels? Can you log into the modem, navigate to the STATUS... DOCSIS WAN page, copy the downstream and upstream tables and paste them into a post? You can grab the text components of the tables and paste them in.
Here is the info:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||BandWidth|
|1||30596000||ATDMA - 64QAM||47.000||4||6400000|
|2||38596000||ATDMA - 64QAM||47.000||6||3200000|
|3||23700000||ATDMA - 64QAM||46.500||5||6400000|
Your downstream levels are ok, but the upstream are elevated above their normal 36 to 40 dBmV range. The limit is 51 dBmV, although Rogers uses 52 dBmV. At that point, the modem should lose a channel or two and run in degraded mode on one or two channels up. I would say that you probably have some sort of cable issue going on, with added intermittent issues. Do you have Rogers cable and Home Phone, and if so, do you see any issues with screen pixelating or audio dropouts.? I would call tech support and have them run a signal check on the modem. With the signal levels as high as they currently are, you might see a tech visit your home to check the external cabling. Is the cable underground or above ground running from a utility pole?
That behaviour isn't normal, but, we haven't seen that reported here before. Maybe the interrupts are not enough to cause the modem to reboot, but, just enough to cause a connection loss at the ethernet ports, which is very strange to say the least. You would think that in most cases, with most modems or routers, there would be a reconnect occur right away.
Rogers tech came out yesterday and replaced some ends on cables which dropped my upstream numbers to the 42 to 43 range, replaced the modem but it looks like the problem of dropped connections is still happening. Tried to give me a CGN3 modem for a replacement and I told him no. The tech proceded to tell me that there are "issues" with the CGN3ACSMR modems. Then he said it was a backend issue. He claimed that he was going to check the cable from the pole to my home but i didn't see anyone up there at all. Guess I'll have to call again. I hooked my modem up to the main cable feed to my house and my upstream is still in the 42 to 43 range. Now the LAN light on the modem is constantly flashing and appears to be constantly sending and receiving data, even when all other devices on my network are disconnected.
Here is a DOCSIS event log from today wonder if this would be of any help. I've removed all MACs
The DOCSIS event logs is shown here
|1||03/10/16 13:45:15||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|2||03/10/16 13:46:35||82000400||critical||Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|3||03/10/16 13:47:19||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|4||03/10/16 13:47:20||73040100||notice||TLV-11 - unrecognized OID;CM-MAC=xxxxxxx;CMTS-MAC=xxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|5||03/10/16 14:24:56||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|6||03/10/16 14:24:57||82000300||critical||Ranging Request Retries exhausted;CM-MAC=xxx;CMTS-MAC=xxxx;CM-QOS=1.1;CM-VER=3.0;|
|7||03/10/16 14:24:57||82000600||critical||Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xxxx;CMTS-MAC=xxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|8||03/10/16 14:47:54||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|9||03/10/16 14:47:55||84000500||critical||SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xxxxxx;CMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|10||03/10/16 14:48:00||84020200||warning||Lost MDD Timeout;CM-MAC=xxxxxxxxx;CMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|11||03/10/16 15:50:46||82000200||critical||No Ranging Response received - T3 time-out;CM-MACxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|12||03/10/16 11:02:58||82000400||critical||Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|13||03/10/16 11:05:00||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|14||03/10/16 11:05:01||73040100||notice||TLV-11 - unrecognized OID;CM-MAC=xxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|15||01/01/70 00:01:35||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=xxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|16||03/10/16 11:41:36||82000400||critical||Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|17||01/01/70 00:01:39||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|18||03/10/16 11:58:22||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxxxCMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
|19||03/10/16 11:58:23||73040100||notice||TLV-11 - unrecognized OID;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.0;|
No Ranging Response received - T3 time-out;CM-MAC=xxxxxx;CMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.0;
Ok, was the modem replaced with another CGN3ACSMR? If so, does it have firmware version 18.104.22.168 loaded, as seen on the Status page, or does it have the older 22.214.171.124 which is very problematic?
Can you log into the modem and check that version, and copy the downstream and upstream tables again and paste them into the thread just to see how they turned out?
Is your internet service running as it should, except for the flashing LAN Led, or are you still having problems?
From the CGN3 manual, which will still apply, a Green blinking Led indicates:
A device is connected to one of the LAN ports via a Fast Ethernet (100Mbps) link, and is transmitting or receiving data.
A blue blinking Led indicates:
A device is connected to one of the LAN ports via a Gigabit Ethernet (1000Mbps) link, and is transmitting or receiving data
From what I remember, the colour of the Led was in error when a gigabit device was connected. Maybe by now that has been corrected. Any chance that you have a connected device that has a standby state that leaves the port up and running when the device is supposed to be off or in standby mode?