Hi All,  To my understanding. In this scenario, the virtual volume would be a known or managed volume for ViPR. But the storage-view is a unmanaged storage-view. So, the corresponding exportgroup would have not been created in ViPR. Once you do a discover unmanaged volumes, ViPR is going to discover the storage-views which does not have "no_vipr" in it and create corresponding exportgroup in ViPR. You should be able to Ingest the volume  after that. This is my understanding and even I don't have a test environment. Let us know if works the same way.  Thanks, Sathya
Hi All,  I have a question regarding the block volume ingestion service on ViPR Controller.  If a Volume is created in ViPR, but the masking and zoning is done manually outside of ViPR (using native element managers)(ViPR-c therefore has no knowledge of the volume masking), will this volume appear in the list of volumes that we can ingest after we run the "Discover Unmanaged Volumes" service in the Service catalogue?  I think that ViPR-C will not find volume as an unmanaged volume. However don't have a test ViPR-C environment to test this out.  Thanks in advance, Luke
ViPR Controller - Block volume ingest question