Jan 09, 2017 Software ID Change Frequently. Sun Dec 11, 2016 3:52 am. But after that we found, every 15 mins it reset user details and Software ID. Admin password reset to blank and other users removed. But my config remain same. We cannot take backup.
Updating MikroTik RouterOS
- You update using ssh / Winbox ⇢ New terminal using:
- Or from Winbox, press System ⇢ Packages ⇢ Check For Updates ⇢ Download&Install
- To manually update, you simply download the new software and with the mouse/pad drag the file to the Winbox file window. Then you reboot, and RouterOS automatically discovers the software and installs it before starting up. For home devices, put the software in the flash folder, otherwise it will be deleted at reboot. Be sure that you use the software version that matches your MikroTik devices chipset. The chipset is shown in parentheses in the top of the Winbox window, after the routers identity (name) - using the wrong chipset software might brick your router.
- You can use Netinstall.
- If you have many MikroTik devices you need to manage and update, you can use The Dude to update them in batches.
- Or you can add the different RouterOS images you want to use on a master MikroTik router, and set the other routers to use that router as the upgrade central.
See Winbox: System ⇢ Auto upgrade or use /system upgrade print
- You can script the updating, from your own proxy server, here is an example - also check the Wiki about scheduler.
Scheduled updating
If you want your router to update during the night, you can edit the date and use this script:
2 | /system scheduleradd name=Upgrade on-event='/system package update install' policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon |
This script will run each night and check if newrouteros.npk exists, and if it do, then reboot to upgrade:
2 4 6 8 | add comment='Check if newrouteros.npk exists. If found, then reboot to update.'interval=1dname= 'Reboot to update'on-event=':local filename 'newrouteros.npk'; r n:if ([:len [/file find name=$filename]] > 0) do={ r n :put 'New RouterOS package named newrouteros.npk found, will reboot in 60 seconds to install'; r n :put 'Rebooting now'; r n}'policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive start-date=nov/14/2012start-time= |
Read more on the wiki about Upgrading RouterOS.
Upgrade paths
Partitions
When upgrading, you always run a risk of getting unforeseen problems. A very convenient way to prepare for this, is to add extra partitions on the router. You may then upgrade the test partition, and if it do not work as expected, you can reboot into the untouched production partition.
If a partition completely fails for some reason (failed upgrade, problematic configuration introduced, software problem), the next partition will automatically boot instead.
Install extra partitions
- Check you have enough free space for the extra partition (/system resource print)
- Upgrade the firmware to latest (/system routerboard ... print ... upgrade ... /system reboot)
- Repartition to 2 partitions (PROD, TEST) or 3 partitions (PROD, QA, TEST) ... the router reboots when you change the number of partitions (/partitions repartition partitions=2). RouterOS automatically splits the partitions to even sizes, and you current partitions OS+config is untouched, as long as there is enough free space to split the NAND/Flash into the selected number of partitions.
- Copy part0 to part1 (/partitions copy-to partition=part1) ... copies both OS and config
- Activate part1 (/partitions activate 1)
- Set new part1 to boot on part0 on fail (/partitions set part1 fallback-to=part0)
You may also copy only the active configuration, without changing the OS version with: /partitions save-config-to partition=partX
And you may also restore config from another partition to the active partition.
And you may also restore config from another partition to the active partition.
If you need to test on remote devices, it may prove helpful to add a script that runs at start time and if not disabled manually, will activate the safe partition and reboot.
If repartitioning fails and automatic boot from a safe partition fails, you may:
- Connect with Netinstall
- Connect with a serial console cable and then in the RouterBOOT menu, press 'y' then 0/1 to activate the desired partition and boot on it.
More about partitions: https://wiki.mikrotik.com/wiki/Manual:Partitions
< Manual:IP
Applies to RouterOS: v5 +
Summary
MikroTik Neighbor Discovery protocol (MNDP) and LLDP allows to 'find' other devices compatible with MNDP or CDP (Cisco Discovery Protocol) or LLDP in Layer2 broadcast domain.
Neigbours
Sub-menu:
/ip neighbor
![Change Routeros Software Identity Change Routeros Software Identity](https://sovandara.com/wp-content/uploads/2016/11/5-25-2015-3-10-23-PM-1-800x445.png)
This sub-menu lists all discovered neighbours in Layer-2 broadcast domain. It shows to which interface neighbour is connected, shows its IP/MAC addresses and several MikroTik related parameters. List is read-only.
Starting from ROS v6.45 amount of neighbour entries are limited to (total RAM in megabytes)*16 per interface to avoid memory exhaustion.
As an example, you can see several RouterBoards and two Cisco routers:
Properties
Property | Description |
---|---|
address (IP) | Highest IP address configured on a discovered device |
address6 (IPv6) | IPv6 address configured on a discovered device |
age (time) | Time interval since last discovery packet |
board (string) | RouterBoard model. Displayed only to devices with installed RouterOS |
identity (string) | Configured system identity |
interface (string) | Interface name to which discovered device is connected |
interface-name (string) | Interface name on the neighbor device connected to the L2 broadcast domain. Applies to CDP. |
ipv6 (yes | no) | Shows whether device has IPv6 enabled. |
mac-address (MAC) | Mac address of remote device. Can be used to connect with mac-telnet. |
platform (string) | Name of the platform. For example 'MikroTik', 'cisco' ... etc. |
software-id (string) | RouterOS software ID on a remote device. Applies only to devices installed with RouterOS. |
system-caps (string) | System capabilities reported by the Link-Layer Discovery Protocol (LLDP). |
system-caps-enabled (string) | Enabled system capabilities reported by the Link-Layer Discovery Protocol (LLDP). |
unpack (none|simple|uncompressed-headers|uncompressed-all) | Shows discovery packet compression type. |
uptime (time) | Uptime of remote device. Shown only to devices installed with RouterOS. |
version (string) | Version number of installed software on a remote device |
Discovery configuration
Sub-menu:
/ip neighbor discovery-settings
In this menu, it is possible to change the state of the interface whether it participates in neighbor discovery or not. If it does, it will send out basic information about system and process received discovery packets broadcasted in Layer-2 network. List of interfaces is automatically managed by RouterOS. Items in the list cannot be removed nor added. Default settings depend on interface type and current state.
Removing an interface from this menu configuration will disable both the discovery of neighbours on this interface, and also the possibility of discovering this device itself on that interface.
Since RouterOS v6.44 a neighbor discovery is working on individual slave interfaces. Whenever master interface (e.g. bonding or bridge) is included in the discovery interface list, all its slave interfaces will automatically participate in neighbor discovery. It is possible to allow neighbor discovery only to some slave interfaces. To do that, include the particular slave interface in the list and make sure that the master interface is not included.
The neighbor list now shows a master interface and actual slave interface on which a discovery message was received.
Properties
Property | Description |
---|---|
discover-interface-list (string; Default: !dynamic) | Interface list on which members the discovery protocol will run on |
LLDP
RouterOS sends out:
Chassis subtype (MAC)
- Port subtype (interface name)
- TTL
- System name (system identity)
- Sys description ({platform} RouterOS {osvers} {boardName})
- All IP addresses configured on the port
RouterOS accepts and processes:
- identity (LLDP_TYPE_SYS_NAME)
- interfaceName (depending on the priority, if one is empty checks the next: LLDP_TYPE_CHASSIS_ID, LLDP_TYPE_PORT_ID, LLDP_TYPE_PORT_DESC)
- ip4 (first entry of IPv4 LLDP_TYPE_MANAGEMENT_ADDR)
- ip6 (first entry of IPv6 LLDP_TYPE_MANAGEMENT_ADDR)
- TTL (LLDP_TYPE_TTL)
- MAC (Source - 6-11 byte)
[Top | Back to Content]
Retrieved from 'https://wiki.mikrotik.com/index.php?title=Manual:IP/Neighbor_discovery&oldid=33545'