{{Warning|This manual is moved to https://help.mikrotik.com/docs/display/ROS/Neighbor+discovery}}
__TOC__
__TOC__
==Overview==
==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.
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.
This sub-menu lists all discovered neighbors in Layer-2 broadcast domain. It shows to which interface neighbor is connected, shows it's ip/MAC addresses and several Mikrotik related parameters. List is read-only.
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:
As an example, you can see several RouterBoards and two Cisco routers:
Line 28:
Line 32:
'''Properties'''
'''Properties'''
{{Mr-arg-table-h
{{Mr-arg-table-h
|prop=Property
|prop=Property
Line 99:
Line 101:
|type=string
|type=string
|desc=RouterOS software ID on a remote device. Applies only to devices installed with RouterOS.
|desc=RouterOS software ID on a remote device. Applies only to devices installed with RouterOS.
}}
{{Mr-arg-ro-table
|arg=system-caps
|type=string
|desc=System capabilities reported by the Link-Layer Discovery Protocol (LLDP).
}}
{{Mr-arg-ro-table
|arg=system-caps-enabled
|type=string
|desc=Enabled system capabilities reported by the Link-Layer Discovery Protocol (LLDP).
}}
}}
Line 119:
Line 134:
|desc=Version number of installed software on a remote device
|desc=Version number of installed software on a remote device
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.
In this menu is possible to change 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.
{{Mr-arg-table-h
<pre>
|prop=Property
/interface bonding
|desc=Description
add name=bond1 slaves=ether5,ether6
}}
/interface list
add name=only-ether5
{{Mr-arg-table
/interface list member
|arg=comment
add interface=ether5 list=only-ether5
|type=string
/ip neighbor discovery-settings
|default=
set discover-interface-list=only-ether5
|desc=Short description of an entry
</pre>
}}
{{Mr-arg-table
|arg=disabled
|type=yes {{!}} no
|default=
|desc=Whether item is disabled and do not participate in sending/receiving of discovery information. Added in v5.x
}}
{{Mr-arg-table-end
|arg=discover
|type=yes {{!}} no
|default=
|desc=Whether to participate in sending/receiving of discovery information. Since v5.x left for compatibility with older scripts.
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
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:
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.
/interface bonding
add name=bond1 slaves=ether5,ether6
/interface list
add name=only-ether5
/interface list member
add interface=ether5 list=only-ether5
/ip neighbor discovery-settings
set discover-interface-list=only-ether5
The neighbor list now shows a master interface and actual slave interface on which a discovery message was received.
