Maybe.Is it OK if I upgrade my RB each time when new upgrade release ?
If your RouterOS license, other policies, and hardware allows it.Is it OK if I upgrade my RB each time when new upgrade release ?
[admin@MikroTik] > /system license print
software-id: xxxx-xxxx
upgradable-to: v6.x
nlevel: 4
features:
Speed reading is a moment calculated reading. If you run a load over a long time you'll see the average goes below 100Mb.Strange behavior or of the interface speed graph.
x86 , ROS v5.6 , RealTeck 1G ethernet.
In some pik situation MT show speed which is more then 100Mbit/s, in same time showes some interrupts in graph.
Seriously, what kind of help are you expecting with this post?i've just updated to v5.6 yesterday, and now i got CPU resource load 100%. it's been hours like this
[...]
somebody help please before the router crash for overheating
reboot? Or power cycle? That sometimes helps. If issue comes back, downgrade reboot, power cycle, and upgrade again....
a lot. but nothing is changed on configuration.Winbox is not "management". What configuration you have on that router?
i'll do this in the morningreboot? Or power cycle? That sometimes helps. If issue comes back, downgrade reboot, power cycle, and upgrade again....i closed all active winbox already, nothing's changed. is there anything else i could check on?
thanks before
I just report that all remaining basestations and CPE:s where successfully upgraded from 4.17 to 5.6 without any problems.---------There is a bug with 4.1X when you try to reboot it shuts down instead, discovered this as usual the hard way when a weekly scheduled reboot resulted in routers shutting down, this is fixed in the 5.X series so i never reboot a 4.x series unless i am close by to re-cycle the power.Hello Folks!
We are also upgrading to 5.6 from 5.4 and 5.5, 4.17.
So far on RB411 (CPE) and RB333 (Routers), RB450G (Routers).
There has been some incidents, when upgrading RB450G and RB411 from 4.17 to 5.5 they never came back up on the network, visiting the router's we discovered that all ethernet leds were off but blue led was on. Fully dissconnect the power and put it back again solved the problem. Upgrading from 5.5 to 5.6 was not an issue.
Please MT, can you do something about the upgrade scenarios, like automatik failback, and automatik restart on previous firmware. Failsafe functions should be implemented like last known good and so on. Other devices we have do so, like our IBM AIX servers.
The devices should never be dead in water exeption is if there are hardware problems.
http://forum.mikrotik.com/viewtopic.php ... it=+reboot
http://forum.mikrotik.com/viewtopic.php?f=1&t=48518
Thanks!
We still have many ros4.17 RB411 CPE spread out over a wide area, hard to reach, upgrades are planned.
I've returned from my holiday now and started to discover what's wrong. I was not able to connect to SXT with 5.6, so I reset settings (using button) and SXT started to respond again (with default settings, of course). Then I tried to restore configuration - I lost SXT again.I've updated remote SXT and after reboot I lost it. Then I tried to update testing SXT which I have here - I lost it as well. No single packet from them - I tried to discover using WinBox, I tried to watch traffic using Wireshark, nothing. What's going on?
please make the support output file from v5.5 with your config, so we could check it. Also maybe make admin user without password and send us the backup file maybe we could try to reproduce it.I've returned from my holiday now and started to discover what's wrong. I was not able to connect to SXT with 5.6, so I reset settings (using button) and SXT started to respond again (with default settings, of course). Then I tried to restore configuration - I lost SXT again.I've updated remote SXT and after reboot I lost it. Then I tried to update testing SXT which I have here - I lost it as well. No single packet from them - I tried to discover using WinBox, I tried to watch traffic using Wireshark, nothing. What's going on?
So I tried to reset, downgrade to 5.5, restore configuration - everything is all right. Upgrade to 5.6 - lost. There is obviously something wrong with my configuration and 5.6. I am using bridge - ethernet and wireless are bridged together. Maybe there is something wrong with that in 5.6? I'm not sure and perhaps I will contact support.
Yes, I've sent you backup file, Ticket#2011081966000477, hoping you will be able to reproduce it.please make the support output file from v5.5 with your config, so we could check it. Also maybe make admin user without password and send us the backup file maybe we could try to reproduce it.
To finish this story: I've got response from support - problem is related to L2MTU and will be fixed for the next RouterOS release. So don't use L2MTU higher than 2020 in SXT with version 5.6.So it seems that problem is with L2MTU set to 2030. I can reset configuration, set L2MTU (not MTU!) to 2030 and connection is lost immediately. Perhaps I have not understood meaning of L2MTU well But why this was working in 5.5?
Well when MT say they cannot reproduce some of the on going disconnection issues in their test lab, effected users have sent in debug logs, we still await a solution from MT for this but it's your call to use NV2 in production it may work flawlessly for you or cause you problems, there is only one way to answer the question you have asked (test)Hello Folks!
Is NV2 now stable to use in production or is suggestion to wait still some releases of routeros ?
I still see lot of fuzz regarding disconnection issues with NV2.
Okey, i will give it a try in production on one smaller sector over the remaining weekend and possibly full next week to see how it behaves. The LAB tests here show good results in half year tests.Well when MT say they cannot reproduce some of the on going disconnection issues in their test lab, effected users have sent in debug logs, we still await a solution from MT for this but it's your call to use NV2 in production it may work flawlessly for you or cause you problems, there is only one way to answer the question you have asked (test)Hello Folks!
Is NV2 now stable to use in production or is suggestion to wait still some releases of routeros ?
I still see lot of fuzz regarding disconnection issues with NV2.
Hi ´steen´, as you could see in this forum, I had many issues with pre 5.6 releases and NV2. My whole network (+/- 250 radio's in 15km radius with 16 AP's) is now in 5Ghz upper band (200Mhz wide) working with NV2 and v5.6. I have no more disconnect issues like before that are NV2 related.Hello Folks!
Is NV2 now stable to use in production or is suggestion to wait still some releases of routeros ?
I still see lot of fuzz regarding disconnection issues with NV2.
Lets hope, we have had rock solid network for years using nstreme here, customers exoect that also in future. Our network is in middle of town and willages, looot of interference. Directional antennas everywhere carefully aligned and placed, that pays offHi ´steen´, as you could see in this forum, I had many issues with pre 5.6 releases and NV2. My whole network (+/- 250 radio's in 15km radius with 16 AP's) is now in 5Ghz upper band (200Mhz wide) working with NV2 and v5.6. I have no more disconnect issues like before that are NV2 related.Hello Folks!
Is NV2 now stable to use in production or is suggestion to wait still some releases of routeros ?
I still see lot of fuzz regarding disconnection issues with NV2.
Users still should understand though that NV2 needs better channel separation between competitive AP's working the same band and clients can at times having problems with interferences due strong signals from other working frequencies than its own. But if the channels (10Mhz!) are chosen with caution the network runs fine.....
With me it runs some 3 weeks now in all v5.6ROS + updated firmwares and it has been long (pre NV2 era!) that I had such a stable network as I have now...
Even the port flap issue still around is merely a ros notification issue than a real one. Although it is still wide spread over my network there seems to be not a single client noticing it. It only happens on Ethernet ports that are connected to 3rd party devices. I hardly see it between MT routers.
Maybe v5.7 might see some extra improvement here since it has improved Ethernet drivers (according newsletter) and hopefully the ´port flap´ issue has disappeared as well!
I use NTP client and Im not using NTP server. So only disabling the NTP package will do the work? NTP client will be still working?IIRC the graphing issue is related to the NTP server package taking too long to sync the system clock, and when the graphs are updated the time gap causes it to clear them. If you don't need the NTP server capabilities, using the simple NTP client rather than the separate package is supposed to avoid this. This has been reported by many people, so Mikrotik is aware of it, but sadly it seems to be a long, long way down their priority list.