VMware Cloud Director Availability™ 4.2.1 | 12 AUG 2021 | Build 18422625 (Product version: 126.96.36.19910807-98aa4437ed)
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
VMware Cloud Director Availability 4.2.1 now supports NSX Data Center for vSphere in addition to NSX-T Data Center support for Stretching On-Premises Layer 2 Networks, with some operations* caveats and limitations.
This VMware Cloud Director Availability release also includes several resolved issues and updates of third-party libraries that provide security fixes.
VMware Cloud Director Availability 4.2.1 supports an in-place upgrade directly from versions 188.8.131.52, 184.108.40.206, 4.1.1, and 4.2. For more information, see Upgrading in the Cloud and Upgrading On-Premises.
Caveats and Limitations
* The Layer 2 VPN sessions have the following limitations in VMware Cloud Director Availability 4.2.1:
|NSX Edition||Can Stretch Routed Type Networks||Can Stretch Isolated Type Networks||Can Stretch Direct Type Networks|
|NSX-T Data Center||Yes||Yes, for NSX-T Data Center 3.1 and later||No|
|NSX Data Center for vSphere||Yes**||No||No|
** NSX Data Center for vSphere stretches only routed networks with interface type subinterface, not with interface type internal nor distributed.
** NSX Data Center for vSphere can stretch VXLAN and VLAN OrgVDC routed networks only connected to the trunk interface, and cannot stretch networks connected to the uplink nor to the internal interfaces. Guest VLAN Allowed must not be selected. If at some point Guest VLAN Allowed was selected, recreate the network from scratch.
- In more than one L2 VPN session, do not attempt to use/add the same organization VDC network, or a network segment, or in NSX-T it causes the following error message: Tunnel ID specified for L2 VPN [list] is already used by...
- The Autonomous Edge cannot distinguish between networks with the same vlan id. Editing the client L2 VPN session and switching from one on-premises network to another with the same vlan id is not reflected in the VMware Cloud Director Availability interface and the original network is still shown as stretched.
- Stretching on-premises standard switches port groups is not supported. Only DVS port groups are supported for stretching.
- One Autonomous Edge supports only one client L2 VPN session, stretching a maximum of 14 networks.
Note: The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. With earlier vSphere versions, to configure replications use the VMware Cloud Director Availability Portal.
For interoperability between paired sites with mismatching VMware Cloud Director Availability versions, see Managing Connections Between Cloud Sites.
For interoperability between VMware Cloud Director Availability and other VMware products, see VMware Product Interoperability Matrices.
For the tested uptime, concurrency, and scale limits, see VMware Configuration Maximums.
- Cannot display the MAC addresses in VM view for on-premises to cloud replications
In VM view, after creating an on-premises to cloud replication, when attempting to change the network settings you cannot see the MAC addresses listed next to the network interfaces.
- Changing the SLA profile does not update the retention policy settings
After changing the SLA profile from either Silver or Gold to an SLA profile that only preserves the latest instance, for example, Bronze, the retention policy settings do not update with the defined in the SLA profile.
- Changing the SLA profile of a replication applies retention policy but does not associate the updated SLA profile with the replication
After changing the SLA profile of a replication, the retention policy of the new SLA profile applies but the updated SLA profile does not associate with the replication and the SLA profile column displays N/A.