Troubleshooting Tip: GUI unavailable after upgrading in an Azure High Availability deployment

[cmaheu]

Description	This article describes behavior where the administration UI is not available after an upgrade in an Azure VM High Availability environment. A solution is offered.
Scope	Version: 8.x and greater
Solution	This can occur if the Azure VM cannot reach the IP address defined in the 'gateway' field in the High Availability configuration. For details on defining gateways in Azure appliances, see Determine Gateway IP Addresses in the High Availability reference manual. CentOS appliances: 1) Log in to the FortiNAC CLI. On a CentOS appliance: Log in as root. FortiNAC-OS appliance: Log in as admin. 2) Identify the IP address currently configured as the gateway. On a CentOS appliance, run the following command: cat /bsc/campusMgr/bin/.networkConfig | grep -i gateway On a FortiNAC-OS appliance, run the following command: execute enter-shell /bsc/campusMgr/bin/.networkConfig | grep -i gateway Example: cat /bsc/campusMgr/bin/.networkConfig | grep -i gateway //Gateway address. This can be any device that supports ICMP Ping and is not Gateway=10.12.242.1 <--- 3) Check if the gateway IP address responds to a ping attempt.  On a CentOS appliance, run the following command: ping <gateway IP> On a FortiNAC-OS appliance, run the following command:  execute ping <gateway IP> 4) If there is no response, modify the gateway IP to loop back to the IP '127.0.0.1' and save the file. 5) Log in to the GUI and navigate to System -> Settings -> System Management -> High Availability. 6) Change the gateway IPs per the requirements listed above. 7) Restart FortiNAC services to apply the change. If services do not restart automatically, enter the following commands in the CLI: shutdownNAC startupNAC Wait twenty to twenty-five minutes for the services to restart and test again. If additional assistance is required, open a support ticket.