08-09-2022 09:55 AM
Hi,
I have been doing several SD-WAN home labs with no issue but now I cannot get vBond/vSmart to connect to vManage. I was using version 19.2.3 with success but now in vManage when I click on Running Configuration for vBond/vSmart I see the following error:
[vmanagedb] no system ip found for uuid......
I decided to to try version 20.6.3 and still not able to get the device to connect? to vManage but the error message is different:
Device not found: cd709bbb-c324-4edb-9a14-4e0a3f9c5d30
I configured vBond/vSmart with no tunnel-interface and tried with tunnel-interface configured and allowed-services sshd / netconf but with both scenarios still not able to get devices to connect/join vManage. I am not sure why this no longer working but I was able to setup labs until last week. Could it be virus protection app that is blocking something?
Solved! Go to Solution.
08-09-2022 11:31 PM
use google translate
version 20.6.1
If the vBon address is specified as an IP address,
Try changing to a method that uses host.
This worked for me.
However, although it is a change in the specification method of vBond,
Is it okay to change only vManage settings?
Is it okay to change only vBond settings?
Do I need to change both settings?
Unknown.
In my case I changed both vBond and vManage.
remarks
Also, it was before vSmart was built, so there is no vSmart.
I left the vBond column of Administration Settings blank in the Web GUI of vManage.
For reference below.
Example) vBond name "vbond.local"
Excerpt of vBond configuration below
====vBond old config====
system
host-name vBond
system-ip 192.168.0.30
site-id 10
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
organization-name test.local
vbond 192.168.0.30 local vbond-only
aaa
===omit===
vpn 0
interface ge0/0
ip address 192.168.100.30/24
====vBond old config====
====vBond new config====
system
host-name vBond
system-ip 192.168.0.30
site-id 10
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
organization-name test.local
vbond vbond.local local vbond-only <==change point
aaa
===omit===
vpn 0
host vbond.local ip 192.168.100.30 <==change point
interface ge0/0
ip address 192.168.100.30/24
===omit===
====vBond new config====
Excerpt of vManage settings below
====vManage old config====
host-name vManage
system-ip 192.168.0.10
site-id 10
admin-tech-on-failure
no vrrp-advt-with-phymac
organization-name test.local
vbond 192.168.0.30
===omit===
vpn 0
interface eth0
ip address 192.168.100.10/24
===omit===
====vManage old config====
====vManage new config====
host-name vManage
system-ip 192.168.0.10
site-id 10
admin-tech-on-failure
no vrrp-advt-with-phymac
organization-name test.local
vbond vbond.local <==change point
===omit===
vpn 0
host vbond.local ip 192.168.100.30 <==change point
interface eth0
ip address 192.168.100.10/24
===omit===
====vManage new config====
08-09-2022 11:31 PM
use google translate
version 20.6.1
If the vBon address is specified as an IP address,
Try changing to a method that uses host.
This worked for me.
However, although it is a change in the specification method of vBond,
Is it okay to change only vManage settings?
Is it okay to change only vBond settings?
Do I need to change both settings?
Unknown.
In my case I changed both vBond and vManage.
remarks
Also, it was before vSmart was built, so there is no vSmart.
I left the vBond column of Administration Settings blank in the Web GUI of vManage.
For reference below.
Example) vBond name "vbond.local"
Excerpt of vBond configuration below
====vBond old config====
system
host-name vBond
system-ip 192.168.0.30
site-id 10
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
organization-name test.local
vbond 192.168.0.30 local vbond-only
aaa
===omit===
vpn 0
interface ge0/0
ip address 192.168.100.30/24
====vBond old config====
====vBond new config====
system
host-name vBond
system-ip 192.168.0.30
site-id 10
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
organization-name test.local
vbond vbond.local local vbond-only <==change point
aaa
===omit===
vpn 0
host vbond.local ip 192.168.100.30 <==change point
interface ge0/0
ip address 192.168.100.30/24
===omit===
====vBond new config====
Excerpt of vManage settings below
====vManage old config====
host-name vManage
system-ip 192.168.0.10
site-id 10
admin-tech-on-failure
no vrrp-advt-with-phymac
organization-name test.local
vbond 192.168.0.30
===omit===
vpn 0
interface eth0
ip address 192.168.100.10/24
===omit===
====vManage old config====
====vManage new config====
host-name vManage
system-ip 192.168.0.10
site-id 10
admin-tech-on-failure
no vrrp-advt-with-phymac
organization-name test.local
vbond vbond.local <==change point
===omit===
vpn 0
host vbond.local ip 192.168.100.30 <==change point
interface eth0
ip address 192.168.100.10/24
===omit===
====vManage new config====
08-10-2022 10:47 AM
So I got the connections established between vbond/vsmart with vmanage but still seems not working properly.
I do not see any omp peers on vbond and vsmart. There was one control up on v20.6.3 but none on v19.2.3. vbond shows no bfd sessions either. On vManage CLI the connections status are all UP so not sure why none is showing up in the vManage GUI in v19.2.3.
Any ideas? I am missing some other 'new' configurations?
08-10-2022 08:51 AM
mgoto,
Thank you very much for the response. The new configuration actually works on version 20.6.3 for me. Do you know if this new config style is for version 20.6.x and later? I was using version 19.2.3 with no issues until about a week or two ago. Also, do I need to do the same for vsmart? I will test that and see. I will also try to see if I can do the same on 19.2.3 version.
p.s. - forgot to mention I running my labs in simulated environments (eve-ng and gns3)
THANKS AGAIN!!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide