Ok - found something and did:
 event route add-destinations {-severity <=ERROR} -destinations criticals

Davin.



On Thu, Nov 7, 2013 at 4:28 PM, Davin Milun <davin.milun@gmail.com> wrote:
As someone else with long NetApp history, but very new to CDOT, I have a related question: syslog.

We have always had a syslog.conf that contained:
  *.err;kern.*                            @loghost
How does one do the equivalent with CDOT?  Is there a shortcut way, or does one need to go manually choose which events to do what with?

Thanks.
Davin.


On Thu, Nov 7, 2013 at 9:37 AM, Iluhes <iluhes@yahoo.com> wrote:
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=search&viewlocale=en_US&searchid=1383790053094

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.


Cheers,

—April

To summarize:
To enable the web services for a cluster, use these steps from the KB article mentioned above:
1. Enable the required Web services for the cluster:
cluster-1::> vserver services web modify -name spi|ontapi|compat -vserver * -enabled true
2. Create the Web service access service spi for the cluster and assign it the admin role:
cluster-1::> vserver services web access create -name spi -role admin -vserver cluster1
3. Create the Web service access service ontapi for the cluster and assign it the admin role:
cluster-1::> vserver services web access create -name ontapi -role admin -vserver cluster1 

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 compat for the cluster and assign it the admin role:
cluster-1::> vserver services web access create -name compat -role admin -vserver cluster1 
5. Identify the cluster-mgmt LIF for the cluster. This will be used for HTTPS access. A node-mgmt LIF can also be used instead of the cluster-mgmt LIF:
cluster-1::*> net int show -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 -authmethod password

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)

3. No separate exports for qtrees

there is, as of cDOT 8.2.1.

4. Not clear how to access log file of the cluster....mounting root
share not possible, right? only for vServer..

"event log ..." commands




_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters