Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Network and Storage Protocols

option interface.blocked.mgmt_data_traffic

pwo

Hello Fellow Toasters,

I can't seem to find any document describing the option interface.blocked.mgmt_data_traffic (found e.g. in Data ONTAP 7.3.6P2, default value: off). Google and now.netapp.com search did not return a single hit.

Kindest regards

Peter

1 ACCEPTED SOLUTION

pwo

The option interface.blocked.mgmt_data_traffic controls the protocol filter for dedicated management ports, such as e0M on many platforms (not all platforms have a dedicated management port). If the option is set to on (the default for new installs), then NDMP, NFS, CIFS, iSCSI and the SNAP* family of data protocols will be blocked by the dedicated management port. "On" is the recommended setting because a dedicated management port is a low-bandwidth port that does not support jumbo frames, vlans or ifgrps. If a dedicated management port is used for data traffic, it can hide misconfigurations that might lead to serious loss of filer throughput. A dedicated management port should only be configured with addresses that are on isolated management-only subnets.

View solution in original post

3 REPLIES 3

pwo

The option interface.blocked.mgmt_data_traffic controls the protocol filter for dedicated management ports, such as e0M on many platforms (not all platforms have a dedicated management port). If the option is set to on (the default for new installs), then NDMP, NFS, CIFS, iSCSI and the SNAP* family of data protocols will be blocked by the dedicated management port. "On" is the recommended setting because a dedicated management port is a low-bandwidth port that does not support jumbo frames, vlans or ifgrps. If a dedicated management port is used for data traffic, it can hide misconfigurations that might lead to serious loss of filer throughput. A dedicated management port should only be configured with addresses that are on isolated management-only subnets.

View solution in original post

Andre_Clark

Will this also block/restrict e0M from registering to DNS if the option dns.update.enable secure is set? I'm trying to keep the e0M interface from dynamically registering the hostname.

scottgelb

Just found this... in the ifconfig the "no_ddns" parameter...   ifconfig e0M no_ddns IP_address

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public