01-05-2017 11:03 AM - edited 05-02-2017 07:09 AM
*** This post was last edited May 2, 2017 ***
Good morning Community,
As I mentioned in a post two days ago, we have received the next firmware 2.0.10.20 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.
However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.
In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂
UDP Packet Loss
The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.
Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).
Bufferbloat
When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.
Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 2.0.10.27 but more likely in 2.0.10.28 and a change in network configuration.
The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.
Update April 22: This problem seems resolved in firmware 2.0.10.27
5 GHz WiFi Low range for channels 36 to 48
Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.
Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.
Workaround: manually select higher channels (149-153-157-161)
Update April 22: The channel selection algorithm has been improved in firmware 2.0.10.27
Loss of OFDM Channel Lock
Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.
Update April 12: This problem is resolved in 2.0.10.26T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 2.0.10.13. We are making improvements at every firmware but it is not a perfect system.
The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.
NAT Loopback not working for wired clients
When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.
Update April 12: This problem is resolved in 2.0.10.26T2 (not confirmed)
LAN Counters not working
Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.
This problem has been reported to Hitron for investigation.
Unexpected modem reboot
Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.
Update April 12: This problem is resolved in 2.0.10.26T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
WiFi Survey
The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.
Guest Network
When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless". This has been reported in firmware 2.0.10.26T2.
Update April 22: This issue has been resolved in firmware 2.0.10.27
Update May 2: It seems this issue is not fully resolved and still experienced by some users
Future Planned Improvements
The following are items that we are working on in parallel of the above.
Dave
*Edited Labels*
02-04-2018 03:50 PM - edited 02-04-2018 03:56 PM
If you're seeing that the device is connecting to the 4582 at 1 gigabit/sec, as evidenced by the port LED, but you're not getting the max data rate out of the modem, there are three other possibilities:
1. you have a signal issue between the modem and the Cable Modem Termination System. The CMTS controls and provides data services to all of the connected Rogers modems in your neighborhood. That includes Cable TV, Internet and Home Phone modems.
2. The modem isn't provisioned properly for the level of service that you have signed up for.
3. The device port is running at 1 Gigabit/sec, but the port transfer rate is set for 100 Mb/s for some reason. That could be an issue with Mac's and Windows pc's, other devices, you would have to check the settings and specs.
To check these items:
1. Log into the modem, navigate to the STATUS .... DOCSIS WAN tab, copy the Downstream table, all the way to the bottom of the OFDM Upstream section. Paste that into a post. The copy and paste process will paste in the text contents of the table. That will allow me to check the OFDM (DOCSIS 3.1) status for the modem.
2. Call tech support and ask the CSR to check the modem and confirm that it is in fact provisioned for your level of service. If you do this, ask the CSR to run a signal check on the modem as well, just to see if it passes or not. If not, you can expect to see a tech at your home within the next few days as arranged with the CSR.
3. Drill down into the device settings to determine the max data transfer rate and set it higher if possible. You might have to check the device specs at this point.
Just to note, if you have subscribed to gigabit service, there are customers who are having issues with that level of service due to issues with the OFDM channel processing. I would expect those that are running the data rate below that shouldn't have huge issues even with OFDM processing issues, but, anything is possible.
Here's a link to an older CGN3 pdf manual. This is getting old at this point, but, it will be close enough except for the newer 802.11ac Wifi settings and items unique to this modem. I don't know if Hitron has produced an updated manual recently but I'll look around.
02-04-2018 04:37 PM
Thanks
I do not think it's the cable side is causing any problem. My WiFi speeds are 200Mb/s. I have an ignite 150, but was having some issues so rogers replaced the modem which is when the wired download speed was reduced by half. But I think the up stream speeds are OK.
On the other hand, perhaps the modem itself is configured incorrectly. The switched ports show a speed of 100M and do not appear to be modified by me.
I shall still investigate the the cable and discuss with SONY to determine if there is something in the protocol between Sony and the router that might limit the speed.
Since you asked, here is the data from the modem. I expect you will find it does not show a problem on the upstream sice.
Thanks
Barry
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | -1.200 | 7 | 40.366 |
2 | 855000000 | 256QAM | -5.300 | 3 | 37.636 |
3 | 861000000 | 256QAM | -5.600 | 4 | 37.636 |
4 | 579000000 | 256QAM | -1.300 | 5 | 40.366 |
5 | 585000000 | 256QAM | -1.400 | 6 | 40.366 |
6 | 849000000 | 256QAM | -5.300 | 2 | 37.636 |
7 | 597000000 | 256QAM | -1.200 | 8 | 40.366 |
8 | 603000000 | 256QAM | -1.000 | 9 | 40.366 |
9 | 609000000 | 256QAM | -0.500 | 10 | 40.366 |
10 | 615000000 | 256QAM | -0.700 | 11 | 40.366 |
11 | 621000000 | 256QAM | -0.900 | 12 | 40.366 |
12 | 633000000 | 256QAM | -1.200 | 13 | 38.983 |
13 | 639000000 | 256QAM | -1.300 | 14 | 38.605 |
14 | 645000000 | 256QAM | -0.900 | 15 | 38.983 |
15 | 651000000 | 256QAM | -0.900 | 16 | 38.983 |
16 | 657000000 | 256QAM | -1.100 | 17 | 38.983 |
17 | 663000000 | 256QAM | -1.700 | 18 | 38.983 |
18 | 669000000 | 256QAM | -1.900 | 19 | 38.605 |
19 | 675000000 | 256QAM | -1.900 | 20 | 38.983 |
20 | 681000000 | 256QAM | -2.000 | 21 | 38.605 |
21 | 687000000 | 256QAM | -1.800 | 22 | 38.983 |
22 | 693000000 | 256QAM | -1.800 | 23 | 38.983 |
23 | 699000000 | 256QAM | -1.800 | 24 | 38.605 |
24 | 705000000 | 256QAM | -1.500 | 25 | 38.983 |
25 | 711000000 | 256QAM | -1.200 | 26 | 38.983 |
26 | 717000000 | 256QAM | -1.500 | 27 | 38.983 |
27 | 723000000 | 256QAM | -1.900 | 28 | 38.983 |
28 | 825000000 | 256QAM | -4.800 | 29 | 37.636 |
29 | 831000000 | 256QAM | -4.900 | 30 | 37.356 |
30 | 837000000 | 256QAM | -4.800 | 31 | 37.636 |
31 | 843000000 | 256QAM | -4.800 | 32 | 37.636 |
32 | 303000000 | 256QAM | 0.600 | 1 | 38.605 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | 1.000000 |
1 | NA | NA | NO | NO | NO | NA |
02-04-2018 04:43 PM
Thanks
I do not think it's the cable side is causing any problem. My WiFi speeds are 200Mb/s. I have an ignite 150, but was having some issues so rogers replaced the modem which is when the wired download speed was reduced by half. But I think the up stream speeds are OK.
On the other hand, perhaps the modem itself is configured incorrectly. The switched ports show a speed of 100M and do not appear to be modified by me.
I shall still investigate the the cable and discuss with SONY to determine if there is something in the protocol between Sony and the router that might limit the speed.
Since you asked, here is the data from the modem. I expect you will find it does not show a problem on the upstream sice.
Thanks
Barry
ps for some reason the Rogers sit will not let me attach the status table. Says there is HTML in the rich text data, whatever.
02-04-2018 04:46 PM
Ahhh Snap. It worked but said it did not.
02-04-2018 05:53 PM - edited 02-04-2018 05:55 PM
Your signal levels aren't too bad. There is the usual high frequency roll off, but, that won't have any effect on your modem. Its running DOCSIS 3.1 on the downstream side, so the upper DOCSIS 3.0 signal levels are essentially meaningless at this point. The signal to noise ratios are ok, so that tells my that you don't have any external noise on the cable system, at least for the upper frequecies in the table. You indicated that your getting 200 Mb/s on a 150 Mb/s plan, so, your doing ok. Can you post the upstream levels as well? Highlight or select the data within the table boundaries, then you should be able to right click and copy the data.
I had a look at the Sony site, just to see what I can find. Looks like the newer Android TVs have 802.11n and 802.11ac, which should ensure that you will get an acceptable data rate from the modem or router to the TV. There is absolutely no mention of the LAN port data rate from what I've seen. All I can see is that it has a bottom LAN port, which is pretty useless.
Do you happen to know if your Mac has an gigabit port on it?
02-04-2018 06:29 PM
So I called Sony and although the CSR was pleasant and tried to help he did not. He sent a reference to their knowledge base items. No joy there.
The 802.11ac performance of the TV and Modem is great indeed.
I can live with this situation until Bell (now in our building) makes an offer for internet that I cannot refuse. I'll then go through similar issues with them.
Here's the upstream, because you asked.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 23700000 | ATDMA - 64QAM | 35.750 | 2 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 41.000 | 3 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 36.750 | 1 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
02-25-2018 06:54 PM - last edited on 02-25-2018 08:05 PM by RogersMaude
I have problems with my Rogers Rocket Modem. Basically I have an access point a $200 Gigabit Business TP Link one. So my house is long and the Rogers Rocket Modem does not cover the whole house. So I have an access point installed. Its hardwired into the CAT6 outlet on the wall which was wired into the house before we bought it (it's a brand new house) The CAT6 goes to a gigabit business netgear switch in the basement which then goes on via CAT6 to the Rocket Modem.
My issue is this, when I first was using the Access point I had similar speeds to as if I was connected to the Rocket Modem on WIFI. Since then speeds have just been slowing and slowing down. We pay for 500mb we usually get around 300mb, on the gigabit access point on the 5ghz band stood right by it I get 10mb down and 20mb up.
What is stranger is if I plug my laptop into the CAT6 outlet where the AP is plugged in with the same cable I'm getting 420mb down and 26mb up. Also FYI whilst the access point is plugged in it shows as gigabit on the Rocket Modem management page. Also I had Rogers swap my modem for an identical one but new to see if this fixed the issue and it didn't.
Its almost like the Rocket Modem is throttling the AP and slowing it right down its just weird.
Are there any solutions to this issue or settings I can change in the Rocket modem to make this work better?
Rogers are useless when it comes to tech support they just say "not our issue" problem is they don't have there own solution which they support either so what can you do if you have a normal sized house. I'm seriously thinking of switching back to Bell just for internet as there Router was awesome and covered the whole house on the 5ghz band.
Also I am an IT tech so all the basic testing has been done. I also tested the CAT6 with my mega tester and there was no interference on the CAT6 cable. It tested end to end for 10.8GBPS. I'm used to working with big business switches routers and modems not these little combi router modems. Another thing is that the WIFI's are all on different channels and the SSIDs are different for all the networks. So I have 2 networks on the access point, 1 is 2.4ghz and the other 5ghz and the same for the Rocket Modem but all with different names. So my WIFI Router is not in bridge mode because thats not what I'm doing I still use the Rocket Modem and also I gave the access point a static IP which is reserved in the Rogers modem.
02-26-2018 09:53 AM - edited 02-26-2018 09:58 AM
@lukesmith2, from the description of your home it sounds as if you might be running into wifi interference issues with your neighbors. Can you have a look at the following post, specifically at the wifi settings and wifi monitoring applications to check out your wifi environment.
http://communityforums.rogers.com/t5/Internet/slow-wifi/m-p/399949#M47222
inSSIDer is getting long in the tooth by now, so, you might want to load both inSSIDer and Acrylic on a laptop and conduct a site survey, from the front of the house to the back, to see who else you're competing with for available wifi channels. If you haven't already done this, doing it now will give you a better idea of what channels you should be using. Do you run wifi site surveys at work by any chance? If so, perhaps you might have access to much better equipment to run the survey.
The other point to keep in mind is the power output for the various wifi channels. In Canada the following power limits apply for the 5 Ghz channels:
Channels Output power
36 to 48 50 or 200 mW This will depend on the approval date by Industry Canada.
200mW is the latest limit
52 to 144 250 mW These are Dynamic Frequency Selection (DFS) channels which
can be accessed by the CODA-4582 modem.
149 to 165 1 W
Here's a chart that shows the same: https://www.semfionetworks.com/blog/industry-canada-new-5ghz-band-regulations
So, the upshot is that running 5 Ghz wifi on the lower channel range will give you the least range from a modem or router. Running in the upper 149 to 165 channel range will result in the largest range from the modem or router. Depending on the layout of your home, you might be able to run both routers in the upper 149 to 165 channel range by selecting channel 149 for one router and channel 161 for the other with 20/40/80 selected as the channel bandwidth. Running 80 Mhz wide channels, there would be an overlap, but the clear channel check which is requested by the transmitter and carried out by the receiver would indicate if the channels required for 80 Mhz wide operation were available or not. If not, then the transmitter will step down to 40 or even 20 Mhz wide channels. Keep in mind that this occurs for every transmission, so it will change from one transmission to the next. The other question that comes into this is what are your neighbors running in terms of their wifi channels and how does that impact on the ability to run your wifi in that upper channel range?
Wifi channels:
You indicated that you have a Rocket modem. Just to be clear, is that one of the black Hitron modems, or do you by any chance have the newer white CODA-4582 modem. The 4582 modem can access the middle channel range, which is the Dynamic Frequency Selection group. I don't know if the CGN3ACSMR and related modems have had a firmware update which will allow that. If, when you do a site survey in the home you find that the DFS channels are open and available for use while the lower and upper 5 Ghz channel group are occupied by nearby modems and routers, then you might want to give the DFS channels a go to see how it might turn out. The 250 mW power restriction might not work for you, depending on the range from the modem that might be typical. That is something that you will have to experiment with, different channel selections, which in turn effects their max power output and therefore the max range from the modem or router that you will see.
When you do a site survey of your home with a laptop application, doing it from the front of the home to the back, stop in place and let the display numbers settle out. That might take two to three minutes, so, you probably want to start at the front of the home in one location, see what other networks show up, then walk about 15 feet (maybe) and wait for the signal levels to settle out, and ... etc, etc. Ideally you would have about 45 dBmW difference between your network, and the next network, in terms of the received power level. If you have other networks on the same channel, you would run into co-channel contention, where there is more than one transmitter on the same channel and every device takes its turn to transmit thru contention access. If there are other channels above or below your network channel that are running nearby, then you run into Adjacent channel interference. So, it all depends on what you see on the display.
Fwiw, that version of inSSIDer does work very well for 802.11n, not so well for 802.11ac. There is a newer version out, but, that is no longer available as a single purchase as Metageek appears to have abandoned the home user market (too bad 😞 ). So, Acrylic will probably be the better choice to properly display 802.11ac network running nearby.
Ok, that should do it for now. My bet is that you're running into interference issues with your neighbors wifi modems and routers. Do you have a neighbor behind your home by any chance? All it takes is for one of your neighbors to bring home a new modem or router and your well running wifi network goes down the drain, so to speak. Fwiw, just walking from one side of my house to the other shows differences in received 5 Ghz networks, as both of my immediate neighbors and I are using the upper 5 Ghz channels. Despite that competition, from where my router sits, to where the wifi is normally used, using an upper channel set for 20/40/80 Mhz in width is still faster than using any of the lower channels where there is almost no competition. So, the output power of the upper channel range does make a difference. The end result is that the wifi is constrained due to the competition, but its still useable and the only thing that might make any difference (maybe) is to park an access point at the other end of the house. That still won't solve the contention access issue for the same channels, but, I might try that one of these days just as an experiment.
Hope this helps.
02-26-2018 11:54 AM
Sounds good thanks.
I try to position tion my channels to avoid the others in my area.
Do you happen to know if the hard wired port has the ability to negotiate a speed in a way the wifi does not.
I get slower speeds when hardwired to my Sony android than when on wifi. Strange but true.
02-26-2018 12:24 PM - edited 02-26-2018 12:25 PM
@holtzkener, the ethernet ports on the modem and device will negotiate an acceptable data rate for both. If that rate is 1 Gb/s, then the connected port LED at the back of the modem will show flashing amber in colour. If the rate is 10/100 Mb/s then the connected port LED will show flashing green. Note that these colours appear to be backwards when compared to the rest of the industry.
The wifi connect rates are dynamic. They will depend on the received signal level and signal to noise ratio. If you right click on the internet symbol in the task bar at the lower right hand side of a laptop monitor, select "Open Network and Internet Settings". Then select View Your Network Properties. On a hardwired desktop that next Network Properties page shows the wired Link Speed. On a laptop it should show the max transmission rate or Link Speed, at any given time. That's not the data rate that you might see from a speedtest. It should show the transmission rate which will include wifi overhead. If you walk around your home with the laptop, moving away from or close to the modem, you should see that Link Speed change. Give it a couple of minutes to settle out if you move to a new location. If you stand next to the tv that will give you an idea of the transmission rate that you can see with the laptop. That's not necessarily applicable to the TV as we don't know how many antenna are installed on the tv and what the tv's wifi adapter will process in terms of data rates. But, if you compare that number to what you see when you're closer to the modem, it will indicate how much of a loss there is in the data rate, from close to further away, or vice versa.
To calculate what the actual data rate will be, have a look at the following modulation and coding index. If you look at the Link Speed with a laptop, that number should correspond to one of the numbers listed in that chart. The spatial streams basically refers to the number of antenna that are operating. Laptops typically have two antenna, although single antenna laptops are common and Macbook Pros have three antenna I believe. So, if you have a typical laptop with two antenna and the Link Speed matches one of the numbers in the table, take the modulation and coding fraction which ranges from 1/2 to 5/6 and multiply the Link Speed by the appropriate number. Remember that the modem or router and laptop will constantly renegotiate link speeds, so the numbers will move up and down, hopefully remaining fairly stable, but there will be some movement up and down in realized data rates.
http://www.wirelessedge.com.au/understanding-modulation-and-coding-scheme-mcs-index-values/
02-26-2018 12:43 PM
02-26-2018 06:48 PM - last edited on 02-26-2018 07:14 PM by RogersShaun
CODA-4582 reboots when Huawei P10 connects to 2.4G Wi-Fi
This one had me stumped pretty bad. Wondering why my internet dropped every time my friend's new Huawei P10 attempted to join the network.
Model: CODA-4582
Hardware Version: 1A
MAC: xx:xx:xx:xx:xx:xx
Current Firmware: 2.0.10.33T3
We've tested on two separate occasions, around 5x each. The last 3 times today, I sat with `ping 8.8.8.8` running and had her connect to WiFi. Immediately I got "Request timeout for icmp_seq nnn". Having her disconnect herself from WiFi at this point is too late and I watch the router reboot itself and come back online in ~3min. We can then repeat and reproduce the issue, although sometimes it takes up to 60sec before it times out.
I have never seen this before and not sure how to proceed. I consider myself pretty technically savvy and am clueless. I'm hoping maybe @RogersDave can shed some light on this... Is her phone's MAC buffer overflowing my router?
My friend's phone details:
Model: Huawei P10, VTR-L09
Android Version: 7.0
Please help, this is a sucky thing to try and diagnose 😞
02-26-2018 09:13 PM - edited 02-26-2018 09:14 PM
@f3ndot I think you've run into a run of the mill Intel or Hitron problem, not sure which it might be. Try the same routine with a connected device and I bet you'll end up with the same result, when the second device is acquiring an IP address from the modem, you will end up with timeouts in the ping test. I've seen similar results with the modem running in Bridge mode, connecting a second device to it. The traffic thru the modem to the first connected device would basically stop while the modem is sorting out what it needs to do for the second device. I didn't see any reboots however. It possible that you've found a new bug! If so, congrats. I haven't checked this recently, but, its one my "to do" list now.
02-27-2018 10:45 AM
Ah yes, I should be clear. Once this phone attempts to connect to WiFi (and the phone does show a successful connection) all other devices on the network are unable to connect to the internet until the router automatically goes into a crash & reboot (usually a minute after the phone connects).
If the phone does not leave the wifi network, the router will continue to bootloop.
02-27-2018 01:08 PM
@f3ndot wrote:Ah yes, I should be clear. Once this phone attempts to connect to WiFi (and the phone does show a successful connection) all other devices on the network are unable to connect to the internet until the router automatically goes into a crash & reboot (usually a minute after the phone connects).
If the phone does not leave the wifi network, the router will continue to bootloop.
Perhaps it is this problem (their explanation is pretty unclear) https://www.androidauthority.com/google-home-chromecast-wifi-problems-830373/
Also https://9to5google.com/2018/01/15/google-chromecast-home-wifi-outage/
There are other bad descriptions. Bottom line, as far as I can make out: apply available updates to your Android devices. Updating Play Services might be a bit different from updating other packages.
Notice that the problem prompted updates to TP-Link router firmware. And others. But with the Android fixes, Android devices should no longer provoke misbehaviour in a router.
02-27-2018 01:15 PM
03-04-2018 01:34 PM
I just moved to a new house and got the gigabit speeds but still having pl issues. can someone tell me if the signal to noise ratios are good.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | -6.400 | 7 | 36.387 |
2 | 849000000 | 256QAM | -7.000 | 2 | 36.610 |
3 | 855000000 | 256QAM | -7.400 | 3 | 36.610 |
4 | 861000000 | 256QAM | -7.500 | 4 | 36.610 |
5 | 579000000 | 256QAM | -6.000 | 5 | 36.610 |
6 | 585000000 | 256QAM | -6.000 | 6 | 36.610 |
7 | 303000000 | 256QAM | -6.200 | 1 | 36.387 |
8 | 597000000 | 256QAM | -5.900 | 8 | 36.610 |
9 | 603000000 | 256QAM | -5.200 | 9 | 36.610 |
10 | 609000000 | 256QAM | -5.700 | 10 | 36.387 |
11 | 615000000 | 256QAM | -5.800 | 11 | 36.387 |
12 | 621000000 | 256QAM | -6.600 | 12 | 36.387 |
13 | 633000000 | 256QAM | -6.100 | 13 | 36.387 |
14 | 639000000 | 256QAM | -7.200 | 14 | 35.780 |
15 | 645000000 | 256QAM | -6.800 | 15 | 36.387 |
16 | 651000000 | 256QAM | -6.300 | 16 | 36.387 |
17 | 657000000 | 256QAM | -6.000 | 17 | 35.780 |
18 | 663000000 | 256QAM | -6.500 | 18 | 36.387 |
19 | 669000000 | 256QAM | -6.600 | 19 | 35.780 |
20 | 675000000 | 256QAM | -6.600 | 20 | 36.387 |
21 | 681000000 | 256QAM | -6.900 | 21 | 36.387 |
22 | 687000000 | 256QAM | -6.500 | 22 | 35.780 |
23 | 693000000 | 256QAM | -5.900 | 23 | 36.387 |
24 | 699000000 | 256QAM | -5.800 | 24 | 36.387 |
25 | 705000000 | 256QAM | -5.700 | 25 | 36.610 |
26 | 711000000 | 256QAM | -6.000 | 26 | 36.387 |
27 | 717000000 | 256QAM | -6.200 | 27 | 36.387 |
28 | 723000000 | 256QAM | -7.300 | 28 | 35.595 |
29 | 825000000 | 256QAM | -6.600 | 29 | 36.610 |
30 | 831000000 | 256QAM | -6.700 | 30 | 36.610 |
31 | 837000000 | 256QAM | -6.900 | 31 | 36.610 |
32 | 843000000 | 256QAM | -6.500 | 32 | 36.610 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | -6.400002 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38596000 | ATDMA - 64QAM | 45.250 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 41.500 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 42.000 | 2 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
03-07-2018 01:07 AM - last edited on 03-07-2018 07:55 AM by RogersShaun
CODA-4582 suddenly auto reboot by itself. Firmware v2.0.10.28T2
Hi,
I have a reboot issue with CODA-4852 Rogers modem. I just got this modem a month ago, I use this modem in bridge mode and connect with my Linksys EA9300 router. But after a short while, the modem will reboot suddenly and it happen very offen. I know that there is a new firmware which will fix the reboot issue which is firmware v2.0.10.33T3 or even newer version. So how can I get this firmware update for my modem. Please advice me the instruction for this firmware upgrade request. This reboot issue also happen in gateway mode. Please help me to fix this issue.
Many thanks
03-07-2018 04:26 PM
@tabochan, if the modem is rebooting on its own, that's usually an indication of cable problems. The reboot is the result of the modem attempting to reconnect to the Cable Modem Termination System (CMTS) which controls and provides data services to all of the Rogers and TPIA connected modems in your neighborhood. A firmware update or change in modems will not resolve a cable issue. You can call tech support and ask the CSR to run a signal check on the modem and indicate that the modem is rebooting on its own. See if the signal check passes or not. The one problem is that the signal levels will look normal after a reboot, normal enough to pass a signal check perhaps, but, ask the CSR to run the check to see what turns up.
You can also post the signal levels here. Log into the modem, navigate to the STATUS .... DOCSIS WAN tab, copy the downstream and upstream table, all in one go. Then paste that into a post. The copy and paste process will paste in the text contents of the table. Ignore the data above the Downstream table as that is specific to the modem. With those levels posted, one of the other RE's, or myself or the moderators can tell you if there are any issues with them.
03-14-2018 03:59 PM
Hey Community!
Check out the latest post from @RogersSergio, regarding updates to the CODA modem! FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial.
@RogersSergio wrote:
Sorry for the delayed in providing an update.
The latest firmware pushed out for the CODA devices is 2.0.10.33T11
Although there is a large "T" version jump we have only implemented a WiFi fix.
During our rollout of the 2.0.10.33T03 code we discovered an issue with a subset of devices in the field which caused wifi to stop working.
Please let us know if you run into any issues especially on WiFi
Thank you all for your ongoing support and feedback
RogersSergio
Keep us posted on updates with it.
Thank you 🙂
RogersCilio
03-17-2018 08:59 PM
Hello @f3ndotf, were you able to find a solution to the p10 connectivity issue? I am experiencing the exact same issue with my Ignite router once my girlfriend connects with her phone...
Thanks,
Gary