Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Node groups

News HP Operations Manager Recommended Links Nodes node groups Layout groups Message groups
Listing members of a node group Assigning nodes to the node group Deassigning nodes from the node group Smart Plug-Ins Object Monitoring
Policies Policy Groups Logfile Encapsulation Integrating Monitor Applications History Humor Etc

Note: HP renamed the product called now HP operations manager way too many times. Also it is very inconsistent with using abbreviations. Here we will assume that the term "HP Operations manager" and abbreviations HPOM, OMU, and OVO mean the same thing :-)

There are two partially overlapping notions is HPOM: node groups and layout groups. Node groups are older concept (layout groups were introduced in version 8 of HPOM ).

There can be special node groups that are not intended for use with responsibilities. These node groups are flagged as Invisible Node Groups and will not appear in any responsibility matrix. That can make responsibilities matrix more compact.

There are two main areas of node group usage in HPOM :

Each node node must appear in at least one Node Group. A typical HPOM configuration uses one node group per operating system, something like Linux, Solaris, HP-UX, AIX, Windows, etc.

A node can be assigned to multiple node groups. When you do not want the node in a particular node group you need to de-assign it ( but not to delete the node from the node group: big mistake).

A node in HPOM can be assigned to multiple node groups.

In order to see anything concerning a managed node, including messages about or from the node, it must be in the Node Hierarchy and at least one Node Group. In this sense node group is a logical group of nodes managed by particular operator(s).

Node groups should not be mixed with different newer concept introduced in version 8 of HPOM called layout groups. They are similar to node groups but are used mostly as the way organize the nodes for operation Java GUI. At the same time they can be used to perform operations on a group of nodes that constitute layout group. In this second role they are quite similar to node groups.

You can either use GUI or command opcnode -assign_node to assign note to a node group.

Applying Actions to All Nodes in a Node Group

After you have created a node hierarchy, HPOM provides the opcnode command-line tool, which allows applying actions to all the nodes contained in the parent group simultaneously. For example, to assign a policy to a series of nodes, specify the parent node group of the nodes you want to assign the policies to and the policy you want to assign:

opcnode -assign_pol pol_name= <policy_name>  pol_type=<policy_type> version=<policy_version> \

group_name=<nodegrp_name>

HPOM automatically assigns the policy to the node group including all nodes contained in that group.

Actions You Can Apply to All Nodes

You can apply the following actions to a managed node, the HPOM node hierarchy, and the HPOM node bank:

Actions You Cannot Apply to All Nodes. You cannot apply any of the following actions to a managed node, the HPOM node hierarchy bank, or the HPOM node bank:

Listing members of a node group

The All Node Groups page displays a list of the nodes groups deployed to the currently selected HPOM for UNIX management server. The information in the All Node Groups page is displayed in a table with the following information; note that you can click the Name column title to reorganise list of managed node groups in ascending or descending order.

Click the actions button () to display a list of the actions you can perform on the node groups in the list; click the browse button () to display a list of the node-group-configuration details that you can browse.

List of Managed Node Groups

Column Title Description
All Check boxes to allow you to select all or individual node groups on which you want to perform an action using the "Choose an action..." drop-down menu at the bottom of the table, for example: "Move to layout group...", "Assign to Node Group...", and "Delete from Node Group...".
Label Indicates the name assigned to the node-group icon in the GUI (OM for Unix only)
Name Shows the name of the managed node group. Click a node-group name to see more detailed information about the selected node group, including the nodes the node group contains. Click one of the icons next to the node-group name to display menus that allow you to view more information about the node group or perform an action on the node group. For more information about the browse and actions menus and the options they contain, see the tables below.
Node The number of nodes in the currently selected node group.
Description A brief explanation of the contents of the selected node group.
Visible Indicates if the node-group icon is visible in the GUI or hidden (OM for Unix only)
Policies Indicates if the node group has policies assigned

Typical command line operations

Pushing policies assigned to a group to a single node

There is a possibility to push policies assigned to a node group to a single node using command line. This is very convenient option for testing.

opcragt -distib -templates -instrum <node>


Top Visited
Switchboard
Latest
Past week
Past month

Old News

[Nov 06, 2010] IT Resource Center forums - HPOM - Nested Node Hierarchy

tompuk:

Hi All

Implementation: HPOM 8.30 on HP-UX (PA) 11.23

To Quote the HPOM Online documentation: "You can use the Add Node Hierarchy Bank Window to add or modify node hierarchies. To assign nodes or other node hierarchies to a node hierarchy, you can simply use OVO's drag and drop mechanism."

Now its the second sentence I'm interested in.

It does not seem possible to have a node in more than one layout group per Hierarchy. However you can create multiple Hierarchies with the same nodes in - how can these be nested as indicated by the quote above? Whenever I try Drag'nDrop it will not let me (tried copy and paste etc)

I'm trying to do this to enable operators to better use the Java console, sometimes they want to be able to choose Nodes by Datacentre, or Domain, or OS, or Application/Server role etc. But if a server can only be in one place on the Hierarchy how can they be in multiple groups?

Thanks for any help

Points Given

I checked out assigning an OVO Operator multiple Hierarchies but this seems to be a non starter (and pointless if nesting works)

Gerry Bonin:

A node will exist exactly once in each layout group hierarchy. If you don't place it somewhere in the hierarchy, it will be put into HoldingArea automatically.

That's the way it works.

Gerry

Tony Cicone:

You can create "Nodebanks" and nodes can be assigned to multiple Nodebanks, but not multiple "Layout Groups". The Node Hierarchy exists for "Layout Groups", and not "Nodebanks", so you can only have a node in one.

tompuk:

Bah - Seems like an irritating limitation. I suppose one would need something like the Configuration Value Pack to be able to achieve what I'm after?



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: August 05, 2013