Adding nodes

You add node using Admin GUI or using the opcnode command line utility to add a node. It there are few nodes that it is simpler to do this operation via GUI.

Before creating a node ensure that the node host name is resolvable by name service or located in Hosts file. It's better to specify ip address explicitly

opcnode -add_node node_name=<node_name> ip_addr=<address> net_type=<network_type>
               mach_type=<machine_type>  
               group_name=<group_name> node_type=<node_type>

mach_type

mach_type specifies the machine type for a node in the HPOM Node Bank. This attribute is mandatory. If a new introduced platform is not yet known by opcnode, the platform number will be used. Machine types are defined in AgentPlatform files.

MACH_BBC_SOL_SPARC
MACH_BBC_HPUX_IPF32
MACH_BBC_HPUX_PA_RISC
MACH_BBC_WIN2K3_X64
MACH_BBC_WINXP_IPF64
MACH_BBC_LX26RPM_X64
MACH_BBC_LX26RPM_X86
MACH_BBC_WINNT_X86
MACH_BBC_OTHER_NON_IP
MACH_BBC_LX26RPM_IPF64
MACH_BBC_SOL10_X86
MACH_BBC_AIX_PPC
MACH_BBC_AIX_K64_PPC
MACH_BBC_OTHER_IP

node_type attribute specifies the type of managed node

• CONTROLLED is the default.
• NOTE: MONITORED means automatic actions will execute, however, operator-initiated action will not.
• Setting MESSAGE ALLOWEDas the node type prevents the distribution of software and instrumentation to that node.

ip_addr

ip_addr specifies the IP Address of the node in "dot" notation (for example: ip_addr=15.1.2.3). Specifying the IP address allows to use a specific IP address when adding a node with mutliple IP addresses.

 

The  heartbeat polling settings can be changed with opchbp command, for example:

opchbp -interval 0h5m0s <nodename>

NEWS CONTENTS

• 20110509 : Issuing certificate request with frontend ip - This thread has been closed ( Issuing certificate request with frontend ip - This thread has been closed, May 09, 2011 )
• 20101105 : HPOM certificate issue - Adding node via command line ( Jan 29, 2009 , IT Resource Center forums )

Old News

[May 09, 2011] Issuing certificate request with frontend ip - This thread has been closed

You can map from GUI too: if you click edit tab on requrst there is a map operation in it

Nov 22, 2005 | IT Resource Center

Ravindra
Nov 22, 2005 00:56:52 GMT

--------------------------------------------------------------------------------
Hi,

I'm using OVO 8.10 on HP-UX. I have installed windows HTTPS agent manually on windows systems which are in cluster. So when I installed Agent it is issuing certificate with backend ip which is not ping'able from my ovo server. and DNS entry has been done for these systems with frontend ip. So when I'm going to map the certificate to a node in node bank, it is throwing an error
---------opc60-1106-------------------
Could not map certificate request to selected node from node bank
Reason
Could not map certificate request to selected node. Node names are not identical

How do I change the IP Address which is coming in certificate request to frontend ip ?

Regards,
Ravindra

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

Laurie Gellatly Nov 22, 2005 16:31:51 GMT 10 pts

--------------------------------------------------------------------------------
If you really know that the mapping is OK then you can force it. From the man page for opccsa:
- map_node <hostname | CertReqID> [=<nodebank_hostname>] [-force]
This option maps the Certificate Request containing

...
-force
If the administrator wants to map Certificate Request to the
node in the Node Bank that has different Hostname as
specified in the Certificate Request itself, and if the node
from the Node Bank has empty OVCoreID field, then -force
flag has to be used for the operation to succeed. If the
OVOCoreID from the Certificate Request and that one from the
node in the database differ, the operation cannot be
completed successfully.

HTH and thanks for any points. ...Laurie:{)

Ravindra Nov 23, 2005 06:12:08 GMT N/A: Question Author

--------------------------------------------------------------------------------
Thank you very much.

Best Regards
Ravindra

Ravindra Nov 23, 2005 06:14:56 GMT Thread closed by author

--------------------------------------------------------------------------------
opccsa <Node Name|request_id>[=<nodebank_nodename>] -force

[Nov 05, 2010] HPOM certificate issue - Adding node via command line

"I tried to add the node with FQDN and it worked, it didn't throw any warning message when i added the node. "

Jan 29, 2009 | IT Resource Center forums

bobby9

Hi,

Iam trying for the first time to add nodes by command line. here are the steps which i did.,

Step 1:
opcnode -add_node node_name=<node_name> group_name=<group_name> mach_type=<machine_type> net_type=<network type>

When i execute the above command i could see the warning message as follows:

"Warning: Mismatch between node name and IP address(according to DNS) please check to whcih IP address the hostname is resolved and if that IP is resolved back to original hostname"

- I have verified the node name and IP address, DNS seems fine.

Step 2: opcragt -distrib <node_name>

Step 3: When i added the node, the certificates are not installed/trusted. I manually created the certificates and granted that certificate request from the management server by using 'ovcm'

My queries are:

- What could be the possible cases/reasons for the warning message in step 1??

- Doesn't the certificates automatically installed/trusted on nodes soon after add/distrib..?? if yes, plz provide the procedure/steps what iam missing through command line.

Thanks in Advance

Raj Stanislav Bocinec

Hi Raj, how did you checked whether your DNS is working correctly? Have you tried nslookup/nmblookup/host on both agent and mgmt server whether DNS is resolving addresses correctly? Both DNS forward and reverse translation should wokr! Good luck ;) S.

bobby9:

Thanks for responding.,

Yes, i did nslookup from both node and management server too., DNS resolution is fine.!

Stanislav Bocinec

hm, it's really strange. after granting certificate does agent work normally? or is there any problem? and how did you installed the agent? have you specified during the installation what is the mgmt & cert. server? i always use following command line syntax: ./opc_inst -srv mgmt.server -cert_srv mgmt.server or on windows nodes: cscript opc_inst.vbs -srv mgmt.server -cert_srv mgmt.server

bobby9:

Yes, After granting certificates manually, the agent works fine and commuicates with management server too!

- Do u mean that by installting the agent by ./opc_inst -srv mgmt.server -cert_srv mgmt.server which u have mentioned does installs the certificates automatically??

- Frankly speaking i didn't do the installation., this task does by another team.., they install the agent and give that to me so that i bring the server to monitoring!!

umashankar:

Hi,

- What could be the possible cases/reasons for the warning message in step 1??

One possible reason might be the case of the nodename returned by DNS lookup.....once i had faced a similar issue where nslookup used to return the hostname in Capital and i was trying to add the node using small letters...later i had to add it with the correct case to solve it.

Hope this helps

Regards, Umashankar

bobby9:

Hello,

As i said earlier., the DNS(nslookup from node and on server too) is fine I have also checked the host(/etc/hosts) file entry on the node. Not sure and looks strange to see the warning message :-O

Pradeep

Might be a silly question but thought of checking. Do you specify FQDN as nodename while using opcnode?

I am aware that there is a way where you can accept the certificate requests automatically. If you planning to use script have a look at the output of

/opt/OV/bin/OpC/opccsa -list_pending_cr -format rhost

HTH

Jeroen Peereboom :

What Unix are you using? On Solaris nslookup does not check the /etc/hosts file. Is your managed node listed in the hosts file?

Did you check forward and reverse resolution?

Maybe itochecker -5 will give some hints?

JP

bobby9:

Thanks for ur response,

Pradeep

While adding node i specify only nodename not the FQDN.

Jeroen -

Iam using HPUX - 11.11 as management server. the waring message which i was referring comes for AIX,Linux and HP-UX nodes while adding to monitoring - Yes i checked forward and reverse resolution. - man pages of 'itochecker' states that it is supported for OVO 6.x and OVO 7.x but iam using OVO 8.x - not sure whether it supports this too?

Any more investigation would be appreciated with points too :-)

Pradeep:

Can you try adding node using FQDN?

bobby9:

I tried to add the node with FQDN and it worked, it didn't throw any warning message when i added the node.

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