@WestPoint there are a couple points to clarify. The Resident Experts, including myself are site volunteers and not Rogers employees. So, unfortunately, the RE's are not in the loop when it comes to deployment decisions. Second, @RogersMargaret has departed the forum and @RogersDarrell is back. If I remember the post correctly, I believe that Darrell is the head honcho for the forum staff.
Firmware Version 35T1 is still out and in use by a small modem test group. I suspect that someone in Tech Support made the decision to roll back from 35T1 over the last two weeks when Rogers was having so much trouble with the data rates due to the fire in New York. I wonder if that decision was made in consultation with the engineering staff in charge of the version development? Definitely looks like 35T1 has absolutely nothing to do with the fire in New York. Don't know why the decision was made to roll back from that version.
If you want 35T1 reloaded, send a message to @CommunityHelps asking for a reload. I don't think there will be any issue with the reload.
In terms of the 2 years of crowd-source data and beta firmware fixes, the 4582 was released in Dec 2016, so, not quite two years to date. Over that course of time, including the current trial version 35T1, there have been 23 test or production versions released, roughly one every 3.3 weeks. That's a pretty decent rate for a new product. Do those updates resolve all of the issues, no, but, the modem has come a long way from day one. I suspect that the CMTS to modem path with DOCSIS 3.1 is proving to be a challenge in a good number of cases and that possibly, the modems DOCSIS 3.1 OFDM channel processing has not lived up to expectations. Its one thing to prove that it works in the lab, quite another to take it into the field and have it live up to expectations. I have already expressed my opinions on that to @RogersSergio. There needs to be a major effort on the part of the field techs to ensure that the OFDM frequency range operates correctly, from CMTS to modem and, at the same time, Intel needs to improve the OFDM processing performance so that the modem operates at expected data rates without fail. All personal opinions of course. Having said that, the Rogers engineers may already have the next Intel SDK version in house for testing. That should bring an improvement in OFDM processing and may be a stepping stone to DOCSIS 3.1 upstream. I haven't heard of any release dates yet for further test versions (remember RE's are not in the loop), so, your guess is as as good as mine, and right now, I have no idea of when that will happen.
Personal opinion, the pressure's on. Bell is running symmetrical download/upload rates up to 1 Gb/s and has indicated that its moving to 5 Gb/s data rates next year. Symmetrical DOCSIS 3.1 can run 10 Gb/s both ways, but, that has yet to be proven in any public (user) installation. The first challenge is for Rogers is to get to symmetrical Gb/s. Of course, even if the equipment can support it, will Rogers actually offer that capability? That's a marketing decision. Who knows how that discussion will go, but, if higher upload rates don't arrive fairly soon, I suspect that Bell will probably take an increasing market share where fibre is available, ready to go.
So, not apologizing for Rogers in any way, shape or form. Not my job. All I can offer is some explanation of what is, and what might be happening in the not too distant future (crystal ball gazing).
If you already have fibre available, my question is, why are you still running cable? You would see reduced latency, but, you run the risk of seeing some pretty strange routings out of Bell's network, and, you would lose IPV6. So, there might be reasons to stay with cable, depending on what item sits higher on the requirements list.
Hope this provides some clarity.
grrr, really ?? I wonder if that means that the next trial version is undergoing internal testing? Wish I could tell you more, but I think I'm being tactfully or not so tactfully ignored, take your pick 😞
@soundwave80, not going to argue the point, but, let me point out the background history as a refresher. The Puma 6 CGN3xxxx modems were found to have severe latency issues, to and thru the modem for all IPV4 and IPV6 protocols. Don't know if you were around for that or not. To their credit, Rogers, with @RogersDave at the helm took this on and forced, finagled, coerced, Intel into resolving the problem. In Sept 2016 the first update to resolve IPV4 ICMP was released on the Rogers network. That was a first, for any ISP anywhere from what I saw. However, that was only IPV4 ICMP, leaving TCP/IP and UDP to be resolved, along with the same protocols for IPV6. At that time, I can only guess that it looked like it was going to be along road ahead and possibly many months before the other protocols were going to be fixed, if that was even possible. My guess, is that the engineering staff made an educated guess and decided to push ahead with the Puma 7 DOCSIS 3.1 modem that we have today. That was released in Dec 2016 and as I indicated above, has seen 23 trial and production firmware versions released. So, the gamble at that time was to either wait for Intel to try to resolve the Puma 6 latency problems, or, simply push ahead and sidestep that issue. Rogers chose the latter. Could the 4582 have used more time in development, yup, but, Intel and Hitron have been fairly active, trying to resolve the issues as they came up. That no doubt leads to a level of customer dissatisfaction, but, the alternative would be to put up with the latency issues of the Puma 6 modem. I don't think that the customers would have been happy with that either. Virgin Media Puma 6 users are just now receiving an update after two years of complete silence from Virgin Media. Their customers are not a bunch of happy campers at this point in time as there still hasn't been any public statement from Virgin Media concerning the firmware update, specifically what it resolves, and what it doesn't resolve, so the customers are left to sort it out on their own. So, back in Canada, this was a no win situation for Rogers with no easy answers in either direction. In that same time span, there have also been firmware updates for the Puma 6 modem to resolve those latency issues. As I'm running the 4582, I won't have an opportunity to determine if those efforts have been successful or not. From a latency perspective, the 4582 is way ahead of the Puma 6 modems.
From a network perspective, the introduction of the 4582 and DOCSIS 3.1 relieves some of the congestion issues that some users were experiencing. Its not perfect, but, it does make a difference. Unfortunately, as I indicated above, that has also exposed issues with the use of Orthogonal Frequency-Division Multiplexing (ODFM) channel, which should be pretty robust compared to the waveform used for DOCSIS 3.0. Implementation of DOCSIS 3.1 is new for a number of ISPs and unfortunately, it comes with teething pains of new technology. Only way around that would have been to push back the 4582 deployment, but, its very possible that the same issues with the OFDM channel processing would have arisen as that's more of a a network issue that the modem has to deal with.
All personal opinions of course .......
Hi all,
I apologize for the delay in responding to your questions around the firmware rollback. We have been heads down completing our investigation which has taken some time.
Although the rollout of the 35T1 firmware was successful and many of you saw improvements to your service we unfortunately identified an issue that was negatively impacting the network.
Given the nature of the issue we had no choice but to roll back to the previous firmware in order to limit the impact. We have also been going through all devices and firmware to confirm this issue is not present in any other device/code while working on a fix. I know for a number of you the update provided a much better experience and we are working hard to get an updated code in order to re-introduce the improvements seen in the 35T1 code which many of you stated had a positive impact to the devices performance.
Regards,
RogersSergio
Was rolled-back to 34T6 in May.... previously had good speeds of 1Gb+, but now for nearly a month cannot even reach 400Mb Did reboot...but still no improvement. Something is definitely awry here..... Rogers took a while to improve the 4582 and finally deliver 1gb speeds for almost a year .....but now, we're back to the same poor results we used to get in the early days of this program. Can you please check this out.....I am sure many others have same issue. Are there CMT issues....area issues or is this a Modem Software issue, ??. If we are not getting the speeds
Hi @rjmaxim
There have been a number of challenges that we have been experiencing but we are actively working to address every customers issues. I will be asking one of the forum moderators to reach out to you privately to see how we can help further.
In the meantime may i ask if you could run another speedtest using speedtest.net and selecting the Rogers speed test server option.
Although it's the same solution the servers are configured slightly differently and I would like to verify that the results you are getting on this speedtest aligns.
Thank you,
RogersSergio
Here's some food for thought on the Bell modem situation, specifically the HH3000. Don't worry about its multi device support. Bypass the HH3000 as described in the following thread and keep using your own router:
https://www.dslreports.com/forum/r31118482-Yes-you-CAN-bypass-the-HomeHub-3000
And .... I do hear what you're saying. I run my 4582 in Bridge mode and where I am in West Ottawa, my service has been rock solid over the last 10+ years. Using a third party router (Asus) has a lot to do with that as well, but, the basic cable service to the modem has been very reliable.
Edit: Just to point out, Netgear also manufacturs and sells a modem which happens to be Puma 6 based, and as a result carries all of the baggage that goes along with the Puma 6 modems (CGN3xxxx). It might not be pretty, but, Rogers has been very proactive over the last two years dealing with the latency issues of the Puma 6 modems. From what I remember, Broadcom didn't market a modem that was equivalent to the Puma 6 modems, as in a 24 channel DOCSIS 3.0 modem. As a result, there really wasn't much of a choice, except to pick Arris, Cisco, Compal or Hitron to manufacture a Puma 6 modem. So, Rogers was pushing the envelope with a 24 and 32 channel modem in order to deliver faster data rates to its customers. Looking back now, its really very very unfortunate that the Puma 6 modems turned out be such a headache for all ISP worldwide, not just with Rogers. But, as I said, Rogers has been very proactive in dealing with it. Its not a perfect situation and I don't think there was any easy answers to be had.
Two steps forward, one step back ..... 🙂 Most of the users in that thread appear to use the fibre to ethernet converter and run that straight into a router. You would need a managed switch or router that is vlan capable in order to separate the tv and internet data nets.
I have strong clean signal to my CODA modem and good speeds no matter what firmware is in it.
Currently 2.0.10.34T6
My issue is DHCP Reservation table limit of 9 devices.
Second issue is connection to those devices through port forwarding when they go into standby with lower link speed 100 or 10Mbs and disappear from connected devices list.
"I have strong clean signal to my CODA modem and good speeds no matter what firmware is in it."
Your ping is high, I would advise that you look into it.
-
938597 views
-
669 Likes
-
-
