Issue with Stacking SX6632YF Switches in Omada Controller
Hello,
I am trying to stack two SX6632YF switches in Omada Controller (version 5.15.24.18). Both switches are successfully adopted and connected in the controller.
When I create a new stack under Device Group to stack both switches, the second switch disconnects after the stack is created and does not reconnect anymore.
Both switches are physically connected: port 29 to port 29, and port 30 to port 30. The priority of my first switch is 100 and the second is 50%.
What am I doing wrong?
Thank you in advance for your support.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
HW25 wrote
Hello,
The only difference is that my Omada Controller is installed in a virtual environment in vCenter. Could that be the problem?
That does not hurt anything.
When it comes to the stacking, if there is a problem during the stacking phase, delay or anything, you did not waited it to finish, it would cause a problem.
The stacking can go wrong even with the proper steps.
But once it is established, it would rarely become down. I think you might try with the steps again. And records the details in CLI output.
If this behaivor persists, you can contact the support team for help.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Details and steps have been explained in this link:
https://www.tp-link.com/en/support/faq/3936/
- Copy Link
- Report Inappropriate Content
Thanks for the info. I've already found this guide and tried these steps. The same thing happens in standalone mode and with the controller. The same problem occurs with both methods.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello,
The only difference is that my Omada Controller is installed in a virtual environment in vCenter. Could that be the problem?
- Copy Link
- Report Inappropriate Content
HW25 wrote
Hello,
The only difference is that my Omada Controller is installed in a virtual environment in vCenter. Could that be the problem?
That does not hurt anything.
When it comes to the stacking, if there is a problem during the stacking phase, delay or anything, you did not waited it to finish, it would cause a problem.
The stacking can go wrong even with the proper steps.
But once it is established, it would rarely become down. I think you might try with the steps again. And records the details in CLI output.
If this behaivor persists, you can contact the support team for help.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 137
Replies: 6
Voters 0
No one has voted for it yet.