Hi all, Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!). On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready? Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along? Any input appreciated!
Hi, I gain the impression that the devices running V7, get a special non beta version of 7 7.0.4 (Maybe) However at this time you can't upgrade it to anything (apart from a beta), or downgrade it. (And if you upgrade it, you may struggle to get the original firmware to put back on it) But you can presumably get Mikrotik support to help with issues you encounter if you keep the non beta version on it. Regards Roger [ Double-click this line for list subscription options ] Hi all, Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!). On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready? Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along? Any input appreciated! _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au---------------------------- Roger Plant
MikroTik has certified ROS v7 for a select few devices as "stable", one of those being the CCR2004-16G-2S+. I'm not sure why they consider it "stable" for some platforms and not others, but that's the current state of play. If you're ultra-concerned about stability (and I wouldn't blame you if you were) you could always try labbing it up with a couple of other MT units with Traffic Generators going to see how the new unit handles pushing packets over a period of time. On Sun, 22 Aug 2021 at 08:54, Thomas Jackson <thomas@thomax.com> wrote:
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
-- Kind regards, Matthew Kobayashi
Hi Thomas, and all.. Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received. Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; ) DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of current 'known bugs' that customers can use for reference in case they want to use this model for any particular application? MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for this product. We do not release products with known issues. So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; ) Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical purpose like a branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Thanks Mike (and all) for your responses We've got about a week between when we get into the new space and when we need to be in production on it, so we're going to give it a go while we have access to the links but no prod traffic, but likely will end up swapping it out before we go to prod. Kind regards, Thomas -----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Thursday, 2 September 2021 2:11 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready? Hi Thomas, and all.. Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received. Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; ) DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of current 'known bugs' that customers can use for reference in case they want to use this model for any particular application? MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for this product. We do not release products with known issues. So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; ) Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical purpose like a branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi all, Bit of a final update - we tried out the CCR2004 with ROSv7 during testing, and we were pleasantly surprised with the stability and feature-set. BUT - in the end we swapped for a CCR running ROSv6 mainly due to some rough edges and missing features with dynamic routing - the final killer was that we couldn't find any commands like "/routing bgp advertisements print <peer_name>" which made troubleshooting the install a lot harder, not to mention the fact that the routing filter functionality is clearly under active development and has a couple of odd bugs (eg editing a filter via WinBox simply doesn't seem to work). We're going to re-deploy the CCR2004 into one of our offices where the needs are very basic (just a few VLANs with some static routing between them) to get some more hands-on experience with v7, but at the moment it's hard to recommend where any dynamic routing comes into play. -----Original Message----- From: Thomas Jackson Sent: Thursday, 2 September 2021 3:01 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: RE: [MT-AU Public] ROS v7 - Production Ready? Thanks Mike (and all) for your responses We've got about a week between when we get into the new space and when we need to be in production on it, so we're going to give it a go while we have access to the links but no prod traffic, but likely will end up swapping it out before we go to prod. Kind regards, Thomas -----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Thursday, 2 September 2021 2:11 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready? Hi Thomas, and all.. Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received. Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; ) DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of current 'known bugs' that customers can use for reference in case they want to use this model for any particular application? MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for this product. We do not release products with known issues. So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; ) Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical purpose like a branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Saturday, 2 October 2021 11:06 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Bit of a final update - we tried out the CCR2004 with ROSv7 during testing, and we were pleasantly surprised with the stability and feature-set.
BUT - in the end we swapped for a CCR running ROSv6 mainly due to some rough edges and missing features with dynamic routing - the final killer was that we couldn't find any commands like "/routing bgp advertisements print <peer_name>" which made troubleshooting the install a lot harder, not to mention the fact that the routing filter functionality is clearly under active development and has a couple of odd bugs (eg editing a filter via WinBox simply doesn't seem to work).
We're going to re-deploy the CCR2004 into one of our offices where the needs are very basic (just a few VLANs with some static routing between them) to get some more hands-on experience with v7, but at the moment it's hard to recommend where any dynamic routing comes into play.
-----Original Message----- From: Thomas Jackson Sent: Thursday, 2 September 2021 3:01 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: RE: [MT-AU Public] ROS v7 - Production Ready?
Thanks Mike (and all) for your responses
We've got about a week between when we get into the new space and when we need to be in production on it, so we're going to give it a go while we have access to the links but no prod traffic, but likely will end up swapping it out before we go to prod.
Kind regards,
Thomas
-----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Thursday, 2 September 2021 2:11 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi Thomas, and all..
Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received.
Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; )
DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of CCR2004-16G-2S+ current 'known bugs' that customers can use for reference in case they want to use this model for any particular application?
MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for
product. We do not release products with known issues.
So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; )
Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical
Hi Thomas, great info - good to know : ) I hear that v7 is close to first production ('stable') release, so may not be far away. I also noticed that there are some very significant changes to how dynamic routing works - especially policy routing - with the old 'routing mark' now replaced with definable 'route table' (vrf-style) so I expect that there will be some important functionality changes in routing configuration. Did you send your feedback also to MT (support@mikrotik.com) - always the most effective way to have bugs addressed and for feature requests and ideas to be posted : ) Cheers! Mike. this purpose like a
branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Oh wow. haven't been tracking ros for a while still got them in the network. Have they fixed all of the single thread issues they had with ros6. bgp tables 10G port limited to 1G single tcp stream good news if V7 is going to deliver all of the stuff the promised On Mon, 4 Oct 2021 at 10:55, Mike Everest <mike@duxtel.com> wrote:
Hi Thomas, great info - good to know : )
I hear that v7 is close to first production ('stable') release, so may not be far away. I also noticed that there are some very significant changes to how dynamic routing works - especially policy routing - with the old 'routing mark' now replaced with definable 'route table' (vrf-style) so I expect that there will be some important functionality changes in routing configuration.
Did you send your feedback also to MT (support@mikrotik.com) - always the most effective way to have bugs addressed and for feature requests and ideas to be posted : )
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Saturday, 2 October 2021 11:06 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Bit of a final update - we tried out the CCR2004 with ROSv7 during testing, and we were pleasantly surprised with the stability and feature-set.
BUT - in the end we swapped for a CCR running ROSv6 mainly due to some rough edges and missing features with dynamic routing - the final killer was that we couldn't find any commands like "/routing bgp advertisements print <peer_name>" which made troubleshooting the install a lot harder, not to mention the fact that the routing filter functionality is clearly under active development and has a couple of odd bugs (eg editing a filter via WinBox simply doesn't seem to work).
We're going to re-deploy the CCR2004 into one of our offices where the needs are very basic (just a few VLANs with some static routing between them) to get some more hands-on experience with v7, but at the moment it's hard to recommend where any dynamic routing comes into play.
-----Original Message----- From: Thomas Jackson Sent: Thursday, 2 September 2021 3:01 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: RE: [MT-AU Public] ROS v7 - Production Ready?
Thanks Mike (and all) for your responses
We've got about a week between when we get into the new space and when we need to be in production on it, so we're going to give it a go while we have access to the links but no prod traffic, but likely will end up swapping it out before we go to prod.
Kind regards,
Thomas
-----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Thursday, 2 September 2021 2:11 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi Thomas, and all..
Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received.
Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; )
DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of CCR2004-16G-2S+ current 'known bugs' that customers can use for reference in case they want to use this model for any particular application?
MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for this product. We do not release products with known issues.
So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; )
Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical purpose like a branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Alex, It has certainly been talked about a lot, and there is already some official hint about status of that particular issue: https://help.mikrotik.com/docs/display/ROS/Routing+Protocol+Multi-core+Suppo rt tldr summary: there *is* support for multithreaded BGP table processing, managed by 'one task per peer or grouped by specific parameters' - i.e. anticipate some extra work involved to optimise performance ;) BUT, looks like there's good news to be had ; ) Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Alex Samad Sent: Wednesday, 6 October 2021 8:07 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Oh wow. haven't been tracking ros for a while still got them in the network. Have they fixed all of the single thread issues they had with ros6. bgp tables 10G port limited to 1G single tcp stream
good news if V7 is going to deliver all of the stuff the promised
On Mon, 4 Oct 2021 at 10:55, Mike Everest <mike@duxtel.com> wrote:
Hi Thomas, great info - good to know : )
I hear that v7 is close to first production ('stable') release, so may not be far away. I also noticed that there are some very significant changes to how dynamic routing works - especially policy routing - with the old 'routing mark' now replaced with definable 'route table' (vrf-style) so I expect that there will be some important functionality changes in routing configuration.
Did you send your feedback also to MT (support@mikrotik.com) - always the most effective way to have bugs addressed and for feature requests and ideas to be posted : )
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Saturday, 2 October 2021 11:06 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Bit of a final update - we tried out the CCR2004 with ROSv7 during testing, and we were pleasantly surprised with the stability and feature-set.
BUT - in the end we swapped for a CCR running ROSv6 mainly due to some rough edges and missing features with dynamic routing - the final killer was that we couldn't find any commands like "/routing bgp advertisements print <peer_name>" which made troubleshooting the install a lot harder, not to mention the fact that the routing filter functionality is clearly under active development and has a couple of odd bugs (eg editing a filter via WinBox simply doesn't seem to work).
We're going to re-deploy the CCR2004 into one of our offices where the needs are very basic (just a few VLANs with some static routing between them) to get some more hands-on experience with v7, but at the moment it's hard to recommend where any dynamic routing comes into play.
-----Original Message----- From: Thomas Jackson Sent: Thursday, 2 September 2021 3:01 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: RE: [MT-AU Public] ROS v7 - Production Ready?
Thanks Mike (and all) for your responses
We've got about a week between when we get into the new space and when we need to be in production on it, so we're going to give it a go while we have access to the links but no prod traffic, but likely will end up swapping it out before we go to prod.
Kind regards,
Thomas
-----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Thursday, 2 September 2021 2:11 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS v7 - Production Ready?
Hi Thomas, and all..
Since your original post (below) regarding CCR2004 and routerOSv7, we've been having some back-and-forth correspondence with MT trying to get a definitive statement about that, but with the usual elusive reponses received.
Eventually, after trying again to spell it all out precisely, we received a response that is about as good as it will get ; )
DUXTEL: what advice do you suggest that we offer to customers seeking to use CCR2004-16G-2S+ in a production environment? Is there any list of CCR2004-16G-2S+ current 'known bugs' that customers can use for reference in case they want to use this model for any particular application?
MIKROTIK: we can not sell a product that is not ready for the production environment. Unfortunately, we do not have a public buglist for any product/model. RouterOSCCR2004-16G-2S+ runs a specially designed and built v7 version. At the moment there are no major or showstopper issues for this product. We do not release products with known issues.
So I /guess/ that it means they are relatively confident that the unit will deliver the required functionality out-of-the-box in this case. (OR, they are keen to get some feedback from a more 'production environment' than usual - i.e. they are seeking willing guinea pig users ; )
Personally, I would be cautious about deploying one to a mission-critical application, but would be perfectly OK to try it in a less critical purpose like a branch or home office gateway - though arguably it is overkill for those kind of applications :-}
From our perspective, I'm really keen to get any feedback on performance and behaviour from anyone running that modem in production. We don't really have a good candidate for one ourselves, so we have not had an opportunity for thourogh testing yet :-}
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Sunday, 22 August 2021 8:52 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] ROS v7 - Production Ready?
Hi all,
Last week I picked up a CCR2004-16G-2S+ for a new build (it ticked basically every box for what we need, dual PSU, >8 ports, appealing price point, etc), and powered it up today to realise it is running ROSv7 out of the box, and doesn't have a downgrade path to v6 (my mistake for not reading the description closely enough!).
On one side, the Mikrotik website still lists v7 as beta which makes me uncomfortable pushing this into a prod environment, but on the other side it looks like all of the new models are coming out v7 only so presumably it is considered production ready?
Before I make the trip down to the DC to rack it up, how are others finding v7 stability? Or should I order a CCR1036 (our usual model for this type of work) and chuck the CCR2004 in the cupboard until v7 is a bit further along?
Any input appreciated!
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au
http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.
au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.co m.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.co m.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
participants (5)
-
Alex Samad -
Matthew Kobayashi -
Mike Everest -
Roger Plant -
Thomas Jackson