MikroTik MTCNA lab 1 of 19
First access and the RouterOS command line
Log in to a brand-new RouterOS 7 router, learn the command line you will use in every other lab, give the router a name, a clock and a LAN address, then manage it from a browser with WebFig.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 3,328 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 01 - First access and the RouterOS command line
- Level
- Beginner
- Time
- About 45 minutes
- Nodes need
- 3 vCPU, 3,328 MB
- Smallest plan
- Lite
The scenario
Fernvale Networks looks after the IT for small businesses in the valley. A new customer, a bakery, has bought a MikroTik router, and your job today is the first visit: get into the router, find your way around RouterOS, give it a name and a LAN address, and prove you can manage it from the office PC.
The router is a Cloud Hosted Router (CHR), the virtual-machine edition of RouterOS. It runs exactly the same RouterOS 7 software as a hEX or a CCR, so everything you learn here applies to real hardware.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | ether1 | DHCP client (not connected today) | – |
| R1 | ether2 | 192.168.88.1/24 | Office LAN |
| Admin-PC | eth0 | 192.168.88.10/24, gateway 192.168.88.1 | Office LAN |
| PC1 | eth0 | 192.168.88.20/24, gateway 192.168.88.1 | Office LAN |
Topology: R1 ether2, Admin-PC and PC1 share the Office LAN switch.
What you’ll practise
- Log in at the console and replace the empty admin password
- Move around the RouterOS menu tree with /, .., Tab, ? and the command history
- Read system information: version, licence level, packages and interfaces
- Set the router identity, a login note and the time zone
- Add an IP address to an interface and test it from a PC
- Use WebFig from a browser and compare it with the CLI
- Export the configuration, and undo a change
The tasks
- Log in for the first time
- Find your way around the command line
- Name the router and add a login note
- Set the clock and time zone
- Address the LAN port
- Manage the router from a browser with WebFig
- Test from the office PC
- Look at your configuration, save an export and undo a change
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
ether2to Office-LAN (network) - Admin-PC
eth0to Office-LAN (network) - PC1
eth0to Office-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| Admin-PC | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCNA RouterOS v7 guided labs.Open
01 - First access and the RouterOS command lineand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More MikroTik MTCNA labs
Related labs in other courses
CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.