Manual:Virtualization: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
No edit summary
Line 55: Line 55:
[[Category:Manual]]
[[Category:Manual]]
[[Category:Virtualization]]
[[Category:Virtualization]]
[[Category:Case Studies]]

Revision as of 14:37, 12 March 2010

Applies to RouterOS: 3, v4

RouterOS has three different Virtualization implementations. Choose your topic:


Metarouter

Metarouter is created by MikroTik and currently is supported only on RouterBOARD 4xx series (mips-be) and RB1000 series (powerpc). Currently Metarouter can only create RouterOS virtual machines.

We are planning to add more features to Metarouter, so that it will even exceed Xen in functionality. New hardware support will also be added to Metarouter

Xen

Xen is based on the Linux Xen Virtual machine project, and current RouterOS implementation is supported only on RouterOS X86 systems (PCs). Xen can create Virtual machines of different Operating Systems that supports Xen.

Kvm

Kvm is based on Linux Kvm virtualization software and requires your CPU to support virtualization. Kvm is available only on x86 systems.

Usage Examples

The following are just a few of possible scenarios where virtual machines could be used (some of these currently are possible only in Xen, but Metarouter features will be expanded to allow even more functionality):

In the datacenter

  • consolidate a number of routers on one hardware platform
  • consolidate routing services and higher levels services such a VOIP switches in the same box
  • use a guest machine on top of a router for custom features such as accounting, LDAP or legacy networking
  • redundant routers much easier and cheaper to have available in case of crashed systems

In the hosting center

  • use RouterOS and extensive networking features as a host with a server (mail, http, ftp...) running as guest or multiple guest virtual machines
  • offer virtual routers with VPN solutions that give a network administrator customer his own router on a highspeed backbone to make any kind of tunneled intranet or simply VPN access system

At the wireless ISP client site

  • set up two isolated routers and set the wireless control only for the router controlled by the WISP while the Ethernet side router is fully under the clients control

At multiclient sites (such as office buildings)

  • in locations serving multiple clients by Ethernet from one backbone connection (wired or wireless), give each customer control over his own isolated virtual router

For network planning and testing

  • build a virtual network on one box with the same topography as a planned network and test the configurations so that the fine tuning of the configurations can be done in the lab and not in the field, simulate and monitor the network with advanced scripting and The Dude network monitor utility

In custom applications

  • develop your own programs (and even Linux distributions) that can be installed on MikroTik supported platforms with minimum difficulty as software patches and virtual drivers are provided for guest systems
  • use low cost RouterBOARD embedded systems easily with your own Linux and the advantage that it will work across all RouterBOARDS with the same CPU