So Im running Untangle NG Firewall and have been for many years. I was using UNIFI switches for years but due to problem after problem, constant firmware releases breaking shit, Im moving to Aruba. I am very familiary with how to setup VLAN's in Untangle as Ive been doing it for years as a long time UT reseller. Im missing someting stupid in the Aruba switch to get VLAN's working...
So I have the Parent (Physical) Interface in Untangle Interfaces setup with 192.168.20.0/24 with DHCP turned on. Thats the main subnet assigned the the Physical Parent Interface.. I then I have 4 VLAN's (Child Interfaces) setup on that Parent Interface identified as follows:
Parent (Physical) Interface - 192.168.20.0/24 (DHCP Enabled)
Child Interface 1 of Parent VOIP VLAN 250 - 192.168.250.0/24 (DHCP Enabled)
Child Interface 2 of Parent IoT VLAN 50 - 192.168.50.0/24 (DHCP Enabled)
Child Interface 3 of Parent Guest VLAN 50 - 192.168.75.0/24 (DHCP Enabled)
The Parent (Physical) Interace on Untangle is a 10GB SFP+ port on an Intel PCI-Express Dual SFP+ NIC in the 1U Supermicro server running Untangle NG Firewall. This SFP+ parent interface on UT server is connected to the 1st Aruba 2500 switch in the 10Gb SFP+ Port 0 via MM LC/LC cable.....
I actually have 2 Aruba 2500 switches here that are factory defaulted, latest firmware installed, Ive setup ArubaOS webgui on both switches via "GUI Quick Setup" on both switches.. then logging into each of the 2 switches individually, assigning them Admin and Enable Mode passwords and I assigned them both static LAN IP's outside the DHCP range on the Parent Interface main subnet 192.168.20.0/24...
After setting passwords and static LAN IP's on both switches...I connected my MM LC/LC cable from Parent Interface SFP+ port on my Untangle server to SFP+ 10GB Port 0 on the Primary Aruba 2500 switch. Everything works great.. I can plug my laptop or any other devices into any port on that switch and get DHCP address from Untangle server from the main Parent interface subnet 192.168.20.0/24 as I should. All is good so far...
I then connected the second switch to the first Aruba switch via 2 DAC's plugged into the 2 SFP+ Stacking 10GB Ports 2 and 3 on both switches. After a minute or so, the switches auto configure stacking.... That main 1st Switch I configured that is connected to Untangle (192.168.20.6) is set to Primary and the Second switch (192.168.20.7) I connected to the 1st switch via DAC cables in stacking ports is now showing Secondary. All is good. I can now plug any computer or device into any of the 48 ports on Primary 2500 or Secondary 2500 and I immediately get DHCP address from the Parent Interface DHCP on Untangle and have internet. All is working normaly as a Layer 2 switch...
I can now log into the ArubaOS webgui via the Primary switches static IP (192.168.20.6) show stacking is working..
My problem lies with getting VLAN's setup on these switches... I want to be able to do 2 things... Have ANY device that plugs into ANY of the 2 switches 48 ports, if tagged to receive a DHCP address from Untangle Child Interface's DHCP server for that respective VLAN. Example, I have a VOIP phone that I already have VLAN enabled on the phone and tagged with VLAN ID 250... When I plug that phone into any port on the 2 Arubs switches...it needs to get an IP address from VLAN 250 DHCP serveron Untangle...
Second, I want to be able to physically tag specific ports within the ArubsOS webgui with a specific VLAN ID so any device that gets plugged into those tagged ports also receive a DHCP address from that respective VLAN DHCP server on Untangle.
Ive been doing this with UBNT for years but cant get it working on these Aruba switches..
I can ping the respective VLAN Gateways when plugged into any port on the 2 Aruba switches. So I can ping 192.168.250.1 (VOIP VLAN 250 Gateway), 192.168.50.1 (IoT VLAN 50 Gateway),and 192.168.75.1 (Guest VLAN 75 Gateway)...
I tried setting up VLAN's both in the Aruba WebOS webgui and via SSH...
in the webgui I went Configuration>VLAN
I add the 3 VLAN's noted above, VLAN 250, 75 and 25 individually. I assigned each of them an IP but that is where Im a bit confused.
Example, when I added VLAN 250, I gave it the DHCP Gateway address for VLAN 250 which is 192.168.250.1... 255.255.255.0... and saved my settings... When I take a computer or VOIP phone I have here, turn on VLAN and tag 250 then plug it into the switch, I dont get a DHCP address from VLAN 250's DHCP server....or any IP address for that matter... I get a 169 IP... I then tried changing the IP in the Aruba switch for VLAN 250 from 192.168.250.1 to a static IP not in use on that VLAN so I gave it 192.168.250.6 255.255.255.0 and saved. Still no DHCP handing out when I plug a VLAN 250 tagged device into any of the switch ports...
So Ive now hit a roadblock on how to get these Arubs 2500 switches configured correctly so any VLAN tagged devices can pull a DHCP address from my Untangle VLAN DHCP server.....
Any help would be much appreciated... I have a feeling its got someting to do with Configuration>Ports>Switching... I have been able to get this working where I can tag specific ports on the 2500 and any untaggaed device plugged into those specific ports does pull the correct IP from the Untanlge VLAN DHCP server....
------------------------------
Dominic Eachus
------------------------------