<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72 in Cisco Software Discussions</title>
    <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000108#M8564</link>
    <description>&lt;P&gt;This is an ASA virtual.&amp;nbsp; So the config is not shared or replicated between them. basically they are two separate devices with what amounts to a load balancer between them.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2024 18:50:32 GMT</pubDate>
    <dc:creator>debbiebeitler</dc:creator>
    <dc:date>2024-01-18T18:50:32Z</dc:date>
    <item>
      <title>Unable to connect via ASDM after upgrading ASDM image in ASA to 7202</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/4998807#M8544</link>
      <description>&lt;P&gt;Tried to upgrade ASDM on a 9.16 ASAv, from 7181-152 to 7202.&lt;BR /&gt;Worked fine on the "secondary" asa.&lt;BR /&gt;But on the active one, Cannot connect after restarting ASDM.&lt;BR /&gt;I goes through the entire log in process, and then I get "ASDM cannot be loaded, hostname wrong".&lt;/P&gt;&lt;P&gt;I can still SSH into it, and everything look goods, so I did a reload. And now I get "The certificate present in this device is not valid. Certificate date is Expired...."&lt;BR /&gt;The Date on the ASA is fine.&lt;BR /&gt;It has the same certificates and CA certs as did the backup. None of which show as expired.&lt;/P&gt;&lt;P&gt;I reverted back to the previous ASDM image for now.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jan 2024 19:26:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/4998807#M8544</guid>
      <dc:creator>debbiebeitler</dc:creator>
      <dc:date>2024-01-17T19:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/4999970#M8562</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;&lt;SPAN&gt;Tried to upgrade ASDM on a 9.16 ASAv, from 7181-152 to 7202.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Worked fine on the "secondary" asa. &amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;this is not possible!&lt;BR /&gt;you need to set your ASDM version from the primary (c.q. active) ASA&lt;BR /&gt;it will activate this for BOTH failover members at the same time (as this is replicated)&lt;BR /&gt;&lt;BR /&gt;my workflow is for the GUI (old ASDM version)&lt;BR /&gt;- transfer the ASDM image to the standby ASA&lt;BR /&gt;- answer NO&amp;nbsp; to the question for setting this as the default ASDM image&lt;BR /&gt;- transfer&amp;nbsp;the ASDM image to the active ASA&lt;BR /&gt;- answer YES to the&amp;nbsp; question for setting this as the default ASDM image&lt;BR /&gt;- restart ASDM connection to use the new version&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 15:57:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/4999970#M8562</guid>
      <dc:creator>pieterh</dc:creator>
      <dc:date>2024-01-18T15:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000108#M8564</link>
      <description>&lt;P&gt;This is an ASA virtual.&amp;nbsp; So the config is not shared or replicated between them. basically they are two separate devices with what amounts to a load balancer between them.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 18:50:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000108#M8564</guid>
      <dc:creator>debbiebeitler</dc:creator>
      <dc:date>2024-01-18T18:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000280#M8565</link>
      <description>&lt;P&gt;Same result with asdm-7201.&amp;nbsp; Using asdm-7191-95 works fine.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 19:52:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000280#M8565</guid>
      <dc:creator>debbiebeitler</dc:creator>
      <dc:date>2024-01-18T19:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000287#M8566</link>
      <description>&lt;P&gt;Upgrading the ASA tp 9.18.3.56 does not make a difference.&amp;nbsp; Still works with asdm-7191. but not with either asdm 7201 or 7272&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 20:06:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000287#M8566</guid>
      <dc:creator>debbiebeitler</dc:creator>
      <dc:date>2024-01-18T20:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000561#M8568</link>
      <description>&lt;P&gt;back to the first post&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;&lt;SPAN&gt;And now I get "The certificate present in this device is not valid. Certificate date is Expired...." &amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;and your addition &amp;gt;&amp;gt;&amp;gt;&amp;nbsp;basically they are two separate devices with what amounts to a load balancer between them &amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;&lt;/SPAN&gt;did you check the consistency of certificates between the two ASA's (maybe also the load-balancer) ?&lt;BR /&gt;(IS the expected certificate assigned to the management interface ?)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 07:33:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5000561#M8568</guid>
      <dc:creator>pieterh</dc:creator>
      <dc:date>2024-01-19T07:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5001122#M8592</link>
      <description>&lt;P&gt;On both units, there are no certificates assigned to the management interface. Only to the public and internal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I accessed the management interface with a browser and saw that it using an older VPN cert "ssl trust-point &amp;lt;expired cert&amp;gt;" management.&amp;nbsp; Odd thing is that in the ASDM, it did not show a cert attached to the management interface.&amp;nbsp; The other one that worked fine, was using the self-signed ASA certificate.&amp;nbsp; I removed the line "ssl trust-point" line for the management interface and it went back to using the self-signed cert which has not expired.&amp;nbsp; So ASDM is now happy with version 7202.&lt;/P&gt;&lt;P&gt;Thanks for helping the light bulb go off.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 15:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5001122#M8592</guid>
      <dc:creator>debbiebeitler</dc:creator>
      <dc:date>2024-01-19T15:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5001147#M8593</link>
      <description>&lt;P&gt;I'm happy to hear you found the interfering configuration&lt;BR /&gt;Regards,&lt;/P&gt;
&lt;P&gt;Pieter&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 15:43:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5001147#M8593</guid>
      <dc:creator>pieterh</dc:creator>
      <dc:date>2024-01-19T15:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5161514#M10071</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I am having the same problem. I only have 1 ASA5525 running &lt;STRONG&gt;ASA Version 9.14(4)24&lt;/STRONG&gt; and &lt;STRONG&gt;ASDM version 7.18(1)152&lt;/STRONG&gt;. ASA upgrade went fine. but when I tried to upgrade the ASDM, I received the error "&lt;SPAN&gt;The certificate present in this device is not valid. Certificate date is Expired or not valid as per current date".&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How do I roll back the ASDM version if I do not have access to the ASA through the ASDM ...? Thank you ...!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2024 18:28:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5161514#M10071</guid>
      <dc:creator>Ced W</dc:creator>
      <dc:date>2024-08-15T18:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to connect via ASDM after upgrading ASDM image in ASA to 72</title>
      <link>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5215520#M10492</link>
      <description>&lt;P&gt;Just add in Java security tab &lt;A href="https://ip_address_asa" target="_blank"&gt;https://ip_address_asa&lt;/A&gt;&amp;nbsp;- then ASDM 7202 will work as well&lt;/P&gt;</description>
      <pubDate>Sat, 26 Oct 2024 12:02:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cisco-software-discussions/unable-to-connect-via-asdm-after-upgrading-asdm-image-in-asa-to/m-p/5215520#M10492</guid>
      <dc:creator>tomasz.gluszko</dc:creator>
      <dc:date>2024-10-26T12:02:34Z</dc:date>
    </item>
  </channel>
</rss>

