5/5/2023 0 Comments Tinycal not syncing![]() I’ll work with Brian and the team to see which broken items we can fix right away, and which ones we may need more time and will go on the roadmap.I’ll work to include these limitations in the docs (hopefully will be less after Brian’s efforts in the next couple of weeks).I’m going to take a couple of action items, and you can also see that our lead engineer for connectors ( ) is also on top of these issues. The process to activate virtual cEdge is very similar with the small deviation in the tunnel-interface configuration and device activation.I sincerely apologize for your time spent debugging this and your frustrations. It is purely optional as you can copy paste directly from vManage portal.ĥ) Verify the status by issuing " show control connection" or troubleshoot by " show control connections-history" and " show control local-properties" Not to mess up with the chassis number and token I saved bootstrap file to the file system and then simply copy pasted relevant information. Use " show orchestrator valid-vedge" command on the vbond to validate the list of devices.Ĥ) Activate the virtual vedge by issuing command " request vedge-cloud activate chassis-number YOUR_CHASSIS_ID token YOUR_TOKEN". Validate IP connectivity with controllers if that is possible.ģ) Generate bootstrap file and make sure you sent this to controllers from vmanage. Put information like system ip, site id, vbond ip/hostname, and vpn 0 relevant configuration to have ip connectivity. Here is workflow I followed after several trials and that worked pretty well for me:ġ) Add basic (tiny) configuration to the vedge. Then I didn't push this information to controllers. My issue was related to the fact that I didn't marked device as valid after generating the bootstrap file. I am confident that on the version 19.2.31 chassis ID is case insensitive. At least the symptoms where very similar.ĭuring different tests I was able to register all cloud vedges. I am not sure if this is expected or not. The vManage shows vBond as reachable however I noticed the " Control" is empty for vBond furthermore show control connection on vBond shows no connections. Looking at the output of the command below, it seems that vBond doesn't have a valid list of vSmart and vManage. I have re-imported vEdge list into vManage deleted and re-import CA cert into vEdge and tired to register again with the request control vedge-cloud command. The good thing is the connectivity works but I am yet to find out what is causing the DTLS issue. Secondly I did the Wireshark capture and I can see DTLS is failing. Is there a debug that can show me what is failing? I issued all sorts of debug commands and none helped me debug the connection between vEdge and vBond. ![]() I noticed the time is way off on the vEdge compared to controllers. I also issued this command on vEdge to activate it with no luck: Considering it can ping all the controllers via vpn0 or vpn512 from and it has the root cert as well (even tho I believe this can be pushed from controllers). I uploaded the viptela file onto vManage and the list was pushed successfully to all controllers.Īt this point I would expect for vEdge to finally be permited to join the overlay network. ![]()
0 Comments
Leave a Reply. |