cisco asdm unable to launch device manager

HTTP: file not modified: public/cisco.gif HTTP: processing GET URL '/admin/public/cisco.gif' from host 11.11.11.2 HTTP: sending file: public/index.html, length: 6725 HTTP: processing GET URL '/admin/public/index.html' from host 11.11.11.2 HTTP: redirecting to: /admin/public/index.html HTTP: processing GET URL '/' from host 11.11.11.2

Once the user accepts the certificate, the web browser displays the Cisco ASDM page: Cisco ASDM 6.4(1) index.htmlĪnd the debug output of theÂ ASA shows the web browser requesting everything that is presented in index.html such as the graphics and the HTML file. The management workstation at 11.11.11.2 opens a web browser to which is the Cisco ASA’s outside interface. The following is what a typical ASDM session establishment looks like in the debug output: To enable debugging, use the debug http command. Other ASDM issues can be more easily diagnosed with a quick snuffle through the debug logs. Management traffic, such as via ASDM, terminates at an interface and does not traverse the firewall. Unlike traffic traversing the ASA, you do not need to explicitly permit HTTP or HTTP traffic in an ACL. ASA does not contain a compatible ASDM image on flash (To rectify, copy a compatible ASDM image onto the ASA flash).

Management workstation does not have a compatible web browser or Java installed (To rectify, install/enable JRE or use another browser).

Management workstation is trying to connect on the wrong port (To rectify, use http server enable command on the ASA to change the port, or have the management workstation connect to.

Management workstation’s IP address is not permitted to access ASA (To rectify, use http command).

HTTP server not enabled on the ASA (To rectify, use http server enable command).

If you cannot connect to the Cisco ASA via ASDM, it’s probably due to one of these causes: ASDM is pretty straightforward to troubleshoot.

Cisco asdm unable to launch device manager