@Vincent-TP 

For your info,the core switch is not adopted into the omada oc300 controller due to limitation on the L3 static route problem.

if i enable LLDP in the core switch does the network can detect the core switch even though its not adopted in the oc300?
for now im running the core without adopting into oc300.but if i adopt it into the oc300,does the setting goes away and i need to setting it all over again?
im in hotel infrastructure network thats running 24/7.

  @Dukesinclair 

what is your static route problem that prevents you adopting the switch?

  Hi @GRL ,

I recently purchased a TP-Link SX6632YF to replace an aging Juniper core switch. Our environment already uses TP-Link Omada for all access switches, managed by an OC300.

The vendor responsible for the supply and installation claims that they cannot adopt the SX6632YF into the OC300 because of "problems with Layer 3 settings." They seem to be struggling with the configuration and have had to call TP-Link support multiple times.

I am trying to determine if this is a genuine hardware/software limitation or a configuration error on their part.

My questions are:

1. Are there known limitations when adopting the SX6632YF into an OC300, specifically regarding Layer 3 configurations?

2. Has anyone successfully managed this specific core switch model via an OC300 in a Layer 3 environment?

Any advice would be appreciated so I can resolve this quickly. Thanks!