<?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: accessing switches via SSH in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/accessing-switches-via-ssh/m-p/3345294#M967541</link>
    <description>&lt;P&gt;try this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/best_practices/cli_mgmt_guide/cli_mgmt_bp/connect.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/best_practices/cli_mgmt_guide/cli_mgmt_bp/connect.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or you could put an acl on every SVi, you dont want to connect to, to deny port 22.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;personally I would worry more about the source IP that is trying to connect than what it is trying to connect TO&lt;/P&gt;</description>
    <pubDate>Fri, 09 Mar 2018 02:35:05 GMT</pubDate>
    <dc:creator>Dennis Mink</dc:creator>
    <dc:date>2018-03-09T02:35:05Z</dc:date>
    <item>
      <title>accessing switches via SSH</title>
      <link>https://community.cisco.com/t5/network-security/accessing-switches-via-ssh/m-p/3345270#M967537</link>
      <description>&lt;P&gt;Hello, I have a couple Nexus 9k switches that have a good amount of interface IPs (SVIs) on them that are used part of the VPC process running between the 2 N9ks.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I take any of those SVIs IP addresses and put in the IP into putty, I can SSH into the switch.&amp;nbsp; Since there are so many IP interfaces on those switches; then in turn there are so many ways to access the N9ks via SSH.&amp;nbsp; How do I limit this so only typing the mgmt address of the switch I can access the switch?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:29:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-switches-via-ssh/m-p/3345270#M967537</guid>
      <dc:creator>Amafsha1</dc:creator>
      <dc:date>2020-02-21T15:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: accessing switches via SSH</title>
      <link>https://community.cisco.com/t5/network-security/accessing-switches-via-ssh/m-p/3345294#M967541</link>
      <description>&lt;P&gt;try this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/best_practices/cli_mgmt_guide/cli_mgmt_bp/connect.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/best_practices/cli_mgmt_guide/cli_mgmt_bp/connect.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or you could put an acl on every SVi, you dont want to connect to, to deny port 22.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;personally I would worry more about the source IP that is trying to connect than what it is trying to connect TO&lt;/P&gt;</description>
      <pubDate>Fri, 09 Mar 2018 02:35:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-switches-via-ssh/m-p/3345294#M967541</guid>
      <dc:creator>Dennis Mink</dc:creator>
      <dc:date>2018-03-09T02:35:05Z</dc:date>
    </item>
  </channel>
</rss>

