Link to home
Start Free TrialLog in
Avatar of pzozulka
pzozulka

asked on

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.
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of robocat
robocat

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.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pzozulka

ASKER

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.