The RDB is the 'vol0' volume which is created on every node of the cluster to manage the cluster operations. No user data is contained in it and is not available for client visibility. RDB's are made up of four units namely VLDB, Vifmgr, management and BCOM.
Saturday, May 18, 2013
Dataflow in NetApp cluster-mode
To understand the dataflow in cluster-mode, one needs to understand the four major software components along with other key software components on every node in the cluster, they are as follows:
a. N-blade, network "blade"
b. D-blade, data "blade"
c. SCSI-blase, SCSI SAN "blade"
d. M-host, Management blade
Vserver and Flex Vol creation - NetApp Cluster-mode
Scenario:
======
a. Create a cluster virtual server (Vserver)
b. Create a flex vol
Step:1 View the available Vservers in the cluster
vserver show
"node" Vservers are the scope where vol0 volumes exist and the node management LIFs and cluster LIFs of each node. The "admin" Vserveris the scope in which the cluster management LIF exists
NetApp Cluster-mode aggregate creation
Scenario:
======
a. Create a new aggregate with name node1_aggr1 on node1
b. Add disks to the aggregate
Run SPcollects on Clariion - Basics
SPcollects contain detailed log and configuration data for a CLARiiON Storage Processor. These are used by EMC Support to diagnose faults and configuration problems. Gathering these files when creating a Service Request is highly recommended to troubleshoot a problem. SPcollects should also be retrieved when gathering data for a performance analysis, along with NAR files.
An SPcollect has the filename format of:
Serial Number _ SP A/B _ Year_Month_Day _ Time _ signature _data.zip
A file that ends with runlog.txt, indicates that an SPcollect is still running and this will disappear once the SPcollect file completes.
Friday, May 17, 2013
Enhancements to NFS and SMB - NetApp Cluster-mode support
NFSv4:
=====
1. Data ONTAP 8.1 cluster-mode introduces support for NFSv4 protocol specification as well as elements of NFSv 4.1
2. cluster mode continues to fully support NFSv2 and NFSv3 although you should not use NFSv2 with cluster mode
3. NFSv4 support brings the Data ONTAP 8.1 cluster mode operating system in parity with the Data ONTAP 7.3 operating system
4. The key feature of NFSv4 is referrals, NFSv4.1 is a minor revision of version 4.0 and is an extension of version 4 not a modification, so it's fully compliant with the NFSv4 specification it extends delegations beyond files to directories and send links introduces NFS sessions for enhanced efficiency and reliability provides parallel NFS, pNFS
=====
1. Data ONTAP 8.1 cluster-mode introduces support for NFSv4 protocol specification as well as elements of NFSv 4.1
2. cluster mode continues to fully support NFSv2 and NFSv3 although you should not use NFSv2 with cluster mode
3. NFSv4 support brings the Data ONTAP 8.1 cluster mode operating system in parity with the Data ONTAP 7.3 operating system
4. The key feature of NFSv4 is referrals, NFSv4.1 is a minor revision of version 4.0 and is an extension of version 4 not a modification, so it's fully compliant with the NFSv4 specification it extends delegations beyond files to directories and send links introduces NFS sessions for enhanced efficiency and reliability provides parallel NFS, pNFS
Basics of NetApp Cluster-mode Shells
Similar to 7-mode we have three administrative privilage levels: admin, advanced and diagnostic. Clustered ONTAP system can be managed either from CLI or GUI (system manager or element manager). There are three different shells available with different scopes: Clustershell, nodeshell, systemshell
Step:1 Access through CLI
Clustershell:
=========
-SSH is default method
-One can access clustershell using cluster management LIF (recommended) or the node management LIFs
-Scope: entire cluster
Step:1 Access through CLI
Clustershell:
=========
-SSH is default method
-One can access clustershell using cluster management LIF (recommended) or the node management LIFs
-Scope: entire cluster
Subscribe to:
Posts (Atom)