Vmware Cloud Foundation Edge (Vcfe) : Specific Program Documentation ("SPD")
Vmware Cloud Foundation Edge (Vcfe) : Specific Program Documentation ("SPD")
The Broadcom software program(s) (“Broadcom Software”) listed below is provided under the following terms and
conditions in addition to any terms and conditions referenced on the Broadcom quote, order form, statement of work, or
other mutually agreed ordering document (each a “Transaction Document”) under the applicable end user agreement or
governing contract (collectively, the “Agreement”) entered into by Customer and the Broadcom entity (“Broadcom”)
through which Customer obtained a license for the Broadcom Software. These terms shall be effective from the effective
date of such Transaction Document. Capitalized terms have the meanings ascribed to them herein, or, otherwise, in the
Agreement.
“BIOS” means the Basic Input Output System, a set of routines that boots the operating system and sets up the
hardware of the Processor.
“Cluster” is a software grouping of Servers running vSphere and/or vSAN for the purpose of resource sharing.
“Cloud Services” means computing infrastructure and platform services (such as compute resources, storage
capabilities, databases or virtual machines and other computing infrastructure and platform services) that a third
party makes available for consumption by customers.
“Edge Location” means Customer’s remote physical banking or retail branch stores, automated teller machines,
fulfillment lines, manufacturing lines, power substations, or federal or state government remote tactical mobile
units. Edge Location does not include dedicated facilities whose sole purpose is the hosting and the provision of
compute services, such as data centers, and colocation facilities, regardless as to whether such services are for
internal or external purposes.
“Instance” means a single installation of the Software on a physical server or Virtual Machine.
“Internally Developed Application” means: i) a computer application that Customer has created or developed
and (ii) a third-party computer application(s) that is ancillary to Customer’s application-based service, and (b)
cannot be accessed directly by end users of Customer’s application-based service.
“Processor” means a single, physical chip that houses at least one Core that can execute computer programs.
“Server” means a hardware system capable of running the server software. A hardware partition or blade is
considered a separate hardware system.
“TiB” means a unit of physical storage capacity that is equal to 2^40 bytes.
“Virtual Desktop Infrastructure” or “VDI” means a technology that utilizes virtual machines to manage and
provide virtual desktops.
“Virtual Machine” means a software container that can run its own operating system and execute applications
like a physical machine.
● Each Core on the Server must be licensed, including Cores deactivated by the BIOS. The required number of Core
licenses equals the number of Cores on the Server, subject to the minimum of 16 Core licenses per Processor.
● VCFE is sold as a single product; the integrated components and capabilities can only be deployed on the same
physical Cores where the vSphere in VCFE Core license is deployed.
● Customers may use VCFE on a Server with up to the number of Cores for which Customer has paid the applicable
license fees.
● Customer may only use or deploy VCFE either in a Edge Location or in a VDI environment, and each of those
possible uses are subject to the restrictions below (which, for clarity, is in addition to any other restrictions defined
herein). For clarity, VCFE may not be used for any purpose other than 1) use in an Edge Location, or 2) use in a
VDI environment.
● Component Specific License Notes. The following table describes additional component specific license
entitlement rights and limitations of VCFE:
2
VCF Metric
# Component Entitlement Entitlement Details
1 vSAN 1 TiB Customer is entitled to 1 TiB of vSAN capacity for each Core licensed for VCFE.
vSAN can only be aggregated and deployed across Cores where the vSphere for
VCF Edge is deployed.
2 Aria Suite 1 Core ● Aria Suite Enterprise and Aria Operations for Networks (“Aria
Enterprise Capabilities”) contained in this VCFE can only manage the same Cores
where the vSphere in VCFE Core license is deployed. Notwithstanding
the foregoing, Customer is entitled to deploy Aria Capabilities on-prem
and manage the equivalent number of Cores as the number of Core
licensed for this VCFE either: i) on-prem and/or ii) on Azure VMware
Solution, Google Cloud VMware Engine, and/or Oracle Cloud VMware
Solution (“MaaS Offerings”) at no additional cost until the earlier of the
expiration or termination of the subscription term or the date that the
MaaS Offering adopts Aria Capabilities as part of its integrated solution.
● For clarity, individual Aria Capability cannot be split to manage separate
Cores from VCFE (i.e. Aria Capabilities in a VCFE license entitlement
3 Aria 1 Core cannot be used to manage Cores licensed by another product (e.g.
Operations for vSphere Foundation, Standard, Essentials)).
Networks
4 vCenter Server 1 Instance vCenter Server may be used to provide centralized management capabilities to
any licensed VMware by Broadcom infrastructure environments with an active
subscription to Support and Subscription Services.
5 vSphere for 1 Core vSphere for vSAN Witness core licenses can only be used to support deploying
vSAN Witness the vSAN Witness appliance Virtual Machine at an Edge Location. Additional
VCFE Core licenses are not required in this situation. For clarity, the vSphere for
vSAN Witness license cannot be deployed in a data center environment.
● vSAN Cluster Expansion or Renewal Exception with VCFE. If the number of total VCFE subscriptions
purchased for the hosts added to, or renewed in, the vSAN Cluster using license entitlements from legacy offers
are greater than, or equal to, the total number of Processors in the vSAN Cluster, Customer has permission to use
any excess entitlements from the included vSAN capacity (1 TiB per 1 Core) in VCFE subscription purchase to
apply to the entire vSAN Cluster, consisting of existing and new or renewed hosts, for the sole reason to enable
vSAN Cluster expansion or renewal. At the time that the legacy offers expire (either SnS or subscription),
Customer must purchase VCFE subscriptions and apply the vSAN license entitlements for the hosts in the vSAN
Cluster that were previously using the license entitlements from the legacy offers.
● iSCSI Support. Customer may only use the iSCSI Support feature in vSAN with physical, non-virtualized Servers.
The iSCSI Support feature supports Microsoft clustering with shared disks. Initiators can be either from virtual
machines or physical servers. For guest initiators in virtual machines, those virtual machines can be residing on:
- The same vSAN Cluster that provides this iSCSI Support feature; or
- An external vSAN or vSphere Cluster.
The iSCSI Support is limited to a maximum of 128 sessions per Server, a maximum of 128 targets per Cluster, and
a maximum of 1024 logical unit numbers (LUNs) per cluster. The vSAN Stretched Clusters using iSCSI target
service are not supported. raw device mapping (RDMs) for Microsoft Windows Server Failover Clustering (WSFC)
using iSCSI target service is not officially supported on vSAN.
● Restrictions on Use with Cloud Services. Customer must not (and must not allow Customer’s Third-Party
Agents to) use or deploy the Software on any Cloud Services.
● Export restrictions and restrictions on use of NSX Software. VMware NSX Software is of United States Origin
and contains some features (including features which support network infrastructure) which result in the application
of stricter export control classifications pursuant to the United States Export Administration Regulations (EAR). For
some uses of the VMware NSX Software, such as for use by “More Sensitive” Government End Users as defined
3
in Part 772 of the EAR, there may be restrictions or prohibitions applicable to Customer’s proposed use of the
Software if that use is in or for certain Group D:1 countries (which include China or Russia) where VMware’s Bulk
Export License may not be used. Customer is responsible for ensuring that Customer’s proposed use of the
VMware NSX Software is not in violation of applicable United States or local law.
● Hosting Rights and Restrictions. Customer may use the Software to deliver Internally Developed Applications as
a service to a third party via an internal or external network. Except as expressly provided in this paragraph and the
License Agreement, the use of the Software for any other types of hosting or for the benefit of any third party in any
manner is strictly prohibited.
● VMware Tools. VMware Tools is a suite of utilities and drivers that can be installed in a Guest Operating System
to enhance the performance and functionality of a Guest Operating System when running in a Virtual Machine in
conjunction with a vSphere hypervisor. Customer may not use VMware Tools with any other hypervisor.
Customer may distribute the VMware Tools to third parties solely when installed in a Guest Operating System
within a Virtual Machine. Customer is liable for compliance by those third parties with the terms and conditions of
the Framework Agreement.