I’m struggling to get a trunk set up on bridge1 and eth8 to an Aruba S2500 0/0/0. Trying to ping it fails. Changed the Aruba IP to 192.168.88.2 with same results.
Ping from switch to 192.168.88.1 doesn’t reply either from the switch. I see 0 TX and 0 RX on the bridge1 interface near as I can tell.
Posted the export here.
Thanks in advance for any tips on how to improve this humble setup.
The Aruba should be assigned an IP address that is on the Trusted subnet vlan of the Router.
One way is to pick an unused lanip, assign it to the aruba, then go into DHCP leases on the Router and enter the IP and mac address of the switch and make it a static entry.
Here’s is the scoop, I will spank you if you continue to use vlan1 for any traffic.
Its the default and should be left alone unless one is an advanced user.
So if you have a subnet that you use 192.168.88..0/24 for traffic, simply create another vlan call it 10 or 100 just not one.
I prefer not to mix apples and oranges and just use the bridge for /interface bridge port and /interface bridge vlan settings… Keeps it clean and simple.
Yes, the management vlan is what I mean. ALL Smart devices should have an IP on the management vlan.
This assumes that this is the vlan the admin uses to manage the devices and configs etc…
I needed to remove the complication I had created.
I have my default subnet already in place on the RB4011.
I had existing 3 VLANs already in place and working on original bridge interface.
I had the idea that I wanted to create a 2nd bridge interface, Tag 2nd bridge tagged and the port out of the RB4011 to which the Aruba switch was connected(both on RB4011) to create the trunk. <–Bad idea. Overcomplicated for my use.
Solution for my use case:
Remove 2nd bridge from the RB4011 and all reference to it.
Add port out of the RB4011 to which the Aruba switch was connected as a tagged port to original bridge.
That’s it. Pings both ways. From router to switch and switch to router.
*And, no, anav, I did not have a VLAN1 per se. I used the wrong terminology to describe the native vlan.
*And, yes, I did have the switch on the same subnet as the RB4011 management IP.