- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: System names not identified
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
тАО03-13-2007 09:44 PM
тАО03-13-2007 09:44 PM
About 20 (of 1000) of my servers do not pick up the system name in HP SIM. Instead it uses the IP address.
The servers are proliant DL360 G4 windows 2003 sp1. As far as i can see they are configured the same way my other servers are.
They pick up all the other information i.e. serial#, model,platform etc.
How does name resolution work in HP SIM?(i know how it works in windows)
Could this have anything to do with my Teamed NICS configuration. The servers were created from a ghost image.
Thanks
Andrew
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 02:18 AM
тАО03-14-2007 02:18 AM
Re: System names not identified
In you 're profile you have 5 asked questions in the past,but no points applied,most of the people here help people that give out points,since you gave out 5 asked tread, zero points, alot of people will not help when people will not aply point ,you will get more help when you do.
Have a nice day.
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 02:37 AM
тАО03-14-2007 02:37 AM
Re: System names not identified
Thanks
Anderw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2007 07:59 AM
тАО03-16-2007 07:59 AM
SolutionGhosting sometimes puts a unique identifier in the registry, if I remember correctly.
(Do a search in the forums and you will probably find the thread). This could be confusing Insight.
Another thing that causes this is servers with multiple IP addresses, like web servers.
What I do in this case, is delete the systems listed by IP, then do a manual discovery using the system name. Then you can edit the properties of that system so Insight does not change the name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2007 08:10 AM
тАО03-16-2007 08:10 AM
Re: System names not identified
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2007 08:14 AM
тАО03-16-2007 08:14 AM
Re: System names not identified
You might check DNS. It could be a corrupted entry for those servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2007 08:16 AM
тАО03-16-2007 08:16 AM