ViPR Controller: Volume provisioning fails after an SMI-S server failure[1]

           

   Article Number:     531231                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

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

 

Issue:

 

 

When the active SMI-S server goes offline, VIPR controller uses the secondary SMI-S server but volume provisioning fails with the error below:   
   
    VIPR Controller UI error   
    "Error 16001: Message: Unable to call Storage Provider successfully. Caused by: A general error occurred that is not covered by a more specific error code. (com.emc.cmp.osls.se.symm.impl.SymapiSloInfoT.com::emc::cmp::osls::se::symm::impl::SymapiSloInfoT::show:48 C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:126 file: SymStructBase.cpp line: 127 func: com::emc::cmp::osls::se::symm::impl::SymStructBase::throwOnSymError errcode: 126 sym err: An internal error occurred during a SYMAPI operation. Please report to EMC message: SymapiSloInfoT::show fail)     
      Description: Creating volumes:     
      Volume: 00000_w000_xxx1_xx_xxx_XX-XXX-XXX-00_0000 (urn:storageos:Volume:e95763b5-f5e3-43af-bccd-6c7fd571xxxxx:vdc1)"
                                                           

 

 

Cause:

 

 

   

         
  1.         The VMAX array which is managed by ViPR Controller is registered to 2 different SMI Providers, both of which are discovered by ViPR Controller.     
  2.      
  3.         SMI Provider #1 is running Solutions Enabler v9.0 and ViPR C was provisioning successfully when discovering the VMAX using this provider.     
  4.      
  5.         SMI Provider #1 went offline or became unreachable due to a hardware issue.     
  6.      
  7.         ViPR Controller switched to use SMI Provider #2 which is running Solutions Enabler v8.4 but was unable to discover the VMAX as the VMAX is an All Flash array and this is not supported by Solutions Enabler v8.4.     
  8.      
  9.         After the hardware issue was resolved on SMI Provider #1, ViPR Controller does not automatically switch back to this provider for VMAX discovery.      
  10.    
                                                             

 

 

Change:

 

 

The active SMI-S Provider (for a VMAX array in VIPR Controller) goes offline or becomes unreachable.                                                           

 

 

Resolution:

 

 

Perform the below steps:   

         
  1.         Login to the respective SMI-S Storage Provider #2     
  2.      
  3.         Locate the SymCLI Installation Directory - the default location is C:\Program Files\EMC\SYMAPI     
  4.      
  5.         Change to the sub-directory "config"     
  6.      
  7.         Edit or Create a text file named  "symavoid"     
  8.      
  9.         Add the serial number of the VMAX array and save the file ( The serial number can be obtained from ViPR Controller UI or from a "symcfg list" command on the SMI Provider.     
  10.      
  11.         Open up a Command Prompt with Administrative Privileges     
  12.      
  13.         Run: "symcfg -sid <arrayid> remove" . This will remove the array from the local symapi db, management of the array from this SMIS-S server will not be possible.     
  14.      
  15.         Open up "Computer Management" → Services and Applications → Services. Restart the "ECOM" service     
  16.      
  17.         Login to the ViPR Controller UI     
  18.      
  19.         Go to "Physical" → "Storage Providers". Select the respective Storage Provider (SMI Provider #2 and rediscover it.     
  20.      
  21.         Assuming SMI-S Provider #1 is online, re-discover it in the VIPR-C UI also.     
  22.      
  23.         In the VIPR-C UI, Verify that the VMAX array is no longer listed under the storage provider after the discovery finishes     
  24.    
   

     
      Note: If the VMAX array needs to be re-added to the SMI-S Provider #2 for any reason please do the following :   

   
         
  1.         Ed​it the symavoid file and remove or comment (with a #) the array serial number     
  2.      
  3.         Open up a Command Prompt with Administrative Privileges     
  4.      
  5.         Run: "symcfg discover"     
  6.