5 Replies Latest reply on May 14, 2019 9:55 AM by BenFB

UAG 3.2 install via Powershell not using staticv4 address

hammord Jan 29, 2018 7:02 PM

Hello. I am trying to use the PowerShell script to install UAG 3.2. This will be a huge time saver over the OVF if I can get past the last remaining issue. When I configure the ini file with a single IPV4 address, the appliance installs, but grabs a DHCP address instead. I can see the OVF properties is missing the STATICV4 setting that is required when building the appliance using the GUI OVF installation. Is there an ini file setting to set STATICV4 during the installation?

Thank you.

1. Re: UAG 3.2 install via Powershell not using staticv4 address

a.p. Jan 30, 2018 12:31 PM (in response to hammord)

It works perfectly for me.
Can you confirm that you create a Network Protocol Profile, and set all of the three below mentioned .ini entries to the same network name?
sample:
netInternet=DMZ
netManagementNetwork=DMZ
netBackendNetwork=DMZ
André
Like Show 0 Likes(0)

Actions
2. Re: UAG 3.2 install via Powershell not using staticv4 address

nettech1 Apr 21, 2018 10:27 AM (in response to hammord)

Did you create Network Profiles in your vCenter to match the network labels in your answer file?
Like Show 0 Likes(0)

Actions
3. Re: UAG 3.2 install via Powershell not using staticv4 address

markbenson Mar 13, 2019 4:03 AM (in response to hammord)

hammord - is this resolved now? The issue will be with your .ini file.

If you still have the issue, attach your .ini file with ip0= entry etc, and someone will help.
Like Show 0 Likes(0)

Actions
4. Re: UAG 3.2 install via Powershell not using staticv4 address

hammord May 10, 2019 3:18 PM (in response to markbenson)

I tried again using the 3.5 script and this time it prompted me that I was missing netmask0=. I added the netmask0 and the script worked flawlessly!
Like Show 0 Likes(0)

Actions
5. Re: UAG 3.2 install via Powershell not using staticv4 address

BenFB May 14, 2019 9:55 AM (in response to hammord)
Yes, that is a required field.
Using PowerShell to Deploy VMware Unified Access Gateway
Deploying Unified Access Gateway Without Network Protocol Profile (NPP)

As of UAG 3.3 the Network Protocol Profile (NPP) requirement has been removed.

Release Notes for VMware Unified Access Gateway 3.3
Removed dependency on Network Protocol Profile (NPP) - It is no longer necessary to set up an NPP or an IP Pool to deploy Unified Access Gateway. Instead, the IPv4 netmask, IPv6 prefix, and default gateway are specified when Unified Access Gateway is deployed. This helps with improved vSphere deployment flexibility.
Like Show 0 Likes(0)

Actions