You are on page 1of 7

RouterBoard-specific functions

Document revision 3 (Wed Jul 06 11:26:35 GMT 2005)


This document applies to V2.9
Table of Contents
Table of Contents
Summary
Specifications
BIOS upgrading
Description
Property Description
Command Description
Example
BIOS Configuration
Description
Property Description
Example
System Health Monitoring
Description
Property Description
Notes
Example
LED Management or RB200
Description
Property Description
Notes
Example
LED Management on RB500
Description
Property Description
Fan voltage control
Description
Property Description
Console Reset Jumper
Description
General Information
Summary
There are some features used to configure specific functions exist only in RouterBOARD series embedded
routers:

B!OS upgrading

B!OS configuration
Page 1 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.

Health monitoring (RouterBOARD 200 series only)

LED control (may be used in scripting)

Fan voltage control (onfoff) (RouterBOARD 200 series only)

Console reset jumper (RouterBOARD 200 series only)


Specifications
Packages required: routerboard
License required: level1
Home menu level: /system routerboard, /system health
Hardware usage: works only on RouterBOARD platform
BIOS upgrading
Home menu level: /system routerboard
Description
The B!OS is needed to recognize all the hardware and boot the system up. Newer B!OS versions might have
support for more hardware, so it's generally a good idea to upgrade the B!OS once a newer version is
available.
The newest versions of B!OS firmware is included in the newest routerboard software package. B!OS
firmware may also be uploaded to router's FTP server (the file is called wlb-bios.rom). This way, for
example, B!OS firmware may be transferred from one router to an another.
Property Description
current-firmware (read-only: text) - the version and build date of the BIOS already flashed
model (read-only: text) - RouterBOARD model
routerboard (read-only: yes | no) - whether the motherboard has been detected as a
RouterBOARD
serial-number (read-only: text) - RouterBOARD serial number
upgrade-firmware (read-only: text) - the version and build date of the BIOS that is available for
flashing
Command Description
upgrade - write the uploaded firmware to the BIOS (asks confirmation, and then reboots the router)
Example
To check the current and available firmware version numbers:
[admin@MikroTik] system routerboard> print
routerboard: yes
model: 230
Page 2 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
serial-number: 8524983
current-firmware: 1.3.4beta7 (Nov/12/2004 17:12:58)
upgrade-firmware: 1.3.4beta7 (Nov/16/2004 17:02:35)
[admin@MikroTik] system routerboard>
To upgrade the B!OS version:
[admin@MikroTik] > system routerboard upgrade
Firmware upgrade requires reboot of the router. Continue? [y/n] y
Firmware upgrade can take up to 20s. Do NOT turn off the power!
BIOS Configuration
Home menu level: /system routerboard bios
Description
!n addition to B!OS own setup possibilities, it is possible to configure B!OS parameters in RouterOS condole
Property Description
baud-rate (1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: 9600) - initian
bitrate of the onboard serial port
beep-on-boot (yes | no; default: yes) - whether to beep during boot procedure (to indicate that it has
succeeded)
boot-delay (time: 0s..10s; default: 1s) - how much time to wait for a key storke while booting
boot-device (etherboot-ide | etherboot-only | ide-only | try-etherboot-once) - specifies from which
device the RouterBoard will boot
etherboot-ide - boot from etherboot, if it fails, boot from ide
etherboot-only - boot only from etherboot
ide-only - boot only from ide
try-etherboot-once - boot from etherboot once, then returns to previous settings
cpu-mode (power-save | regular; default: power-save) - whether to enter CPU suspend mode in
HTL instruction. Most OSs use HLT instruction during CPU idle cycle. When CPU is in suspend
mode, it consumes less power, but in low-temperatire conditions it is recommended to choose
regular mode, so that overall system temperature would be greater
debug-level (none | low | high) - BIOS output debug level
none - no debugging output
low - show only some debugging information
high - show all debugging information about the boot process
enter-setup-on (any-key | delete-key; default: any-key) - which key will cause the BIOS to enter
configuration mode during boot delay. Note that in some serial terminal programs, it is impossible
to use Delete key to enter the setup - in this case it might be possible to do this with the Backspace
key
etherboot-timeot (time; default: 1m) - how much time to wait for booting from ethernet
Page 3 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
memory-settings (fail-safe | optimal; default: auto) - SDRAM memory speed
optimal - the BIOS tries to determine the correct memory settings by itself
fail-safe - use if you have memory-related errors (generally random, not reproducible errors and
freezes). In this case, minimal timing parametrs are used, so most memory modules will work
reliably
memory-test (yes | no; default: no) - whether to testall the RAM during boot procedure. Regardless
of the choice, hte first megabyte of the RAM will be tested anyway. Enabling this option may cause
longer boot process
pci-backoff (enabled | disabled; default: enabled) - when enabled, external PCI masters can access
system memory even when a CPU cycle has been retried. If you are experiencing uncommon
problems with PCI/PCMCIA/CardBUS interfaces (including RouterBOARD is rebooting or
hanging up once in a while), try to disable it
vga-to-serial (yes | no; default: yes) - whether to map VGA output to the serial console. Should be
enabled if working via serial terminal (gives much more output)
Example
To set high debug level with RAN test:
[admin@MikroTik] system routerboard bios> print
baud-rate: 9600
debug-level: low
boot-delay: 00:00:01
enter-setup-on: any-key
beep-on-boot: yes
boot-device: ide-only
etherboot-timeout: 00:01:00
vga-to-serial: yes
memory-settings: optimal
memory-test: no
cpu-mode: power-save
pci-backoff: enabled
[admin@MikroTik] system routerboard bios> set debug-level=high
[admin@MikroTik] system routerboard bios> print
baud-rate: 9600
debug-level: high
boot-delay: 00:00:01
enter-setup-on: any-key
beep-on-boot: yes
boot-device: ide-only
etherboot-timeout: 00:01:00
vga-to-serial: yes
memory-settings: optimal
memory-test: no
cpu-mode: power-save
pci-backoff: enabled
[admin@MikroTik] system routerboard bios>
System Health Monitoring
Home menu level: /system health
Description
LN87 health controller chip provides some measurments of temperature and voltage on RouterBOARD 200
series computers. !nformation becomes available not sooner than 2 minutes after boot up. !t is not available
Page 4 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
if LN87 chip is not detected successfully. All values are 10 second averages, with short peak values ignored
as likely read errors
Property Description
3.3v - +3.3V power line voltage
5v - +5V power line voltage
board-temp - temperature of the PCI area
core - CPU core voltage
cpu-temp - temperature of the CPU area
lm87-temp - temperature of the LM87 chip
state (read-only: enabled | disabled; default: disabled) - the current state of health monitoring
(whether it is enabled or not)
state-after-reboot (enabled | disabled; default: disabled) - the state of the health monitor after the
reboot
Notes
You cannot change state on the fly, just control, whether the health control will be enabled after reboot
All themperature values are in Celsius degrees
Example
To check system health:
[admin@MikroTik] system health> print
core: 1.32
3.3v: 3.26
5v: 4.97
lm87-temp: -0.9
cpu-temp: -0.9
board-temp: -0.9
state: enabled
state-after-reboot: enabled
[admin@MikroTik] system routerboard health>
LED Management or RB200
Command name: :led
Description
The four user LEDs of the RouterBOARD 200 series can be controlled from user-space scripts.
Property Description
led1 (yes | no; default: no) - whether the LED1 is on
Page 5 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
led2 (yes | no; default: no) - whether the LED2 is on
led3 (yes | no; default: no) - whether the LED3 is on
led4 (yes | no; default: no) - whether the LED3 is on
length (time; default: 0s) - how long to hold the given combination
0s - no limit
Notes
The command does not imply a pause in execution. !t works asynchronously, allowing execution to continue
just after the command was entered, not waiting for LEDs to switch off.
After the given time (length property) the LEDs will return to the default (off) condition.
Any new :led command overrides the the previous state and resets the LED state after the length time
interval.
Example
To turn LED1 on for a minute:
[admin@MikroTik] > :led led1=yes length=1m
[admin@MikroTik] >
LED Management on RB500
Command name: /blink
Description
!t is possible to blink with the only user LED (the red one, near the blue power LED) of ROuterBOARD 500
series boards
Property Description
duration (time; default: 10s) - how long to flash the red LED
Fan voltage control
Command name: /system routerboard fan-control
Description
On RouterBOARD 200 series you can control, whether the J11 fan 5v voltage output is enabled. This feature
will only work with newest B!OS versions. This is useful in scripts to control some devices attached to the
J11 connector.
Property Description
Page 6 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
length (time; default: 0) - how long to hold the set state value, and then return to the prevoius state
0 - leave the state in the set mode until restart
state (yes | no) - whether to enable the 5V output on pins 1-2 of the J11 header
Console Reset Jumper
Description
The J16 jumper on the RouterBOARD 200 may be used as serial console reset pin. !f it held short for at least
10 seconds, then:

Serial console configuration is reset

Serial port that serial console will pick by default (usually serial0) is set to 9600 baud 8 bit 1 stop bit no
parity (default settings after installation)

Special flag that prevents any other program except serial console to acquire this port is set

Router is rebooted
Page 7 of 7
Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.

You might also like