ViPR Controller: Volume ingestion fails with Zoning is not consistent across hosts in this cluster

           

   Article Number:     531731                                   Article Version: 2     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller,ViPR Controller Controller 3.6

 

Issue:

 

 

The user is unable to successfully run a "Ingest Exported Unmanaged Volume" order.   
   
    ViPR Controller UI error :   
    Error 64000: Zoning is not consistent across hosts in this cluster. Zoning may be missing, insufficient, or otherwise incompatible for one or more hosts   

          
                                                             

 

 

Cause:

 

 

One or more UnManagedExportMask's zoningMap is incomplete.       
       
        The zoningMap contains the HOST_INITIATOR > STORAGE_PORT mapping details and is necessary for ViPR Controller to determine which zones are being used to expose the volume being ingested.       
       
        During the execution of a "Discover Unmanaged Volumes" order ViPR Controller verifies which zones are used to present exported volumes to a host and/or cluster.       
       
        In this scenario, ViPR Controller was unable to find zones on an MDS switch resulting in an incomplete zoningMap.       
       
        The VSAN is associated with multiple switches and the zone details were not distributing across all switches.       
       
        Controllersvc debug logs :
   

     
      As seen below, ViPR-C successfully discovers the initiator is present in zone(s)     
     
      vipr3 controllersvc 2019-03-06 10:15:25,752 [236|<ARRAY>|Discovery|<IP>|86d2ac6e-d1e2-4038-b644-abe43cfa1d3f] DEBUG  SSHDialog.java (line 169) Host: <SWITCH IP>, Port: 22 - sendWaitFor: show zone member pwwn <INITIATOR> active vsan <VSAN ID>     
     
      vipr3 controllersvc 2019-03-06 10:15:25,820 [236|<ARRAY>|Discovery|<IP>|86d2ac6e-d1e2-4038-b644-abe43cfa1d3f] DEBUG  SSHDialog.java (line 108) insr is ready and the buffer will be appended by pwwn <INITIATOR> vsan <VSAN ID>       
          zone <ZONE_NAME1>       
          zone <ZONE_NAME2>
     
     
     
     
      ViPR-C queries the zone membership on one of the switches in the fabric and fails to find the zone     
     
      vipr3 controllersvc 2019-03-06 10:15:28,260 [236|<ARRAY>|Discovery|<ip>|86d2ac6e-d1e2-4038-b644-abe43cfa1d3f] DEBUG  SSHDialog.java (line 169) Host: <SWITCH IP>, Port: 22 - sendWaitFor: show zone name <ZONE NAME>     
     
      vipr3 controllersvc 2019-03-06 10:15:28,325 [236|<ARRAY>|Discovery|<IP>|86d2ac6e-d1e2-4038-b644-abe43cfa1d3f] DEBUG  SSHDialog.java (line 108) insr is ready and the buffer will be appended by Zone not present     
     
          
                                                             

 

 

Resolution:

 

 

Enhanced Zoning was not enabled on the switches and this is recommended for ViPR Controller when a VSAN spans multiple switches and more than one of these switches is added to ViPR Controller.                                                           

 

 

Notes:

 

 

ViPR Controller apisvc logs :   
        

      vipr1 apisvc 2019-03-05 12:04:08,239 [AsyncTaskExecutorService_865] ERROR VolumeIngestionUtil.java (line 2200) The requested host initiators (<HOSTNAME>:<INITIATOR>, <HOSTNAME>:<INITIATOR>) have no zoning configured.       
       
        vipr1 vipr1 apisvc 2019-03-05 11:46:15,955 [AsyncTaskExecutorService_853]  WARN  IngestVolumesExportedSchedulingThread.java (line 278) Zoning is not consistent across hosts in this cluster. Zoning may be missing, insufficient, or otherwise incompatible for one or more hosts: 1 of <NUMBER_OF_HOST> unmanaged export mask(s) failed zoning checks: The requested host initiators (<HOSTNAME>:<INITIATOR>, <HOSTNAME>:<INITIATOR>) have no zoning configured.       
            at com.emc.storageos.api.service.impl.resource.utils.VolumeIngestionUtil.findMatchingExportMaskForCluster(VolumeIngestionUtil.java:2210)