SOLVED - Confusing changes made to port profiles. I need to better understand these changes.

SOLVED - Confusing changes made to port profiles. I need to better understand these changes.

SOLVED - Confusing changes made to port profiles. I need to better understand these changes.
SOLVED - Confusing changes made to port profiles. I need to better understand these changes.
Wednesday - last edited Yesterday
Model: TL-SG2008  
Hardware Version: V4
Firmware Version: 4.20.13 Build 20250928 Rel.82909

I'm reviewing my VLANs and port application because I noticed a visual change that made things a bit confusing and changed how port profiles and VLAN profiles could be applied to a port profile configuration.

 

To be more precise, I remember that a Port Profile was the current Port Settings, where we entered a name for the profile, for example, "Port3-ALLOWED VLANS." In this profile, I had the VLAN settings and then applied this profile to the desired port.

 

With these latest updates, Omada changed the logic behind this, and this ended up leaving me with a very different and strange application, leaving seemingly garbage in my configuration.

 

Why am I referring to garbage? Because before, I had logical visibility, and now, it seems that the updates have migrated this to a new logic, and Port Profiles are now a Profile within Port Settings. This has made things a bit confusing, as there are now other settings that don't follow my logic, but somehow maintain the settings as they were before.

 

The Profile within Port Settings is now something separate that doesn't make much sense. And I had several Profiles (previously Port Profiles) with VLAN settings assigned to each.

I need guidance and even documentation regarding this change, as this is a big surprise, and I need to adapt the situation by eliminating the clutter that was created.

 

I would also really appreciate an explanation, as this was something I had decided to do as a post and changes only tomorrow or next Friday, but since it bothered me so much, I came here to try to understand it.

 

Unlike the current approach, another thing that didn't work for me was this configuration for creating VLANs with the next, next, finish type. I preferred the previous model, as we had more control.

 

As an example of what I'm saying, the one marked with the large red box was previously a Port Profile, not a Port Settings.

 

 

And, looking closely, what used to be the Port Profile was disassembled, removing the native VLAN settings and those that would be applied as Trunk and tagged, moving them to Port Settings and the Profile, which is new. That's the problem: this meaningless garbage is gone, and now I need to review the logic behind how it works.

 

 

 

Now, what do I do with this???

 

 

I'm using this link as a guide to what I'm saying.
https://community.tp-link.com/en/business/forum/topic/274132

  0      
  0      
#1
Options
1 Accepted Solution
Re:Confusing changes made to port profiles. I need to better understand these changes.-Solution
Friday - last edited Yesterday

  @Artur.Aragao 

 

It looks like you have updated to v6 beta controller - In v6 the switch port settings are totally reworked.

 

When you upgraded, your previous configurations were adapted into the new style of management automatically for you, which is why everything still has the same port anmes, vlans etc...

 

You now set VLANs native, tagged etc per port.  You can edit them in batches

You can add Labels to ports to allow you to filter by label in the future

You do not set VLANs in port profiles any more

 

Port profiles now only manage things like Spanning tree, flow control, QOS - everything they used to, except vlans.

 

 

Recommended Solution
  1  
  1  
#2
Options
2 Reply
Re:Confusing changes made to port profiles. I need to better understand these changes.-Solution
Friday - last edited Yesterday

  @Artur.Aragao 

 

It looks like you have updated to v6 beta controller - In v6 the switch port settings are totally reworked.

 

When you upgraded, your previous configurations were adapted into the new style of management automatically for you, which is why everything still has the same port anmes, vlans etc...

 

You now set VLANs native, tagged etc per port.  You can edit them in batches

You can add Labels to ports to allow you to filter by label in the future

You do not set VLANs in port profiles any more

 

Port profiles now only manage things like Spanning tree, flow control, QOS - everything they used to, except vlans.

 

 

Recommended Solution
  1  
  1  
#2
Options
Re:Confusing changes made to port profiles. I need to better understand these changes.
Saturday - last edited Yesterday

  @GRL

 

Thank you very much.

 

Before you replied, I paused to understand this new logic.

 

I already messed up here by applying VLANs to the ports using the next, next, finish method. I recommend that you don't do that and only configure them manually, or you may lose access to the devices. I needed to restore a configuration backup on the OC200 to normalize things and then remove unnecessary clutter.

 

Thank you for your kindness and contribution.

 

I can say now that I am more at ease and the new method makes the configurations more organized.

  0  
  0  
#3
Options