Unable to "Add VMware" due to duplicate UUID error during discovery.
OK, this seems to be a challenge for everyone. I would like to use the "Add VMware" feature with OpManager but am running into problems. Ive attempted many times to "Add VMware" but receive an error in the middle of the discovery stating
"VMWARE VCENTER DISCOVERY DISCARDED DUE TO DUPLICATION OF UUID FOR MORE THAN ONE HOST"
Upon my initial case creation with OpManager support, I was provided with a KB article from VMware whcih stated to reach out to the host hardware manufacture for support regarding duplicate UUID. Being that my host are from Cisco, I proceeded to open a TAC with Cisco who spent a couple hours with me confirming our physical host DO NOT have duplicate UUID's. On the other hand, we did generate a spread sheet that displayed multiple UUID's for several of our virtual servers. Cisco and I determined the duplicate UUID's from the virtual servers were in result of replica VM's being replicated to our DR site with Veeam which makes total sense, but shouldn't be the cause of the above notification in red. If it is, I would think OpManager developers would be able to somehow bypass this as replicas are common.
After coordinating with Cisco, I proceeded to follow up on my case with OpManager regarding our (Cisco and I) foundings providing the exported spread sheet from Vcenter which shows the VM's specyfiyng the duplicte UUID's. I then recived a reply from OpManager to provide log files which I did. I then was informed to run a bin command that provides outputhostdetails which I ran with the result of "Exception in establishing the Service Instance connection for device :vcenter"
"VMWARE VCENTER DISCOVERY DISCARDED DUE TO DUPLICATION OF UUID FOR MORE THAN ONE HOST"
Upon my initial case creation with OpManager support, I was provided with a KB article from VMware whcih stated to reach out to the host hardware manufacture for support regarding duplicate UUID. Being that my host are from Cisco, I proceeded to open a TAC with Cisco who spent a couple hours with me confirming our physical host DO NOT have duplicate UUID's. On the other hand, we did generate a spread sheet that displayed multiple UUID's for several of our virtual servers. Cisco and I determined the duplicate UUID's from the virtual servers were in result of replica VM's being replicated to our DR site with Veeam which makes total sense, but shouldn't be the cause of the above notification in red. If it is, I would think OpManager developers would be able to somehow bypass this as replicas are common.
After coordinating with Cisco, I proceeded to follow up on my case with OpManager regarding our (Cisco and I) foundings providing the exported spread sheet from Vcenter which shows the VM's specyfiyng the duplicte UUID's. I then recived a reply from OpManager to provide log files which I did. I then was informed to run a bin command that provides outputhostdetails which I ran with the result of "Exception in establishing the Service Instance connection for device :vcenter"