You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NetApp HCI provides a network settings page with an easy form to simplify network configuration. When you complete the easy form, NetApp HCI automatically populates much of the rest of the information on the network settings page. You can then enter final network settings and verify that the network configuration is correct before proceeding. You do not need to complete the form in its entirety.
16
+
NetApp HCI provides a network settings page with several sections to simplify network configuration. You can proceed through each section and enter information or assign IP addresses for hosts and nodes in each network.
17
17
18
18
.What you'll need
19
19
* You have obtained the following information:
20
20
** The planned naming prefix for the hosts and storage cluster
21
21
** All planned subnet mask, starting IP address, default gateway, and VLAN IDs for the management, iSCSI, and vMotion networks
22
-
** The IP address, default gateway, VLAN IDs, and subnet mask information for any planned VMware vCenter deployment
22
+
** The subnet mask, IP address, default gateway, and VLAN IDs for any planned VMware vCenter deployment
23
23
** The Network Time Protocol (NTP) server address for NetApp HCI
24
24
** The DNS server IP address information for NetApp HCI
25
25
* If you are deploying a vSphere Distributed Switch, you have a vSphere Enterprise Plus license ready to apply after deployment is complete.
26
26
* If you assigned VLAN IDs to node ports during terminal user interface (TUI) configuration, you have configured those ports with the same VLAN ID during network configuration. You do not need to configure tagged host ports as access ports or native VLANs on the connected switch ports.
27
27
* You have verified that your network switch configuration is correct. Incorrect switch configurations (such as incorrect VLANs or MTU size) will cause deployment errors.
28
28
29
29
.About this task
30
-
If you selected the two-cable network topology for compute nodes, you must use VLAN IDs for the vMotion and storage networks for all compute and storage nodes in the deployment (VLAN IDs are optional for the management networks).
30
+
If you selected the two-cable network topology for compute nodes, you need to use VLAN IDs for the vMotion and storage networks for all compute and storage nodes in the deployment (VLAN IDs are optional for the management networks). Note that NetApp HCI validates the IP addresses you enter during these steps, but you can disable this validation with the *Live network validation is* button. NetApp HCI also performs checks on other information that you enter during these steps, such as ensuring that no subnets overlap, ensuring that no VLAN IDs are assigned to multiple networks, and other basic validations.
31
31
32
32
NOTE: In environments that require host-side VLAN tagging before deployment, if you have configured VLAN IDs on compute and storage nodes so they are discoverable by the NetApp Deployment Engine, ensure you use the correct VLANs when configuring network settings in the NetApp Deployment Engine.
33
33
34
-
If you are deploying using a two-node or three-node storage cluster, you can complete IP address information for Witness Nodes on the *Network Settings* page after using the easy form.
34
+
If you are deploying a two-node or three-node storage cluster, you can complete IP address information for Witness Nodes on the *Network Settings* page.
35
+
36
+
NOTE: In the IP address assignment pages, information you enter in the *Automatically assign IP addresses* mode does not affect information entered in the *Manually assign IP addresses* mode, and vice versa. If you enter IP addresses in both modes, NetApp HCI uses the IP address information in whatever mode is active when you click *Continue* at the bottom of the page.
37
+
38
+
.Troubleshooting common problems
39
+
NetApp HCI performs checks on the information you enter on these pages. Here are some common problems and workarounds:
40
+
41
+
|===
42
+
|Problem |Workaround
43
+
44
+
|In automatic IP address assignment mode, after you enter a starting IP address, you see the message `IPs in the range are in use:` with a scrollable drop-down list of the in-use IP addresses.
45
+
|NetApp HCI has assigned a contiguous range of IP addresses, but one or more of those IP addresses is already in use. Free the in-use IP addresses and try again, or use manual IP address assignment mode to assign specific IP addresses.
46
+
47
+
|After entering a default gateway, you see the message `The gateway is not valid`.
48
+
a|The default gateway IP address either does not match the subnet you provided, or there is an issue with the network or server you need to resolve. See the following NetApp Knowledge Base articles for more information:
49
+
50
+
* https://kb.netapp.com/Advice_and_Troubleshooting/Hybrid_Cloud_Infrastructure/NetApp_HCI/Troubleshoot_Invalid_Gateway_in_NDE[Troubleshoot an invalid gateway in the NetApp Deployment Engine^]
51
+
* https://kb.netapp.com/Advice_and_Troubleshooting/Hybrid_Cloud_Infrastructure/NetApp_HCI/%22The_gateway_is_not_valid%22_during_NDE[The gateway is not valid in the NetApp Deployment Engine^]
52
+
53
+
|You complete several *Network Settings* configuration pages and realize that there is incorrect information on one of the previous pages in the sequence.
54
+
|Using the numbered page sequence at the top of the page, you can select a page that you have previously completed and change information there. When finished, you can click *Continue* on the completed pages to return to the current page.
55
+
|===
56
+
57
+
== Configure DNS and NTP settings
35
58
36
59
.Steps
37
-
. Optional: To disable live validation of network information you enter on this page, toggle the *Live network validation is* switch to *Off*.
38
-
. In the *Infrastructure Services* section of the *Network Settings* page, enter the DNS and NTP server information for NetApp HCI in the following fields:
60
+
61
+
. On the *DNS/NTP* page, enter the DNS and NTP server information for NetApp HCI in the following fields:
39
62
+
40
63
|===
41
64
|Field |Description
@@ -52,24 +75,14 @@ If you are deploying using a two-node or three-node storage cluster, you can com
52
75
|*NTP Server Address 2 (Optional)*
53
76
|An optional IP address or fully qualified domain name of the secondary NTP server for this infrastructure.
54
77
|===
55
-
. Click *To save time, launch the easy form* to enter fewer network settings.
56
-
+
57
-
The *Network Settings Easy Form* dialog box appears.
58
78
59
-
. Enter a naming prefix in the *Naming Prefix* field.
60
-
+
61
-
The naming prefix is applied to the name of each host and the name of the storage cluster. Naming prefixes have the following characteristics:
62
-
+
63
-
* Must start with a letter
64
-
* Can contain letters, numbers, and hyphens
65
-
* Cannot exceed 55 characters
66
-
. Choose one of the following options for assigning VLAN IDs.
67
-
+
68
-
At any time when using the form, click *Clear* next to a row to clear input from a row of fields.
69
-
+
79
+
== Assign VLAN IDs
80
+
On the *VLAN IDs* page, you can assign VLAN IDs to NetApp HCI networks. You can also choose to not use VLAN IDs. If you selected the two-cable network topology for compute nodes, you need to use VLAN IDs for the vMotion and storage networks for all compute and storage nodes in the deployment (VLAN IDs are optional for the management networks).
81
+
70
82
NOTE: When you assign VLAN IDs, you are configuring VLAN tags that NetApp HCI will apply to the network traffic. You do not need to enter your native VLAN as a VLAN ID; to use the native VLAN for a network, leave the appropriate field empty.
71
83
72
-
+
84
+
.Steps
85
+
Choose one of the following options:
73
86
|===
74
87
|Option |Steps
75
88
@@ -79,25 +92,122 @@ a|
79
92
. In the *VLAN ID* column, enter a VLAN tag to use for each type of network traffic you want to assign to a VLAN.
80
93
+
81
94
Both compute vMotion traffic and iSCSI traffic must use an unshared VLAN ID.
82
-
. Click *Next*.
83
-
. In the *Subnet* column, enter subnet definitions in CIDR format for each type of network traffic in each network; for example, 192.168.1.0/24.
84
-
. In the *Default Gateway* column, enter the IP address of the default gateway for each type of network traffic in each network.
85
-
. In the *Starting IP* column, enter the first useable IP address for each network subnet in each network.
95
+
. Click *Continue*.
86
96
87
97
|Do not assign VLAN IDs
88
98
a|
89
99
. Select *No* for the *Will you assign VLAN IDs* option.
90
-
. In the *Subnet* column, enter subnet definitions in CIDR format for each type of network traffic in each network; for example, 192.168.1.0/24.
91
-
. In the *Default Gateway* column, enter the IP address of the default gateway for each type of network traffic in each network.
92
-
. In the *Starting IP* column, enter the first useable IP address for each type of network traffic in each network.
100
+
. Click *Continue*.
101
+
|===
102
+
103
+
== Configure the management network
104
+
On the *Management* page, you can choose to have NetApp HCI automatically populate IP address ranges for the management networks based on a starting IP address, or you can choose to manually enter all IP address information.
105
+
106
+
.Steps
107
+
Choose one of the following options:
108
+
|===
109
+
|Option |Steps
110
+
111
+
|Automatically assign IP addresses
112
+
a|
113
+
. Select the *Automatically assign IP addresses* option.
114
+
. In the *Subnet* column, enter a subnet definition in CIDR format for each VLAN.
115
+
. In the *Default Gateway* column, enter a default gateway for each VLAN.
116
+
. In the *Subnet* column, enter a starting IP address to use for each VLAN and node type.
117
+
+
118
+
NetApp HCI automatically populates the ending IP addresses for each host or group of hosts.
119
+
. Click *Continue*.
120
+
121
+
|Manually assign IP addresses
122
+
a|
123
+
. Select the *Manually assign IP addresses* option.
124
+
. In the *Subnet* column, enter a subnet definition in CIDR format for each VLAN.
125
+
. In the *Default Gateway* column, enter a default gateway for each VLAN.
126
+
. In the row for each host or node, enter the IP address for that host or node.
127
+
. Enter the Management Virtual IP (MVIP) address for the management network.
128
+
. Click *Continue*.
129
+
|===
130
+
131
+
== Configure the vMotion network
132
+
On the *vMotion* page, you can choose to have NetApp HCI automatically populate IP address ranges for the vMotion network based on a starting IP address, or you can choose to manually enter all IP address information.
133
+
134
+
.Steps
135
+
Choose one of the following options:
93
136
|===
94
-
. Click *Apply to Network Settings*.
95
-
. Click *Yes* to confirm.
137
+
|Option |Steps
138
+
139
+
|Automatically assign IP addresses
140
+
a|
141
+
. Select the *Automatically assign IP addresses* option.
142
+
. In the *Subnet* column, enter a subnet definition in CIDR format for each VLAN.
143
+
. (Optional) In the *Default Gateway* column, enter a default gateway for each VLAN.
144
+
. In the *Subnet* column, enter a starting IP address to use for each VLAN and node type.
96
145
+
97
-
This populates the *Network Settings* page with the settings you entered in the easy form. NetApp HCI validates the IP addresses you entered. You can disable this validation with the Disable Live Network Validation button.
98
-
. Verify that the automatically populated data is correct.
146
+
NetApp HCI automatically populates the ending IP addresses for each host or group of hosts.
147
+
. Click *Continue*.
148
+
149
+
|Manually assign IP addresses
150
+
a|
151
+
. Select the *Manually assign IP addresses* option.
152
+
. In the *Subnet* column, enter a subnet definition in CIDR format for each VLAN.
153
+
. (Optional) In the *Default Gateway* column, enter a default gateway for each VLAN.
154
+
. In the row for each host or node, enter the IP address for that host or node.
99
155
. Click *Continue*.
156
+
|===
157
+
158
+
== Configure the iSCSI network
159
+
On the *iSCSI* page, you can choose to have NetApp HCI automatically populate IP address ranges for the iSCSI network based on a starting IP address, or you can choose to manually enter all IP address information.
100
160
161
+
.Steps
162
+
Choose one of the following options:
163
+
|===
164
+
|Option |Steps
165
+
166
+
|Automatically assign IP addresses
167
+
a|
168
+
. Select the *Automatically assign IP addresses* option.
169
+
. In the *Subnet* column, enter a subnet definition in CIDR format for the iSCSI network.
170
+
. (Optional) In the *Default Gateway* column, enter a default gateway for the iSCSI network.
171
+
. In the *Subnet* column, enter a starting IP address to use for each node type.
172
+
+
173
+
NetApp HCI automatically populates the ending IP addresses for each host or group of hosts.
174
+
. Click *Continue*.
175
+
176
+
|Manually assign IP addresses
177
+
a|
178
+
. Select the *Manually assign IP addresses* option.
179
+
. In the *Subnet* column, enter a subnet definition in CIDR format for the iSCSI network.
180
+
. (Optional) In the *Default Gateway* column, enter a default gateway for the iSCSI network.
181
+
. In the *Management Node* section, enter an IP address for the management node.
182
+
. For each node in the *Compute Nodes* section, enter the iSCSI A and iSCSI B IP addresses.
183
+
. In the *Storage Virtual IP (SVIP)* row, enter the SVIP IP address for the iSCSI network.
184
+
. In the remaining rows, for each host or node, enter the IP address for that host or node.
185
+
. Click *Continue*.
186
+
|===
187
+
188
+
== Assign cluster and host names
189
+
On the *Naming* page, you can choose to have NetApp HCI automatically populate the cluster name and the names of the nodes in the cluster, based on a naming prefix, or you can choose to manually enter all of the names for the cluster and nodes.
190
+
191
+
.Steps
192
+
Choose one of the following options:
193
+
|===
194
+
|Option |Steps
195
+
196
+
|Automatically assign cluster and host names
197
+
a|
198
+
. Select the *Automatically assign cluster / host names* option.
199
+
. In the *Installation Prefix* section, enter a naming prefix to use for all of the node host names in the cluster (including the management node and witness nodes).
200
+
+
201
+
NetApp HCI automatically populates the host names based on the type of node, as well as suffixes for common node names (such as the compute and storage nodes).
202
+
. (Optional) In the *Naming Scheme* column, modify any of the resulting names for the hosts.
203
+
. Click *Continue*.
204
+
205
+
|Manually assign cluster and host names
206
+
a|
207
+
. Select the *Manually assign cluster / host names* option.
208
+
. In the *Host / Cluster Name* column, enter the host name for each host, and a cluster name for the storage cluster.
209
+
. Click *Continue*.
210
+
|===
101
211
102
212
== Find more information
103
213
* https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
summary: Learn how to import a NetApp HCI installation profile that will enable NetApp HCI to automatically fill in fields of the NetApp Deployment Engine wizard.
If you obtained the NetApp https://configbuilder.netapp.com/[ConfigBuilder^] profile output for your installation, you can import it during the NetApp HCI installation process to automatically fill out the fields in the NetApp Deployment Engine. This is an optional step.
17
+
18
+
.About this task
19
+
If you import an installation profile, you still need to enter credentials for NetApp HCI to use on the *Credentials* page of the NetApp Deployment Engine.
20
+
21
+
NOTE: If fields in the installation profile are left blank or entered incorrectly, you might need to manually enter or correct the information in the NetApp Deployment Engine pages. If you need to add or correct information, ensure that you update the information in your records and the installation profile.
22
+
23
+
.Import a profile
24
+
. On the *Installation Profile* page, click *Browse* to search for and upload your installation profile.
25
+
. In the file dialog, select and open the profile JSON file.
26
+
. After the profile is successfully imported, click *Continue*.
27
+
+
28
+
You can step through each page of the NetApp Deployment Engine and verify the settings that were imported from the installation profile.
29
+
30
+
.Continue without importing a profile
31
+
. To skip the import step, on the *Installation Profile* page, click *Continue*.
32
+
33
+
== Find more information
34
+
* https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
Copy file name to clipboardExpand all lines: docs/task_nde_review_deploy.adoc
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,10 @@ You can review the information you provided before beginning deployment. You can
18
18
NOTE: During deployment, the management node installation process creates volumes with names beginning with `NetApp-HCI-` in the Element storage cluster, and a SolidFire account beginning with the name `tenant_`. Do not delete these volumes or accounts; doing so will cause a loss in management functionality.
19
19
20
20
.Steps
21
-
. Optional: Click the *Download* icon to download installation information in CSV format.
21
+
. Optional: Click the *Download* icon to download installation information in CSV format. You can save this file and refer to it later for configuration information.
22
22
+
23
-
You can save this file and refer to it later for configuration information.
23
+
NOTE: You can import the CSV file as an installation profile on the *Installation Profile* page of the NetApp Deployment Engine if needed during a future installation.
24
+
24
25
. Expand each section and review the information. To expand all sections at once, click *Expand All*.
25
26
. Optional: To make changes to information in any displayed section:
0 commit comments