NAS configuration
Note: This step will take up to 10 minutes to complete. Be patient as it will appear
as nothing is happening or ‘UNHEALTHY’ text will show. This is normal.
-
Run the NAS configuration script which utilizes the
information from the configuration file.
[root@qnode2 ovfconfig]# ./nas_configure.sh Wed Nov 4 11:07:55 PST 2020 [24778]: Running ./nas_configure.sh Wed Nov 4 11:07:55 PST 2020 [24778]: Configuring NAS Updating NAS cluster configuration ... Verifying NAS cluster configuration for 10.16.232.174 ... NAS cluster enable node 10.16.232.174 starting ... Updating system NAS cluster configuration ... NFS: services (v4=no, v3=yes, HA=no)Setting master local auth config ... Applying local configuration settings ... Master node successfully enabled for NAS cluster using 10.16.232.174 Updating NAS cluster configuration ... Verifying NAS cluster configuration for 10.16.232.173 ... Node 10.16.232.173 successfully enabled for NAS cluster NAS Cluster preparing to set virtual IPs: 10.16.232.177 ... Verifying virtual IPs: 10.16.232.177 ... NAS Cluster setting paused state ... NAS Cluster updating virtual IP addr list to: ['10.16.232.177'] ... NAS Cluster applying virtual ipaddr settings ... Updating system NAS cluster configuration ... NFS: services (v4=no, v3=yes, HA=no) NAS Cluster clearing paused state ... Virtual IP addresses ['10.16.232.177'] successfully stored NAS Cluster join starting ... NAS Cluster ID 0c3a5438-1ed1-11eb-9576-00308c0c2480 found ... Preparing for NAS cluster join as ID 10.16.232.174 Applying NAS cluster join settings ... Updating system NAS cluster configuration ... NFS: services (v4=no, v3=yes, HA=no) Check for master takeover ... Publish master configuration ... Cluster verification for 10.16.232.174 in-progress ... Node state: pnn:0 10.16.232.174 UNHEALTHY (THIS NODE), waiting ... Node state: pnn:0 10.16.232.174 OK (THIS NODE) Cluster verification of 10.16.232.174 successful ... Waiting for NAS Master VIP 10.16.232.177 to be reachable ... Successfully joined NAS cluster Waiting for config already in-progress ... wait complete NAS Cluster join starting ... NAS Cluster ID 0c3a5438-1ed1-11eb-9576-00308c0c2480 found ... Proxy join to 10.16.232.173 ... [10.16.232.173]: NAS Cluster join to cluster ID 0c3a5438-1ed1-11eb-9576-00308c0c2480 starting ... [10.16.232.173]: Preparing for NAS cluster join as ID 10.16.232.173 [10.16.232.173]: Verifying local configuration with master 10.16.232.174 ... [10.16.232.173]: Synchronization of local configuration with master 10.16.232.174 starting... [10.16.232.173]: Applying local auth config sync settings ... [10.16.232.173]: Applying local configuration settings ... [10.16.232.173]: Applying NAS cluster join settings ... [10.16.232.173]: Updating system NAS cluster configuration ... [10.16.232.173]: NFS: services (v4=no, v3=yes, HA=no) [10.16.232.173]: Verifying local configuration with master 10.16.232.174 ... [10.16.232.173]: Cluster verification for 10.16.232.173 in-progress ... [10.16.232.173]: Node state: pnn:1 10.16.232.173 UNHEALTHY (THIS NODE), waiting ... [10.16.232.173]: Node state: pnn:1 10.16.232.173 OK (THIS NODE) [10.16.232.173]: Cluster verification of 10.16.232.173 successful ... Successfully joined NAS cluster Broadcasting share config-sync to NAS cluster ... Waiting for nascluster_share_config_sync to complete on node 10.16.232.173 Share global successfully changed Broadcasting share config-sync to NAS cluster ... Waiting for nascluster_share_config_sync to complete on node 10.16.232.173 Share gvfs_sysman1 successfully added Registry key 'cifs.allow_trusted_domains' set to '1'. NAS Cluster IP: 10.16.232.174/em2, Master: Yes, SNFS Root: /Volumes/gvfs_sysman1, Joined: Yes ID: 0c3a5438-1ed1-11eb-9576-00308c0c2480 Cluster Hostname: DNS Enabled: No Load balancing: Proxy-Disabled NFS-HA: Disabled Master IP: 10.16.232.174 qnode2.gvservice.com VIP: 10.16.232.177 (active, node:master) gvnas2.gvservice.com Nodes: 2 1: 10.16.232.174 (Joined, MDC) qnode2.gvservice.com 2: 10.16.232.173 (Joined, MDC)
- Exit the shell.
- Ping the NAS VIP to ensure it is accessible.
- Exit the CLI.