Discussions specific to the VMware vSphere hypervisor
Post Reply
c0t0d0s0
Novice
Posts: 4
Liked: never
Joined: Sep 15, 2015 1:14 pm
Full Name: Michael Westman

NFC storage connection is unavailable.

Post by c0t0d0s0 »

We are demoing hardware from Nutanix and have run into a goofy problem. When we have a VM running on the Nutanix cluster we cannot back it up with Veeam. If we move it to a traditional server with traditional storage we can backup just fine. Same vCenter, same Veeam.

Error is:
10/4/2015 4:11:08 PM :: Processing mc1-txsw-ci Error: NFC storage connection is unavailable. Storage: [stg:datastore-590,nfchost:host-587,conn:mc1-vcenter60.<domain>]. Storage display name: [nutanix].
Failed to create NFC download stream. NFC path: [nfc://conn:mc1-vcenter60.<domain>,nfchost:host-587,stg:datastore-590@mc1-txsw-ci/mc1-txsw-ci.vmx].

Any thoughts?

PTide
Product Manager
Posts: 5574
Liked: 531 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: NFC storage connection is unavailable.

Post by PTide »

Hi,

Please try this article to troubleshoot the issue. If nothing helps please open a case with support and post your case ID here.

Thank you.

c0t0d0s0
Novice
Posts: 4
Liked: never
Joined: Sep 15, 2015 1:14 pm
Full Name: Michael Westman

Re: NFC storage connection is unavailable.

Post by c0t0d0s0 »

Looks like an SSL problem:

[05.10.2015 01:24:51] < 4032> nfc| Initializing new SSL connection...
[05.10.2015 01:24:51] < 4032> nfc| Establishing connection with the SSL server... Failed.
[05.10.2015 01:24:51] < 4032> nfc| Initializing new SSL connection... Failed.
[05.10.2015 01:24:51] < 4032> nfc| Opening NFC session with the specified ticket [52 4b ef 38 ba 08 0a 87-45 f1 dc 3c 1c d2 38 8e]... Failed.

c0t0d0s0
Novice
Posts: 4
Liked: never
Joined: Sep 15, 2015 1:14 pm
Full Name: Michael Westman

Re: NFC storage connection is unavailable.

Post by c0t0d0s0 »

Ticket opened: 01075797

Gostev
SVP, Product Management
Posts: 26460
Liked: 4143 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: NFC storage connection is unavailable.

Post by Gostev »

Are you using vSphere 6 Update 1? If yes, see the sticky topic :D

fab69
Lurker
Posts: 1
Liked: never
Joined: Oct 07, 2015 10:37 am
Full Name: Fabian Trowitz
Contact:

Re: NFC storage connection is unavailable.

Post by fab69 »

i had the same problem:

Code: Select all

Connecting to NFC session. Target host: [172.26.18.199]. Storage: [vmDATA99]. VI SOAP connection ID: [VCENTER].
       NFC service: [vpxa-nfc]. Port: [902].
       Establishing connection with the host [172.26.18.199]. Port: [902].
       Resolving host name (172.26.18.199) to IP address...
       Host's IP addresses (172.26.18.199):
       {
         172.26.18.199
       }
        Trying to connect to [172.26.18.199]...
        Succeeded to connect to the remote host. IP: [172.26.18.199]. Port: [902].
        Connection with the host [172.26.18.199] was established.
        Opening NFC session with the specified ticket [52 3e 89 c0 12 47 02 bd-11 ea 00 82 64 69 aa 26]...
        Waiting for the authd reply message...
          220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported, NFCSSL supported/t
        Authd version: [1.10]
        SSL connection is required to perform authentication.
        Initializing the SSL subsystem...
        The SSL subsystem was successfully initialized.
        Initializing new SSL connection...
        Establishing connection with the SSL server... Failed.
        Initializing new SSL connection... Failed.
I found the solution here (reactivate SSLv3 on port 902 on my ESXi hosts)
http://forums.veeam.com/vmware-vsphere- ... 30210.html

I followed the instruction posted here:
http://kb.vmware.com/selfservice/micros ... Id=2121021

fab

bouda05
Lurker
Posts: 1
Liked: never
Joined: Oct 05, 2015 7:19 am
Contact:

Re: NFC storage connection is unavailable.

Post by bouda05 »

I have the same issue on vSphere 6 U1. This version disable SSLv3 which is used for SSL handshake during backup. VMware released update U1a, which enables SSLv3 and resovle this isuse.

alexia_net
Novice
Posts: 4
Liked: 1 time
Joined: Nov 02, 2015 9:32 am
Full Name: Alex
Contact:

[MERGED] Veeam Free

Post by alexia_net »

Hi,
I am trying to take backup of a VM running on a vSphere 6 host. For backup i use Veeam Free. It's for testing purposes. I get an error
2/24/2016 9:54:42 AM :: Processing '<VM>' Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-144,nfchost:host-143,conn:<IP>]. Storage display name: [datastore1 (1)].
Failed to create NFC download stream. NFC path: [nfc://conn:<IP>,nfchost:host-143,stg:datastore-144@<VM>/<VM>.vmx].
The storage is local.
The Veeam server, the VmWare host and the server I try to backup are on the same network segment.

Should the VSS feature be installed along with VmWare tools?

Any tips much appreciated.
Thank you!

foggy
Veeam Software
Posts: 19285
Liked: 1741 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: NFC storage connection is unavailable.

Post by foggy »

Alex, please review the thread above for the hints.

alexia_net
Novice
Posts: 4
Liked: 1 time
Joined: Nov 02, 2015 9:32 am
Full Name: Alex
Contact:

Re: NFC storage connection is unavailable.

Post by alexia_net » 1 person likes this post

Hi,
Thank you. It was one of those two:
- I had to upgrade the Veeam version
- the clock was not in sync between the Veeam server and VmWare host.

Thanks!

veasna.ok
Lurker
Posts: 1
Liked: never
Joined: Feb 03, 2020 6:39 am
Full Name: Veasna Ok
Contact:

Re: NFC storage connection is unavailable.

Post by veasna.ok »

Dear Support,

I followed your guide here but not possible to fix. I would share logs here please help to check.

Code: Select all

[31.01.2020 16:40:53] <  9868> cli| LOG: Parsing log parameters ...
[31.01.2020 16:40:53] <  9868> cli| LOG: Initializing log file ...
[31.01.2020 16:40:53] <  9868> cli| LOG: C:\ProgramData\Veeam\Backup\ESXi-HMS-VLT_RPT/Agent.ESXi-HMS-VLT_RPT.Source.HMS-VLT_RPT-ESXi.log
[31.01.2020 16:40:53] <  9868> ====================================================================================
[31.01.2020 16:40:53] <  9868> {
[31.01.2020 16:40:53] <  9868>   Windows agent.
[31.01.2020 16:40:53] <  9868>   Path to the executable module: C:\Program Files (x86)\Veeam\Backup Transport\x64\VeeamAgent.exe
[31.01.2020 16:40:53] <  9868>   Agent version: 9.5.4.2866
[31.01.2020 16:40:53] <  9868>   Comments: Private Fix TF179079
[31.01.2020 16:40:53] <  9868> cli|   Loading kernel32.dll ...
[31.01.2020 16:40:53] <  9868>   OS version: Microsoft Windows Server 2012 R2 (64-bit) (6.3.9600)
[31.01.2020 16:40:53] <  9868>   Processors num: 8
[31.01.2020 16:40:53] <  9868>   Active processors mask: 255
[31.01.2020 16:40:53] <  9868>   Processor 0: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 1: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 2: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 3: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 4: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 5: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 6: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Processor 7: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
[31.01.2020 16:40:53] <  9868>   Installed memory, MB: 16383
[31.01.2020 16:40:53] <  9868>   PID: 6024
[31.01.2020 16:40:53] <  9868> }
[31.01.2020 16:40:53] <  9868> Adjusting system file cache limit (25 percent)
[31.01.2020 16:40:53] <  9868>   Total physical memory installed: [16383 MB], available: [13229 MB].
[31.01.2020 16:40:53] <  9868>   Maximum file cache size is already [4095 MB].
[31.01.2020 16:40:53] <  9868> VDDK logging level: 1
[31.01.2020 16:40:53] <  9868> Maximum pending blocks value: 10000
[31.01.2020 16:40:53] <  9868> AgentId:{ef9cfde0-2f71-4c03-98dc-a11035daf281}
[31.01.2020 16:40:53] <  3624> Thread started. Thread id: 3624, parent id: 9868, role: Clean up procedure
[31.01.2020 16:40:53] <  9868> Add HostFS to the factories map.
[31.01.2020 16:40:53] <  3624> vim| Entering to the VI connections pool cleanup thread.
[31.01.2020 16:40:53] <  9868> Add cloud to the factories map.
[31.01.2020 16:40:53] <  9868> Add TapeFs to the factories map.
[31.01.2020 16:40:53] <  9868> Add nfc to the factories map.
[31.01.2020 16:40:53] <  9868> Add ddboost to the factories map.
[31.01.2020 16:40:53] <  9868> Add storeonce to the factories map.
[31.01.2020 16:40:53] <  9868> Add fakestoreonce to the factories map.
[31.01.2020 16:40:53] <  9868> Loading options.
[31.01.2020 16:40:53] <  9868> Management connection keyset: 'ID: 04d83eb43cfe55a3e25546e8e15aef2f (session), keys: 1, repair records: 0 (master keys:)'.
[31.01.2020 16:40:53] <  9448> Thread started. Thread id: 9448, parent id: 9868, role: Session container
[31.01.2020 16:40:53] <  9448> srv| Srv. cleanup thread is started.
[31.01.2020 16:40:53] <  9868> cli| Client session has been started.
[31.01.2020 16:40:53] < 10092> cli| Thread started. Thread id: 10092, parent id: 9868, role: VRPC server thread
[31.01.2020 16:40:53] < 10092> net| Veeam RPC server started.
[31.01.2020 16:40:53] < 10092> cli| SIO_LOOPBACK_FAST_PATH is disabled in configuration
[31.01.2020 16:40:53] < 10092> net| Selected vRPC port: '2501'.
[31.01.2020 16:40:53] < 10092> net| Listening vRPC port '2501'.
[31.01.2020 16:40:53] <  9868> cli|   Opening event: [VeeamEvent{fcec26cb-5993-4a69-8fc2-d88201e72aeb}]
[31.01.2020 16:40:53] <  9868> cli|   Opening shared memory: [VeeamMem{fcec26cb-5993-4a69-8fc2-d88201e72aeb}]
[31.01.2020 16:40:53] < 10092> net|   Accepted incoming vRPC connection from '127.0.0.1:51709'.
[31.01.2020 16:40:53] <  7576> cli| Thread started. Thread id: 7576, parent id: 10092, role: Client processor thread (127.0.0.1:51709)
[31.01.2020 16:40:53] <  7576> net| Client connected...
[31.01.2020 16:40:53] <  7576> cli| Creating session ( redirect output session: 'false')
[31.01.2020 16:40:53] <  7576> cli| CAgentFlowDispatcher: connection will be encrypted. Management keyset: 'ID: 04d83eb43cfe55a3e25546e8e15aef2f (session), keys: 1, repair records: 0 (master keys:)'.
[31.01.2020 16:40:53] <  7576> cli| Client works in standalone mode.
[31.01.2020 16:40:53] < 10092> net|   Accepted incoming vRPC connection from '172.16.100.7:51710'.
[31.01.2020 16:40:53] <  8544> cli| Thread started. Thread id: 8544, parent id: 10092, role: Client processor thread (172.16.100.7:51710)
[31.01.2020 16:40:53] <  8544> net| Client connected...
[31.01.2020 16:40:53] <  8544> cli| Creating session ( redirect output session: 'false')
[31.01.2020 16:40:53] <  8544> cli| CAgentFlowDispatcher: connection will be encrypted. Management keyset: 'ID: 04d83eb43cfe55a3e25546e8e15aef2f (session), keys: 1, repair records: 0 (master keys:)'.
[31.01.2020 16:40:53] <  8544> cli| Client works in standalone mode.
[31.01.2020 16:40:53] <  8544> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  8544> cli| Generic.SetNetworkReconnectOptions
[31.01.2020 16:40:53] <  8544> cli|   (EUInt64) AttemptIntervalMs = 15000
[31.01.2020 16:40:53] <  8544> cli|   (EBoolean) Enabled = true
[31.01.2020 16:40:53] <  8544> cli|   (EUInt64) OverallTimeoutMs = 1800000
[31.01.2020 16:40:53] <  8544> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[31.01.2020 16:40:53] <  8544> cli| New client-server reconnection options were set and will be applied to future connections.
[31.01.2020 16:40:53] <  8544> cli| Reconnects: enabled.
[31.01.2020 16:40:53] <  8544> cli| Overall reconnect timeout [ms]: 1800000.
[31.01.2020 16:40:53] <  8544> cli| Single attempt interval [ms]: 15000.
[31.01.2020 16:40:53] <  8544> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  8544> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  8544> cli| Generic.EnableAgentReconnectPolicy
[31.01.2020 16:40:53] <  8544> cli|   (EBoolean) IsRemoteAgent = true
[31.01.2020 16:40:53] <  8544> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[31.01.2020 16:40:53] <  8544> cli| Enabling agent reconnection policy. Mode: [remote].
[31.01.2020 16:40:53] <  8544> cli| Remote agent reconnection policy is active.
[31.01.2020 16:40:53] <  8544> cli| This client session is a control session. Client-server reconnection will be suspended if this session fails until it is re-established.
[31.01.2020 16:40:53] <  8544> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] < 10092> net|   Accepted incoming vRPC connection from '172.16.100.7:51711'.
[31.01.2020 16:40:53] <  8768> cli| Thread started. Thread id: 8768, parent id: 10092, role: Client processor thread (172.16.100.7:51711)
[31.01.2020 16:40:53] <  8768> net| Client connected...
[31.01.2020 16:40:53] <  8768> net| Received reconnect options: [enabled: timeout 1800000, interval 15000].
[31.01.2020 16:40:53] <  8768> cli| Creating client session in raw binary mode (redirect output session: 'true')
[31.01.2020 16:40:53] <  8768> cli| Thread finished. Role: 'Client processor thread (172.16.100.7:51711)'.
[31.01.2020 16:40:53] <  7444> cli| Thread started. Thread id: 7444, parent id: 8768, role: (async) reconn. receiver {895a12ce-9fce-449f-8c9a-d1bc42efb4f9}
[31.01.2020 16:40:53] <  7444> alg| Receiver stage: running recv cycle.
[31.01.2020 16:40:53] < 10044> cli| Thread started. Thread id: 10044, parent id: 8768, role: (async) reconn. sender {895a12ce-9fce-449f-8c9a-d1bc42efb4f9}
[31.01.2020 16:40:53] <  1216> cli| Thread started. Thread id: 1216, parent id: 8768, role: (async) client session (172.16.100.7:51711)
[31.01.2020 16:40:53] < 10044> alg| Sender stage: running send cycle. Resend list: [0].
[31.01.2020 16:40:53] <  1216> cli| CliSessionRunnableStage: connection will be encrypted. Management keyset: 'ID: 04d83eb43cfe55a3e25546e8e15aef2f (session), keys: 1, repair records: 0 (master keys:)'.
[31.01.2020 16:40:53] <  1216> cli| Registering stdin/stdout redirector: '179911259472'.
[31.01.2020 16:40:53] <  1216> cli| Client works in standalone mode.
[31.01.2020 16:40:53] <  1216> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  1216> cli| VDDK.SetApiVersion
[31.01.2020 16:40:53] <  1216> cli|   (EBoolean) IsCloudConfig = false
[31.01.2020 16:40:53] <  1216> cli|   (EUInt32) Major = 6
[31.01.2020 16:40:53] <  1216> cli|   (EUInt32) Minor = 0
[31.01.2020 16:40:53] <  1216> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[31.01.2020 16:40:53] <  1216> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  1216> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  1216> cli| System.SetSoapCredentials
[31.01.2020 16:40:53] <  1216> cli|   (EString) ConnectionId = ESXi
[31.01.2020 16:40:53] <  1216> cli|   (EString) Host = ESXi
[31.01.2020 16:40:53] <  1216> cli|   (EInt32) Port = 443
[31.01.2020 16:40:53] <  1216> cli|   (EString) Thumbprint = 75:2F:35:E8:03:CC:4B:BB:89:78:5B:59:A1:57:28:D2:E8:BB:9B:69
[31.01.2020 16:40:53] <  1216> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[31.01.2020 16:40:53] <  1216> cli| Updating vmware SOAP credentials on local side (connection id: 'ESXi', host: '10.0.0.6', port: '443', user: 'root').
[31.01.2020 16:40:53] <  1216> vim| Allocating SOAP VI connection. Connection ID: [ESXi]. Target host: [ESXi]. Login: [root].
[31.01.2020 16:40:53] <  1216> vim| SOAP VI connection was successfully allocated. Connection ID: [ESXi].
[31.01.2020 16:40:53] <  1216> cli| -------------------------------------------------------------------------------
[31.01.2020 16:40:53] <  1216> cli| Next client command: [disconnect].
[31.01.2020 16:40:53] <  1216> cli| 
[31.01.2020 16:40:53] <  1216> cli| _______________________________________________________________________________
[31.01.2020 16:40:53] <  1216> cli| Waiting for the next command.
[31.01.2020 16:40:53] <  1216> cli| Next client command: [connectLocal].
[31.01.2020 16:40:53] <  1216> cli|       :>  ESXi.7:2500
[31.01.2020 16:40:53] <  1216> cli|       :>  Veambackup.sunandmoonhotel.com:2500
[31.01.2020 16:40:53] <  1216> cli|       :>  .
[31.01.2020 16:40:53] <  1216> cli|       :>  0
[31.01.2020 16:40:53] <  1216> cli|       :>  {edb7775a-6783-4456-b09a-b66aad58447a}
[31.01.2020 16:40:53] <  1216> cli|       :>  {093ec692-3b2a-4e12-82d4-66dd573dc6b0}
[31.01.2020 16:40:53] <  1216> cli|       :>  2
[31.01.2020 16:40:53] <  1216> cli|       :>  00000000-0000-0000-0000-000000000000
[31.01.2020 16:40:53] <  1216> cli| Connecting to the server agent with the following parameters: [172.16.100.7:2500; Veambackup.sunandmoonhotel.com:2500].
[31.01.2020 16:40:53] <  1216> cli|   [Hook] Creating redirection hooks rules instance.
[31.01.2020 16:40:53] <  1216> cli|   All client-server connections will be established using following reconnect options:
[31.01.2020 16:40:53] <  1216> cli|     Reconnects: enabled.
[31.01.2020 16:40:53] <  1216> cli|     Overall reconnect timeout [ms]: 1800000.
[31.01.2020 16:40:53] <  1216> cli|     Single attempt interval [ms]: 15000.
[31.01.2020 16:40:53] <  1216> cli|   Trying to connect to the endpoint [ESXi:2500]
[31.01.2020 16:40:53] <  1216> cli|   Connection status: system:0 ( The operation completed successfully ).
[31.01.2020 16:40:53] <  1216> cli|   Attempting to establish shared memory connection.
[31.01.2020 16:40:53] <  1216> cli|     Opening shared memory device with name: [SharedMemDev_{510a28aa-593a-402d-b082-76aa53f1b5c3}].
[31.01.2020 16:40:53] <  1216> cli|       Opening process handle for PID: [7752].
[31.01.2020 16:40:53] <  1216> cli|       Opening ring buffer: [SharedMemDev_{510a28aa-593a-402d-b082-76aa53f1b5c3}_ForwardBuf_SharedMem].
[31.01.2020 16:40:53] <  1216> cli|       Opening ring buffer: [SharedMemDev_{510a28aa-593a-402d-b082-76aa53f1b5c3}_BackwardBuf_SharedMem].
[31.01.2020 16:40:53] <  1216> cli|     Opening shared memory device with name: [SharedMemDev_{510a28aa-593a-402d-b082-76aa53f1b5c3}]. ok.
[31.01.2020 16:40:53] <  1216> cli|   Shared memory connection has been successfully established.
[31.01.2020 16:40:53] <  1216> cli|   Login ticket: {edb7775a-6783-4456-b09a-b66aad58447a}
[31.01.2020 16:40:53] <  1216> cli|   Current component version: [9.5.4.2866]. Server version: [9.5.4.2866].
[31.01.2020 16:40:53] <  1216> cli|   Server declared full support of current client version.
[31.01.2020 16:40:53] <  1216> cli|   Negotiating transport pool id.
[31.01.2020 16:40:53] <  1216> cli|   Additional transport connections will be assigned to pool '1'.
[31.01.2020 16:40:53] <  1216> net|   Initiating AUX data channel. Client id: '{3f189db0-b1c7-430e-b21e-b7e6c4c5dcea}'.
[31.01.2020 16:40:53] <  1216> cli|   Trying to connect to the endpoint [ESXi:2500]
[31.01.2020 16:40:53] <  1216> cli|   Connection status: system:0 ( The operation completed successfully ).
[31.01.2020 16:40:53] <  1216> net|   Sending reconnect options: [enabled: timeout 1800000, interval 15000].
[31.01.2020 16:40:53] < 11100> cli| Thread started. Thread id: 11100, parent id: 1216, role: (async) reconn. receiver {8f544bb7-a8f2-4e8c-9349-8bcb6a82f089}
[31.01.2020 16:40:53] < 11100> alg| Receiver stage: running recv cycle.
[31.01.2020 16:40:53] <  1216> cli|   Trying to connect to the endpoint [172.16.100.7:2500]
[31.01.2020 16:40:53] < 11204> cli| Thread started. Thread id: 11204, parent id: 1216, role: (async) reconn. sender {8f544bb7-a8f2-4e8c-9349-8bcb6a82f089}
[31.01.2020 16:40:53] <  8052> cli| Thread started. Thread id: 8052, parent id: 1216, role: (async) AUX channel receiver
[31.01.2020 16:40:53] < 11204> alg| Sender stage: running send cycle. Resend list: [0].
[31.01.2020 16:40:53] <  1216> cli|   Connection status: system:0 ( The operation completed successfully ).
[31.01.2020 16:40:53] <  1216> net|   Sending reconnect options: [enabled: timeout 1800000, interval 15000].
[31.01.2020 16:40:53] < 10500> cli| Thread started. Thread id: 10500, parent id: 1216, role: (async) reconn. receiver {129baf8d-acce-405e-8f7e-d8c5bb88b2c3}
[31.01.2020 16:40:53] < 10500> alg| Receiver stage: running recv cycle.
[31.01.2020 16:40:53] < 10516> cli| Thread started. Thread id: 10516, parent id: 1216, role: (async) reconn. sender {129baf8d-acce-405e-8f7e-d8c5bb88b2c3}
[31.01.2020 16:40:53] <  1216> cli|   All connections were established, sending acknowledge.
[31.01.2020 16:40:53] < 10516> alg| Sender stage: running send cycle. Resend list: [0].
[31.01.2020 16:40:53] <  1216> cli| Connection established ( server IP: 'ESXi:2500').
[31.01.2020 16:40:53] < 10528> cli| Thread started. Thread id: 10528, parent id: 1216, role: (async) AUX channel sender
[31.01.2020 16:40:53] <  1216> cli| 
[31.01.2020 16:40:53] <  1216> cli| _______________________________________________________________________________
[31.01.2020 16:40:53] <  1216> cli| Waiting for the next command.
[31.01.2020 16:40:53] <  8052> cli| Remote time: 31.01.2020 16:40:53
[31.01.2020 16:40:58] <  1216> cli| Next client command: [file2text].
[31.01.2020 16:40:58] <  1216> cli|       :>  nfc://conn:ESXi,nfchost:ha-host,stg:55d47399-41c47745-a41e-44a842259797@HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-172.16.100.14.vmx
[31.01.2020 16:40:58] <  1216> cli|       :>  2097152
[31.01.2020 16:40:58] <  1216> cli| Getting content of the file. File path: [nfc://conn:EXi,nfchost:ha-host,stg:55d47399-41c47745-a41e-44a842259797@HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-ESXi.vmx].
[31.01.2020 16:40:58] <  1216> cli|   Copying file locally. Source: [nfc://conn:ESXi,nfchost:ha-host,stg:55d47399-41c47745-a41e-44a842259797@HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-172.16.100.14.vmx]. Target: [MemFs://GetRemoteFileText_{4c34934d-2fdb-41b0-8164-39c06a2d94dc}].
[31.01.2020 16:40:58] <  1216> fs |     Creating NFC download stream. NFC path: [nfc://conn:ESXi,nfchost:ha-host,stg:55d47399-41c47745-a41e-44a842259797@HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-172.16.100.14.vmx].
[31.01.2020 16:40:58] <  1216> vim|       Initializing VI SOAP connection...
[31.01.2020 16:40:58] <  1216> vim|         Specification of VI connection
[31.01.2020 16:40:58] <  1216> vim|         {
[31.01.2020 16:40:58] <  1216> vim|           Connection ID: [ESXi].
[31.01.2020 16:40:58] <  1216> vim|           Host: [ESXi].
[31.01.2020 16:40:58] <  1216> vim|           Port: [443].
[31.01.2020 16:40:58] <  1216> vim|           Login: [root].
[31.01.2020 16:40:58] <  1216> vim|         }
[31.01.2020 16:40:58] <  1216> vim|         [SOAP] Successfully logged in ( server: [ESXi], user: [root], sessionKey: [52fbcd03-772d-fdaa-468d-056732fd8058] )
[31.01.2020 16:40:58] <  1216> vim|       VI SOAP connection initialized.
[31.01.2020 16:40:58] <  1216> fs |       Native NFC file path: [[Local Storage] HMS-VLT&RPT-vmback/HMS-VLT&RPT-172.16.100.14.vmx].
[31.01.2020 16:40:58] <  1216> nfc|       Reconnecting to the NFC storage. Storage: [stg:55d47399-41c47745-a41e-44a842259797,nfchost:ha-host,conn:10.0.0.6]. Display name: [Local Storage].
[31.01.2020 16:40:58] <  1216> nfc|         Preferred NFC server: [ha-host].
[31.01.2020 16:40:58] <  1216> nfc|         Connecting to NFC session. Target host: [ESXi]. Storage: [Local Storage]. VI SOAP connection ID: [10.0.0.6].
[31.01.2020 16:40:58] <  1216> nfc|           NFC service: [nfc]. Port: [902].
[31.01.2020 16:40:58] <  1216> nfc|           Opening NFC session with the specified ticket [52 ca 12 92 6d fe 94 19-09 d7 03 7d 10 df de ca]...
[31.01.2020 16:40:58] <  1216> nfc|             Establishing connection with the host [ESXi]. Port: [902].
[31.01.2020 16:40:58] <  1216> nfc|               Resolving host name (ESXi) to IP address...
[31.01.2020 16:40:58] <  1216> nfc|               Host's IP addresses (ESXi6):
[31.01.2020 16:40:58] <  1216> nfc|               {
[31.01.2020 16:40:58] <  1216> nfc|                 ESXi
[31.01.2020 16:40:58] <  1216> nfc|               }
[31.01.2020 16:40:58] <  1216> nfc|               Trying to connect to [ESXi]...
[31.01.2020 16:40:58] <  1216> nfc|               Succeeded to connect to the remote host. IP: [ESXi]. Port: [902].
[31.01.2020 16:40:58] <  1216> nfc|             Connection with the host [ESXi] was established.
[31.01.2020 16:40:58] <  1216> nfc|             Waiting for the authd reply message...
[31.01.2020 16:40:58] <  1216> nfc|               220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported, NFCSSL supported/t
[31.01.2020 16:40:58] <  1216> nfc|             Authd version: [1.10]
[31.01.2020 16:40:58] <  1216> nfc|             SSL connection is required to perform authentication.
[31.01.2020 16:40:58] <  1216> nfc|             Initializing the SSL subsystem...
[31.01.2020 16:40:58] <  1216> nfc|             The SSL subsystem was successfully initialized.
[31.01.2020 16:40:58] <  1216> nfc|             Initializing new SSL connection...
[31.01.2020 16:40:58] <  1216> nfc|               Connection with the SSL server was established.
[31.01.2020 16:40:58] <  1216> nfc|               Number of bits used to crypt SSL traffic: [256].
[31.01.2020 16:40:58] <  1216> nfc|               Protocol used to crypt SSL traffic: [DHE-RSA-AES256-GCM-SHA384].
[31.01.2020 16:40:58] <  1216> nfc|             Sending authd message: [SESSION 52 ca 12 92 6d fe 94 19-09 d7 03 7d 10 df de ca].
[31.01.2020 16:40:58] <  1216> nfc|             Sending authd message: [PROXY nfc].
[31.01.2020 16:40:58] <  1216> nfc|             Waiting for the authd reply message...
[31.01.2020 16:40:59] <  1216> nfc|               200 Connect ha-nfc
[31.01.2020 16:40:59] <  1216> nfc|         NFC session was opened.
[31.01.2020 16:40:59] <  1216> nfc|       Connected to the ESX storage through specified ESX. ESX: [10.0.0.6].
[31.01.2020 16:40:59] <  1216> nfc|       Starting file download. File: [[Local Storage] HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-172.16.100.14.vmx].
[31.01.2020 16:40:59] <  1216> nfc|         Expected size [2902] of the file [[Local Storage] HMS-VLT&RPT-172.16.100.14/HMS-VLT&RPT-172.16.100.14.vmx].

wishr
Veeam Software
Posts: 1741
Liked: 195 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: NFC storage connection is unavailable.

Post by wishr »

Hi Veasna,

Welcome to Veeam Community Forums.

Please reach out to our technical support team directly as support engineers are not present on this forum and the forum itself cannot replace the technical support service. Please let us know your case ID once you get it.

Thanks

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 43 guests