Now that the static route has been configured, an ipv4Routes.sh script has been created in the folder /opt/vmware/gateway/conf. Use the CIDR notation for specifying a static route.ĭo not forget to click the (+) button to actually really add the static route. Open up the IPv4 Configuration and enter your static route in the IPv4 Static Routes field. Under Advanced Settings click the gear icon next to Network Settings.Ĭlick the gear icon next to the nic interface for which you want to add a static route. The Management Interface PartĬonnect to the UAG management interface (:9443) using a web browser and login using the user name admin and the password that you configured during the UAG appliance deployment. Since we regained access to the management interface, we will now configure the static route there. Only static routes that are configured in the management interface will be retained during an UAG appliance reboot. However, static routes that are configured from the command line are not retained during an UAG appliance reboot. Where eth1 is the nic for the management interface/LAN in my case.Īdding the static route regained access to the management interface. This can be done using the following command. To fix that, I needed to add a static route first. In my case I needed to regain access to the management interface first. You can type the following command to show the current routes. Login using the user name root and the password that you specified during the UAG appliance deployment. Select Login using the Up/Down arrow keys and hit Enter.

Open the UAG console in whatever hypervisor you are using.

This short blog post shows a way to fix this.

Instead of redeploying, I decided to fix my mistake manually. During the deployment I forgot to specify the required static route which prevented me from reaching the UAG management interface (:9443). Recently, I deployed a new VMware Unified Access Gateway (UAG) multi-nic appliance.

Uag unified access gateway