|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||HP Operations Manager||Recommended Links||node groups||Layout groups||Message groups|
|Policies||Default Policy Groups||Policies troubleshooting||Documentation||Humor||Support Forum|
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 :-)
Node in HPOM is a computer with the agent installed or computer with SNMP installed that sends information to HPOM manager. Different types of nodes managed by HPOM are brought into the configuration, including
Controlled— Agent installed and allows remote logins, actions and monitoring.
Monitored— Agent installed but does not allow remote logins or remote actions.
Message allowed— No agent, node sends SNMP traps (for example, router or printer).
Disabled— Node is not monitored for status, sends no messages.
External nodes— Only send events via SNMP that will be processed and transformed into HPOM messages. These are referred to as nodes for external events inside the GUI.
root@unlab12:/opt/OV # opcnode -list_nodes List of all Nodes in the HPOM database: ==================================================================== Name = unlab12.rockaway.firma.com Label = unlab12 IP-Address = 10.194.146.2 Network Type = NETWORK_IP Machine Type = MACH_BBC_LX26RPM_X64 Comm Type = COMM_BBC DHCP enabled = no (0x22) ==================================================================== Operation successfully completed.
HPOM does not create nodes automatically. You must add the desired node to the Node Bank first.
If the node is fully managed, a Node Configuration window appears and waits for you to verify the default settings or make changes. After you click OK, the information about the node is stored in the database. The node is not yet installed with the agent software; you will perform this task after the node configuration is complete. If the node is only sending events to HPOM in the GUI, use the Add Node for External Events window. Although the GUI method is described here, there are commands to accomplish the same tasks.
There are several methods to add nodes to the Node Bank. (Refer to the HPOM Administrator's Reference, Volume I for more detailed information.) Examples of the process to add nodes to the Node Bank are shown here for reference. Each example assumes that a selection is made from the menu.
Example 1: Actions→Node→Add
This method is ideal for installing one node at a time. You need to provide the hostname of the node you want to add. HPOM then attempts to determine additional attributes (IP address, system type, and so on) by querying the node's SNMP agent. If an SNMP agent is not running on the managed node, you will need to set the machine type manually in the configuration window.
Example 2: Edit→Copy
Locate the node in the root map, by selecting Edit→Find→Object by Selection Name (or some other attribute; see the list in the Selection Window). Once you have identified the node, select the node, and from the menu select Edit. In the HPOM Node Bank, select the menu item Edit→Copy. The new node appears in the Node Bank. A drag/drop from the ipmap would also work to add the node to the Node Bank.
Example 3: Open the Node Group Bank, double-click with the left-mouse button on a node group icon, and then select from the menu, Actions→Node→Add
This is similar to Example one, just a different menu location. Add a new node to the node group and it will automatically appear in the Node Bank (Holding Area). Here you could also use the Menu option Edit→Copy, Edit→Paste. Node Groups are covered in more detail in Section 13.9.2.
Example 4: Actions→Node→Add for External Events
Use this method for managing devices that typically do not have the HPOM agent installed but are capable of sending their events to a node that does have an HPOM agent (a proxy node) or directly to the server. When the event arrives on the managed node, it is transformed into an HPOM massage and sent to the server. A use case is to manage SNMP devices like routers, bridges, network printers this way. The external events icon changes status as the messages from the external nodes are processed on the server. When the window “Add Node for External Events” opens, provide a label name for the icon in the GUI.
Select the Network Type, IP-Addr, IP-Name, or Others. This determines what type of entry you will use in the Node Pattern field. For example, if you use IP addresses in the Node Pattern Field, select IP-Addr. Provide a Node Pattern, which is actually a node name pattern (such as *.hp.com). The Node Pattern field can contain wild cards for the IP address range if there are many nodes on one a network that will send events to the server (i.e. 192.14.*.*). Other options for the address range can include and exclude specific IP numbers (i.e. 192.14.123. <5 –le [<#>] –lt 72>. Finally, select the Type of Node, Message Allowed (in order to enable the events from the external node(s) to appear in the browser). The external node icon is located in the node bank with the other node types as shown in Figure 13-7. Configure the external device to send SNMP events to the HPOM server.
Example 5: Upload the node configuration from the command line.
Example 6: Command line method, see the man page for opcnode.
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.
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-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.
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: October 11, 2015