Port-Profile with R1 and Configuration Profiles

[justin_jeremias]

I'm here to ask a question (that I'm pretty sure I know the answer to) and suggest a feature for R1.

The problem is that using dynamic port-profiles (for phones, APs, cameras, etc.) will cause dynamic port-profile assignments on uplink ports that are going to another switch. I've tested this and confirmed the behavior. It also overwrites MVRP for what it's worth. If you're configuring a switch manually then adding to R1, you can account for this by manually creating a port-profile for uplinks that tag and untag the correct vlans. However, if you add a switch out of the box, it's not possible to do this until after it has joined and possibly grabbed the wrong dynamic port-profile. You also cannot set a manual vlan assignment in the configuration profile because the whole system is designed to use the default vlan as the interface. Again, you cloud manually set this, but that defeats the purpose of using configuration profiles.

An easy solution would be to add an option in the configuration profile to set an uplink profile to designated ports, or to simply exclude ports from port-profiles in this process. You could do this with self created uplink port-profiles or just treat it as a traditional trunk port and tag all the vlans on the switch accross these designated ports as default behavior.

Essentially, if Ruckus wants R1 to compete with Meraki and others in the cloud managed switch sphere, these things have to be capable of automatically working rather than requiring manual configuration before importing to R1. Again, that's the whole point of a configuration profile. Am I correct in my thought process here?

[AshwinM]

Hi Justin,

Hope you are doing great!

Your understanding is correct, and thank you for sharing us your concern with the behavior of dynamic port‑profiles on uplink ports when using RUCKUS One. Dynamic port‑profiles are intended to automatically apply configurations based on the connected end device, using methods such as LLDP‑TLV or MAC‑OUI for identification. However, this behavior can sometimes result in dynamic port‑profiles being applied to uplink ports, which are typically used for switch‑to‑switch connections and require specific VLAN configurations.

To have this behavior reviewed and considered for enhancement, please get in touch with your SE (System Engineer) to raise it as a feature request.

Regards,
Ashwin M