Hello
I was looking for technical support to perform upgrade from 6.5 to 6.7 vcenter version.
When I try to do upgrade from UI method, at stage two its failed.
Log Reference :1 (when I try to start manually)
root@photon-machine [ /var/log/firstboot ]# service-control --start vmware-vpxd
Operation not cancellable. Please wait for it to finish...
Performing start operation on service vpxd...
Error executing start on service vpxd. Details {
"problemId": null,
"componentKey": null,
"resolution": null,
"detail": [
{
"translatable": "An error occurred while starting service '%(0)s'",
"localized": "An error occurred while starting service 'vpxd'",
"id": "install.ciscommon.service.failstart",
"args": [
"vpxd"
]
}
]
}
Service-control failed. Error: {
"problemId": null,
"componentKey": null,
"resolution": null,
"detail": [
{
"translatable": "An error occurred while starting service '%(0)s'",
"localized": "An error occurred while starting service 'vpxd'",
"id": "install.ciscommon.service.failstart",
"args": [
"vpxd"
]
}
]
}
root@photon-machine [ /var/log/firstboot ]#
Log reference : 2 (vpxd_update.log)
root@photon-machine [ /var/log/firstboot ]# cat vpxd_update.log
2019-08-19T06:38:02.983Z INFO vpxd_update Start vpxd-prop update
2019-08-19T06:38:31.767Z INFO vpxd_update The file vpxd-service-spec.prop.rpmnew doesn't exist, no patching needed...
2019-08-19T06:38:31.768Z INFO vpxd_update End vpxd-prop update
2019-08-19T07:20:42.317Z INFO vpxd_update Start vpxd-prop update
2019-08-19T07:21:03.266Z INFO vpxd_update The file vpxd-service-spec.prop.rpmnew doesn't exist, no patching needed...
2019-08-19T07:21:03.267Z INFO vpxd_update End vpxd-prop update
2019-08-19T08:54:38.191Z INFO vpxd_update Start vpxd-prop update
2019-08-19T08:54:58.114Z INFO vpxd_update The file vpxd-service-spec.prop.rpmnew doesn't exist, no patching needed...
2019-08-19T08:54:58.116Z INFO vpxd_update End vpxd-prop update
root@photon-machine [ /var/log/firstboot ]#
Regards,
Bala
Hi
The problem has been resolved by configuring the DNS Server for host name "photon-machine".
root cause of the issue was DNS server mandatory for this upgrade operation.
DNS Server can be configured on vCD Database Windows server as below. or else you can use any running DNS server.
https://www.atlantic.net/cloud-hosting/how-to-configure-dns-windows-server-2012/
Note: FQDN : photon-machine should be resolved by your vCenter service IP.
Regards,
Bala
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
can you check the vpxd.log under /var/log/vmware/vpxd when the upgrade fails and validate if the service started? or upload the logs under /var/log/vmware/vpxd
thanks,
MS
Is PSC external or embedded
6.5 was appliances or windows based
Do you have snap shot
Check you IP , error is pointing to IP conflict
019-08-19T11:50:17.759Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.101] conflict between vm [VMSC2_AP-B (36ec2ac8-df99-4d58-b48d-e2796b4cb2be)] (moId:vm-5848) nic:GuestInfo.net[5].ipAddress[1] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.759Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.2] conflict between vm [VMSC2_AP-B (36ec2ac8-df99-4d58-b48d-e2796b4cb2be)] (moId:vm-5848) nic:GuestInfo.net[5].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.759Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.213.2] conflict between vm [VMSC2_AP-B (36ec2ac8-df99-4d58-b48d-e2796b4cb2be)] (moId:vm-5848) nic:GuestInfo.net[6].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.759Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.2] conflict between vm [VMSC2_AP-B (36ec2ac8-df99-4d58-b48d-e2796b4cb2be)] (moId:vm-5848) nic:GuestInfo.net[3].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.759Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.2] conflict between vm [VMSC2_AP-B (36ec2ac8-df99-4d58-b48d-e2796b4cb2be)] (moId:vm-5848) nic:GuestInfo.net[4].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.1] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[5].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.100] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[5].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.102] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[5].ipAddress[3] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.121] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[5].ipAddress[2] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.213.1] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[6].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.1] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[3].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.33] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[3].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.1] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[4].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.770Z error vpxd[38161] [Originator@6876 sub=InvtId opID=DbParallelLoad-6d7d4b3] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.33] conflict between vm [VMSC2_AP-A (831550f6-84dd-4b01-b981-5163b7f4ee36)] (moId:vm-5850) nic:GuestInfo.net[4].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.101] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[5].ipAddress[1] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.121] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[5].ipAddress[2] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.2] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[5].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.213.2] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[6].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.2] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[3].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.33] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[3].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.2] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[4].ipAddress[0] and entity [VHLR1-AP-B (f4fab920-c816-4eef-a617-4fbcf5a5bcd0)] (moId:vm-5805)
2019-08-19T11:50:17.780Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.33] conflict between vm [VIPSTP_AP-B (57a3b926-7648-4109-b8ba-27917e555900)] (moId:vm-4491) nic:GuestInfo.net[4].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.1] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[5].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.100] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[5].ipAddress[1] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.208.102] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[5].ipAddress[2] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:169.254.213.1] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[6].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.169.1] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[3].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.783Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.170.1] conflict between vm [VIPSTP_AP-A (1ea13011-eadc-4150-94bd-eb287cf7ad93)] (moId:vm-4492) nic:GuestInfo.net[4].ipAddress[0] and entity [VHLR1-AP-A (94e54b38-8336-4943-916a-4e7da12feb2c)] (moId:vm-5806)
2019-08-19T11:50:17.808Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.104] conflict between vm [PL-4] (moId:vm-5272) nic:GuestInfo.net[0].ipAddress[1] and entity [PL-4] (moId:vm-5150)
2019-08-19T11:50:17.808Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.4] conflict between vm [PL-4] (moId:vm-5272) nic:GuestInfo.net[0].ipAddress[0] and entity [PL-4] (moId:vm-5150)
2019-08-19T11:50:17.808Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.1.4] conflict between vm [PL-4] (moId:vm-5272) nic:GuestInfo.net[1].ipAddress[0] and entity [PL-4] (moId:vm-5150)
2019-08-19T11:50:17.808Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.2.4] conflict between vm [PL-4] (moId:vm-5272) nic:GuestInfo.net[2].ipAddress[4] and entity [PL-4] (moId:vm-5150)
2019-08-19T11:50:17.812Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.3] conflict between vm [PL-3] (moId:vm-5273) nic:GuestInfo.net[0].ipAddress[0] and entity [PL-3] (moId:vm-5151)
2019-08-19T11:50:17.812Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.1.3] conflict between vm [PL-3] (moId:vm-5273) nic:GuestInfo.net[1].ipAddress[0] and entity [PL-3] (moId:vm-5151)
2019-08-19T11:50:17.812Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.2.3] conflict between vm [PL-3] (moId:vm-5273) nic:GuestInfo.net[2].ipAddress[4] and entity [PL-3] (moId:vm-5151)
2019-08-19T11:50:17.815Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.101] conflict between vm [SC-2] (moId:vm-5274) nic:GuestInfo.net[0].ipAddress[1] and entity [SC-2] (moId:vm-5152)
2019-08-19T11:50:17.815Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.2] conflict between vm [SC-2] (moId:vm-5274) nic:GuestInfo.net[0].ipAddress[0] and entity [SC-2] (moId:vm-5152)
2019-08-19T11:50:17.815Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.1.2] conflict between vm [SC-2] (moId:vm-5274) nic:GuestInfo.net[1].ipAddress[0] and entity [SC-2] (moId:vm-5152)
2019-08-19T11:50:17.815Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.2.2] conflict between vm [SC-2] (moId:vm-5274) nic:GuestInfo.net[2].ipAddress[4] and entity [SC-2] (moId:vm-5152)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.1] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[0].ipAddress[0] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.100] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[0].ipAddress[1] and entity [SC-2] (moId:vm-5152)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.102] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[0].ipAddress[2] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.0.103] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[0].ipAddress[3] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.1.1] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[1].ipAddress[0] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:192.168.2.1] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[2].ipAddress[5] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:fe80::1ff:fe01:2] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[2].ipAddress[4] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e 4c 02 6f e1 19 95-86 58 b8 57 a9 a9 07 be:fe80::200:ff:feff:1] conflict between vm [SC-1] (moId:vm-5275) nic:GuestInfo.net[2].ipAddress[1] and entity [SC-1] (moId:vm-5153)
2019-08-19T11:50:17.818Z error vpxd[38158] [Originator@6876 sub=InvtId opID=DbParallelLoad-46cdbe2] [VpxdInvtId::CheckIp] detected IP [50 2e
Thanks for the logs.. You have KMS setup in your environment?
This line is suspicious for me...
2019-08-19T11:43:26.998Z info vpxd[35885] [Originator@6876 sub=CryptoManager] KMS cert earliest expiry time is 9223372036854775807, check interval is 7776000000000
Thanks,
MS
Hello
It is embedded platform and it's(6.5 version) Linux based Appliances as shown in print screen.
Regards,
Bala
Hello
we are not using KMS as we don't have windows based vCenter. both old 6.5 and new 6.7 are Linux based Appliances.
Regards,
Bala
Hello
While upgrading in stage:2 i have this warning message before proceed next step. which may address some things which is related to this issue.
vSphere 6.7
Getting Started - vCenter Server Appliance with an Embedded Platform Services Controller (PSC)
vCenter Server 6.7 has been successfully installed. However, additional steps must be completed before it is available for use. Click one of the links below to continue setup.
Set up
Configure this Appliance as a new vCenter Server.
Upgrade
Transfer the configuration, historical, and identity data from a vCenter Server Appliance.
Migrate
Transfer the configuration, historical, and identity data from a vCenter Server instance on Windows.
Restore
Transfer the configuration, historical, and identity data from a vCenter Server Appliance backup.
Copyright © 1998-2018 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents . VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware products may contain individual open source software components, each of which has its own copyright and applicable license conditions. See http://www.vmware.com/info?id=1127 for more information.
Upgrade - Stage 2: vCenter Server Appliance with an Embedded Platform Services Controller
Introduction
Connect to source vCenter Server
Select upgrade data
Configure CEIP
Ready to complete
Select upgrade data
Select the data that you want to copy from the source vCenter Server.
The data sizes shown below represent only the data that will be copied to the target server. It does not correspond to the actual size of your data on the source server. The identity of the server will also be copied and the source server will remain unchanged.
Configuration (2.8 GB) Estimated downtime: 44 minutes
Configuration and historical data (events and tasks) (2.9 GB)
Configuration and historical data (events, tasks and performance metrics) (2.9 GB)
Pre-upgrade check result
Warning
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
Description
Files that cannot be used with Update Manager 6.7 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESX 5.5 and lower version host patches baselines.
Resolution
Please review VMware Update Manager 6.7 Documentation for details
Warning
vCenter External Extensions
Description
This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: NSX Manager (by VMware) on https://10.164.228.149/sdk/vimService, NSX Manager (by VMware) on https://10.164.228.149/sdk/vimService,
Resolution
Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade. Please refer to the vSphere documentation on extensions, and the upgrade and interoperability guides.
Warning
The newly deployed appliance FQDN will be set to 10.164.228.149, although the source appliance FQDN is set to localhost.localdom. This might result in inability to access the appliance through FQDN localhost.localdom
Description
The newly deployed appliance FQDN will be set to 10.164.228.149, although the source appliance FQDN is set to localhost.localdom. This might result in inability to access the appliance through FQDN localhost.localdom
Resolution
To preserve current appliance FQDN, verify that the FQDN matches the configuration of the vCenter Single Sign-On and the vCenter Server certificates. To verify that the FQDN is DNS resolvable - execute `dig localhost.localdom +short` locally on the appliance, or `nslookup localhost.localdom` on a windows machine
Regards,
Bala
Hi
The problem has been resolved by configuring the DNS Server for host name "photon-machine".
root cause of the issue was DNS server mandatory for this upgrade operation.
DNS Server can be configured on vCD Database Windows server as below. or else you can use any running DNS server.
https://www.atlantic.net/cloud-hosting/how-to-configure-dns-windows-server-2012/
Note: FQDN : photon-machine should be resolved by your vCenter service IP.
Regards,
Bala
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.