<?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: EOS Out-Of-Band Management in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44105#M5849</link>
    <description>Question:  if you set an  ip address on an  interface as management and then disable ip-forwarding on that interface  does that restrict management access to that address?</description>
    <pubDate>Wed, 20 Apr 2016 19:13:00 GMT</pubDate>
    <dc:creator>Curtis_Parish1</dc:creator>
    <dc:date>2016-04-20T19:13:00Z</dc:date>
    <item>
      <title>EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44102#M5846</link>
      <description>In the process of configuring / designing an Out-Of-Band management network in EOS.&lt;BR /&gt;
&lt;BR /&gt;
Will need to make this as secure as possible so things like SNMP, SSH, Syslog, HTTPS and Netflow for / via NetSight are all done out of band on the management network only. All the switches in use are either S or K series.&lt;BR /&gt;
&lt;BR /&gt;
My first thoughts are that I would have to do this with Policy and ACL's, but it would be preferential to use a separate VRF. &lt;BR /&gt;
&lt;BR /&gt;
So my questions are:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;What would the best why to ago about this in the most secure manner? 
&lt;/LI&gt;&lt;LI&gt;Perhaps there is a better method in EOS? 
 
&lt;/LI&gt;&lt;LI&gt;If I was to use a VRF for management (and my point in using it), is I could then just enable the management protocols on the management VRF and turn them off on the default VRF. (I don't believe its possible, but it would provide the simplest and most secure set-up, perhaps still in conjunction with policy and ACL's)&lt;/LI&gt;&lt;/UL&gt;Many thanks in advance.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Apr 2016 20:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44102#M5846</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-04-19T20:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44103#M5847</link>
      <description>Hi Martin,&lt;BR /&gt;
&lt;BR /&gt;
I don't think you can disable SNMP, SSH, etc. in a VRF.&lt;BR /&gt;
&lt;BR /&gt;
To lock down management access you should look into the host ACL ("ip host-access &lt;ACL&gt;"). You can (and should) use an extended ACL, so you can allow just the interface IP you want to use for management. With a host ACL you need to consider and allow all layer 3 protocols (VRRP, OSPF, BGP, ...) you intend to use.&lt;BR /&gt;
&lt;BR /&gt;
Erik&lt;BR /&gt;&lt;/ACL&gt;</description>
      <pubDate>Wed, 20 Apr 2016 12:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44103#M5847</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2016-04-20T12:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44104#M5848</link>
      <description>Thanks for the reply.&lt;BR /&gt;
&lt;BR /&gt;
Think my plan will be to use a VRF for management and use ACL's either side to stop and control IP traffic for containment, with the use of 'ip host-access' that you have helpfully provided.&lt;BR /&gt;
&lt;BR /&gt;
Many thanks.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Apr 2016 13:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44104#M5848</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-04-20T13:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44105#M5849</link>
      <description>Question:  if you set an  ip address on an  interface as management and then disable ip-forwarding on that interface  does that restrict management access to that address?</description>
      <pubDate>Wed, 20 Apr 2016 19:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44105#M5849</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2016-04-20T19:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44106#M5850</link>
      <description>I do not think that is sufficient.&lt;BR /&gt;
&lt;BR /&gt;
There are two GTAC Knowledge articles regarding restricting management access:&lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-ACL-on-a-S-K-Series-to-Allow-Access-to-only-One-Interface" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-ACL-on-a-S-K-Series-to...&lt;/A&gt; 
&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-host-access-list-on-S-Series-to-prevent-unauthorized-login-attempts/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-host-access-list-on-S-Series...&lt;/A&gt; 
&lt;/LI&gt;&lt;/OL&gt;As far as I remember any reachable active interface can be used for management unless an ACL restricts access. The host ACL controls access via any interface.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Apr 2016 19:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44106#M5850</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2016-04-20T19:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: EOS Out-Of-Band Management</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44107#M5851</link>
      <description>Here is a brief KB article, but maybe it is of use to you: &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/Non-Global-VRF-Loopback-IP-not-responding-to-SNMP-or-SSH" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/Non-Global-VRF-Loopback-IP-not-responding-to-...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
What I take from that: Use the global VRF to perform management, and put your production traffic into a VRF that you create additionally.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Apr 2016 01:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/eos-out-of-band-management/m-p/44107#M5851</guid>
      <dc:creator>jeronimo</dc:creator>
      <dc:date>2016-04-29T01:30:00Z</dc:date>
    </item>
  </channel>
</rss>

