But there’s a certain logic to the config, especially if you’ve ever done any CLI work on something like a Cisco.Ī recent photo of the CCR (cabling disaster included):įor routing, I’ll say I absolutely adore Mikrotik and RouterOS.
As mentioned, Mikrotik likes to do things a little differently. I wasn’t worried about any layer 3 capabilities on the switch (at the time), so it didn’t bother me at all that while the CRS317 was capable of being a full layer 3 switch, it couldn’t do it at anywhere near line-rate. Around that time, I also started using a CCR (Cloud Core Router) for my main edge device. This is Mikrotik’s 16 port SFP+ switch with a single gigabit port, ostenibly for management. A few days ago, thanks to a one or two sentence post on Reddit, I finally figured it out.īack in October 2017, I picked up a CRS317-1G-16S+RM. Well, not constantly, but it’s something that I keep finding reasons to try and hash out. Since October of 2017, I’ve been fighting with RouterOS and switching. That tiny company from Latvia does things a bit… different. These are dependent on the RAID "raid-chunk-size", filesystem block size, and the number of disks.I think anybody that’s ever used a Mikrotik and RouterOS can probably agree. In theory for RAID performance optimization - correct stride and stripe-width should be used. In this example we will create RAID 6 with 10 disks Disks has to be in same size or have to be set in same size partitions or use raid-max-component-size parameter to limit larger volume size to match other elements. For example RAID 10 (RAID 1+0) combines disk mirroring (RAID 1) and disk striping (RAID 0) RAID configuration Nested RAIDĬombination of multiple RAID configurations into other RAID. Provides no redundancy and is limited to single disk read/write speed.
Linearĭata is appended over multiple disks combining them into single large disk. RAID 6īlock-level data is striped evenly over the available disks. RAID 5īlock-level data is striped evenly over the available disks. Performance will be limited to a parity writing speed. RAID 4īlock-level data is striped to a dedicated disk where parity bits are stored. Same data is written in all drives (data is mirrored), this configuration provides best fault tolerance, but performance wise write speeds will be equal to slowest disk used in array.
RAID 0Īll data is written evenly over all disks in this RAID, this configuration does not provide any fault tolerance but provides best performance. RouterOS supports software RAID levels 0,1,4,5,6,linear and nested RAID. RAID (Redundant Array of Independent Disks) technology allows storing data on multiple drives - improving data transfer performance, data protection or both by combining them into logical units. On partition overlap, RouterOS will return error. Add type=partition parent=sata1 partition-size=500M partition-offset=10G
0 kommentar(er)
