Considerations for virtual networking

The following considerations apply to virtual networking with HCP:

The IP mode of a front-end network determines the type of IP addresses that can be used to communicate with HCP over that network. Before selecting a specific network for a specific purpose, you need to ensure that all devices that need to communicate with HCP for that purpose are configured to use at least one type of IP address supported by that network.

HCP accepts communications from Active Directory only on the [hcp_system] network. Therefore, if a tenant is configured to use AD for user authentication, that tenant must also be configured to use either the [hcp_system] network or an alias for that network for both management and data access purposes. In addition, each Active Directory domain controller used for HCP user authentication must have at least one IPv4 or IPv6 address that is routable from the [hcp_system] network.

When using HCP Data Migrator to copy objects between namespaces owned by different tenants, a client must have visibility into the data access networks for both tenants.

HCP Data Migrator does not support the use of IPv6 networks for communication with HCP. Therefore, to use HCP Data Migrator to access namespaces owned by a given tenant, that tenant must have IPv4 addresses defined for its data access network.

In addition, if the data access network for a tenant has both IPv4 and IPv6 addresses, HCP Data Migrator cannot use a domain name to connect to any namespace owned by that tenant. Instead, HCP Data Migrator must be configured to connect to each namespace using the IPv4 addresses assigned to the nodes for the data access network.

After HCP is upgraded from release 6.x to release 7.0 or later, by default, the HCP system is configured to support only IPv4 addresses for front-end networks. If you need to use IPv6 addresses for communication between HCP and other devices over the [hcp_system] network or any user-defined network, you need to ensure that when the upgrade is complete, your authorized HCP service provider configures HCP to enable support for IPv6 addresses and then configures the [hcp_system] network to use IPv6 addresses.

When a new node is added to the HCP system, it automatically has IP addresses on each subnet defined for the [hcp_system] network. However, it does not have any IP addresses for any user-defined front-end networks. Those networks, therefore, become partial networks. You can assign IP addresses to the new node for each of those networks at any time.

For considerations related to replicating an HCP system that uses virtual networking, see Network aliases and Replicating Tenants and Namespaces.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.