The [hcp_system] network is always used for:
•Access to the HCP System Management Console
•Access to the Tenant Management Console for the default tenant
•Access to the HCP management API using a system-level URL
•Syslog functions at the system and tenant levels
•SNMP functions at the system and tenant levels
•Access to the default namespace using the namespace access protocols
•Access to the HCP metadata query API using a system-level URL
•Access to the HCP Search Console using a system-level URL
•Access to the default namespace using HCP Data Migrator
•Communication between HCP and Active Directory for configuration and for user authentication at the system and tenant levels
•Communication between HCP and RADIUS servers for user authentication at the system and tenant levels
•For SAIN systems, communication between HCP and the storage arrays
•Communication between HCP and any external storage components configured for the system
•Communication between HCP and Hitachi Tiered Storage Manager
•Communication between HCP and Hitachi Device Manager (HDvM)
•Communication between HCP and Hi-Track®
•Access to the HCP system through interfaces reserved for authorized service providers
You can choose to use [hcp_system] or any user-defined network for the following purposes:
•Management of a given HCP tenant, including:
oAccess to the Tenant Management Console for the tenant
oAccess to the HCP management API using a URL for the tenant
You select the network for this purpose when you create or modify the tenant.
•Access to the namespaces owned by a given HCP tenant, including access through:
oThe namespace access protocols
oThe Namespace Browser
oThe HCP metadata query API using a URL for the tenant
oThe HCP Search Console using a URL for the tenant
oHCP Data Migrator
You select the network for this purpose when you create or modify the tenant.
•Communication with other HCP systems in a replication topology. For information on selecting the network for this purpose, see Replicating Tenants and Namespaces.
You can use the same network for multiple purposes. If you don’t choose a network for a purpose, HCP uses [hcp_system] by default.
When you select a network for a given purpose, you need to ensure that your networking infrastructure is configured to allow client requests for that purpose to be routed to that network. HCP responds to each client request on the same network as the one on which the request arrived. Therefore, clients do not need to be on the same subnet as the network they are using to access the system, but they do need to be configured to use at least one IPv4 or IPv6 address that is routable from that network.
© 2016 Hitachi Data Systems Corporation. All rights reserved.