Hello CockneyUSA and Wei     Same issue occurred in my environment. I failed to recognized vVNX through smi-provider host also.  There are some comments on white paper for vVNX.  the vVNX system provides an on-array SMI-S v1.6 provider which can be used for both file and block file and block "operations. Any application which has the capability to leverage the SMI-S API can be used to discover and configure the vVNX system based on the supported operations."  vVNX seems be supported with SMI-provider. But why did the SMI-provider fail to identify vVNX?  Some finding for SMI-S,  Only SMI-S 1.5 is  available in EMC download. Is it a issue for this ?  Any suggestion would be appreciated.
I've tried adding the vVNX to ViPR as a VNX file device and also adding it to SMI-S as a block device.     Both fail.  Is this because it emulates the VNXe, not the VNX?
Can vVNX work with ViPR?