ViPR Controller: Export Volume order fails with, "Error 22003: Failed to create zones for export group because of: Could not find an active zoneset for fabric"

           

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

 


Product:

 

ViPR Controller,ViPR Controller Controller 3.0

 

Issue:

 

 

User is running ViPR Controller with Cisco MDS switch and is unable to export a volume a host.   
   
   
    When trying to export volumes, the user sees the following in the "orders" directory of a ViPR C logs collect :   
        

      ORDER DETAILS       
        -------------       
        Order ID: urn:storageos:Order:<URN>       
        Order Number: <ORDER #>       
        Submitted By: root       
        Date Submitted: <DATE>       
        Date Completed: <DATE>       
        Message: Error 22003: Failed to create zones for export group because of: Could not find an active zoneset for fabric 40.  ; Rollback error: Zoning rollback operation failed for export group urn:storageos:ExportGroup:<URN>, because of: Could not find an active zoneset for fabric 50.  ; Rollback error: Failed to remove zones for removed export mask because of: Could not find an active zoneset for fabric 50.        
        Status: ERROR       
        Catalog Service: Export Volume to a Host       
        Catalog ID: urn:storageos:CatalogService:<URN>       
        Base Service: ExportVolume       
        Requires Approval? false       
        Requires Execution Window? false
   
   
   
        
          
                                                             

 

 

Cause:

 

 

There is a requirement within ViPR that one active zoneset is required at the switch per COP-25598. The user has confirmed that zonesets are in fact active in their environment:   
        

      Fabric A       
        hostname# sh zoneset active | i zoneset       
        zoneset name <zoneset name>       
        hostname#       
                
        Fabric B       
        hostname# sh zoneset active | i zoneset       
        zoneset name <zoneset name>       
        hostname#
     
          
    In this case, it was noted in the controllersvc.log that enhanced zoning was not enabled:   
        
      WARN  MDSDialog.java (line 960) Enhanced zoning not enabled   
   
     
      According to the ViPR Controller support matrix, Cisco MDS requires that Enhanced Zoning be enabled.      
     
     
     
          
                                                             

 

 

Resolution:

 

 

Enable Enhanced Zoning per Cisco documentation, re-discover network within ViPR and re-submit the order.