Community discussions

 
SnakeSK
just joined
Topic Author
Posts: 16
Joined: Fri Mar 09, 2018 1:30 am

Warning before installing CHR 6.42.1 on Hyper-V

Thu Apr 26, 2018 12:04 pm

Setup:

Windows Hyper-V Server 2016
LACP Network Team through 4 NICs
4 Network adapters (1 untagged, 3 tagged)

After upgrading to 6.42.1 system locks up after couple of hours, WAN (VLAN 2) stays on, LAN (VLAN 1) refuses to communicate, after another hour system loses connectivity completely, IPsec drops completely, routing doesn ´t work anymore.

I suspect this is due to Hyper-V integration services being added.

Had to revert back to 6.41.4

Successfully reproduced on 4 systems, this build is broken, stay away from it.
 
hack520
just joined
Posts: 2
Joined: Thu Apr 26, 2018 4:48 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Thu Apr 26, 2018 4:50 pm

yes,6.42 there is a serious bug in hyperv. After a period of time, the network is disconnected and resumed after resumption. I have restored snapshot to 6.41.4..
 
hack520
just joined
Posts: 2
Joined: Thu Apr 26, 2018 4:48 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Thu Apr 26, 2018 5:09 pm

I also encountered the same problem, after win2012r2 hyperv, ros run some time, wan disconnected, lan normal, and finally all disconnected, reboot ros returned to normal. I am having the same problem on multiple servers and I think that 6.42 is not perfect on hyperv (integration service related). I have recovered the snapshot to 6.41.4. Everything works fine.
 
SnakeSK
just joined
Topic Author
Posts: 16
Joined: Fri Mar 09, 2018 1:30 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Fri Apr 27, 2018 7:04 pm

So it is widespread, thank you guys, filed a support request with supout file
 
total13
newbie
Posts: 29
Joined: Fri Jul 08, 2016 2:29 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Wed May 09, 2018 6:28 pm

I came here to find if there is some bug, we have had 3 devices already cut off from network. Devices seem to be "pingable" from local network, but reboot solves issue. Also do not know if it is related, but we had 2 devices loose interface data - interface name reverted to default perhaps. (IP addresses detached from interfaces when they lost interface name)
 
BrettH
just joined
Posts: 10
Joined: Thu Nov 16, 2017 10:13 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Mon May 14, 2018 8:42 am

We have interfaces dying on us on Hyper-V since the 6.42.1 update,

Avoid 6.42 on Hyper-V right now.
Last edited by BrettH on Wed May 30, 2018 3:53 am, edited 1 time in total.
 
total13
newbie
Posts: 29
Joined: Fri Jul 08, 2016 2:29 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Mon May 14, 2018 3:15 pm

Any update planned for this issue?
 
Kindis
Member Candidate
Member Candidate
Posts: 195
Joined: Tue Nov 01, 2011 6:54 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Tue May 15, 2018 9:38 am

For you that have this issue what guest servies have you activated? Are all activated including Dynamic Memory?
I wonder if this issue goes away if you disable all services including dynamic memory.
 
SnakeSK
just joined
Topic Author
Posts: 16
Joined: Fri Mar 09, 2018 1:30 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Tue May 15, 2018 9:08 pm

No, no dynamic memory.
 
nickdwhite
just joined
Posts: 10
Joined: Thu Jun 22, 2006 11:41 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Wed May 16, 2018 11:07 pm

For you that have this issue what guest servies have you activated? Are all activated including Dynamic Memory?
I wonder if this issue goes away if you disable all services including dynamic memory.
I had all guest services disabled and still experienced the issue. Leaving all production Hyper-V CHR on 6.40.8 for now which is stable.
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6610
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: Warning before installing CHR 6.42.1 on Hyper-V

Thu May 17, 2018 1:22 pm

Thank you very much for your reports.
Please provide us with support output files, when you are experiencing issues with interfaces on your CHR.
Currently we got some files, but they do not contain enough information for us, so we can work on fix faster.
 
total13
newbie
Posts: 29
Joined: Fri Jul 08, 2016 2:29 pm

Re: Warning before installing CHR 6.42.1 on Hyper-V

Wed May 23, 2018 12:13 pm

Hello,

I can confirm 6.40.8 is stable on all but one device I plan to replace today. I will remove it from production and upgrade it to 6.42.1 to try to get more spout files.

I have watchdog enabled and it reboots device whenever it looses connection but for some reason it never sends spout via mail (although it might be due to connection loss-but I have simulated loss of ping with firewall rule and it still rebooted without sending spout in mail)
 
User avatar
Clevelus
just joined
Posts: 2
Joined: Wed May 23, 2018 3:17 pm
Contact:

Re: Warning before installing CHR 6.42.1 on Hyper-V

Wed May 23, 2018 3:33 pm

Completely similar problems :(
CHR on Hyper-V (on VMM SCCM Networks)
Both on firmware 6.42.1 and on firmware 6.42.2.
Only the change of the update channel from current to bugfix has helped.
Firmware 6.40.8 works stably.

When can we expect a correction of the situation?
 
SnakeSK
just joined
Topic Author
Posts: 16
Joined: Fri Mar 09, 2018 1:30 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Mon May 28, 2018 11:54 pm

Any new info from mikrotik? they didnt even replied to me when i sent them the supout
 
BrettH
just joined
Posts: 10
Joined: Thu Nov 16, 2017 10:13 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Wed May 30, 2018 3:52 am

I emailed Mikrotik support a supout file for the issue today, with a lengthy description of our setup. Will see how we go.
 
User avatar
maxrate
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Mon Oct 23, 2006 10:55 pm
Location: Toronto

Re: Warning before installing CHR 6.42.1 on Hyper-V

Sat Jun 02, 2018 4:46 pm

Hello - I am writing to confirm that I too seem to be experiencing this issue. I have submitted a support.rif to Mikrotik. Running 6.42.3 CHR

I find if I take any of the following actions: /system restart, Hyper-V shutdown the guest OS, Hyper-V pause then resume the guest OS - network connectivity is then restored. I am running Windows 2012 R2 Datacentre edition on Lenovo RD550 servers with the 4 port Intel I350 Interface adapter on the mezzanine finger interface on the rear of the unit. The interface is going thru a hyper-v virtual swtich, connected with a physical ethernet port on the server.

I have tried enabling MAC spoofing on the guest OS, added VLANs, removed VLANs, etc - trouble persists. I have NOT tried manually deselecting integration services offerings to the guest OS (CHR) at this time. (Customer already super upset!) I have not found a pattern as to what triggers this.

I have this problem on a few servers right now.
Mikrotik everywhere!
 
BrettH
just joined
Posts: 10
Joined: Thu Nov 16, 2017 10:13 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Mon Jun 04, 2018 6:16 am

I emailed Mikrotik support a supout file for the issue today, with a lengthy description of our setup. Will see how we go.
Update: Three business days (5 Days) without a human response.

I'm getting the impression that Mikrotik either:
A) Don't care.
B) Don't have any idea what the problem is.
 
strods
MikroTik Support
MikroTik Support
Posts: 1346
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: Warning before installing CHR 6.42.1 on Hyper-V

Tue Jun 05, 2018 3:24 pm

RouterOS version 6.43rc23 just have been released. It involves CHR related fixes that might resolve problems mentioned within this topic.
 
BrettH
just joined
Posts: 10
Joined: Thu Nov 16, 2017 10:13 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Tue Jun 12, 2018 12:15 pm

RouterOS version 6.43rc23 just have been released. It involves CHR related fixes that might resolve problems mentioned within this topic.

We applied 6.43rc23 to a couple of hAPs and a handful of Hyper-V CHRs in response to advice issued by Mikrotik Support. In all instances, the CHRs ended up even more broken then they were before, failing to detect anything other than a single interface despite several interfaces being present. We tried to debug why this was occurring, but couldn't figure it out.

I think I preferred the "periodic breaking of interfaces" feature that headlined v6.42, at least I could write a script to resolve that automatically... Could we return?
 
SnakeSK
just joined
Topic Author
Posts: 16
Joined: Fri Mar 09, 2018 1:30 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Fri Jun 15, 2018 1:10 am

Oh god, im so glad i didnt upgrade. I have no room to experiment with production devices, yet mikrotik puts head in the sand instead of proper testing and fixing the 6.42 branch.

Staying on 6.41, we’ll see in the following months if we’ll replace these with ciscos, better to have an expensive working product thank cheap nonworking one
 
strods
MikroTik Support
MikroTik Support
Posts: 1346
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: Warning before installing CHR 6.42.1 on Hyper-V

Fri Jun 15, 2018 10:23 am

If your CHR does detect only single interface although it should detect more, then increase RAM assigned for this CHR, reboot and see if problem is resolved.
 
BrettH
just joined
Posts: 10
Joined: Thu Nov 16, 2017 10:13 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Thu Jun 21, 2018 2:36 am

If your CHR does detect only single interface although it should detect more, then increase RAM assigned for this CHR, reboot and see if problem is resolved.

The CHR has 128 MB of RAM, which is the requirement specified at https://wiki.mikrotik.com/wiki/Manual:CHR

Do you mean to suggest that it's no longer possible to run CHR on Hyper-V with 128 MB of RAM, and that the minimum requirements have surreptitiously increased with v6.42 / v6.43?
 
User avatar
vecernik87
Member Candidate
Member Candidate
Posts: 235
Joined: Fri Nov 10, 2017 8:19 am

Re: Warning before installing CHR 6.42.1 on Hyper-V

Thu Jun 21, 2018 2:44 pm

Interesting. Lucky me :D I didn't even notice that there is such memory limit. Fortunately everything works. (Host system is actually ordinary win10pro x64). Seems it is not happening everywhere so it may be harder to debug and fix.
You do not have the required permissions to view the files attached to this post.

Who is online

Users browsing this forum: Markut, mkx, redalg and 44 guests