====== NIOS Grid Join ====== ===== VPN Ports ===== Remember, the Grid Manager/Grid Manager Candidate and Grid Members need bi-directional access to each other. * UDP-2114 - Starts VPN tunnel creation * UDP-1194 - Actual VPN tunnel. Can be configured if needed. ===== MGMT Port ===== * Create appliance * Boot appliance * Set LAN1 * Connect to Web UI * Use web UI to set MGMT port * Appliance reboots * Use CLI to set membership * CLI wizard will ask if you want to use the MGMT port for Grid VPN. ===== Grid Join ===== We re-IP first and then join to Grid rather than joining to Grid as part of the re-IP. The reason for this is we have seen issues with re-IP AND Grid join where the box hung and needed console access + reset database to fix it. The following example is when joinging an appliance that is to be a member of a HA pair. If memory serves correctly, the "hour" jump is actually the appliance adjusting to British Summer Time as it joins the Grid. The total join time was about 10 minutes (not 1 hour and 10 minutes). Infoblox > set membership Join status: No previous attempt to join a grid. Enter New Grid Master VIP: 10.1.1.1 Enter Grid Name [Default Infoblox]: Enter Grid Shared Secret: test Join grid as member with attributes: Grid Master VIP: 10.1.1.1 Grid Name: Infoblox Grid Shared Secret: test WARNING: Joining a grid will replace all the data on this node! Is this correct? (y or n): y Are you sure? (y or n): y NOTE: This node will not become an active member of the ID grid until it has been configured on the grid master. Good Bye [2021/04/14 17:40:57.492] System restart... [2021/04/14 17:41:30.330] Infoblox system initializing... [2021/04/14 17:41:31.094] LAN port IPv4 192.168.1.123, netmask 255.255.255.0, gateway 192.168.1.1 [2021/04/14 17:42:01.284] Contacting the grid master at 10.1.1.1.... [2021/04/14 17:42:06.024] Synchronizing time with the grid master. [2021/04/14 17:44:25.500] System restart: time reset... [2021/04/14 17:45:00.273] Infoblox system initializing... [2021/04/14 17:45:01.023] LAN port IPv4 192.168.1.123, netmask 255.255.255.0, gateway 192.168.1.1 [2021/04/14 17:45:31.167] Contacting the grid master at 10.1.1.1.... [2021/04/14 17:45:36.390] System restart: config change... [2021/04/14 17:46:11.184] Infoblox system initializing... [2021/04/14 17:46:12.151] LAN port IPv4 192.168.1.123, netmask 255.255.255.0, gateway 192.168.1.1 [2021/04/14 17:47:05.359] Contacting the active HA node at 10.248.198.89.... [2021/04/14 17:47:10.664] Synchronizing database with the active HA node... [2021/04/14 17:47:41.831] System restart: config change... [2021/04/14 18:48:15.457] Infoblox system initializing... [2021/04/14 18:48:16.211] LAN port IPv4 192.168.1.123, netmask 255.255.255.0, gateway 192.168.1.1 [2021/04/14 18:49:15.459] Starting services... Disconnect NOW if you have not been expressly authorized to use this system. login: [2021/04/14 18:49:31.120] Completed database sync with the active HA node. [2021/04/14 18:49:31.120] Stopping services for database switchover... [2021/04/14 18:49:36.198] Starting services... Disconnect NOW if you have not been expressly authorized to use this system. login: ===== Leave Grid ===== A very dirty way to leave a grid is set nogrid Don't use this in production.