Always when I am configuring the OnCommand Operations Manager portion, I get the following doubt: when configuring the ip address for the data collection feature, I tend to select the management port ip address. Which makes sense.
But on the page where I configure this, I have the NDMP status field. Which could show a failed status if the management port is configured for management traffic only (which I also think is the correct setting). So this is a normal bahavior? How should I set up this?
Starting with Data ONTAP 8.0.2, you can block certain types of data traffic on the e0M interface, including SnapMirror transfers, SnapVault transfers, and data transfers that use the CIFS, NFS, and NDMP protocols. This optimizes the system performance by not allowing high-bandwidth data traffic on e0M, which is a low-bandwidth dedicated management interface.
This task needs to be performed for storage systems that are upgraded to Data ONTAP 8.0.2 because the default value of the interface.blocked.mgmt_data_traffic option is off in such systems. However, in new systems installed with Data ONTAP 8.0.2, the default value of the interface.blocked.mgmt_data_traffic option is on.
1. To block all types of data traffic on e0M, enter the following command:
options interface.blocked.mgmt_data_traffic on
Or ONTAP can block certain protocols:
Restricting protocol access
If a protocol is enabled for Data ONTAP, you can restrict the protocol's access to the storage system by specifying the host name, IP address, or network interface name.
• protocol is the name of the protocol you want to allow access to the storage system. It can
be rsh, telnet, ssh, httpd, httpd.admin, snmp, ndmpd, snapmirror, or snapvault.
Hope this helps and explains why NDMP is showing down.
First let me tell you how to make this work. Later explain you the same.
Turn this option value to OFF.
This mean that we are allowing data traffice through e0m. That way DFM is happy and NDMP status would be shown as up and good. As DFM always talks to one interface it checks for the NDMP service also in the same interface.
So to make it happy we are enabling the option by setting its value to OFF, which mean allow data traffic.
But in the background we are specifying the options ndmpd.preferred_interface vif_nas-48 which is sitting on a interface other than e0m. This way the data traffic is not happening through e0m instead through the vif.
Note for SV you will have to use ndmpd.preferred_interface on the controller.
For QSM and VSM you will have to use dfm host set <hostid> hostPreferredAddr1=<IP address of interface other than e0m> on both your source and destination filer.
PM will create a connection entry for VSM and QSM in the snapmirror.conf entry of the filer and route the traffic through those interfaces and not through e0m.