Hmm, I suggest you take a look at these issues to see if you can troubleshoot the problem.
First of all, your command to create the root CA certificate seems to be a bit off in your post. I think it may have to do with the way you pasted it. However, you must make sure that it appears as in the lesson. Notice that Rene states that it is a “one-liner” which means you can copy and paste it as-is from the lesson. Notice that’s what he did in the video as well. It should be copied and pasted exactly like so:
After doing a bit of research I have found that even if the command is issued correctly, this type of error is also seen in other cases where root CA certificates are created, and it can be due to a bug. You can attempt to issue the command without a subject if you like since that is optional. This may resolve the problem.
The biz-internet and public-internet “clouds” in the diagram represent the WANs that businesses can use to connect their vEdge devices. This topology is created within EVE-NG, and the clouds are entities created by the emulator. Take a look at this lesson to see the process with which the clouds, and the rest of the topology, were created.
Take a look at the configuration of any and all tunnel interfaces on your vEdge device. The tunnel interfaces can be assigned “colors” which are used to distinguish between the WAN tunnels being created. It looks like you have more than one tunnel interface with the color “default” (which is the default color when no other color is assigned). This is not allowed since there will be no way to distinguish between them, unless the colors are different.
Do you have more than one VPN 0 on your vEdge device? The problem here is not specific to the vBond configuration but to the colors on the tunnel interfaces. For more information about configuring the color on tunnel interfaces take a look at the vEdge onboarding lesson, and specifically, at the VPN0 underlay network section that details how to configure colors:
I’m going to state the obvious . Are your username and password correct? I assume they are. But still, there seems to be an authentication issue. Can you give us some more info about where in the installation you are at? Is this the addition of the vBond controller? Let us know…
Yes, thank you for the response. I can’t get it to work still even after going through the steps multiple times. I am stuck at step 1.2.1 Start Up Configuration. I’ll go through and try it again.
All controllers are placed on VLAN 10 which is configured in the DC1 switch. This VLAN uses the 10.1.0.0/24 subnet. The 10.1.0.254 address is the default gateway for that subnet which is assigned to the VLAN 10 SVI of the switch. This is explained in the first video under the Configuration heading starting at Chapter 4 of the video at 4:41.
Your ping in 512 works, but I can’t tell in which VPN it tries to do request download scp. In my examples, I used VPN 0 on the controllers and vedges for onboarding.
The other option is that for some reason, SSH server is not running on vManage. That’s something you can check too.
Hi Rene,
After restarting to vEdge Router issue get resolved but if I’m restarting the vManage then all configuration getting erased and unable to export the config in EVE-NG.
Sometime i must have to stop the SD-WAN Lab when need to restart the Server but in that case, vManage getting erase and on boarding vedge,vBond etc getting empty in vManage in the EVE-NG Lab.
Please help in this case if have a shortcut solution or alternative solution.