---
name: vmwaresolutions-vc_viewinginstances
title: Viewing VCF for Classic - Automated instances
description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2025-10-24
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Viewing VCF for Classic - Automated instances
{: #vc_viewinginstances}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

View the summary and detailed information of the VMware Cloud Foundation for Classic - Automated instances that are provisioned for different user accounts.

## Procedure to view a summary of Automated instances
{: #vc_viewinginstances-procedure-view-inst-summary}

To view a summary of all the Automated instances that are provisioned for a user account, complete the following steps:

1. In the VMware Solutions console, click **Licensing and metering > Add-on services** from the left navigation panel.
2. From the console banner, click the **Avatar** icon ![Avatar icon](../../icons/i-avatar-icon.svg "Avatar"), and then click the **Account** field. Select the user account that you want to check instances for.
3. In the **VMware Cloud Foundation for Classic** table, view the list of instances that are provisioned in the selected user account.

| Item | Description |
|:---- |:----------- |
| Name | The name of the instance. |
| Resource type | The resource type of the instance. |
| Location | The IBM Cloud data center where the instance is hosted. |
| Creation time | The date and time when the instance was created. |
| Status | The status of the instance. |
{: caption="Automated instance summary" caption-side="bottom"}

The instance can have different statuses.

| Status | Description |
|:------ |:----------- |
| Creating | The instance is being created. |
| Building | The instance is being configured. |
| Available | The instance is ready to use. |
| Modifying | The instance is being modified. |
| Failed | The creation, configuration, or modification process failed. |
| Deleting | The instance is being deleted. |
| Deletion error | An error occurred when the instance was being deleted. |
| Deleted | The instance is deleted. |
{: caption="Automated instance statuses" caption-side="bottom"}

## Procedure to view details for Automated instances
{: #vc_viewinginstances-procedure-view-inst-property}

To view the property details of an instance, complete the following steps.

1. In the **VMware Cloud Foundation for Classic** table, click an instance name.
2. On the **Summary** tab, view the details for the instance.

| Property | Description |
|:-------- |:----------- |
| Resource type | The resource type of the instance. |
| Current version | The current version of IBM Cloud for VMware Solutions. |
| VMware vSphere version[^vsphere] | The version of VMware vSphere. |
| vCenter version | The vCenter Server version. \n \n **Note:** The vCenter Server versions that are displayed on the IBM Cloud for VMware Solutions console and the VMware vSphere® Web Client are slightly different. Both are correct. |
| Name | The name of the instance. |
| ID | The ID of the instance. |
| Multizone region[^multizone] | The IBM Cloud data center region where the instance is hosted. |
| Location | The IBM Cloud data center where the instance is hosted. \n \n **Note:** For multizone instances, locations are listed for each cluster type. |
| VMware NSX® networking solution[^NSX] | * NSX for instances that are provisioned with NSX version 4.0 or later. \n * NSX-T or NSX-V for instances that are provisioned with previous versions of NSX, earlier than version 4.0. |
| NSX version | The VMware NSX product version. |
| Root domain | The root domain name is the DNS domain name and the Microsoft® Active Directory™ (AD) forest root name. |
| SSO domain | The SSO domain is the vSphere single sign-on domain. The SSO domain name is fixed for all deployed Automated instances with a value of **`vsphere.local`**. |
{: caption="Automated instance properties" caption-side="bottom"}

[^multizone]: Multizone instances only

[^NSX]: Single-zone instances only

[^vsphere]: Single-zone instances only

## Procedure to view access information for Automated instances
{: #vc_viewinginstances-procedure-view-access-info}

On the **Access information** tab, view the access information for the instance-related components. The passwords that are displayed are initial passwords that are generated by the system. If you change them outside of the IBM Cloud for VMware Solutions console, they are not updated on the **Access information** tab.

| Component | Description |
|:--------- |:----------- |
| IP[^ips] | The IP address or addresses of the AD server or servers. |
| FQDN[^fqdn] | The fully qualified domain names (FQDNs) of the AD/DNS server. \n The same administrator password can be used to connect to all AD/DNS servers by using a remote desktop connection. |
| ADMIN (Remote Desktop) | For primary instances, it displays the username and password to access the AD server through a remote desktop connection. \n For secondary instances, click the **View on primary instance** link to be directed to the username and password information on the primary instance. \n After the secondary instance is added to the primary DNS domain and replication occurs, the local administrator password on the primary instance might overwrite the local administrator password on the secondary instance. By clicking the **View on primary instance** link, you can access the correct administrator password. |
{: caption="Access information tab - AD/DNS" caption-side="bottom"}
{: tab-title="AD/DNS"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-ad-dns}

| Component | Description |
|:--------- |:----------- |
| IP | The IP address of the vCenter Server. |
| FQDN | The FQDN of the vCenter Server. |
| ADMIN | The VMware vCenter SSO username and password that you can use to log in to vCenter Server by using the VMware vSphere Web Client. |
| SSH | The username and password that you can use to access the vCenter Server VM through SSH connection. |
{: caption="Access information tab - vCenter/PSC" caption-side="bottom"}
{: tab-title="vCenter/PSC"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-vcenter-psc}

| Component | Description |
|:--------- |:----------- |
| IP | The IP address of the NSX Manager. |
| FQDN | The FQDN of NSX Manager. |
| HTTP | The username and password that is used to access the NSX Manager web console. |
{: caption="Access information tab - NSX Manager" caption-side="bottom"}
{: tab-title="NSX Manager"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-nsx-manager}

| Component[^nsxt-1] | Description |
|:------------------ |:----------- |
| IPs | The IP address or addresses for the NSX node VM. |
| SSH | The username and password that you can use to access the NSX node VM through KVM or SSH connection. |
{: caption="Access information tab - NSX Controllers" caption-side="bottom"}
{: tab-title="NSX Controllers"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-nsx-controllers}

| Component[^nsxt-sz] | Description |
|:------------------- |:----------- |
| IPs | The IP address or addresses for the Customer Edge VM. |
| SSH | The username and password that you can use to access the Customer Edge VM through KVM or SSH connection. |
{: caption="Access information tab - Customer Edge VM" caption-side="bottom"}
{: tab-title="Customer Edge VM"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-customer-edge-vm}

| Component[^nsxt-2] | Description |
|:------------------ |:----------- |
| IPs | The IP address or addresses for the NSX Service Edge VM. |
| SSH | The username and password that you can use to access the NSX Service Edge VM through KVM or SSH connection. |
{: caption="Access information tab - NSX Service Edge VMs" caption-side="bottom"}
{: tab-title="NSX Service Edge VMs"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-nsx-service-edge-vms}

| Component | Description |
|:------------------ |:----------- |
| IPs | The IP address or addresses for the Usage Meter VM. |
| FQDN | The FQDN of the Usage Meter. |
| ADMIN | The Usage Meter username and password that you can use to log in to the Usage Meter web interface. |
| SSH | The username and password that you can use to access the Usage Meter VM through KVM or SSH connection. |
{: caption="Access information tab - Usage Meter VMs" caption-side="bottom"}
{: tab-title="Usage Meter VMs"}
{: tab-group="access info"}
{: class="simple-tab-table"}
{: #simpletable-access-info-usage-meter}

[^ips]: Two IP addresses for the two AD servers.

[^fqdn]: Two FQDNs for the two AD servers.

[^nsxt-1]: NSX-T only

[^nsxt-sz]: NSX-T single-zone only

[^nsxt-2]: NSX-T only

## Procedure to view infrastructure details for Automated instances
{: #vc_viewinginstances-procedure-view-infra}

Click the **Infrastructure** tab to view the details of the clusters in the instance.

| Item | Description |
|:---- |:----------- |
| Cluster name | The name of the cluster. |
| Cluster type | The type of the cluster (consolidated, gateway, management, or workload). |
| ESXi servers | The number of ESXi servers in the cluster. |
| Storage | The storage type and whether **vSAN deduplication and compression** is enabled. |
| Data center location | The IBM Cloud data center where the cluster is hosted. |
| Pod | The IBM Cloud data center pod where the cluster is hosted. |
| Networking | The networking type, either **Public and private network** or **Private network only**. |
| Uplink speed | The uplink speed, either 10 or 25 Gb. |
| Status | The status of the cluster. The cluster statuses are similar to the instance statuses. |
{: caption="Infrastructure tab" caption-side="bottom"}

## Procedure to view service details for Automated instances
{: #vc_viewinginstances-procedure-view-services}

Click the **Services** tab to view the details of the add-on services on the instance.

| Item | Description |
|:---- |:----------- |
| Service | The name of the service. |
| Name | The name of the service instance, if applicable. |
| Cluster type | The type of the cluster (consolidated, gateway, management, or workload) that the add-on service is installed on. |
| Cluster name | The name of the cluster that the add-on service is installed on. |
| Status | The status of the add-on service. |
| Delete icon | To delete the service, click this icon and confirm. |
{: caption="Services tab for Automated instances" caption-side="bottom"}

## Procedure to view licensing details for Automated instances
{: #vc_viewinginstances-procedure-view-license}

Click the **Licensing** tab to view the details of the current license. You can compare with other license types and change the current license if required.

## Procedure to view deployment history for Automated instances
{: #vc_viewinginstances-procedure-view-deploy-history}

Click the **Deployment history** tab to view the deployment history for the instance.

If you see errors in the deployment history, the IBM Cloud Support team is automatically notified. To inquire about the status of your ticket, follow the steps in [Getting help and support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support&format=markdown).

## What to do next
{: #vc_viewinginstances-next}

Manage your instances from the IBM Cloud for VMware Solutions console or the VMware vSphere Web Client.

Before you click **vCenter console** on the instance summary page to go to the vSphere Web Client and start managing your VMware ESXi™ servers, you must log in to the VPN portal of the IBM Cloud data center. Hover over **vCenter console** and follow the instructions to ensure that you meet all requirements and you completed the necessary steps before you access the vSphere Web Client.
{: important}

Review the following topics for information to help you complete the login instructions:
*  For the requirements and necessary steps before you access the vSphere Web Client, see [Timeout reached while connecting to the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_timeout_vc_console&format=markdown).
*  For a list of access points to log in to the IBM Cloud infrastructure private network by using VPN, see [Getting started with IBM Cloud Virtual Private Networking](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-started&format=markdown).
*  If you have problems when you deploy an OVF (Open Virtualization Format) file by using the vSphere Web Client, see [Deploying an OVF file by using the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_deploy_ovf&format=markdown).

## Related links
{: #vc_viewinginstances-related}

* [Ordering Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req&format=markdown)
* [Adding clusters for Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters&format=markdown)
* [Adding ESXi servers to Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers&format=markdown)
* [Deleting Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance&format=markdown)