Highlighted
carlos_romero
1 Copper

VDDK Error: 14009: The server refused connection

Jump to solution

I have a Networker 9.2.1 with a vproxy on vmware6. I am trying to do a nbd backup on a different esx where the vproxy is installed. The backup of another VM on the esx where the vproxy is, works without issue.

I already check the port 902 (telnet) from the vproxyVM to the ESX host and it works. the nslookup too.

Tags (2)
Reply
1 Solution

Accepted Solutions
Highlighted
carlos_romero
1 Copper

Re: VDDK Error: 14009: The server refused connection

Jump to solution

Ok, I resolved the issue.

The actual problem was SSL protocol not supported (old versions tls.protocols=tls1.0,tls1.1,tls1.2 ). This happen because one of the esxi host was version 5.1 (not supported), The client is going to migrate those VMs to the esxi version 5.5 and above . I already did the test on those esx and all work fine.

View solution in original post

Reply
5 Replies
Highlighted
crazyrov
4 Tellurium

Re: VDDK Error: 14009: The server refused connection

Jump to solution

Hi Carlos,

             Can you check the vbackupd-vddk.log at the location /opt/emc/vproxy/runtime/logs/vbackupd/ on the NvProxy and see what error you see there or which host is not being able to be communicated to.

Reply
Highlighted
carlos_romero
1 Copper

Re: VDDK Error: 14009: The server refused connection

Jump to solution

Thanks for the reply,

I check the log and saw this:

AVP01V/Template_WS2008R2x.vmdk.

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLibVim: Request RandomAccessRO diskKey = 2000, readOnly = 1, openSnapshot = 0.

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2018/03/07 11:22:11 NOTICE: VDDK INFO NBD_ClientOpen: attempting to create connection to vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902

2018/03/07 11:22:11 NOTICE: VDDK WARN SSL: Unknown SSL Error

2018/03/07 11:22:11 NOTICE: VDDK INFO SSL Error: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol

2018/03/07 11:22:11 NOTICE: VDDK WARN SSL: connect failed (1)

2018/03/07 11:22:11 NOTICE: VDDK INFO CnxAuthdConnect: Returning false because SSL_ConnectAndVerify failed

2018/03/07 11:22:11 NOTICE: VDDK INFO CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2018/03/07 11:22:11 NOTICE: VDDK INFO Cnx_Connect: Returning false because CnxConnectAuthd failed

2018/03/07 11:22:11 NOTICE: VDDK INFO Cnx_Connect: Error message:

2018/03/07 11:22:11 NOTICE: VDDK WARN [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error:

2018/03/07 11:22:11 NOTICE: VDDK WARN SSL: Unknown SSL Error

2018/03/07 11:22:11 NOTICE: VDDK INFO SSL Error: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol

2018/03/07 11:22:11 NOTICE: VDDK WARN SSL: connect failed (1)

2018/03/07 11:22:11 NOTICE: VDDK INFO CnxAuthdConnect: Returning false because SSL_ConnectAndVerify failed

2018/03/07 11:22:11 NOTICE: VDDK INFO CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2018/03/07 11:22:11 NOTICE: VDDK INFO Cnx_Connect: Returning false because CnxConnectAuthd failed

2018/03/07 11:22:11 NOTICE: VDDK INFO Cnx_Connect: Error message:

2018/03/07 11:22:11 NOTICE: VDDK WARN [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error:

2018/03/07 11:22:11 NOTICE: VDDK INFO NBD_ClientOpen: Couldn't connect to vmwarea.berlitz.com.co:902

2018/03/07 11:22:11 NOTICE: VDDK INFO DISKLIB-DSCPTR: : "vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902" : Failed to open NBD extent.

2018/03/07 11:22:11 NOTICE: VDDK INFO DISKLIB-LINK  : "vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902" : failed to open (NBD_ERR_NETWORK_CONNECT). 

2018/03/07 11:22:11 NOTICE: VDDK INFO DISKLIB-CHAIN : "vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902" : failed to open (NBD_ERR_NETWORK_CONNECT).

2018/03/07 11:22:11 NOTICE: VDDK INFO DISKLIB-LIB   : Failed to open 'vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: Detected DiskLib error 2338 (NBD_ERR_NETWORK_CONNECT).

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: Failed to open disk vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902!52 24 3c b6 cb f9 f9 ad-f5 f2 19 07 70 dc df 41. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 4799.

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore A] AVP01V/Template_WS2008R2x.vmdk. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 5026.

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore A] AVP01V/Template_WS2008R2x.vmdk. Error 14009 (The server refused connection) at 5064.

2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Disconnect: Disconnect.

It seem some kind of SSL error, but dont know how to solve it yet.

This error occur when i I tried to make a backup of a VM with NBD on a different ESX where the vproxy is.

Reply
Highlighted
crazyrov
4 Tellurium

Re: VDDK Error: 14009: The server refused connection

Jump to solution

So your are saying that if you use hotadd the backups work ?

Reply
Highlighted
carlos_romero
1 Copper

Re: VDDK Error: 14009: The server refused connection

Jump to solution

Ok, let me explain better. The hotadd and the NBD works as long as the VMs are on the same ESXi host as the vproxy. When the VMs that I am trying to backup are not on the same ESXi host as the vproxy the NBD is not working.

I need to use the NBD protocol because not all the storage on the ESXi host are SAN base, some are local.

Reply
Highlighted
carlos_romero
1 Copper

Re: VDDK Error: 14009: The server refused connection

Jump to solution

Ok, I resolved the issue.

The actual problem was SSL protocol not supported (old versions tls.protocols=tls1.0,tls1.1,tls1.2 ). This happen because one of the esxi host was version 5.1 (not supported), The client is going to migrate those VMs to the esxi version 5.5 and above . I already did the test on those esx and all work fine.

View solution in original post

Reply