NetApp C-mode for 7 mode engineers

16,311 views

Published on

Introduction of NetApp cluster mode (c-mode) administration for storage engineers, already working with NetApp filers in 7-mode.

Published in: Technology
0 Comments
22 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
16,311
On SlideShare
0
From Embeds
0
Number of Embeds
105
Actions
Shares
0
Downloads
0
Comments
0
Likes
22
Embeds 0
No embeds

No notes for slide
  • Brendon Higgins is an operational engineer who supports cloud infrastructure. He is very active in the NetApp user community and speaks at user group events about his role.
  • http://www.cisco.com/en/US/docs/unified_computing/ucs/UCS_CVDs/ucs_sharepoint2010_flexpod_vmware.html
  • Everything on one large box
  • Image fromhttps://communities.netapp.com/community/netapp-blogs/exposed/blog/2011/11/02/hpc-comes-to-enterprise-it
  • https://communities.netapp.com/docs/DOC-17138/
  • Storage Failover between HA pairs• Cluster interconnect. A 10Gbps, private, dedicated, redundant, high-throughput network used forcommunication between the cluster nodes and for data motion. The cluster interconnect infrastructureis included with every Data ONTAP 8.1 configuration to support this network.• Management network. All management traffic passes over this network. The management networkswitches are also included with every Data ONTAP 8.1 configuration.OnCommand™ System Manager 2.0 and unified manager are available for management,configuration, and monitoring of Data ONTAP clusters along with 7-Mode systems. These utilitiesprovide GUI management, including a number of easy-to-use wizards for common tasks. In addition,a CLI, ZAPI set, and SDK are available for more specialized use.• Data networks. Provide data access services over Ethernet or Fibre Channel to the SAN hosts andNAS clients. These networks are customer provided according to requirements and could alsoinclude connections to other clusters acting as volume replication targets for data protection.
  • The primary logical cluster component is the virtual server. Data ONTAP supports from one to hundredsof virtual servers in a single cluster. Each virtual server enables one or more SAN and NAS accessprotocols and contains at least one volume and at least one logical interface. The administration of eachvirtual server can also be delegated if desired, so that separate administrators could be responsible forprovisioning volumes and other virtual server–specific operations. This is particularly appropriate for multitenantedenvironments or where workload separation is desired.For NAS clients, the volumes are junctioned together into a namespace for CIFS and NFS access, andfor SAN hosts, LUNs are defined in the volumes and made available, as described in section 1.2.The accessing hosts and clients connect to the virtual server using a logical interface (or LIF). LIFspresent either an IP address (which will be used by NAS clients and iSCSI hosts) or a WWN (for FC andFCoE access). Each LIF is mapped to a home port on a NIC or HBA. LIFs are used to virtualize the NICand HBA ports rather than mapping IP addresses or WWNs directly to the physical ports, because therewill almost always be many more LIFs than physical ports in a cluster. Each virtual server requires its owndedicated set of LIFs, and up to 128 LIFs can be defined on any cluster node. A LIF defined for NASaccess can temporarily move or migrate to another port on the same or a different controller to preserveavailability or to rebalance client performance.Figure 3 shows a single virtual server that is providing data services to SAN hosts and NAS clients. Eachvolume, shown by the orange circles, is provisioned on an aggregate on a cluster node, and thecombination of all the volumes constitutes the entire namespace or resource pool for LUNs. By default,volumes in a virtual server can be created in any of the defined aggregates and moved at any time fromaggregate to aggregate as required. A delegated virtual server administrator can provision volumes intheir own virtual server. The delegated virtual server administrator cannot, however, initiate the movementof volumes around across the cluster, since this might affect the entire cluster. For this reason, only acluster administrator can move volumes.
  • A cluster namespace is a collection of file systems hosted from different nodes in the cluster. Each Vserver has a file namespace that consists of a single root volume. The Vserver namespace consists of one or more volumes linked by means of junctions that connect from a named junction inode in one volume to the root directory of another volume. A cluster can have more than one Vserver. All the volumes belonging to the Vserver are linked into the global namespace in that cluster. The cluster namespace is mounted at a single point in the cluster. The top directory of the cluster namespace within a cluster is a synthetic directory containing entries for the root directory of each Vserver namespace in the cluster.
  • Namespace unchanged as data moves Much easier to manage Much easier to change Seamlessly scales to petabytes
  • tr-3982 Data ONTAP 8.1 and 8.1.1 Operating in Cluster-Mode An Introduction.pdf
  • NetApp C-mode for 7 mode engineers

    1. 1. NetApp C-Mode for 7 mode engineers Brendon Higgins
    2. 2. Brendon Higgins – The numbers• 30 Petabytes of NetApp storage• 15 Years service in operational roles• 5 Years using NetApp 7-mode
    3. 3. NetApp Data ONTAP 8 7-Mode or C-Mode
    4. 4. Data ONTAP 8 7 - Mode• 64 bit aggregates• Compression• Data Migration• Unified Connect
    5. 5. Growing Up
    6. 6. Limits of the box • CPU • Memory • Disk Shelves
    7. 7. HA Partner
    8. 8. Oops!
    9. 9. Immortal ClusterNAS Custer 2 – 24 nodeSAN Cluster 2 or 4 nodes
    10. 10. Multiprotocol unified architecture• NFS v3, v4, v4.1, including pNFS• SMB 1 and 2• iSCSI• Fibre Channel• FCoE• ?Anti Virus?
    11. 11. Cluster Mode Scale Up
    12. 12. Mix it up (2 - FAS3200 Series) (2 – FAS3200 Series) Mixed Cluster-Mode(2 - FAS6200 Series) Network
    13. 13. Scale outData ONTAP – Cluster Mode
    14. 14. Building Blocks
    15. 15. Physical Cluster• Storage Controllers – Cluster Nodes• Individual disks – Defined into aggregates• Ports – HBA – Network Interface CardOnly visible to the cluster administrator
    16. 16. Logical Cluster• Virtual Server – Volumes – NFS service – CIFS service – LUNs (requires ALUA) – Logical Interface (or LIF) • Either IP or WWN address
    17. 17. Namespace VolumesVolumes are linked bymeans of junctionswhich connect from ajunction inode back tothe root directory
    18. 18. Single Mount Point NFS clients can go direct
    19. 19. ManagementPurchase configured system• Element Manager• System Manager 2.0.2• CLI• Powershell
    20. 20. Long Live Filer View
    21. 21. Change is good
    22. 22. Must be 2.0.2+
    23. 23. System Manager
    24. 24. Powerful Wizards
    25. 25. Delegation
    26. 26. CLI• Most powerful management tool• New command names Data ONTAP® 8.1 7-Mode to Cluster-Mode Command Map i.e. snap list is now snap show
    27. 27. CLI NavigationCluster :: Volume
    28. 28. Easy Navigation• Tab autocomplete• .. Back one level• ‘top’ Returns to ::• ? For help
    29. 29. Fast commands‘Order’ of parameters important if not usingname parameters
    30. 30. Demo• Add disks to aggregate• Add volume to virtual filer
    31. 31. NetApp Simulator• Download from NOW site
    32. 32. More?https://forums.netapp.com/community/support/cfor7Start wit TR-3982, Operating in Cluster-Mode An Introduction
    33. 33. February 2013
    34. 34. Thank you

    ×