HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Configure Agent

 
Ray Bell
Regular Advisor

Configure Agent

I have at least 30 agents on our in-house network and they are all set up the same and when I tried to configure the agen for two of my server I get the followingf error messages:

Server:143.61.10.164
Status: Major
Details:
Error while retrieving OS name


Server:143.61.17.10
Status: Normal
Details:
Error while retrieving OS name


Task ID of task configuring HP-UX systems: 40138
Error while retrieving OS name com.hp.mx.core.nodemanager.MxUndefinedNodeException: The name "prod1"
does not represent a node in this system.
Error while retrieving OS name com.hp.mx.core.nodemanager.MxUndefinedNodeException: The name "demo1"
does not represent a node in this system.

Why would I get this error messages on these servers? If I do a "uname -n" the names comes up with the node name. Please give some insight on what I need to do to correct this problem.

Thanks..
5 REPLIES
Rob Buxton
Honored Contributor

Re: Configure Agent

I don't know much about HPUX, but HPSIM uses DNS for name resolution.
LukaS_9
Regular Advisor

Re: Configure Agent

Hi,
do you use dns?
If not you have to insert an entry in /etc/hosts of CMS for the 2 systems.
Take care of insert hostname first.
Also, try to run this command from CMS:
mxnode -ld

Also you can try to run on the system that has problem "osinfo". This use cim, so this can help you to check if cim works fine.

regards
Luca
Ray Bell
Regular Advisor

Re: Configure Agent

No we do not use dns but I have made sure the servers was added to our local dns. The two servers are added to the /etc/hosts file on the CMS. Just like the other 30 systems and these are the only one failing. Not sure why..

I ran the commands:
mxnode -ld demo1 &
mxnode -ld prod1 and the information came back.

When I ran discover on these servers it came back with the ip address and I added the node name to the file. Would that make a different. Not sure why it did not gather the node name from the server.
Rob Buxton
Honored Contributor

Re: Configure Agent

HPSIM uses DNS and it does both forward and reverse lookups.
If you try to add by name but HPSIM cannot resolve that name itself then it will not be added.
You could add by IP Address, HPSIM would add it but the name will not display as HPSIM cannot resolve it.

LukaS_9
Regular Advisor

Re: Configure Agent

Yes, Rob has right...also the crown in his head confirms it :)
Try to run "nslookup demo1" and check if the IP returned is correct.

Sorry if I harp on mxnode command, but was the OS info correct?
In my systems I get back:
OS name: HPUX
OS revision: 11.11
OS revision text: HP-UX B.11.11 U
OS vendor: HP
....
Another consideration:
We have had a problem with system name when it is in upper case.
In fact nslookup is not key sensitive (if you run nslookup DEMO1 you'll get back the same info of nslookup demo1), but some SIM functions is key sensitive. The workaround is to change /etc/hosts setting the hostname in lower case.

let me know...I'm curious to know the end of the tale :)

Luca