|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
|News||HP Operations Manager||Recommended Links||Node Hierarchies||Manpage of OPCLAYGRP||node groups|
|Policies||Default Policy Groups||Message groups||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 :-)
This notion introduced around version 8 is helpful both for operators and for management of servers. It exist in addition and separately from the old notion of Node Groups.
It allow both applying some actions to the set of nodes contains in a group as well as to present hierarchical structure of the datacenter for operators. By default, all managed nodes are presented in "flat" window (Managed Nodes Window) in the Operator GUIs.
If you have several hundred nodes it is better to structure operator view either by OS or by location. For this purpose different node hierarchies can be created all rooted at specific members of Node Hierarchy view of Admin GUI. The list of root members is available from All Node Hierarchies tab in Admin GUI.
For example you can have two root members in Node hierarchy: OS_centric_view and Geographical_view
Each view can be assigned to different user profiles.
At the same time this concept introduced new types of errors. For example in operator Java GUI all layout groups are listed as a hierarchy under nodes symbol and administrators can mix them with regular node groups. So names should be different. For example you can use suffix _view for each name as in example above. The problem is that messages from a particular node will not be visible unless this node is a member of one of set of visible layout groups. This control exists is in addition to the responsibility matrix assigned to the user account directly or via profile and can easily be overlooked.
root@unlab12:/opt/OV # opclaygrp -list_node_hier List of node hierarchies: ==================================================================== Name = NodeBank Label = HPOM Node Bank Description = Node hierarchy of administrator ==================================================================== Operation successfully completed.
You can use layout groups to group the nodes and arrange them hierarchically. Layout groups can contain nodes and other layout groups creating a node hierarchy. The opclaygrp command-line tool can be used to manage layout groups and node hierarchies.
opclaygrp -add_lay_group lay_group=Data_center \
lay_group_desc="Layout group for data center" \
By default, HPOM presents all managed nodes in a single, “flat” window (Managed Nodes Window) in the Operator GUIs. When there are so many icons in a window, it is difficult to distinguish which node manages what environment. For example, in the node bank, you might have several hundred nodes in the domain and the icons appear very small. Creating Node Layout Groups lets you create a hierarchy of windows where, for example, you organize your managed nodes by location or geography, by the role these systems fulfill, or by other custom criteria. You could use the features of the window to pan and zoom or create a quick navigator window, but you could also organize the nodes inside the current window.
You can create a Node Layout Group for each physical location, department, or type of application. Drag and drop the nodes onto the Layout Group Icon.
You can also list members of Layout Groups using SQL create by Goran Koruga ( HPOM 8, list of nodes in Layout Group from CLI)
set pagesize 0 set linesize 1000 select distinct Path from ( select PARENT_ID, LEVEL || ' ' || SYS_CONNECT_BY_PATH( case h.name when ' ' then ( select nn.node_name || ' (' || n.label || ')' from opc_nodes n, opc_node_names nn where n.node_id = h.node_id and nn.node_id = n.node_id) else (h.label || ' (' || h.name || ')') end, ' -> ') || ' -> ' || (select NAME || ' (' || LABEL || ')' from OPC_NODEHIERS b whe re h.NODEHIER_ID = b.NODEHIER_ID) AS Path from opc_nodehier_layout h start with h.NODE_ID in ( select nn.NODE_ID from opc_node_names nn, opc_nodes n where nn.NODE_ID = n.NODE_ID ) connect by prior h.PARENT_ID = h.LAYOUT_ID) where PARENT_ID IS NULL order by Path;
IT Resource Center forums
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
I checked out assigning an OVO Operator multiple Hierarchies but this seems to be a non starter (and pointless if nesting works)
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.
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.
pete_p Jul 5, 2010 14:12:26 GMTsekar sundaram: Jul 6, 2010 02:46:34 GMT
Can you add nodes into multiple layout groups?
(When I try this, the nodes move from their current layout group to the new one, I need them in a few groups).
any thoughts, suggestions?
about this node layout group, the information i read:
Use this concept to pre-arrange the nodes within a window hierarchy for your operators. By default, HPOM presents all managed nodes in a single, "flat" window (Managed Nodes Window) in the Operator GUIs. When there are so many icons in a window, it is difficult to distinguish which node manages what environment. For example, in the node bank, you might have several hundred nodes in the domain and the icons appear very small.
Creating Node Layout Groups lets you create a hierarchy of windows where, for example, you organize your managed nodes by location or geography, by the role these systems fulfill, or by other custom criteria.
You could use the features of the window to pan and zoom or create a quick navigator window, but you could also organize the nodes inside the current window.
So, looks like we can add a server only in one layout group (because layout groups are just layers under the same node bank)
Nov 9, 2009 22:01:41 GMT
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here
is it possible to get a list of nodes in layout Group(s)?
opclaygrp command only provides the Layout Groups and not the nodes within them.
opcnode has no idea about Layout Groups content.
thank you in advance,
Nov 10, 2009 06:47:35 GMT Unassigned
Is this what you're after? Put the file in "/etc/opt/OV/share/conf/OpC/mgmt_sv/reports/C" directory, name it to your own liking (be sure to use ".sql" extension) and call it like so:
where <your_name> does nto include ".sql" extension.
I think I posted this once before, but can't find it now.
-starts with next line ------------------------------
set pagesize 0
set linesize 1000
select distinct Path
( select PARENT_ID,
LEVEL || ' ' ||
case h.name when ' '
then ( select nn.node_name || ' (' || n.label || ')'
from opc_nodes n,
where n.node_id = h.node_id
and nn.node_id = n.node_id)
else (h.label || ' (' || h.name || ')')
' -> ') || ' -> ' || (select NAME || ' (' || LABEL || ')' from OPC_NODEHIERS b where h.NODEHIER_ID = b.NODEHIER_ID) AS Path
from opc_nodehier_layout h
start with h.NODE_ID in
from opc_node_names nn,
where nn.NODE_ID = n.NODE_ID
connect by prior h.PARENT_ID = h.LAYOUT_ID)
where PARENT_ID IS NULL
order by Path;
Nov 14, 2008 15:16:06 GMT
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here
i have not been able to figure out to list a layout group within HPOM . we are running 8.30 on hp-ux. i have tried both opcnode and opclaygrp. please assist. points will be distributed...
Nov 14, 2008 18:14:50 GMT 6 pts
Go to you Node Bank Window. Every group in the window is a layout group. If you double click on oned of the layout group icons, it will open a new window with the contents of the layout group. For example, if you have a layout group called "PreTest", double clicking on the PreTest icon will show you the contents of the PreTest layuout group. The contents can be nodes or other layout groups.
"opclaygrp -list_lay_group -v" will show you all the layout groups in the Node Bank.
"opclaygrp -list_lay_group_rec -v" will recursively show you all the layout groups in the Node Bank.
Nov 14, 2008 18:24:52 GMT 6 pts
to list 1 layout group add lay_group= to the command, like:
/opt/OV/bin/OpC/utils/opclaygrp -list_lay_group_rec lay_group='Servers/W2k servers'
You can use '/' as level separator if you have several levels of layout groups. Put quotes around arguments that have spaces (for example a layout group like 'Win 2000 servers').
Nov 14, 2008 18:45:52 GMT N/A: Question Author
thanks for the replies!!!
Joroen and Marty,
my need is to perform this through the command line and i have found that the opclaygrp command only shows the layout groups and not the nodes within them...
am i doing something wrong or is there another way?
Nov 17, 2008 06:59:21 GMT 7 pts
My first guess was using opcnode. However, '-list_nodes' does not allow the layout group to be specified ('layout_group='xxx') according to the man page (and some quick testing).
So maybe the only option is to write an sql query and use call_sqlplus.sh (or opcdbpwd) to run the sql query. I cannot think of other useful commands...
Dec 23, 2008 15:53:12 GMT N/A: Question Author
Marty the man johnson provided some reports within the console via HPOM reports. he took the time to figure out the sql commands and we are huming
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
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 quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
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
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 DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting 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
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How 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-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. 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|
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: September 12, 2017