I just finished pushing the newest code 2.0.10.33T2 to the participants that reported reboots. Hitron reported to me that they are still investigating the cause of these reboots and may provide me with a subsequent revision of the code later this week.
I'll be waiting for feedback on this code from both the community here and Hitron before I deploy it further.
--Dave
@Triple_Helix wrote:I just got it as well thanks @RogersDave
Software Version 2.0.10.33T2
The DOCSIS event logs is shown here No. Time Type Priority Event 1 11/01/2017 12:57:15 69010100 notice SW Download INIT - Via NMS 2 11/01/2017 12:59:20 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 3 11/01/2017 13:00:02 69010900 error Disruption during SW download - Power Failure 4 11/01/2017 13:00:02 69010100 notice SW Download INIT - Via NMS 5 11/01/2017 13:00:37 69011100 notice SW download Successful - Via NMS 6 11/01/2017 13:03:38 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 7 11/01/2017 13:06:12 69010100 notice SW Download INIT - Via NMS 8 11/01/2017 13:07:11 69011100 notice SW download Successful - Via NMS 9 11/01/2017 13:08:58 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Well I just got another random reboot with the new firmware. 
Hardware Version 2A Software Version 2.0.10.33T2 LAN Up Time 000 days 00h:09m:42s WAN Up Time 000 days 00h:07m:44s
MoCA 2.0 further testing. 
I purchased one MoCA 2.0 adapter with 4 gigabit port switch buildin from Amazon:
With recent CODA firmware .33 I'm getting good stable connection with speeds ranging around 400 to 500Mbps and ping 3ms. I can connect to my NAS drive and download large file at 50 Megabytes per second. MoCA throughput and responsiveness is very good according to my basic tests.
However when trying to stream media file over the MoCA connection the video is buffering every minute or so for few seconds. Replacing the MoCA connection with long direct Ethernet wire resolves the problem. My media streaming device is small single board computer Raspberry Pi with Ethernet 100Mbps port only.
Here is my dilemma. Why is the device working without any issues over 100Mbps direct Ethernet wire but not through MoCA adapter with 500Mbps speed? Is CODA modem MoCA 2.0 connection full duplex?
@mES19, personal opinion, if you're not running a gigabit plan, and even if you were, my advice would be to step down to the CGN3ACSMR for any plan less than the gig plan, or down to the CGNM-3552 for a gig plan. Last thing you need is to be in a trade and then, the modem suddenly decides to reboot. If you have a router running with a continuous fail-over internet feed, then ok, its manageable but certainly not desirable. In your situation, typically you don't want, nor can you afford to have money on the line with modem issues afoot.
Whenever the reboot cause is sorted out, you could return to the CODA-4582.
Edit: The drawback to changing to the CGN3ACSMR or CGNM-3552 is the possibility of latency issues due to the type of protocol used in the platform data feed. You would have to monitor the incoming feed and orders with wireshark to determine exactly what protocol is used. If its TCP/IP, and possibly UDP, you could run into latency spikes with the data feed and orders. If you were running an HFT platform, that would definitely be a concern. If you were running minute charts or longer, and trading off of those charts, this isn't such a large issue and you might not notice any large latency spikes which can run up into the 200 to 300 ms range. If you were scalping with sub-minute charts, then this starts to become more important, just depends on how far down, in terms of time scales you might go with your charts. Trading off of tick charts would be a definite problem.
@mES19 wrote:As a daytrader these reboots are very frustrating and can be costly.
@mES19, are you experiencing the reboots on CODA firmware 2.0.10.33? If so, you can always roll back to the current production firmware (2.0.10.28T2) by performing a factory reset. Remember that the firmware trial program is for users willing to try out new features, latest enhancements and corrections. This software is released to the community in parallel of our internal testing and it happens that a firmware is worst than the previous.
I am always happy to change the version of software on your modem (temporary roll-back) if a specific version is causing too many issues to you. Just let me know.
--Dave
So far no reboots from the get go double install. This hints, the reboots are linked to certain modem activities. I suggest trial participants to post more detail report about modem setup and activities at reboot. Did you use it in wireless or wired mode, what are your QoS, Firewall and other modem settings, did it happen when you downloaded a torrent, watched a high resolution YouTube movie stream, browsed Ebay, did several things in parallel - what things? Or it happen, when the connected equipment was in sleep mode and did nothing? A little effort on your side rather than saying "Rogers modems are bad" can go a long way. Just remember, as Dave said you volunteered for this trial, so obviously were prepared to contribute a little more than complaints.
I also assume Rogers Trial Team has access to a lot more detail modem log compare to user WebUI log version, and possibly your entire ongoing traffic copy for analysis of modem workload causing failures? May be Dave can clarify that as part of the mandatory trial conditions disclosure? 
From security standpoint, also remember every time you hook your PC ethernet port directly to the modem in Bridge mode, you expose that PC to all kind of attacks directly from the web, so use a good router and other gear, and scan your PC with A/V each time you changed hardware setup.
Another important thing I leaned - just do factory reset and forget about the FW that causes you grief until next update - its still beta, issues are expected. I noted a more responsive WebUI and 1st page load in this FW version compare to 28T2. Currently running the modem in wired mode only with no reboots. Didn't change default settings much as using other LAN protection gear behind the modem.
@mES19 I would say that the best plan for now would be to run a factory reset as Dave indicated in order to return the modem to the current production firmware version which I believe is 2.0.10.28T2. The 4582 itself has much better performance in terms of any latency through the modem compared to the previous CGN3xxxx series or CGNM-3552 modems. I would say that the latency which can be seen in the other modems doesn't exist in this modem, so, for trading sub-minute or scalping, the 4582 is what you want to be using.
To run the factory reset, you can either hold the recessed reset button down (at the back of the modem) for 30 seconds and release it, or, use the modem's ADMIN .... DEVICE RESET ..... Factory Reset function.
In either case the reset will initiate the firmware check and production firmware load followed by a reboot back into Gateway mode.
-
932501 views
-
669 Likes
-
-
