| copyright | lastupdated | keywords | subcollection | content-type | ||
|---|---|---|---|---|---|---|
|
2025-01-29 |
IBM Cloud for VMware Solutions, getting started, vmware solutions offerings, services for vmwaresolutions, vmwaresolutions use cases |
vmwaresolutions |
conref |
{{site.data.keyword.attribute-definition-list}}
{: #conref-vmwaresolutions}
CONTENT:
For Sapphire Rapids servers, choose the following CPU model and a supported RAM size: {: #sapphire-para-intro}
| CPU model | Cores | GHz | Storage type | RAM options |
|---|---|---|---|---|
| Dual Intel Xeon Platinum 8474C | 96 | 2.1/3.1 | Up to 14 drives | 256 GB, 512 GB, 1 TB, 2 TB |
| {: caption="Option for Sapphire Rapids bare metal servers" caption-side="bottom"} | ||||
| {: #simpletabtable-sapphire} |
For Cascade Lake servers, choose from the following CPU models and supported RAM sizes: {: #cascade-para-intro}
| CPU model | Cores | GHz | Storage type | RAM options |
|---|---|---|---|---|
| Dual Intel Xeon Silver 4210 | 20 | 2.2 | Up to 12 drives | 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB |
| Dual Intel Xeon Gold 5218 | 32 | 2.3 | Up to 12 drives | 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB |
| Dual Intel Xeon Gold 6248 | 40 | 2.5 | Up to 12 drives | 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB |
| Dual Intel Xeon Platinum 8260 | 48 | 2.4 | Up to 12 drives | 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB |
| Quad Intel Xeon Gold 6248 | 80 | 2.5 | Up to 24 drives | 384 GB, 768 GB, 1.5 TB, 3 TB |
| Quad Intel Xeon Platinum 8260 | 96 | 2.4 | Up to 24 drives | 384 GB, 768 GB, 1.5 TB, 3 TB |
| {: caption="Options for Cascade Lake bare metal servers" caption-side="bottom"} | ||||
| {: #simpletabtable-cascade} |
For SAP-certified Cascade Lake servers, choose from the following configurations: {: #sap-para-intro}
| CPU model | Cores | GHz | RAM | Storage type |
|---|---|---|---|---|
| Dual Intel Xeon Gold 5218 (BI.S4.NW192) | 32 | 2.3 | 192 GB | Up to 12 drives |
| Dual Intel Xeon Gold 5218 (BI.S4.NW384) | 32 | 2.3 | 384 GB | Up to 12 drives |
| Dual Intel Xeon Gold 6248 (BI.S4.NW768) | 40 | 2.5 | 768 GB | Up to 12 drives |
| Dual Intel Xeon Platinum 8260 (BI.S4.NW768_v2) | 48 | 2.4 | 768 GB | Up to 12 drives |
| Dual Intel Xeon Platinum 8280M (BI.S4.NW1500) | 56 | 2.7 | 1.5 TB | Up to 12 drives |
| Dual Intel Xeon Platinum 8280M (BI.S4.NW3000) | 56 | 2.7 | 3 TB | Up to 12 drives |
| {: caption="Options for SAP-certified Cascade Lake bare metal servers - NetWeaver" caption-side="bottom"} | ||||
| {: tab-title="NetWeaver"} | ||||
| {: tab-group="SAP-certified Intel servers"} | ||||
| {: class="simple-tab-table"} | ||||
| {: #simpletabtable-sap-netweaver} |
| CPU model | Cores | GHz | RAM | Storage type |
|---|---|---|---|---|
| Dual Intel Xeon Gold 5218 (BI.S4.H2.192) | 32 | 2.3 | 192 GB | Up to 12 drives |
| Dual Intel Xeon Gold 5218 (BI.S4.H2.384) | 32 | 2.3 | 384 GB | Up to 12 drives |
| Dual Intel Xeon Gold 6248 (BI.S4.H2.768) | 40 | 2.5 | 768 GB | Up to 12 drives |
| Dual Intel Xeon Platinum 8280M (BI.S4.H2.1500) | 56 | 2.7 | 1.5 TB | Up to 12 drives |
| Dual Intel Xeon Platinum 8280M (BI.S4.H2.3000) | 56 | 2.7 | 3 TB | Up to 12 drives |
| Quad Intel Xeon Platinum 8280M (BI.S4.H4.3000) | 112 | 2.7 | 3 TB | Up to 24 drives |
| Quad Intel Xeon Platinum 8280M (BI.S4.H4.6000) | 112 | 2.7 | 6 TB | Up to 24 drives |
| {: caption="Options for SAP-certified Cascade Lake bare metal servers - HANA and NetWeaver" caption-side="bottom"} | ||||
| {: tab-title="HANA and NetWeaver"} | ||||
| {: tab-group="SAP-certified Intel servers"} | ||||
| {: class="simple-tab-table"} | ||||
| {: #simpletabtable-sap-hana} |
CONTENT:
The uplink speed provides two options:
- 10 Gb, which is selected by default.
- 25 Gb, which is available only for specific pods and data center locations. The following table shows the available locations for the 25 Gb uplink speed. {: #uplink-speed-options-list}
| Data center | Pod |
|---|---|
| SYD04 | 01 |
| SYD05 | 01 |
| TOK02 | 02 |
| TOK04 | 01 |
| TOK05 | 01 |
| {: caption="Available locations for 25 Gb uplink speed - Asia Pacific" caption-side="bottom"} | |
| {: tab-title="Asia Pacific"} | |
| {: tab-group="Data centers"} | |
| {: class="simple-tab-table"} | |
| {: #simpletable-uplink-speed-locations-ap} |
| Data center | Pod |
|---|---|
| FRA02 | 02 |
| FRA04 | 01 |
| FRA05 | 01 |
| LON04 | 01 |
| LON06 | 01 |
| MAD02 | 01 |
| MAD04 | 01 |
| MAD05 | 01 |
| PAR04 | 01 |
| PAR05 | 01 |
| PAR06 | 01 |
| {: caption="Available locations for 25 Gb uplink speed - Europe" caption-side="bottom"} | |
| {: tab-title="Europe"} | |
| {: tab-group="Data centers"} | |
| {: class="simple-tab-table"} | |
| {: #simpletable-uplink-speed-locations-eur} |
| Data center | Pod |
|---|---|
| TOR04 | 01 |
| TOR05 | 01 |
| WDC04 | 05 |
| WDC06 | 01 |
| {: caption="Available locations for 25 Gb uplink speed - NA East" caption-side="bottom"} | |
| {: tab-title="NA East"} | |
| {: tab-group="Data centers"} | |
| {: class="simple-tab-table"} | |
| {: #simpletable-uplink-speed-locations-naeast} |
| Data center | Pod |
|---|---|
| DAL10 | 03 |
| DAL13 | 02 |
| DAL14 | 01 |
| {: caption="Available locations for 25 Gb uplink speed - NA South" caption-side="bottom"} | |
| {: tab-title="NA South"} | |
| {: tab-group="Data centers"} | |
| {: class="simple-tab-table"} | |
| {: #simpletable-uplink-speed-locations-nasouth} |
CONTENT:
CAUTION Managing any {{site.data.keyword.vmwaresolutions_short}} components (which were installed into your {{site.data.keyword.cloud_notm}} account when you ordered the instance) from outside the VMware Solutions console can make your environment unstable. The following activities are considered management activities:
- Adding, modifying, returning, or removing components
- Expanding or contracting instance capacity through adding or removing ESXi servers
- Powering off components
- Restarting services {: #caution-component-management}
CONTENT:
{{site.data.keyword.vmwaresolutions_full}} offers promotions for some add-on services. Promotional pricing offers a number of months at no cost for a service license, if the service has license charges. For more information, see Promotions for services. {: #para-promotion-services}
CONTENT:
When you delete a {{site.data.keyword.vcf-auto}} instance, the following components are released sequentially:
- All deployed services
- NFS storage
- The Support fee for NSX-T instances or the Support and Services fee for NSX-V instances
- VMware® product licenses
- VMware ESXi™ servers
- Subnets
- VLANs {: #deletinginstance-components-list}
Review the following information before you proceed.
- Any existing VLANs that you own, outside of {{site.data.keyword.vmwaresolutions_full}}, are not deleted.
- Any VLANs that contain your own resources, such as gateways or Veeam® servers are not deleted.
- Any VLANs or subnets without attached gateways or servers are deleted even though you might have IP addresses assigned to it from the subnets to your VMs. {: #deletinginstance-delete-vlans}
Because of resource dependencies, the components in your instance are not released immediately when you delete the instance. For example, the VLANs and the VLAN primary subnets cannot be deleted until the ESXi servers are fully reclaimed by the {{site.data.keyword.cloud_notm}} infrastructure, which happens at the end of the {{site.data.keyword.cloud_notm}} infrastructure billing cycle. At the end of the billing cycle, which is typically 30 days, the subnets and VLANs are deleted and the instance deletion is completed. {: #deletinginstance-delete-info}
You are billed until the end of the {{site.data.keyword.cloud_notm}} infrastructure billing cycle for the deleted instance. {: important} {: #deletinginstance-important-note}
CONTENT:
Whenever possible, add ESXi servers by using the {{site.data.keyword.vmwaresolutions_full}} console because changes that you make on the VMware vSphere® Web Client are not synchronized with the VMware Solutions console. Therefore, add ESXi servers to vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the VMware Solutions console. {: important} {: #para-vcenteraddESXiservers}
Whenever possible, remove ESXi servers by using the {{site.data.keyword.vmwaresolutions_full}} console because changes that you make on the VMware vSphere® Web Client are not synchronized with the VMware Solutions console. Therefore, remove ESXi servers from vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the VMware Solutions console. {: important} {: #para-vcenterremoveESXiservers}
CONTENT:
Whenever possible, add clusters by using the {{site.data.keyword.vmwaresolutions_full}} console and not the VMware vSphere® Web Client. Changes that you make on the vSphere Web Client are not synchronized with the VMware Solutions console. If you want to add clusters to {{site.data.keyword.vcf-auto}} instances by using the vSphere Web Client, do so only for on-premises clusters or clusters that you don't manage in the VMware Solutions console. {: important} {: #para-vcenteraddclusters}
Whenever possible, delete clusters by using the {{site.data.keyword.vmwaresolutions_full}} console and not the VMware vSphere® Web Client. Changes that you make on the vSphere Web Client are not synchronized with the VMware Solutions console. If you want to delete clusters from {{site.data.keyword.vcf-auto}} instances by using the vSphere Web Client, do so only for on-premises clusters or clusters that you don't manage in the VMware Solutions console. {: important} {: #para-vcenterremoveclusters}
CONTENT:
You can also specify an instance name that meets the following requirements:
- Only lowercase alphabetic, numeric, and hyphen (-) characters are allowed.
- No consecutive hyphens are allowed.
- The instance name must start with a lowercase alphabetic character.
- The instance name must end with a lowercase alphabetic or numeric character.
- The maximum length of the instance name is 10 characters.
- The instance name must be unique within your account. {: #orderinginstance-inst-name-list}
CONTENT:
You can also specify a cluster name that meets the following requirements:
- Only lowercase alphabetic, numeric, and hyphen (-) characters are allowed.
- The cluster name must start with a lowercase alphabetic character.
- The cluster name must end with a lowercase alphabetic or numeric character.
- The maximum length of the cluster name is 10 characters.
- The cluster name must be unique within your account. {: #orderinginstance-cluster-name-list}
CONTENT:
You can also specify a new cluster name that meets the following requirements:
- Only lowercase alphabetic, numeric, and hyphen (-) characters are allowed.
- The cluster name must start with a lowercase alphabetic character.
- The cluster name must end with a lowercase alphabetic or numeric character.
- The maximum length of the cluster name is 30 characters.
- The cluster name must be unique within the {{site.data.keyword.vcf-auto}} instance. {: #cluster-name-requirements-list}
CONTENT:
Use resource groups to organize the resources in your account for access control and billing purposes. The default resource group in your account is selected. You can also select another resource group according to your needs. The resource group that you select cannot be changed after the instance is created. {: #para-orderinginstance-resource-group}
If No resource group available is displayed in this field, you currently do not have permissions to any resource group in this account. Contact the account owner to be assigned an Editor or Administrator role on a resource group in the account. For more information, see {{site.data.keyword.cloud_notm}} IAM roles. {: note} {: #note-orderinginstance-resource-group}
Click Browse configurations to open the configuration manager side panel. Here, you can choose a configuration from the list of saved templates to update it and then save it as a new configuration template. {: #paraone-orderinginstance-inst-config}
If you do not see any configurations in the list, then you do not have any saved templates and might want to create one. To create a configuration, first specify the settings for your instance as a configuration template without placing an order. To save the settings, click Save configuration on the Summary pane. {: #paratwo-orderinginstance-inst-config}
Select whether to order a new primary instance or a secondary instance for an existing primary instance. {: #para-orderinginstance-primary-secondary}
CONTENT:
-
If you are planning to use vSAN™ OSA storage, you can order 4-51 servers.
-
If you are planning to use vSAN ESA storage, you can order 3-51 servers.
-
If you are planning to use NFS storage, you can order 3-51 servers.
-
All servers that you order have the same configuration. {: #number-of-baremetal-servers-consol}
-
If you are planning to use vSAN™ OSA storage, you can order 4-59 servers.
-
If you are planning to use vSAN ESA storage, you can order 3-59 servers.
-
If you are planning to use NFS storage, you can order 2-59 servers.
-
All servers that you order have the same configuration. {: #number-of-baremetal-servers-wkld}
CONTENT:
The time to complete the upgrade is unknown. It is possible that it might take several maintenance windows to completely upgrade an environment. Running up-leveled and down-leveled versions of the SDDC software is supported by VMware® during the upgrade process. However, some functions such as vMotion, might be limited during this process. {: #para-vcs80upgrade-prereq}
CONTENT:
vCenter Server 7 is selected by default. {: #para-vcsversion80-vcsline1}
For new instances, vCenter Server 8 is available to order. However, for existing instances or clusters with vCenter Server 7, you can add only vCenter Server 7 clusters or hosts. {: #para-vcsversion80-vcsline2}
CONTENT:
As of 28 March 2024, {{site.data.keyword.vm-shared}} is not available for new deployments. Support for existing instances is extended until 28 February 2025. All customer and management data, including the backups of workloads, will be deleted in March 2025. Migrate all your {{site.data.keyword.vm-shared}} resources to {{site.data.keyword.vmware-service_full}} by 28 February 2025. For more information, see End of Support for {{site.data.keyword.vm-shared}} deployments. {: deprecated} {: #shared-deprecated-note}
CONTENT:
The VMware® licensing model is changed. You are entitled to the VMware software products that are included in the VMware Cloud Foundation™ bundle. To request VMware NSX® license upgrades and other licensing changes, open an IBM Support ticket by following the steps in Getting help and support. {: #vmware-licensing}
Bring Your Own License (BYOL) is no longer supported except for migrations or upgrades of existing BYOL clusters. Use this feature only if you are upgrading or migrating an existing BYOL cluster. {: attention} {: #attnnote-byol}
Bring Your Own License (BYOL) is no longer supported except for migrations or upgrades of existing BYOL clusters. Add a host to a BYOL cluster only if you are upgrading or migrating an existing BYOL cluster. {: attention} {: #attnnote-addhost-byol}
The automated deployment process is not supported for BYOL (Bring Your Own License). You must complete the HCX deployment process manually. {: important} {: #impnote-deploymanual-hcx}
As of 28 March 2024, the {{site.data.keyword.at_full_notm}} service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to {{site.data.keyword.logs_full_notm}} before 30 March 2025. During the migration period, customers can use {{site.data.keyword.at_full_notm}} along with {{site.data.keyword.logs_full_notm}}. Activity tracking events are the same for both services. For information about migrating from {{site.data.keyword.at_full_notm}} to {{site.data.keyword.logs_full_notm}} and running the services in parallel, see migration planning. {: important} {: #impnote-at-deprecation}
As of 28 March 2024, the {{site.data.keyword.la_full_notm}} service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to {{site.data.keyword.logs_full_notm}} before 30 March 2025. During the migration period, customers can use {{site.data.keyword.la_full_notm}} along with {{site.data.keyword.logs_full_notm}}. Logging is the same for both services. For information about migrating from {{site.data.keyword.la_full_notm}} to {{site.data.keyword.logs_full_notm}} and running the services in parallel, see migration planning. {: important} {: #impnote-la-deprecation}
The storage architecture can be either vSAN ESA (Express Storage Architecture) for instances with vSphere 8 or vSAN OSA (Original Storage Architecture) for instances with vSphere 7 and 8. {: #storage-arch-spr-intro}
Review the following considerations for the vSAN storage architectures:
- For Sapphire Rapids servers, both vSAN ESA and vSAN OSA are available. For Cascade Lake servers, only vSAN OSA is available.
- vSAN ESA requires a minimum of 3 bare metal servers. vSAN OSA requires a minimum of 4 bare metal servers.
- For both vSAN ESA and vSAN OSA, you can select the size for and number of vSAN capacity disks. For vSAN OSA, the size and number of vSAN cache disks are selected by default.
- For vSAN ESA, the Enable vSAN compression option is available. For vSAN OSA, the Enable vSAN deduplication and compression option is available.
- vSAN ESA is selected by default with the 25 Gb uplink speed. If you select the 10 Gb uplink speed, the vSAN storage architecture is changed to vSAN OSA, because vSAN ESA is not compatible with the 10 Gb uplink speed. {: #storage-arch-spr}