Note
The Serial Console Access feature has been rolled out only to the YNY region. It will be rolled out to other regions in a phased manner.

You can create and delete serial console connections to your ExaDB-C@C systems to diagnose and resolve VM guest operating system issues using an SSH connection in case standard SSH access to the VMs is not possible.

Requirements: The use of the serial console feature requires Exadata Infrastructure version 22.1.10 or higher for 22.x users and version 23.1.1 or higher for 23.x users. The serial console feature will be available on any new VM Clusters created immediately but will only be available on previously existing VM Clusters after the next quarterly maintenance cycle. Also, make sure to review all prerequisites stated below, including setting a password for either the opc or the root user. Failure to make necessary changes for meeting these requirements in advance will result in the inability to urgently connect to the serial console when the need arises when the VM is not otherwise accessible.

Note
The following two endpoints have been added for the Control Plane Server (CPS). Use these URL formats, replacing oci_region with your region.

• console1.exacc.oci_region.oci.oraclecloud.com

• console2.exacc.oci_region.oci.oraclecloud.com

These must be allowed at your firewall in order for serial console connections to function. See Network Requirements for Oracle Exadata Database Service on Cloud@Customer Table 3-2 for further details.

Related Topics

• Network Requirements for Oracle Exadata Database Service on Cloud@Customer
• Troubleshooting Virtual Machines Using Console Connections
• Create the Virtual Machine Serial Console Connection
• Resource-Types for Exadata Database Service on Cloud@Customer
• db-nodes
• Permissions Required for Each API Operation
• dbnode-console-connection
• Serial Console Connection Event Types
• Viewing Audit Log Events