Let’s say I have two switches connected through an uplink port.
Then I give to both bridges swith an ip of the same class.
If I connect my pc to one of these switches and then I launch winbox, I can discoverer in neighbors only the switch that is connected directly on the pc, not the other one, but If I manually insert the IP of the second switch I can connect, so it is not a connection problem, it just the discovery.
Is there a way to discover both switches passing from the bridges’s IP, without using a dedicated management port? This is usefull because winbox is showing the version of routerOS in a dedicated coloumn, so If I have a lot of hardware I can check what is outdated.
A really strange thing is that if I leave winbox opened for some times like 5 or 6 minutes, then the second switch will appear in the list.
Device discovery is done through broadcast frames … so if management interfaces of switches are in same L2 broadcast domain, autodiscovery should work (unless there’s some filtering involved on switches them selves). IP is routed which means that discovery of devices on different segment is not possible (connectivity is).
There are many different solutions to this problem and which one is the best greatly depends on topology of your network … both L2 (ethernet/VLAN) and L3 (IP). Based on information you provided so far it’s impossible to say which solution would work best for you.
The schema is a little more complex from the question that I posted, so it looks like this
The first two switches are my top of rack in an MLAG configuration, the other three switches are essentialy for the LAN of the office(servers, workstations, ip phones etc). What I want is to manage all switches from any eth port present in the diagram.
For the moment the only solution I found is to connect the management port of each switch into the third switch and add an IP to the bridge of the third switch. It works but I have to sacrifice a lot of ports for this setup.
One important thing is that the setup is more complex then this, cause the TOR configuration is not just for the LAN that I described above, but there are multiple VLANs for differente kind of traffic, like proxmox ceph, proxmox cluster, and other stuffs.
So essentialy in this diagram the TOR ports are all in the same bridge VLAN with id 300, and all other swithces have a bond vlan interface with id 300 in the same bridge with all the other ports
Just to clarify
As I wrote in the First post, If I put my PC in any port of the switches I can manage through winbox all the switches but I have to insert the IP manually, what I want is to Discovery the devices through neighbors list.
Dear, the First post was about a really simple schema, cause I can reply the same problem at a very basic level, furthermore from my POV since I’m not a mikrotik Expert, even the complete diagram doesn’t looks so super Advance Setup.. any way I added a Just to clarify at the end of the diagram post to reply to your suggestion.
