<?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: Firepower Secondary SSH in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4404793#M1080877</link>
    <description>&lt;P&gt;Both devices' management interfaces should be available via ssh (as long as you did not apply an ssh-access-list via the FTD cli).&lt;/P&gt;
&lt;P&gt;The default is that there is no restriction:&lt;/P&gt;
&lt;PRE&gt;&amp;gt; show ssh-access-list 
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
ACCEPT     tcp      anywhere             anywhere             state NEW tcp dpt:ssh
&amp;gt; &lt;/PRE&gt;</description>
    <pubDate>Tue, 18 May 2021 15:42:31 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2021-05-18T15:42:31Z</dc:date>
    <item>
      <title>Firepower Secondary SSH</title>
      <link>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4404720#M1080873</link>
      <description>&lt;P&gt;I have a firepower 4100 series setup as an HA pair that I just inherited. I am not familiar with this device. I noticed today that I can SSH into the primary FTD, but not the secondary. Is this normal? I just want to make sure there isn't anything wrong. In the FMC web interface, I am not seeing any problem. I just want to check and see if this is normal.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 18 May 2021 14:22:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4404720#M1080873</guid>
      <dc:creator>jeremy-rogers</dc:creator>
      <dc:date>2021-05-18T14:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Secondary SSH</title>
      <link>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4404793#M1080877</link>
      <description>&lt;P&gt;Both devices' management interfaces should be available via ssh (as long as you did not apply an ssh-access-list via the FTD cli).&lt;/P&gt;
&lt;P&gt;The default is that there is no restriction:&lt;/P&gt;
&lt;PRE&gt;&amp;gt; show ssh-access-list 
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
ACCEPT     tcp      anywhere             anywhere             state NEW tcp dpt:ssh
&amp;gt; &lt;/PRE&gt;</description>
      <pubDate>Tue, 18 May 2021 15:42:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4404793#M1080877</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-05-18T15:42:31Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Secondary SSH</title>
      <link>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4759292#M1097053</link>
      <description>&lt;P&gt;This is a bug in Cisco FTD. Sometimes it works, sometimes it does not. I'll file a bug report in the next beta session.&lt;/P&gt;</description>
      <pubDate>Sun, 22 Jan 2023 05:56:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4759292#M1097053</guid>
      <dc:creator>bcoverstone</dc:creator>
      <dc:date>2023-01-22T05:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Secondary SSH</title>
      <link>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4846641#M1101088</link>
      <description>&lt;P&gt;Was the bug report completed by chance? Wondering what the bug ID is.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 18:11:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-secondary-ssh/m-p/4846641#M1101088</guid>
      <dc:creator>KeelynHenning0941</dc:creator>
      <dc:date>2023-05-31T18:11:15Z</dc:date>
    </item>
  </channel>
</rss>

