Description

It is sometimes necessary to change the IP address of the NetApp Cluster Management Logical Interface (LIF) in the datacenter.

Once this is done, Data Insight (DI) will need to be updated to maintain connectivity for scanning and receiving audit events from the Storage Virtual Machines (SVM’s).

The following process can be used to update DI accordingly.

Collect the following information:

• The Device ID’s of the SVM’s/CIFS Servers from the NetApp cluster that are monitored by DI:
   
  • On the Management Server, open a command prompt with elevated permissions (Run as Administrator) and navigate to \Program Files\DataInsight\bin.
     
  • Execute the following command to retrieve the ID’s.

> configdb.exe -p -T filer

• • The output will appear similar to this:

#|dev_id|dev_name|dev_type|dev_enabled|coll_id|flags|

|4|CIFS2|9|1|3|0|

|1|CIFS_SERVER01|9|1|3|0|

|2|winnas.vtas.local|4|1|3|0|

• • In this example, both CIFS_SERVER01 (Device ID = 1) and CIFS2 (Device ID = 4) are SVM’s from the NetApp cluster that has a new IP address.
     
• New IP address of the NetApp cluster Management LIF.

After the base information has been obtained, update Data Insight as follows:

• Use the previously opened command prompt (or open a new prompt with elevated permissions).
   
• Run the following command to update the IP address for the NetApp cluster:

> configdb.exe -o -T filer -k -J vserver.cluster -j

Example from a lab environment:

> configdb.exe -o -T filer -k 1 -J vserver.cluster -j 192.168.10.130

> configdb.exe -o -T filer -k 4 -J vserver.cluster -j 192.168.10.130

• Allow at least two minutes for the change to replicate to the collector node
   
  • To confirm the configuration change has been replicated successfully, compare the \DataInsight\data\conf\config.db.### files are the same name/version (file extension) between the Management Server and collector nodes.
     
• Login to the DI Console and navigate to Settings – Inventory – Data Insight Servers – – Services
   
• Select the DataInsightFpolicyCMod service and click the Configure button.

To confirm the changes are successful, review the fpolicycmod.log and netapp_util.log on the collector node.

Each log will record the IP address when connecting to the cluster and should show the new address.