The previous post
was 4-Node
ONTAP Select cluster on KVM. Here we do a single-node cluster on VMware.
The ONTAP Deploy CLI commands are pretty much the same, just one node/host
rather than 4.
1) Login to the ONTAP Select Deploy VM over SSH. Default
username = admin (default password = admin123.)
2) Add the ESX host to the list of possible hypervisors
for an ONTAP node deployment, and verify the host has been added and has a
status of authenticated (will take ~15 seconds):
(ONTAPdeploy)
(ONTAPdeploy)
host add --host-id 192.168.0.51 --username
"DEMO\administrator" --password "********" --vcenter
vc1.demo.company.com
Host:
192.168.0.51 Status: authentication_in_progress
(ONTAPdeploy)
(ONTAPdeploy)
host show-all
+--------------+----------------------------+---------+-----------------+
|
Host | Status | Type | Cluster Created |
+--------------+----------------------------+---------+-----------------+
|
192.168.0.51 | authentication_in_progress | Unknown | False |
+--------------+----------------------------+---------+-----------------+
(ONTAPdeploy)
(ONTAPdeploy)
host show-all
+--------------+---------------+------+-----------------+
|
Host | Status | Type | Cluster Created |
+--------------+---------------+------+-----------------+
|
192.168.0.51 | authenticated | ESX |
False |
+--------------+---------------+------+-----------------+
(ONTAPdeploy)
3) Configure the ESX host that was just added, and after
~2 minutes verify the host has a status of “configured”.
(ONTAPdeploy)
(ONTAPdeploy)
host configure --host-id 192.168.0.51 --location
LAB --storage-pool esx1data --management-network ONTAP-external --data-network
ONTAP-external --eval
Host
configuration in progress for host: 192.168.0.51
(ONTAPdeploy)
(ONTAPdeploy)
host show-all
+--------------+------------+------+-----------------+
|
Host | Status | Type | Cluster Created |
+--------------+------------+------+-----------------+
|
192.168.0.51 | configured | ESX |
False |
+--------------+------------+------+-----------------+
(ONTAPdeploy)
4) Create the cluster. The cluster create command takes
approximately 60 seconds to complete. The cluster creation process takes
approximately 30 minutes.
(ONTAPdeploy)
(ONTAPdeploy)
cluster create --name cluster3
--admin-password ******** --cluster-mgmt-ip 192.168.0.103 --netmask
255.255.255.0 --gateway 192.168.0.1 --ontap-image-version 9.2 --node-names
cluster3-1 --node-mgmt-ips 192.168.0.113 --node-hosts 192.168.0.51 --dns-ips
192.168.0.253 --dns-domains demo.company.com --ntp-servers 192.168.0.1
Cluster
cluster3 create request accepted
(ONTAPdeploy)
(ONTAPdeploy)
host show-all
+--------------+------------+------+-----------------+
|
Host | Status | Type | Cluster Created |
+--------------+------------+------+-----------------+
|
192.168.0.51 | configured | ESX |
True |
+--------------+------------+------+-----------------+
(ONTAPdeploy)
cluster show-all
+----------+-----------------+-----------+-----------------+
|
Name | State | Num Nodes | Cluster Mgmt IP |
+----------+-----------------+-----------+-----------------+
|
cluster3 | deploying_nodes | 1 |
192.168.0.103 |
+----------+-----------------+-----------+-----------------+
(ONTAPdeploy)
(ONTAPdeploy)
cluster show-all
+----------+--------+-----------+-----------------+
|
Name | State | Num Nodes | Cluster Mgmt IP |
+----------+--------+-----------+-----------------+
|
cluster3 | online | 1 |
192.168.0.103 |
+----------+--------+-----------+-----------------+
(ONTAPdeploy)
You can see the cluster powered up in the
vSphere Web Client.
5) Finally use OnCommand System Manager to configure the
cluster (like a ‘normal’ ONTAP cluster.)
Image: ONTAP Select
cluster in the vSphere Web Client
Image: ONTAP Select
cluster managed via OnCommand System Manager (model FDvM300)
Comments
Post a Comment