![]() I had posted some inqueries on a few subreddits and at the Mikrotik forums without much luck. This was not enough time for me to be able to figure it out, not to mention formulate the correct questions to be asking after a failed attempt. Unfortunately, as the CRS317 is my core switch, I was only able to schedule an hour or two of downtime every other week. Unfortunately, like any transition, it doesn’t help that the documentation is a bit hard to follow as it’s a mix of the old and new ways to handle things. I say “attempted” because it’s still a bit of a mess, but the bridging system is at least a SMALL measure of improvement over the old master-port config. It helped that the current RouterOS versions have attempted to clean up the switching config. Not to mentioned my interest in networking concepts has evolved and I wanted to use some non-router-y layer 3 features, like DHCP Relay. My RouterOS knowledge had grown exponentially through my machinations on the CCR, and it constantly bugged me that RouterOS on the CRS had defeated me. Until Mikrotik released SwOS version 2.6, around mid-November, the switch was as good as a brick, at least to me.įast forward some months and once again I was looking to get RouterOS running on my CRS317. Trying to figure RouterOS switching (especially in the pre-6.41 RouterOS versions) was probably one of the first IT related things in a long time that I would honestly say “defeated” me.The available firmware (2.5) at the time broke DHCP on any VLANs the switch could see.The default SwOS firmware (2.3p) on the switch resulted in a SwOS bootloop.RouterOS, which gives you full layer 3 capabilites, but potentially sacrifices line-rate speeds if you try and use any routing features, or SwOS, which turns the switch into an almost too-dumb managed switch that only supports LAGs, VLANs, RSTP, and not much else. With a CRS (Cloud Router Switch), there are two options. Switching on the other hand is a disaster, and for almost a month when I first had the CRS317, I was unable to even use the switch. I have even started replacing some of my VPSs with CHRs, just because it works so well. 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. The original file on the device was routeros-mipsbe-6.42.3.npk.I think anybody that’s ever used a Mikrotik and RouterOS can probably agree. The file I grabbed was routeros-mipsbe-6.42.5.npk. All others do not appear to contain a package file in their files list so I am assuming the primary wlc pushes the upgrade to the others? Haven't been able to find any documentation which confirms this. I also tried the upgrade through system/packages to the new version 6.42.7 and it downloaded but again, the system is not upgraded.Īm I missing something here? The only device with the package file is the primary wlc. I tried upgrading the routerboard as well with no luck. It did not come up on the new version but stayed on 6.42.3. Then, as per the instructions, I rebooted the box. Last night I downloaded the version from the MikroTik website and, using winbox, transferred it to the files area. This based on some reading I did on forums where the newer version corrected some issues we seem to be having. Using instructions I found on a couple of internet sites including the MikroTik site, I am trying to upgrade these from their current 6.42.3 to 6.42.5. I am able to connect to all devices either via https/http, ssh and winbox. All are attached via ethernet cables to cisco core switches. I have 2 RouterBOARD 3011UiAS acting as WLC's and 12 AP's hap ac RouterBOARD 962UiGS-5HacT2HnT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |