Page 2 of 2

Re: CHR feature requests

Posted: Thu Jan 10, 2019 6:27 pm
by TomjNorthIdaho
CHR feature request

--> Mikrotik , I could really use an ISO image of a CHR so that I can install CHR on a bare metal box (just like x86 ROS).

Info :

- x86 ROS is available as an ISO that can be installed on a bare metal box. All CPU's are available to the x86 ROS system. The problem is that it is 32-Bit

- CHR ROS (64-bit) is only available as a disk image to be copied into a hypervisor system ( in my case a VmWare ESXi hypervisor ). The problem is that there are no free and popular hypervisors (that I know of) that will present greater than eight ( 8 ) CPUs to the guest hosted CHR ROS system. So your options are 1, use 8 CPUs on your CHR or 2, purchase a very expensive hypervisor license ( 100 K ? or so ) so that the hypervisor can then permit a CHR to run with greater than 8 CPUs. Example - a high end bare metal box with two Xeon 56 core processors could yield 112 Xeon processors to a CHR (without hyper-threading enabled). - - - Now you could have as many firewall rules and connections as you want and probably almost never bog down the layer-3 throughput. Also , a bare metal CHR with two Intel® Xeon® Processor E7-8890 v4 processors would yield 24 CPU cores and 120 Meg of CPU cache - thus a CHR could run at full CPU cache clock speed instead of the slower RAM speed for crazy fast CHR throughput.

In my network, I have a CHR with multiple 10-Gig interfaces performing bandwidth management on a dozen class C networks to customers averaging up to almost 150 thousand firewall connections. I suspect a bare metal CHR would increase firewall bandwidth processing yielding an additional 500 to 1,000 percent (or greater) CHR throughput.

Re: CHR feature requests

Posted: Thu Jan 10, 2019 8:16 pm
by pe1chl
Can't you just boot from a Linux Live CD and then use that to dd the disk image to the physical disk?

Re: CHR feature requests

Posted: Fri Jan 11, 2019 8:53 am
by raystream
you cant just copy the image to a disk. it is a container for the hypervisor and uses only virtual devices without drivers for the baremetal server.

But you are talking about using a server with so much cores and ram and cant afford an esc licence for around 800€ per CPU?
The Server is abaout 3000€ with 2 sockets just add 1600€ esx licence.
if you are running a business this should not be a problem.

Re: CHR feature requests

Posted: Fri Jan 11, 2019 6:20 pm
by TomjNorthIdaho
My thoughts on possible methods to get CHR running on a bare metal box . . .

- I believe a CHR does have IDE drivers to directly manage/talk to an IDE hard disk controller and IDE drives. I'm pretty sure a CHR does not have any SCSI, SAS, SATA support/drivers. Sooo #1 a bare metal box might have to be IDE hard disk based.

- CHR does have support for Intel E1000e and E1000 network cards. FYI - there are no physical vmxnet-3 network cards , all vmxnet-3 ethernet interfaces only live in a virtual world. Sooo #2 a bare metal box might have to have Intel E1000e and/or Intel E1000 physical network card interfaces.

Building a physical bare metal box with IDE drives and Intel E1000e networks cards at this point is pretty easy.
The hard part is moving a virtual CHR file system on a virtual IDE disk drive to a physical bare metal IDE hard disk drive and keeping the boot information and CHR linux file system identical so that a CHR ROS system can boot on the bare metal system. This procedure is slightly beyond my knowledge at this time.

However , I do know that a virtual CHR file system can be mounted under a virtual Linux system. I have done this with both 32-Bit x86 ROS and 64-Bit CHR ROS. I've already done this a couple of times to examine the Mikrotik x86/CHR Linux file systems on some virtual ROS systems. What I don't know is a possible procedure to dd a CHR virtual file system to a physical IDE hard disk and what may be needed to get it to boot on the physical bare metal box. I am guessing this should be an easy process to follow if a person was to follow some instructions.

With all of the above teckie steps to attempt to get a CHR running on bare metal, I can only assume it would be much much much easier if Mikrotik just came out with a CHR ISO so that it would be easy to install CHR on a bare metal system (just like x86).

Had anybody ever attempted building a bare metal CHR ?

Re: CHR feature requests

Posted: Wed Jan 30, 2019 10:52 am
by enzain
Why not possible use hw ROS with CHR licensing model?

This is not correct.

I can give wh and install free ESXi, and use CHR, why Mikrotik can't just change licensing model?