ViPR Controller: Approved actionable event results in Error 18000: An error occurred while executing a job in the VPLEX device

           

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

 


Product:

 

ViPR Controller

 

Issue:

 

 

When an ESXi host is moved out of a cluster and the actionable event is accepted to remove storage from the host, the below error is received.     
   
    ViPR Controller GUI will show:   

      Error 18000: An error occurred while executing a job in the VPLEX device       
       
        Message: Message: Message: Error encountered in deleting initiator from export group, Op: DELETE INITIATOR FROM EXPORT GROUP caused by Validation of export mask <ExportMask maskName> (<URN of ExportMask>) on storage system SDCE1VPLEX (<VPLEX URN>) failed.       
       
        Internal Details: Controller database object ID [<ExportMask maskName> (null)(<URN of ExportMask>)], field [virtual-volume/snap WWN]: The hardware reported entry [<WWN of unmanaged volume> (<Label of unmanaged volume>)], whereas the controller is not managing or does not have a reference to the same resource
   
                                                             

 

 

Cause:

 

 

The cause of this issue is that the the ESXi host has a VPLEX boot LUN that is not managed by ViPR Controller.                                                             

 

 

Change:

 

 

The user moved an ESXi host out of the cluster and accepted the Actionable Event to remove the cluster LUNs from the host.                                                           

 

 

Resolution:

 

 

Resolution   
    The user exclusively, fully ingested the VPLEX boot LUN into ViPR Controller management resolving the issue.   

         
  1.         Discover Unmanaged Volumes     
  2.    
   
      Catalog > Vew Catalog > Block Storage Services > Discover Unmanaged Volumes   
   
         
  1.         Ingest Exported Unmanaged Volumes     
  2.    
   
      Catalog > Vew Catalog >Block Storage Services > Ingest Exported Unmanaged Volumes   
   
      For Storage Type select Exclusive from the drop down menu   
   
      For Ingestion Method select Full Ingestion Backend Volumes to ingest the virtual volumes and the backend volumes   
   
      Fill in the form as appropriate for the volume to be ingested   
   
      For further details reference the EMC ViPR Controller 3.6 Service Catalog Reference Guide.   
   
    EMC customers can download documentation or software from EMC Online Support.  From the EMC Support home page menu bar, select Support by Product, search for the product using "Find a Product". The product page provides one-stop access to technical and support-related information by EMC product for downloads, documentation, tools and additional content.   
   
    Because the view is restricted based on customer agreements, you may not have permission to view certain documentation or software downloads. Should you not see documentation or software downloads you believe you should have access to, follow the instructions in How to get assistance for EMC Online Support tools.   
   
   
   
                                                                

 

 

Notes:

 

 

Controllersvc log:   

      vipr2 vipr2 controllersvc 2017-10-09 18:02:27,945 [15995|exportRemoveInitiators|6d767380-bb6c-43be-9e73-64c80fb77819fa99eae1-c893-4664-a82e-249197641156]  INFO  ValidatorLogger.java (line 66) Controller database object ID [<ExportMask maskName> (null)(<URN of ExportMask>)], field [virtual-volume/snap WWN]: The hardware reported entry [<WWN of unmanaged volume> (<Label of unmanaged volume>)], whereas the controller is not managing or does not have a reference to the same resource       
        vipr2 vipr2 controllersvc 2017-10-09 18:02:27,947 [15995|exportRemoveInitiators|6d767380-bb6c-43be-9e73-64c80fb77819fa99eae1-c893-4664-a82e-249197641156] ERROR  VPlexDeviceController.java (line 5255) Exception in exportRemoveInitiators: [<URN of initiator>, <URN of initiator>]       
        Internal Details: Controller database object ID [<ExportMask maskName> (null)(<URN of ExportMask>)], field [virtual-volume/snap WWN]: The hardware reported entry [<WWN of unmanaged volume> (<Label of unmanaged volume>)], whereas the controller is not managing or does not have a reference to the same resource       
        Remediation options are as follows:       
        1. If the extra volumes or initiators not managed by controller are not needed, modify the export mask manually on the storage array to reflect controllers representation.       
        2. Inventory-only delete all volumes in this export mask and ingest the volumes back into the controller.       
        3. Contact EMC Support for additional remediation paths including a force option for advanced users.       
        Additional Details:       
        This occurred when comparing the controller-managed initiators and/or volumes against the volumes and initiators on the storage array.       
        This inconsistency may cause undesired or unintended export updates on the storage array that may impact externally-managed hosts and clusters.       
        The internal details in this message highlight external volumes or initiators that may be impacted if the controller proceeds with this export operation.       
        This may have occurred as the result of an export mask (masking view or similar) changing outside of the controller.       
         at com.emc.storageos.volumecontroller.impl.validators.ValidatorLogger.generateException(ValidatorLogger.java:113)       
         at com.emc.storageos.volumecontroller.impl.validators.DefaultValidator.validate(DefaultValidator.java:55)       
         at com.emc.storageos.vplexcontroller.VPlexDeviceController.exportGroupRemoveInitiators(VPlexDeviceController.java:5214)       
         at com.emc.storageos.volumecontroller.impl.block.ExportWorkflowEntryPoints.exportRemoveInitiators(ExportWorkflowEntryPoints.java:295)       
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)       
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)       
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)       
         at java.lang.reflect.Method.invoke(Method.java:498)       
         at com.emc.storageos.volumecontroller.impl.Dispatcher$DeviceMethodInvoker.run(Dispatcher.java:273)       
         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)       
         at java.util.concurrent.FutureTask.run(FutureTask.java:266)       
         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)       
         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)       
         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)       
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)       
         at java.lang.Thread.run(Thread.java:745)