tdubb123
Expert
Expert

deleting and redeploy controller add increment

when i delete a controller and redeploy a new one it keep incrementing the number. why is that. I want to start from #1

0 Kudos
6 Replies
Sreec
VMware Employee
VMware Employee

This is expected behavior and i don't think there is any way to change it as of now.

Cheers,
Sree | CKA|CKAD|VCIX-3X| VCAP-4X| VExpert 5x
Please KUDO helpful posts and mark the thread as solved if answered
0 Kudos
amolnjadhav
Enthusiast
Enthusiast

Hi,

As sree mentioned No way we can restart the controller counting from #1.

I guess you can give a try,  Unregistered the NSX Manager with vCenter Server Then reboot NSX Manager n try to register Manager with VC.

Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly. Regards Amol Jadhav VCP NSXT | VCP NSXV | VCIX6-NV | VCAP-DCA | CCNA | CCNP - BSCI
0 Kudos
A13x
Hot Shot
Hot Shot

No this will not work, the controller is on a counter and that will continue to increment. At the end of the day it is just a number, we have controllers since the early days which have no names. There is no way i can find to remotely configure the names now they have been deployed and the only way is to delete and redeploy. You have a number issue and my controllers are referred to as 'null' :smileycry:

0 Kudos
tanurkov
Enthusiast
Enthusiast

Count of the controllers are in NSX Manger database, there is field which increment count numbers. this is a good indication what was done to controllers before.

there is no practical reason why you want to change numbers. It just a number nothing more. DB is hidden from access and I not recommend you to play with it if you never touch NSX Manager DB

Regards Dmitri

0 Kudos
tanurkov
Enthusiast
Enthusiast

HI ,

If  you OK with answers , can you mark them please as helpful or correct to close the loop

thanks in advance

Dmitri

0 Kudos
Mid_Hudson_IT
Contributor
Contributor

There is no reasoning at all to name them "Controller-1" "Controller-2" "Controller-3" because when the host is rebooted or a controller dies and the slices are redistributed when the controller is redeployed it will just follow a sequence and not a number scheme that is aesthetically pleasing. For this very reason it's pointless to even add this is a VCDX-NV design, you'll just get a O.o (ooo really, explain...)

VCP5/6-DCV, VCP6-NV, vExpert 2015/2016/2017, A+, Net+, Sec +, Storage+, CCENT, ICM NSX 6.2, 70-410, 70-411
0 Kudos