netapp c-mode terms
4
Quick Help on c-mode terms NetApp CFO, Active/Active & HA: Refers to a pair of nodes, whose controllers are configured to serve data for each other, if one of the two nodes stops functioning. C-mode [cluster mode]: Introduced in ONTAP 8.0, c-mode describes an OS mode; in which two or more controller operate as one shared resource pool or storage cluster. LIF: This is a cluster mode term, used to define the physical network port on the Vserver. Vserver: This is a cluster mode term, used to describe a virtual system, just as vFiler is called in 7-mode. Major difference: In 7-mode, each individual CIFS/NFS share had to be separately mapped/mounted. This is where, c-mode charms, it uses Global-Name-Space. That means, for users, there is only one namespace or mountpoint for all the storage systems [Internally it is hosted by a cluster of systems]. The volumes that create the namespace can span multiple storage systems. What is scale-out? With scale-out, multiple controllers are used to increase performance and capacity but are presented as one logical large storage unit. What is scale-up? With scale-up, bigger and bigger controllers are used. How clustered pairs are connected? The cluster is typically two or more systems that are interconnected through a two private 10-Gbe network. Logically, entire cluster can be managed through any one of the controllers. What is an aggregate?
-
Upload
ashwin-pawar -
Category
Technology
-
view
2.160 -
download
1
Transcript of netapp c-mode terms
Quick Help on c-mode terms NetApp
CFO, Active/Active & HA: Refers to a pair of nodes, whose controllers are configured to serve data for each other, if one of the two nodes stops functioning.
C-mode [cluster mode]: Introduced in ONTAP 8.0, c-mode describes an OS mode; in which two or more controller operate as one shared resource pool or storage cluster.
LIF: This is a cluster mode term, used to define the physical network port on the Vserver.
Vserver: This is a cluster mode term, used to describe a virtual system, just as vFiler is called in 7-mode.
Major difference: In 7-mode, each individual CIFS/NFS share had to be separately mapped/mounted. This is where, c-mode charms, it uses Global-Name-Space. That means, for users, there is only one namespace or mountpoint for all the storage systems [Internally it is hosted by a cluster of systems]. The volumes that create the namespace can span multiple storage systems.
What is scale-out?With scale-out, multiple controllers are used to increase performance and capacity but are presented as one logical large storage unit.
What is scale-up?With scale-up, bigger and bigger controllers are used.
How clustered pairs are connected?The cluster is typically two or more systems that are interconnected through a two private 10-Gbe network. Logically, entire cluster can be managed through any one of the controllers.
What is an aggregate?Aggregate are made of one of more RAID GROUPS, large aggregates can be created in order to take advantage of striping.
What is flexvol?flexvol are created within the aggregates and are re-sizable.
What is vServer?Once the aggregates are formed on the c-mode, the next step is to create one or more Virtual Server (Vserver) for example: vs1, vs2,etc. Vserver is the logical container for VOLUMES and LIF. Vserver presents as namespace, which spans across system.
For example:flexvol are create within vServer [vs1], and are mounted or junctioned into a namespace. The root volume is 'R', and anything underneath it is called Junction volumes such as A, B & C etc.
For NFS: vs1-lif1:RFor CIFS: \\vs1-lif2\R
What is root flexvol volume?Root flexvol volume forms the root of the namespace or filesystem. You can further populate vServer by creating additional vServer volumes.
What is namespace?Namespace is what client sees for CIFS/NFS shares.
Is there a relationship between vServer, aggregate and nodes?No permanent relation-ship exists between Vserver & aggregates or any of the nodes. A Vserver can span one, more or all of the nodes.
What do I make of all these great features in c-mode, how does it differentiate the business continuity from 7-mode?As no permanent relationship exists between Vserver, aggregates & nodes, it allows c-mode administrator to move volume[s] transparently from one aggregate to another on the same node or a different nodes. This is the key enabler for FULL NDO [non-disruptive operations].
Now you can: move all of the volumes in a vServer to consolidate them on aggregates on only one or two nodes. Yet the Vserver presents the same namespace (directory) before, during and after the volume move. The client's view of the filesystem does not change.
When was cluster mode introduced?It was introduced in ONTAP 8, ontap versions 8.0,8.1 and 8.2 can run in either cluster-mode or 7-mode. As per NetApp: 7-mode is dropped in version 8.3.
Shells in cluster mode:Cluster shell = [::], scope = entire cluster, username 'root' is not allowed, username = admin is allowed, you can access cluster shell by using cluster mgmt LIF or node mgmt LIF.Node shell = is similar to 7-mode shell, scope = local controller, you can access node shell by using node mgmt LIF, if node mgmt LIF is inaccessible, you can even use RLM.System shell = To access to BSD shell for low level diags , scope = local controller
To run 7-mode commands: From cluster shell, enter 'run local' and to exit, type 'exit' or Ctrl+D. When in nodeshell, double colon disappears and cluster hostname is replaced with hostname of the controller/node.
What are giveback commands in cluster mode, compared to 7-mode?In 7-mode = filer>cf giveback, gives back controller ownership.In c-mdoe = ::>storage failover giveback -fromnode local, gives back storage & LIFS
To display commands that are available at the current prompt?Enter [?] question mark, you can return to the root prompt by typing 'top'.
To verify if the aggregates are home after Giveback?::>Storage failover show-giveback
To check the current status of failed-over aggregates?::>Storage failover show
