Setting up the DNS and DHCP for IBM Storage Fusion HCI System
As a prerequisite to IBM Storage Fusion HCI System installation, update Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) with the information that is detailed in the planning worksheet for your system.
Before you begin
Download the installation preparation worksheet and review the network preparation section. To download the worksheets, see IBM Storage Fusion HCI Installation worksheets.
- Ensure that you have the MAC addresses from your IBM Technical Seller with whom you engaged
with. If you do not have your IBM Technical Seller contact information, see the planning worksheets
for contact details.
To download the worksheets, see IBM Storage Fusion HCI Installation worksheets.
For DHCP configuration of bootstrap VM, you must use the MAC address of Bootstrap that is provided in the mail from IBM Technical Seller. For example,
Bootstrap 00:16:3e:11:4d:dd. - The sample files that are used in this section are based on standard DNS/DHCP services available on Red Hat® Enterprise Linux 8.
About this task
You can access IBM Storage Fusion
OpenShift® Container Platform cluster nodes on your network. As such,
each cluster node requires an IP address that is accessible on this network. During installation,
each cluster node obtains its IP address from an external DHCP server based on the MAC address of
the cluster node. As a prerequisite for IBM Storage Fusion HCI System
installation, you must reserve few IP addresses for OpenShift:
Note: All these IPs must be in the
same range.
- One IP address for the OpenShift API
server endpointFor example:
- API in DNS lookup file.
api IN A 10.44.100.143 - API in DNS reverse lookup file.
143 IN PTR api.isf.mycompany.com.
- API in DNS lookup file.
- One IP address for the wildcard ingress endpoint (to access your workloads)For example, ingress in DNS.
; Ingress LB (apps) *.apps IN A 10.44.100.144 - One IP address for each cluster node (control, compute, AFM, and GPU nodes)
- One IP address for the bootstrap node (it is temporary and is only required during the OpenShift Container Platform installation)For example:
- Bootstrap in
DHCP.
host bootstrap.isf.mycompany.com { option host-name "bootstrap.isf.mycompany.com"; hardware ethernet 00:16:3e:e0:31:65; fixed-address 10.44.100. 151; } - Bootstrap in DNS lookup.
bootstrap IN A 10.44.100.151 - Bootstrap in DNS reverse
lookup.
151 IN PTR bootstrap.isf.mycompany.com.
- Bootstrap in
DHCP.
Note:
- For each cluster node and the bootstrap node, you must add DHCP reservations to your DHCP configuration.
A single sample DHCP reservation record for a cluster node looks similar to the following
example:
host control-1-ru2.isf.mycompany.com { option host-name "control-1-ru2.isf.mycompany.com"; hardware ethernet 04:3f:72:f7:2f:76; fixed-address 10.44.100.145;}IBM provides the node's hostname (for example, control-1-rux) and hardware Ethernet (MAC) address and you cannot change them. The fixed-address that you provide is the IP address that gets assigned to the cluster node.
A fully functional DNS environment is a requirement for IBM Storage Fusion HCI System and OpenShift Enterprise to work correctly. Adding entries into the /etc/hosts file is not enough because that file is not copied into containers that are running on the platform. For more information about DHCP and DNS, see OpenShift documentation.
Mapping of rack unit with OpenShift host
name in a single rack:
| Rack unit | Host name | Node type |
|---|---|---|
| RU2 | control-1-ru2.<domainname> | Storage |
| RU3 | control-1-ru3.<domainname> | Storage |
| RU4 | control-1-ru4.<domainname> | Storage |
| RU5 | compute-1-ru5.<domainname> | Storage |
| RU6 | compute-1-ru6.<domainname> | Storage |
| RU7 | compute-1-ru7.<domainname> | Storage |
| RU8 | compute-1-ru8.<domainname> | Storage or compute-only |
| RU9 | compute-1-ru9.<domainname> | Storage or compute-only |
| RU10 | compute-1-ru10.<domainname> | Storage or compute-only |
| RU11 | compute-1-ru11.<domainname> | Storage or compute-only |
| RU12 | compute-1-ru12.<domainname> | Storage or compute-only |
| RU13 | compute-1-ru13.<domainname> | Storage or compute-only |
| RU14 | compute-1-ru14.<domainname> | Storage or compute-only |
| RU15 | compute-1-ru15.<domainname> | Storage or compute-only |
| RU16 | compute-1-ru16.<domainname> | Storage or compute-only |
| RU17 | compute-1-ru17.<domainname> | Storage or compute-only |
| RU23 | compute-1-ru23.<domainname> | AFM |
| RU24 | compute-1-ru24.<domainname> | AFM |
| RU25* | compute-1-ru25.<domainname> | GPU |
| RU27* | compute-1-ru27.<domainname> | GPU |
| RU29 | compute-1-ru29.<domainname> | Storage or compute-only |
| RU30 | compute-1-ru30.<domainname> | Storage or compute-only |
| RU31** | compute-1-ru31.<domainname> | Storage or compute-only |
| RU32** | compute-1-ru32.<domainname> | Storage or compute-only |
* GPU nodes occupy two rack units.
** Nodes are mutually exclusive with the GPU nodes.
For a high availability multi rack cluster, mapping of rack unit with OpenShift host name:
| Rack unit | Host name | Node type | ||
|---|---|---|---|---|
| Rack 1 | Rack 2 | Rack 3 | ||
| RU2 | control-1-ru2.<domainname> | control-2-ru2.<domainname> | control-3-ru2.<domainname> | Storage |
| RU3 | compute-1-ru3.<domainname> | compute-2-ru3.<domainname> | compute-3-ru3.<domainname> | Storage |
| RU4 | compute-1-ru4.<domainname> | compute-2-ru4.<domainname> | compute-3-ru4.<domainname> | Storage |
| RU5 | compute-1-ru5.<domainname> | compute-2-ru5.<domainname> | compute-3-ru5.<domainname> | Storage |
| RU6 | compute-1-ru6.<domainname> | compute-2-ru6.<domainname> | compute-3-ru6.<domainname> | Storage |
| RU7 | compute-1-ru7.<domainname> | compute-2-ru7.<domainname> | compute-3-ru7.<domainname> | Storage |
| RU8 | compute-1-ru8.<domainname> | compute-2-ru8.<domainname> | compute-3-ru8.<domainname> | Storage or compute-only |
| RU9 | compute-1-ru9.<domainname> | compute-2-ru9.<domainname> | compute-3-ru9.<domainname> | Storage or compute-only |
| RU10 | compute-1-ru10.<domainname> | compute-2-ru10.<domainname> | compute-3-ru10.<domainname> | Storage or compute-only |
| RU11 | compute-1-ru11.<domainname> | compute-2-ru11.<domainname> | compute-3-ru11.<domainname> | Storage or compute-only |
| RU12 | compute-1-ru12.<domainname> | compute-2-ru12.<domainname> | compute-3-ru12.<domainname> | Storage or compute-only |
| RU13 | compute-1-ru13.<domainname> | compute-2-ru13.<domainname> | compute-3-ru13.<domainname> | Storage or compute-only |
| RU14 | compute-1-ru14.<domainname> | compute-2-ru14.<domainname> | compute-3-ru14.<domainname> | Storage or compute-only |
| RU15 | compute-1-ru15.<domainname> | compute-2-ru15.<domainname> | compute-3-ru15.<domainname> | Storage or compute-only |
| RU16 | compute-1-ru16.<domainname> | compute-2-ru16.<domainname> | compute-3-ru16.<domainname> | Storage or compute-only |
| RU17 | compute-1-ru17.<domainname> | compute-2-ru17.<domainname> | compute-3-ru17.<domainname> | Storage or compute-only |
| RU23 | compute-1-ru23.<domainname> | compute-2-ru23.<domainname> | compute-3-ru23.<domainname> | AFM |
| RU24 | compute-1-ru24.<domainname> | compute-2-ru24.<domainname> | compute-3-ru24.<domainname> | AFM |
| RU25* | compute-1-ru25.<domainname> | compute-2-ru25.<domainname> | compute-3-ru25.<domainname> | GPU |
| RU27* | compute-1-ru27.<domainname> | compute-2-ru27.<domainname> | compute-3-ru27.<domainname> | GPU |
| RU29 | compute-1-ru29.<domainname> | compute-2-ru29.<domainname> | compute-3-ru29.<domainname> | Storage or compute-only |
| RU30 | compute-1-ru30.<domainname> | compute-2-ru30.<domainname> | compute-3-ru30.<domainname> | Storage or compute-only |
| RU31** | compute-1-ru31.<domainname> | compute-2-ru31.<domainname> | compute-3-ru31.<domainname> | Storage or compute-only |
| RU32** | compute-1-ru32.<domainname> | compute-2-ru32.<domainname> | compute-3-ru32.<domainname> | Storage or compute-only |