How’s everyone’s experience with the CCR2004-16G-2S+ been these days? I remember hearing a lot about stability issues, but that was a while ago and could have been related to running V6 on it, when it was designed for V7, or maybe early V7 bugs. What’s everyone’s thoughts on the stability of the CCR2004?
I’ve configured a few of them in different places. They’ve been solid. I’ve read about the instabilities on v6, but I have only ever used them with v7, where I haven’t encountered anything worrying. EDIT: I1m not sure they still even run on v6; I’m quite sure the 12S+ variants don’t any more. (There was a hw rev.)
I know this wasn’t your question, and I’m only making assumptions based on your username , but if your use case is for long-term unattended operation in not-exactly-DC-clean and temperature regulated environments especially if combined with poorer maintenance access, I’d take a look at passively cooled devices, and specifically the rb5009. It has a more industrial type build and if the environment is anything like I’ve described, you’ll be much happier with it.
The 16G-2S+ variant of the CCR2004 was never released running v6, and v6 has no support for its networking hardware.
The 12S+2XS variant was initially released with v6, but many people have reported instability with it (though most of those reports seemed to calm down after the release of 6.49+).
It is true that there was a hardware rev of the 12S+2XS that renders it not entirely compatible with v6. But even before that hardware rev was released, the factory had already been churning out the original rev of the hardware but pre-loaded with v7 and with ‘factory-software’ set to a 7.x version#, preventing downgrading to v6 by the “usual”/supported methods.
I have managed to downgrade multiple 12S+2XS units to 6.49 through a very much unsupported and convoluted process. I have also done this with the newer hardware rev/refresh, and can report that it actually runs v6 perfectly fine (all networking interfaces are recognized and work fine), with the exception that the System > Health stuff doesn’t work…the hardware health monitoring part(s) of the logic board circuit were what primarily received changes on the newer revision. The practical end-result of this is that a r2 or greater 12S+2XS running (unofficially downgraded to) v6 cannot monitor fan RPMs nor control fan speed. Thus, the fans spin up to maximum RPM at power-up and never throttle back. Sounds like a jet engine the entire time and likely will wear out the fans prematurely. At least it doesn’t leave the fans not running at all, though, which would probably be a worse sin. So the unit isn’t cooking itself while it is running v6.
In contrast, the 16G-2S+ that never shipped with v6 to begin with can’t run v6 at all. I have “successfully” downgraded one to test this. All of the base hardware is actually recognized and works (it can boot from the NAND and read/write it just fine, most importantly) …but doesn’t recognize ANY of the built-in ethernet interfaces, because v6 was never updated to support the 16G-2S+ hardware configuration. Which makes it pretty useless as a router when running v6, heh.
I haven’t done too much with the single 16G-2S+ unit we received for testing, so cannot comment much on its stability or performance. However, I do not remember seeing any wide reports about it being unstable. This is in contrast to the deluge of reports about 12S+2XS instability, especially when it first started shipping. So I have no idea what OP is talking about, and am guessing they’re confusing the two CCR2004 models with each other.