2012-05-23 08:39 AM
recently I wanted to work with the configuration management offered by OnCommand Core / Operations Manager and pulled a configuration file from a controller running ONTAP 8.1. When editing the configuration file via Operations Manager I figured out that not all options available via CLI are included (e.g. cf.takeover.on_reboot).
Are some options intentionally hidden? Or are these options simply missing in the OC Core's template for ONTAP 8.1?
2012-08-07 08:06 AM
Bumping your question because of the following:
2 was answered in my other post. SFTP is not available in 8.0.x.
2012-08-07 10:10 AM
There are bugs reported on the NetApp Site about system manager, if you make any changes to rc, config files, they may get corrupted and screw up your environment. Please make sure to use the cli interface.
2012-08-07 11:50 AM
We're referring to Operations Manager AKA DFM, not Systems Manager.
For the record, i reported system manager causing /etc/rc and /etc/hosts file corruption late last year. It was easy to replicate the issue even from a clean install of windows and yet, doesn't show up as a bug until now... bad bad bad. There's also a corruption issue while using ssh to connect to RLM port to paste a config file using wrfile.
2012-08-09 05:43 AM
- why are /etc/rc and /etc/hosts not included?
The general idea of Config Mgmt is to have standards for value that are common and can be shared. But in case of rc and host files there inst much to share. Esp in case of rc file its the ip address of the filer which will be different for all filers, so there inst much to share. Similary in case of host file its contains the IP and dns names which are different for each filer.
Can you explain me what is that you are looking to do by doing config mgmt of file or options which needs to be specific to each filer
2012-08-09 08:53 AM
I understand what you're saying. The problem is that NetApp offers no method(that im aware of) to check and/or verify /etc/rc and /etc/hosts file health, history and comparison with it's HA pair.
At least 80% of our failed fail-over attempts have been due to misconfigured /etc/rc and /etc/hosts files. After multiple failures I've had to make it a habit to manually compare those two files between HA pairs prior to a maintenance, which doesn't just consist of comparing between the pair, but verifying all active interfaces, vifs etc.. exist in the rc file.
Also, I actually have matching /etc/rc files between HA pairs (minus the hostname). So matching configs between the two is absolutely critical in my environment.
OnCommand Config Mgmt just seems like a fitting place to offer some historical and automated checks between HA pairs... Perhaps this should be a separate function in config mgmt and not built-in to what already exists. Maybe an additional area called HA or HA Pair Config Management? If it could be intelligent enough to check that a filer's active configuration exists in /etc/rc and /etc/hosts that would save us a LOT of headaches. It could also help restore faith in System Manager... when it's fixed.
I imagine a good comparision check could work like this:
I did have time to review my post, let me know if this doesn't make sense.
2012-08-09 09:02 AM
I have config advisor installed and only recently began using to check filer health. I remember something about checking config files but a quick glance at it and i dont see any mention of /etc/rc or /etc/hosts... something in 3.0.1 maybe?
2012-08-09 09:27 AM
What you are really looking for is for Cluster(HA) Configuration checker. You could either do this using the Check Configuration OnCommand/DFM or a better and more enhanced tool is wire gauge. Attached is screen shot on OC from where you can do this.