Support and News Forum

Posted: **Tue Mar 21, 2017 11:38 am**

Hi,

I run eve-ng on a bare metal box.

My ASAv 9.4.1 worked just fine in unetlab, but now on boot I get a loop, as shown below. I have no idea how to proceed.

Code: Select all

loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680

Posted: **Tue Mar 21, 2017 4:51 pm**

I solved my own issue with a bit more research. Following the guide in the "HowTo" I add some steps. This works for 9.5.2 and even 9.7.1 for the ASAv

EVE

Run following commands from eve terminal to enable telnet access instead of vnc:

Code: Select all

mkdir -p /opt/unetlab/addons/qemu/asav-9.7.1
mv asav971.qcow2 /opt/unetlab/addons/qemu/asav-9.7.1/virtioa.qcow2
cd /opt/unetlab/addons/qemu/asav-9.7.1/

To clarify, the below lets you see the virtual file structure of the ASAv

Code: Select all

apt-get update
apt-get install libguestfs-tools
guestfish -a virtioa.qcow2 
run
mount /dev/sda2 /
touch /use_ttyS0
umount /
exit

Clean and fix permissions:

Code: Select all

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

Then...

boot ASA using vnc.

Code: Select all

rename the g0/0 to management like this:
ciscoasa(config)# int g0/0
ciscoasa(config-if)# nameif Management0
ciscoasa(config)#wr mem
ciscoasa(config)# cd coredumpinfo
ciscoasa(config)# copy coredump.cfg disk0:/use_ttyS0  (that's  S zero not S and the letter O)
ciscoasa(config)# dir disk0:/

you will see the "use_ttyS0"

now, power down the ASA.
Change to telnet.
boot up with telnet!
BACKGROUND:
http://blog.scottlowe.org/2014/03/17/mo ... guestfish/
https://gns3.com/qa/how-to-configure-any-asav-qcow2-

Posted: **Tue Mar 21, 2017 4:59 pm**

The problem with your solution is you have to do this for "every" ASAv you deploy within your topology. The method in the "How to" section it to make this change permanent within the node image. But it's not working.

Posted: **Tue Mar 21, 2017 5:33 pm**

That's why I did it this way. If one way doesn't work, then you have to do it again. It only seems to work part time, however.

Support and News Forum

ASAv Boot Loop since upgrade

ASAv Boot Loop since upgrade

Re: ASAv Boot Loop since upgrade

Re: ASAv Boot Loop since upgrade

Re: ASAv Boot Loop since upgrade