Using IPv6 with Management Console

Management Console 20.07 and newer versions support pure IPv4 or pure IPv6 networks; hybrid or dual stacked networks are not supported. In a pure IP deployment, Management Console only stores and displays the PCoIP endpoint data that is relevant to the IP version of the Management Console NIC. This means that when migrating between networks, data that is not relevant to the new network is permanently deleted. Please see Deleted Data When Migrating between IP Protocols for details.

Management Console will automatically display the IP information such as ip addresses relative to it's configured NIC. For example, if the NIC is configured for IPv6, all endpoint properties will display their IPv6 information. Searching for PCoIP endpoints will only display properties for endpoints in IP-only networks.

Management Console supports DHCPv6 with and without SLAAC configurations. The Web UI can be accessed by either a manual, DHCPv6, or SLAAC IPv6 address depending on the network configuration and the Management Console NIC configuration.

Management Console Host Requirements

  • Only one NIC can be configured with one IP version

  • Must be able to ping and communicate with PCoIP endpoints

  • Must have an internet connection

  • Firewall must be configured before installing Management Console

  • PCoIP endpoints must be using firmware 20.07 or higher


In an environment with DHCPv6 without SLAAC, there is a limitation between the caching systems of the Management Console CentOS host operating system and administrators using Windows-based clients to access the Web UI. This limitation prevents a connection on the initial connection to the Management Console Web UI. This limitation requires any of two work arounds to fix the issue.

  1. Configure a static route from the Management Console CentOS host operating system to Windows host (MC Client). This can be done by issuing a command similar to:

    sudo ip -6 route add via link local address of Windows host dev Ethernet name in CentOS


    sudo ip -6 route add 3505:b900:9000:19::/64 via fe80::e887:4e5d:fab7:cc dev eth0

  2. From the Management Console host operating system, ping the administrators Windows computer that is accessing the Management Console Web UI prior to the first connection.

Information on IPv6 is included in the Installation and Migration topics for all formats of Management Console.