NVP-vProxy: vProxies show unavailable after upgrading the NetWorker Server to 18.2.0.0

           

   Article Number:     530031                                   Article Version: 5     Article Type:    Break Fix 
   

 


Product:

 

NetWorker 18.2

 

Issue:

 

 

The NetWorker VMware Protection integration is configured with the vProxy Appliance.  The environment was upgraded to NetWorker 18.2.x and the vProxies show an alert in the NetWorker Management Console (NMC) indicating the vProxies are unavailable.  The re-registration of an existing or the registration of a new vProxy fails with "libCURL: function "curl_easy_perform" returned error 7".   
   
    The daemon.log shows:   

MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR info VM proxy Warning event: vProxy 'vproxy01' is unavailable. MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrdisp_vproxy NSR info libCURL: function "curl_easy_perform" returned error 7: "Failed connect to [VPROXY_NAME]:9090; No error" MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrmon NSR info libCURL: function "curl_easy_perform" returned error 7: "Failed connect to [VPROXY_NAME]:9090; No error"    
                                                             

 

 

Cause:

 

 

The NetWorker server has two network interfaces and the vProxy does not recognize the second interface. The vProxy is using the backup network interface to perform the registration and the NetWorker server is identifying with the primary network interface.                                                           

 

 

Change:

 

 

The NetWorker Server was upgraded to 18.2.0.0 from 9.x or 18.1.x.                                                           

 

 

Resolution:

 

 

The issue has been resolved in the NetWorker 18.2.0.2 with 3.0.1-2 release. Install the latest NetWorker 18.2.0.x cumulative hot fix package to resolve the symptom. The latest cumulative hot fix is available on the Dell EMC NetWorker Support Download web page:   
   
    https://support.emc.com/downloads/1095_NetWorker   
   
    Workaround:   
   
    Change the metric for the backup network interface to have a higher priority from the primary network interface.    
   
    1) Run the ipconfig command line utility from a command prompt to validate the current network settings.  In the following ipconfig output the Ethernet0 interface is the primary network interface and Ethernet1 is the backup network interface.   
        

C:\>ipconfigWindows IP ConfigurationEthernet adapter Ethernet0: Connection-specific DNS Suffix  . :    IPv4 Address. . . . . . . . . . . : 192.xxx.x.xxx   Subnet Mask . . . . . . . . . . . : 255.xxx.xxx.x    Default Gateway . . . . . . . . . : 192.xxx.x.xEthernet adapter Ethernet1:   Connection-specific DNS Suffix  . :    IPv4 Address. . . . . . . . . . . : 192.xxx.x.xxx    Subnet Mask . . . . . . . . . . . : 255.xxx.xxx.x    Default Gateway . . . . . . . . . :...    
   
    2) The default priority for each network interface is the same. Use the Get-NetInterface command line utility from the PowerShell command prompt to validate the priority.   
        
PS C:\Users\> Get-NetipinterfaceifIndex InterfaceAlias  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore------- --------------  ------------- ------------ --------------- ----     --------------- -----------...3       Ethernet1       IPv4                  1500              25 Disabled Connected       ActiveStore6       Ethernet0       IPv4                  1500              25 Disabled Connected       ActiveStore    
   
    3) Change the backup network to have a higher priority (lower InterfaceMetric).  Use the set-Netipinterface command line utility from the PowerShell command prompt to set the new interfaceMetric.   
        
PS C:\Windows\system32>  set-Netipinterface -interfaceindex 3 -interfacemetric 1    
   
    4) Validate the new network interface priority on the server with the Get-NetInterface command line utility.   
PS C:\Windows\system32> Get-NetipinterfaceifIndex InterfaceAlias AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore------- -------------- ------------- ------------ --------------- ----     --------------- -----------...3       Ethernet1      IPv4                  1500               1 Disabled Connected       ActiveStore6       Ethernet0      IPv4                  1500              25 Disabled Connected       ActiveStore