TCA 3.0 introduces support for IPv6 VNFs. Starting VMware Telco Cloud Automation 3.0 catalogs with IPv6 network configuration/interfaces is supported.
For vCenter and Cloud Director-based VIMs, users can instantiate IPv6 VNF catalogs and create IPv6 networks to further allocate these to VNFs.
User also can perform VNF lifecycle management operations such as Terminate, Scale, Heal and Operate for the VNFs that have IPv6 interfaces.
VMware Telco Cloud Automation 3.0 has introduced new implicit Workflows for SCP and SSH, which can be leveraged by IPv6 VNFs. These new Workflows do not rely on an external VMware Aria Automation Orchestrator (previously known as vRealize Orchestrator, or simply vRO).
While designing a VNF catalog via the TCA UI, users can choose to have the newly introduced IPv6 entries in the following scenarios:
Creating/ Configuring a Virtual Link
When creating/configuring a virtual link, the “Select Layer Protocol” entry has a dropdown to choose the IPv6 option from.
To successfully complete the configuration process, the CIDR entry provided by the user must be a valid IPv6 address.
Gateway IP and IP Allocation Pools are optional fields. For the Gateway IP value, the user should enter an IPv6 address within the already provided CIDR range. The IP Allocation Pools should contain valid start and end addresses that fall within the CIDR range.
Configuring a VDU
While configuring a VDU, the user creates IPv6 virtual links, and then can connect/attach the VNF VDU to these links using the add internal connection (ICP) option in the edit VDU feature.