Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Actions

News Policies Recommended Links Conditions Regex/Patterns used in conditions Message Keys
 Policy variables Deduplication Automatic acknowledgement Condition Matching Optimization 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 :-)

HPOM/ HPOM provides several options for responding to messages that match conditions. Operators use some of these options in Message Browser to respond to messages. Some of these responses are transparent to operators. You may configure an application or script to run as an automatic action, operator-initiated action, or scheduled action:

Actions are always performed by the HPOM action agent, which operates as root on UNIX systems, as HP ITO Account on Windows systems. To be executed, the action must be available on the managed node on which it is expected to be executed (which can be different from the node on which the event originated). The applications must be accessible iether via the $PATH settings of the root (Unix)  or  path to it must be fully qualified

You can choose from the following response types:

As a general rule, in instructions, you enter details about the operator-initiated actions, so operators know what exactly will be executed when the operator-initiated action is started. Normally, an operator-initiated action requires some kind of operator interaction. Or operators must set up or verify some type of prerequisite. Examples: You can forward messages to a trouble ticket system or external notification service. In addition, you can configure automatic acknowledgments after forwarding a message. Configuring Automatic Annotations and Acknowledgments For both automatic and operator-initiated actions, you can configure automatic annotations and automatic acknowledgments. An automatic annotation logs the following: If an action fails, an annotation is automatically written. When you configure an automatic acknowledgment for an action, the message is acknowledged automatically if processing of the action was successful. Without automatic acknowledgment, operators must manually acknowledge messages in the Java GUI Browser.

Operator Actions in Java GUI

This is a diffirent animal then actions in messages, but the key idea is the same. All applications are available for direct use or for assignment to operators in the Application Bank. The Application Bank's  represent set of Application Groups, each in turn is a collection of applications.

This resource area contains symbols that represent categories of tools that are readily available for use. The tools are represented by symbols arranged in a hierarchy starting with a top-level represented by oval shaped symbols, called application groups (oval-shaped symbols)

If you double-click on the icon, you'll find that the second level contains specific tools for that application group category.

The leaf level of the Application Bank contains square-shaped symbols that are executable. Drag and drop the node onto the application to launch the program. Double-click with the mouse on the application group icon to move to the second level of the hierarchy.

The symbols at the second level could represent additional Application Groups within this category if the symbol is oval. There are also square icons, which are ready for use and only require a drag/drop operation, as previously described.

The applications icons are embedded with program instructions that execute programs on the specific node or on the management server. For example, to check the status of a node, drag and drop a managed node symbol from the Node Bank onto the square symbol in the Application Bank called ITO Status. This task executes the command opcragt –status on the HPOM server and returns the results to the operator console in a separate window.

Customized application techniques are covered in more detail in the User Guide.


Top Visited
Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News

[Jan 24, 2011] MOM HPOM to OMW node Action Allowed not working

IT Resource Center forums

Bill Collyns
Nov 19, 2009 16:34:11 GMT

--------------------------------------------------------------------------------
I have configured our OMW 8.10 nodes with agent version 8.6.006 to allow actions from our HPOM 8.31 server.

I received the following error;

automatic action failed at 11:08:16, 11/19/09.
Result : -1

Output :

Didn't execute automatic action "ovc -status coda" on node my-inf-rep01.mycompany.com.
Network communication problems occurred.

Also when I attempt to do an opcragt from the HPOM server I get the following;

#sudo opcragt my-node
Node my-node.mycompany.com:

Cannot get status information from node my-node.mycompany.com. (OpC40-428)
Network communication problems occurred. (OpC40-427)

-------------------------------------------------------------------------------
CTRL - CommunicationException:
-------------------------------------------------------------------------------
(ctrl-21) Communication error when executing 'Status' method.
(bbc-49) The HTTP server failed authentication. The server's target ID 'f767f7e2-68e9-7540-14fd-e5c3a78204f7' is not specified in the target ID list: ' 000000000000000000000000000000000000 '. (OpC40-2130)
Probably there's a mismatch between the core ID for the node in the
OVO DB and the core ID set on the node. On the OVO mgmt server check with
"/opt/OV/bin/OpC/utils/opcnode -list_id node_list=<managed_node>"
on the managed node check via command "ovcoreid". Correction on OVO server
via "opcnode -chg_id node_name=<managed_node id=<managed_node_core_id>" (OpC40-2170)
Failed.


When I update the core id I get the following error;


#sudo opcnode -chg_id node_name=my-node id=f767f7e2-68e9-7540-14fd-e5c3a78204f7
Operation successfully completed.
itd_op@ovopvm1 [/home/itd_op]
#sudo opcragt my-node
Node my-node.mycompany.com:

Cannot get status information from node my-node.mycompany.com. (OpC40-428)
Network communication problems occurred. (OpC40-427)

-------------------------------------------------------------------------------
CTRL - CommunicationException:
-------------------------------------------------------------------------------
(ctrl-21) Communication error when executing 'Status' method.
SoapFaultException:
faultcode: ctrlauthorization
faultstring: Authorization failed (OpC40-2130)
Probably the OVO server isn't authorized to access the node.
Check whether the server's core ID (on server call "ovcoreid -ovrg server")
is mentioned on the node in the MANAGER_ID setting or in the mgrconf policy
(on the node call "ovconfget sec.core.auth MANAGER_ID" and look
into the file $OvDataDir/datafiles/policies/mgrconf/*_data (if any)). (OpC40-2173)
Failed.

Has anybody else run into similiar problems.

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


Sort Answers By: Date or Points


Bill Collyns Nov 19, 2009 16:57:10 GMT N/A: Question Author

--------------------------------------------------------------------------------
Further testing produced this result.

There was a problem running an action
after the communications link was established.: Execution of API call failed. Error code: Access denied. (ITO210-131)
Can't start operator initiated action for message 'c6ef9d40-d529-71de-19e1-aa3f0b190000'. (ITO219-1)

Goran Koruga Nov 20, 2009 06:00:03 GMT 5 pts

--------------------------------------------------------------------------------
Hello.

You need mgrconf policy on the node so that it allows actions from another server.

For HPOM you can find examples here:

/etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs

Regards,
Goran



Etc

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 Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D


Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) 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 to buy a cup of coffee for authors of this site

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 Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. 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.

Last modified: March 12, 2019