Then reboot the ASAv and you should be able to manage ASAv via GNS3 console afterwards. When ASAv boots up, copy the file coredump.cfg to a disk0 in a privileged exec mode (password is not set).
Therefore we need to redirect vASA output to a serial port. However we want to use GNS3 console instead of Qemu console. Once we start ASAv, the Qemu window is launched.
Note: Here is the configuration file of vASA-I. Similarly, the second connected interface eth2 is referred as the GigabitEthernet0/1 and so on. The first connected interface is then the interface eth1 that is referred as the interface GigabitEthernet0/0 in ASAv CLI. The interface eth0 is not connected as we use the inside interfaces for management instead. Note: The interface eth0 on the ASAv-I is referred as the interface Management0/0 in ASAv configuration. In order to lower memory consumption, GNS3 is configured to assign 1536 MB to the ASAv. Note: The recommended RAM size for ASAv instance is 2048 MB. Picture 1 - ASAv-I, Campus, DC and Edge Connection It also connects the campus network and DC to the vIOS-EDGE-I edge router. The ASAv-I provides traffic filtering and inspection services for the campus network and Data Center (DC).
The device is a Cisco Adaptive Security Virtual Appliance (ASAv) version 9.6(1) installed on qcow2 Qemu disk. The article explains configuration of the device ASAv-I. This is the fourth from the series of the articles that discuss configuration of the enterprise network.