ViPR Controller: No volumes visible for catalog service Export Volume to a Host

           

   Article Number:     526085                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller,ViPR Controller Controller 3.6 SP2,ViPR Controller Controller 3.6 SP1,ViPR Controller Controller 3.6,ViPR Controller Controller 3.5

 

Issue:

 

 

When attempting to run an "Export Volume to a Host" order, to export a VPLEX volume to a cluster, the volumes field does not populate with a list of available volumes to be exported.   
   
    ViPR Controller sasvc service log reports the following API call to check the VirtualArray association to the cluster:   
        

      vipr1 sasvc 2018-08-08 14:31:52,380 [qtp514587349-47 - /catalog/asset-options/vipr.unassignedBlockVolume]  INFO  LoggingFilter.java (line 238) 196 > GET https://<VIP/FQDN>:4443/vdc/varrays/search?cluster=urn:storageos:Cluster:d08eb16f-e018-4e14-bff4-bd209d1cf8e2:vdc1    
    ViPR Controller sasvc service log reports the response to the above API call:   
        
      vipr1 sasvc 2018-08-08 14:31:52,685 [qtp514587349-47 - /catalog/asset-options/vipr.unassignedBlockVolume]  INFO  LoggingFilter.java (line 125) 196 < 200  took 305 ms{"resource":[]}    
   

      ​     
      As the API response is empty, this prevents ViPR Controller from showing volumes that are available to be exported to the cluster.     
          

                                                             

 

 

Cause:

 

 

The cluster that the user is attempting to export to contains hosts that are associated to more than one VirtualArray.   
   
    The API call used in Export Volume to a Host, expects the hosts in the cluster to be associated to just one VirtualArray.   
     
                                                           

 

 

Change:

 

 

This behaviour is per design.   
     
                                                           

 

 

Resolution:

 

 

The service catalog Export Volume to a Host is not designed to export a VPLEX volume to a cluster whose hosts are associated to more than one VirtualArray.   
   
    The service catalog "Export VPLEX Volume" should be used to export a volume to clusters of this configuration.   
   
    The API call used in "Export VPLEX Volume" is run against each host in the cluster as opposed to the cluster itself:   

vipr1 sasvc 2018-08-30 12:25:55,259 [qtp514587349-1211]  INFO  LoggingFilter.java (line 238) 1361 > GET https://<VIP/FQDN>:4443/vdc/varrays/search?host=urn:storageos:Host:019d835c-3998-4b81-b083-5e2202b0ba3f:vdc1    
                                                             

 

 

Notes:

 

 

As an example take the following:   

         
  •         The user has added a VPLEX Metro to ViPR Controller.                
               
    •             No VPLEX cross-connect configured         
    •        
                  
  •      
  •         The user has configured 2 VirtualArrays in ViPR Controller                
               
    •             The first represents VPLEX cluster-1 and its backend array         
    •          
    •             The second represents VPLEX cluster-2 and its backend array         
    •        
                  
  •      
  •         The user has configured a stretched host cluster with 4 hosts                
               
    •             2 of the hosts have connectivity back to VPLEX cluster-1 and VA_1 by association         
    •          
    •             2 of the hosts have connectivity back to VPLEX cluster-2 and VA_2 by association         
    •        
                  
  •    
   
    When the user attempts to run "Export Volume to a Host" against this cluster the API expects all 4 hosts to be associated to the same VirtualArray.   
   
    When the user attempts to run Export VPLEX Volume, this API call is not made and ViPR Controller is successfully able to populate the volume field.