Lol their support is a fucken joke. "Community forum" only. Smh.

The POE has power and looks fine, I'm not sure what is going on

if you use the "tagged" command then yes, it puts them in a tagged vlan. if you use the "untagged" command, then it puts them in an untagged vlan. Hope that makes sense.

@@XshlomoX the untagged doesn't make much sense. So then how would I put specific ports on a separate vlan? Would I do that but just tagging them and then anything untagged is on vlan1?

@@tommykavounidis You simply add them as "untagged". You can for example add ports 1-10 to vlan 10 as "untagged eth 1/1/1 to eth 1/1/10" and then also add ports 11-20 to vlan 20 as "untagged eth 1/1/11 to eth 1/1/20" Of course you have to be in the global config mode "conf t" and enter the respective vlan configuration when adding ports as either tagged or untagged. The main difference between adding the ports as tagged or untagged: With tagged ports, the port will expect traffic with vlan headers of the respective vlan in order to accept them, the upstream device would then have to "strip"/"read" the vlan header. With untagged ports, the port doesn't expect a VLAN ID header to be present, nor will it forward the traffic with a VLAN ID (unless you also configure a tagged/trunk port to forward the traffic)

Okay and how to specify the IP address of the vlans?

@@tommykavounidis You should watch the videos Ruckus and Brocade have on the matter, they explain how to configure them step-by-step.

And what if my connection with neighbour switch is via aggregate lag interface? (created with two 10gig ports on both switch) I still put spanning tree parameter on aggregate level of interface?

it really isnt