Solved

NetApp: Cluster Failover and Rebooting

Posted on 2013-06-29
5
2,210 Views
Last Modified: 2013-06-30
Our company just moved to a new building so I had to shutdown our NetApp and VMware Infrastructure. When I was shutting down the NetApp (FAS2240), I issued CF disable command. When I brought the NetApp back up, I forgot to issue CF enable, and just left. I then started getting phone calls when the other engineers started to turn ON the ESXi hosts saying all the VMs say they are inaccessible. The host configuration, under storage showed only local storage, and could not detect the NetApp NFS volumes. I could not confirm this myself, because I was not there.

When I cam back, I issued the CF enable command, and so far, things are looking OK, and I was able to boot up several VMs, and am able to see NetApp volumes in VSphere.

Is it possible that the "CF enable" command is necessary before turning ON the VMs? If so, why?

Thanks.
0
Comment
Question by:pzozulka
5 Comments
 
LVL 118

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE)
Andrew Hancock (VMware vExpert / EE MVE) earned 166 total points
ID: 39286523
It would appear that when you failed over the cluster NetApp heads, the ESXi servers did not have access to the NFS datastore (NetApp volume/lun/export) on the other clustered node until you failed back (e.g. giveback).

So how is your NetApp filer heads configured? usually, the other NetApp clustered head (passive controller) would take over the IP Address of the other filer, so although there would be a small hiccup in access, NFS access would continue.

In your case, when you failed over, (takeover), the other head did not impersonate the other head, and hence you had an outgae, until you gaveback the resources.
0
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 334 total points
ID: 39286759
If both controllers are up and running "cf enable" is not needed to run.  

How did you configure the interfaces for the controllers?  If you had used OnCommand System Manager there is a known issue that corrupts the rc file if you don't use command line, it manifests itself after reboot.
0
 
LVL 21

Expert Comment

by:robocat
ID: 39287077
The only way to know exactly what happened, is to study the system logs on each node. Look for any errors that point to configuration problems. Look closely at the log entries at the time you issued the cf enable.
0
 
LVL 42

Accepted Solution

by:
paulsolov earned 334 total points
ID: 39287163
BTW, the correct way to do reboot each controller non disruptively is to use "cf takeover/cf giveback"  otherwise you'll lose the resources on the node.  cf takeover allows you to reboot each controller at a time without disruption
0
 
LVL 8

Author Comment

by:pzozulka
ID: 39288419
Hmm...not sure what happened then..I probably should have checked to verify that the ESXi hosts were not seeing the NetApp before issuing the CF ENABLE command, because the way I did it made it seem as if that was the magical fix since right after that I logged into VMware and was able to see the NetApp volumes.

paulsolov:
Since this was a company move, we had to shutdown the NetApp entirely for several hours, so "cf takeover/cf giveback" was not an option. But thanks for the tip, as it might come in handy in the near future.
0

Featured Post

Give your grad a cloud of their own!

With up to 8TB of storage, give your favorite graduate their own personal cloud to centralize all their photos, videos and music in one safe place. They can save, sync and share all their stuff, and automatic photo backup helps free up space on their smartphone and tablet.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now