Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:grid_master_candidates [2024/07/25 13:10] – bstafford
+++ infoblox_nios:grid_master_candidates [2025/10/15 13:18] (current) – [Promote Grid Master Candidate] bstafford
@@ Line 12: / Line 12: @@
 Note, the test command doesn't test all communication channels.
-Note: During the GMC promotion test, communication through ports (2114/1194) will be checked. The test cannot be performed when MGMT port is used for communication (this is known behavior). As a workaround we can use the "show network_connectivity" command to confirm whether the Member is reachable on ports 2114 and 1194 which is required for the Grid Master and the Grid Member to communicate with each other. The result of the command shows that the Host is up and both the ports 2114 and 1194 are open between the Grid Master Candidate and the Grid Member.
+Note: During the GMC promotion test, communication through ports (2114/1194) will be checked. The test cannot be performed when MGMT port is used for communication (this is known behavior). As a workaround we can use the "show network_connectivity" command to confirm whether the Member is reachable on ports 2114 and 1194 which is required for the Grid Master and the Grid Member to communicate with each other. The result of the command shows that the Host is up and both the ports 2114 and 1194 are open between the Grid Master Candidate and the Grid Member. For more details on "show network_connectivity" see [[infoblox_nios:troubleshooting#show_port_is_open|this page]].
@@ Line 27: / Line 27: @@
 During a promotion, the members will connect to the new GM, re-sync and perform a services restart (not a product restart and no reboot)
+When you promote a HA GMC to GM
+  *Upon running "set promote_master" from CLI on the Grid Master Candidate, the request goes to the active node of the Grid Master Candidate.
+  *The active node of the Grid Master Candidate restarts in the process of transitioning from Grid Master Candidate to Grid Master.
+  *When the passive node of the Grid Master Candidate misses multiple consecutive heartbeats from the active node, the passive node assumes the active node role of the Grid Master Candidate.
+  *When the previously active node of the Grid Master Candidate finishes the restart process, the previously active node of the Grid Master Candidate comes back up as the new Grid Master.
+  *The current active node of the Grid Master Candidate logs "restart: new master found" and restarts to come back up as the passive node of the new Grid Master.
+  *All Members, including the previous Grid Master, should log the same message "restart: new master found" and restart.
+  *If the previous Grid Master and other Grid Members are HA pairs, the HA pairs will restart almost simultaneously because the active nodes will see the new master, log the message "restart: new master found" and restart. Then, when the passive nodes transition to active nodes, these newly active nodes will also see the new Grid Master and immediately restart.
+For HA members, both nodes (active and passive) restart almost at the same time. This is because as soon as the active node restarts and the passive becomes active, it also detects the new grid manager and restarts immediately.
+Find the below KB article for the order of restart:
+  * https://support.infoblox.com/s/article/4307
+  * https://support.infoblox.com/s/article/98
 ===== GMC Error =====
-If you have a VM Grid and the GM says that the GMC is not suitable for GMC role, it could be that the GMC hard drive is too small. I had this when I deployed a NIOS 7.3.11 VM that had a 55Gb hard drive. This image is really for Multi-GM only. GM and GMC should use the 250Gb image.
+If you have a VM Grid and the GM says that the GMC is not suitable for GMC role, it could be that the GMC hard drive is too small. Years ago I had this when I deployed a NIOS 7.3.11 VM that had a 55Gb hard drive. This image is really for Multi-GM only. GM and GMC should use the 250Gb image. As of 2025, the minimum image you can deploy is 150GB (resizable image). 150GB should not be used in production but is okay for simple labbing.