I am trying to setup the discovery of the VMWare vCenter appliance VM. We already have the vCenter discovery working, but I need to discover the VM itself. I worked with our VMWare team to setup SNMP but the Linux Server part would still not discover. I found that the OID was not in the CMDB so I created an OID entry and a Classification and used the Linux Server table. This worked and now I have the Linux Server CI being discovered. However, after discovery is ran the [cmdb_ci_vcenter] record that is created by the VMWare probes also creates a CI in the [cmdb_ci_computer] class using CredentiallessDiscovery and a runs on::runs relationship to it. It does not seem to find the Linux Server to create the relationship with. Also, according to the documentation it should not create a runs on::runs relationship at all if you have an appliance (see link and text below)
Discovery for VMware vCenter (servicenow.com)
"If a Windows or Linux server is running vCenter application, after creating the vCenter CI, a "Runs on" relationship to the Windows or Linux server host is created.
When a vCenter application is running on a dedicated vCenter appliance, "Runs on" relationship to the vCenter CI is not created."
Has anyone created a way to discover and create both the [cmdb_ci_vcenter] record and the [cmdb_ci_linux_server] record creating the relationship correctly? Even though the docs say it should not, I would think a relationship is needed to tie the vCenter CI to the Linux Server CI in a runs on::runs relationship.
