• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2499
  • Last Modified:

NetApp: Cluster Failover and Rebooting

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
pzozulka
Asked:
pzozulka
3 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
 
Paul SolovyovskySenior IT AdvisorCommented:
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
 
robocatCommented:
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
 
Paul SolovyovskySenior IT AdvisorCommented:
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
 
pzozulkaAuthor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now