Support and News Forum

Hello
I am playing aroud with Viptela edge and need to add bootstrap config. Normally its achievable by :
cloud-localds config.iso vedge.cfg and adding this to our Image during a boot as second disk similar like:
--disk path=config.iso,device=cdrom .

I have tried to add -disk file=config.iso, device=cdrom via custom qemu option under edit option of image inside a lab - but this option not working for me because image not started at all.
Do you have any ideas how to achieve it.

Any feedback is very appreciable.
Tom

no,
you can obtaing bootstrap from vManager and using cli command join vEdge in vmanager..
request platform software sdwan vedge_cloud activate chassis-number CSR-BDD3FF60-8146-E42A-84A1-F61A3346XXXX token ef29cc1285d0086be8c76d83febaXXXX
line above is for cedge, but same is for veadge as well


Read viptela documents..

Uldis

hi ,
I am using version 19.2.097 and seems for me as not working this option anymore.
It was good solution for images below 17.x.
I read this article https://codingpackets.com/blog/cisco-sd ... lab-part-2 and he is creating following virtual machine
virt-install \
--name vedge \
--os-type linux \
--os-variant ubuntu14.04 \
--cpu host \
--vcpus=2 \
--hvm \
--arch=x86_64 \
--ram 2048 \
--disk path=viptela-edge-19.1.0-genericx86-64.qcow2,size=16,device=disk,bus=ide,format=qcow2 \
--disk path=config.iso,device=cdrom \
--network=network:default,model=virtio \
--network=network:default,model=virtio \
--graphics none \
--import

My question is how to inject this config into vedge.qcow2 via custom setting or prepare custom image for each chasis No?
i have tried your solution but it worked with images 16.3 or 16.4.

Regards,
Tom

Hi Again
in addition for vedges not working such sommand
vedgeDC01# show hardware inventory

HW
DEV SERIAL
HW TYPE INDEX VERSION PART NUMBER NUMBER HW DESCRIPTION
--------------------------------------------------------------------
Chassis 0 1.0 vEdge-Cloud sim vEdge-Cloud
PIM 0 None ge-8 None Max 8 x 1GE VM ports

vedgeDC01# request platform software sdwan vedge_cloud activate chassis-number
-------------------^
syntax error: incomplete path
vedgeDC01#

Regards,
Tom

You must obtain bootstrap infor from vManager to complete this command !!

Return to the vEdge and apply the UUID and OTP token using the request vedge-cloud activate chassis <UUID> token <token> command. Use the values obtained in the previous step. Command will look similar as the one in the output below:
all these values will give you vManage node!

vEdge cloud nodes are different vs HW boxes sir..