Two hosts of them through old within the cluster into maintenance mode remove, add in the new vcenter, other host through directly add,
Now found that the two within the host through the maintenance mode using VMRC console to open the virtual machine is normal, but the other host within the virtual machine to use open VMRC error,
Host an error will be moved to the two hosts which is normal,
First consider whether the host cache, shut down the original vcenter6.0, and tested a host in maintenance mode, remove the cluster, restart, add the host, but no actual effect,
Other host and two hosts and vcenter6.7 in the same vlan, between a computer and not through the firewall, Telnet test also on port 443902,
Check the MVRC log, as if there is something wrong with the connection,
The main | I005: SOCKET connect to WSS://10.4.1.11:443
The main | I005: SOCKET creating new IPv4 SOCKET, connecting to 10.4.1.11:443 (10.4.1.11)
The main | I005: PollSocketPairConnect: non - blocking socket 1016 connected immediately!
The main | I005: PollSocketPairConnect: non - blocking socket 1032 connected immediately!
MKS | I005: MKSControlMgr: connected
MKS | I005: MKS - VMDB: VMDB requested a screenshot
MKS | I005: MKSScreenShotMgr: Taking a screenshot
MKS | I005: KHBKL: Unable to parse keystring at: "'
MKS | I005: KHBKL: Unable to parse keystring at: "'
MKS | I005:2 (868) Connection SOCKET verified with the thumbprint: 8 a: 29: DA: E0:72: FC: 35: BA: DC: C4: FE: 0 B: 24:0 B: CE: they 8:9 3: A0:05
MKS | I005: HTTP message Received - HTTP/1.1 404
MKS | W003: MVNCClient: received the socket error 19: Upgrade to the websocket error: NOT FOUND, the status code 404
MKS | I005: MVNCClient: Setting vncClient. MksConnectionError, previous error is 0, the new error is 2
MKS | I005: MVNCClient: Destroying the VNC Client socket.
MKS | I005: MKSRoleMain: Disconnected from the server.
MKS | I005: MKS - RoleRemote: Disconnected from the server with the error code 2
And then looked at the virtual machine/log/virtual machine vmware. The log,
VMX | I120:493 (618), creating new SOCKET listening SOCKET on the port 1
VMX | I120: Listening on WebSocket pipe/var/run/vmware/ticket/627 a106918257d6b for 120 seconds
VMX | I120: Issuing new WebMKS ticket 627 a106918257d6b
VMX | I120: VigorTransport_ServerSendResponse opID=a57244 - seq f0-9987=954: Completed MKS request.
VMX | I120: VigorTransportProcessClientPayload: seq opID=6 df0ceb0 - a7-9988=955: identifiers MKS. IssueTicket request.
See have the same problem, but find someone hair solution, can someone answer