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

HPOM Backup Server and Server rotation

News HP Operations Center Recommended Links Banal Corporate Idiotism of HPOM developers Server Installation Configuration Reference
Troubleshooting Troubleshooting agents Server Health checking Checking the Processes Log Files opcmsg opcmon
Agents agent installation via ssh Installation from local files Deinstallation of agent Adding nodes Agent patching Nodes
node groups Layout groups Message groups Policies Server rotation Event Correlation SiteScope - Operations Manager integration
Certificates management Logfile Encapsulation Server patch Installation Migration from Tivoli TEC Terminology Humor OpenView Support  Forum

The relationship between the management server (the primary server) and the managed node is extended to other servers that will have responsibility for the node in the event of a primary server failure. The backup server should be installed following the standard OpenView Management server procedure.

In larger environments, multiple management servers become essential. The advantages include minimized use of network bandwidth for message transmission between the agents and servers, configuration of nodes within a specific region to report to a regional server, message forwarding and configuration control between multiple servers.

OpenView Failover Concepts

If a failover or takeover becomes necessary it means that the primary server where the node normally sends its messages is no longer available to receive information from its managed nodes. A surrogate server must assume responsibility for the nodes. When the primary server is available, it must resume responsibility for the managed nodes. Therefore, both servers including the primary and all secondary servers must maintain consistent configurations to minimize the time it takes to failover and failback.

1. Configure the management responsibilities (authorization) file called allnodes. Next, install and configure the backup server. Distribution of the all nodes file is final step prior to testing the setup.

2. Download the configuration data. In the GUI, select Action→Server→Download Configuration.

3. Install the backup server.

4. Distribute the downloaded configuration data to the backup server with the command opcmgrdist.

5. Stop all services on the backup server with ovstop opc.

6. Upload the configuration data to the backup server with the command opccfgupld.

7. Start the services on the backup server with ovstart opc.

8. Distribute the allnodes file and test the backup server. Switch to the backup server using the command on the backup server, opcragt –primmgr <node_name>.


Top Visited
Past week
Past month


Old News ;-)

Switch management server from OMW to HPOM in case OMW failure


I am having two management server architecture and out of which Operation Manager for Unix acts as Manager of Managers which receives alerts from OMW, NNM, BAC etc. and other management server is OMW which monitors servers and applications.

I want to forward all alerts to HPOM from OMW in case OMW services goes down or OMW server is not available.

Solution -
To achieve above target, perform following actions -

(1) Create a failover policy in OMW.
Failover policy would of type Flexible Management Policy with following content -

# Configuration file
# defines two action-allow managers
# messages are always send to the primary manager
DESCRIPTION "responsible mgrs for Nodes in VAA"
#Secondary managers have to be specified,
#but this section is not used by OpenView Operations for Windows
DESCRIPTION "HP OpenView Operation for Unix Management Server"
DESCRIPTION "HP OpenView Opearion for Windows Management Server"
DESCRIPTION "HP OpenView Operation for Unix Management Server"
DESCRIPTION "HP OpenView Opearion for Windows Management Server"
# Recommended: include the primary manager into the list of action-allow managers
# even if all possible managers are already listed
DESCRIPTION "current primary manager"
DESCRIPTION "always send all messages to current primary manager"

(2) Deploy the policy on all of the managed nodes

(3) When you want to switch management server from OMW to HPOM , run following command on HPOM server :
opcragt -primmgr

Wait till the command execution completes and check whether command is executed succesfully. If it goes successful then management server switching is done.

(4) If you want to revert the management server back to OMW then issue the same command on OMW server :
opcragt -primmgr


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 quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard 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 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. 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 is down you can use the at


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