VASA is looking at the % written/allocated on the TDEV, which is why the alarm is red.  As the whitepaper says, this is because it's over 80%.  The volume could be 93% full due to pre-allocating or, perhaps more likely, tracks have been written/deleted and have filled up that space.  You should be able to issue a reclaim on the free space to resolve this.
Trying to determine how to resolve the issue I have with VMware (5.1 env) thinking a particular device is oversubscribed?  [IMAGE] The volumes itself from a VMware perspective is fine in terms of free space: [IMAGE] From a VMAX perspective my meta device: [IMAGE]  We typically fully allocate volumes on creation, don't ask me why, still trying to change things a bit.  Is that the reason why I have the alarm?  I have other volumes that we provision the same way but dont have the alarm.  In reading the EMC white paper on the topic its normal behavior, i'm just trying to understand how to make sense of it a bit more.  Seems like running a space reclamation on the device is the answer?  Just hoping to get some feedback/advice.
VASA Storage Alarm/VMax Meta Device