F5F Stay Refreshed Power Users Networks Connecting two VLANs on a Cisco SG 350 device

Connecting two VLANs on a Cisco SG 350 device

Connecting two VLANs on a Cisco SG 350 device

U
Ugne30
Member
50
09-25-2016, 02:08 PM
#1
Hello, I'm trying to figure out this VLAN configuration issue. My new AP doesn't allow adding SSIDs on the default VLAN when other VLANs are already set up. I considered creating another VLAN and bridging it to the default, but I wasn't sure how to do that on a Cisco SG 350. I found online suggestions about bridge groups, but those aren't accessible via CLI—only the multicast command is available. I also thought about using two untagged ports for VLANs 1 and 11, but I don’t have room to spare those ports. Can there be another way to resolve this?
U
Ugne30
09-25-2016, 02:08 PM #1

Hello, I'm trying to figure out this VLAN configuration issue. My new AP doesn't allow adding SSIDs on the default VLAN when other VLANs are already set up. I considered creating another VLAN and bridging it to the default, but I wasn't sure how to do that on a Cisco SG 350. I found online suggestions about bridge groups, but those aren't accessible via CLI—only the multicast command is available. I also thought about using two untagged ports for VLANs 1 and 11, but I don’t have room to spare those ports. Can there be another way to resolve this?

F
f10dynamo
Junior Member
18
09-25-2016, 09:59 PM
#2
Cisco expert Lurick is here to assist
F
f10dynamo
09-25-2016, 09:59 PM #2

Cisco expert Lurick is here to assist

O
OmgItsStar
Junior Member
24
09-28-2016, 11:43 PM
#3
The SG350 doesn’t allow bridge groups, which means it can’t be configured that way. You can assign each SSID a unique VLAN and configure the access point to use the same VLAN for all of them.
O
OmgItsStar
09-28-2016, 11:43 PM #3

The SG350 doesn’t allow bridge groups, which means it can’t be configured that way. You can assign each SSID a unique VLAN and configure the access point to use the same VLAN for all of them.

A
Amtrak10
Senior Member
639
09-29-2016, 06:59 AM
#4
Unfortunately, none of the other SSIDs are linked to their VLAN due to existing networks, which means I might need to contact Sophos about an issue with their AP. However, with the central management subscription active, I can still manage this, even though it has expired, so I’ll have to rely on the XG firewall instead.
A
Amtrak10
09-29-2016, 06:59 AM #4

Unfortunately, none of the other SSIDs are linked to their VLAN due to existing networks, which means I might need to contact Sophos about an issue with their AP. However, with the central management subscription active, I can still manage this, even though it has expired, so I’ll have to rely on the XG firewall instead.

T
64
09-29-2016, 10:29 AM
#5
It seems each network name needs its own VLAN, which isn't ideal. I thought assigning VLAN 11 to all SSIDs would simplify things—using the SG350 with a trunk port and setting native VLAN 11 could work.
T
txdarlin202002
09-29-2016, 10:29 AM #5

It seems each network name needs its own VLAN, which isn't ideal. I thought assigning VLAN 11 to all SSIDs would simplify things—using the SG350 with a trunk port and setting native VLAN 11 could work.

D
Danjaberry
Member
65
10-21-2016, 09:55 AM
#6
I’m revisiting this discussion and tried a hands-on approach. I discovered two open ports and decided to link them by removing their tags. I connected them on a short cable and set up VLAN 11 on port 9, linking it to the default VLAN on port 35. I also turned off STP for those ports to prevent loop detection issues. Despite these changes, I’m still unable to receive DHCP from VLAN 1. It seems there might be something missing in my configuration. The AP acting as a trunk port should deliver VLAN 11 traffic to VLAN 1, but it’s not working as expected.
D
Danjaberry
10-21-2016, 09:55 AM #6

I’m revisiting this discussion and tried a hands-on approach. I discovered two open ports and decided to link them by removing their tags. I connected them on a short cable and set up VLAN 11 on port 9, linking it to the default VLAN on port 35. I also turned off STP for those ports to prevent loop detection issues. Despite these changes, I’m still unable to receive DHCP from VLAN 1. It seems there might be something missing in my configuration. The AP acting as a trunk port should deliver VLAN 11 traffic to VLAN 1, but it’s not working as expected.

S
SpaceMonkeh
Junior Member
10
10-31-2016, 12:29 PM
#7
When using the AP as a trunk port, establish a default VLAN to ensure traffic from the switch carries the VLAN ID removed.
S
SpaceMonkeh
10-31-2016, 12:29 PM #7

When using the AP as a trunk port, establish a default VLAN to ensure traffic from the switch carries the VLAN ID removed.