takla

Glad to know that you got them up as we. Thanks again to Kamui and Ariyarathna

Thanks bro, its working now

Thanks @Ariyarathna, I bumped on this whilst troubleshooting but didn't believe it would effect both 19.x and 20.x hence didn't work on it for too long. But this actually fixed the issue. Thanks!

I have the same issue, and I have exhausted all options. I have also tried with 19.2 or 20.3 same result vedge not coming up.

Thanks bro, I have now exhausted all options, but still no luck. I tried all kinds of windows servers both in DC and Standalone modes with Root Certificate servers, including Webserver template for controllers and synched time but now I am stuck with SERNTPRES and followed by VECRTREV. And upon running logs, looks like vBond is complaining that the serial file has mismatching serials, I have synched it from vManage to all controllers but still no joy. local7.debug: Oct 18 17:21:06 vedge ZEBRA[1180]: RTM_DELROUTE ipv6 unicast proto local7.debug: Oct 18 17:21:30 vedge VBOND[31111]: vbond_handshake_event_cb[6543]: %VDAEMON_DBG_MISC-1: Get CA RSA Public key local7.debug: Oct 18 17:21:30 vedge VBOND[31111]: vbond_proc_challenge_ack[4724]: %VDAEMON_DBG_MISC-1: No signed challenge sent by the Peer.. Sent OTP instead local7.debug: Oct 18 17:21:30 vedge VBOND[31111]: vdaemon_find_vedge_in_vedge_list[285]: %VDAEMON_DBG_MISC-1: Peer's device (10b1a004b80b4eb48b5efc13b93892d3) serial num mistmatch. In db - 8D67D384 local7.info: Oct 18 17:21:30 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:21:30 vbond-reject-vedge-connection severity-level:major host-name:"vBond" system-ip:1.1.1.3 uuid:"C5448751-A49C-CEEB-A865-D623CB6DA5B8" organization-name:"viptela sdwan" sp-organization-name:"viptela sdwan" reason:"ERR_SER_NUM_NT_PRESENT" local7.info: Oct 18 17:21:30 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:21:30 control-connection-auth-fail severity-level:major host-name:"vBond" system-ip:1.1.1.3 personality:vbond peer-type:vedge peer-system-ip::: local-system-ip:1.1.1.3 local-color:default reason:"ERR_SER_NUM_NT_PRESENT" local7.debug: Oct 18 17:21:59 vedge VBOND[31111]: vbond_handshake_event_cb[6543]: %VDAEMON_DBG_MISC-1: Get CA RSA Public key local7.debug: Oct 18 17:21:59 vedge VBOND[31111]: vbond_proc_challenge_ack[4724]: %VDAEMON_DBG_MISC-1: No signed challenge sent by the Peer.. Sent OTP instead local7.debug: Oct 18 17:21:59 vedge VBOND[31111]: vdaemon_find_vedge_in_vedge_list[285]: %VDAEMON_DBG_MISC-1: Peer's device (10b1a004b80b4eb48b5efc13b93892d3) serial num mistmatch. In db - 8D67D384 local7.info: Oct 18 17:21:59 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:21:59 vbond-reject-vedge-connection severity-level:major host-name:"vBond" system-ip:1.1.1.3 uuid:"C5448751-A49C-CEEB-A865-D623CB6DA5B8" organization-name:"viptela sdwan" sp-organization-name:"viptela sdwan" reason:"ERR_SER_NUM_NT_PRESENT" local7.info: Oct 18 17:21:59 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:21:59 control-connection-auth-fail severity-level:major host-name:"vBond" system-ip:1.1.1.3 personality:vbond peer-type:vedge peer-system-ip::: local-system-ip:1.1.1.3 local-color:default reason:"ERR_SER_NUM_NT_PRESENT" local7.debug: Oct 18 17:22:27 vedge VBOND[31111]: vbond_handshake_event_cb[6543]: %VDAEMON_DBG_MISC-1: Get CA RSA Public key local7.debug: Oct 18 17:22:27 vedge VBOND[31111]: vbond_proc_challenge_ack[4724]: %VDAEMON_DBG_MISC-1: No signed challenge sent by the Peer.. Sent OTP instead local7.debug: Oct 18 17:22:27 vedge VBOND[31111]: vdaemon_find_vedge_in_vedge_list[285]: %VDAEMON_DBG_MISC-1: Peer's device (10b1a004b80b4eb48b5efc13b93892d3) serial num mistmatch. In db - 8D67D384 local7.info: Oct 18 17:22:27 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:22:27 vbond-reject-vedge-connection severity-level:major host-name:"vBond" system-ip:1.1.1.3 uuid:"C5448751-A49C-CEEB-A865-D623CB6DA5B8" organization-name:"viptela sdwan" sp-organization-name:"viptela sdwan" reason:"ERR_SER_NUM_NT_PRESENT" local7.info: Oct 18 17:22:27 vedge VBOND[31111]: %Viptela-vBond-vbond_0-6-INFO-1400002: Notification: 10/18/2020 16:22:27 control-connection-auth-fail severity-level:major host-name:"vBond" system-ip:1.1.1.3 personality:vbond peer-type:vedge peer-system-ip::: local-system-ip:1.1.1.3 local-color:default reason:"ERR_SER_NUM_NT_PRESENT" local7.debug: Oct 18 17:22:44 vedge ZEBRA[1180]: RTM_NEWROUTE ipv6 unicast proto Has anyone else been able to get this to work apart from @kamui? I have recreated the labs from scratch multiple times and now I am really frustrated with it and fell like giving up.

Hi comtaq0, Thanks for the share but its a session from 2017. Thanks

Thanks Bro, Yes, I have followed all the steps correctly, used the same clocks and timezones, I was able to get the controllers onboarded successfuly and even the Edges show up on the vManage with a cert issued, but the control history shows that cert revoked. I have done this whole thing 4 times now and I am out of patience. The only thing that I suspect is different is the windows image I am using. Can you please point to the right direction as to where to get the windows server image from. I just googled one but I am not sure this one is working as it should. Thanks

Hi Kamui, Thanks for the fantastic share, I have everythingn working except that the vedge/cedges are not reachable [Hidden Content] [Hidden Content] I wonder if you had encountered a similar issue. In the control connections history, that the certificate has been revoked [Hidden Content] Any help would be apprecaited. Thanks

@sallywally thanks mate, not sad, it was mis click. Thanks for the great share

Hi digiter, The link you provided doesn't work, can you check please. Thanks

Not easily available. You will have to reachout to Cisco, if they approve your request, you might get it.

Count me in!

Yup, still not released, its available for pre-order only.

Pass: [Hidden Content]

Where is Page number 3 gone with all the comments? Is it just me or it is the case for all. Someone said they had the course and wanted to share but anonymously, where is that person gone. If you see this can you please share? Thanks