@TW_EPC 

1.  VLAN configurations of the LAN ports on Omada Gateway in Controller mode

Same for the switch. Or read the docs on the forum regarding the VLAN. 

2. It does not affect the use. That's the VLAN interface on the switch.

No.

3. Fail safe in case you mess up.

  @Clive_A 

Clive_A wrote

  @TW_EPC 

1.  VLAN configurations of the LAN ports on Omada Gateway in Controller mode

Same for the switch. Or read the docs on the forum regarding the VLAN. 

2. It does not affect the use. That's the VLAN interface on the switch.

No.

3. Fail safe in case you mess up.

Hello Clive,

Thanks. I was aware of your information. But a trunk port with only tagged VLANs isn't possible, correct?

And regarding point two: What benefit does activating two VLANs on the switch's VLAN interface provide? What scenarios can I imagine?

BR Tim

TW_EPC wrote

Hello everyone,

 

We want to renew our infrastructure soon and have bought 6x SG3452XMPP. Plus an OC300, because the WLAN system will also be integrated there soon.

 

Unfortunately, several questions and problems have now arisen that I would like to have clarified briefly:

 

1.  Can I create a trunk port, i.e. only tagged VLANs as a profile in the OC300? I see that a native, untagged VLAN must always be specified. Shouldn't there be another way to do this?
2. What happens if I change the management VLAN under “Devices” to a tagged one but leave the (old) default VLAN switched on? Does the switch then receive an IP via both networks and use the tagged VLAN as management?
3. Why can't I change the management VLAN via the group configuration of the switches under “Devices”? I had to set each switch individually, even with the same model.

 

I think that there is still a lot of room for improvement here, for example in comparison with Juniper switches. Above all, the fact that you can't make a trunk port exclusively from tagged VLANs is very strange.

 

Best regards
Tim

 

 

  @TW_EPC 

For some reason, VLANs in Omada-land are most confusing, at least to me.

In general, user devices connecting to the switch should be untagged (no VLAN tag) while inter-switch traffic should have a VLAN tag. For each port, the switch needs to answer a few questions about packets coming and going.

1. If a packet enters the port (ingress) without a VLAN tag, what tag should the switch affix?
2. Which tag should be stripped when leaving a port (egress) so that the connected device sees untagged traffic?
3. Which tags should the switch allow to pass through unchanged (for inter-switch links)?

Questions (1) and (2) address user devices attached to the switch that are receiving and sending untagged traffic. Question (3) addresses inter-switch traffic.

The "Native Network" parameter answers question (1). The "Untagged Network" parameter answers question (2). The "Tagged Networks" parameter answers question (3).

The "All" switch profile automagically populates all defined tags so that it can safely pass all tagged traffic for (3), even if new tags are later added.