RouterOS allows to configure each leds activity the way that user wishes. It is possible to configure the leds to display wireless strength, blink the leds on interface traffic activity and many other options.
For example default led configuration on Groove
[admin@MikroTik] /system leds> print Flags: X - disabled # TYPE INTERFACE LEDS 0 wireless-signal-strength led1 led2 led3 led4 led5 1 interface-activity ether1 user-led
RB Groove uses five leds for wireless strength and one for ethernet activity monitoring.
|disabled (yes | no; Default: no)||Whether item is disabled|
|interface (string; Default: )||Name of the interface which will be used for led status. Applicable only if type is interface specific.|
|modem-signal-treshold (integer [-113..-51]; Default: )||Applicable if type is modem-signal|
|leds (list of leds; Default: )||List of led names used for status report. For example wireless signal strength will require more than one led.|
|type (ap-cap| flash-access | interface-activity | interface-receive | interface-speed | interface-status | interface-transmit | modem-signal | off | on | poe-out | wireless-signal-strength | wireless-status; Default: )||Type of the status:
Global settings are stored in Leds Setting menu. Currently "RB cAP 2n" and "RB cAP 2nD" supports turning off all leds (LED dark mode).
/system leds setting
|all-leds-off (after-1h | after-1min | immediate | never; Default: never)||Whether and when all leds of router can be turned off|
Enable the User ACT LED to show current CAP status on a RB951
/system leds add leds=user-led type=ap-cap
Led control via CLI commands for scripting purposes:
- prior to v6.23 and older releases:
#turn led on :led led1=yes #turn led off :led led1=no
- v6.23 and newer releases:
#add led entry with specific type "on" or "off" to leds menu /system leds add leds=led1 type=off #to control led /system leds set [find where leds="led1"] type=on or /system leds set [find where leds="led1"] type=off