{Working} How to add or install ASA 8.4 on Gns3 1.1 windows 8.1

This article is related to installation and configuration of ASA on Gns3 1.1 and also include some tips for older versions of Gns3.

How to configure / use Cisco ASA on Gns3 1.1:

You can add ASA in Gns3 1.1 by following steps:

  • Open Edit \ Preferences \ Qemu \Qemu VMs

  • Click on New button
  • this will start a wizard for ASA, Type it’s name and select it’s type ASA and click next

  • Set a suitable memory for ASA

  • Now browse the initrd.gz & kernel files for ASA and click finish.

  • Now you may need for flash, yo can create it easily. Open the “C:\Program Files\GNS3\qemu” directory by cmd (command prompt) using command cd C:\Program Files\GNS3\qemu. For flash type the command “qemu-img create FLASH 512M” and press enter.

  • this will create a file flash in this directory.

  • now again go to Edit \ Preferences \ Qemu \Qemu VMs & edit the ASA.

  • In HDD tab define the path for flash.




In Advanced Settings, on kernel command line replace with following code:
-append ide_generic.probe_mask=0x01 ide_core.chs=0.0:980,16,32 auto nousb console=ttyS0,9600 bigphysarea=65536 ide1=noprobe no-hlt -net nic
On options: Replace the content with -vnc none -vga none -m 1024 -icount auto -hdachs 980,16,32



Click on apply.

note: It will take some time for first boot

------------------------------------------------------------------------------------

Emulate ASA in older versions of  gns3:

Please carefully follow these step to configure ASA in older gns3 on windows 7 or XP.
  • Download ASA IOS
  • Configure ASA in gns3 
  • Start the ASA
  • Open the console 
 Step-1 Download ASA IOS and how to solved ASA console hangs Problem: 


First you need two file for ASA one is ".kernel" and other is ".initrd.gz". In my case these are "asa802-k8.kernel" and asa802-k8.initrd.gz. You can download these files from following link:

Download ASA IOS for GNS3

Add ASA in gns3:

Now run the gns3 open the Preferences from edit/preferences, and in qemu/ASA tab define the name for ASA and these two file i.e. "asa802-k8.kernel" and "asa802-k8.initrd.gz" in respective fileld.




Start the ASA:

 Start the ASA and a qemu console window is open don't close this window.
 
Open the console:
Now open the ASA console by rigth clicking on it and after some time you received a message that  copy these two commands and press enter, do this.
and then you received the welcome message of ASA.
 




Learn about OSPFCloud Computing and Active Directory

66 comments:

  1. Which password this pix and asa asking for ?

    ReplyDelete
  2. asking for enable password which is none, just press the enter key..

    ReplyDelete
  3. its working fine thanks

    ReplyDelete
  4. Dude,
    Thanks you so much for this, I`ve been trying to get this working for a bout 6 days, and after your advice, its working, may the force be with you dude, respect !!!!!!!!

    ReplyDelete
  5. Hey guys, I am still having problems. You said that you would explain why the console just hangs but never did. I am going nuts trying to just get started. Can someone please help me? What I am going to do is attempt to download a new image and kernel from the site that is suggested on this page but I downloaded mine originally from here Hey guys, I am still having problems. You said that you would explain why the console just hangs but never did. I am going nuts trying to just get started. Can someone please help me? What I am going to do is attempt to download a new image and kernel from the site that is suggested on this page but I downloaded mine originally from here...http://cozzi.co.uk/?page_id=6...they appear official and I did not unpack them or anything like that. Please help!!

    ReplyDelete
  6. download kerner and initrd
    http://www.4shared.com/file/KhbzGgrF/ASA_IOS.htm

    don't extract asa802-k8.initrd.gz it appear as rar file, if you extract this file and configure ASA with this file you should face console problem.

    make sure your files extensions should be .gz and .kernel when you define these in preferences tab.

    ReplyDelete
    Replies
    1. thank you very much for this explenation............

      Delete
  7. Mekky
    thank you very much for this support it work fine with me

    ReplyDelete
  8. HOW TO SAVE RUN-CONFIG IN ASA.WHEN I AM TRYING TO WRITE RECEIVED FOLLOWING ERROR:

    %Error copying system:/running-config (Not enough space on device)
    Error executing command
    [FAILED]

    ReplyDelete
  9. Even iam facing same issue, can someone tell me why this error is occuring.

    Thanks,
    Mohan

    ReplyDelete
    Replies
    1. when i write these commands to solve flash memory issue i got this msg plz help

      ciscoasa# copy running-config disk0:/.private/running-config

      Source filename [running-config]?

      Destination filename [/.private/running-config]?
      Cryptochecksum: 512f5652 61106c9d ffde486e 44abc040

      %Error copying system:/running-config (Not enough space on device)

      Delete
  10. first run erase flash command to free up disk space on your ASA. then try these commands.

    ciscoasa# copy running-config disk0:/.private/running-config


    ciscoasa# copy disk0:/.private/running-config disk0:/.private/startup-config


    ciscoasa# configure terminal

    ciscoasa(config)# boot config disk0:/.private/startup-config

    ReplyDelete
  11. I am at the Putty window. Noithing ever happens. Do I need to start loop back manager? Do I need to press enter? When I do all I get is # sign.

    ReplyDelete
  12. sorry false alarm i downloaded from http://www.4shared.com/file/KhbzGgrF/ASA_IOS.htm

    ReplyDelete
  13. Hi all
    I did exactly as described on this site but when I console my ASA console pops up for 1 second and closes again.
    Please advice what im doing wrong I did not extract asa802-k8.initrd.gz

    ReplyDelete
  14. is there Qemu(ASA) console is open when u start the ASA???(as shown above)

    ReplyDelete
  15. I am so greatful,now that my ASA is working perfectly.thx so much guys......by the way how do i managed to get the juniper router working in gns3.............Thx a lot fom KULY in GHANA

    ReplyDelete
  16. Thnx so much...its working.:)

    ReplyDelete
  17. Thank you so much, finally it is working now!!!!!

    ReplyDelete
  18. Thanks a lot ..it works.

    ReplyDelete
  19. your the best.it has worked in xp,vista and 7.took me ages trying to get a solution. your the man.

    ReplyDelete
  20. I downloaded these two files,but when I add these files to qemu,I get this message:"identifier,initrd and kernel must be set.what's the problem?

    ReplyDelete
  21. thanks WAQAS.the config works perfectly fine

    ReplyDelete
  22. I have a problem i installed and configure asa on gns3 and asa starts but when I open console show this lines::<0>Kernel panic - not syncing: bad gzip magic numbers

    How do I solve this?

    Thanks in advance

    ReplyDelete
  23. crypto commands not working

    ReplyDelete
  24. hi
    i am unable to open the console as in last step
    console open
    but nothing appear next

    ReplyDelete
  25. Hi, my putty window is blank when i console to the ASA

    ReplyDelete
  26. I tryed to follow this guide but I can't ping either the asa from the pc and viceversa.
    I get this:
    ciscoasa# ping 192.168.50.2
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.50.2, timeout is 2 seconds:
    ?????
    Anyone has the same problem? :s

    ReplyDelete
  27. Kernal is booting but I am unable to take console .Console Screen appear but not Loading.. Please Help......

    ReplyDelete
  28. Thanks a lot...

    ReplyDelete
  29. The author is good at removing posts but unable to answer simple question above, why then blogging?

    ReplyDelete
  30. Hi, I got the same problem. Stay stopped in Booting the Kernel...

    How can I fix it?

    ReplyDelete
  31. i cannot see the picture. is there anything i can do?

    ReplyDelete
  32. It works like a charm. After first boot use command
    /asa/bin/lina_monitor

    For those who are not getting any response when console is launched or empty putty screen, check system requirement for running GNS. Minimum of 4GB RAM is must. If you have less RAM you can keep stop and start ASA and try launching console, sometime it might work or sometime it wont.

    Cheers,
    JNK

    ReplyDelete
    Replies
    1. Thanks Mr. JNK for this advice but its possible if one has less Physical RAM just need to decrease ASA's RAM and its works fine, extremely happy for your answer.

      Thanks
      San

      Delete
  33. Iam also facing problem with asa. My putty stop working after sometime and i cannot enter any command. Just fedup of trying different things. Plz help

    ReplyDelete
  34. Just configured and taken console. looks good. need to configure the box.

    ReplyDelete
  35. Can we configure Site to Site VPN with this image

    ReplyDelete
  36. What could be the resolution for this issue:

    ASA1: error from server 127.0.0.1:10525: 209-unable to start instance 'ASA1'

    ReplyDelete
    Replies
    1. Hello Devavrat, I have the same problem here, you found the solution? Tks

      Delete
  37. Thank you JNK,

    After enter /asa/bin/lina_monitor command it's start to booting.

    ReplyDelete
  38. I have the same problem above:
    error from server 127.0.0.1:10525: 209-unable to start instance
    how I can solve it? Thank you!
    BR

    ReplyDelete
  39. This comment has been removed by the author.

    ReplyDelete
  40. i have already done all the steps except when i click on console putty stop with black screen and nothing comes after that,,
    here is the error message "127.0.0.1:3001 Network error : Connection refused! inactive Restart in 5sec"
    so guys please any tip for this

    thanks

    Thanks in advance

    ReplyDelete
    Replies
    1. Hi, Did you resolve this.... If so Please share.

      Delete
  41. all I have is a .bin file for my asa 8.4 code. Where do you get the file that extracts into .gz and .kernel. I can't find anything via google.

    ReplyDelete
  42. HI,
    Can anyone help me with the activate console problem in GNS for ASA.

    ReplyDelete
  43. Jagdeep

    Hii everone. Can u guys help me for the error comes always when i start to ASA Firewall- ASA1:error from server 127.0.0.1:10525:209-unable to start instance 'ASA1'...Please suggest me what can i do now.

    ReplyDelete
  44. Guys Guys Guys...... if anyone got issues starting the ASA might this would be helpful..

    Drag ASA into GNS3 Workbench...Obviously you already done the configuration under QEMU...

    When you start ASA... it says... QEMU (ASA) ...Uncompressing the linux..ok... booting kernel...

    Now.....

    open console and you will find only # (Nothing is there) dont panic..

    Type the following:

    # cd /
    # cd /asa/scripts
    # ./first_start.sh

    Firewall Started...

    Now do this..

    ciscoasa# copy running-config disk0:/.private/running-config


    ciscoasa# copy disk0:/.private/running-config disk0:/.private/startup-config


    ciscoasa# configure terminal

    ciscoasa(config)# boot config disk0:/.private/startup-config

    ReplyDelete
    Replies
    1. All the above commands are working but it asking foe password
      >en
      Password:
      what is the default password

      Delete
    2. hi

      Thanks for the advice.

      you saved a lot of time bro.

      thanks

      Delete
    3. Thank you. Worked perfectly.

      Delete
  45. thanks for sharing
    any lab scenario for test please ?

    ReplyDelete
  46. Thanks for sharing.
    any lab scenario for test please

    ReplyDelete
  47. Thanks you so much. Finally it worked.

    ReplyDelete
  48. thannnnnnnnnnnnnnnk youuuuuuuuuu

    ReplyDelete
  49. it's worked well in windows 8 too.

    ReplyDelete
  50. Hi Guys,
    I have the ASA setup, but after a while when i am running scenarios, like configuring dynamic routing . the ASA hangs.

    Any help would be appreciated

    ReplyDelete
  51. Error
    An internal error occurred. Specifically, a programming assertion was
    violated. Copy the error message exactly as it appears, and get the
    output of the show version command and the contents of the configuration
    file. Then call your technical support representative.

    assertion "_vf_mode_init" failed: file "vf_api.c", line 99



    Rebooting....
    e1000: eth5: e1000_suspend: Error enabling D3 wake
    e1000: eth5: e1000_suspend: Error enabling D3 cold wake
    e1000: eth5: e1000_suspend: Error in setting power state
    e1000: eth4: e1000_suspend: Error enabling D3 wake
    e1000: eth4: e1000_suspend: Error enabling D3 cold wake
    e1000: eth4: e1000_suspend: Error in setting power state
    e1000: eth3: e1000_suspend: Error enabling D3 wake
    e1000: eth3: e1000_suspend: Error enabling D3 cold wake
    e1000: eth3: e1000_suspend: Error in setting power state
    e1000: eth2: e1000_suspend: Error enabling D3 wake
    e1000: eth2: e1000_suspend: Error enabling D3 cold wake
    e1000: eth2: e1000_suspend: Error in setting power state
    e1000: eth1: e1000_suspend: Error enabling D3 wake
    e1000: eth1: e1000_suspend: Error enabling D3 cold wake
    e1000: eth1: e1000_suspend: Error in setting power state
    e1000: eth0: e1000_suspend: Error enabling D3 wake
    e1000: eth0: e1000_suspend: Error enabling D3 cold wake
    e1000: eth0: e1000_suspend: Error in setting power state
    Restarting system.
    .

    its stuck ..please guide me..

    ReplyDelete
  52. stuck with

    An internal error occurred. Specifically, a programming assertion was
    violated. Copy the error message exactly as it appears, and get the
    output of the show version command and the contents of the configuration
    file. Then call your technical support representative.

    assertion "_vf_mode_init" failed: file "vf_api.c", line 99



    Rebooting....
    e1000: eth5: e1000_suspend: Error enabling D3 wake
    e1000: eth5: e1000_suspend: Error enabling D3 cold wake
    e1000: eth5: e1000_suspend: Error in setting power state
    e1000: eth4: e1000_suspend: Error enabling D3 wake
    e1000: eth4: e1000_suspend: Error enabling D3 cold wake
    e1000: eth4: e1000_suspend: Error in setting power state
    e1000: eth3: e1000_suspend: Error enabling D3 wake
    e1000: eth3: e1000_suspend: Error enabling D3 cold wake
    e1000: eth3: e1000_suspend: Error in setting power state
    e1000: eth2: e1000_suspend: Error enabling D3 wake
    e1000: eth2: e1000_suspend: Error enabling D3 cold wake
    e1000: eth2: e1000_suspend: Error in setting power state
    e1000: eth1: e1000_suspend: Error enabling D3 wake
    e1000: eth1: e1000_suspend: Error enabling D3 cold wake
    e1000: eth1: e1000_suspend: Error in setting power state
    e1000: eth0: e1000_suspend: Error enabling D3 wake
    e1000: eth0: e1000_suspend: Error enabling D3 cold wake
    e1000: eth0: e1000_suspend: Error in setting power state
    Restarting system.
    .

    please help..

    ReplyDelete
    Replies

    1. # cd /
      # cd/asa/scripts
      -ash: cd/asa/scripts: not found
      # cd /asa/scripts
      # ./first_start.sh
      test: yes: unknown operand

      Processor memory 731447296, Reserved memory: 41943040 (DSOs: 0 + kernel: 41943040)
      Guest RAM start: 0xb4400080
      Guest RAM end: 0xdd400000
      LINA unit number: 1
      Guest RAM brk: 0xb4401000

      MKDIR failed No such file or directory for /var/log/
      Welcome to LINA - ( F1-on-Linux platform ) desktop version!

      ********************************************************************
      * WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING *
      * *
      * This product is for Cisco internal use ONLY!!! *
      * *
      * WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING *
      ********************************************************************

      i2c_read_byte_w_wait() error, slot = 0x4, device = 0xb0, address = 0 byte count = 1. Reason: I2C_SMBUS_UNSUPPORT

      Total SSMs found: 0
      Ignoring PCI card in slot:0 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:1 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:2 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:3 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:4 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:5 (vendor:0x0 deviceid:0x0)
      Ignoring PCI card in slot:6 (vendor:0x0 deviceid:0x0)

      Total NICs found: 6
      setup_irq: irq handler mismatch






      Unable to open /proc/irq/15/irq error: Device or resource busy
      Panic: kernel - intr_establish: open interupt descriptor irq 15


      -----------------------------------------------
      Traceback output aborted.
      Flushing first exception frame:
      Abort: Assert failure
      vector 0x00000000
      edi 0x0000000f
      esi 0xb4a4a7c8
      ebp 0xb43f7658
      esp 0xb43f764c
      ebx 0x000000ea
      edx 0xb43f7690
      ecx 0x00000006
      eax 0x00000000
      error code n/a
      eip 0xdd6a72a1
      cs 0x00000073
      eflags 0x00000246
      CR2 0x00000000
      Nested traceback attempted via signal, from:
      Page fault: Address not mapped
      vector 0x0000000e
      edi 0xb43f70db
      esi 0xb43f70bf
      ebp 0xb43f6fe8
      esp 0xb43f6fa0
      ebx 0xb43f70bf
      edx 0x08acd5d8
      ecx 0x00000000
      eax 0x00000000
      error code 0x00000004
      eip 0x0805ee77
      cs 0x00000073
      eflags 0x00000286
      CR2 0x00000084

      An internal error occurred. Specifically, a programming assertion was
      violated. Copy the error message exactly as it appears, and get the
      output of the show version command and the contents of the configuration
      file. Then call your technical support representative.

      assertion "_vf_mode_init" failed: file "vf_api.c", line 99



      Rebooting....
      e1000: eth5: e1000_suspend: Error enabling D3 wake
      e1000: eth5: e1000_suspend: Error enabling D3 cold wake
      e1000: eth5: e1000_suspend: Error in setting power state
      e1000: eth4: e1000_suspend: Error enabling D3 wake
      e1000: eth4: e1000_suspend: Error enabling D3 cold wake
      e1000: eth4: e1000_suspend: Error in setting power state
      e1000: eth3: e1000_suspend: Error enabling D3 wake
      e1000: eth3: e1000_suspend: Error enabling D3 cold wake
      e1000: eth3: e1000_suspend: Error in setting power state
      e1000: eth2: e1000_suspend: Error enabling D3 wake
      e1000: eth2: e1000_suspend: Error enabling D3 cold wake
      e1000: eth2: e1000_suspend: Error in setting power state
      e1000: eth1: e1000_suspend: Error enabling D3 wake
      e1000: eth1: e1000_suspend: Error enabling D3 cold wake
      e1000: eth1: e1000_suspend: Error in setting power state
      e1000: eth0: e1000_suspend: Error enabling D3 wake
      e1000: eth0: e1000_suspend: Error enabling D3 cold wake
      e1000: eth0: e1000_suspend: Error in setting power state
      Restarting system.

      Delete
  53. Unable to configure routing process

    ReplyDelete

  54. ciscoasa# copy running-config disk0:/.private/running-config

    Source filename [running-config]?

    Destination filename [/.private/running-config]?
    Cryptochecksum: 6e33e06b 255d8b92 90c27d70 9f5b4de4

    1471 bytes copied in 2.310 secs (735 bytes/sec)
    ciscoasa# copy disk0:/.private/running-config disk0:/.private/startup-config

    Source filename [/.private/running-config]?

    Destination filename [/.private/startup-config]?

    Copy in progress...C
    1471 bytes copied in 0.10 secs
    ciscoasa# conf t
    ciscoasa(config)# boot config disk0:/.private/startup-config
    ciscoasa(config)#
    ciscoasa(config)#
    ciscoasa(config)#
    ciscoasa(config)#
    ciscoasa(config)# exi
    ciscoasa#
    ciscoasa#
    ciscoasa# wr mem
    Building configuration...
    Cryptochecksum: a0ce05e6 e361a34f d8bc3b81 55185b42

    1514 bytes copied in 2.280 secs (757 bytes/sec)open(ffsdev/2/write/41) failed
    open(ffsdev/2/write/40) failed

    ReplyDelete

UA-23728446-1