Every component of the Telco Cloud stack has its own IPv4-IPv6 support matrix.
IPv6 was defined by the Internet Engineering Task Force (IETF) to overcome the IPv4 limitations like the number of available address space. IPv6 also provides improved address autoconfiguration between nodes.
In the Telco Cloud, VNFs and CNFs can communicate in multiple ways using IPv4 and IPv6 protocols, leveraging the capabilities of the platform components:
VNFs deployed on top of VMware Cloud Director or VMware Integrated OpenStack deployments: separate vNICs for each address family or a dual stack configuration with DHCP or static assignment
CNFs deployed through VMware Telco Cloud Automation on to the CaaS infrastructure.
NSX: single or dual stack for overlay or VLAN segment with Standard or EDP configuration
NSX Advanced Load Balancer: single or dual stack for Load Balancer
Several options are available at the VNF and CNF level to consume IPV4 and IPv6 communications. Some constrains apply on the management component interactions. The following table summarizes the address family capabilities of the management components. IPv4 is standard for all components.
Components |
Release |
IPv6 only |
Dual Stack |
Notes |
|---|---|---|---|---|
ESXi |
8.0b |
X |
X |
|
vCenter Server |
8.0b |
X |
||
NSX |
4.1.0.2 |
X |
Management Plane and Control Plane TEP supports only IPv4. |
|
Telco Cloud Automation |
2.3 |
X |
X |
|
Tanzu Kubernetes Grid |
2.1.1 |
X |
Management and Workload clusters must have the same Address Family. |
|
Aria Operations |
8.10 |
X |
X |
All nodes in the cluster must follow the Address Family. |
Aria Operations for Logs |
8.10 |
X |
X |
|
Aria Automation Orchestrator |
8.11 |
|||
Aria Operations for Networks |
6.9 |
X |
X |
|
VMware Cloud Director |
10.4.1 |
|||
Bare Metal Automation |
3.0 |
|||
VMware Integrated OpenStack |
7.3 |
|||
NSX Advanced Load Balancer |
22.1.3 |
|||
Avi Kubernetes Operator |
1.9.2 |
X |
X |
Management plane to NSX ALB can be IPv4 only. |
Due to the interaction of the components in a deployment and the limitations of some components, only part of the stack can be deployed in an IPv6 or a Dual Stack scenario.
Telco Cloud IPv6 Ingress in CaaS
The following diagram illustrates a deployment where IPv4 and IPv6 coexist. Some components are configured with dual stack and can communicate with components that have limitations in supported address families. Aria Automation Orchestrator is one such component that supports only IPv4. In the diagram, ESXi hosts are configured in IPv6 only since they are connected to vCenter, NSX, and TCA that are configured in Dual Stack.
Even if the TKG Workload is configured in IPv4, only the NSX Advanced Load Balancer enables to export IPv4, IPv6, and Dual Stack routes. This allows CNFs to export ingress VIPs in IPv4 and IPv6. The additional interfaces consumed by the CNFs with multus can be configured in IPv4 or IPv6 but not in a Dual Stack configuration. Both ingress and egress CNF communications of any address family can be aggregated over NSX gateways.
Telco Cloud IPv6 VNF
The following diagram illustrates a deployment where most of the management components are configured with IPv4. This is the result of limitation in some components such as VMware Cloud Director and Aria Automation Orchestrator.
Even if the management communications are managed with IPv4, the hosted VNFs can be configured with IPv4, IPv6, or dual stack. Several options are available to be consumed by VNFs:
Dual Stack Overlay segments
Dual stack Trunk VLANs configured with EDP
Dual stack load balancer configured on NSX Advanced Load Balancer
The VNF Manager can be configured with Dual Stack and it can communicate with the VNF over IPv6 and with VMware Cloud Director over IPv4.
Telco Cloud RAN IPv6
The following diagram illustrates an IPv6 environment where all the components are connected with IPv6 interfaces. Some components such as TCA Manager, TCA control plane, and vCenter might be configured in a dual stack configuration. Other components such as TKG Management and TKG Workload are both configured in IPv6 only since they are not supporting dual stack.
Aria Automation Orchestrator is not used in this example since it supports only IPv4. CNFs can use Javascript-based workflows directly from TCA.
