3 - Enabling ASDM in GNS3

I've looked up a few how to articles online on how to bring up the Adaptive Security Device Management (ASDM) from a virtual environment. They all seemed either too complicated, or used a very different interface for GNS3. After a lot of trial and error, I found the simplest way to bring up the ASDM in a virtual lab environment.

To recap post 2, the ASAv has a successful bridge with the host laptop to allow a connection out to the internet. VMNet8 is configured to allow my host laptop to fit in the IP addressing. This will later allow, my web browser to access the ASAv. But first we have to make some configurations to allow http traffic range going to the ASAv. We'll also change the hostname in the process. Then we'll save.

http server enable

http 192.168.14.0 255.255.255.0 outside 

hostname asa-1

write

Once we've enabled an http connection, we can connect to the ASAv through a browser. Note, the IP address 192.168.14.130, is the assigned IP of the outside interface.

Type this into the browser: https://192.168.14.130

Click "Proceed to 192.168.14.130 (unsafe)" 

Proceed with the installation of the ASDM or Java Web Start install. Either way will allow the use of ASDM. The instructions that follow are pretty self explanatory. If any authentication requirements show, go ahead and click login. By default, there is no user name or password required.

Once the installation of the ASDM is finished, find the ASDM launcher and open it. I had to open Windows Start and search for ASDM to open the launcher. There will be a prompt requesting the Device IP Address / Name, make sure you have the outside interface's IP address listed as 192.168.14.130. Again, Username and Password will not be required. Click okay.

You will receive prompts, go ahead and confirm them. Finally you should have access to the ASDM. You can configure the ASAv through this graphical user face. I'll show some examples a few posts down. But first the rest of the lab environment must be created.