1) what are the steps which you are going to perform whenever you encountered cl uster nodes are in "Attention" state: Reasonia) avscan job failure b) dblog is full Answer: first we will run "isi stat" command on node to check its status.if s ‘tatus is showing as Attention perform below steps Acollect islion logs by conmand "isi_gather_info",we may be prompted for your root password, and then the logs frem each of the nodes in the cluster will be c ompiled into one file and automatically uploaded to us. 2) by Analysing the islion logs, we found that The issue here is identified as Avscan failure event as the another job kicked in and is running. 3)run command "isi event list™ to check the status of all jobs running on that n ode.Note down the instanceid of failed avscan job. 4)cancel the job by comand "isi events cancel ~-instanceids 3.2163 5) run command "isi stat", now status of node should be "ok" 4) check the size of dblog, If it is full then we have to clear the Logs. 2) A Unix client is getting a permission denied error Answer: 1) checking verifying quorum, ensuring that the cluster has not split an d that the user is connecting to a node which can write to /ifs. Next check whether quotas are in use, and if so how much room there is on the ta rget directory. Check to see if the user has already exceeded their quota limit, ‘and then verify the mount options that they are using. 2) check the user by issuing the “isi auth users view username * conmand,Make su re the user is in one of the groups that has write permissions. 3) now repair the permissions assigned + login to BUT go to filesharing>advanced>repair permission job>select job option To run che Repair Permission job: 1.In the web administration interface click PROTOCOLS, then click ACLs, and then Click Repair Permissions Job. The Repair Permissions dob page displays. 2.for Repair task, click to select one of the permission job tasks; clone, conve rt, dnherit3) nfsvd mounted client reports permission problems accessing resource on cluste r 1) check that nfsv4 domain string matches cluster a) if domain doesn't matches * set the resource to default owner/group or typically nobody/no group The resolution is to set the @Donain string on the cluster to match exactly the @Domain string on the Linux client’s /etc/idnap.conf file. On the cluster, you can set the string in the web administration interface click PROTOCOLS, then click ONIX Sharing (NFS), and then click NFS Settings page. 4) how will you trouble shoot SMB issues if encountered: 1) run command ist smh session list 2)isi smb openfiles list 3) logs are stored in path /var/log/Iwiod.1og default log level is error, we need to chnage it to debug change leg level isi smb log-level -- set=debug 5) how will you resolve atp issues: ljuse the AD domain controller to set cluster time