<?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: Firewall AAA configuration in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778463#M7931</link>
    <description>&lt;P&gt;ISE seems to indicate that the Authorization result is looking for an undefined shell profile.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does the detail report from ISE Live logs shed any more light?&lt;/P&gt;</description>
    <pubDate>Sun, 13 Jan 2019 05:17:28 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2019-01-13T05:17:28Z</dc:date>
    <item>
      <title>Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777863#M7855</link>
      <description>&lt;P&gt;Does the aaa commands/configuration copy to standby firewall? I can't seem to get to my secondary ASA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE class="content_table" border="0"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="31%"&gt;Message Text&lt;/TD&gt;
&lt;TD width="69%"&gt;Failed-Attempt: Session Authorization encountered an error&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="31%"&gt;Failure Reason&lt;/TD&gt;
&lt;TD width="69%"&gt;15020 Could not find selected Shell Profiles&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="31%"&gt;Resolution&lt;/TD&gt;
&lt;TD width="69%"&gt;Add a shell profile to the result of the rule, or modify the rule condition so that this rule is not selected for session authorisation&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="31%"&gt;Root Cause&lt;/TD&gt;
&lt;TD width="69%"&gt;Could not find selected Shell Profiles&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="31%"&gt;Username&lt;/TD&gt;
&lt;TD width="69%"&gt;stevenwilliams&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:39:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777863#M7855</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2020-02-21T16:39:14Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777882#M7859</link>
      <description>&lt;P&gt;hmm..... they should be.&lt;/P&gt;&lt;P&gt;stupid question does your asa configured with active standby ip addresses?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 15:48:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777882#M7859</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-11T15:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777890#M7863</link>
      <description>Yes they do. I can ping the standby and get a login prompt but nothing works, but the primary works fine and a wr standby doesnt seem to fix the issue.</description>
      <pubDate>Fri, 11 Jan 2019 15:55:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777890#M7863</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-01-11T15:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777920#M7865</link>
      <description>&lt;P&gt;What ASA code on it?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 16:50:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3777920#M7865</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-11T16:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778001#M7868</link>
      <description>9.6</description>
      <pubDate>Fri, 11 Jan 2019 18:56:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778001#M7868</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-01-11T18:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778003#M7869</link>
      <description>&lt;P&gt;curious does the ISE in network devices have a standby ip address of this ASA?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 18:58:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778003#M7869</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-11T18:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778086#M7871</link>
      <description>Yes since thats how I grabbed that log I posted. Its from ISE.</description>
      <pubDate>Fri, 11 Jan 2019 21:15:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778086#M7871</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-01-11T21:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778093#M7929</link>
      <description>&lt;P&gt;Run &lt;STRONG&gt;'test aaa-server authentication '&lt;/STRONG&gt; on the Standby unit and check what the reason for the failure is.&lt;BR /&gt;Enable &lt;STRONG&gt;'debug aaa authentication'&lt;/STRONG&gt; on the Standby unit and watch the output when you try to authenticate.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 21:24:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778093#M7929</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-11T21:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778095#M7930</link>
      <description>don't have the ability till I can get someone onsite to console it for me. wont allow access via ssh or http.</description>
      <pubDate>Fri, 11 Jan 2019 21:25:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778095#M7930</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-01-11T21:25:19Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778463#M7931</link>
      <description>&lt;P&gt;ISE seems to indicate that the Authorization result is looking for an undefined shell profile.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does the detail report from ISE Live logs shed any more light?&lt;/P&gt;</description>
      <pubDate>Sun, 13 Jan 2019 05:17:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778463#M7931</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-01-13T05:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778609#M8140</link>
      <description>&lt;P&gt;I agree with Marvin here that there is an issue with the ISE authorization profile configuration, however it is a bit strange that you are unable to access the secondary ASA via SSH or HTTPS.&amp;nbsp; Have you tried to power-cycle the standby ASA?&lt;/P&gt;</description>
      <pubDate>Sun, 13 Jan 2019 15:50:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3778609#M8140</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2019-01-13T15:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779358#M8141</link>
      <description>The ISE authorization profile is fine since it works on the primary ASA and uses the same auth profile. It just seems like the standby ASA didnt get the aaa commands on the wr standby.</description>
      <pubDate>Mon, 14 Jan 2019 16:56:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779358#M8141</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-01-14T16:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779364#M8142</link>
      <description>&lt;P&gt;I agree with&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/321173"&gt;@Steven Williams&lt;/a&gt;. As he done all from the active ASA to figure out what could be the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for the update.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 17:04:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779364#M8142</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-14T17:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall AAA configuration</title>
      <link>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779372#M8143</link>
      <description>&lt;P&gt;You do know you can check the configuration on the standby ASA from the primary ASA, right?&lt;/P&gt;
&lt;P&gt;for example you can issue the following command to se the AAA configuration on the standby&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;failover exec standby show run aaa&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;As long as failover is configured correctly I am having a hard time believing there is an issue with the configuration on the standby device.&amp;nbsp; I am leaning towards either a process that is hanging on the standby which will be solved by rebooting the standby device, or an issue with configuration on ISE.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 17:11:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-aaa-configuration/m-p/3779372#M8143</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2019-01-14T17:11:10Z</dc:date>
    </item>
  </channel>
</rss>

