Unable to add a system in NetApp OnCommand System Manager

[GazouGazou]

Hello,

Following a reinstallation of the OnCommand System Manager on a new management computer, it is not possible for us to add and manage our NetApp FAS2552. The management IP of our NetApp cluster_mgmt no longer responds to us to ping.

We would like to restart our data vserver but we are afraid of the consequences because VMs are running on this NetApp. We are in version 9.0.

We are unfamiliar with NetApp systems and now only have ssh access.

Could someone help us knowing that we can't reboot the device and we don't have the availability to move these VMs somewhere else?

Thanks in advance and have a great day.

Sorry for my english.

[James_Huang]

The NetApp OnCommand System Manager is used for the ONTAP 8 7-Mode system. However, you mention that your storage is ONTAP 9.0.  So the ONTAP 9 cluster has the management IP, but can not ping. How about the node management IP? can you ping the node management IPs?

If can ping the Node management IPs, you can just HTTP it or ssh it directly.

If donot know the Node management IPs, you have to use the node SP IPs to manage it.

If donot know the SP IPs, you have to use the console to log in to the storage.

Refer to:

Access the system console of a node

https://docs.netapp.com/us-en/ontap/system-admin/access-system-console-node-task.html

Accessing a cluster by using the ONTAP System Manager browser-based graphic interface

https://docs.netapp.com/us-en/ontap-sm-classic/online-help-96-97/task_accessing_cluster_by_using_system_manager_brower_based_gui.html

[GazouGazou]

Hello,

Thanks a lot for your help.

We can ping the 10.0.0.51 and 10.0.0.52 IP but not the 10.0.0.50

In http we can only access to 10.0.0.51 and 10.0.0.52 with some parameters like /SPI,...
Before our problem, we managed the Netapp (disk, lun, system, raid,...) via http on the 10.0.0.50. The IP actually in fault.

Thanks again!

[Ontapforrum]

From the screenshot I see the 2nd colum indicates 'Is Home', is "false" for this clust_mgmt LIF "10.0.0.50". That could be the reason. Simply rever it back to the 'home/true' where it was before.

::> network interface revert -vserver *NACLUS00 -lif cluster_mgmt

If that doesn't solve the problem, check if there is a Duplicate IP on the network that has the same IP as the Cluster-mgmt lif.

Also, If you are totally unfamiliar with the NetApp stuff, then it may be a good idea to engage a NetApp resource, as you have production stuff running. In general, NetApp can failover safely provided it is configured as per best practices.

[GazouGazou · Accepted solution]

Thanks a lot !
Before trying the network interface revert we just made a network interface show to know the port interface for cluster_mgmt. then on the NetApp, we've just unplugged and plug the cable inside (it was already blink before) and all works fine!
And for your information the IsHome status passed to true after that.

Thanks again for your help!