Classification volume discovery using wrong interface

[AndrewPDX]

Hi all,

I'm fairly new to this product but was able to get the connector and classification appliances installed and connected together, and with my on-prem clusters. However, I'm running into an issue on a few of my SVMs where the classification appliance appears to be "discovering" the volumes using the incorrect LIFs; that is, on LIFs that are either unrouted or on a different VLAN from the appliance. 

I've confirmed that the SVMs in question do have LIFs on the correct/same VLAN as the appliance, and the export policies are all set to allow the connection. Checking access via the check-access command shows that connections are allowed using the LIF on the same VLAN. 

Is there any way to force these volumes to use a particular LIF? Or a way to tell why they are preferring a "bad" LIF over the one on the same VLAN? 

Thanks!

[devvik]

This happens when SVM having more than one IP while  discovering a volume in BlueXP Classification, One can fix it using the steps mentioned in below KB or just perform the below action item:

-- Create a default Ethernet interface on the Datasense VM and Connector VM to the same network/vlan as the SMB LIF on the ONTAP node.

https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/Classification_discovers_wrong_SVM_IP