<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: System Name problems in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215739#M1607</link>
    <description>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.</description>
    <pubDate>Thu, 11 Mar 2004 06:11:10 GMT</pubDate>
    <dc:creator>David Claypool</dc:creator>
    <dc:date>2004-03-11T06:11:10Z</dc:date>
    <item>
      <title>System Name problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215738#M1606</link>
      <description>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.&lt;BR /&gt;nslookup is working for those systems on CMS.&lt;BR /&gt;The servers are registered on another DNS server. DNS-Server is added in TCP/IP settings.</description>
      <pubDate>Thu, 11 Mar 2004 05:35:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215738#M1606</guid>
      <dc:creator>Hans Muller</dc:creator>
      <dc:date>2004-03-11T05:35:57Z</dc:date>
    </item>
    <item>
      <title>Re: System Name problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215739#M1607</link>
      <description>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.</description>
      <pubDate>Thu, 11 Mar 2004 06:11:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215739#M1607</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2004-03-11T06:11:10Z</dc:date>
    </item>
    <item>
      <title>Re: System Name problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215740#M1608</link>
      <description>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.</description>
      <pubDate>Thu, 11 Mar 2004 13:59:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215740#M1608</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-03-11T13:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: System Name problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215741#M1609</link>
      <description>Thanx, that's looks to be the problem.&lt;BR /&gt;IP to name working. Name to IP not functioning.</description>
      <pubDate>Mon, 15 Mar 2004 02:27:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/system-name-problems/m-p/3215741#M1609</guid>
      <dc:creator>Hans Muller</dc:creator>
      <dc:date>2004-03-15T02:27:27Z</dc:date>
    </item>
  </channel>
</rss>

