VMware Horizon Community
MayurPatel
Expert
Expert
Jump to solution

New UAG v2012 - Unable to Assign IP using Powershell Deploy Script

I am trying to deploy a new UAG 2012 using the Powershell script.

The deployment runs successfully but after over 10 attempts. The only thing that works after the ovf import completes successfully without any errors is only the correct Network adaptors get created correctly but the IP, Host name and Root Passwords details from the INI file details are not being applied.

Below is the excerpt from the INI file of the IP adaptor details I am using in the INI file.

# This section was added but does not seem to make any difference

ipMode=STATICV4
ip0AllocationMode=STATICV4
ip1AllocationMode=STATICV4

# Two NIC option

deploymentOption=twonic
ip0=172.16.1.10
netmask0=255.255.255.0
routes0=172.16.1.0/24 172.16.1.2, 192.168.1.0/24 192.168.1.1
ip1=172.16.1.11
netmask1=255.255.255.0
routes1=172.16.1.0/24 172.16.1.2, 192.168.199.0/24 192.168.199.2

dns=192.168.199.4

Host name fails to register/apply. The password also fails to apply from the INI file

hostname fail.JPG

IP details fail to register from the script

UAG Build Error.JPGNo Network.JPG

No errors but the deployment does not apply any details from the INI file.

 

0 Kudos
1 Solution

Accepted Solutions
MayurPatel
Expert
Expert
Jump to solution

I deployed the UAG ova using the vCenter option and that worked.

Not sure about others but the scripted method did not work for me at all.

 

 

 

I tried to use the UAG deployment tool and for some reason this is also failing with the below error log which I have also attached.

MayurPatel_0-1613533274375.png

2021-02-17T03:37:55.357Z - info: installerLogFile: C:\Users\user\AppData\Local\Temp\vcsaUiInstaller\installer-20210216-193755350.log
2021-02-17T03:37:55.358Z - info: networkLogFile: C:\Users\user\AppData\Local\Temp\vcsaUiInstaller\network-20210216-193755350.log
2021-02-17T03:37:56.723Z - debug: wizardTitle: Deploy UAG Appliance
2021-02-17T03:37:58.881Z - debug: wizardTitle: Deploy UAG Appliance
2021-02-17T03:38:17.685Z - info: THUMBPRINT(Target): 77:EA:21:18:AC:0B:91:3F:23:79:2B:85:E3:AA:80:B6:30:FC:31:E4
2021-02-17T03:38:19.417Z - info: login() to 192.168.1.10
2021-02-17T03:38:19.417Z - info: initializing vsphere API connection to 192.168.1.10:443
2021-02-17T03:38:22.154Z - info: vimService apiType: HostAgent, version: 6.7.0
2021-02-17T03:38:22.189Z - debug: session does not exist: 192.168.1.10, root
2021-02-17T03:38:22.189Z - debug: Logging in to 192.168.1.10:443 as root
2021-02-17T03:38:22.243Z - info: Logged in to 192.168.1.10:443 as root, session: 5297cf54-584a-5cda-aa3e-59a84b4e76e4
2021-02-17T03:38:22.243Z - debug: After successful login, initiate pingTimer with delay: 300000
2021-02-17T03:38:22.278Z - debug: admin roles:[ { entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'vpxuser',
group: false,
roleId: -1,
propagate: true },
{ entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'dcui',
group: false,
roleId: -1,
propagate: true },
{ entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'root',
group: false,
roleId: -1,
propagate: true } ]
2021-02-17T03:38:22.279Z - debug: user: root, userPrincipal: root
2021-02-17T03:38:22.279Z - debug: userHasAdminRole:root:root: has admin role
2021-02-17T03:38:22.279Z - debug: adminRole: true
2021-02-17T03:38:22.279Z - info: host target precheck
2021-02-17T03:38:22.870Z - info: hostPrecheck: localhost.cipherkey.com, ha-host
2021-02-17T03:38:22.870Z - info: ESXi hostVersion=6.7, minVersion=5.5
2021-02-17T03:38:22.870Z - info: lockdownMode: 'lockdownDisabled'
2021-02-17T03:38:22.871Z - info: inMaintenanceMode: false
2021-02-17T03:38:22.871Z - info: hostPrecheck succeeded: localhost.cipherkey.com
2021-02-17T03:38:22.871Z - info: ESXi hostCheck was successful
2021-02-17T03:38:22.932Z - debug: [object Object]
2021-02-17T03:39:02.209Z - info: vmName: SS01
2021-02-17T03:39:02.244Z - error: Error in creation of container viewServerFaultCode: The object 'vim.Folder:null' has already been deleted or has not been completely created
2021-02-17T03:42:36.160Z - info: Log file was saved at: C:\uagdeploy\installer-20210216-193755350.log

 

View solution in original post

0 Kudos
3 Replies
EricMonjoin
Expert
Expert
Jump to solution

Why do you want  to set IP in the same range with the same route in 2 differents interface. ? !!!

Just try to deploy in a 1 nic configuration

Eric

0 Kudos
MayurPatel
Expert
Expert
Jump to solution

Thank you for your reply Eric!

The reason I am using two nics is because in my lab testing environment I have a DMZ vlan that I use for dual nic Netscaler /XenDesktop testing.

I have tried using the one nic option but for some strange reason, when i deploy it using the uagdeploy.ps1 script - the IP, Password, Hostname settings are not propagating to the UAG VM. I can't even logon to the appliance after it is deployed because the password is not being configured. From what I can observe, the configuration state of the NIC's remains set to DHCP instead of STATICV4.

Hope you can shed some light on the above.

0 Kudos
MayurPatel
Expert
Expert
Jump to solution

I deployed the UAG ova using the vCenter option and that worked.

Not sure about others but the scripted method did not work for me at all.

 

 

 

I tried to use the UAG deployment tool and for some reason this is also failing with the below error log which I have also attached.

MayurPatel_0-1613533274375.png

2021-02-17T03:37:55.357Z - info: installerLogFile: C:\Users\user\AppData\Local\Temp\vcsaUiInstaller\installer-20210216-193755350.log
2021-02-17T03:37:55.358Z - info: networkLogFile: C:\Users\user\AppData\Local\Temp\vcsaUiInstaller\network-20210216-193755350.log
2021-02-17T03:37:56.723Z - debug: wizardTitle: Deploy UAG Appliance
2021-02-17T03:37:58.881Z - debug: wizardTitle: Deploy UAG Appliance
2021-02-17T03:38:17.685Z - info: THUMBPRINT(Target): 77:EA:21:18:AC:0B:91:3F:23:79:2B:85:E3:AA:80:B6:30:FC:31:E4
2021-02-17T03:38:19.417Z - info: login() to 192.168.1.10
2021-02-17T03:38:19.417Z - info: initializing vsphere API connection to 192.168.1.10:443
2021-02-17T03:38:22.154Z - info: vimService apiType: HostAgent, version: 6.7.0
2021-02-17T03:38:22.189Z - debug: session does not exist: 192.168.1.10, root
2021-02-17T03:38:22.189Z - debug: Logging in to 192.168.1.10:443 as root
2021-02-17T03:38:22.243Z - info: Logged in to 192.168.1.10:443 as root, session: 5297cf54-584a-5cda-aa3e-59a84b4e76e4
2021-02-17T03:38:22.243Z - debug: After successful login, initiate pingTimer with delay: 300000
2021-02-17T03:38:22.278Z - debug: admin roles:[ { entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'vpxuser',
group: false,
roleId: -1,
propagate: true },
{ entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'dcui',
group: false,
roleId: -1,
propagate: true },
{ entity: { value: 'ha-folder-root', type: 'Folder' },
principal: 'root',
group: false,
roleId: -1,
propagate: true } ]
2021-02-17T03:38:22.279Z - debug: user: root, userPrincipal: root
2021-02-17T03:38:22.279Z - debug: userHasAdminRole:root:root: has admin role
2021-02-17T03:38:22.279Z - debug: adminRole: true
2021-02-17T03:38:22.279Z - info: host target precheck
2021-02-17T03:38:22.870Z - info: hostPrecheck: localhost.cipherkey.com, ha-host
2021-02-17T03:38:22.870Z - info: ESXi hostVersion=6.7, minVersion=5.5
2021-02-17T03:38:22.870Z - info: lockdownMode: 'lockdownDisabled'
2021-02-17T03:38:22.871Z - info: inMaintenanceMode: false
2021-02-17T03:38:22.871Z - info: hostPrecheck succeeded: localhost.cipherkey.com
2021-02-17T03:38:22.871Z - info: ESXi hostCheck was successful
2021-02-17T03:38:22.932Z - debug: [object Object]
2021-02-17T03:39:02.209Z - info: vmName: SS01
2021-02-17T03:39:02.244Z - error: Error in creation of container viewServerFaultCode: The object 'vim.Folder:null' has already been deleted or has not been completely created
2021-02-17T03:42:36.160Z - info: Log file was saved at: C:\uagdeploy\installer-20210216-193755350.log

 

0 Kudos