Tips

Use /bin/true and /bin/false for policy debugging

If you have troubles executing action scripts, especially with return codes you can debug you policy using /bin/true and /bin/false to provide success and failure, correspondingly.

Buffering Messages

Messages received during the defined service hours are passed to the Java GUI Message Browser in the normal way. All messages that are received outside of the defined service hours are buffered. The buffered messages can be viewed in the Java GUI Pending Messages browser. Unbuffering Messages Automatically

Buffered messages are automatically unbuffered (that is, moved to the Java GUI Message Browser) At the start of the next period of defined service hours. After the buffered messages are moved to the Java GUI Message Browser, they may be worked on in the usual way.

Unbuffering Messages Manually

Buffered messages can be unbuffered manually, either from the Message Properties window or from the Java GUI Pending Messages Browser itself. Messages that are unbuffered manually are owned or marked by the user who carried out the unbuffer operation.

The following restrictions apply to the manual unbuffer operation:

• Messages Sent Only When Buffer Time Has Expired Buffered messages are sent to the trouble ticket and notification interface either when the buffer time of the message has expired (that is, at the start of the next service hours of the service that generated the message) or when an operator opens the message.
• Messages Forwarded On Arrival on Management Server If manager-to-manager forwarding is configured, buffered messages are forwarded to any other defined management servers as soon as the message arrives on the HP Operations management server. Implementing Message Policies

NOTE Other managers may have their own configuration for outages and service hours.

Defining Service Hours

To find out how to set up service hours and for more information about the policies and syntax rules used to define service hours, see the HPOM

Scheduled Outages

In the context of HPOM, a scheduled outage allows you to log or suppress (delete) incoming messages during a defined period of time if the messages relate to a service or system that is known or planned to be unavailable. For example, you can use a scheduled outage to suppress all messages from a component that is temporarily unavailable for maintenance reasons.

A scheduled outage defines a planned and potentially recurring period of time in which one or more components or services in a distributed working environment are not available, and in which messages relating to these components or services need to be logged or perhaps even deleted. An outage may be set dynamically if a major problem occurs, and if further messages from a particular component need to be suppressed. For example, if an Oracle Database goes down, you could suppress, for a defined period of time, all messages that are related to Oracle. The status of an outage can also be set by an external application.

Defining a Scheduled Outage

To find out how to set up a scheduled outage and for more information about the policies and syntax rules used to define a scheduled outage, see the HPOM Administrator’s Reference.

Implementing Message Policies

You can configure service hours and scheduled outages on the management server with a policy similar to the one used to configure flexible management. The same syntax is used and, as a consequence, may be checked with the opcmomchk tool. This policy is located in /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs. For more information on the policy and the syntax used, see the HPOM Administrator’s Reference.

NOTE Scheduled outages and service hours may be configured by an external application. However, the designated external application must create the policy for outages and service hours and use the opccfgout(1M) command to control outages.

This chapter describes how to configure and manage HPOM in widely distributed environments. It also discusses the underlying concepts of flexible management and manager-of-manager (MoM) communications. NOTE In this chapter, the term “manager” refers to the management server, and the term “agents” refers to managed nodes.

• Communication Between Servers Basic concepts and sample applications behind server-to-server communication.
• Transferring Messages to Servers Configurable message transferring from managed nodes to different servers, based on time or message attributes. Changes of HPOM message attributes, for example message severity, message text, and custom message attributes can be synchronized with other HPOM management servers.
• Configuring Management Server Responsibilities Setting up management server responsibilities for the HPOM managed nodes. These responsibilities permit the full use of knowledge centers, and eliminates single-point-of-failure bottlenecks.

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 quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard 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 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

Classic books:

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 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

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