Typically, HCP is included as a subdomain in your DNS. If this is not the case
•For system-level access, you can use an IP address in the URL, or you can use the [hcp_system] network domain name in the URL and use a hosts file to define mappings of one or more node IP addresses to that domain name.
•For tenant-level access, you need to use the tenant management network domain name in the URL and use a hosts file to define mappings of one or more node IP addresses to that domain name.
The location of the hosts file depends on the client operating system:
•On Windows, by default: c:\windows\system32\drivers\etc\hosts
•On Mac OS® X: /private/etc/hosts
![]() |
Note:
|
Hostname mappings
Each entry in a hosts file is a mapping of an IP address to a hostname. For HCP, the hostname must be the fully qualified domain name (FQDN) for the
Each hosts file entry you create for access to
•A
•The FQDN of the domain
For example, if the
192.168.210.16 |
|
2001:0db8::101 |
|
You can include comments in a hosts file either on separate lines or following a mapping on the same line. Each comment must start with a number sign (#). Blank lines are ignored.
Hostname mapping considerations
In the hosts file, you can map IP addresses for any number of nodes to a single domain name. The way a client uses multiple IP address mappings for a single domain name depends on the client platform. For information about how your client handles hosts file entries that define multiple IP address mappings for a single domain name, see your client documentation.
If any of the HCP nodes listed in the hosts file are unavailable, timeouts may occur when you use a hosts file to access the system through the management API.
Sample hosts file
Here’s a sample hosts file that contains mappings
# HCP system-level mappings |
|
192.168.210.16 |
admin.hcp.example.com |
192.168.210.17 |
admin.hcp.example.com |
192.168.210.18 |
admin.hcp.example.com |
192.168.210.19 |
admin.hcp.example.com |
2001:0db8::101 |
admin.hcp.example.com |
2001:0db8::102 |
admin.hcp.example.com |
2001:0db8::103 |
admin.hcp.example.com |
2001:0db8::104 |
admin.hcp.example.com |
|
|
# tenant-level mappings |
|
192.168.210.16 |
finance.hcp.example.com |
192.168.210.17 |
finance.hcp.example.com |
192.168.210.18 |
finance.hcp.example.com |
192.168.210.19 |
finance.hcp.example.com |
2001:0db8::101 |
finance.hcp.example.com |
2001:0db8::102 |
finance.hcp.example.com |
2001:0db8::103 |
finance.hcp.example.com |
2001:0db8::104 |
finance.hcp.example.com |
|
|
192.168.210.16 |
hr.hcp.example.com |
192.168.210.17 |
hr.hcp.example.com |
192.168.210.18 |
hr.hcp.example.com |
192.168.210.19 |
hr.hcp.example.com |
2001:0db8::101 |
hr.hcp.example.com |
2001:0db8::102 |
hr.hcp.example.com |
2001:0db8::103 |
hr.hcp.example.com |
2001:0db8::104 |
hr.hcp.example.com |
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.