Both the vCenter Server and VASA Provider generate alarms that are specific to VVOL datastores.
The vCenter Server monitors information that VASA Provider reports about VVOL datastores and automatically triggers an alarm if there is a space issue on the VVOL datastore.
VASA Provider checks the VVOL datastores each time it performs a cluster rediscovery operation. If it discovers a problem, it displays a red or yellow alarm. These alarms can indicate obvious problems, such as a FlexVol in a VVOL datastore going offline, or more subtle problems, such as a path to the storage suddenly becoming non-optimal because a network LIF went down.
Unlike earlier versions of VASA Provider, you do not need to manually reset the alarm after you resolve the problem. The alarm color changes back to green to indicate that everything is now normal.
If a problem occurs, VASA Provider sends a message stating the cause of the alarm. If the alarm was triggered by a FlexVol issue, it states which FlexVols are affected.
There are several conditions that can trigger an alarm for a VVOL datastore, including the following:
VASA Provider generates a red alarm when something is not working as it should. This alarm can occur when a FlexVol has one of the following problems:
This alarm is also triggered when problems occur with an underlying Data ONTAP entity, such as a Storage Virtual Machine (SVM, formerly known as Vserver) or cluster.
VASA Provider generates a yellow alarm when a FlexVol is overcommitted for deduplication. You can determine whether the FlexVol is overcommitted by adding the combined deduplication size that was saved and the FlexVol size that was used and dividing that sum by the total size of the FlexVol; If the result is greater than 1, the FlexVol is overcommitted:
(Deduplication size saved + FlexVol size used) / Flexvol total size > 1.0
For San VVOL datastores, VASA Provider generates a yellow alarm when the number of LUNs in the FlexVol are greater than 80 percent of the limit allowed by Data ONTAP.
The default limit is 512 LUNs for each FlexVol.
For SAN (or block) VVOL datastores, VASA Provider generates a red alarm if there are FlexVols that do not have a usable Protocol Endpoint (PE) LUN.
For NFS VVOL datastores, VASA Provider generates a yellow alarm if it detects that some nodes on the cluster do not have a NFS PE.
If VASA Provider detects that there are no NFS PEs, it generates a red alarm.
The alarm message that VASA Provider sends will list the node names of the cluster.
VASA Provider generates a red alarm if the default profile for the storage container (also called "backing storage") is no longer supported.
VASA Provider generates a red alarm when the storage container is overcommitted. This occurs when the container logical size (the size of all the VVOLs in the container) divided by the container size (the size of all FlexVols in the container) is greater than the threshold. The default value for the threshold is 10.
(Size of all the VVOLs in the container) / (Size of all FlexVols in teh container) > threshold