Vcenter 6.5

[Trinh Livingston]

Ifyou have VBR connection to enterprise manager then you need to remove it from there. That is where this is read from. If not the case then editing the database would be the only other way but I suggest contacting support for that.

1 to know how to remove orphaned vcenter from EM but the support engineering is different and don t want to give me the query. He wants me to send the database and the name lf the stale vcenter... If I want my answer, that means I have to reproduction the issue :( that s boring....

Make sure to make a backup of the VCSA before updating since that is a tricky process that may finish unexpectedly, resulting in weird WebUI failures (most typical issue) or VCSA not being able to start at all. A complete VM backup, a temporary snapshot, or a native VCSA backup -vcenter-server-7-tips will work.

The only time that a vCenter would affect the startup or function of a VM is if the host RELIES on the cluster services like Virtual Distributed Networking (vDS) or VSAN. Even in these cases there are ways to architect the environment to reduce that impact.

That is not quite true since you can manage virtual machines and ESXi hosts using the ESXi web console. PowerCLI and ESXCLI are also some valid alternative options -vsphere-command-line-interface-esxcli-commands-helped-lot/ .

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)

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.

Before the update all was OK. The vCenter and all scanned information was there.

We upgraded from v10.6.2.0

Scanning credentials are OK.

I have the vCenter IP with credentials as scanning target to scan it manually.

I can trigger the scan manually, the IP shows up in the scanning queue but seems not to be scanned because the vCenter server does not show up as asset and the widget stays empty.

Any ideas?

Update:

Logon with the given credentials works on the webclient/webpage of the vcenter.

LS calls the api and that logon runs into the error.

Hello,It is suspected that we are running into an error parsing the certificate, though it is not yet clear what part exactly. We have created a new bug report for this: LAN-16378. We recommend checking our changelog when a new version is released to make sure this fix is included. You can find our changelog here: [lansweeper.com] Kind regards,"

NOTE: otelcol.receiver.vcenter is a wrapper over the upstreamOpenTelemetry Collector vcenter receiver from the otelcol-contribdistribution. Bug reports or feature requests will be redirected to theupstream repository, if necessary.

disable_high_cardinality_metrics is the Grafana Agent equivalent to the telemetry.disableHighCardinalityMetrics feature gate in the OpenTelemetry Collector.It removes attributes that could cause high cardinality metrics.For example, attributes with IP addresses and port numbers in metrics about HTTP and gRPC connections are removed.

You must specify the output block, but all its arguments are optional.By default, telemetry data is dropped.Configure the metrics, logs, and traces arguments accordingly to send telemetry data to other components.

3a8082e126