DCO - VMware vCenter integration DCO write in vCenter

[DCIM_Support]

This question was originally posted on DCIM Support by Mate Fekete on 2019-08-27

---

Hello,

I'm using vCenter integration in DCO. I noticed in vCenter event logs are full with the followings:

MGMT\x_apcdcim is  the user which has read only in vCenter. But DCO tries to create a custom host value so wants to write something in vCenter. This appears when I do association between DCO entity and ESXi host which is coming from the integration.

What DCO wants to create as a custom value in vCenter and how can I avoid these errors?

(CID:148343237)

[DCIM_Support · Accepted solution]

This answer was originally posted on DCIM Support by Greg Sterling on 2019-08-27

---

Hello Mate

The link which describes the permissions required for the vCenter integration is here: Configuring VMware vCenter integration

I have pasted the info below so you don't have to move to the link. Yes. Once the ESXi host is associated to a device in a rack, DCO will attempt to set a couple of custom properties on the host in vCenter which notes the location of the server. This means when you view the host in vCenter you'll see a property which notes which room, rack, and U location the ESXi host resides.

The VMware vCenter user must have permission to these operations:

• setCustomValue
• logUserEvent
• setTaskDescription
• addCustomFieldDef
• exitMaintenanceModeTask
• destroyPropertyFilter
• createFilter
• waitForUpdatesEx
• retrieveServiceContent
• login
• logout
• waitForUpdates
• retrieveProperties

Far as I know this can not be turned off.

Regards

Greg Sterling

(CID:148343361)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.