ViPR SRM: VNX discovery error.

           

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

 


Product:

 

ViPR SRM,ViPR SRM 4.2,ViPR SRM 4.1,ViPR SRM 4.0,ViPR SRM 3.7

 

Issue:

 

 

While discovering a VNX array the test completes with errors.   
   
    The expanded test result displays an error on line 53.   
   
    line 53: fail: command returned with a non-zero status (status: 1)!   
   
    >>>INFO: The SSL connection result for SPA is: 0   
    >>>INFO: The SSL connection succeeded for SPA.   
    >>>INFO: The SSL connection result for SPB is: 0   
    >>>INFO: The SSL connection succeeded for SPB.   
    >>>ERROR: 1   
   
    Expanded Discovery Test Result.
                                                           

 

 

Cause:

 

 

NavisecCLI was installed in a different location which was causing the issue.   
   
    After saving the configuration (despite the test result) you should see an error similar to the one below in the collecting logs:   
   
   
    SEVERE     -- [2018-03-25 18:21:40 EDT] -- LocalCommandRetriever::execute(): Error while executing primary command @{command}   
    java.io.IOException: Cannot run program "C:\Program Files (x86)\EMC\Navisphere CLI\NaviSECCli.exe" (in directory "D:\Program Files\APG\Collecting\Stream-Collector\emc-vnx\."): CreateProcess error=2, The system cannot find the file specified   
   
    Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
                                                           

 

 

Change:

 

 

The NavisecCLI was not installed in the default path. Updating the navisecCLI path in the SolutionPack configuration resolved the issue.                                                           

 

 

Resolution:

 

 

To rectify this issue:   

         
  1.         Navigate to Centralized Management >> SolutionPacks >> EMC Unity/VNX/VNXe     
  2.      
  3.         Edit (pencil icon) the Data collection component. You’ll find the option to mention the NavisecCLI path here.     
  4.      
  5.         Mention the location of Naviseccli and reconfigure the SolutionPack.     
  6.      
  7.         Rediscover the array and it should go through successfully.     
  8.    
   
    User-added image   
   
   
    User-added image