EOS Out-Of-Band Management

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • Answered
In the process of configuring / designing an Out-Of-Band management network in EOS.

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.

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.

So my questions are:
  • What would the best why to ago about this in the most secure manner?
  • Perhaps there is a better method in EOS?
  • 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)
Many thanks in advance.
Photo of Martin Flammia

Martin Flammia

  • 5,724 Points 5k badge 2x thumb

Posted 2 years ago

  • 0
  • 1
Photo of Erik Auerswald

Erik Auerswald, Embassador

  • 12,782 Points 10k badge 2x thumb
Hi Martin,

I don't think you can disable SNMP, SSH, etc. in a VRF.

To lock down management access you should look into the host ACL ("ip host-access <ACL>"). 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.

Erik
Photo of Martin Flammia

Martin Flammia

  • 5,724 Points 5k badge 2x thumb
Thanks for the reply.

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.

Many thanks.
Photo of Curtis Parish

Curtis Parish

  • 3,332 Points 3k badge 2x thumb
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? 
(Edited)
Photo of Erik Auerswald

Erik Auerswald, Embassador

  • 12,782 Points 10k badge 2x thumb
I do not think that is sufficient.

There are two GTAC Knowledge articles regarding restricting management access:
  1. https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-ACL-on-a-S-K-Series-to...
  2. https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-host-access-list-on-S-Series...
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.
Photo of jeronimo

jeronimo

  • 1,198 Points 1k badge 2x thumb
Here is a brief KB article, but maybe it is of use to you: https://gtacknowledge.extremenetworks.com/articles/Q_A/Non-Global-VRF-Loopback-IP-not-responding-to-...

What I take from that: Use the global VRF to perform management, and put your production traffic into a VRF that you create additionally.