VPLEX: RecoverPoint related CLI commands stuck and impacting the health-check command

           

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

 


Product:

 

VPLEX Series,VPLEX GeoSynchrony,VPLEX GeoSynchrony 5.4 Service Pack 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 3,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 5

 

Issue:

 

 

Executing RecoverPoint related commands like "rp summary" and "rp validate-configuration" causes the CLI to become stuck until the connection is lost either by timing out or by restarting the management console.    

         
  •         Issuing the 'rp summary' command will hang blocking the CLI and taking a lot of time until auto disconnecting from the VPLEXCLI.      
  •    
VPlexcli:/> rp summary   

      Connection closed by foreign host. << after time this is the result   

   
         
  •         Issuing "rp validate-configuration" will take a long time in the "Validating volumes" phase of this command until auto disconnecting from the VPLEXCLI.      
  •    
        

      VPlexcli:/> rp validate-configuration       
        Info: Able to contact director-2-1-A at 128.221.252.67.       
        Info: Able to contact director-2-1-B at 128.221.252.68.       
        Info: Able to contact director-2-2-A at 128.221.252.69.       
        Info: Able to contact director-2-2-B at 128.221.252.70.       
        Info: Able to contact director-2-3-A at 128.221.252.71.       
        Info: Able to contact director-2-3-B at 128.221.252.72.       
        Info: Able to contact director-2-4-A at 128.221.252.73.       
        Info: Able to contact director-2-4-B at 128.221.252.74.       
        =======================================================       
        =======================================================       
        Validate the VPLEX Kdrivers       
        =======================================================       
        =======================================================       
        Validating that VPLEX Kdrivers are installed OK       
        Validating that all VPLEX Kdriver versions agree OK       
        Validating the VPLEX Kdriver status OK       
        =======================================================       
        =======================================================       
        Validate RecoverPoint Appliance Clusters       
        =======================================================       
        =======================================================       
        Validating that VPLEX management server can reach all attached RecoverPoint Appliance Clusters OK       
        Validating that all attached RecoverPoint Appliance Clusters are healthy OK       
        Validating that each registered RecoverPoint Appliance Cluster is associated correctly with the VPLEX Cluster in the I/O path       
        OK       
        Validating that all RecoverPoint Appliance Clusters configured to VPLEX are registered to VPLEX management server       
        ERROR       
        RecoverPoint initiator port(s) 0x5001248004c1c603, 0x5001248004c1d612, 0x5001248004327603, 0x5001248004328612, 0x500124800e727603, 0x500124800e728612, 0x5001248005b27603, 0x5001248005b28612, 0x5001248007726603, 0x5001248007727612, 0x5001248004a27603, 0x5001248004a28612, 0x5001248004f26603, 0x5001248004f27612, 0x5001248007626603, 0x5001248007627612 are not associated with any registered RecoverPoint Appliance Cluster(s).       
        =======================================================       
        ​​​​​​​=======================================================       
        Validate Storage Views       
        =======================================================       
        ​​​​​​​=======================================================       
        Validating that storage views do not have mixed non-RecoverPoint and RecoverPoint initiator ports OK       
        Validating that RecoverPoint storage views have access to multiple RecoverPoint ports OK       
        Validating that no volume is exposed to more than one RecoverPoint storage view OK       
        Validating that no journal or repository volumes are exposed to non RecoverPoint hosts OK       
        Validating that only a single RecoverPoint Appliance Cluster is exposed to each RecoverPoint storage view OK       
        =======================================================       
        ​​​​​​​=======================================================       
        Validate Initiator Ports       
        =======================================================       
        ​​​​​​​=======================================================       
        Validating that all RecoverPoint initiator ports are registered OK       
        Validating that all registered initiator ports are registered as correct type OK       
        Validating that all registered RecoverPoint initiator ports are used OK       
        Validating that all RecoverPoint initiator ports have an associated RecoverPoint Appliance Cluster OK       
        =======================================================       
        ​​​​​​​=======================================================       
        Validate Volumes
<<<< here it seems to hang     
      =======================================================       
        ​​​​​​​=======================================================
   

Connection closed by foreign host.   
   
        
         
  •         After enabling advanced logging as per KB 477533,  client logs will stream "still waiting for pending refreshes" events. This means that the VPLEX is still waiting for RecoverPoint responses.      
  •    
    Sample output from client.log:   
    12:55,695 DEBUG [DefaultCommandHandler-Thread-7124] ConsistencyGroupRecoverPoint: Still waiting for pending refreshes on [preferred-cluster, recoverpoint-information, vplex-rp-cg-alignment-status, protection-type, vplex-rp-cg-alignment-indications, active-replicating-rp-cluster]   
         
  •         Investigating the tcpdumps file between the VPLEX management server and the RecoverPoint will show that VPLEX is trying to establish a connection to the RecoverPoint via SSL port "443" yet the firewall is blocking the connection of this port.      
  •    
   
         
  •         The "health-check" command will take a long time as the "health-check" command retrieves information from the RecoverPoint side.      
  •    
                                                             

 

 

Cause:

 

 

The end user's firewall is blocking the SSL connection, port "443", between the VPLEX management server and RecoverPoint.                                                           

 

 

Change:

 

 

Adding RecoverPoint to the VPLEX                                                           

 

 

Resolution:

 

 

   

      Communication between the VPLEX management server and the RecoverPoint     
      over SSL "port 443" should be allowed bi-directional.     
     
      Allowing bi-directional communication between the VPLEX and the RecoverPoint over SSL port "443" solved the issue. The commands ran without issues in the     
      expected time.