- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Configure Agent
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2006 02:52 AM
тАО10-30-2006 02:52 AM
Configure Agent
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..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2006 06:26 AM
тАО10-30-2006 06:26 AM
Re: Configure Agent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2006 09:06 PM
тАО10-30-2006 09:06 PM
Re: Configure Agent
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2006 07:29 AM
тАО10-31-2006 07:29 AM
Re: Configure Agent
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2006 08:13 AM
тАО10-31-2006 08:13 AM
Re: Configure Agent
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2006 08:31 PM
тАО11-01-2006 08:31 PM
Re: Configure Agent
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