<?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 cdot management interface firewall rules. in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/cdot-management-interface-firewall-rules/m-p/111539#M23560</link>
    <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are in the early stages of deploying a new Cdot 831 cluster.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For security reasons, management interfaces will be firewalled.. (nodemgmt/clustermgmt/SP) &amp;nbsp;so various firewall rules need to be put in place for services access.&lt;/P&gt;&lt;P&gt;I see that administration services normally connect to the cluster management (over port 443) but what about other "infrastructure" type services.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eg. SMTP,NTP, DNS, SNMP &amp;nbsp;etc - It is not clear which services&amp;nbsp;use which interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone provide an overview?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 22:59:00 GMT</pubDate>
    <dc:creator>colin_graham</dc:creator>
    <dc:date>2025-06-04T22:59:00Z</dc:date>
    <item>
      <title>cdot management interface firewall rules.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/cdot-management-interface-firewall-rules/m-p/111539#M23560</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are in the early stages of deploying a new Cdot 831 cluster.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For security reasons, management interfaces will be firewalled.. (nodemgmt/clustermgmt/SP) &amp;nbsp;so various firewall rules need to be put in place for services access.&lt;/P&gt;&lt;P&gt;I see that administration services normally connect to the cluster management (over port 443) but what about other "infrastructure" type services.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eg. SMTP,NTP, DNS, SNMP &amp;nbsp;etc - It is not clear which services&amp;nbsp;use which interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone provide an overview?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 22:59:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/cdot-management-interface-firewall-rules/m-p/111539#M23560</guid>
      <dc:creator>colin_graham</dc:creator>
      <dc:date>2025-06-04T22:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: cdot management interface firewall rules.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/cdot-management-interface-firewall-rules/m-p/111550#M23561</link>
      <description>&lt;P&gt;Hi Colin -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Great question. &amp;nbsp;CDot 8.3 family changed a number of things with respect to various networking services you mentioned.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Services can be generally categorized by scope - that is cluster scoped (or cluster wide) services, node scoped services, and SVM (vServer) scoped services. &amp;nbsp;Prior to cDot 8.3, SVM scoped services such as DNs, LDAP, Active Directory, etc. could use cluster or node level management interfaces to query the appropriate service. &amp;nbsp;In 8.3+, SVM scoped services must use a network interface associated only with the SVM. &amp;nbsp;For that reason, there are now three possible types of management interfaces to consider - cluster, node, and SVM. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SVM scoped services need an SVM based interface. &amp;nbsp;It is best practice to define a "management" interface with protocol&amp;nbsp;"none". &amp;nbsp;Such an interface will be the default to use for SVM scoped services. &amp;nbsp;If a specific management interface is not defined, SVMs will use any other "data" interface available. &amp;nbsp;SVM scoped services include DNS client (for the SVM), LDAP, AD, NIS, and the data protocols of course.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Node scoped services use a node management network interface. &amp;nbsp;Node scoped services include NTP, SNMP, SMTP (for autosupport if configured to send email), SSH server for connection to a node specifically, HTTPS server, HTTP/S outbound (again for autosupport), DNS client (for the node), FTP client (might be used for software updates, sending support logs, etc.). &amp;nbsp;Some of these are optional depending on your use case - for example I use an internal utility FTP server for software/firmware updates because it's simpler, so I have to allow FTP client out from my node management interfaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster scoped services use a cluster management network interface. &amp;nbsp;Cluster scoped services are SSH server for connection to the "cluster" by name, and the HTTPS server for cluster management functions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A Node service processor should allow SSH inbound of course. &amp;nbsp;There is also a configureable API-service port for the SPs, default is port 50000 per documentation. &amp;nbsp;This service can be disabled. &amp;nbsp;The SP also supports the Remote Support Agent function which is a service that can enable automatic upload of information to Netapp Support when incidents occur. &amp;nbsp;It basically works by periodically connecting to a designated Netapp server over the web via HTTPS protocols to see if Netapp Support needs anything. &amp;nbsp;When an incident has occurred, the RSA connects more frequently - about once every five minutes for a while if memory servers. &amp;nbsp;Netapp support engineers can post that they'd like a specific log or autosupport to help solve an incident, and the RSA mechanism can then automatically upload that log. &amp;nbsp;RSA uses web protocols and can also work through a proxy server to access the internet if desired. &amp;nbsp;If you plan for using RSA the key thing to understand is that Netapp cannot access your kit directly, nor can they pull any data from your SVMs. &amp;nbsp;RSA just makes getting the data that you'd normally send to Netapp more easily available in cases where a person isn't immediately available to do it. &amp;nbsp;There's a whole guide on network setup for RSA available on the support site. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's the quick summary - there is a lot more detail information of course available in the 8.3.1 documentation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob Greenwald&lt;/P&gt;&lt;P&gt;Lead Storage Engineer&lt;/P&gt;&lt;P&gt;Huron Legal | Huron Consulting Group&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 13:39:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/cdot-management-interface-firewall-rules/m-p/111550#M23561</guid>
      <dc:creator>bobshouseofcards</dc:creator>
      <dc:date>2015-10-22T13:39:37Z</dc:date>
    </item>
  </channel>
</rss>

