I guess coming from unix background, I always found very useful having ability to have an admin box with all root volumes mounted and just search/grep messages file, copy and edit RC files, rsh scripts via scripts for quota reports, backups, etc. I am sure there might be a way to get some/most/all of that functionality with cDOT, but just the elegance of administering everything from single linux admin hosts just does not seem to be present or fully capable anymore. Am I wrong? I also never worked on anything that need to grow beyond 2-nodes, single cluster. Why would netapp force cluster on such setups, I would have think that majority of install base is small, medium, 2 node clusters
On Wednesday, November 6, 2013 8:08 PM, aprilogi aprilogi@yahoo.com wrote:
Just adding a few things:
2. RSH? Can I run RSH commands?
you can ssh commands, passwordless (once you set up the proper keys) See KB: 1012524 https://kb.netapp.com/support/index?page=content&id=1012542&actp=sea...
4. Not clear how to access log file of the cluster....mounting root
share not possible, right? only for vServer..
"event log ...” commands
You can also enable remost access so that you can view the logs from http. This is very useful.
See: https://kb.netapp.com/support/index?page=content&id=1013814
Cheers,
—April
To summarize: To enable the webservices for a cluster, use these steps from the KB article mentioned above: 1. Enable the required Web services for the cluster: cluster-1::> vserverservices web modify -name spi|ontapi|compat-vserver* -enabled true 2. Create the Web service access service spifor the cluster and assign it the admin role: cluster-1::> vserverservices web access create -name spi-role admin -vservercluster1 3. Create the Web service access service ontapifor the cluster and assign it the admin role: cluster-1::> vserverservices web access create -name ontapi-role admin -vservercluster1 Note: This error will be returned for the admin role, as it is pre-created on cluster create. This error will not be returned if a different role name that is not pre-created is provided. Error: command failed: duplicate entry 4. Create the Web service access service compatfor the cluster and assign it the admin role: cluster-1::> vserverservices web access create -name compat-role admin -vservercluster1 5. Identify the cluster-mgmtLIF for the cluster. This will be used for HTTPS access. A node-mgmtLIF can also be used instead of the cluster-mgmtLIF: cluster-1::*> net intshow -role cluster-mgmt-fields address (network interface show) vserver lif address -------- ----------- ----------- cluster-1 clus_mgmt 10.98.243.120 6. Identify the names of the nodes in the cluster: cluster-1:> node show -fields node node ---------- cluster1-01 cluster1-02 Cluster1-03 Cluster1-04 4 entries were displayed.
6. Add the login to allow http access. cluster1::> login create -username admin -application http -authmethodpassword
cluster1::> login show -username admin -application http (security login show) Authentication Acct Vserver UserName Application Method Role Name Locked ----------- ---------------- ----------- -------------- ---------------- ------ cluster1 admin http password admin no
The following URLs will provide access to the log directory on each node: https://<cluster-mgmt-ip>/spi/<node_name>/etc/log/ https://10.98.243.120/spi/node-a/etc/log/ https://10.98.243.120/spi/node-b/etc/log/ https://10.98.243.120/spi/node-c/etc/log/ https://10.98.243.120/spi/node-d/etc/log/
The following URLs will provide access to the directory where the core files are saved on each node: https://<cluster-mgmt-ip>/spi/<node_name>/etc/crash/ https://10.98.243.120/spi/node-a/etc/crash/ https://10.98.243.120/spi/node-b/etc/crash/ https://10.98.243.120/spi/node-c/etc/crash/ https://10.98.243.120/spi/node-d/etc/crash/
On Nov 6, 2013, at 4:54 PM, Scott Miller Scott.Miller@dreamworks.com wrote:
2. RSH? Can I run RSH commands?
you can ssh commands, passwordless (once you set up the proper keys)
- No separate exports for qtrees
there is, as of cDOT 8.2.1.
- Not clear how to access log file of the cluster....mounting root
share not possible, right? only for vServer..
"event log ..." commands