<?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 ASA Multiple Contexts on ASDM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3344705#M967669</link>
    <description>&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using 2 x ASA running&amp;nbsp;9.6(2) with ASDM 7.8(2). Multiple contexts have been enabled on Active-Active configuration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While on CLI I can easily spot on what unit the context&amp;nbsp;is Active so I don't risk using the Standby unit and un sync the config (I have added:&amp;nbsp;prompt hostname context priority state )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now on ASDM no matter what unit I connect to and the connect to a context it's always reported as Active as in the attachment below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Florin.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 15:29:31 GMT</pubDate>
    <dc:creator>Florin Barhala</dc:creator>
    <dc:date>2020-02-21T15:29:31Z</dc:date>
    <item>
      <title>ASA Multiple Contexts on ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3344705#M967669</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using 2 x ASA running&amp;nbsp;9.6(2) with ASDM 7.8(2). Multiple contexts have been enabled on Active-Active configuration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While on CLI I can easily spot on what unit the context&amp;nbsp;is Active so I don't risk using the Standby unit and un sync the config (I have added:&amp;nbsp;prompt hostname context priority state )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now on ASDM no matter what unit I connect to and the connect to a context it's always reported as Active as in the attachment below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Florin.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:29:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3344705#M967669</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2020-02-21T15:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Multiple Contexts on ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3345469#M967670</link>
      <description>&lt;P&gt;I will just bump this and post another "ASDM management question": how can you find out the users using ASDM on the firewall you are connected to?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was scrolling through ASDM config and I got the message about config update and need to refresh. How can I see the other logged in users?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;CLI doesn't help that much:&amp;nbsp;&lt;EM&gt;show asdm sessions&amp;nbsp;&lt;/EM&gt;shows just the ASDM allowed ip, but no username/login detail&lt;/P&gt;</description>
      <pubDate>Fri, 09 Mar 2018 11:13:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3345469#M967670</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-09T11:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Multiple Contexts on ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3345512#M967671</link>
      <description>&lt;P&gt;One day later I solved the mystery: while on ASDM when changing config, ASDM uses a dedicated command: &lt;STRONG&gt;failover exec active&lt;/STRONG&gt;.&lt;BR /&gt;&lt;BR /&gt;This makes sure the config is being pushed on the ACTIVE unit, no matter that ASDM admin sits on the standby unit for that context.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Mar 2018 12:10:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-contexts-on-asdm/m-p/3345512#M967671</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-09T12:10:13Z</dc:date>
    </item>
  </channel>
</rss>

