TRSWH's Posts

Hello, everyone, In addition to the current vSphere farm, I am currently building our current farm, which should be active in the future. The farm under construction, hosts will be connected to a d... See more...
Hello, everyone, In addition to the current vSphere farm, I am currently building our current farm, which should be active in the future. The farm under construction, hosts will be connected to a distributed switch and other hosts will be connected to normal vSwitches. Now, of course, the goal is that VMotion should be possible from host to host without downtime if possible. From the hosts with normal vSwitches to the distributed switches it now works properly. However, back from the distributed switch to the hosts with vSwitches, I get a warning and it is not possible. Here's the message. As a side info vDSwitch has version 6.5 Hosts ESXi 7 U3 and hosts with vSwitch 6.5/6.7 multiple clusters The question is now is this generally not possible or do I have to set up a specific configuration. Unfortunately I mostly only find texts on how to migrate vSwitch to VDswitch and back. Unfortunately that's not what I need. Are there any options or do I have to look at a complete vDSwitch network infrastructure so that migration between each other is possible? Or do I just have a board in front of my head when thinking?
Hello all togehter, i not found directly a Thread with my Problem. We have installed the new fix for our vcsa 6.7 appliance and now at the build 18831133. With the Installation we have a side effe... See more...
Hello all togehter, i not found directly a Thread with my Problem. We have installed the new fix for our vcsa 6.7 appliance and now at the build 18831133. With the Installation we have a side effect. Browsers like Chrome, Opera an Co can not select in the HTML5 Client the Hosts, VMs oder even can make any action or interaction with the Web client. Only some menus work fine. Only now the browser firefox works fine with the WebClient and can use all functions (until now) Have anyone see this problem or can get me a direction to fix it? Until know it is not mentioned as known issue. Best regards Thomas
Probleme mit vCenter und SSO Domäne. Keine Anmeldung mehr an vCenter möglich. Verschiedene Fehlermeldungen. Aufgefallen dadurch, das Update auf aktuelle Version durchgeführt, aufgrund Problem... See more...
Probleme mit vCenter und SSO Domäne. Keine Anmeldung mehr an vCenter möglich. Verschiedene Fehlermeldungen. Aufgefallen dadurch, das Update auf aktuelle Version durchgeführt, aufgrund Probleme mit einem VMPatch wo HA Prozessoren Warnungen aufkommen. Nach Update fiel dies auf. Backup vorher durchgeführt, jedoch auch das Backup bzw. der Restore zeigt die Probleme mit der Version 6.5 U1e zeigt das Verhalten auf. Verschiedene Versuche oder Recherchen schlugen leider fehl. Daher sind wir hier auf Unterstützung angewiesen, da fehler bisher unbekannt und dadurch keine Verwaltung mehr möglich. Da Veeam Backup angebunden, leider auch keine aktuellen Backups möglich. VCenter ist im HA Verbund und mit external Platform Service Controller. Fehlermeldung von Internet Explorer:   A server error occurred. [400] Beim Senden der Authentifizierungsanforderung an den vCenter Single Sign-On-Server ist ein Fehler aufgetreten - Beim Verarbeiten der Metadaten für die Einrichtung von vCenter Single Sign-On ist ein Fehler aufgetreten - Cannot connect to the VMware Component Manager https://VMVCP01.LAN.LOCAL/cm/sdk?hostid=5689b31a-f9a1-4937-b8d0-46af12e0ef86. Fehlermeldung mit Chrome: A server error occurred. [500] SSO error: Cannot connect to the VMware Component Manager https://VMVCP01.LAN.LOCAL/cm/sdk?hostid=5689b31a-f9a1-4937-b8d0-46af12e0ef86 Fehlermeldung Firefox: 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x0000561964401b80] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe) SSO Status in Appliance Oberfläche:   Single Sign On         Single Sign On-Domäne    Status    Nicht anwendbar ===========Problems with vCenter and SSO domain. No more login to vCenter possible. Various error messages. Noticed by this, the update to current version performed, due to problems with a VMPatch where HA processors warnings arise. After update, this was noticeable. Backup done before, but also the backup or the restore shows the problems with version 6.5 U1e shows the behavior. Various attempts or research unfortunately failed. Therefore, we depend on support here, because errors so far unknown and thus no administration possible. Since Veeam Backup is connected, unfortunately, no current backups possible. VCenter is in the HA network and with external Platform Service Controller. Error message from Internet Explorer: A server error occurred. [400] An error occurred while sending the authentication request to the vCenter Single Sign-On server - An error occurred while processing the vCenter Single Sign-On metadata - Can not connect to the VMware Component Manager https: // VMVCP01.LAN.LOCAL / cm / sdk? hostid = 5689b31a-f9a1-4937-b8d0-46af12e0ef86. Error message with Chrome: A server error occurred. [500] SSO error: Can not connect to VMware Component Manager https: //VMVCP01.LAN.LOCAL/cm/sdk? Hostid = 5689b31a-f9a1-4937-b8d0-46af12e0ef86 Error message Firefox: 503 Service Unavailable ([N7Vmacore4Http20NamedPipeServiceSpecE: 0x0000561964401b80] _serverNamespace = / action = Allow_pipeName = / var / run / vmware / vpxd-webserver-pipe) SSO status in appliance interface: Single Sign On Single sign-on domain status Not applicable