I have implemented the Serial Connection under one of our VM's running in our EXACC solution. Followed the note (https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-9B812B5A-D4B9-4820-AF1E-E300B453300C)
I get the following error message connecting:
ssh_exchange_identification: Connection closed by remote host
ssh_exchange_identification: Connection closed by remote host
Steps completed:
- Verified connectivity from the application server trying to establish the console connection from on port 443
- created public and private key for OS user on a remote application server as custom linux user
- Created the console connection on one of our VM's pasting the public key from the custom linux user
- Fetched the command from the console serial connection.
- Run the command from the application server using the -i option to specify my private key file.
I can see from the documentation that required IAM policies states two policies required:
Allow group <group_name> to manage dbnode-console-connection in tenancy
Allow group <group_name> to read db-nodes in tenancy
Question that comes to mind. Do I need an OCI user with the given public key? Is that even possible. Or does the console functionality require that you spin up a compute in your tenant and uses this to connect to the serial console?
Anyone who have done this with a locally installed application server and can enlighten me on the steps I am missing.
Thanks.
Best regards
KOS