.
My idea to also create the supout file before the reboot was to “prove” the config, that was there minutes before, simply vanished, and that all was simply caused by a reboot. While I can’t say the reboot is the culprit, it’s very clear to us that a single reboot (that shouldn’t be a big deal) at least makes the problem presents itself. As I had experienced that a few times before, I was prepared to “prove” what’s going on. Instead of showing the “after” config and reporting what’s missed, I created both (before and after) and now even the own Dev Team can compare configs, side by side, and see what’s missing. That was my idea of generating both files, before and after reboot, because I was already expecting something to dissapear and, with both, comparing them would be trivial and stronger than just believing in my words that something went wrong.
I really don’t know if that’ll help on the solving itself. But I expect that’s hard to question it’s really happening, given the mayhen caused by a simple reboot on a config that was fully working 2 minutes ago. For that, I really believe having both files was a success.
And at the meantime, I have downgraded the few boxes I had upgraded to 7.1.1 back to 6.49.2. There’s really no way I can afford to “lose” connectivity to remote located boxes. I’ll personally give ROS7 a few more months of maturing. There’s no question the evolution from ROS6 to ROS7, but I can’t afford taking this risk.
I just upgraded a RB1100AHx4 to 7.1.1 -- on reconnection after reboot I see a warning that I don't have a key:
I thought it might be a weird 7.1.1 glitch -- the other two RB1100AHx4's I've upgraded were running 7.1 not 7.1.1 - so I tried a downgrade to 7.1 -- no luck, same message:
You have 14h18m to configure the router to be remotely accessible,
and to enter the key by pasting it in a Telnet window or in Winbox.
Turn off the device to stop the timer.
See www.mikrotik.com/key for more details.
Current installation "software ID": C67I-7SHJ
Please press "Enter" to continue!
Good afternoon.
Has anyone tried using chr-7.1.1 in EVE-NG?
When I created a node, the sequence of mac-addresses of interfaces was mixed up. In version 6.48.6 everything is fine.
Mikrotik answer on the dissapering config items on reboot couldn’t be more frustrating … boxes were working for years, problems started (as reported) right after upgrading to ROS7. Others are also complaining of similar problems. But more than not acknowledging the problem, Mikrotik just wants me to reinstall the ROS7. As said, I have already downgraded, will wait ROS7 get really mature.
.
Hello,
Your described configuration loss and long creation of supout file, may be due to disk errors, Please save your configuration and then perform Netinstall on this device to fix disk errors, after that reconfigure and monitor, if same issue appears again let us know.
I can already assure you that this will not help! If anything, my problem has STARTED after I did that (I reinstalled and cleared the config and imported it from a saved export, from that time I am losing the ipsec identities after every reboot)…
.
At the end, I just lost my time trying to create supout files to help. Will just stay at ROS6 until Mikrotik dev team solves this SEVERE problems on ROS7.
I am using router hEX - 750 GR3, when I upgrade RouterOS version v7.1.1 (stable) or RouterOS version v7.2rc1 (testing), error occurs as shown below.
Bandwidth test is not full speed 1 Gbps on total Tx/Rx Current, even when I am using bonding ethers with command “send” or “both” , but before that I use RouterOS version 6.48.6 (long-term) this is not the case.
I have tried to reset configuration (back to default) and reconfigure step by step, but the situation is still not fixed.
Is RouterOS v7 not good support for old model routers, specifically architectures: MMIPS, MIPSBE ?!!
I think I just got this “ROUTER HAS NO SOFTWARE KEY” problem on an RB941-2nD. Before the device went offline, it showed 7.1.1 (Level 0) via snmp. I have to check tomorrow.
If this pisses you off so much, why don’t you downgrade your very important router to 6.49 and wait for v7 to stabilise enough to meet your operational demands?
hi!
after using the CHR for a while on hyper-v, I have upgraded to the all new CHR7.1 stable.
so far so good. the only thing am missing is, I am unable to uninstall functionality’s which i do not use.
I tried uninstalling wireless, hotspot IPV6 but there is no option to do this under the packages in system menu.
am I finding them in a wrong menu? or Mikrotik 7.1 is made to stay with all this options.
Yes, unfortunately this possibility was removed by putting the entire RouterOS except some really niche functions in one big package.
I agree that was good for some low-level functions like dhcp,ppp,security,ipv6 etc that have lots of inter-dependecies, but frankly I think wireless and hotspot do not belong there.
Nothing we are going to change about that…
I am writing to advise of a problem I encountered with a CCR1009-8G-1S-1S+ that was upgraded to v7.1.1. I received a call from the client that their Vonage VOIP service was not working. At first I thought it was a problem with the Vonage VTA adaptor and I proceeded to replace it with a spare. After doing so, the problem remained and the two numbers associated with the Vonage service would not register (could not be provisioned). I tried a variety of things such as disabling the SIP helper, adding NAT rules for TCP/UDP 5060 and nothing worked. I then took the VTA adaptor to a different location on another network and found that it worked immediately. This was very odd. I took the adaptor back to the office and plugged it into the CCR and again, the numbers would not register. After tearing my hair out with a very unhelpful Vonage support person, I proceeded to downgrade the CCR back to 6.49.2 and on the subsequent reboot the Vonage VTA immediately started working. I have no explanation for this, but there must be some issue with 7.1.1 and SIP with the CCR1009.
EDIT: My problem is the same as that of post #281 as I also have a WAN over PPPoE VLAN connection on this CCR.
Stabilize ?
Stable version = Stabilized Version, right ?
I am with ccr2004 with random reboot issues from nearly 1.5yrs, no fix till now, there is whole topic going on.
Support asked spout, I gave, nothing in that spout, then support asked spout via serial cable with watchdog disabled, which means router will not reboot, i need manual reboot, router was in remote location, I cant do that., but others did and support find nothing in it. 1.5 yrs, same situation.
They released half baked 7.1.1 as stable 7.1.1, which is not stable at all. its not even alpha capable, forgot beta release.
7.1.1 is rebooting for all ccr1009 users, there are lot of complaints about cpu going nuts.
So, its obvious that users will get pissed.
Wrong. If you can’t afford downtime or are not willing to chase bugs, then
closely follow discussions on this vivid forum to assess general opinion on stability of a particular version on your particular hardware
create lab setup where you can test and verify both upgrade procedure and fitness for your particular setup and if not satisfied, go back to #1
Nothing that software producer states about some particular release shouldn’t make you skip any of steps above, it can only intrigue you into looking at some particular release more closely.
