- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- System Address Incorrect
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
Forums
Discussions
Discussions
Discussions
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
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
06-09-2005 02:44 PM
06-09-2005 02:44 PM
When I click on Server A for System Page, the address listed there 1.1.1.1 and 2.2.2.2.
I did a NSlookup at the CIM server, there is no problem. i.e Server A - 1.1.1.1 and Server B - 2.2.2.2.
Is it due to the corrupted data in the HPSIM database?
How can I clean it up?
Hope to hear from you guys soon...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2005 10:41 AM
06-12-2005 10:41 AM
Re: System Address Incorrect
Try doing an nslookup of the IP Address from the CIM Server, not the name.
It will be this way round that HPSIm will equate the name.
You could delete the devices and try to re-discover them, but typically this would be a DNS issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2005 09:32 PM
06-12-2005 09:32 PM
Re: System Address Incorrect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2005 07:56 AM
06-13-2005 07:56 AM
Re: System Address Incorrect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2005 08:24 AM
06-13-2005 08:24 AM
SolutionSolution
Delete and recreate a Unique GUID for the Insight Agent Host in the registry. In order to do this follow the instructions below:
1. Stop the Foundation Agents Service
2. Start/Run/Regedit
3. Goto HKEY_Local_Machine
4. Select the Software\Compaq Insight Agent folder and locate the hostGUID
5. Select and delete the value hostGUID
6. Restart the Foundations Agents Service.
When the Foundation Agents restart a unique Host GUID is created.
Then delete and rediscover the servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2005 08:38 AM
06-13-2005 08:38 AM
Re: System Address Incorrect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2005 03:14 AM
06-21-2005 03:14 AM
Re: System Address Incorrect
I did a nslookup from the cim server using the ip address. Its the same.
I've done many times of delete and rediscover of the servers, but still the same problem.
Joel,
Indeed, both the two servers are having the same hostGUID. I've done what you have guided and both servers now have its own unique hostGUID. However, when I delete and rediscover the servers, its still the same.
(Maybe I did that too fast, not sure if needs to wait a while before delete and rediscover)
In the end, I've got tired of troubleshooting this problem, I added a secondary ip address to one server and using this ip to rediscover. Then the problem resolves....