Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What is the implementation of NetApp's VVOLs?

2025-02-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/01 Report--

This article shows you what is the implementation of NetApp's VVOLs. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Today I went to study how NetApp is implemented.

VASA Provider (VP)

NetApp deploys VP as a virtual application of OVA, which is managed by VSC (Virtual Storage Console), a plug-in for vSphere Web Client. Because VVOLs needs to be managed by VP runs, VP cannot be deployed under VVOLs, otherwise it becomes an endless loop. I read NetApp's previous documentation and deployed VP on vSphere 5.5 for fear of 6.0 beta instability. Now that 6. 0 has been released, it should be all right with 6. 0, but it must be deployed in the traditional way rather than VVOL.

Storage Container (SC)

In the implementation of NetApp, a SC is a collection of FlexVol volumes that use Virtual Volume datastore. All FlexVol within a SC must use the same access protocol (NFS,iSCSI or FC) and belong to the same SVM (Storage Virtual Machine), but they can be hosted on different aggregate and nodes in the cluster.

Protocol Endpoint (PE)

For the block protocol, a PE is a 4MB-sized LUN. VP creates a PE for each FlexVol as part of the Viutual Volume datastore. PE automatically maps to initiator groups that are created and managed through VP.

For NFS, a PE is a mount point that uses the ip address of SVM's LIF.

Both VSC and VP communicate with ONTAP OS through NetApp API (ZAPI).

Storage Capability Profile (SCP)

NetApp also has the term SCP, which refers to the set of capabilities of a set of volumes. To be clear, what features are supported by its VVOLs, and these features can be perceived by VMWARE vSphere. At present, the features supported by NetApp VVOL and VM linkage are:

Autogrow enabled

Compression enabled

De-duplication enabled

Disk Type (SATA, FCAL, SAS, SSD)

Flash Accelerated (Flash Cache or Flash Pool)

High Availability (HA Controllers)

Maximum Throughput (IOPS or Mbps)

Protocol (iSCSI, FC, FCoE or NFS)

Replication (Async or Sync)

From the implementation of NetApp, we can see that NetApp and VMware work closely together, so they can launch the VVOL function at the first time.

The above content is what is the implementation of NetApp's VVOLs? have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report