HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- System Name problems
Server Management - Systems Insight Manager
1833792
Members
2195
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-10-2004 09:35 PM
03-10-2004 09:35 PM
System Name problems
I have snmp devices that do not resolve to a system name. The IP address floods the System Name field. There seems to be no way to change the system name once it has been discovered. I have made DNS entires and host file entries after which I can ping the device by name but doing another discover continues to place the IP address in the System Name field. Any suggestions would be helpful.
nslookup is working for those systems on CMS.
The servers are registered on another DNS server. DNS-Server is added in TCP/IP settings.
nslookup is working for those systems on CMS.
The servers are registered on another DNS server. DNS-Server is added in TCP/IP settings.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 10:11 PM
03-10-2004 10:11 PM
Re: System Name problems
From the CMS use nslookup to make sure you can resolve IP to name AND name to IP. The only place hpSIM gets name information is from DNS. If it can't resolve there is no other place to look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2004 05:59 AM
03-11-2004 05:59 AM
Re: System Name problems
Just to backup David, name to IP translatetion is not enough, nor is just IP to name, you have to have both for HPSIM to correctly identify the device.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2004 06:27 PM
03-14-2004 06:27 PM
Re: System Name problems
Thanx, that's looks to be the problem.
IP to name working. Name to IP not functioning.
IP to name working. Name to IP not functioning.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP