NSP deployment network addressing requirements

Using IPv4 and IPv6 in NSP deployments

The NSP supports IPv4 and IPv6 network connectivity with client applications and other components in the NSP architecture.

Deploying NSP with IPv6 network communications has the following limitations and restrictions:

• The deployer host for an NSP cluster must have IPv4 connectivity to NSP cluster nodes. The NSP cluster can be configured for IPv6 communications for NSP applications, but must have IPv4 connectivity to the deployer node.

• Common web browser applications have security policies that may prevent the use of bracketed IPv6 addresses in the URL browser bar. Customers that use IPv6 networking for client communications to NSP must use hostname configuration for NSP components.

• All NSP components in an NSP deployment must use IPv4 or IPv6 for inter-component communications. Different integrated components in an NSP deployment cannot communicate between IPv4 and IPv6 interchangeably (example: if NSP is deployed with IPv6, then NFMP also needs to be deployed with IPv6.).

• The NSP kubernetes cluster communications uses internal addressing in 10.233.0.0/18 subnet. Customers should avoid using this subnet in their NSP deployment on VM network interfaces.

• WS-NOC does not support IPv6 deployment. An integrated deployment of NSP with WS-NOC must be deployed with IPv4 addressing.

The NSP can be deployed with multiple network interfaces using IPv4 and IPv6 addressing. Chapter 7 of this guide documents the requirements and limitations of a multiple network interface NSP deployment.

VSR-NRC

For NSP to VSR-NRC communications, both IPv4 and IPv6 are supported. These protocols are also supported in communications between VSR-NRC and PCCs.