- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Name Resolution Hell
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-13-2007 11:10 AM
тАО10-13-2007 11:10 AM
Name Resolution Hell
I am running SIM 5.1. We have hundreds of unknown and unmanaged devices which show up as IP only. Now, I know the name for most and figured out how to add the systems via mxnode. Adding the systems via the mxnode command works great. The systems are added, and the IP updates to the server name. Problem is, on discovery, the name is whacked and the system reverts back to IP.. LOL
Any workaround to this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2007 12:02 AM
тАО10-14-2007 12:02 AM
Re: Name Resolution Hell
Configure/Repair Agent will do the trick;
Regards,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2007 04:02 AM
тАО10-14-2007 04:02 AM
Re: Name Resolution Hell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2007 04:30 AM
тАО10-14-2007 04:30 AM
Re: Name Resolution Hell
May be I am wrong.
Regards,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2007 07:32 AM
тАО10-14-2007 07:32 AM
Re: Name Resolution Hell
As for the "Unknown / Unmanaged" these can be resolved by SNMP in most cases to get you started. UnManaged means HPSIM hasn't been able to see any protocol it can use to interrogate the server, UnKnown means it found a protocol but couldn't use it - e.g. snmp but the HPSIM Server wasn't an allowed host or the community name was wrong.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2007 01:01 AM
тАО10-15-2007 01:01 AM