|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||HP HPOM Policies||Recommended Links||Reference||Version Management||Comparing Policies|
|Creating and Uploading Policies||Listing policies installed on the node||Removal of policies||Assigning Policies||Deploying Policies||How to find out which policies are associated with the particular node|
|Policy Groups||Default Policy Groups||node groups||Layout groups||Message groups||Policy Files Naming Conventions|
Policies can be assigned to nodes, node groups, and policy groups.
You can assign policies and policy groups to managed nodes and node groups by using the opcnode command-line tool. The process of assigning a policy group to a node is the same as the process you use to assign a single policy. All nodes within a node group automatically inherit the policies and policy groups assigned to the node group. This inheritance simplifies assigning policies to new nodes. For example, you can assign a policy group to a node group by using the following command:
opcnode -assign_pol_group pol_group=In this command,
NOTE HPOM assigns and distributes policies individually. If only one policy in a policy group is changed, HPOM redistributes only the changed policy. If a policy is assigned several times to the same node through different policy groups, the policy is distributed and handled only once on the managed node. While policies are being modified, they are locked and cannot be distributed. You can verify the status of policies, and their assignment to managed nodes, by generating a report. For details about available reports, see the HPOM Administrator’s Reference.
After you have configured policies and policy groups, you need to determine which node or node groups should receive the new policies. You can assign policies to nodes or node groups by using the opcnode command-line tool. Or you can assign policy groups to nodes or node groups where the message interception should be performed. Then you can distribute the new configuration.
Policies can be assigned to policy groups using the opcpolicy command and to managed nodes using the opcnode command, as follows:
Policy assignment to a policy group:
# opcpolicy -add_to_group group=<policy_group> \ pol_name=<policy_name> pol_type=<policy_type_name> version=<policy_version>
Policy assignment to a node:
# opcnode -assign_pol pol_name=<policy_name> \ pol_type=<policy_type_name> version=<policy_version> node_name=<node_name> net_type=<node_network_type>
You can list policy types by using the opcpoltype -list command.
To remove policy assignments, use the following options:
• opcpolicy -del_from_group
• opcnode -deassign_pol
To list the contents of a policy group, use the opcpolicy command as follows:
# opcpolicy -list_group pol_group=<policy_group_name>
To retrieve a list of policies assigned to a managed node, use the opcnode command as follows: # opcnode -list_ass_pol node_name=<node_name> \ <net_type>=<node_network_type>
Example of assigning a policy to a policy group: opcpolicy -add_to_group pol_name="Test policy" \ pol_type=Logfile_Entry version=1.0 pol_group="Test group"
Example of assigning a policy to a managed node: opcnode -assign_pol pol_name="Measurement policy" \ pol_type=Measurement_Threshold version=1.2 \ node_name=remote.hp.com net_type=NETWORK_IP
For more information about the parameters and options available with the opcpolicy and opcnode commands, refer to the opcpolicy (1M) and opcnode (1M) reference pages.
This also means that the existing assignments point to the older policy version, and not to them modified one. Therefore, the assignments must be updated.
The updateof the assignments can be done automatically. HPOM 9.0x introduces three assignment modes, namely FIX, LATEST, and MINOR_TO_LATEST.
You can specify the assignment mode by using the opcpolicy and opcnode command line utilities.
Refer to the opcpolicy (1M) and opcnode(1m) reference pages for usage details.
Policies can be assigned:
Policy assignment to a policy group:
# opcpolicy -add_to_group group=<policy_group> \pol_name=<policy_name> pol_type=<policy_type_name>version=<policy_version>
Policy assignment to a node: #
opcnode -assign_pol pol_name=<policy_name> \ pol_type=<policy_type_name> version=<policy_version>node_name=<node_name> net_type=<node_network_type>
You can list policy types by using the opcpoltype -list command.
To remove policy assignments, use the following options:• opcpolicy -del_from_group• opcnode -deassign_pol
To list the contents of a policy group, use the opcpolicy command asfollows:# opcpolicy -list_group pol_group=<policy_group_name>
To retrieve a list of policies assigned to a managed node, use the opcnodecommand as follows:#
opcnode -list_ass_pol node_name=<node_name> \ <net_type>=<node_network_type>Example of assigning a policy to a policy group:opcpolicy -add_to_group pol_name="Test policy" \pol_type=Logfile_Entry version=1.0 pol_group="Test group"Example of assigning a policy to a managed node:
opcnode -assign_pol pol_name="Measurement policy" \pol_type=Measurement_Threshold version=1.2 \node_name=remote.hp.com net_type=NETWORK_IPFor more information about the parameters and options available withthe opcpolicy and opcnode commands, refer to the opcpolicy (1M) andopcnode (1M) reference pages.
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