VMware Cloud Community
jcorreia
Contributor
Contributor
Jump to solution

VCB cannot connect to VirtualCenter

Environment consists of:

Virtual Infrastructure Server, Version 2.0.1 build 32042

VMware ESX Server, Version 3.0.1 build 35804

Installed VCB 1.0.2 base and receiving the following error when I try to run this vcbmounter command:

vcbmounter -h wa-vcenter.rn.wilde.com -u rn\bkupservice -p password -a ipaddr:powerconvert.rn.wilde.com -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6

Here is the error output:

Initializing SSL context

Using system libcrypto, version 90703F

Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 1200000

00

Connecting to host wa-vcenter.rn.wilde.com on port 902

Error: Other error encountered: Cannot connect to host wa-vce

nter.rn.wilde.com: No connection could be made because the target machine actively refused it

I can log into the VC client using my account rn\bkupservice and password just fine but can't seem to track down where or why Virtual Center is refusing my connection vcbMounter.

Reply
0 Kudos
25 Replies
jcorreia
Contributor
Contributor
Jump to solution

Thanks for your help on this. At least it's running now and with some patching and updating to do on both VC and the ESX hosts maybe both the port and performance issues will get resolved.

thanks!

Reply
0 Kudos
serracon_suppor
Enthusiast
Enthusiast
Jump to solution

your are welcome Smiley Wink

Reply
0 Kudos
jcorreia
Contributor
Contributor
Jump to solution

Okay so it took a while to complete the fullVM snapshot and it did complete successfully. However now when I go to unmount the snapshot to remove it from the proxy I get the following error:

C:\>vcbmounter -h wa-vcenter.rn.wilde.com:905 -u rn\bkupservice -p veritas -U y:\mnt\sulu2.rn.wilde.com-fullVM

-L 6

Current working directory: C:\

Initializing SSL context

Using system libcrypto, version 90703F

Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 1200000

00

Connecting to host wa-vcenter.rn.wilde.com on port 905

Connected to stream: [class Vmacore::Ssl::SSLStreamImpl:018

83958]

Unsetting unknown path: /vmomi/

Authenticating user rn\bkupservice

Logged in!

Performing automatic unmount

Error: Could not read unmount information

Got vmdb error -14 (Pipe connection has been broken) when invoking

on

Error on logout (ignored): vmodl.fault.HostNotReachable

Shutting down VMDB service...

Unregistering callback...

...done

C:\>

Seems like this running on port 905 is going to be a little more bothersome.

Any ideas on why I can't unmount?

Reply
0 Kudos
serracon_suppor
Enthusiast
Enthusiast
Jump to solution

this seems strange to me. i try guessing a bit

but i noticed in yout posting you refered the path to be y:\mnt\powerconvert-fullVM on the mounts. The dismount one is some other.....

an other option is that the VC service was restarted in the mean time oder someone als has dismounted the vcb-snapshot...

have never seen such a problem in quiet some installation

Reply
0 Kudos
s90099a
Contributor
Contributor
Jump to solution

Got a question related to this subject.

What about if i "netstat -a" in my VirtualCenter and the results come out do NOT have TCP 902 Port LISTENING? What am i suppose to do? How i can actually open/enable the TCP 902 Port in my VirtualCenter?

I actually also having problem with VCB cannot connect to VirtualCenter. Below is the error message:

"Cannot connect to host VirtualCenterIP: No connection could be made because the target machine actively refused it"

I suspect it is due to TCP 902 Port is not listening. Can anyone help?

Thanks in advance.

Reply
0 Kudos
Davidkov
Contributor
Contributor
Jump to solution

Hi,

As far as I see from you post the 902 is open and this is the port you need to use.

You have to be aware that this is a UDP port and not TCP! You can change it from your VirtualCenter by clicking on:

"Administration" > "VirtualCenter Management Server Configuration" > "Runtime Settings" > "Port" by default 902

Regards,

Ivan

Reply
0 Kudos