Mikrotik RB5009 paired with Ruckus ICX7150 for VLAN configuration
Mikrotik RB5009 paired with Ruckus ICX7150 for VLAN configuration
Change the DHCP server management VLAN to Management_Bridge and remove the DHCP relay from that interface. Keep the 192.168.99.1/24 entry on the switch. Include the "Management" VLAN interface on the management bridge. At this stage, devices on eth0 and VLAN 99 switches should communicate via DHCP and ping. If not, adjust the management VLAN settings for STP or RSTP as needed. Verify with "show span" using STP, RSTP, or MSTP options. Ensure the firewall rule #5 is configured correctly—disable logging afterward if required.
Here’s a revised version of your message:
Thank you once more for your time reviewing my response. The adjustments addressed most issues except for the management VLAN (99). I spent countless attempts trying various configurations today, but nothing worked. I gained valuable insights into what to avoid with Mikrotik Ether2. It wasn’t assigned to 192.168.99.0/24, which prevented me from obtaining an IP from the ICX. However, I was able to get an IP when I set Mikrotik Ether8 on the management bridge.
I found a helpful article here: https://forum.mikrotik.com/viewtopic.php...92#p469941. To resolve this, I decided to set up two DHCP servers sharing the same address pool but using different relays. VLAN 99 was configured on Ether2 with IP 192.168.99.2, while VLAN 99 on Management_bridge used IP 192.168.99.1. I assigned Ether8 to the management bridge.
I discovered that creating a DHCP server for the ICX and another for RB5009 helped. Both servers used the same address pool but differed in relays. The management DHCP server was set up with a relay at 192.168.99.254 (ICX IP), and the Management_dhcp_pool was linked to the transit VLAN "Management DHCP Server for RB5009."
When connected via ICX 1/1/3, the lease pointed to "Management DHCP Server for ICX." Through Mikrotik Ether8, it pointed to "Management DHCP Server for RB5009." Both had the same router IP (192.168.99.1) and DNS (192.168.88.1).
I’m facing inconsistent DNS resolution and ping issues. Sometimes the DNS fails when I try to ping, and sometimes it works but returns "No route to host." It seems the computer might already have a lease from 192.168.88.x, even though it’s connected via a different port. The ICX configuration hasn’t changed.
Any further advice would be appreciated. I’m close to using a different port on the ICX for the management VLAN and would prefer to stop trying. For example, Mikrotik Ether8 to ICX 1/2/2. This might be more manageable, but it would require updating routes on both sides.
I noticed a few issues: the same subnet shouldn't appear on multiple interfaces at once. You must include the Management VLAN interface in the Management_Bridge configuration. This was mentioned in my previous post. Navigate to Bridge > Ports > Add New > Interface Management and Bridge Management_Bridge. Then, remove the IP address 192.168.99.2/24. This subnet overlaps with another, and once an interface joins a bridge, all settings should be managed at the bridge level, not per interface. You need to ensure only one DHCP server/relay exists within each broadcast domain. Since you want the default gateway for this subnet to point to the router, it makes sense the switch should relay traffic there—not act as a relay itself. I appreciate your effort, but keep clarifying and we can go through this together. If you'd like, send me a direct message with your contact details so we discuss it live.