Aruba Core to Ubiquiti Edge switches - VLAN 1 issue

[Techie-Tech]

Hi there,

 

We have an Aruba Core with various VLANs configured which work well across the site, with the exception of VLAN1 on the Ubi's.

 

VLAN1 1 is used for SALTO door system and is set to untagged on the core to all live ports, but when we look at the Ubi's, we can see SALTO devices connected and the IP addresses, but these devices cannot seem to communicate with each other.

 

We have some area where the edge switches are HP right down the chain and VLAN 1 is working absolutely fine.

 

Any pointers as to what could be going on with VLAN 1 on the Unbiquiti's would be gretaly appreciated.

 

Thanks

[DalekSec]

I always thought it was best practice not to use VLAN 1, due to various security reasons.

 

It might be better to move anything on VLAN 1 to a new VLAN ID.

[Techie-Tech]

I always thought it was best practice not to use VLAN 1, due to various security reasons.

It might be better to move anything on VLAN 1 to a new VLAN ID.

 

Thanks, and I agree.

 

This was inherited so just trying to get it working for now.

[PotNoodleTech]

It's likely that the Aruba core has VLAN1 disabled as per best practice - so once your VLAN1 data tries to go from your Edge to Core it dissapears.

 

Realistically you would be best off moving VLAN1 into a different VLAN number on your edge switches to match your core and then changing all the door system ports from VLAN1 to VLAN whatever, shouldnt be any changes needed on the door system devices as they would likely just be running "untagged" rather than tagged with multiple vlan IDs?

Edited October 30, 2023 by PotNoodleTech

[Techie-Tech]

Hi,

 

On Friday we moved it onto a newly created VLAN and all appears to be working sweet as a nut.

 

Many thanks