Add vBond to vMange

[Juraj Papic]

Hi all

Im working with viptela version 18.4.1 every time I try to add the vBbond to the vMange I get this error

java.net.SocketTimeoutException: connect timed out

Thanks. 

[Jason Xie]

I have the same issue too when adding the vBond to the vManager. Have this issue been resolved?  I have tried the solutions proposed but still not good. 

Thanks,

Jason 

[Jason Xie]

The issue has been resolved by installing the correct version of the vBond.

Thanks all for your help!

Jason

[Mahmoud Elsoury]

Hello, 

I know this is an old topic, but I just wanted to share how I solved mine.

I'm running version 20.6.3 and had the same error.

Problem solved after adding the "local" keyword to the vbond command on vbond itself.

i.e. when I had the problem I had: 

vbond 10.10.1.106

the correct one which solved the problem:

vbond 10.10.1.106 local

I hope that helps anyone.

[ibnoesany28]

Hii,

reconfigure vbond vpn 0 and set "no tunnel-interface"

ex:

vpn 0
interface ge0/0
ip address x.x.x.x/x
no tunnel-interface
no shutdown
!
!

[OloratoDITIRO0365]

This worked for me too, quiet helpful.

[mehdizrq]

It worked for me

[rward2801]

Does not work for me

Cisco vBond error Failed to add device java.io.IOException: Unable to connect to admin@1.1.1.3:830

[rward2801]

vManage

vpn 0
dns 8.8.8.8 primary
interface eth1
ip address 1.1.1.1/24
no shutdown

vBond

vpn 0
interface ge0/0
ip address 1.1.1.3/24
ipv6 dhcp-client
no shutdown

[MichielVercoutter]

Hi,

I had the same issue and my solution was to enable the tunnel interface on the vbond and allow all services:

config
vpn 0
interface ge0/0
tunnel-interface
encapsulation ipsec
allow-service all
commit and-quit

[Jelle Le]

This also helped for my deployment.

vBond# show version
20.9.4

conf t
 vpn 0
  interface ge0/0
    tunnel-interface
      encapsulation ipsec
      allow-service all
      commit and-quit

edit: I don't think you actually need to specify the "allow-service all". Just adding "tunnel-interface" and "encapsulation ipsec" should do the trick.

[jean-burgosdeleon]

Thank you, this was absolutely my issue. I didn't have to add the tunnel interface on VPN 0 for vSmart, but had to absolutely do it for vBond. After hours of troubleshooting. 

vpn 0
interface ge0/0
ip address 10.1.1.2/24
tunnel-interface
encapsulation ipsec
allow-service all
no allow-service bgp
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service ospf
no allow-service stun
allow-service https
!
no shutdown

[dawodi55]

I had the same issue and my solution was to disable the tunnel interface on the vbond.

version 19.2.31.