Querying for a particular type of lock mgr is confusing to users. Don't do it. Instead, if there are more than 16-nodes configured, use gulm otherwise, stick with the DLM. Customer had no clue what quorum votes meant when adding a new node. Don't ask for quorum vote - always assume that it is one. If they are that smart that they think they need to change it, they are smart enough to hand-edit the config file.
Don't ask to create a new fence level. Just ask for how the node is connected. In other words, clicking on "Manage fence for this node" should bring up a window in which you can "add a new fence to this level" instead of "add a new fence level". You are not letting them choose the method name anyway... You may ask what to do about dual ported nodes... A type will have to be associated with the fence devices so that you can group proplerly. (I.E all power ports would go in one method, all fabric connections would go in the next, etc) This shields the user from having to understand the fencing heirarchy
I agree with Jon, there is no intuitve way to figure out how to configure fencing. If I click "Add a new fence level", that is all it does and if I continue to do that, it will just create a bunch of (meaningless to the user) level "icons" until I somehow figure out that I need to click (highlight) the created "Fence-Level-*" icon then go back and click the EXACT same "Add a new fence level" which now does a completely different task to in bring up the "fence properties" window.
Very good insight. Deferring for future release