Still unable to boot on IBM servers. http://forum.mikrotik.com/viewtopic.php?f=2&t=29078

Normis, as we discussed in early posts (also ref. http://forum.mikrotik.com/viewtopic.php?f=2&t=28587) , since 3.5 all IBM servers are unable to boot (in my case, blade HS21XM): I see i am not the only one that have this problem. I have opened several tickets, sent several supout, sent several s...

There's high chanche that the problem is not MT related. When you remove entries from ARP table, you are also refreshing Layer2 Swicthes paths and MAC table, because your rotuer will send a broadcast to which the clients respond and swicthes learn the destination port again. So your problem can eith...

Yes, but this is not the case. The board can perfectly boot from this USB 4GB drive, as even ROS 3.4 boots correctly. Starting from 3.5, to boot from USB drive, I had to add one more drive (like a sas or scsi disk, even if not supported on ros). If I do that, it will boot correctly *from* USB. My gu...

Hello, On 3.17, i did not experienced clocking issue yet. Uptime is 4 days and two main problems with multi cpu did not appeared yet: - Clocking - full cpu usage after few hours I am running a 4 core Intel Xeon on IBM HS21XM. So i presume those two problems were a side effect of something that have ...

It looks like everyone experiencing these problems have motherboards with Intel 5xxx Chipset.
For istance, I am using an IBM HS21XM blade server which has a Intel 5000P Chipset.

Am I wrong?

Tested 3.16 and still have 100% CPU. On my system, this happens after 10-14 hours of uptime. Stepped back to 3.13.

I found the same problem on all IBM servers (including HS21 blade) since version 3.4.
What you have to do to boot is to add a second boot device (a second sata drive will be ok). Don't ask me why, it's odd i know. I opened a ticket with support in april, but we haven't made much progress.

bye

I'm seeing the exact same problem since upgrading from 2.9.49 to 3.11 in July. It seems like 3.14 improves somehow the situation a little bit, but we still see some pages not fully loaded and a lot of timeouts.